
From nobody Sat Nov  1 01:23:34 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 474CA1A885F for <tsvwg@ietfa.amsl.com>; Sat,  1 Nov 2014 01:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6qMykVwzeMWY for <tsvwg@ietfa.amsl.com>; Sat,  1 Nov 2014 01:23:27 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id E8EDD1A885D for <tsvwg@ietf.org>; Sat,  1 Nov 2014 01:23:26 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id E7B092B454E; Sat,  1 Nov 2014 08:23:25 +0000 (GMT)
Received: from Gorrys-MacBook-Air.local (fgrpf.plus.com [212.159.18.54]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id E70AB2B442A for <tsvwg@ietf.org>; Sat,  1 Nov 2014 08:23:24 +0000 (GMT)
Message-ID: <5454987C.4060800@erg.abdn.ac.uk>
Date: Sat, 01 Nov 2014 08:23:24 +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.9; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: tsvwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/PAP2AqpStcq0DWqfSorSrG__8oQ
Subject: [tsvwg] draft-ietf-tsvwg-port-use-05
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Nov 2014 08:23:29 -0000

The above draft has completed WGLC with minor comments, and the Chairs 
have asked for a new revision to fix these.

We plan to submit this updated ID to our AD.

Gorry
(TSVWG Co-Chair)


From nobody Sat Nov  1 08:05:16 2014
Return-Path: <randall@lakerest.net>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A45061A88D5 for <tsvwg@ietfa.amsl.com>; Sat,  1 Nov 2014 08:05:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.51
X-Spam-Level: 
X-Spam-Status: No, score=-0.51 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id meFfkYvbzJ1m for <tsvwg@ietfa.amsl.com>; Sat,  1 Nov 2014 08:05:12 -0700 (PDT)
Received: from lakerest.net (lakerest.net [162.235.35.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E149E1A88D2 for <tsvwg@ietf.org>; Sat,  1 Nov 2014 08:05:11 -0700 (PDT)
Received: from [192.168.0.2] (97-114-98-97.spkn.qwest.net [97.114.98.97]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id sA1EtAiO045415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 1 Nov 2014 10:55:13 -0400 (EDT) (envelope-from randall@lakerest.net)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <D075B8BB.3D24D%mzanaty@cisco.com>
Date: Sat, 1 Nov 2014 11:05:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F865F129-0555-4F02-922C-61FDCD778FC3@lakerest.net>
References: <D075B8BB.3D24D%mzanaty@cisco.com>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/IAfYXytjXjFRp64bm6wtvK5WYww
Cc: =?windows-1252?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Nov 2014 15:05:14 -0000

Mo:

Comments in-line below..

> On Oct 28, 2014, at 9:18 PM, Mo Zanaty (mzanaty) <mzanaty@cisco.com> =
wrote:
>=20
> Hi,
> While reviewing this draft for becoming mandatory in rtcweb data =
channels, I see two issues, which are independent of rtcweb.
>=20
> 1. If negotiated, NDATA must be used for all messages. The NDATA =
format requires 8 more bytes than DATA (for MID+FSN). But these extra 8 =
bytes are only useful for fragmented messages. To avoid this overhead =
for small non-fragmented messages, can we relax / optimize this rule to =
be NDATA must be used for all *fragmented* messages, while =
non-fragmented messages continue to use DATA?
>=20
> Proposed change to the next-to-last paragraph of section 1.1:
>=20
> OLD:
>    The support of the N-DATA chunk is negotiated during the =
association
>    setup using the Supported Extensions Parameter as defined in
>    [RFC5061].  If N-DATA support has been negotiated for an =
association
>    N-DATA chunks are used for all user-messages and no DATA chunks.  =
It
>    should be noted, that an SCTP implementation needs to support the
>    coexistence of associations using DATA chunks and associations =
using
>    N-DATA chunks.
>=20
> NEW:
>    The support of the N-DATA chunk is negotiated during the =
association
>    setup using the Supported Extensions Parameter as defined in
>    [RFC5061].  If N-DATA support has been negotiated for an =
association
>    N-DATA chunks are used for all fragmented user messages, and
>    DATA chunks are used for all non-fragmented user messages.  It
>    should be noted, that an SCTP implementation needs to support the
>    coexistence of associations using DATA chunks and associations =
using
>    N-DATA chunks.


I will let Michael comment on the above, I think he put that in place to =
be
consistent, but I will leave him to answer..


>=20
> 2. Fragmented messages can=92t be interleaved. This significantly =
dilutes the value of NDATA. Apps that truly care about head of line =
blocking can=92t rely on NDATA at all. They must implement app layer =
fragmentation with messages well below common MTUs to avoid blocking, =
hence defeating NDATA. NDATA is arguably harmful for these apps, since =
it is 8 bytes closer to exceeding the MTU, forcing SCTP fragments and =
hence risking HOL blocking. To avoid this, can we relax this rule to =
allow interleaving fragmented messages, since MID is already part of =
NDATA?
>=20
> Proposed change to the last paragraph of section 3.1:
>=20
> OLD:
>    The sender MUST NOT have more than one ordered fragmented message
>    being produced in any one stream.  The sender MUST NOT have more =
than
>    one un-ordered fragmented message being produced in any one stream.
>    The sender MAY have one ordered and one unordered fragmented =
message
>    being produced within a single stream.  At any time multiple =
streams
>    MAY be producing an ordered or unordered fragmented message.
>=20
> NEW:
>    The sender MAY have more than one ordered fragmented message
>    being produced in any one stream.  The sender MAY have more than
>    one un-ordered fragmented message being produced in any one stream.
>    The sender MAY have multiple ordered and unordered fragmented =
messages
>    being produced within a single stream.  At any time multiple =
streams
>    MAY be producing multiple ordered or unordered fragmented messages.


The above restriction=92s were first put into place *before* a MID was =
added. I notice
that there is not a lot on the MID in the draft.. it needs to be =
specified as a monotonically=20
incrementing number, that is incremented every time a fragmented message =
is sent on any stream. Since
you need a unique identifier for unordered to make it so you can have =
multiple in flight.

As to the ordered side, I don=92t see that you can lift that restriction =
and here is why,
Consider this simple scenario:

BE =3D B
TSN =3D 1
SSN =3D 1
STR =3D 1
MID =3D 1
FSN =3D 0
<=97

BE =3D B
TSN =3D 2
SSN =3D 2
STR =3D 1
MID =3D 2
FSN =3D 0
<=97

BE =3D E
TSN =3D 3
SSN =3D 2
STR =3D 1
MID =3D 2
FSN =3D 1
<=97

BE =3D E
TSN =3D 4
SSN =3D 1
STR =3D 1
MID =3D 1
FSN =3D 1
<=97


Which is what could happen if you loosen the restriction upon ordered =
messages.

First of all from the user perspective, you gain *nothing*. By =
definition, an ordered
message will *not* allow STR=3D1, SSN=3D2 to be delivered *before* =
STR=3D1, SSN=3D1. So=20
by allowing multiple to be assigned TSN=92s you *gain* nothing from the =
user perspective.

Now what you do gain however is a deadlock scenario (which can also be =
used as a DOS=20
attack). Now the above illustrates a simple set of 2 fragment messages, =
this is *not* really what
NDATA addresses, since where you see HOL is where you have 1Megabyte =
messages (or higher). An
application sending 3k messages is *not* going to see HOL and inside the =
same stream you
are enforcing HOL by definition.. But what happens if we *expand* SSN =
from its small
2800 bytes size, into a 500,000 byte message. Assuming a rwnd of 256,000 =
bytes you are deadlocked.
You will have filled the rwnd and have *no* way to deliver SSN=3D2 since =
you are waiting for
SSN=3D1 so you can *not* start the partial delivery API..

This can be used as a dead-lock or an attack vector. Get a bot to setup =
an association, send the
first of SSN=3D1, now fill the rwnd with SSN=3D2 and that association is =
hopelessly deadlocked and
cannot make forward progress.

This is why the restriction was placed on ordered messages.

For the unordered messages, we did add the same restriction. Why, well =
there was no MID, which
means that there was no way for the receiver to tell two fragmented =
messages apart. But there
is still a problem with an unordered message. When you start the partial =
delivery API, you now
may be seeing two unordered messages at the same time on the same =
stream. And in order to prevent
the deadlock described above you would *need* to start the PD-API in =
order to make forward progress
(imagine two 40Meg unordered messages being sent a the same time). Right =
now the Socket API has
no way to tell the difference.. i.e. it has no access to the MID.. so it =
can=92t tell which
message is which.

We *could* possibly loosen the unordered restriction, but it will also =
require work on getting
the socket API to change.. which I don=92t think Michael or I thought =
was worth it since the goal
of the draft was to get rid of the inter-stream HOL. Streams are cheap, =
so if you really wanted
to have 10 unordered 40Meg messages, you could easily put them in each =
one..=20

It would be quite a change to the Socket-API in order to do this, =
possibly effecting the
delivery mode.. but I suppose we could do it if the WG feels that its =
that critical.. I
personally don=92t think it is worth the gain..

Remember, and maybe this needs clarification, the no =93two=94 in flight =
at the same time
is really in respect to the TSN assignment.. i.e. if I send Message 1 =
and Message 2, I must
assign all the TSN=92s of message 1 before starting to assign TSN=92s =
for message 2. You
always have the possibility that TSN=92s will arrive out of order..=20

No matter if the WG wants to remove the restriction on un-ordered and =
complicate the socket-API
I don=92t see how one could remove the restriction on ordered messages.


Best wishes

R

>=20
> Regards,
> Mo
>=20

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





From nobody Tue Nov  4 13:05:23 2014
Return-Path: <mzanaty@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B12961ACF66 for <tsvwg@ietfa.amsl.com>; Tue,  4 Nov 2014 13:05:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.095
X-Spam-Level: 
X-Spam-Status: No, score=-15.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hdlUt-alQ8CB for <tsvwg@ietfa.amsl.com>; Tue,  4 Nov 2014 13:05:17 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 780451ACF6D for <tsvwg@ietf.org>; Tue,  4 Nov 2014 13:05:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9026; q=dns/txt; s=iport; t=1415135117; x=1416344717; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=iwgR0FCayY/urWrIIUm84JERZGcHBmT0wwI2/PhREfY=; b=ReO5MPceRJWh3sRRKQJ0qm4hPL1MYPTtV9D5bhJ7SXBbGzFHRogZ8gIq ZJymqB43/Q7UCaP2pBKDCIzCKqOau+dPlQG+ijGieRN5MFMW0t9mThCDH LYBgkAh11uFJQQgJ5aEVRswbWzXkj+nsALUOvUMrC74RUAZPAN0aQvaBZ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFAJc+WVStJV2d/2dsb2JhbABbgw5UWATOW4Z5VAKBIxYBAQEBAX2EAwEBAwFsCgMFCwIBCA44MiUCBA4FCYgvCQ3KPwEBAQEGAQEBAQEBHJA/AQEcCCsCBYRLBY9bgkWHEoIBglSBQ5UMgX4ggVpsAYEOOYEDAQEB
X-IronPort-AV: E=Sophos;i="5.07,314,1413244800"; d="scan'208";a="369284727"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-6.cisco.com with ESMTP; 04 Nov 2014 21:05:16 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id sA4L5GNV015440 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 4 Nov 2014 21:05:16 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.140]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0195.001; Tue, 4 Nov 2014 15:05:10 -0600
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: Randy Stewart <randall@lakerest.net>
Thread-Topic: [tsvwg] SCTP NDATA draft
Thread-Index: AQHP+HMEYTEJ7HotWEKtmVX6fj9QIA==
Date: Tue, 4 Nov 2014 21:05:10 +0000
Message-ID: <D07E87AF.3DA23%mzanaty@cisco.com>
References: <D075B8BB.3D24D%mzanaty@cisco.com> <F865F129-0555-4F02-922C-61FDCD778FC3@lakerest.net>
In-Reply-To: <F865F129-0555-4F02-922C-61FDCD778FC3@lakerest.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.5.141003
x-originating-ip: [10.81.3.31]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <E95AB9F6C50EB04D85970EAA98F1E55E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/XW-kKSjb_b70E_l5kehMc0yOasc
Cc: =?Windows-1252?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Nov 2014 21:05:21 -0000

Hi Randy,

Good points about filling rwnd and the API lacking MID.

The API issue seems like it could be fixed by just exposing MID in partial
deliveries. Is that very complex in the implementation? It seems rather
straightforward in the API/spec.


The rwnd problem already exists without any proposed changes, since rwnd
is for the entire association, right? For example, if you create 2
streams, send a huge message (>rwnd) on stream1 and a tiny message (<MTU)
on stream2, the default stream schedulers will block the tiny message on
stream2 until rwnd opens, right? You would have to create streams with
non-default schedulers like =B3priority=B2 or =B3fair bandwidth=B2 to avoid
blocking.

Unfortunately, WebRTC data channels have no API to set stream schedulers,
so they always get the default. More discussion of NDATA in the context of
WebRTC data channels here:
http://www.ietf.org/mail-archive/web/rtcweb/current/msg13351.html
(Sorry about scattering this thread between two lists, but tsvwg and
rtcweb are rather disjoint lists, so chairs may complain about cross
posting.)

As for malicious attacks, SCTP is not a secure protocol, so on-path
adversaries can easily flood, deadlock, or otherwise hose either end of
the association, independent of NDATA or any of the proposed changes.
Hence a major reason why WebRTC requires SCTP over DTLS.

Cheers,
Mo


On 11/1/14, 11:05 AM, Randy Stewart <randall@lakerest.net> wrote:

Mo:

Comments in-line below..

> On Oct 28, 2014, at 9:18 PM, Mo Zanaty (mzanaty) <mzanaty@cisco.com>
>wrote:
>=20
> Hi,
> While reviewing this draft for becoming mandatory in rtcweb data
>channels, I see two issues, which are independent of rtcweb.
>=20
> 1. If negotiated, NDATA must be used for all messages. The NDATA format
>requires 8 more bytes than DATA (for MID+FSN). But these extra 8 bytes
>are only useful for fragmented messages. To avoid this overhead for small
>non-fragmented messages, can we relax / optimize this rule to be NDATA
>must be used for all *fragmented* messages, while non-fragmented messages
>continue to use DATA?
>=20
> Proposed change to the next-to-last paragraph of section 1.1:
>=20
> OLD:
>    The support of the N-DATA chunk is negotiated during the association
>    setup using the Supported Extensions Parameter as defined in
>    [RFC5061].  If N-DATA support has been negotiated for an association
>    N-DATA chunks are used for all user-messages and no DATA chunks.  It
>    should be noted, that an SCTP implementation needs to support the
>    coexistence of associations using DATA chunks and associations using
>    N-DATA chunks.
>=20
> NEW:
>    The support of the N-DATA chunk is negotiated during the association
>    setup using the Supported Extensions Parameter as defined in
>    [RFC5061].  If N-DATA support has been negotiated for an association
>    N-DATA chunks are used for all fragmented user messages, and
>    DATA chunks are used for all non-fragmented user messages.  It
>    should be noted, that an SCTP implementation needs to support the
>    coexistence of associations using DATA chunks and associations using
>    N-DATA chunks.


I will let Michael comment on the above, I think he put that in place to be
consistent, but I will leave him to answer..


>=20
> 2. Fragmented messages can=B9t be interleaved. This significantly dilutes
>the value of NDATA. Apps that truly care about head of line blocking
>can=B9t rely on NDATA at all. They must implement app layer fragmentation
>with messages well below common MTUs to avoid blocking, hence defeating
>NDATA. NDATA is arguably harmful for these apps, since it is 8 bytes
>closer to exceeding the MTU, forcing SCTP fragments and hence risking HOL
>blocking. To avoid this, can we relax this rule to allow interleaving
>fragmented messages, since MID is already part of NDATA?
>=20
> Proposed change to the last paragraph of section 3.1:
>=20
> OLD:
>    The sender MUST NOT have more than one ordered fragmented message
>    being produced in any one stream.  The sender MUST NOT have more than
>    one un-ordered fragmented message being produced in any one stream.
>    The sender MAY have one ordered and one unordered fragmented message
>    being produced within a single stream.  At any time multiple streams
>    MAY be producing an ordered or unordered fragmented message.
>=20
> NEW:
>    The sender MAY have more than one ordered fragmented message
>    being produced in any one stream.  The sender MAY have more than
>    one un-ordered fragmented message being produced in any one stream.
>    The sender MAY have multiple ordered and unordered fragmented messages
>    being produced within a single stream.  At any time multiple streams
>    MAY be producing multiple ordered or unordered fragmented messages.


The above restriction=B9s were first put into place *before* a MID was
added. I notice
that there is not a lot on the MID in the draft.. it needs to be specified
as a monotonically=20
incrementing number, that is incremented every time a fragmented message
is sent on any stream. Since
you need a unique identifier for unordered to make it so you can have
multiple in flight.

As to the ordered side, I don=B9t see that you can lift that restriction an=
d
here is why,
Consider this simple scenario:

BE =3D B
TSN =3D 1
SSN =3D 1
STR =3D 1
MID =3D 1
FSN =3D 0
<=8B

BE =3D B
TSN =3D 2
SSN =3D 2
STR =3D 1
MID =3D 2
FSN =3D 0
<=8B

BE =3D E
TSN =3D 3
SSN =3D 2
STR =3D 1
MID =3D 2
FSN =3D 1
<=8B

BE =3D E
TSN =3D 4
SSN =3D 1
STR =3D 1
MID =3D 1
FSN =3D 1
<=8B


Which is what could happen if you loosen the restriction upon ordered
messages.

First of all from the user perspective, you gain *nothing*. By definition,
an ordered
message will *not* allow STR=3D1, SSN=3D2 to be delivered *before* STR=3D1,
SSN=3D1. So=20
by allowing multiple to be assigned TSN=B9s you *gain* nothing from the use=
r
perspective.

Now what you do gain however is a deadlock scenario (which can also be
used as a DOS=20
attack). Now the above illustrates a simple set of 2 fragment messages,
this is *not* really what
NDATA addresses, since where you see HOL is where you have 1Megabyte
messages (or higher). An
application sending 3k messages is *not* going to see HOL and inside the
same stream you
are enforcing HOL by definition.. But what happens if we *expand* SSN from
its small
2800 bytes size, into a 500,000 byte message. Assuming a rwnd of 256,000
bytes you are deadlocked.
You will have filled the rwnd and have *no* way to deliver SSN=3D2 since yo=
u
are waiting for
SSN=3D1 so you can *not* start the partial delivery API..

This can be used as a dead-lock or an attack vector. Get a bot to setup an
association, send the
first of SSN=3D1, now fill the rwnd with SSN=3D2 and that association is
hopelessly deadlocked and
cannot make forward progress.

This is why the restriction was placed on ordered messages.

For the unordered messages, we did add the same restriction. Why, well
there was no MID, which
means that there was no way for the receiver to tell two fragmented
messages apart. But there
is still a problem with an unordered message. When you start the partial
delivery API, you now
may be seeing two unordered messages at the same time on the same stream.
And in order to prevent
the deadlock described above you would *need* to start the PD-API in order
to make forward progress
(imagine two 40Meg unordered messages being sent a the same time). Right
now the Socket API has
no way to tell the difference.. i.e. it has no access to the MID.. so it
can=B9t tell which
message is which.

We *could* possibly loosen the unordered restriction, but it will also
require work on getting
the socket API to change.. which I don=B9t think Michael or I thought was
worth it since the goal
of the draft was to get rid of the inter-stream HOL. Streams are cheap, so
if you really wanted
to have 10 unordered 40Meg messages, you could easily put them in each
one..=20

It would be quite a change to the Socket-API in order to do this, possibly
effecting the
delivery mode.. but I suppose we could do it if the WG feels that its that
critical.. I
personally don=B9t think it is worth the gain..

Remember, and maybe this needs clarification, the no =B3two=B2 in flight at
the same time
is really in respect to the TSN assignment.. i.e. if I send Message 1 and
Message 2, I must
assign all the TSN=B9s of message 1 before starting to assign TSN=B9s for
message 2. You
always have the possibility that TSN=B9s will arrive out of order..

No matter if the WG wants to remove the restriction on un-ordered and
complicate the socket-API
I don=B9t see how one could remove the restriction on ordered messages.


Best wishes

R

>=20
> Regards,
> Mo
>=20

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






From nobody Tue Nov  4 13:17:51 2014
Return-Path: <rrs@netflix.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6274A1A00B5 for <tsvwg@ietfa.amsl.com>; Tue,  4 Nov 2014 13:17:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S3KFF-Nf-3ut for <tsvwg@ietfa.amsl.com>; Tue,  4 Nov 2014 13:17:45 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D42FC1A00CD for <tsvwg@ietf.org>; Tue,  4 Nov 2014 13:17:44 -0800 (PST)
Received: by mail-pa0-f42.google.com with SMTP id bj1so15231892pad.15 for <tsvwg@ietf.org>; Tue, 04 Nov 2014 13:17:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netflix.com; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=IBGOQQj5HhL3Ea/BxONnUiYfWGL2k4gi6aJZSek89h8=; b=RlpGBcRo82TZmO92F/Le9JNAfxB/lcaz01IKyWNJincTgkxstAsvW2hTC7/r7Lzke3 9gFMqsfYnc/pqkPBtWiS1kzClnazQ7UezIJyAWz9VHPEedEp/zTtrJyM7mWnQDDLj99I jWjQqO4PA/AlzyrClInWJHrMJzfmbKGUumJJ0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=IBGOQQj5HhL3Ea/BxONnUiYfWGL2k4gi6aJZSek89h8=; b=HyiQLn1d0RYaqiCajYNE5/wiVMvVadqrM8bSVR92J/6Bx1PUpw8P5AUC/g6RwcjD+/ lKo+Q3vHPgQWIRyimro1YTMWUJ4mG5UJnG5gl3rKvq3o56zX1yJkhnzfMkXB7zL20BSO qN6RtNN5cp9QLhz4mUG3WqU1BUoRWGrt42bQWVTZ4QGmDndIflB+3ohfpcp3/Kh/bBP8 bAwBgoWy7mTzdnoOykhPGvWdP0BOOdz3otgX8p9oa1KyltJlnIKMsk1lYL+/dQT8mgtK AbBu1fciI3uxkeADtDe3E1oICEDPkkrtOfWdCaAhK+ZwY87ZaUgijiw1T+/5GWWvOod+ hslg==
X-Gm-Message-State: ALoCoQlUrMBhyHZdvTShkxHiHPHR/lE3JW2O+PLvXbnWuO9QBt/FeIswWrsJFopgUmsq2/N1a7Wi
X-Received: by 10.68.88.225 with SMTP id bj1mr13198287pbb.118.1415135863897; Tue, 04 Nov 2014 13:17:43 -0800 (PST)
Received: from lgmac-bvermilion.corp.netflix.com ([69.53.236.236]) by mx.google.com with ESMTPSA id n3sm1271209pda.7.2014.11.04.13.17.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Nov 2014 13:17:42 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_0EAB1543-BDA3-47C0-B3A9-FE4211EAE4E7"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Randall Stewart <rrs@netflix.com>
In-Reply-To: <D07E87AF.3DA23%mzanaty@cisco.com>
Date: Tue, 4 Nov 2014 16:17:31 -0500
Message-Id: <A9DDD2B4-00EA-4ED8-855E-B315A5B9DAD7@netflix.com>
References: <D075B8BB.3D24D%mzanaty@cisco.com> <F865F129-0555-4F02-922C-61FDCD778FC3@lakerest.net> <D07E87AF.3DA23%mzanaty@cisco.com>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/ydB8Wj-7EVMj6VXAwawBLjLiDDU
Cc: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Nov 2014 21:17:49 -0000

--Apple-Mail=_0EAB1543-BDA3-47C0-B3A9-FE4211EAE4E7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Nov 4, 2014, at 4:05 PM, Mo Zanaty (mzanaty) <mzanaty@cisco.com> =
wrote:

> Hi Randy,
>=20
> Good points about filling rwnd and the API lacking MID.
>=20
> The API issue seems like it could be fixed by just exposing MID in =
partial
> deliveries. Is that very complex in the implementation? It seems =
rather
> straightforward in the API/spec.
>=20
>=20
> The rwnd problem already exists without any proposed changes, since =
rwnd
> is for the entire association, right? For example, if you create 2
> streams, send a huge message (>rwnd) on stream1 and a tiny message =
(<MTU)
> on stream2, the default stream schedulers will block the tiny message =
on
> stream2 until rwnd opens, right? You would have to create streams with
> non-default schedulers like =B3priority=B2 or =B3fair bandwidth=B2 to =
avoid
> blocking.

It may be slow,  but you *can* make forward progress. I.e. you *can* =
deliver
messages from a stream say stream 1, even if stream 2 is hogging
up rwnd space. What your change breaks is  you create a situation where
you *can not* make forward progress at all. This is vastly different =
then
the current RFC or draft. You can *always* make forward progress, it may =
be slow
but you can.

>=20
> Unfortunately, WebRTC data channels have no API to set stream =
schedulers,
> so they always get the default. More discussion of NDATA in the =
context of
> WebRTC data channels here:
> http://www.ietf.org/mail-archive/web/rtcweb/current/msg13351.html
> (Sorry about scattering this thread between two lists, but tsvwg and
> rtcweb are rather disjoint lists, so chairs may complain about cross
> posting.)

Of course that again is an API problem=20

Just as in the un-ordered case for SCTP :-D

>=20
> As for malicious attacks, SCTP is not a secure protocol, so on-path
> adversaries can easily flood, deadlock, or otherwise hose either end =
of
> the association, independent of NDATA or any of the proposed changes.
> Hence a major reason why WebRTC requires SCTP over DTLS.
>=20


The protocol is designed in general to *not* deadlock. Adding a deadlock =
to
the spec is something I could never agree with.

R

> Cheers,
> Mo
>=20
>=20
> On 11/1/14, 11:05 AM, Randy Stewart <randall@lakerest.net> wrote:
>=20
> Mo:
>=20
> Comments in-line below..
>=20
>> On Oct 28, 2014, at 9:18 PM, Mo Zanaty (mzanaty) <mzanaty@cisco.com>
>> wrote:
>>=20
>> Hi,
>> While reviewing this draft for becoming mandatory in rtcweb data
>> channels, I see two issues, which are independent of rtcweb.
>>=20
>> 1. If negotiated, NDATA must be used for all messages. The NDATA =
format
>> requires 8 more bytes than DATA (for MID+FSN). But these extra 8 =
bytes
>> are only useful for fragmented messages. To avoid this overhead for =
small
>> non-fragmented messages, can we relax / optimize this rule to be =
NDATA
>> must be used for all *fragmented* messages, while non-fragmented =
messages
>> continue to use DATA?
>>=20
>> Proposed change to the next-to-last paragraph of section 1.1:
>>=20
>> OLD:
>>   The support of the N-DATA chunk is negotiated during the =
association
>>   setup using the Supported Extensions Parameter as defined in
>>   [RFC5061].  If N-DATA support has been negotiated for an =
association
>>   N-DATA chunks are used for all user-messages and no DATA chunks.  =
It
>>   should be noted, that an SCTP implementation needs to support the
>>   coexistence of associations using DATA chunks and associations =
using
>>   N-DATA chunks.
>>=20
>> NEW:
>>   The support of the N-DATA chunk is negotiated during the =
association
>>   setup using the Supported Extensions Parameter as defined in
>>   [RFC5061].  If N-DATA support has been negotiated for an =
association
>>   N-DATA chunks are used for all fragmented user messages, and
>>   DATA chunks are used for all non-fragmented user messages.  It
>>   should be noted, that an SCTP implementation needs to support the
>>   coexistence of associations using DATA chunks and associations =
using
>>   N-DATA chunks.
>=20
>=20
> I will let Michael comment on the above, I think he put that in place =
to be
> consistent, but I will leave him to answer..
>=20
>=20
>>=20
>> 2. Fragmented messages can=B9t be interleaved. This significantly =
dilutes
>> the value of NDATA. Apps that truly care about head of line blocking
>> can=B9t rely on NDATA at all. They must implement app layer =
fragmentation
>> with messages well below common MTUs to avoid blocking, hence =
defeating
>> NDATA. NDATA is arguably harmful for these apps, since it is 8 bytes
>> closer to exceeding the MTU, forcing SCTP fragments and hence risking =
HOL
>> blocking. To avoid this, can we relax this rule to allow interleaving
>> fragmented messages, since MID is already part of NDATA?
>>=20
>> Proposed change to the last paragraph of section 3.1:
>>=20
>> OLD:
>>   The sender MUST NOT have more than one ordered fragmented message
>>   being produced in any one stream.  The sender MUST NOT have more =
than
>>   one un-ordered fragmented message being produced in any one stream.
>>   The sender MAY have one ordered and one unordered fragmented =
message
>>   being produced within a single stream.  At any time multiple =
streams
>>   MAY be producing an ordered or unordered fragmented message.
>>=20
>> NEW:
>>   The sender MAY have more than one ordered fragmented message
>>   being produced in any one stream.  The sender MAY have more than
>>   one un-ordered fragmented message being produced in any one stream.
>>   The sender MAY have multiple ordered and unordered fragmented =
messages
>>   being produced within a single stream.  At any time multiple =
streams
>>   MAY be producing multiple ordered or unordered fragmented messages.
>=20
>=20
> The above restriction=B9s were first put into place *before* a MID was
> added. I notice
> that there is not a lot on the MID in the draft.. it needs to be =
specified
> as a monotonically=20
> incrementing number, that is incremented every time a fragmented =
message
> is sent on any stream. Since
> you need a unique identifier for unordered to make it so you can have
> multiple in flight.
>=20
> As to the ordered side, I don=B9t see that you can lift that =
restriction and
> here is why,
> Consider this simple scenario:
>=20
> BE =3D B
> TSN =3D 1
> SSN =3D 1
> STR =3D 1
> MID =3D 1
> FSN =3D 0
> <=8B
>=20
> BE =3D B
> TSN =3D 2
> SSN =3D 2
> STR =3D 1
> MID =3D 2
> FSN =3D 0
> <=8B
>=20
> BE =3D E
> TSN =3D 3
> SSN =3D 2
> STR =3D 1
> MID =3D 2
> FSN =3D 1
> <=8B
>=20
> BE =3D E
> TSN =3D 4
> SSN =3D 1
> STR =3D 1
> MID =3D 1
> FSN =3D 1
> <=8B
>=20
>=20
> Which is what could happen if you loosen the restriction upon ordered
> messages.
>=20
> First of all from the user perspective, you gain *nothing*. By =
definition,
> an ordered
> message will *not* allow STR=3D1, SSN=3D2 to be delivered *before* =
STR=3D1,
> SSN=3D1. So=20
> by allowing multiple to be assigned TSN=B9s you *gain* nothing from =
the user
> perspective.
>=20
> Now what you do gain however is a deadlock scenario (which can also be
> used as a DOS=20
> attack). Now the above illustrates a simple set of 2 fragment =
messages,
> this is *not* really what
> NDATA addresses, since where you see HOL is where you have 1Megabyte
> messages (or higher). An
> application sending 3k messages is *not* going to see HOL and inside =
the
> same stream you
> are enforcing HOL by definition.. But what happens if we *expand* SSN =
from
> its small
> 2800 bytes size, into a 500,000 byte message. Assuming a rwnd of =
256,000
> bytes you are deadlocked.
> You will have filled the rwnd and have *no* way to deliver SSN=3D2 =
since you
> are waiting for
> SSN=3D1 so you can *not* start the partial delivery API..
>=20
> This can be used as a dead-lock or an attack vector. Get a bot to =
setup an
> association, send the
> first of SSN=3D1, now fill the rwnd with SSN=3D2 and that association =
is
> hopelessly deadlocked and
> cannot make forward progress.
>=20
> This is why the restriction was placed on ordered messages.
>=20
> For the unordered messages, we did add the same restriction. Why, well
> there was no MID, which
> means that there was no way for the receiver to tell two fragmented
> messages apart. But there
> is still a problem with an unordered message. When you start the =
partial
> delivery API, you now
> may be seeing two unordered messages at the same time on the same =
stream.
> And in order to prevent
> the deadlock described above you would *need* to start the PD-API in =
order
> to make forward progress
> (imagine two 40Meg unordered messages being sent a the same time). =
Right
> now the Socket API has
> no way to tell the difference.. i.e. it has no access to the MID.. so =
it
> can=B9t tell which
> message is which.
>=20
> We *could* possibly loosen the unordered restriction, but it will also
> require work on getting
> the socket API to change.. which I don=B9t think Michael or I thought =
was
> worth it since the goal
> of the draft was to get rid of the inter-stream HOL. Streams are =
cheap, so
> if you really wanted
> to have 10 unordered 40Meg messages, you could easily put them in each
> one..=20
>=20
> It would be quite a change to the Socket-API in order to do this, =
possibly
> effecting the
> delivery mode.. but I suppose we could do it if the WG feels that its =
that
> critical.. I
> personally don=B9t think it is worth the gain..
>=20
> Remember, and maybe this needs clarification, the no =B3two=B2 in =
flight at
> the same time
> is really in respect to the TSN assignment.. i.e. if I send Message 1 =
and
> Message 2, I must
> assign all the TSN=B9s of message 1 before starting to assign TSN=B9s =
for
> message 2. You
> always have the possibility that TSN=B9s will arrive out of order..
>=20
> No matter if the WG wants to remove the restriction on un-ordered and
> complicate the socket-API
> I don=B9t see how one could remove the restriction on ordered =
messages.
>=20
>=20
> Best wishes
>=20
> R
>=20
>>=20
>> Regards,
>> Mo
>>=20
>=20
> -----
> Randall Stewart
> randall@lakerest.net

--------
Randall Stewart
rrs@netflix.com
803-317-4952






--Apple-Mail=_0EAB1543-BDA3-47C0-B3A9-FE4211EAE4E7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Nov 4, 2014, at 4:05 PM, Mo Zanaty =
(mzanaty) &lt;<a =
href=3D"mailto:mzanaty@cisco.com">mzanaty@cisco.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;">Hi Randy,<br><br>Good points about =
filling rwnd and the API lacking MID.<br><br>The API issue seems like it =
could be fixed by just exposing MID in partial<br>deliveries. Is that =
very complex in the implementation? It seems rather<br>straightforward =
in the API/spec.<br><br><br>The rwnd problem already exists without any =
proposed changes, since rwnd<br>is for the entire association, right? =
For example, if you create 2<br>streams, send a huge message (&gt;rwnd) =
on stream1 and a tiny message (&lt;MTU)<br>on stream2, the default =
stream schedulers will block the tiny message on<br>stream2 until rwnd =
opens, right? You would have to create streams with<br>non-default =
schedulers like =B3priority=B2 or =B3fair bandwidth=B2 to =
avoid<br>blocking.<br></div></blockquote><div><br></div><div>It may be =
slow, &nbsp;but you *can* make forward progress. I.e. you *can* =
deliver</div><div>messages from a stream say stream 1, even if stream 2 =
is hogging</div><div>up rwnd space. What your change breaks is &nbsp;you =
create a situation where</div><div>you *can not* make forward progress =
at all. This is vastly different then</div><div>the current RFC or =
draft. You can *always* make forward progress, it may be =
slow</div><div>but you can.</div><br><blockquote type=3D"cite"><div =
style=3D"font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br>Unfortunately, WebRTC data channels =
have no API to set stream schedulers,<br>so they always get the default. =
More discussion of NDATA in the context of<br>WebRTC data channels =
here:<br><a =
href=3D"http://www.ietf.org/mail-archive/web/rtcweb/current/msg13351.html"=
>http://www.ietf.org/mail-archive/web/rtcweb/current/msg13351.html</a><br>=
(Sorry about scattering this thread between two lists, but tsvwg =
and<br>rtcweb are rather disjoint lists, so chairs may complain about =
cross<br>posting.)<br></div></blockquote><div><br></div><div>Of course =
that again is an API problem&nbsp;</div><div><br></div><div>Just as in =
the un-ordered case for SCTP :-D</div><br><blockquote type=3D"cite"><div =
style=3D"font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br>As for malicious attacks, SCTP is =
not a secure protocol, so on-path<br>adversaries can easily flood, =
deadlock, or otherwise hose either end of<br>the association, =
independent of NDATA or any of the proposed changes.<br>Hence a major =
reason why WebRTC requires SCTP over =
DTLS.<br><br></div></blockquote><div><br></div><div><br></div><div>The =
protocol is designed in general to *not* deadlock. Adding a deadlock =
to</div><div>the spec is something I could never agree =
with.</div><div><br></div><div>R</div><br><blockquote type=3D"cite"><div =
style=3D"font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;">Cheers,<br>Mo<br><br><br>On 11/1/14, =
11:05 AM, Randy Stewart &lt;<a =
href=3D"mailto:randall@lakerest.net">randall@lakerest.net</a>&gt; =
wrote:<br><br>Mo:<br><br>Comments in-line below..<br><br><blockquote =
type=3D"cite">On Oct 28, 2014, at 9:18 PM, Mo Zanaty (mzanaty) &lt;<a =
href=3D"mailto:mzanaty@cisco.com">mzanaty@cisco.com</a>&gt;<br>wrote:<br><=
br>Hi,<br>While reviewing this draft for becoming mandatory in rtcweb =
data<br>channels, I see two issues, which are independent of =
rtcweb.<br><br>1. If negotiated, NDATA must be used for all messages. =
The NDATA format<br>requires 8 more bytes than DATA (for MID+FSN). But =
these extra 8 bytes<br>are only useful for fragmented messages. To avoid =
this overhead for small<br>non-fragmented messages, can we relax / =
optimize this rule to be NDATA<br>must be used for all *fragmented* =
messages, while non-fragmented messages<br>continue to use =
DATA?<br><br>Proposed change to the next-to-last paragraph of section =
1.1:<br><br>OLD:<br>&nbsp;&nbsp;The support of the N-DATA chunk is =
negotiated during the association<br>&nbsp;&nbsp;setup using the =
Supported Extensions Parameter as defined in<br>&nbsp;&nbsp;[RFC5061]. =
&nbsp;If N-DATA support has been negotiated for an =
association<br>&nbsp;&nbsp;N-DATA chunks are used for all user-messages =
and no DATA chunks. &nbsp;It<br>&nbsp;&nbsp;should be noted, that an =
SCTP implementation needs to support the<br>&nbsp;&nbsp;coexistence of =
associations using DATA chunks and associations =
using<br>&nbsp;&nbsp;N-DATA chunks.<br><br>NEW:<br>&nbsp;&nbsp;The =
support of the N-DATA chunk is negotiated during the =
association<br>&nbsp;&nbsp;setup using the Supported Extensions =
Parameter as defined in<br>&nbsp;&nbsp;[RFC5061]. &nbsp;If N-DATA =
support has been negotiated for an association<br>&nbsp;&nbsp;N-DATA =
chunks are used for all fragmented user messages, =
and<br>&nbsp;&nbsp;DATA chunks are used for all non-fragmented user =
messages. &nbsp;It<br>&nbsp;&nbsp;should be noted, that an SCTP =
implementation needs to support the<br>&nbsp;&nbsp;coexistence of =
associations using DATA chunks and associations =
using<br>&nbsp;&nbsp;N-DATA chunks.<br></blockquote><br><br>I will let =
Michael comment on the above, I think he put that in place to =
be<br>consistent, but I will leave him to =
answer..<br><br><br><blockquote type=3D"cite"><br>2. Fragmented messages =
can=B9t be interleaved. This significantly dilutes<br>the value of =
NDATA. Apps that truly care about head of line blocking<br>can=B9t rely =
on NDATA at all. They must implement app layer fragmentation<br>with =
messages well below common MTUs to avoid blocking, hence =
defeating<br>NDATA. NDATA is arguably harmful for these apps, since it =
is 8 bytes<br>closer to exceeding the MTU, forcing SCTP fragments and =
hence risking HOL<br>blocking. To avoid this, can we relax this rule to =
allow interleaving<br>fragmented messages, since MID is already part of =
NDATA?<br><br>Proposed change to the last paragraph of section =
3.1:<br><br>OLD:<br>&nbsp;&nbsp;The sender MUST NOT have more than one =
ordered fragmented message<br>&nbsp;&nbsp;being produced in any one =
stream. &nbsp;The sender MUST NOT have more than<br>&nbsp;&nbsp;one =
un-ordered fragmented message being produced in any one =
stream.<br>&nbsp;&nbsp;The sender MAY have one ordered and one unordered =
fragmented message<br>&nbsp;&nbsp;being produced within a single stream. =
&nbsp;At any time multiple streams<br>&nbsp;&nbsp;MAY be producing an =
ordered or unordered fragmented message.<br><br>NEW:<br>&nbsp;&nbsp;The =
sender MAY have more than one ordered fragmented =
message<br>&nbsp;&nbsp;being produced in any one stream. &nbsp;The =
sender MAY have more than<br>&nbsp;&nbsp;one un-ordered fragmented =
message being produced in any one stream.<br>&nbsp;&nbsp;The sender MAY =
have multiple ordered and unordered fragmented =
messages<br>&nbsp;&nbsp;being produced within a single stream. &nbsp;At =
any time multiple streams<br>&nbsp;&nbsp;MAY be producing multiple =
ordered or unordered fragmented messages.<br></blockquote><br><br>The =
above restriction=B9s were first put into place *before* a MID =
was<br>added. I notice<br>that there is not a lot on the MID in the =
draft.. it needs to be specified<br>as a monotonically<span =
class=3D"Apple-converted-space">&nbsp;</span><br>incrementing number, =
that is incremented every time a fragmented message<br>is sent on any =
stream. Since<br>you need a unique identifier for unordered to make it =
so you can have<br>multiple in flight.<br><br>As to the ordered side, I =
don=B9t see that you can lift that restriction and<br>here is =
why,<br>Consider this simple scenario:<br><br>BE =3D B<br>TSN =3D =
1<br>SSN =3D 1<br>STR =3D 1<br>MID =3D 1<br>FSN =3D 0<br>&lt;=8B<br><br>BE=
 =3D B<br>TSN =3D 2<br>SSN =3D 2<br>STR =3D 1<br>MID =3D 2<br>FSN =3D =
0<br>&lt;=8B<br><br>BE =3D E<br>TSN =3D 3<br>SSN =3D 2<br>STR =3D =
1<br>MID =3D 2<br>FSN =3D 1<br>&lt;=8B<br><br>BE =3D E<br>TSN =3D =
4<br>SSN =3D 1<br>STR =3D 1<br>MID =3D 1<br>FSN =3D =
1<br>&lt;=8B<br><br><br>Which is what could happen if you loosen the =
restriction upon ordered<br>messages.<br><br>First of all from the user =
perspective, you gain *nothing*. By definition,<br>an ordered<br>message =
will *not* allow STR=3D1, SSN=3D2 to be delivered *before* =
STR=3D1,<br>SSN=3D1. So<span =
class=3D"Apple-converted-space">&nbsp;</span><br>by allowing multiple to =
be assigned TSN=B9s you *gain* nothing from the =
user<br>perspective.<br><br>Now what you do gain however is a deadlock =
scenario (which can also be<br>used as a DOS<span =
class=3D"Apple-converted-space">&nbsp;</span><br>attack). Now the above =
illustrates a simple set of 2 fragment messages,<br>this is *not* really =
what<br>NDATA addresses, since where you see HOL is where you have =
1Megabyte<br>messages (or higher). An<br>application sending 3k messages =
is *not* going to see HOL and inside the<br>same stream you<br>are =
enforcing HOL by definition.. But what happens if we *expand* SSN =
from<br>its small<br>2800 bytes size, into a 500,000 byte message. =
Assuming a rwnd of 256,000<br>bytes you are deadlocked.<br>You will have =
filled the rwnd and have *no* way to deliver SSN=3D2 since you<br>are =
waiting for<br>SSN=3D1 so you can *not* start the partial delivery =
API..<br><br>This can be used as a dead-lock or an attack vector. Get a =
bot to setup an<br>association, send the<br>first of SSN=3D1, now fill =
the rwnd with SSN=3D2 and that association is<br>hopelessly deadlocked =
and<br>cannot make forward progress.<br><br>This is why the restriction =
was placed on ordered messages.<br><br>For the unordered messages, we =
did add the same restriction. Why, well<br>there was no MID, =
which<br>means that there was no way for the receiver to tell two =
fragmented<br>messages apart. But there<br>is still a problem with an =
unordered message. When you start the partial<br>delivery API, you =
now<br>may be seeing two unordered messages at the same time on the same =
stream.<br>And in order to prevent<br>the deadlock described above you =
would *need* to start the PD-API in order<br>to make forward =
progress<br>(imagine two 40Meg unordered messages being sent a the same =
time). Right<br>now the Socket API has<br>no way to tell the =
difference.. i.e. it has no access to the MID.. so it<br>can=B9t tell =
which<br>message is which.<br><br>We *could* possibly loosen the =
unordered restriction, but it will also<br>require work on =
getting<br>the socket API to change.. which I don=B9t think Michael or I =
thought was<br>worth it since the goal<br>of the draft was to get rid of =
the inter-stream HOL. Streams are cheap, so<br>if you really =
wanted<br>to have 10 unordered 40Meg messages, you could easily put them =
in each<br>one..<span =
class=3D"Apple-converted-space">&nbsp;</span><br><br>It would be quite a =
change to the Socket-API in order to do this, possibly<br>effecting =
the<br>delivery mode.. but I suppose we could do it if the WG feels that =
its that<br>critical.. I<br>personally don=B9t think it is worth the =
gain..<br><br>Remember, and maybe this needs clarification, the no =B3two=B2=
 in flight at<br>the same time<br>is really in respect to the TSN =
assignment.. i.e. if I send Message 1 and<br>Message 2, I must<br>assign =
all the TSN=B9s of message 1 before starting to assign TSN=B9s =
for<br>message 2. You<br>always have the possibility that TSN=B9s will =
arrive out of order..<br><br>No matter if the WG wants to remove the =
restriction on un-ordered and<br>complicate the socket-API<br>I don=B9t =
see how one could remove the restriction on ordered =
messages.<br><br><br>Best wishes<br><br>R<br><br><blockquote =
type=3D"cite"><br>Regards,<br>Mo<br><br></blockquote><br>-----<br>Randall =
Stewart<br><a =
href=3D"mailto:randall@lakerest.net">randall@lakerest.net</a></div></block=
quote></div><br><div apple-content-edited=3D"true">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: =
auto; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div =
style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div>--------</div><div>Randall Stewart</div><div><a =
href=3D"mailto:rrs@netflix.com">rrs@netflix.com</a></div><div>803-317-4952=
</div><div><br></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_0EAB1543-BDA3-47C0-B3A9-FE4211EAE4E7--


From nobody Tue Nov  4 13:46:38 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ADE11A0141 for <tsvwg@ietfa.amsl.com>; Tue,  4 Nov 2014 13:46:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R4maGjsco0aN for <tsvwg@ietfa.amsl.com>; Tue,  4 Nov 2014 13:46:32 -0800 (PST)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 614371A0146 for <tsvwg@ietf.org>; Tue,  4 Nov 2014 13:46:32 -0800 (PST)
Received: by mail-wi0-f179.google.com with SMTP id h11so315785wiw.12 for <tsvwg@ietf.org>; Tue, 04 Nov 2014 13:46:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=X217JxrP9KRtvX+InUDHUsj7q7PtVCL571axKD7+l6s=; b=CJXRXuRUODqJg6A2INRjwzwSxRv2nsJufjYlk8xQ8RTS6xUbvJ81qGM4dOyCm30VEq caUgABDriRVF+z0dTxVyj/hDJBlKmicjypND1N2wZrKfuDYb9EULQJOz330b3AytcAur ef6PK/nlldbBleefeCxKL2XGJFbefeoTQC0L8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=X217JxrP9KRtvX+InUDHUsj7q7PtVCL571axKD7+l6s=; b=Yu1ZWC47u4R2/TQjGLYVXm8W5hyCGqJQG3GS/umeELwGvEd4fBBSXzw9FbA9wp9VH4 Rkums/jcJQKHc8BTxh/QeaEzIqsDadZGmQmv5KXg0u5yIpylxWXgDPQqZicFzSKoQVQS gWvKv3/4CXZfsb6dANWjOBnIZ4BH/pg+APaKnPgTRIS4SOgL6ofa2ek7GM25Ca3Aw+xT HUtOPF4qoSO7i5gOZKzbQhT+Fc66CpVNrF1r+O8M52Aap9vfTLE/vZ5rAPRK8QLmH5Sl LvGX9tWCFKYQkq8XNbjMszE9MIAIsdBSzp3mcEQoc35yw3dByjBbo8g3A56q0r2DbcCC EWVQ==
X-Gm-Message-State: ALoCoQlgqL3b9GuFBcFyP7T/BgDjTg5fg/k+bXljTp4/F86qQrn3hjFfx1XIlq+Br7EP133TzVNrCy6HnDL+icHT9n9hvpLEpapyD7BqT8AdPkg4ZAOWeBM=
X-Received: by 10.180.182.195 with SMTP id eg3mr683419wic.31.1415137590035; Tue, 04 Nov 2014 13:46:30 -0800 (PST)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <D075B8BB.3D24D%mzanaty@cisco.com> <F865F129-0555-4F02-922C-61FDCD778FC3@lakerest.net>
In-Reply-To: <F865F129-0555-4F02-922C-61FDCD778FC3@lakerest.net>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLPgmF8M9ZhEd0HzQpwy3Li9Fcu7AKeHfNNmjzvrjA=
Date: Tue, 4 Nov 2014 22:46:30 +0100
Message-ID: <cdab95a79dac5c5ee9c45bf90224e8b5@mail.gmail.com>
To: Randy Stewart <randall@lakerest.net>, "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/EEwMxVn_ye0RvRRmdV0-ogAUfCE
Cc: =?UTF-8?Q?Michael_T=C3=BCxen?= <Michael.Tuexen@lurchi.franken.de>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Nov 2014 21:46:34 -0000

Hi,


>>
>> NEW:
>>    The sender MAY have more than one ordered fragmented message
>>    being produced in any one stream.  The sender MAY have more than
>>    one un-ordered fragmented message being produced in any one stream.
>>    The sender MAY have multiple ordered and unordered fragmented
>messages
>>    being produced within a single stream.  At any time multiple streams
>>    MAY be producing multiple ordered or unordered fragmented messages.
>
>
>The above restriction=E2=80=99s were first put into place *before* a MID w=
as
added. I
>notice that there is not a lot on the MID in the draft.. it needs to be
specified
>as a monotonically incrementing number, that is incremented every time a
>fragmented message is sent on any stream. Since you need a unique
>identifier for unordered to make it so you can have multiple in flight.
>
[Karen ]
I think that it is key to have the word "produced" be clarified.

It would be extremely inefficient if  this was intended to mean that only
the fragments
of one message (or one unordered and one ordered - meaning two messages)
may be in flight on
each stream.  This might be ok, when the use case scenario in mind is a
message (to be fragmented) which is larger than the RCV buffer,
but not in general.  E.g. not when there are messages  larger than PMTU
but << RCV buffer.

I think that it would be important to have this clarified as to explain
that what is meant is that only fragments of unordered messages may
overtake other message fragments or messages written into the stream in
respect to the order in which TSN numbers  are assigned and further that
the mutual sequential order in between sequentially written unordered
messages are maintained (as the order  is maintained for the messages
written for in-order delivery).

BR, Karen


From nobody Tue Nov  4 14:51:35 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D211A1A0276 for <tsvwg@ietfa.amsl.com>; Tue,  4 Nov 2014 14:51:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.895
X-Spam-Level: 
X-Spam-Status: No, score=-4.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a7Nqh3IwmBfF for <tsvwg@ietfa.amsl.com>; Tue,  4 Nov 2014 14:51:31 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8EBF1A0267 for <tsvwg@ietf.org>; Tue,  4 Nov 2014 14:51:30 -0800 (PST)
Received: from maildlpprd56.lss.emc.com (maildlpprd56.lss.emc.com [10.106.48.160]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sA4MpS8o027098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Tue, 4 Nov 2014 17:51:29 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com sA4MpS8o027098
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1415141489; bh=itKWx0qr67rZEo2ajvN1m7XzBd8=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=oCHEm0X66he4wfjoXN3v7c39lKhbJRQhU100dkJYP9jbTEozGQ8V5HYTWtfBDDdKv U2H/uL8xd7rcLx6DvkL4dMF866GsJDYclVcbPHX50wAYemBCmiyI6Ee4wdMsW5+yaJ R8bR8hkv2lbFqKTXj60iW41RhE+ugrCZeK83NxzQ=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com sA4MpS8o027098
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd56.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Tue, 4 Nov 2014 17:51:12 -0500
Received: from mxhub39.corp.emc.com (mxhub39.corp.emc.com [128.222.70.106]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sA4MpEGb020925 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Tue, 4 Nov 2014 17:51:14 -0500
Received: from MXHUB101.corp.emc.com (10.253.50.15) by mxhub39.corp.emc.com (128.222.70.106) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 4 Nov 2014 17:51:14 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB101.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Tue, 4 Nov 2014 17:51:14 -0500
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: IMPORTANT: tsvwg now on Thu: 0900 & 1300
Thread-Index: Ac/4gcsog7cfA08BQJqdQMpdJZ/DTw==
Importance: high
X-Priority: 1
Date: Tue, 4 Nov 2014 22:51:13 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493623BF57@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.13.37.246]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: public, GIS Solicitation
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/cW5g_3-8fFwkx_kHSu3MPGlTX5U
Subject: [tsvwg] IMPORTANT: tsvwg now on Thu: 0900 & 1300
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Nov 2014 22:51:33 -0000

In order to avoid the conflict with dclcrg on Tue in Honolulu,
the Tue 1300-1500 tsvwg meeting session has been swapped with
the Thu 0900-1130 taps meeting session.

*** TSVWG session times for Honolulu are now: ***
*** Thursday, November 13, 0900-1130 *and* 1300-1500. ***

Due to the late nature of this schedule change (for which the
responsible IRTF and IESG folks profusely apologize ...), I want
to offer anyone who has other plans for Thu 0900-1130 (the new
tsvwg time slot) to ask for specific drafts to be assigned to
the original 1300-1500 time slot.  Conflict list:
	- Thu 0900-1130: 6tisch nfvrg lmap mmusic manet spring tls
	- Thu 1300-1500: dnssd lime ecrit idr saag
Requests can be sent to the list or directly to the chairs.  The
sooner, the better, please.  We can't promise to honor all
requests, but we'll try to do what we can.

The overall agenda plan is that the first meeting session
(Thu 0900-1130) will run short - by how much will be determined
when the final tsvwg agenda is uploaded later this week.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From nobody Wed Nov  5 12:02:13 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7D11A7009 for <tsvwg@ietfa.amsl.com>; Wed,  5 Nov 2014 12:02:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AwWMiyDLtMHk for <tsvwg@ietfa.amsl.com>; Wed,  5 Nov 2014 12:02:07 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B0C4B1ACCC7 for <tsvwg@ietf.org>; Wed,  5 Nov 2014 12:01:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
To: tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.2.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141105200122.32478.62139.idtracker@ietfa.amsl.com>
Date: Wed, 05 Nov 2014 12:01:22 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/s1gKvJkj7VBLFFMUZdgU5iKbZTs
Subject: [tsvwg] Milestones changed for tsvwg WG
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 05 Nov 2014 20:02:09 -0000

Deleted milestone "Submit 'Â‘Multicast UDP Guidelines' as a BCP RFC".

Changed milestone "Submit 'Quick Failover Algorithm in SCTP' to the
IESG for consideration as an Experimental RFC", set description to
"Submit 'Quick Failover Algorithm in SCTP' to the IESG for
consideration as a Proposed Standard RFC", set due date to December
2014 from May 2014.

Changed milestone "Submit 'SCTP New Data Chunk' as a PS RFC", set
description to "Submit 'SCTP New Data Chunk' as a Proposed Standard
RFC", set due date to February 2015 from July 2014.

Changed milestone "Submit 'DSCP packet markings for RTCWeb QoS' to
IESG as a Proposed Standard RFC", set due date to August 2015 from
September 2014.

Changed milestone "Submit 'Specification of GRE in UDP encapsulation'
to IESG as a PS RFC", set due date to December 2015 from December
2014.

URL: http://datatracker.ietf.org/wg/tsvwg/charter/


From nobody Wed Nov  5 12:03:19 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96C9F1ACC89 for <tsvwg@ietfa.amsl.com>; Wed,  5 Nov 2014 12:03:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fbb5ZB15DmTq for <tsvwg@ietfa.amsl.com>; Wed,  5 Nov 2014 12:03:04 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E0F6E1ACCE9 for <tsvwg@ietf.org>; Wed,  5 Nov 2014 12:02:11 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.2.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141105200211.22783.77246.idtracker@ietfa.amsl.com>
Date: Wed, 05 Nov 2014 12:02:11 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/wcygIfvBVI5l9WUzur_fIpE8S2w
Subject: [tsvwg] Milestones changed for tsvwg WG
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 05 Nov 2014 20:03:06 -0000

Changed milestone "Submit 'Network Transport Circuit Breakers' to
IESG", set state to active from review, accepting new milestone.

URL: http://datatracker.ietf.org/wg/tsvwg/charter/


From nobody Sat Nov  8 11:25:31 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD8F1A0B76 for <tsvwg@ietfa.amsl.com>; Sat,  8 Nov 2014 11:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.482
X-Spam-Level: 
X-Spam-Status: No, score=-1.482 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id edoDWOakhoE0 for <tsvwg@ietfa.amsl.com>; Sat,  8 Nov 2014 11:25:27 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFC9F1A033B for <tsvwg@ietf.org>; Sat,  8 Nov 2014 11:25:27 -0800 (PST)
Received: from maildlpprd01.lss.emc.com (maildlpprd01.lss.emc.com [10.253.24.33]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sA8JPQm9016359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Sat, 8 Nov 2014 14:25:26 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com sA8JPQm9016359
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1415474726; bh=evl9HzQZSBm1Q0pSfS77N4C4Rzg=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=TO+sDaz6tiHmVIVtL0N/pfpYkctbrV0I6b1t3xLiWa2SKkd/DvLIjJC3seFa1/Qz2 1QbinbTskbIA37bOOxgn8l3eSXYYlXL7DcyloUf46FElxf/j5daScwB2D8fuNywz+2 wOqvc4A+n5PFK6+OpoyAPXWg5w8IbZY4o4oBUqnE=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com sA8JPQm9016359
Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd01.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Sat, 8 Nov 2014 14:24:49 -0500
Received: from mxhub21.corp.emc.com (mxhub21.corp.emc.com [128.222.70.133]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sA8JP21H025040 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Sat, 8 Nov 2014 14:25:02 -0500
Received: from MXHUB102.corp.emc.com (10.253.58.15) by mxhub21.corp.emc.com (128.222.70.133) with Microsoft SMTP Server (TLS) id 8.3.327.1; Sat, 8 Nov 2014 14:25:01 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB102.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Sat, 8 Nov 2014 14:25:01 -0500
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Revised tsvwg Honolulu agenda posted
Thread-Index: Ac/7ia/5Vci2GjcSS9GiTt/9RIREMA==
Date: Sat, 8 Nov 2014 19:25:00 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936244A55@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.13.60.126]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd53.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/kFJatXYvY5CMJwvZ-z3kGzbQJ44
Subject: [tsvwg] Revised tsvwg Honolulu agenda posted
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 08 Nov 2014 19:25:29 -0000

https://datatracker.ietf.org/meeting/91/agenda/tsvwg/

Reminder - both TSVWG sessions are now on **Thursday** (hit reload in
the browser if you see an agenda that includes Tuesday - that's
now a taps WG meeting).

This agenda should be the final assignment of drafts to sessions,
but we have flexibility to make changes if needed.

Both sessions on Thursday are expected to run short, in part because
the Honolulu location seems to have discouraged a number of the usual
participants from attending.

Many thanks to the presenters who have already pro-actively sent me
their slides.  For the rest of them, including me ;-), I'd like
to have all the slides by mid-afternoon (Honolulu time) on Tuesday.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------



From nobody Sun Nov  9 08:49:58 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 377241A1B3E for <tsvwg@ietfa.amsl.com>; Sun,  9 Nov 2014 08:49:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RC_oobYdjXgm; Sun,  9 Nov 2014 08:49:54 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD361A1B31; Sun,  9 Nov 2014 08:49:54 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.2.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141109164954.24764.19262.idtracker@ietfa.amsl.com>
Date: Sun, 09 Nov 2014 08:49:54 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/50lM-RgGTO-M0JVeA545TiSuQ40
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-prpolicies-04.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Nov 2014 16:49:55 -0000

IESG state changed to AD Evaluation::Revised I-D Needed from Publication Requested
A revised I-D may not be needed - I sent questions to the shepherd that may result in a revised I-D, but this is the Substate that seemed to reflect that most clearly ...
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/


From nobody Sun Nov  9 23:44:06 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 099021A891E; Sun,  9 Nov 2014 23:44:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aaa2PZHTo-yu; Sun,  9 Nov 2014 23:44:01 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ED4AF1A8942; Sun,  9 Nov 2014 23:44:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.2.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141110074400.9660.49221.idtracker@ietfa.amsl.com>
Date: Sun, 09 Nov 2014 23:44:00 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/MlRZIlV4Ntp4J-Qxp-5lVqCk3uw
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Nov 2014 07:44:02 -0000

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           : Additional Policies for the Partial Reliability Extension of the Stream Control Transmission Protocol
        Authors         : Michael Tuexen
                          Robin Seggelmann
                          Randall R. Stewart
                          Salvatore Loreto
	Filename        : draft-ietf-tsvwg-sctp-prpolicies-05.txt
	Pages           : 10
	Date            : 2014-11-09

Abstract:
   This document defines two additional policies for the Partial
   Reliability Extension of the Stream Control Transmission Protocol
   (PR-SCTP) allowing to limit the number of retransmissions or to
   prioritize user messages for more efficient send buffer usage.


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

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

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


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/


From nobody Sun Nov  9 23:44:07 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC9B51A8945 for <tsvwg@ietfa.amsl.com>; Sun,  9 Nov 2014 23:44:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HNqF8yTSPwHQ; Sun,  9 Nov 2014 23:44:02 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 44C431A8947; Sun,  9 Nov 2014 23:44:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org, spencerdawkins.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.2.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141110074401.9660.13568.idtracker@ietfa.amsl.com>
Date: Sun, 09 Nov 2014 23:44:01 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/nSPeAaz3FF7TfJflzZAkgTDYDJc
Subject: [tsvwg] New Version Notification - draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Nov 2014 07:44:04 -0000

A new version (-05) has been submitted for draft-ietf-tsvwg-sctp-prpolicies:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctp-prpolicies-05.txt

Sub state has been changed to AD Followup from Revised ID Needed


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-prpolicies-05

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.

IETF Secretariat.


From nobody Mon Nov 10 10:03:38 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A26371A1B94 for <tsvwg@ietfa.amsl.com>; Mon, 10 Nov 2014 10:03:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0URVpmp2TGGl; Mon, 10 Nov 2014 10:03:33 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 12E511A1B70; Mon, 10 Nov 2014 10:03:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.2.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141110180333.14389.29790.idtracker@ietfa.amsl.com>
Date: Mon, 10 Nov 2014 10:03:33 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/F3no4RPMV4gZuH_I-YpoxHpq_1E
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-prpolicies-05.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Nov 2014 18:03:35 -0000

IESG state changed to Last Call Requested from AD Evaluation::AD Followup
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/


From nobody Mon Nov 10 11:10:44 2014
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BBE41AC3C6; Mon, 10 Nov 2014 11:10:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c438RGE1zlMz; Mon, 10 Nov 2014 11:10:35 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 782161AC3B6; Mon, 10 Nov 2014 11:10:18 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.2.p1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20141110191018.22796.76836.idtracker@ietfa.amsl.com>
Date: Mon, 10 Nov 2014 11:10:18 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/51Iq9IOBP7nX1xJ1Q2xIKZZAYyU
Cc: tsvwg@ietf.org
Subject: [tsvwg] Last Call: <draft-ietf-tsvwg-sctp-prpolicies-05.txt> (Additional Policies for the Partial Reliability Extension of the Stream Control Transmission Protocol) to Proposed Standard
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Nov 2014 19:10:41 -0000

The IESG has received a request from the Transport Area Working Group WG
(tsvwg) to consider the following document:
- 'Additional Policies for the Partial Reliability Extension of the
   Stream Control Transmission Protocol'
  <draft-ietf-tsvwg-sctp-prpolicies-05.txt> as Proposed Standard

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

Abstract


   This document defines two additional policies for the Partial
   Reliability Extension of the Stream Control Transmission Protocol
   (PR-SCTP) allowing to limit the number of retransmissions or to
   prioritize user messages for more efficient send buffer usage.




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

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


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



From nobody Mon Nov 10 11:11:00 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E6391AC3E6 for <tsvwg@ietfa.amsl.com>; Mon, 10 Nov 2014 11:10:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id edadiP_v4OHc; Mon, 10 Nov 2014 11:10:44 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 894731A914F; Mon, 10 Nov 2014 11:10:19 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.2.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141110191019.22796.15645.idtracker@ietfa.amsl.com>
Date: Mon, 10 Nov 2014 11:10:19 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/fMwIuwNUy1RIk9OsMN2xGMOvBbY
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-prpolicies-05.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Nov 2014 19:10:54 -0000

Last call has been made for draft-ietf-tsvwg-sctp-prpolicies and state has been changed to In Last Call
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/


From nobody Mon Nov 10 19:26:13 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 592751A8845 for <tsvwg@ietfa.amsl.com>; Mon, 10 Nov 2014 19:26:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0GH7HVe-8OQv for <tsvwg@ietfa.amsl.com>; Mon, 10 Nov 2014 19:26:05 -0800 (PST)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 868C91A887C for <tsvwg@ietf.org>; Mon, 10 Nov 2014 19:26:05 -0800 (PST)
Received: by mail-wi0-f176.google.com with SMTP id h11so351240wiw.9 for <tsvwg@ietf.org>; Mon, 10 Nov 2014 19:26:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ACTBSqOGtXhACGbxJZW0a1vRHhutWo595mD/RHi1G3I=; b=ZkbrcldIqC2ytHETFX23BpTqL+sUkXusspbnoOTeAMsf6clPq9hDAs09Bva1+0neo3 rOpNWlDpzlwVU6sZ38KuAXu+ah6xIbi33BVDOXsmTBB5E/zCQF2/MgtlDSQ+u1Q3/OE0 WgIuKJAPU/raaR/UOqiKX6/BBbywStKNbjBWSYXnGajR2uVL/0RW+AT0r7f9K1Th/dly kkz48PSsHDJB8azd+spqPKCsPH3gety3hH/XcCULY2dPv7RStkXw+6xHiGn5cqb/bqEH 5BtMODbL8v1XQj33zTHEpiCPwLoXZzWtzeaJ8a0WnaglMaF6hrUeAYyoG0lWi4pk/4l4 2a6g==
X-Received: by 10.180.91.70 with SMTP id cc6mr37633708wib.5.1415676364291; Mon, 10 Nov 2014 19:26:04 -0800 (PST)
Received: from [31.133.163.84] (dhcp-a354.meeting.ietf.org. [31.133.163.84]) by mx.google.com with ESMTPSA id dm10sm8008907wib.18.2014.11.10.19.26.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Nov 2014 19:26:03 -0800 (PST)
Message-ID: <546181CC.3000106@gmail.com>
Date: Tue, 11 Nov 2014 16:26:04 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-xia-nvo3-vxlan-qosmarking@drafts.ietf.org
References: <20141110200919.27869.2915.idtracker@ietfa.amsl.com>
In-Reply-To: <20141110200919.27869.2915.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/gp25oNg_SYBcBd-Ab6CoHdXPYzc
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Nov 2014 03:26:10 -0000

Hi,

>  The first three bits (bits 5-7) are precedence bits. They are	
>  assigned according to [RFC0791]. Precedence values '110' and '111'	
>  are selected for routing traffic.	
> 				
>  The last three bits (bits 8-10) are class selector bits. Thet are	
>  assigned as follows:
>
> 001 - BK or background traffic
...
> As can be seen the markings are the same as in IEEE 802.1p...

This is not in any way compatible with RFC 2474, which also made the
relevant part of RFC 791 obsolete.

If you want to be compatible with RFC 2474 you should not specify the
bits at all - just say that they are exactly as defined in RFC 2474
and the various PHB definitions that have been published. If you
want to be compatible with IEEE 802.1p that is a different matter,
but you cannot mix the two up in this way.

    Brian
 			


From nobody Mon Nov 10 19:37:24 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B33B81AD50F; Mon, 10 Nov 2014 19:37:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.895
X-Spam-Level: 
X-Spam-Status: No, score=-4.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BKaHLo6LMg9q; Mon, 10 Nov 2014 19:37:18 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5659A1AD50D; Mon, 10 Nov 2014 19:37:17 -0800 (PST)
Received: from maildlpprd54.lss.emc.com (maildlpprd54.lss.emc.com [10.106.48.158]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sAB3bEbm028838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Nov 2014 22:37:15 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com sAB3bEbm028838
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1415677035; bh=J6vMKwKpjFRZrI6UJw2ELKwl6xU=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:Content-Type: Content-Transfer-Encoding:MIME-Version; b=stYIVEG5K3cfb8rIe3RNIkLtlEjuvJSovGfqD+S4cJ+Pmjc7EMI7H8lz3ZmqbGWMZ qXfI6jBSToimz4OmdUls6GRE91vzXG480aq2cfbrt6X+VLp5QnzRp4Imhqznm7YZXi CMHm2uUP2qTBLa/AfBT34jMtjOSgoppqNmr77BVE=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com sAB3bEbm028838
Received: from mailusrhubprd03.lss.emc.com (mailusrhubprd03.lss.emc.com [10.253.24.21]) by maildlpprd54.lss.emc.com (RSA Interceptor); Mon, 10 Nov 2014 22:36:47 -0500
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailusrhubprd03.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sAB3av3O001870 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 10 Nov 2014 22:36:57 -0500
Received: from MXHUB102.corp.emc.com (10.253.58.15) by mxhub05.corp.emc.com (128.222.70.202) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 10 Nov 2014 22:36:57 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB102.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Mon, 10 Nov 2014 22:36:57 -0500
From: "Black, David" <david.black@emc.com>
To: "'brian.e.carpenter@gmail.com'" <brian.e.carpenter@gmail.com>, "'draft-xia-nvo3-vxlan-qosmarking@drafts.ietf.org'" <draft-xia-nvo3-vxlan-qosmarking@drafts.ietf.org>
Thread-Topic: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-01.txt
Thread-Index: AQHP/SJZ+SJcDuWsBkib/E7le/ydA5xbF/8A//+vOII=
Date: Tue, 11 Nov 2014 03:36:56 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493624824C@MX104CL02.corp.emc.com>
In-Reply-To: <546181CC.3000106@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.254.141.184]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd03.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/P-zuI6Y1aTa5CTcdCCxvnJHUeUY
Cc: "'nvo3@ietf.org'" <nvo3@ietf.org>, "'tsvwg@ietf.org'" <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Nov 2014 03:37:20 -0000

I said effectively the same thing at the mike in the nvo3 meeting - this dr=
aft is not using diffserv - it's inventing something new, and that's a bad =
idea.

Thanks, --David +++Sent from Blackberry

----- Original Message -----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
Sent: Monday, November 10, 2014 10:26 PM=0A=
To: draft-xia-nvo3-vxlan-qosmarking@drafts.ietf.org <draft-xia-nvo3-vxlan-q=
osmarking@drafts.ietf.org>
Cc: tsvwg@ietf.org <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-01.txt

Hi,

>  The first three bits (bits 5-7) are precedence bits. They are=09
>  assigned according to [RFC0791]. Precedence values '110' and '111'=09
>  are selected for routing traffic.=09
> 			=09
>  The last three bits (bits 8-10) are class selector bits. Thet are=09
>  assigned as follows:
>
> 001 - BK or background traffic
...
> As can be seen the markings are the same as in IEEE 802.1p...

This is not in any way compatible with RFC 2474, which also made the
relevant part of RFC 791 obsolete.

If you want to be compatible with RFC 2474 you should not specify the
bits at all - just say that they are exactly as defined in RFC 2474
and the various PHB definitions that have been published. If you
want to be compatible with IEEE 802.1p that is a different matter,
but you cannot mix the two up in this way.

    Brian
 		=09


From nobody Mon Nov 10 19:41:11 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F3621AD525 for <tsvwg@ietfa.amsl.com>; Mon, 10 Nov 2014 19:41:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2PXj4h1oYmw for <tsvwg@ietfa.amsl.com>; Mon, 10 Nov 2014 19:41:06 -0800 (PST)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DB2E1AD523 for <tsvwg@ietf.org>; Mon, 10 Nov 2014 19:41:06 -0800 (PST)
Received: by mail-wg0-f42.google.com with SMTP id k14so10475241wgh.15 for <tsvwg@ietf.org>; Mon, 10 Nov 2014 19:41:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4uBh5+fXnMfzSRL8MstV1el8adke8Zkv1hAvoANvVic=; b=gHBT4b6A+CLrBryWrHXh8Y/WY3lGD6AMCypRly47de1PE5W5orvsEBHNgChkjqAuIy zMtLrfis//0ZMWGNkVZa+ou1Mp1Gwo3GDeUma8gKK7YXA3rVGMnWVbFx5nfWdKAinpP3 M47hSgpRrUYGHEJV8urDjdqdF43jx4r+4vjHLP6KXiQuhjv7Yzd/mHq3FaEYfJea0Otx 3S75CjXZGvlEGp61yKQYvtVGvXnWCrg+yJKzxG3XOAI9ZJidqpPXTNeTenf/DS29TmTW pz/Wec7kCRr3KqoVfjt0a4vrq0bZY0NdesxnhvE+Z9KXmn4Vf5UbJD0vR/B9VX1xJl1t iVMg==
X-Received: by 10.194.52.68 with SMTP id r4mr50252760wjo.82.1415677264655; Mon, 10 Nov 2014 19:41:04 -0800 (PST)
Received: from [31.133.163.84] (dhcp-a354.meeting.ietf.org. [31.133.163.84]) by mx.google.com with ESMTPSA id f9sm25510799wjw.31.2014.11.10.19.41.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Nov 2014 19:41:04 -0800 (PST)
Message-ID: <5461854F.3020305@gmail.com>
Date: Tue, 11 Nov 2014 16:41:03 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org
References: <20141110200919.27869.2915.idtracker@ietfa.amsl.com>
In-Reply-To: <20141110200919.27869.2915.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/sQ7M3c8-WwEg25sIfnYxx0TjZ2E
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Nov 2014 03:41:08 -0000

[resend with corrected address, sorry]

Hi,

>  The first three bits (bits 5-7) are precedence bits. They are	
>  assigned according to [RFC0791]. Precedence values '110' and '111'	
>  are selected for routing traffic.	
> 				
>  The last three bits (bits 8-10) are class selector bits. Thet are	
>  assigned as follows:
>
> 001 - BK or background traffic
...
> As can be seen the markings are the same as in IEEE 802.1p...

This is not in any way compatible with RFC 2474, which also made the
relevant part of RFC 791 obsolete.

If you want to be compatible with RFC 2474 you should not specify the
bits at all - just say that they are exactly as defined in RFC 2474
and the various PHB definitions that have been published. If you
want to be compatible with IEEE 802.1p that is a different matter,
but you cannot mix the two up in this way.

    Brian
 			



From nobody Tue Nov 11 14:05:28 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 245EC1A1B32; Tue, 11 Nov 2014 14:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Og8MyzbtO0Up; Tue, 11 Nov 2014 14:05:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD441A1B19; Tue, 11 Nov 2014 14:05:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.2.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141111220521.8284.34491.idtracker@ietfa.amsl.com>
Date: Tue, 11 Nov 2014 14:05:21 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/CysH9bK6eep5qTKSRyZLjHP91-k
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-dtls-encaps-06.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Nov 2014 22:05:23 -0000

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           : DTLS Encapsulation of SCTP Packets
        Authors         : Michael Tuexen
                          Randall R. Stewart
                          Randell Jesup
                          Salvatore Loreto
	Filename        : draft-ietf-tsvwg-sctp-dtls-encaps-06.txt
	Pages           : 8
	Date            : 2014-11-11

Abstract:
   The Stream Control Transmission Protocol (SCTP) is a transport
   protocol originally defined to run on top of the network protocols
   IPv4 or IPv6.  This document specifies how SCTP can be used on top of
   the Datagram Transport Layer Security (DTLS) protocol.  Using the
   encapsulation method described in this document, SCTP is agnostic
   about the protocols being used below DTLS, explicit IP addresses can
   not be used in the SCTP control chunks.  As a consequence, the SCTP
   associations are single homed.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-dtls-encaps-06


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/


From nobody Tue Nov 11 14:49:21 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 935201A1BB4 for <tsvwg@ietfa.amsl.com>; Tue, 11 Nov 2014 14:49:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.895
X-Spam-Level: 
X-Spam-Status: No, score=-4.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r-5Pgsug4UyO for <tsvwg@ietfa.amsl.com>; Tue, 11 Nov 2014 14:49:17 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02B341A1B38 for <tsvwg@ietf.org>; Tue, 11 Nov 2014 14:49:16 -0800 (PST)
Received: from maildlpprd56.lss.emc.com (maildlpprd56.lss.emc.com [10.106.48.160]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sABMnFeX025417 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Tue, 11 Nov 2014 17:49:15 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com sABMnFeX025417
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1415746155; bh=szmtdlPkQ9dMBs3jF3w5wYHgg/U=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=diWk1CPoWmFFU5XV9HAu1+ajkb5Lj9Ij7Zu3EjR0U015Cc35GsuPwp5jKulizVbnw ct2H8tMynUnSDRztD09h+IXJ1PhrIatxpR90m/HdnfXKbT95XygzMrzBiTlrSpX2cg B/2EY22ckq5WzeS/9UwM5PjeMB0pqYdC1xe70gyg=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com sABMnFeX025417
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd56.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Tue, 11 Nov 2014 17:48:57 -0500
Received: from mxhub34.corp.emc.com (mxhub34.corp.emc.com [10.254.93.82]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sABMn2nP024910 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Tue, 11 Nov 2014 17:49:02 -0500
Received: from MXHUB102.corp.emc.com (10.253.58.15) by mxhub34.corp.emc.com (10.254.93.82) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 11 Nov 2014 17:49:02 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB102.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Tue, 11 Nov 2014 17:49:02 -0500
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: I-D Action: draft-ietf-tsvwg-sctp-dtls-encaps-06.txt
Thread-Index: AQHP/fukkxJS35GePEq2xb7nulu+DJxcBcaQ
Date: Tue, 11 Nov 2014 22:49:00 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936249187@MX104CL02.corp.emc.com>
References: <20141111220521.8284.34491.idtracker@ietfa.amsl.com>
In-Reply-To: <20141111220521.8284.34491.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.13.53.176]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/igSNglHk9MZj-aZ9WDpSktKmla0
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-dtls-encaps-06.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Nov 2014 22:49:19 -0000

The -06 version of this draft resolves the DTLS version issue that was
holding up this draft - out here in Honolulu, I've been busy "encouraging"
the WebRTC folks to make a decision, and a decision has now been made ;-).

The short summary is that DTLS 1.0 is "MUST implement" and the latest
version of DTLS (currently 1.2) is "SHOULD implement."

This version of the draft should be ready for submission to the IESG.

Thanks,
--David

> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Tuesday, November 11, 2014 5:05 PM
> To: i-d-announce@ietf.org
> Cc: tsvwg@ietf.org
> Subject: I-D Action: draft-ietf-tsvwg-sctp-dtls-encaps-06.txt
>=20
>=20
> 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 Gr=
oup
> of the IETF.
>=20
>         Title           : DTLS Encapsulation of SCTP Packets
>         Authors         : Michael Tuexen
>                           Randall R. Stewart
>                           Randell Jesup
>                           Salvatore Loreto
> 	Filename        : draft-ietf-tsvwg-sctp-dtls-encaps-06.txt
> 	Pages           : 8
> 	Date            : 2014-11-11
>=20
> Abstract:
>    The Stream Control Transmission Protocol (SCTP) is a transport
>    protocol originally defined to run on top of the network protocols
>    IPv4 or IPv6.  This document specifies how SCTP can be used on top of
>    the Datagram Transport Layer Security (DTLS) protocol.  Using the
>    encapsulation method described in this document, SCTP is agnostic
>    about the protocols being used below DTLS, explicit IP addresses can
>    not be used in the SCTP control chunks.  As a consequence, the SCTP
>    associations are single homed.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-06
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-dtls-encaps-06
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> 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 nobody Tue Nov 11 19:54:27 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6A01AC41A; Tue, 11 Nov 2014 19:54:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NqrBlfTWiTyE; Tue, 11 Nov 2014 19:54:23 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0197C1A8872; Tue, 11 Nov 2014 19:54:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.2.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141112035423.24455.10110.idtracker@ietfa.amsl.com>
Date: Tue, 11 Nov 2014 19:54:23 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/vuoFseVR18NXzYGxtfP10ppeFkg
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-port-use-06.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Nov 2014 03:54:24 -0000

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           : Recommendations for Transport Port Number Uses
        Author          : Joe Touch
	Filename        : draft-ietf-tsvwg-port-use-06.txt
	Pages           : 21
	Date            : 2014-11-11

Abstract:
   This document provides recommendations to application and service
   designers on how to use the transport protocol port number space. IT
   complements (but does not update) RFC6335, which focuses on IANA
   process.


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

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

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


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/


From nobody Tue Nov 11 21:41:30 2014
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 451F71A6F8B for <tsvwg@ietfa.amsl.com>; Tue, 11 Nov 2014 21:41:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.794
X-Spam-Level: 
X-Spam-Status: No, score=-4.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03CYrPmkCnA4 for <tsvwg@ietfa.amsl.com>; Tue, 11 Nov 2014 21:41:26 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF66E1A6F28 for <tsvwg@ietf.org>; Tue, 11 Nov 2014 21:41:26 -0800 (PST)
Received: from [192.168.1.9] (pool-71-103-148-202.lsanca.dsl-w.verizon.net [71.103.148.202]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id sAC5emef012909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 11 Nov 2014 21:40:58 -0800 (PST)
Message-ID: <5462F2E3.3090700@isi.edu>
Date: Tue, 11 Nov 2014 21:40:51 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>
References: <20141112035423.24455.95502.idtracker@ietfa.amsl.com>
In-Reply-To: <20141112035423.24455.95502.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20141112035423.24455.95502.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/_uAf-jlzNikgTB6Z6ePJzP3RTK0
Subject: [tsvwg] Fwd: New Version Notification for draft-ietf-tsvwg-port-use-06.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Nov 2014 05:41:28 -0000

Hi, all,

This version incorporates final input from WGLC:

- corrections to some obsoleted references

- addition of intra-machine use case

Joe

-------- Original Message --------
Subject: New Version Notification for draft-ietf-tsvwg-port-use-06.txt
Date: Tue, 11 Nov 2014 19:54:23 -0800
From: internet-drafts@ietf.org
To: Dr. Joseph D. Touch <touch@isi.edu>, Joe Touch <touch@isi.edu>


A new version of I-D, draft-ietf-tsvwg-port-use-06.txt
has been successfully submitted by Joe Touch and posted to the
IETF repository.

Name:		draft-ietf-tsvwg-port-use
Revision:	06
Title:		Recommendations for Transport Port Number Uses
Document date:	2014-11-11
Group:		tsvwg
Pages:		21
URL:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-port-use-06.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/
Htmlized:       http://tools.ietf.org/html/draft-ietf-tsvwg-port-use-06
Diff:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-port-use-06

Abstract:
   This document provides recommendations to application and service
   designers on how to use the transport protocol port number space. IT
   complements (but does not update) RFC6335, which focuses on IANA
   process.





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



From nobody Wed Nov 12 02:55:08 2014
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACB081A6F42 for <tsvwg@ietfa.amsl.com>; Wed, 12 Nov 2014 02:55:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.444
X-Spam-Level: 
X-Spam-Status: No, score=-4.444 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7_ehq_y1owb0 for <tsvwg@ietfa.amsl.com>; Wed, 12 Nov 2014 02:55:05 -0800 (PST)
Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADCB41A6F0A for <tsvwg@ietf.org>; Wed, 12 Nov 2014 02:55:03 -0800 (PST)
Received: from q4de8psa169.blf.telekom.de ([10.151.13.200]) by tcmail41.telekom.de with ESMTP; 12 Nov 2014 11:54:57 +0100
X-IronPort-AV: E=Sophos;i="5.07,368,1413237600"; d="scan'208";a="699704746"
Received: from he113472.emea1.cds.t-internal.com ([10.134.93.130]) by q4de8psazkj.blf.telekom.de with ESMTP/TLS/AES128-SHA; 12 Nov 2014 11:54:49 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113472.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 12 Nov 2014 11:54:49 +0100
From: <Ruediger.Geib@telekom.de>
To: <gorry@erg.abdn.ac.uk>
Date: Wed, 12 Nov 2014 11:54:48 +0100
Thread-Topic: New Version Notification for draft-geib-tsvwg-diffserv-intercon-08.txt
Thread-Index: Ac/+Zbu6fotj3ILISwCNqFli8HckZQAAI2lg
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5033EDAA334@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Q3EF-UcNMvQpJDCnpLBc3I_LKks
Cc: jmpolk@cisco.com, tsvwg@ietf.org
Subject: [tsvwg] WG: New Version Notification for draft-geib-tsvwg-diffserv-intercon-08.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Nov 2014 10:55:07 -0000

SGkgR29ycnksDQoNCmFzIGRyYWZ0IC0wNyByZWZlcnMgdG8gdHdvIGFubmV4ZXMsIGJ1dCBkb2Vz
bid0IGNvbnRhaW4gdGhlbSwgSSd2ZSByZS1zdWJtaXR0ZWQgdmVyc2lvbiAtMDggb2YgRGlmZnNl
cnYgSW50ZXJjb24uDQoNClRoZSBjb3JlIHRleHQgb2YgdGhlIGRyYWZ0IGhhcyBub3QgYmVlbiBj
aGFuZ2VkLiBUaGUgYW5uZXhlcyBhcmUgaW50ZW5kZWQgdG8gZXhwbGFpbiBzb21lIG9mIHRoZSBp
c3N1ZXMgd2hpY2ggbGVkIHRvIHRoaXMgZHJhZnQuIElmIHRoZXkgYXJlIGZlbHQgdG8gYmUgY29u
dHJvdmVyc2lhbCwgbm90IG5lY2Vzc2FyeSBvciBjcmVhdGUgYSBzaWduaWZpY2FudCBhbW91bnQg
b2YgcXVlc3Rpb25zLCBJJ2QgcmF0aGVyIGxpa2UgdG8gcmVtb3ZlIHRoZW0uDQoNCkknbGwgY29u
dGFjdCBzb21lIGNhcnJpZXIgcmVwcmVzZW50YXRpdmVzIGFuZCBhc2sgdGhlbSBmb3IgY29tbWVu
dHMgd2l0aCB2ZXJzaW9uIC0wOC4NCg0KUmVnYXJkcywNCg0KUnVlZGlnZXINCg0KIA0KDQotLS0t
LVVyc3Byw7xuZ2xpY2hlIE5hY2hyaWNodC0tLS0tDQpWb246IGludGVybmV0LWRyYWZ0c0BpZXRm
Lm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10gDQpHZXNlbmRldDogTWl0dHdv
Y2gsIDEyLiBOb3ZlbWJlciAyMDE0IDExOjQ0DQpBbjogR2VpYiwgUsO8ZGlnZXI7IERhdmlkIEwu
IEJsYWNrOyBEYXZpZCBMLkJsYWNrOyBHZWliLCBSw7xkaWdlcg0KQmV0cmVmZjogTmV3IFZlcnNp
b24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1nZWliLXRzdndnLWRpZmZzZXJ2LWludGVyY29uLTA4
LnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1nZWliLXRzdndnLWRpZmZzZXJ2
LWludGVyY29uLTA4LnR4dA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBSdWVk
aWdlciBHZWliIGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KTmFtZToJCWRy
YWZ0LWdlaWItdHN2d2ctZGlmZnNlcnYtaW50ZXJjb24NClJldmlzaW9uOgkwOA0KVGl0bGU6CQlE
aWZmU2VydiBpbnRlcmNvbm5lY3Rpb24gY2xhc3NlcyBhbmQgcHJhY3RpY2UNCkRvY3VtZW50IGRh
dGU6CTIwMTQtMTEtMTINCkdyb3VwOgkJSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQpQYWdlczoJCTIy
DQpVUkw6ICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh
ZnQtZ2VpYi10c3Z3Zy1kaWZmc2Vydi1pbnRlcmNvbi0wOC50eHQNClN0YXR1czogICAgICAgICBo
dHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1nZWliLXRzdndnLWRpZmZzZXJ2
LWludGVyY29uLw0KSHRtbGl6ZWQ6ICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWdlaWItdHN2d2ctZGlmZnNlcnYtaW50ZXJjb24tMDgNCkRpZmY6ICAgICAgICAgICBodHRw
Oi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1nZWliLXRzdndnLWRpZmZzZXJ2LWlu
dGVyY29uLTA4DQoNCkFic3RyYWN0Og0KICAgVGhpcyBkb2N1bWVudCBwcm9wb3NlcyBhIGxpbWl0
ZWQgYW5kIHdlbGwgZGVmaW5lZCBzZXQgb2YgRGlmZlNlcnYNCiAgIFBIQnMgYW5kIGNvZGVwb2lu
dHMgdG8gYmUgYXBwbGllZCBhdCAoaW50ZXIpY29ubmVjdGlvbnMgb2YgdHdvDQogICBzZXBhcmF0
ZWx5IGFkbWluaXN0ZXJlZCBhbmQgb3BlcmF0ZWQgbmV0d29ya3MuICBNYW55IG5ldHdvcmsNCiAg
IHByb3ZpZGVycyBvcGVyYXRlIE1QTFMgdXNpbmcgVHJlYXRtZW50IEFnZ3JlZ2F0ZXMgZm9yIHRy
YWZmaWMgbWFya2VkDQogICB3aXRoIGRpZmZlcmVudCBEaWZmU2VydiBQSEJzLCBhbmQgdXNlIE1Q
TFMgZm9yIGludGVyY29ubmVjdGlvbiB3aXRoDQogICBvdGhlciBuZXR3b3Jrcy4gIFRoaXMgZG9j
dW1lbnQgb2ZmZXJzIGEgc2ltcGxlIGludGVyY29ubmVjdGlvbg0KICAgYXBwcm9hY2ggdGhhdCBt
YXkgc2ltcGxpZnkgb3BlcmF0aW9uIG9mIERpZmZTZXJ2IGZvciBuZXR3b3JrDQogICBpbnRlcmNv
bm5lY3Rpb24gYW1vbmcgcHJvdmlkZXJzLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoN
Cg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20g
dGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlm
ZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KDQpUaGUgSUVURiBTZWNyZXRhcmlh
dA0KDQo=


From nobody Wed Nov 12 14:30:12 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90D1A1A0007 for <tsvwg@ietfa.amsl.com>; Wed, 12 Nov 2014 14:30:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.895
X-Spam-Level: 
X-Spam-Status: No, score=-4.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UYayrU3rfuzf for <tsvwg@ietfa.amsl.com>; Wed, 12 Nov 2014 14:30:09 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08C191A0006 for <tsvwg@ietf.org>; Wed, 12 Nov 2014 14:30:08 -0800 (PST)
Received: from maildlpprd52.lss.emc.com (maildlpprd52.lss.emc.com [10.106.48.156]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sACMU7Bc010582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 12 Nov 2014 17:30:07 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com sACMU7Bc010582
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1415831407; bh=2XaaXsXMZ/f/gI46ZTVY2x9O1Gk=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=eSljKPAiheLXpma5dIVP+JvUV7oCeJeLlFfdHBfU/VPDcwEN95fJputKG8Pzvcwr3 2bw6NynyeZmReN23lg5GK+2FZoi8lPqJsK2ql3eX/htFDMpXYJL2M+e1A4oP63zK10 YU/XlwL9y+D5ZPx1oDSHOTSmi4z5ksB8tx9Fl5vw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com sACMU7Bc010582
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd52.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Wed, 12 Nov 2014 17:29:57 -0500
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sACMTvfx011244 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Wed, 12 Nov 2014 17:29:57 -0500
Received: from MXHUB103.corp.emc.com (10.253.50.16) by mxhub20.corp.emc.com (10.254.93.49) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 12 Nov 2014 17:29:56 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB103.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Wed, 12 Nov 2014 17:29:56 -0500
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Honolulu Agenda updated
Thread-Index: Ac/+yC82WQnJwawOS56/AnkVscehyw==
Date: Wed, 12 Nov 2014 22:29:56 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493624AC9D@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.13.62.5]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/nsHU8WBg8eQqTL7F-YuRmMfW8TQ
Subject: [tsvwg] Honolulu Agenda updated
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Nov 2014 22:30:10 -0000

I've uploaded a slightly revised agenda, plus all of the
presentations that I've received to date (please note that
the GRE in UDP presentation was replaced w/a completely=20
new one).

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From nobody Thu Nov 13 08:03:53 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13BB61A8A47; Thu, 13 Nov 2014 08:03:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dLIS16b9hqbl; Thu, 13 Nov 2014 08:03:44 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 38C701A8A25; Thu, 13 Nov 2014 08:03:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141113160342.8955.69151.idtracker@ietfa.amsl.com>
Date: Thu, 13 Nov 2014 08:03:42 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/koaiP2xRd-3s4reKu6dhlHi4WW0
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rtcweb-qos-03.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 13 Nov 2014 16:03:48 -0000

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           : DSCP and other packet markings for RTCWeb QoS
        Authors         : Subha Dhesikan
                          Cullen Jennings
                          Dan Druta
                          Paul E. Jones
                          James Polk
	Filename        : draft-ietf-tsvwg-rtcweb-qos-03.txt
	Pages           : 8
	Date            : 2014-11-13

Abstract:
   Many networks, such as service provider and enterprise networks, can
   provide treatment for individual packets based on Differentiated
   Services Code Points (DSCP) on a per-hop basis.  This document
   provides the recommended DSCP values for browsers to use for various
   classes of traffic.


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

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

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


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/


From nobody Fri Nov 14 11:06:29 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F78B1A8A50 for <tsvwg@ietfa.amsl.com>; Fri, 14 Nov 2014 11:06:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fY7_k7KLd8hi; Fri, 14 Nov 2014 11:06:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8546F1A0059; Fri, 14 Nov 2014 11:06:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141114190625.6101.12798.idtracker@ietfa.amsl.com>
Date: Fri, 14 Nov 2014 11:06:25 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/r8JX8YPEK_rDPCoCw5cQ1E8MEyA
Subject: [tsvwg] ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-prpolicies-05.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 14 Nov 2014 19:06:27 -0000

IANA review state changed to IANA OK - No Actions Needed
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/


From nobody Fri Nov 14 19:48:32 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2264F1A1AAE; Fri, 14 Nov 2014 19:48:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.895
X-Spam-Level: 
X-Spam-Status: No, score=-4.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eBHML8xjhB1w; Fri, 14 Nov 2014 19:48:18 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA30D1A1AA6; Fri, 14 Nov 2014 19:48:17 -0800 (PST)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sAF3mF0J003382 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Nov 2014 22:48:16 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com sAF3mF0J003382
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1416023296; bh=wv8dzxreARABjg5Q3GLm9pf15so=; h=From:To:CC:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=nEcM8ebHG5TIa8y17cEs9RwtXAw3W9iv83WuVh9VY023xYQPvSeyWRAIKsVDvpTXL Sdf+pu/h3wPN+Y2ROMSYgoIq6EddsivOVRZ4upta5C2hTKOaEy1d5MCJLorykGyLho viB0VolC/1lM/TU8a7BvtpgnBJv0wfKMTse4xXoY=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com sAF3mF0J003382
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd04.lss.emc.com (RSA Interceptor); Fri, 14 Nov 2014 22:47:46 -0500
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sAF3m5nI013731 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 14 Nov 2014 22:48:06 -0500
Received: from MXHUB105.corp.emc.com (10.253.50.22) by mxhub13.corp.emc.com (128.222.70.234) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 14 Nov 2014 22:48:05 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.125]) by MXHUB105.corp.emc.com ([10.253.50.22]) with mapi id 14.03.0195.001; Fri, 14 Nov 2014 22:48:05 -0500
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Draft Honolulu minutes posted
Thread-Index: AdAAhvKsgvidKflzSn6eZ5hy7E5pUQ==
Date: Sat, 15 Nov 2014 03:48:04 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493626C5E8@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.13.53.238]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/9vrA3iWPa3ubbhfuGEdK5_DGTVg
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: [tsvwg] Draft Honolulu minutes posted
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 15 Nov 2014 03:48:20 -0000

... before I get on the plane out of here!

http://www.ietf.org/proceedings/91/minutes/minutes-91-tsvwg

Many thanks to Aaron Falk and Joel Halpern for taking notes, as
there were lively discussions in both sessions that were not easy
to follow.  They captured everything important.

Here are some important items that people should know about:

1) There are a number of expired WG drafts that need author attention:
	ECN Encapsulation Guidelines
	NAT Behavioral Requirements Updates
	RSVP Multiple Instance Object
	SCTP NAT Support

2) The sense of the room in Honolulu was to adopt the following two
	drafts as WG drafts:

      DiffServ interconnection classes and practice
	draft-geib-tsvwg-diffserv-intercon
http://datatracker.ietf.org/doc/draft-geib-tsvwg-diffserv-intercon/

      UDP Usage Guidelines
      draft-eggert-tsvwg-rfc5405bis
http://datatracker.ietf.org/doc/draft-eggert-tsvwg-rfc5405bis/

      Absent objection on the list, these drafts will be adopted.
      Please comment by November 30.

3) The meeting determined that there is no WG rough consensus
      for requiring use of the full UDP checksum for GRE-in-UDP
      with IPv6.  The design team will continue work on when
      zero checksum is acceptable (as well as congestion
      considerations).

4) See the minutes for the lengthy and interesting discussion of the
      tunnel congestion feedback draft.  There is one important issue
	that needs to be followed up across the TSVWG and AQM WGs (aqm
      list cc:'d for this reason):

      OPEN ISSUE *1: Should ECN indications (CE) be treated as equivalent
      to drops?  This also came  up in AQM.  This is primarily about
      endpoint (or tunnel egress) reaction to CE.

Enjoy,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------



From nobody Sun Nov 16 12:42:29 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E575C1A1AFC; Sun, 16 Nov 2014 12:42:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NGi3-DE0M29a; Sun, 16 Nov 2014 12:42:04 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0811A1A03; Sun, 16 Nov 2014 12:42:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141116204204.10253.97081.idtracker@ietfa.amsl.com>
Date: Sun, 16 Nov 2014 12:42:04 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/z7PzncgTZVqkFp94th2MTp1ha8s
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-ecn-encap-guidelines-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 16 Nov 2014 20:42:06 -0000

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           : Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
        Authors         : Bob Briscoe
                          John Kaippallimalil
                          Pat Thaler
	Filename        : draft-ietf-tsvwg-ecn-encap-guidelines-01.txt
	Pages           : 30
	Date            : 2014-11-16

Abstract:
   The purpose of this document is to guide the design of congestion
   notification in any lower layer or tunnelling protocol that
   encapsulates IP.  The aim is for explicit congestion signals to
   propagate consistently from lower layer protocols into IP.  Then the
   IP internetwork layer can act as a portability layer to carry
   congestion notification from non-IP-aware congested nodes up to the
   transport layer (L4).  Following these guidelines should assure
   interworking between new lower layer congestion notification
   mechanisms, whether specified by the IETF or other standards bodies.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-ecn-encap-guidelines-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/


From nobody Mon Nov 17 02:53:50 2014
Return-Path: <iana-shared@icann.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBEE81A88F5; Fri, 14 Nov 2014 10:50:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.774
X-Spam-Level: 
X-Spam-Status: No, score=-3.774 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DghR9Rw1uEp6; Fri, 14 Nov 2014 10:50:54 -0800 (PST)
Received: from smtp1.lax.icann.org (smtp01.icann.org [192.0.33.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 265E41A88EB; Fri, 14 Nov 2014 10:50:54 -0800 (PST)
Received: from request1.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp1.lax.icann.org (8.13.8/8.13.8) with ESMTP id sAEIorA1024568;  Fri, 14 Nov 2014 18:50:53 GMT
Received: by request1.lax.icann.org (Postfix, from userid 48) id CCE3856080B; Fri, 14 Nov 2014 18:50:53 +0000 (UTC)
RT-Owner: pearl.liang
From: "Pearl Liang via RT" <drafts-lastcall@iana.org>
In-Reply-To: <20141110191018.22796.67139.idtracker@ietfa.amsl.com>
References: <RT-Ticket-792302@icann.org> <20141110191018.22796.67139.idtracker@ietfa.amsl.com>
Message-ID: <rt-4.0.8-7913-1415991053-611.792302-7-0@icann.org>
Precedence: bulk
X-RT-Loop-Prevention: IANA
RT-Ticket: IANA #792302
Managed-BY: RT 4.0.8 (http://www.bestpractical.com/rt/)
RT-Originator: pearl.liang@icann.org
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Date: Fri, 14 Nov 2014 18:50:53 +0000
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/NnWANZcyZDBNsC4LTS29Iu-iZ54
X-Mailman-Approved-At: Mon, 17 Nov 2014 02:53:49 -0800
Cc: tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
Subject: [tsvwg] [IANA #792302] Last Call: <draft-ietf-tsvwg-sctp-prpolicies-05.txt> (Additional Policies for the Partial Reliability Extension of the Stream Control Transmission Protocol) to Proposed Standard
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: drafts-lastcall@iana.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: Fri, 14 Nov 2014 18:50:55 -0000

(BEGIN IANA LAST CALL COMMENTS)

IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-tsvwg-sctp-prpolicies-05, which is currently in Last Call, and has the following comments:

We understand that, upon approval of this document, there are no IANA Actions that need completion.

While it is helpful for the IANA Considerations section of the document to remain in place upon publication, if the authors prefer to remove it, IANA doesn't object.

If this assessment is not accurate, please respond as soon as possible.

Thanks,

Pearl Liang
ICANN

(END IANA LAST CALL COMMENTS)


On Mon Nov 10 19:11:05 2014, iesg-secretary@ietf.org wrote:
> 
> The IESG has received a request from the Transport Area Working Group WG
> (tsvwg) to consider the following document:
> - 'Additional Policies for the Partial Reliability Extension of the
>    Stream Control Transmission Protocol'
>   <draft-ietf-tsvwg-sctp-prpolicies-05.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2014-12-1. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document defines two additional policies for the Partial
>    Reliability Extension of the Stream Control Transmission Protocol
>    (PR-SCTP) allowing to limit the number of retransmissions or to
>    prioritize user messages for more efficient send buffer usage.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 



From jun.dr.cheng@ericsson.com  Tue Nov 18 04:46:33 2014
Return-Path: <jun.dr.cheng@ericsson.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07C791A037B for <tsvwg@ietfa.amsl.com>; Tue, 18 Nov 2014 04:46:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-eDUPKGtqRE for <tsvwg@ietfa.amsl.com>; Tue, 18 Nov 2014 04:46:31 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86AE71A0377 for <tsvwg@ietf.org>; Tue, 18 Nov 2014 04:46:30 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-6a-546b3fa437c2
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 86.95.04076.4AF3B645; Tue, 18 Nov 2014 13:46:28 +0100 (CET)
Received: from ESESSMB203.ericsson.se ([169.254.3.75]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0174.001; Tue, 18 Nov 2014 13:46:27 +0100
From: Jun Cheng DR <jun.dr.cheng@ericsson.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: IETF WG state changed to In WG Last Call from WG Document [rev. 08]
Thread-Index: AdADGgrI7y2FTnhwQw6BhJeSZd5LIgAE2bkw
Date: Tue, 18 Nov 2014 12:46:27 +0000
Message-ID: <B91AB8217303A246B7C0455B8229639F2885E2FF@ESESSMB203.ericsson.se>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.19]
Content-Type: multipart/alternative; boundary="_000_B91AB8217303A246B7C0455B8229639F2885E2FFESESSMB203erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJLMWRmVeSWpSXmKPExsUyM+Jvje4S++wQg6sNQhaHWmeyWBx7c5fN gcljyZKfTB6HngcFMEVx2aSk5mSWpRbp2yVwZdxYup6x4JBsxcK9z9gaGO9JdjFyckgImEg8 7d3KDGGLSVy4t56ti5GLQ0jgCKPEsUvXoZzFjBL3F3QBVXFwsAnoSXSczQRpEBFQlbjcsZYJ JMwskC7RvqoMJCwsECRxas89RpCwiECwxLwnlhDVRhI3lp1hBbFZgDrnb13LClLCK+Ar8bbP AiTMKCArcf/7PRYQm1lAXOLWk/lMEJcJSCzZcx7qSlGJl4//sULYihLtTxsYIerzJa733WMD sXkFBCVOznzCMoFReBaSUbOQlM1CUgYR15O4MXUKG4StLbFs4WtmCFtXYsa/QyzI4gsY2Vcx ihanFhfnphsZ6aUWZSYXF+fn6eWllmxiBMbNwS2/rXYwHnzueIhRgINRiYfXYFtWiBBrYllx Ze4hRmkOFiVx3oXn5gULCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYAzK3vFbyFTPRu6DU9gW 7tlLni7a+k/KyFjQ/spfhWVWb5bu4QvRXzQ1aU+fsqdrisCRK/ebCs/M43X2mtr/9sUmx5xn K/3F0q/rch28cN1yg6X/Yp6TJ5ca3uu+KlafuOn8uSbuw0v730SzFoccfaV+bvXU3pqzE34Y Xy6Mzt246oT2/f41s08qsRRnJBpqMRcVJwIAiT55q3wCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/-HQSIKXnR6m4rx3316SRCMMTGdo
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>
Subject: Re: [tsvwg] IETF WG state changed to In WG Last Call from WG Document [rev. 08]
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 18 Nov 2014 13:29:26 -0000

--_000_B91AB8217303A246B7C0455B8229639F2885E2FFESESSMB203erics_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi TSV Working Group,

I have read the WGLC version of the PF draft i.e. Quick Failover Algorithm =
in SCTP draft-ietf-tsvwg-sctp-failover-08,
and I support its progression to RFC.

The SCTP PF function is running successfully in various variants in the dep=
loyment of the signaling products to alleviate congestion at SCTP path fail=
ure. When this WGLC becomes RFC, we will fulfill the RFC in Ericsson's prod=
uct lines.

Many thanks  for the WG work on this draft!

Best regards

Jun
Jun Cheng, Ph.D.
Ericsson AB
DU Core Networks, PDU Evolved Infrastructure
Kistav=E4gen 25
164 80 Stockholm, Sweden

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi TSV Working Group,&nbsp; <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I have read the WGLC version of the PF draft i.e. Qu=
ick Failover Algorithm in SCTP draft-ietf-tsvwg-sctp-failover-08,
<o:p></o:p></p>
<p class=3D"MsoNormal">and I support its progression to RFC.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The SCTP PF function is running successfully in vari=
ous variants in the deployment of the signaling products to alleviate conge=
stion at SCTP path failure. When this WGLC becomes RFC, we will fulfill the=
 RFC in Ericsson&#8217;s product lines.&nbsp;&nbsp;
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Many thanks&nbsp; for the WG work on this draft!<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best regards<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Jun<o:p></o:p></p>
<p class=3D"MsoNormal">Jun Cheng, Ph.D. <o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson AB<o:p></o:p></p>
<p class=3D"MsoNormal">DU Core Networks, PDU Evolved Infrastructure <o:p></=
o:p></p>
<p class=3D"MsoNormal">Kistav=E4gen 25<o:p></o:p></p>
<p class=3D"MsoNormal">164 80 Stockholm, Sweden<o:p></o:p></p>
</div>
</body>
</html>

--_000_B91AB8217303A246B7C0455B8229639F2885E2FFESESSMB203erics_--


From nobody Tue Nov 18 06:17:46 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25A8C1A049A for <tsvwg@ietfa.amsl.com>; Tue, 18 Nov 2014 06:17:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.795
X-Spam-Level: 
X-Spam-Status: No, score=-4.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vcoIGLPnUlXH for <tsvwg@ietfa.amsl.com>; Tue, 18 Nov 2014 06:17:42 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 2340C1A066C for <tsvwg@ietf.org>; Tue, 18 Nov 2014 06:17:42 -0800 (PST)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 33) id 4361B2B4481; Tue, 18 Nov 2014 14:17:37 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by spey.erg.abdn.ac.uk with HTTP; Tue, 18 Nov 2014 14:17:37 -0000
Message-ID: <e4c19dd34a0b4e53c6ac6599de25feee.squirrel@spey.erg.abdn.ac.uk>
In-Reply-To: <B91AB8217303A246B7C0455B8229639F2885E2FF@ESESSMB203.ericsson.se>
References: <B91AB8217303A246B7C0455B8229639F2885E2FF@ESESSMB203.ericsson.se>
Date: Tue, 18 Nov 2014 14:17:37 -0000
From: gorry@erg.abdn.ac.uk
To: "Jun Cheng DR" <jun.dr.cheng@ericsson.com>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/qjkNc-gd7hJyZLjchf7Tnvhk2qQ
Cc: "Karen E. E. Nielsen" <karen.nielsen@tieto.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] IETF WG state changed to In WG Last Call from WG Document [rev. 08]
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 18 Nov 2014 14:17:44 -0000

Thanks,

It is really helpful to hear implementation feedback during a LC.

Best wishes,

Gorry

(TSVWG Co-Chair)


> Hi TSV Working Group,
>
> I have read the WGLC version of the PF draft i.e. Quick Failover Algorithm
> in SCTP draft-ietf-tsvwg-sctp-failover-08,
> and I support its progression to RFC.
>
> The SCTP PF function is running successfully in various variants in the
> deployment of the signaling products to alleviate congestion at SCTP path
> failure. When this WGLC becomes RFC, we will fulfill the RFC in Ericsson's
> product lines.
>
> Many thanks  for the WG work on this draft!
>
> Best regards
>
> Jun
> Jun Cheng, Ph.D.
> Ericsson AB
> DU Core Networks, PDU Evolved Infrastructure
> Kistavägen 25
> 164 80 Stockholm, Sweden
>


From nobody Tue Nov 18 10:37:41 2014
Return-Path: <jeff.morriss.ws@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E95A91A1AF0 for <tsvwg@ietfa.amsl.com>; Tue, 18 Nov 2014 10:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d5MvVBiwotpQ for <tsvwg@ietfa.amsl.com>; Tue, 18 Nov 2014 10:37:37 -0800 (PST)
Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com [IPv6:2607:f8b0:400d:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B92191A001E for <tsvwg@ietf.org>; Tue, 18 Nov 2014 10:37:36 -0800 (PST)
Received: by mail-qg0-f42.google.com with SMTP id i50so17730614qgf.15 for <tsvwg@ietf.org>; Tue, 18 Nov 2014 10:37:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=dqfsMRqg7Nu0ISUx8luH2uf4KSh/9gMSxaFfSCrLHbk=; b=CUEuUUAEb1nsJpEZv3l5Mf29q37TstvSJ5uAEUKPzJox69eaWFglf93Yg1cYgCW4FB FcniR621X8O5O06qBykSGKOUzwani44hGBI2ZUN47qkdqPYTnTM7stdfmXs5fwxITET0 j84DwtoyXdb3pm7MQVntKGoXPZILmVIx6TQAYGZo1oIVEzZkBT9iBbRQWO8/Hnh/1EIz r0oTfGf+ZGr8Il4unxZ4BR89m4Pqzko8q34wtDijZ0oFjYxmiW1IpECSZGVFv3GwW9tl 5R9MbfsHGGiAdO5SURRglIo++X7krkJrJ+zSIdwtl3kMw26UqzNl3rDPVLTZac778W4p 3MsA==
X-Received: by 10.224.40.202 with SMTP id l10mr21698120qae.7.1416335855955; Tue, 18 Nov 2014 10:37:35 -0800 (PST)
Received: from mtl-morriss-d1.ulticom.com (74-8-208-5.ulticom.com. [74.8.208.5]) by mx.google.com with ESMTPSA id e2sm20910206qac.34.2014.11.18.10.37.35 for <tsvwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Nov 2014 10:37:35 -0800 (PST)
Message-ID: <546B91EE.4000008@gmail.com>
Date: Tue, 18 Nov 2014 13:37:34 -0500
From: Jeff Morriss <jeff.morriss.ws@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <B91AB8217303A246B7C0455B8229639F2885E2FF@ESESSMB203.ericsson.se> <e4c19dd34a0b4e53c6ac6599de25feee.squirrel@spey.erg.abdn.ac.uk>
In-Reply-To: <e4c19dd34a0b4e53c6ac6599de25feee.squirrel@spey.erg.abdn.ac.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/CGBA5IAgICDkJSkLDOZIeHDTDNE
Subject: Re: [tsvwg] IETF WG state changed to In WG Last Call from WG Document [rev. 08]
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 18 Nov 2014 18:37:39 -0000

In that case I would remind the group of David's email indicating that 
Ulticom's SCTP has had a (simplified, compared to what is in the draft) 
version of fast path failover since ~2001:

http://www.ietf.org/mail-archive/web/tsvwg/current/msg10526.html

It was found long ago to be necessary, as stated below, to avoid 
congestion and delays during path failover.

I agree it is important for this draft to progress: there are 
environments where it is important to maintain throughput even during 
path failover.

On 11/18/14 09:17, gorry@erg.abdn.ac.uk wrote:
> Thanks,
>
> It is really helpful to hear implementation feedback during a LC.
>
> Best wishes,
>
> Gorry
>
> (TSVWG Co-Chair)
>
>
>> Hi TSV Working Group,
>>
>> I have read the WGLC version of the PF draft i.e. Quick Failover Algorithm
>> in SCTP draft-ietf-tsvwg-sctp-failover-08,
>> and I support its progression to RFC.
>>
>> The SCTP PF function is running successfully in various variants in the
>> deployment of the signaling products to alleviate congestion at SCTP path
>> failure. When this WGLC becomes RFC, we will fulfill the RFC in Ericsson's
>> product lines.
>>
>> Many thanks  for the WG work on this draft!
>>
>> Best regards
>>
>> Jun
>> Jun Cheng, Ph.D.
>> Ericsson AB
>> DU Core Networks, PDU Evolved Infrastructure
>> Kistavägen 25
>> 164 80 Stockholm, Sweden
>>
>
>


From nobody Wed Nov 19 12:54:52 2014
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E38801A8739 for <tsvwg@ietfa.amsl.com>; Wed, 19 Nov 2014 12:54:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.145
X-Spam-Level: 
X-Spam-Status: No, score=-2.145 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.594, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3YW9Yz2rK9ip for <tsvwg@ietfa.amsl.com>; Wed, 19 Nov 2014 12:54:44 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38E151A8747 for <tsvwg@ietf.org>; Wed, 19 Nov 2014 12:53:39 -0800 (PST)
Received: from [192.168.1.200] (p508F059E.dip0.t-ipconnect.de [80.143.5.158]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 737A71C1052A8; Wed, 19 Nov 2014 21:53:36 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset=iso-8859-1
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
X-Priority: 3 (Normal)
In-Reply-To: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk>
Date: Wed, 19 Nov 2014 21:53:34 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <798ABCB9-1C4E-4781-A51C-4D3228C0F1EC@lurchi.franken.de>
References: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/sgHGKQJc7bESzkThO0BoejAY_So
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Nov 2014 20:54:49 -0000

On 29 Oct 2014, at 15:01, gorry@erg.abdn.ac.uk wrote:

> TSVWG,
>=20
> This is the start of a WGLC on "Quick Failover Algorithm in SCTP".
> https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08
>=20
> This WGLC will last until Wednesday, 19th November, 2014, this =
includes
> the period of the coming IETF meeting.
>=20
> A good note to the list is "I have read this version of the draft,
> and I approve (or support) its progression to RFC". The chairs
> request notes to the list showing support to get a sense of the WG.
Dear TSVSG,

I have read this version of the ID and approve its progression to RFC.
FreeBSD implements most of the stuff, however exposing the PF_State is
not implemented yet (so no support for the =
SCTP_EXPOSE_POTENTIALLY_FAILED_STATE
socket option). Furthermore, FreeBSD doesn't support yet the =
spt_pathcpthld
field in struct sctp_paddrthlds, which means FreeBSD doesn't support the
optional features described in Section 4.3.

I have a general remark:
The document uses the terms
* Quick failover (it is even in the title of the document)
* Permanent failover
* SCTP-PF
The relation of the above three is not clear for me since they are not
used consistently.

Some editorial comments. Please pick them carefully, since I'm not a =
native
speaker and therefore my suggestions might be sub-optimal. But I think =
the
language used in the document needs to be improved.

* Abstract:
  s/is that it supports multi-homed communication/is the support of =
multi-homing/
  s/[RFC4960] specified failover operation/failover operation as =
specified in [RFC4960]/
  s/of SCTP multi-homed operation./of the SCTP failover operation./
  s/The memo complements RFC 4960/This memo complements [RFC4960]/
  s/of the Potentially Failed state/of the Potentially Failed path =
state/
  s/and associated new/and the associated new/
  s/during network failure/during a network failure./
  s/and specifies for SCTP senders to support this
    more performance optimal failover procedure as an add-on to the
    [RFC4960] failover operation.//
  s/The memo in addition complements [RFC4960]/Furthermore this memo =
complements [RFC4960]/
  s/by introduction of/by introducing of an/
  s/modes/mode/
  s/a failover/the recovery of a failed primary path/
  s/These operation modes offer/This operation mode offers/
  s/for more performance optimal operation in/performance improvements =
in/
  s/=46rom the perspective of this memo the/The/
  s/considered optional./optional./
  s/The procedures defined require/The procedures defined in this =
document require/

* Section 1:
  s/an SCTP association can bind to multiple IP addresses at each =
endpoint/an SCTP endpoint can bind multiple IP addresses./
  s/network interface redundancy and improved end-to-end fault =
tolerance./network fault tolerance./
  s/failed retransmissions/failed timer-based retransmissions/
  s/to SCTP and allows/to SCTP that allows/
  s/after a failover impacts/after the recovery of a failed path/
  s/With [RFC4960] procedures/With the procedures specified in =
[RFC4960]/
  s/switch back to use the primary path/switch back to the primary path/
  s/becomes available./becomes available again./
  s/for SCTP to support the Permanent Failover switchover procedures =
proposed by [CARO02]./the Permanent Failover procedures proposed by =
[CARO02]./
  s/alternative approach/alternative approaches/
  s/provided in Appendix./provided in the Appendices./

* Section 3:
  s/Issues with the SCTP Path Management/Issues with the SCTP Path =
Management as specified in RFC 4960/
  s/issues in the current SCTP/issues in SCTP as specified in [RFC4960]/
  s/SCTP can utilize multiple IP addresses for a single SCTP =
association./An SCTP endpoint can support multiple IP addresses./
  s/initial negotiation/the initial negotiation/
  s/define this as the primary/use this as the primary/
  s/SCTP sends/an SCTP endpoint sends/
  s/heartbeat packets/packets containing a HEARTBEAT chunk/
  s/of the path./of these destination addresses./
  s/to secondary destination address, when/ to an non-primary =
destination address, if/
  s/to be active/to be active and clears the error counter for that =
destination address./
  s/error count for the/error counter for that/
  s/protocol parameter 'Path.Max.Retrans'/tunable protocol parameter =
Path.Max.Retrans (PMR)/
  s/SCTP endpoint/the SCTP endpoint/
  s/(error counter/(the error counter/
  s/stop using non-primary one./stops using the non-primary one./
  s/significant amount/a significant amount/
  s/starts to use the secondary path./starts to use the non-primary path =
for initial data transmission./
  s/in the standard/in [RFC4960]/
  s/before failover takes place/before the failover takes place/
  s/to the secondary address/to an active non-primary address/
  s/to the primary/to the primary address/
  s/to the secondary/to the non-primary/
  s/and can thus be reached at the receiver./and thus can be received by =
the peer./
  s/will not be acceptable/is not acceptable/
  s/path is active again/path becomes active again/

* Section 4:
  s/updates SCTP path management scheme with the Potentially Failed =
state and associated Quick Failover operation./extends the SCTP path =
management scheme by adding the Potentially Failed state and the =
associated Quick Failover operation./

* Section 4.1:
  s/minimize performance impact/minimize the performance impact/
  s/destination/destination address/
  s/destination/destination address/
  s/is ideal so that/is better because/
  s/transitions a destination/can transition a destination address/
  s/a destination as/a destination address/
  Define AMR. It is used here the first time.
  s/address performance impact/address the performance impact/
  s/This new method/SCTP-PF defined in this document/=20
  s/between Active and Failed states/between the Active and Failed =
state/

* Section 4.2:
  s/SCTP-PF Algorithm Detail/SCTP-PF Algorithm in Detail/
  s/SCTP PF operation/The SCTP-PF operation/
  s/Heartbeats/HEARTBEAT chunks/
  s/If an heartbeat is unanswered/If a HEARTBEAT chunk is not =
acknowledged/
  s/another heartbeat immediately/another packet containing a HEARTBEAT =
chunk immediately/
  s/of heartbeats may/of HEARTBEAT chunks MAY/
  s/as SACK or T3-rtx timer/as a T3-rtx timer/
  s/that heartbeats be send/that HEARTBEAT chunks are send/
  s/for the destination address/for that destination address/
  s/receives an heartbeat ACK/receives a HEARTBEAT ACK/
  s/transmit heartbeats to the/transmit HEARTBEAT chunks to the/
  s/ACKs/Acknowledgements/
  s/ACKs/Acknowledgements/
  s/chunks which has been/chunks that have been/
  s/ACKs/SACKs/ or s/ACKs/Acknowledgements/
  s/SCTP stack SHOULD/An SCTP stack should/
  Wouldn't you also want to signal state changes from PF to Failed and =
vice-versa?
  s/such SCTP stack MUST/such an SCTP stack must/
  s/association state transitions/associated state transitions/

* Section 4.3:
  s/degradation, Permanent Failover/degradation, the Permanent Failover/
  s/even if the old primary/even when the old primary/

Sorry for the long list of editorial comments, but I wanted to be as =
concrete as possible.

Best regards
Michael
>=20
> Of course, you can ask for alternate text (where you supply the
> actual replacement text, or convey the meaning sufficiently to the
> authors) for anywhere in the document that you find unclear or =
troublesome.
>=20
> James/Gorry/David
> TSVWG chairs
>=20
>=20


From nobody Fri Nov 21 09:36:39 2014
Return-Path: <bob.briscoe@bt.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A19B1AD5F2 for <tsvwg@ietfa.amsl.com>; Fri, 21 Nov 2014 09:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.195
X-Spam-Level: 
X-Spam-Status: No, score=-3.195 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YF0g9NLM2sfV for <tsvwg@ietfa.amsl.com>; Fri, 21 Nov 2014 09:36:34 -0800 (PST)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.98]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E2451AD67A for <tsvwg@ietf.org>; Fri, 21 Nov 2014 09:34:13 -0800 (PST)
Received: from EVMHR02-UKBR.domain1.systemhost.net (193.113.108.41) by EVMHR66-UKRD.bt.com (10.187.101.21) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 21 Nov 2014 17:34:10 +0000
Received: from EPHR02-UKIP.domain1.systemhost.net (147.149.100.81) by EVMHR02-UKBR.domain1.systemhost.net (193.113.108.41) with Microsoft SMTP Server (TLS) id 8.3.348.2; Fri, 21 Nov 2014 17:34:09 +0000
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR02-UKIP.domain1.systemhost.net (147.149.100.81) with Microsoft SMTP Server id 14.3.181.6; Fri, 21 Nov 2014 17:34:09 +0000
Received: from BTP075694.jungle.bt.co.uk ([10.109.24.23])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id sALHY7vn010130;	Fri, 21 Nov 2014 17:34:07 GMT
Message-ID: <201411211734.sALHY7vn010130@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 21 Nov 2014 17:30:18 +0000
To: Lucy yong <lucy.yong@huawei.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D453FF325@dfweml701-chm>
References: <CE03DB3D7B45C245BCA0D2432779493606DC0C@MX104CL02.corp.emc.com> <2691CE0099834E4A9C5044EEC662BB9D453FF325@dfweml701-chm>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/bWDOxmsnwIr21JaAyiRTgIbLVuw
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: [tsvwg] partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 21 Nov 2014 17:36:37 -0000

Lucy,

I'll wait for David's promised proposal to the list before commenting 
on the checksum issue.

1) Regarding congestion control, I do not share the position of some 
others in tsvwg. Congestion responsiveness is determined by how the 
source spaces out the packets (i.e. their instantaneous rate). Just 
because a tunnel ingress encapsulates a packet with a UDP header does 
not suddenly make it unresponsive to congestion. The spacing between 
packets is still determined by the source. So there is no need to 
even mention congestion control considerations in a tunnelling 
document, except to say in the scoping at the start that the addition 
of tunnel headers is completely orthogonal to congestion avoidance and control.

2)
Please replace:
    Tunnel end points that support
    ECN MUST use the method described in [RFC6040] for ECN marking
    propagation.
With:
    Tunnel end points need to use the method described in [RFC6040] 
for ECN marking
    propagation.
Rationale:
    i) There is no such thing as a tunnel end point that does not 
support ECN - it has to put something in the ECN field, and it would 
not be appropriate to put anything in there other than what RFC6040 says.
   ii) Generally it is not a good idea to fill one draft with 
normative statements that repeat normative statements made in other 
drafts. Otherwise updating an RFC gets very difficult - we have to 
update all the other RFCs that gratuitously repeat what it says.

3) Nit in section 3.1.
    Section 5 of RFC6936 [RFC6936] specifies the additional requirements
    that implementation of UDP zero-checksum over IPv6 MUST compliant
    with. To compliant with it, the following additional requirements
    apply
s/compliant/comply/ (twice)

There are other nits, but they can be dealt with later.


Cheers


Bob




________________________________________________________________
Bob Briscoe,                                                  BT 


From nobody Fri Nov 21 11:08:13 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3DB11A0074 for <tsvwg@ietfa.amsl.com>; Fri, 21 Nov 2014 11:08:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.895
X-Spam-Level: 
X-Spam-Status: No, score=-4.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IH9jUSSHw_Ff for <tsvwg@ietfa.amsl.com>; Fri, 21 Nov 2014 11:08:07 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C31131A0439 for <tsvwg@ietf.org>; Fri, 21 Nov 2014 11:04:13 -0800 (PST)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sALJ48kJ022435 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Nov 2014 14:04:09 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com sALJ48kJ022435
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1416596649; bh=ewR30EKWZU3R4Kem9W0ClEiC/aw=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=N007DEOYTNnUDOB/qdUYWGd3PM1Y323EfySqM3PilUrpmRQik1kUTp7VfledJaU6o HjaG7VzpbFn4mQwKMxkWTpuG319PDAm8Esf3osCf110XMEuDm+3isjWh6bFP1dgr9I MatHPbVIqNUuhREtMcbFmYXz8iy6AlBB/1i+98hw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com sALJ48kJ022435
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd04.lss.emc.com (RSA Interceptor); Fri, 21 Nov 2014 14:03:24 -0500
Received: from mxhub17.corp.emc.com (mxhub17.corp.emc.com [10.254.93.46]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sALJ3our030884 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 21 Nov 2014 14:03:51 -0500
Received: from MXHUB205.corp.emc.com (10.253.68.31) by mxhub17.corp.emc.com (10.254.93.46) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 21 Nov 2014 14:03:50 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.125]) by MXHUB205.corp.emc.com ([fe80::2b:c770:c6f4:ee06%12]) with mapi id 14.03.0195.001; Fri, 21 Nov 2014 14:03:50 -0500
From: "Black, David" <david.black@emc.com>
To: Bob Briscoe <bob.briscoe@bt.com>
Thread-Topic: partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
Thread-Index: AQHQBbFgNPxZKlPnckibF3usr/uACpxrbU8Q
Date: Fri, 21 Nov 2014 19:03:49 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936276347@MX104CL02.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D2432779493606DC0C@MX104CL02.corp.emc.com> <2691CE0099834E4A9C5044EEC662BB9D453FF325@dfweml701-chm> <201411211734.sALHY7vn010130@bagheera.jungle.bt.co.uk>
In-Reply-To: <201411211734.sALHY7vn010130@bagheera.jungle.bt.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.119]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/2vEMhFPo3GYCVuZG3poZhObaN1c
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 21 Nov 2014 19:08:11 -0000

Bob,

> I'll wait for David's promised proposal to the list before commenting
> on the checksum issue.

Don't hold your breath waiting for this one, but you might take a look
at the text on UDP zero checksums for IPv6 in draft-ietf-mpls-in-udp for
a more contained worked example.  The overall approach is applicability
restrictions (networks on which it is ok vs. not ok to use UDP zero
checksums for IPv6) plus additional header checks at tunnel egress -
if/when those are objectionable, turn on full UDP checksums.

> 1) Regarding congestion control, I do not share the position of some
> others in tsvwg. Congestion responsiveness is determined by how the
> source spaces out the packets (i.e. their instantaneous rate). Just
> because a tunnel ingress encapsulates a packet with a UDP header does
> not suddenly make it unresponsive to congestion. The spacing between
> packets is still determined by the source. So there is no need to
> even mention congestion control considerations in a tunneling
> document, except to say in the scoping at the start that the addition
> of tunnel headers is completely orthogonal to congestion avoidance and
> control.

Unfortunately, it's not "completely orthogonal" because UDP goes many
places that the encapsulated protocols can't.  Hence "can't get there
from here" protection in NATs and other middleboxes that drop the
unencapsulated protocol won't stop non-congestion controlled UDP-
encapsulated traffic from getting into places that it shouldn't and
causing damage.  Also, please take note of the text in the mpls-in-udp
draft that recommends filters to block such traffic from going where
it shouldn't, which restores some of these protections.

Thanks,
--David

> -----Original Message-----
> From: Bob Briscoe [mailto:bob.briscoe@bt.com]
> Sent: Friday, November 21, 2014 12:30 PM
> To: Lucy yong
> Cc: Black, David; tsvwg@ietf.org
> Subject: partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
>=20
> Lucy,
>=20
> I'll wait for David's promised proposal to the list before commenting
> on the checksum issue.
>=20
> 1) Regarding congestion control, I do not share the position of some
> others in tsvwg. Congestion responsiveness is determined by how the
> source spaces out the packets (i.e. their instantaneous rate). Just
> because a tunnel ingress encapsulates a packet with a UDP header does
> not suddenly make it unresponsive to congestion. The spacing between
> packets is still determined by the source. So there is no need to
> even mention congestion control considerations in a tunnelling
> document, except to say in the scoping at the start that the addition
> of tunnel headers is completely orthogonal to congestion avoidance and
> control.
>=20
> 2)
> Please replace:
>     Tunnel end points that support
>     ECN MUST use the method described in [RFC6040] for ECN marking
>     propagation.
> With:
>     Tunnel end points need to use the method described in [RFC6040]
> for ECN marking
>     propagation.
> Rationale:
>     i) There is no such thing as a tunnel end point that does not
> support ECN - it has to put something in the ECN field, and it would
> not be appropriate to put anything in there other than what RFC6040 says.
>    ii) Generally it is not a good idea to fill one draft with
> normative statements that repeat normative statements made in other
> drafts. Otherwise updating an RFC gets very difficult - we have to
> update all the other RFCs that gratuitously repeat what it says.
>=20
> 3) Nit in section 3.1.
>     Section 5 of RFC6936 [RFC6936] specifies the additional requirements
>     that implementation of UDP zero-checksum over IPv6 MUST compliant
>     with. To compliant with it, the following additional requirements
>     apply
> s/compliant/comply/ (twice)
>=20
> There are other nits, but they can be dealt with later.
>=20
>=20
> Cheers
>=20
>=20
> Bob
>=20
>=20
>=20
>=20
> ________________________________________________________________
> Bob Briscoe,                                                  BT


From nobody Tue Nov 25 11:55:01 2014
Return-Path: <martin.becke@uni-due.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1B221A6FB4 for <tsvwg@ietfa.amsl.com>; Tue, 25 Nov 2014 11:53:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.96
X-Spam-Level: 
X-Spam-Status: No, score=-0.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_28=0.6, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sQHm9QvFVZwz for <tsvwg@ietfa.amsl.com>; Tue, 25 Nov 2014 11:53:27 -0800 (PST)
Received: from mailoutzim.uni-due.de (mailoutzim.uni-due.de [132.252.185.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9459E1A0367 for <tsvwg@ietf.org>; Tue, 25 Nov 2014 11:53:27 -0800 (PST)
Received: from HT01.win.uni-due.de ([132.252.185.215]) by mailoutzim.uni-due.de (8.13.1/8.13.1) with ESMTP id sAPJrOPO013988 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 25 Nov 2014 20:53:24 +0100
Received: from ccr02.win.uni-due.de ([169.254.2.70]) by HT01.win.uni-due.de ([132.252.190.233]) with mapi id 14.03.0210.002; Tue, 25 Nov 2014 20:53:23 +0100
From: "Becke, Martin" <martin.becke@uni-due.de>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
Thread-Index: AQHP84DRDtBde8o0EkqP4662Lb1M95xx687N
Date: Tue, 25 Nov 2014 19:53:22 +0000
Message-ID: <A33D17830EBE774E8AEFAED600DD54E20180066A0A@ccr02.win.uni-due.de>
References: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk>
In-Reply-To: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [132.252.185.216]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Virus-Scanned: Clam Anti Virus - http://www.clamav.net
X-Spam-Scanned: SpamAssassin: 3.002004 - http://www.spamassassin.org
X-Scanned-By: MIMEDefang 2.57 on 132.252.185.16
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/wgluaxmvk4xVKviiIr8bEbsQsRM
Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Nov 2014 19:53:29 -0000

Hi all, =0A=
=0A=
I read the draft and I still think the algorithm described is functional an=
d useful. I like the idea to introduce a potentially failed state (PF) to o=
ptimize the send process. =0A=
=0A=
I have only some questions/comments (No editorial comments, perhaps a nativ=
e speaker can check the text, too):=0A=
=0A=
- Perhaps the authors can give me a hint why it should be RECOMMENDED  to s=
et the PFMR value to 0 when Quick Failover is used.  I would expect a value=
 > 0 when it is used and 0 when it is not(!) used.   =0A=
=0A=
- I think the term =93multiple destinations=94 irritates.  Perhaps you can =
use =93destination addresses=94 or =93addresses=94 instead=94.  FMPOV the u=
se of the term =93destination=94 in this draft is inaccurate.  In general t=
he terms path, destination, destination address are very mixed for my feeli=
ng. Perhaps this can be rechecked.   =0A=
=0A=
- =93Heartbeats SHOULD be sent to PF destination(s) once per RTO. This mean=
s the sender MUST ignore HB.interval for PF destinations.=94=0A=
 =0A=
This sounds strange to me. Why is SHOULD used here and what are the alterna=
tives, when I MUST ignore HB.interval for PF destinations. I guess a rephra=
se of this two lines can help. =0A=
=0A=
- A link is missing in Section 5.1: [RFC6458] defines the constants SCTP_AD=
DR_AVAILABLE,=85.=0A=
=0A=
Best =0A=
________________________________________=0A=
Von: tsvwg [tsvwg-bounces@ietf.org]&quot; im Auftrag von &quot;gorry@erg.ab=
dn.ac.uk [gorry@erg.abdn.ac.uk]=0A=
Gesendet: Mittwoch, 29. Oktober 2014 15:01=0A=
An: tsvwg@ietf.org=0A=
Cc: gorry@erg.abdn.ac.uk=0A=
Betreff: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 1=
9th November, 2014=0A=
=0A=
TSVWG,=0A=
=0A=
This is the start of a WGLC on "Quick Failover Algorithm in SCTP".=0A=
https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08=0A=
=0A=
This WGLC will last until Wednesday, 19th November, 2014, this includes=0A=
the period of the coming IETF meeting.=0A=
=0A=
A good note to the list is "I have read this version of the draft,=0A=
and I approve (or support) its progression to RFC". The chairs=0A=
request notes to the list showing support to get a sense of the WG.=0A=
=0A=
Of course, you can ask for alternate text (where you supply the=0A=
actual replacement text, or convey the meaning sufficiently to the=0A=
authors) for anywhere in the document that you find unclear or troublesome.=
=0A=
=0A=
James/Gorry/David=0A=
TSVWG chairs=0A=
=0A=


From nobody Wed Nov 26 00:28:00 2014
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F26051A6F5A for <tsvwg@ietfa.amsl.com>; Wed, 26 Nov 2014 00:27:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.961
X-Spam-Level: 
X-Spam-Status: No, score=-0.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_28=0.6, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vDVFF2qYtkNM for <tsvwg@ietfa.amsl.com>; Wed, 26 Nov 2014 00:27:57 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D4D91A6F57 for <tsvwg@ietf.org>; Wed, 26 Nov 2014 00:27:57 -0800 (PST)
Received: from [192.168.1.200] (p548190F0.dip0.t-ipconnect.de [84.129.144.240]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 44E911C1622BA; Wed, 26 Nov 2014 09:27:55 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <A33D17830EBE774E8AEFAED600DD54E20180066A0A@ccr02.win.uni-due.de>
Date: Wed, 26 Nov 2014 09:27:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3275B07E-DFD6-412E-97D5-7E71740DDBBC@lurchi.franken.de>
References: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk> <A33D17830EBE774E8AEFAED600DD54E20180066A0A@ccr02.win.uni-due.de>
To: Martin Becke <martin.becke@uni-due.de>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/pEZYhu8nCrqPwgx63B2JCOfJDOo
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Nov 2014 08:27:59 -0000

On 25 Nov 2014, at 20:53, Becke, Martin <martin.becke@uni-due.de> wrote:

> Hi all,=20
>=20
> I read the draft and I still think the algorithm described is =
functional and useful. I like the idea to introduce a potentially failed =
state (PF) to optimize the send process.=20
>=20
> I have only some questions/comments (No editorial comments, perhaps a =
native speaker can check the text, too):
>=20
> - Perhaps the authors can give me a hint why it should be RECOMMENDED  =
to set the PFMR value to 0 when Quick Failover is used.  I would expect =
a value > 0 when it is used and 0 when it is not(!) used.  =20
Because it is not a flag controlling the usage of Quick Failover, but a =
threshold. See second item
in the enumeration in Section 4.2.

Best regards
Michael
>=20
> - I think the term =93multiple destinations=94 irritates.  Perhaps you =
can use =93destination addresses=94 or =93addresses=94 instead=94.  =
FMPOV the use of the term =93destination=94 in this draft is inaccurate. =
 In general the terms path, destination, destination address are very =
mixed for my feeling. Perhaps this can be rechecked.  =20
>=20
> - =93Heartbeats SHOULD be sent to PF destination(s) once per RTO. This =
means the sender MUST ignore HB.interval for PF destinations.=94
>=20
> This sounds strange to me. Why is SHOULD used here and what are the =
alternatives, when I MUST ignore HB.interval for PF destinations. I =
guess a rephrase of this two lines can help.=20
>=20
> - A link is missing in Section 5.1: [RFC6458] defines the constants =
SCTP_ADDR_AVAILABLE,=85.
>=20
> Best=20
> ________________________________________
> Von: tsvwg [tsvwg-bounces@ietf.org]&quot; im Auftrag von =
&quot;gorry@erg.abdn.ac.uk [gorry@erg.abdn.ac.uk]
> Gesendet: Mittwoch, 29. Oktober 2014 15:01
> An: tsvwg@ietf.org
> Cc: gorry@erg.abdn.ac.uk
> Betreff: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To =
conclude 19th November, 2014
>=20
> TSVWG,
>=20
> This is the start of a WGLC on "Quick Failover Algorithm in SCTP".
> https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08
>=20
> This WGLC will last until Wednesday, 19th November, 2014, this =
includes
> the period of the coming IETF meeting.
>=20
> A good note to the list is "I have read this version of the draft,
> and I approve (or support) its progression to RFC". The chairs
> request notes to the list showing support to get a sense of the WG.
>=20
> Of course, you can ask for alternate text (where you supply the
> actual replacement text, or convey the meaning sufficiently to the
> authors) for anywhere in the document that you find unclear or =
troublesome.
>=20
> James/Gorry/David
> TSVWG chairs
>=20
>=20
>=20


From nobody Wed Nov 26 00:42:17 2014
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8831A0049 for <tsvwg@ietfa.amsl.com>; Wed, 26 Nov 2014 00:42:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.221
X-Spam-Level: *
X-Spam-Status: No, score=1.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KQVsifdkvd1h for <tsvwg@ietfa.amsl.com>; Wed, 26 Nov 2014 00:42:10 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [IPv6:2001:200:0:8803::53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A47D11A002F for <tsvwg@ietf.org>; Wed, 26 Nov 2014 00:42:10 -0800 (PST)
Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com [209.85.217.170]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id F2E7027817F for <tsvwg@ietf.org>; Wed, 26 Nov 2014 17:42:07 +0900 (JST)
Received: by mail-lb0-f170.google.com with SMTP id w7so2053620lbi.15 for <tsvwg@ietf.org>; Wed, 26 Nov 2014 00:42:05 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.112.130.65 with SMTP id oc1mr33057199lbb.7.1416991325576; Wed, 26 Nov 2014 00:42:05 -0800 (PST)
Received: by 10.114.200.170 with HTTP; Wed, 26 Nov 2014 00:42:05 -0800 (PST)
In-Reply-To: <798ABCB9-1C4E-4781-A51C-4D3228C0F1EC@lurchi.franken.de>
References: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk> <798ABCB9-1C4E-4781-A51C-4D3228C0F1EC@lurchi.franken.de>
Date: Wed, 26 Nov 2014 00:42:05 -0800
Message-ID: <CAO249yewdBLPwAJBeu8q8cQKCWmZV0+e4T+YC9GFbwktbO+iMA@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Content-Type: multipart/alternative; boundary=047d7b3433189c65d70508bf0015
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/el7-wNOFKAHreddSHCCo93BtKCg
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Nov 2014 08:42:14 -0000

--047d7b3433189c65d70508bf0015
Content-Type: text/plain; charset=UTF-8

Hi Michael,

On Wed, Nov 19, 2014 at 12:53 PM, Michael Tuexen <
Michael.Tuexen@lurchi.franken.de> wrote:

> On 29 Oct 2014, at 15:01, gorry@erg.abdn.ac.uk wrote:
>
> > TSVWG,
> >
> > This is the start of a WGLC on "Quick Failover Algorithm in SCTP".
> > https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08
> >
> > This WGLC will last until Wednesday, 19th November, 2014, this includes
> > the period of the coming IETF meeting.
> >
> > A good note to the list is "I have read this version of the draft,
> > and I approve (or support) its progression to RFC". The chairs
> > request notes to the list showing support to get a sense of the WG.
> Dear TSVSG,
>
> I have read this version of the ID and approve its progression to RFC.
> FreeBSD implements most of the stuff, however exposing the PF_State is
> not implemented yet (so no support for the
> SCTP_EXPOSE_POTENTIALLY_FAILED_STATE
> socket option). Furthermore, FreeBSD doesn't support yet the spt_pathcpthld
> field in struct sctp_paddrthlds, which means FreeBSD doesn't support the
> optional features described in Section 4.3.
>

Thanks for the info.
I just would like to mention that there is no conflict between the draft
and freebsd implementation as these missing features are optional or
informational.


> I have a general remark:
> The document uses the terms
> * Quick failover (it is even in the title of the document)
> * Permanent failover
> * SCTP-PF
> The relation of the above three is not clear for me since they are not
> used consistently.
>

Yes. This makes senses. Thanks for pointing out. We'll think about how to
solve this inconsistency.


> Some editorial comments. Please pick them carefully, since I'm not a native
> speaker and therefore my suggestions might be sub-optimal. But I think the
> language used in the document needs to be improved.


> * Abstract:
>   s/is that it supports multi-homed communication/is the support of
> multi-homing/
>   s/[RFC4960] specified failover operation/failover operation as specified
> in [RFC4960]/
>   s/of SCTP multi-homed operation./of the SCTP failover operation./
>   s/The memo complements RFC 4960/This memo complements [RFC4960]/
>   s/of the Potentially Failed state/of the Potentially Failed path state/
>   s/and associated new/and the associated new/
>   s/during network failure/during a network failure./
>   s/and specifies for SCTP senders to support this
>     more performance optimal failover procedure as an add-on to the
>     [RFC4960] failover operation.//
>   s/The memo in addition complements [RFC4960]/Furthermore this memo
> complements [RFC4960]/
>   s/by introduction of/by introducing of an/
>   s/modes/mode/
>   s/a failover/the recovery of a failed primary path/
>   s/These operation modes offer/This operation mode offers/
>   s/for more performance optimal operation in/performance improvements in/
>   s/From the perspective of this memo the/The/
>   s/considered optional./optional./
>   s/The procedures defined require/The procedures defined in this document
> require/
>
> * Section 1:
>   s/an SCTP association can bind to multiple IP addresses at each
> endpoint/an SCTP endpoint can bind multiple IP addresses./
>   s/network interface redundancy and improved end-to-end fault
> tolerance./network fault tolerance./
>   s/failed retransmissions/failed timer-based retransmissions/
>   s/to SCTP and allows/to SCTP that allows/
>   s/after a failover impacts/after the recovery of a failed path/
>   s/With [RFC4960] procedures/With the procedures specified in [RFC4960]/
>   s/switch back to use the primary path/switch back to the primary path/
>   s/becomes available./becomes available again./
>   s/for SCTP to support the Permanent Failover switchover procedures
> proposed by [CARO02]./the Permanent Failover procedures proposed by
> [CARO02]./
>   s/alternative approach/alternative approaches/
>   s/provided in Appendix./provided in the Appendices./
>
> * Section 3:
>   s/Issues with the SCTP Path Management/Issues with the SCTP Path
> Management as specified in RFC 4960/
>   s/issues in the current SCTP/issues in SCTP as specified in [RFC4960]/
>   s/SCTP can utilize multiple IP addresses for a single SCTP
> association./An SCTP endpoint can support multiple IP addresses./
>   s/initial negotiation/the initial negotiation/
>   s/define this as the primary/use this as the primary/
>   s/SCTP sends/an SCTP endpoint sends/
>   s/heartbeat packets/packets containing a HEARTBEAT chunk/
>   s/of the path./of these destination addresses./
>   s/to secondary destination address, when/ to an non-primary destination
> address, if/
>   s/to be active/to be active and clears the error counter for that
> destination address./
>   s/error count for the/error counter for that/
>   s/protocol parameter 'Path.Max.Retrans'/tunable protocol parameter
> Path.Max.Retrans (PMR)/
>   s/SCTP endpoint/the SCTP endpoint/
>   s/(error counter/(the error counter/
>   s/stop using non-primary one./stops using the non-primary one./
>   s/significant amount/a significant amount/
>   s/starts to use the secondary path./starts to use the non-primary path
> for initial data transmission./
>   s/in the standard/in [RFC4960]/
>   s/before failover takes place/before the failover takes place/
>   s/to the secondary address/to an active non-primary address/
>   s/to the primary/to the primary address/
>   s/to the secondary/to the non-primary/
>   s/and can thus be reached at the receiver./and thus can be received by
> the peer./
>   s/will not be acceptable/is not acceptable/
>   s/path is active again/path becomes active again/
>
> * Section 4:
>   s/updates SCTP path management scheme with the Potentially Failed state
> and associated Quick Failover operation./extends the SCTP path management
> scheme by adding the Potentially Failed state and the associated Quick
> Failover operation./
>
> * Section 4.1:
>   s/minimize performance impact/minimize the performance impact/
>   s/destination/destination address/
>   s/destination/destination address/
>   s/is ideal so that/is better because/
>   s/transitions a destination/can transition a destination address/
>   s/a destination as/a destination address/
>   Define AMR. It is used here the first time.
>   s/address performance impact/address the performance impact/
>   s/This new method/SCTP-PF defined in this document/
>   s/between Active and Failed states/between the Active and Failed state/
>
> * Section 4.2:
>   s/SCTP-PF Algorithm Detail/SCTP-PF Algorithm in Detail/
>   s/SCTP PF operation/The SCTP-PF operation/
>   s/Heartbeats/HEARTBEAT chunks/
>   s/If an heartbeat is unanswered/If a HEARTBEAT chunk is not acknowledged/
>   s/another heartbeat immediately/another packet containing a HEARTBEAT
> chunk immediately/
>   s/of heartbeats may/of HEARTBEAT chunks MAY/
>   s/as SACK or T3-rtx timer/as a T3-rtx timer/
>   s/that heartbeats be send/that HEARTBEAT chunks are send/
>   s/for the destination address/for that destination address/
>   s/receives an heartbeat ACK/receives a HEARTBEAT ACK/
>   s/transmit heartbeats to the/transmit HEARTBEAT chunks to the/
>   s/ACKs/Acknowledgements/
>   s/ACKs/Acknowledgements/
>   s/chunks which has been/chunks that have been/
>   s/ACKs/SACKs/ or s/ACKs/Acknowledgements/
>   s/SCTP stack SHOULD/An SCTP stack should/
>   Wouldn't you also want to signal state changes from PF to Failed and
> vice-versa?
>   s/such SCTP stack MUST/such an SCTP stack must/
>   s/association state transitions/associated state transitions/
>
> * Section 4.3:
>   s/degradation, Permanent Failover/degradation, the Permanent Failover/
>   s/even if the old primary/even when the old primary/
>
> Sorry for the long list of editorial comments, but I wanted to be as
> concrete as possible.
>

Thank you so much! They look very reasonable although we'll need to check
in detail.
We appreciate very detailed comments.

Regards,
--
Yoshi

--047d7b3433189c65d70508bf0015
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Michael,<div><br></div><div><div class=3D"gmail_extra">=
<div class=3D"gmail_quote">On Wed, Nov 19, 2014 at 12:53 PM, Michael Tuexen=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Tuexen@lurchi.franken.de" =
target=3D"_blank">Michael.Tuexen@lurchi.franken.de</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;=
padding-left:1ex"><span class=3D"">On 29 Oct 2014, at 15:01, <a href=3D"mai=
lto:gorry@erg.abdn.ac.uk">gorry@erg.abdn.ac.uk</a> wrote:<br>
<br>
&gt; TSVWG,<br>
&gt;<br>
&gt; This is the start of a WGLC on &quot;Quick Failover Algorithm in SCTP&=
quot;.<br>
&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-=
08" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-fai=
lover-08</a><br>
&gt;<br>
&gt; This WGLC will last until Wednesday, 19th November, 2014, this include=
s<br>
&gt; the period of the coming IETF meeting.<br>
&gt;<br>
&gt; A good note to the list is &quot;I have read this version of the draft=
,<br>
&gt; and I approve (or support) its progression to RFC&quot;. The chairs<br=
>
&gt; request notes to the list showing support to get a sense of the WG.<br=
>
</span>Dear TSVSG,<br>
<br>
I have read this version of the ID and approve its progression to RFC.<br>
FreeBSD implements most of the stuff, however exposing the PF_State is<br>
not implemented yet (so no support for the SCTP_EXPOSE_POTENTIALLY_FAILED_S=
TATE<br>
socket option). Furthermore, FreeBSD doesn&#39;t support yet the spt_pathcp=
thld<br>
field in struct sctp_paddrthlds, which means FreeBSD doesn&#39;t support th=
e<br>
optional features described in Section 4.3.<br></blockquote><div><br></div>=
<div>Thanks for the info.</div><div>I just would like to mention that there=
 is no conflict between the draft and freebsd implementation as these missi=
ng features are optional or informational.</div><div>=C2=A0<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w=
idth:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding=
-left:1ex">
I have a general remark:<br>
The document uses the terms<br>
* Quick failover (it is even in the title of the document)<br>
* Permanent failover<br>
* SCTP-PF<br>
The relation of the above three is not clear for me since they are not<br>
used consistently.<br></blockquote><div><br></div><div>Yes. This makes sens=
es. Thanks for pointing out. We&#39;ll think about how to solve this incons=
istency.=C2=A0</div><div>=C2=A0<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:r=
gb(204,204,204);border-left-style:solid;padding-left:1ex">
Some editorial comments. Please pick them carefully, since I&#39;m not a na=
tive<br>
speaker and therefore my suggestions might be sub-optimal. But I think the<=
br>
language used in the document needs to be improved.</blockquote><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:=
1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left=
:1ex">
<br>
* Abstract:<br>
=C2=A0 s/is that it supports multi-homed communication/is the support of mu=
lti-homing/<br>
=C2=A0 s/[RFC4960] specified failover operation/failover operation as speci=
fied in [RFC4960]/<br>
=C2=A0 s/of SCTP multi-homed operation./of the SCTP failover operation./<br=
>
=C2=A0 s/The memo complements RFC 4960/This memo complements [RFC4960]/<br>
=C2=A0 s/of the Potentially Failed state/of the Potentially Failed path sta=
te/<br>
=C2=A0 s/and associated new/and the associated new/<br>
=C2=A0 s/during network failure/during a network failure./<br>
=C2=A0 s/and specifies for SCTP senders to support this<br>
=C2=A0 =C2=A0 more performance optimal failover procedure as an add-on to t=
he<br>
=C2=A0 =C2=A0 [RFC4960] failover operation.//<br>
=C2=A0 s/The memo in addition complements [RFC4960]/Furthermore this memo c=
omplements [RFC4960]/<br>
=C2=A0 s/by introduction of/by introducing of an/<br>
=C2=A0 s/modes/mode/<br>
=C2=A0 s/a failover/the recovery of a failed primary path/<br>
=C2=A0 s/These operation modes offer/This operation mode offers/<br>
=C2=A0 s/for more performance optimal operation in/performance improvements=
 in/<br>
=C2=A0 s/From the perspective of this memo the/The/<br>
=C2=A0 s/considered optional./optional./<br>
=C2=A0 s/The procedures defined require/The procedures defined in this docu=
ment require/<br>
<br>
* Section 1:<br>
=C2=A0 s/an SCTP association can bind to multiple IP addresses at each endp=
oint/an SCTP endpoint can bind multiple IP addresses./<br>
=C2=A0 s/network interface redundancy and improved end-to-end fault toleran=
ce./network fault tolerance./<br>
=C2=A0 s/failed retransmissions/failed timer-based retransmissions/<br>
=C2=A0 s/to SCTP and allows/to SCTP that allows/<br>
=C2=A0 s/after a failover impacts/after the recovery of a failed path/<br>
=C2=A0 s/With [RFC4960] procedures/With the procedures specified in [RFC496=
0]/<br>
=C2=A0 s/switch back to use the primary path/switch back to the primary pat=
h/<br>
=C2=A0 s/becomes available./becomes available again./<br>
=C2=A0 s/for SCTP to support the Permanent Failover switchover procedures p=
roposed by [CARO02]./the Permanent Failover procedures proposed by [CARO02]=
./<br>
=C2=A0 s/alternative approach/alternative approaches/<br>
=C2=A0 s/provided in Appendix./provided in the Appendices./<br>
<br>
* Section 3:<br>
=C2=A0 s/Issues with the SCTP Path Management/Issues with the SCTP Path Man=
agement as specified in RFC 4960/<br>
=C2=A0 s/issues in the current SCTP/issues in SCTP as specified in [RFC4960=
]/<br>
=C2=A0 s/SCTP can utilize multiple IP addresses for a single SCTP associati=
on./An SCTP endpoint can support multiple IP addresses./<br>
=C2=A0 s/initial negotiation/the initial negotiation/<br>
=C2=A0 s/define this as the primary/use this as the primary/<br>
=C2=A0 s/SCTP sends/an SCTP endpoint sends/<br>
=C2=A0 s/heartbeat packets/packets containing a HEARTBEAT chunk/<br>
=C2=A0 s/of the path./of these destination addresses./<br>
=C2=A0 s/to secondary destination address, when/ to an non-primary destinat=
ion address, if/<br>
=C2=A0 s/to be active/to be active and clears the error counter for that de=
stination address./<br>
=C2=A0 s/error count for the/error counter for that/<br>
=C2=A0 s/protocol parameter &#39;Path.Max.Retrans&#39;/tunable protocol par=
ameter Path.Max.Retrans (PMR)/<br>
=C2=A0 s/SCTP endpoint/the SCTP endpoint/<br>
=C2=A0 s/(error counter/(the error counter/<br>
=C2=A0 s/stop using non-primary one./stops using the non-primary one./<br>
=C2=A0 s/significant amount/a significant amount/<br>
=C2=A0 s/starts to use the secondary path./starts to use the non-primary pa=
th for initial data transmission./<br>
=C2=A0 s/in the standard/in [RFC4960]/<br>
=C2=A0 s/before failover takes place/before the failover takes place/<br>
=C2=A0 s/to the secondary address/to an active non-primary address/<br>
=C2=A0 s/to the primary/to the primary address/<br>
=C2=A0 s/to the secondary/to the non-primary/<br>
=C2=A0 s/and can thus be reached at the receiver./and thus can be received =
by the peer./<br>
=C2=A0 s/will not be acceptable/is not acceptable/<br>
=C2=A0 s/path is active again/path becomes active again/<br>
<br>
* Section 4:<br>
=C2=A0 s/updates SCTP path management scheme with the Potentially Failed st=
ate and associated Quick Failover operation./extends the SCTP path manageme=
nt scheme by adding the Potentially Failed state and the associated Quick F=
ailover operation./<br>
<br>
* Section 4.1:<br>
=C2=A0 s/minimize performance impact/minimize the performance impact/<br>
=C2=A0 s/destination/destination address/<br>
=C2=A0 s/destination/destination address/<br>
=C2=A0 s/is ideal so that/is better because/<br>
=C2=A0 s/transitions a destination/can transition a destination address/<br=
>
=C2=A0 s/a destination as/a destination address/<br>
=C2=A0 Define AMR. It is used here the first time.<br>
=C2=A0 s/address performance impact/address the performance impact/<br>
=C2=A0 s/This new method/SCTP-PF defined in this document/<br>
=C2=A0 s/between Active and Failed states/between the Active and Failed sta=
te/<br>
<br>
* Section 4.2:<br>
=C2=A0 s/SCTP-PF Algorithm Detail/SCTP-PF Algorithm in Detail/<br>
=C2=A0 s/SCTP PF operation/The SCTP-PF operation/<br>
=C2=A0 s/Heartbeats/HEARTBEAT chunks/<br>
=C2=A0 s/If an heartbeat is unanswered/If a HEARTBEAT chunk is not acknowle=
dged/<br>
=C2=A0 s/another heartbeat immediately/another packet containing a HEARTBEA=
T chunk immediately/<br>
=C2=A0 s/of heartbeats may/of HEARTBEAT chunks MAY/<br>
=C2=A0 s/as SACK or T3-rtx timer/as a T3-rtx timer/<br>
=C2=A0 s/that heartbeats be send/that HEARTBEAT chunks are send/<br>
=C2=A0 s/for the destination address/for that destination address/<br>
=C2=A0 s/receives an heartbeat ACK/receives a HEARTBEAT ACK/<br>
=C2=A0 s/transmit heartbeats to the/transmit HEARTBEAT chunks to the/<br>
=C2=A0 s/ACKs/Acknowledgements/<br>
=C2=A0 s/ACKs/Acknowledgements/<br>
=C2=A0 s/chunks which has been/chunks that have been/<br>
=C2=A0 s/ACKs/SACKs/ or s/ACKs/Acknowledgements/<br>
=C2=A0 s/SCTP stack SHOULD/An SCTP stack should/<br>
=C2=A0 Wouldn&#39;t you also want to signal state changes from PF to Failed=
 and vice-versa?<br>
=C2=A0 s/such SCTP stack MUST/such an SCTP stack must/<br>
=C2=A0 s/association state transitions/associated state transitions/<br>
<br>
* Section 4.3:<br>
=C2=A0 s/degradation, Permanent Failover/degradation, the Permanent Failove=
r/<br>
=C2=A0 s/even if the old primary/even when the old primary/<br>
<br>
Sorry for the long list of editorial comments, but I wanted to be as concre=
te as possible.<br></blockquote><div><br></div><div>Thank you so much! They=
 look very reasonable although we&#39;ll need to check in detail.=C2=A0</di=
v><div>We appreciate very detailed comments.</div><div><br></div><div>Regar=
ds,</div><div>--</div><div>Yoshi</div></div></div></div></div>

--047d7b3433189c65d70508bf0015--


From nobody Wed Nov 26 00:42:49 2014
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 808261A002F for <tsvwg@ietfa.amsl.com>; Wed, 26 Nov 2014 00:42:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.815
X-Spam-Level: **
X-Spam-Status: No, score=2.815 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, J_CHICKENPOX_28=0.6, RELAY_IS_203=0.994, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GlYDMTPNrXCf for <tsvwg@ietfa.amsl.com>; Wed, 26 Nov 2014 00:42:35 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DA951A6FFD for <tsvwg@ietf.org>; Wed, 26 Nov 2014 00:42:35 -0800 (PST)
Received: from mail-lb0-f175.google.com (mail-lb0-f175.google.com [209.85.217.175]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 4095E278180 for <tsvwg@ietf.org>; Wed, 26 Nov 2014 17:42:33 +0900 (JST)
Received: by mail-lb0-f175.google.com with SMTP id u10so1985734lbd.20 for <tsvwg@ietf.org>; Wed, 26 Nov 2014 00:42:31 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.152.5.198 with SMTP id u6mr33481270lau.42.1416991351092; Wed, 26 Nov 2014 00:42:31 -0800 (PST)
Received: by 10.114.200.170 with HTTP; Wed, 26 Nov 2014 00:42:31 -0800 (PST)
In-Reply-To: <A33D17830EBE774E8AEFAED600DD54E20180066A0A@ccr02.win.uni-due.de>
References: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk> <A33D17830EBE774E8AEFAED600DD54E20180066A0A@ccr02.win.uni-due.de>
Date: Wed, 26 Nov 2014 00:42:31 -0800
Message-ID: <CAO249ycHQSxk+0+63Wr6AWvPrhjtiJDyRpaU2s9KC+BNd=eB-Q@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: "Becke, Martin" <martin.becke@uni-due.de>
Content-Type: multipart/alternative; boundary=089e013d1b6e21bc3b0508bf02a3
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/y3ON3u3Vrm-qHTNBCQj4gn-OIbw
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Nov 2014 08:42:37 -0000

--089e013d1b6e21bc3b0508bf02a3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Martin,

Thanks for the comments.

On Tue, Nov 25, 2014 at 11:53 AM, Becke, Martin <martin.becke@uni-due.de>
wrote:

> Hi all,
>
> I read the draft and I still think the algorithm described is functional
> and useful. I like the idea to introduce a potentially failed state (PF) =
to
> optimize the send process.
>
> I have only some questions/comments (No editorial comments, perhaps a
> native speaker can check the text, too):
>
> - Perhaps the authors can give me a hint why it should be RECOMMENDED  to
> set the PFMR value to 0 when Quick Failover is used.  I would expect a
> value > 0 when it is used and 0 when it is not(!) used.
>

Setting PFMR to 0 means one single timeout triggers Quick Failover.
According to some studies, this will be the most efficient setting as you
can quickly utilize another available path. Setting PFMR to PFMR > 0 &&
PFMR < PMR means you'll need some consecutive timeouts before Quick
Failover is triggered.
As described, when PFMR >=3D PMR, Quick Failover will be turned off.


> - I think the term =E2=80=9Cmultiple destinations=E2=80=9D irritates.  Pe=
rhaps you can use
> =E2=80=9Cdestination addresses=E2=80=9D or =E2=80=9Caddresses=E2=80=9D in=
stead=E2=80=9D.  FMPOV the use of the term
> =E2=80=9Cdestination=E2=80=9D in this draft is inaccurate.  In general th=
e terms path,
> destination, destination address are very mixed for my feeling. Perhaps
> this can be rechecked.
>

OK. We'll check this.

>
> - =E2=80=9CHeartbeats SHOULD be sent to PF destination(s) once per RTO. T=
his means
> the sender MUST ignore HB.interval for PF destinations.=E2=80=9D
>
> This sounds strange to me. Why is SHOULD used here and what are the
> alternatives, when I MUST ignore HB.interval for PF destinations. I guess=
 a
> rephrase of this two lines can help.
>

I see your point. We'll think about this. I think we should change SHOULD
to MUST for now.

>
> - A link is missing in Section 5.1: [RFC6458] defines the constants
> SCTP_ADDR_AVAILABLE,=E2=80=A6.
>

Thanks for pointing out! We'll fix this.

Regards,
--
Yoshi

________________________________________
> Von: tsvwg [tsvwg-bounces@ietf.org]&quot; im Auftrag von &
> quot;gorry@erg.abdn.ac.uk [gorry@erg.abdn.ac.uk]
> Gesendet: Mittwoch, 29. Oktober 2014 15:01
> An: tsvwg@ietf.org
> Cc: gorry@erg.abdn.ac.uk
> Betreff: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude
> 19th November, 2014
>
> TSVWG,
>
> This is the start of a WGLC on "Quick Failover Algorithm in SCTP".
> https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08
>
> This WGLC will last until Wednesday, 19th November, 2014, this includes
> the period of the coming IETF meeting.
>
> A good note to the list is "I have read this version of the draft,
> and I approve (or support) its progression to RFC". The chairs
> request notes to the list showing support to get a sense of the WG.
>
> Of course, you can ask for alternate text (where you supply the
> actual replacement text, or convey the meaning sufficiently to the
> authors) for anywhere in the document that you find unclear or troublesom=
e.
>
> James/Gorry/David
> TSVWG chairs
>
>
>

--089e013d1b6e21bc3b0508bf02a3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Martin,<div><br></div><div>Thanks for the comments.<br>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Nov 25, 2=
014 at 11:53 AM, Becke, Martin <span dir=3D"ltr">&lt;<a href=3D"mailto:mart=
in.becke@uni-due.de" target=3D"_blank">martin.becke@uni-due.de</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
I read the draft and I still think the algorithm described is functional an=
d useful. I like the idea to introduce a potentially failed state (PF) to o=
ptimize the send process.<br>
<br>
I have only some questions/comments (No editorial comments, perhaps a nativ=
e speaker can check the text, too):<br>
<br>
- Perhaps the authors can give me a hint why it should be RECOMMENDED=C2=A0=
 to set the PFMR value to 0 when Quick Failover is used.=C2=A0 I would expe=
ct a value &gt; 0 when it is used and 0 when it is not(!) used.<br></blockq=
uote><div><br></div><div>Setting PFMR to 0 means one single timeout trigger=
s Quick Failover. According to some studies, this will be the most efficien=
t setting as you can quickly utilize another available path. Setting PFMR t=
o PFMR &gt; 0 &amp;&amp; PFMR &lt; PMR means you&#39;ll need some consecuti=
ve timeouts before Quick Failover is triggered.=C2=A0</div><div>As describe=
d, when PFMR &gt;=3D PMR, Quick Failover will be turned off.</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
- I think the term =E2=80=9Cmultiple destinations=E2=80=9D irritates.=C2=A0=
 Perhaps you can use =E2=80=9Cdestination addresses=E2=80=9D or =E2=80=9Cad=
dresses=E2=80=9D instead=E2=80=9D.=C2=A0 FMPOV the use of the term =E2=80=
=9Cdestination=E2=80=9D in this draft is inaccurate.=C2=A0 In general the t=
erms path, destination, destination address are very mixed for my feeling. =
Perhaps this can be rechecked.<br></blockquote><div><br></div><div>OK. We&#=
39;ll check this.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- =E2=80=9CHeartbeats SHOULD be sent to PF destination(s) once per RTO. Thi=
s means the sender MUST ignore HB.interval for PF destinations.=E2=80=9D<br=
>
<br>
This sounds strange to me. Why is SHOULD used here and what are the alterna=
tives, when I MUST ignore HB.interval for PF destinations. I guess a rephra=
se of this two lines can help.<br></blockquote><div><br></div><div>I see yo=
ur point. We&#39;ll think about this. I think we should change SHOULD to MU=
ST for now.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
- A link is missing in Section 5.1: [RFC6458] defines the constants SCTP_AD=
DR_AVAILABLE,=E2=80=A6.<br></blockquote><div><br></div><div>Thanks for poin=
ting out! We&#39;ll fix this.=C2=A0</div><div><br></div><div>Regards,</div>=
<div>--</div><div>Yoshi</div><div><br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
________________________________________<br>
Von: tsvwg [<a href=3D"mailto:tsvwg-bounces@ietf.org">tsvwg-bounces@ietf.or=
g</a>]&amp;quot; im Auftrag von &amp;<a href=3D"mailto:quot%3Bgorry@erg.abd=
n.ac.uk">quot;gorry@erg.abdn.ac.uk</a> [<a href=3D"mailto:gorry@erg.abdn.ac=
.uk">gorry@erg.abdn.ac.uk</a>]<br>
Gesendet: Mittwoch, 29. Oktober 2014 15:01<br>
An: <a href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a><br>
Cc: <a href=3D"mailto:gorry@erg.abdn.ac.uk">gorry@erg.abdn.ac.uk</a><br>
Betreff: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 1=
9th November, 2014<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
TSVWG,<br>
<br>
This is the start of a WGLC on &quot;Quick Failover Algorithm in SCTP&quot;=
.<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08" t=
arget=3D"_blank">https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover=
-08</a><br>
<br>
This WGLC will last until Wednesday, 19th November, 2014, this includes<br>
the period of the coming IETF meeting.<br>
<br>
A good note to the list is &quot;I have read this version of the draft,<br>
and I approve (or support) its progression to RFC&quot;. The chairs<br>
request notes to the list showing support to get a sense of the WG.<br>
<br>
Of course, you can ask for alternate text (where you supply the<br>
actual replacement text, or convey the meaning sufficiently to the<br>
authors) for anywhere in the document that you find unclear or troublesome.=
<br>
<br>
James/Gorry/David<br>
TSVWG chairs<br>
<br>
<br>
</div></div></blockquote></div><br></div></div></div>

--089e013d1b6e21bc3b0508bf02a3--


From nobody Wed Nov 26 02:24:53 2014
Return-Path: <martin.becke@uni-due.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B737F1A8A3A for <tsvwg@ietfa.amsl.com>; Wed, 26 Nov 2014 02:24:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.96
X-Spam-Level: 
X-Spam-Status: No, score=-0.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_28=0.6, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qUwg1ukzBFN1 for <tsvwg@ietfa.amsl.com>; Wed, 26 Nov 2014 02:24:49 -0800 (PST)
Received: from mailoutzim.uni-due.de (mailoutzim.uni-due.de [132.252.185.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 824731A8A39 for <tsvwg@ietf.org>; Wed, 26 Nov 2014 02:24:48 -0800 (PST)
Received: from HT01.win.uni-due.de ([132.252.185.215]) by mailoutzim.uni-due.de (8.13.1/8.13.1) with ESMTP id sAQANWiX009944 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 26 Nov 2014 11:24:46 +0100
Received: from ccr02.win.uni-due.de ([169.254.2.70]) by HT01.win.uni-due.de ([132.252.190.233]) with mapi id 14.03.0210.002; Wed, 26 Nov 2014 11:23:19 +0100
From: "Becke, Martin" <martin.becke@uni-due.de>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "michael.tuexen@lurchi.franken.de" <michael.tuexen@lurchi.franken.de>
Thread-Topic: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
Thread-Index: AQHP84DRDtBde8o0EkqP4662Lb1M95xx687NgADv9UE=
Date: Wed, 26 Nov 2014 10:23:19 +0000
Message-ID: <A33D17830EBE774E8AEFAED600DD54E20180066A29@ccr02.win.uni-due.de>
References: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk>, <A33D17830EBE774E8AEFAED600DD54E20180066A0A@ccr02.win.uni-due.de>
In-Reply-To: <A33D17830EBE774E8AEFAED600DD54E20180066A0A@ccr02.win.uni-due.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [132.252.185.216]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Virus-Scanned: Clam Anti Virus - http://www.clamav.net
X-Spam-Scanned: SpamAssassin: 3.002004 - http://www.spamassassin.org
X-Scanned-By: MIMEDefang 2.57 on 132.252.185.16
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/FoCO0SpCrSnrX8YcZH-nPwpV7M0
Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Nov 2014 10:24:52 -0000

Hi, =0A=
=0A=
2014-11-26 9:27 GMT+01:00 Michael Tuexen <Michael.Tuexen@lurchi.franken.de>=
:=0A=
On 25 Nov 2014, at 20:53, Becke, Martin <martin.becke@uni-due.de> wrote:=0A=
=0A=
> Hi all,=0A=
>=0A=
> I read the draft and I still think the algorithm described is functional =
and useful. I like the idea to introduce a potentially failed state (PF) to=
 optimize the send process.=0A=
>=0A=
> I have only some questions/comments (No editorial comments, perhaps a nat=
ive speaker can check the text, too):=0A=
>=0A=
> - Perhaps the authors can give me a hint why it should be RECOMMENDED  to=
 set the PFMR value to 0 when Quick Failover is used.  I would expect a val=
ue > 0 when it is used and 0 when it is not(!) used.=0A=
> Because it is not a flag controlling the usage of Quick Failover, but a t=
hreshold. See second item=0A=
> in the enumeration in Section 4.2.=0A=
=0A=
Yes, exact. I only wonder why the threshold is not used as control flag, to=
o.=0A=
FMPOV there is no difference for the algorithm if the threshold PFMR has an=
other interpretation. =0A=
Instead defining the trigger with the event error counter > threshold it mi=
ght be a alternative to define the trigger with threshold =3D error counter=
. =0A=
Thus the PFMR can be used as control flag, too. This has the benefit, that =
the Quick Failover is always deactivated by 0, even if the PMR will be re=
=DFconfigured over the time (increased so that PFMR<PMR). =0A=
=0A=
Best regards=0A=
Martin=0A=
>=0A=
> - I think the term =93multiple destinations=94 irritates.  Perhaps you ca=
n use =93destination addresses=94 or =93addresses=94 instead=94.  FMPOV the=
 use of the term =93destination=94 in this draft is inaccurate.  In general=
 the terms path, destination, destination address are very mixed for my fee=
ling. Perhaps this can be rechecked.=0A=
>=0A=
> - =93Heartbeats SHOULD be sent to PF destination(s) once per RTO. This me=
ans the sender MUST ignore HB.interval for PF destinations.=94=0A=
>=0A=
> This sounds strange to me. Why is SHOULD used here and what are the alter=
natives, when I MUST ignore HB.interval for PF destinations. I guess a reph=
rase of this two lines can help.=0A=
>=0A=
> - A link is missing in Section 5.1: [RFC6458] defines the constants SCTP_=
ADDR_AVAILABLE,=85.=0A=
>=0A=
> Best=0A=
> ________________________________________=0A=
> Von: tsvwg [tsvwg-bounces@ietf.org]&quot; im Auftrag von &quot;gorry@erg.=
abdn.ac.uk [gorry@erg.abdn.ac.uk]=0A=
> Gesendet: Mittwoch, 29. Oktober 2014 15:01=0A=
> An: tsvwg@ietf.org=0A=
> Cc: gorry@erg.abdn.ac.uk=0A=
> Betreff: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude=
 19th November, 2014=0A=
>=0A=
> TSVWG,=0A=
>=0A=
> This is the start of a WGLC on "Quick Failover Algorithm in SCTP".=0A=
> https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08=0A=
>=0A=
> This WGLC will last until Wednesday, 19th November, 2014, this includes=
=0A=
> the period of the coming IETF meeting.=0A=
>=0A=
> A good note to the list is "I have read this version of the draft,=0A=
> and I approve (or support) its progression to RFC". The chairs=0A=
> request notes to the list showing support to get a sense of the WG.=0A=
>=0A=
> Of course, you can ask for alternate text (where you supply the=0A=
> actual replacement text, or convey the meaning sufficiently to the=0A=
> authors) for anywhere in the document that you find unclear or troublesom=
e.=0A=
>=0A=
> James/Gorry/David=0A=
> TSVWG chairs=0A=
>=0A=
>=0A=
>=0A=
=0A=
=0A=


From nobody Wed Nov 26 04:34:50 2014
Return-Path: <dromasca@avaya.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D82C1A1BBC; Wed, 26 Nov 2014 04:34:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eO2EEnAeZHJC; Wed, 26 Nov 2014 04:34:45 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8E3A1A010C; Wed, 26 Nov 2014 04:34:44 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlsFAInIdVSHCzIm/2dsb2JhbABbgkIhIyIwW7QEAQEBAQEBBpNmHQGGVgKBCxYBAQEBAQF8hAQBAQMSG0wSARUVFkAmAQQODRqIHgGwd6B1AQEBAQYBAQEBAQEBG4Y3iWwBJjGCPg9EJIEfBZJjhziNFo5ng3yBfQEfIoECAQEB
X-IronPort-AV: E=Sophos; i="5.07,462,1413259200"; d="scan'208,217"; a="82170074"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by de307622-de-outbound.net.avaya.com with ESMTP; 26 Nov 2014 07:34:10 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 26 Nov 2014 07:33:56 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Wed, 26 Nov 2014 13:33:55 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "ops-dir@ietf.org" <ops-dir@ietf.org>
Thread-Topic: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
Thread-Index: AdAJdT0umfZFzhEDQ36ooszawUNr3Q==
Date: Wed, 26 Nov 2014 12:33:54 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C912939AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/wtUSRhgFWxcXfkDzIRvEHgi122s
Cc: "draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: [tsvwg] OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Nov 2014 12:34:48 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C912939AZFFEXMB04globa_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have reviewed this document as part of the Operational directorate's ongo=
ing effort to review all IETF documents being processed by the IESG.  These=
 comments  were written primarily for the benefit of the operational area d=
irectors.  Document editors and WG chairs should treat these comments just =
like any other last call comments.

Summary: Ready with issues

Document Ready, but Operational and Management considerations missing.

As the Abstract says:


   This document defines two additional policies for the Partial
   Reliability Extension of the Stream Control Transmission Protocol
   (PR-SCTP) allowing to limit the number of retransmissions or to
   prioritize user messages for more efficient send buffer usage.
Although this document defines an extension of an existing protocol, there =
are no explicit considerations about operations and management. The OPS and=
 Transport ADs should decide whether this is an issue to be addressed befor=
e the document is approved.

Specifically, following the checklists in RFC 5707, Appendix A:


-       Deployment is not discussed, although there is text that says that =
the Limited Retransmissions Policy can be used with data channels in the We=
bRTC protocol stack, and that the Priority Policy can be used in the IPFIX =
protocol stack

-       Installation and initial setup is not discussed

-       Migration Path does not seem to apply

-       There is information about RFC 3758 being mandatory to implement in=
 order to implement these extensions

-       The impact on the network operation is not discussed explicitly

-       There are no explicit suggestions about verifying correct operation=
s, although one can understand that the socket options described in section=
s 4.3, 4.4, 4.5 are useful to determine stream specific status, association=
 specific status, and to get and set the PR-SCTP support

-       Interoperability does not seem to apply excepting the requirement t=
o implement RFC 3758

-       There is no information about faults or threshold conditions to be =
reported

-       Configuration is not discussed, it may not apply, but it would be g=
ood to state this

-       There are no manageability considerations of any kind



One terminology issue is worth being considered: The document speaks about =
two additional policies for PR-SCTP. However, the RFC defining PR-SCTP (RFC=
 3758) does not use the term policy at all. Timed Reliability which in this=
 document is called a 'policy' is described in RFC 3758 as a 'service to up=
per layer'. It would be good to either align terminology, or to explain tha=
t the term policy used here corresponds to the 'service' described in RFC 3=
758.


Regards,

Dan


--_000_9904FB1B0159DA42B0B887B7FA8119CA5C912939AZFFEXMB04globa_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:168176457;
	mso-list-type:hybrid;
	mso-list-template-ids:-1316174570 -1790792206 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Arial","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1881669766;
	mso-list-type:hybrid;
	mso-list-template-ids:1945509282 1167750956 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<div style=3D"mso-element:para-border-div;border:solid #D7D7D7 1.0pt;paddin=
g:3.0pt 3.0pt 3.0pt 3.0pt;background:#F7F7F7;margin-left:31.2pt;margin-righ=
t:25.8pt">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:12.0pt;margin-right:0cm;=
margin-bottom:12.0pt;margin-left:0cm;background:#F7F7F7;border:none;padding=
:0cm">
<span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:b=
lack">I have reviewed this document as part of the Operational directorate'=
s ongoing effort to review all IETF documents being processed by the IESG.&=
nbsp; These comments &nbsp;were written primarily for the benefit
 of the operational area directors.&nbsp; Document editors and WG chairs sh=
ould treat these comments just like any other last call comments.<o:p></o:p=
></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Summary: Ready with issues
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Document Ready, but Operational and Management considerati=
ons missing.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">As the Abstract says:
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">&nbsp;&nbsp; This document defines two=
 additional policies for the Partial<br>
&nbsp;&nbsp; Reliability Extension of the Stream Control Transmission Proto=
col<br>
&nbsp;&nbsp; (PR-SCTP) allowing to limit the number of retransmissions or t=
o<br>
&nbsp;&nbsp; prioritize user messages for more efficient send buffer usage.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Although this document defines an extension of an existing=
 protocol, there are no explicit considerations about operations and manage=
ment. The OPS and Transport ADs should decide whether this
 is an issue to be addressed before the document is approved. <o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Specifically, following the checklists in RFC 5707, Append=
ix A:
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<span styl=
e=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Deployme=
nt is not discussed, although there is text that says that the Limited Retr=
ansmissions Policy can be used with data channels in the
 WebRTC protocol stack, and that the Priority Policy can be used in the IPF=
IX protocol stack<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<span styl=
e=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Installa=
tion and initial setup is not discussed<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<span styl=
e=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Migratio=
n Path does not seem to apply<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<span styl=
e=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">There is=
 information about RFC 3758 being mandatory to implement in order to implem=
ent these extensions<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<span styl=
e=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">The impa=
ct on the network operation is not discussed explicitly<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<span styl=
e=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">There ar=
e no explicit suggestions about verifying correct operations, although one =
can understand that the socket options described in sections
 4.3, 4.4, 4.5 are useful to determine stream specific status, association =
specific status, and to get and set the PR-SCTP support<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<span styl=
e=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Interope=
rability does not seem to apply excepting the requirement to implement RFC =
3758
<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<span styl=
e=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">There is=
 no information about faults or threshold conditions to be reported<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<span styl=
e=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Configur=
ation is not discussed, it may not apply, but it would be good to state thi=
s<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<span styl=
e=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">There ar=
e no manageability considerations of any kind<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">One terminology issue is worth being c=
onsidered: The document speaks about two additional policies for PR-SCTP. H=
owever, the RFC defining PR-SCTP (RFC 3758) does not use
 the term policy at all. Timed Reliability which in this document is called=
 a &#8216;policy&#8217; is described in RFC 3758 as a &#8216;service to upp=
er layer&#8217;. It would be good to either align terminology, or to explai=
n that the term policy used here corresponds to the &#8216;service&#8217;
 described in RFC 3758.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Dan<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C912939AZFFEXMB04globa_--


From nobody Wed Nov 26 07:17:27 2014
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D22651A020B for <tsvwg@ietfa.amsl.com>; Wed, 26 Nov 2014 07:17:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.961
X-Spam-Level: 
X-Spam-Status: No, score=-0.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_28=0.6, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WvLNEai-VVGv for <tsvwg@ietfa.amsl.com>; Wed, 26 Nov 2014 07:17:23 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAD2B1A0203 for <tsvwg@ietf.org>; Wed, 26 Nov 2014 07:17:22 -0800 (PST)
Received: from [192.168.1.102] (p508F1C5D.dip0.t-ipconnect.de [80.143.28.93]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 142DF1C104615; Wed, 26 Nov 2014 16:17:19 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <A33D17830EBE774E8AEFAED600DD54E20180066A29@ccr02.win.uni-due.de>
Date: Wed, 26 Nov 2014 16:17:18 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D27AC707-5E7C-40E7-9456-FB40CF3A5507@lurchi.franken.de>
References: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk>, <A33D17830EBE774E8AEFAED600DD54E20180066A0A@ccr02.win.uni-due.de> <A33D17830EBE774E8AEFAED600DD54E20180066A29@ccr02.win.uni-due.de>
To: Martin Becke <martin.becke@uni-due.de>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/e2-wx_D-pdKFROpF-S39ThJkF8w
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Nov 2014 15:17:25 -0000

On 26 Nov 2014, at 11:23, Becke, Martin <martin.becke@uni-due.de> wrote:

> Hi,=20
>=20
> 2014-11-26 9:27 GMT+01:00 Michael Tuexen =
<Michael.Tuexen@lurchi.franken.de>:
> On 25 Nov 2014, at 20:53, Becke, Martin <martin.becke@uni-due.de> =
wrote:
>=20
>> Hi all,
>>=20
>> I read the draft and I still think the algorithm described is =
functional and useful. I like the idea to introduce a potentially failed =
state (PF) to optimize the send process.
>>=20
>> I have only some questions/comments (No editorial comments, perhaps a =
native speaker can check the text, too):
>>=20
>> - Perhaps the authors can give me a hint why it should be RECOMMENDED =
 to set the PFMR value to 0 when Quick Failover is used.  I would expect =
a value > 0 when it is used and 0 when it is not(!) used.
>> Because it is not a flag controlling the usage of Quick Failover, but =
a threshold. See second item
>> in the enumeration in Section 4.2.
>=20
> Yes, exact. I only wonder why the threshold is not used as control =
flag, too.
> FMPOV there is no difference for the algorithm if the threshold PFMR =
has another interpretation.=20
> Instead defining the trigger with the event error counter > threshold =
it might be a alternative to define the trigger with threshold =3D error =
counter.=20
This is for consistency with the usage of thresholds in other cases. We =
always use
the the counter exceeds the threshold, then do...
> Thus the PFMR can be used as control flag, too. This has the benefit, =
that the Quick Failover is always deactivated by 0, even if the PMR will =
be re=DFconfigured over the time (increased so that PFMR<PMR).=20
This is what we use in FreeBSD to disable quick failover per default:
net.inet.sctp.path_rtx_max: 5
net.inet.sctp.path_pf_threshold: 65535
Whatever value you configure PMR to, quick failover is off.

Best regards
Michael
>=20
> Best regards
> Martin
>>=20
>> - I think the term =93multiple destinations=94 irritates.  Perhaps =
you can use =93destination addresses=94 or =93addresses=94 instead=94.  =
FMPOV the use of the term =93destination=94 in this draft is inaccurate. =
 In general the terms path, destination, destination address are very =
mixed for my feeling. Perhaps this can be rechecked.
>>=20
>> - =93Heartbeats SHOULD be sent to PF destination(s) once per RTO. =
This means the sender MUST ignore HB.interval for PF destinations.=94
>>=20
>> This sounds strange to me. Why is SHOULD used here and what are the =
alternatives, when I MUST ignore HB.interval for PF destinations. I =
guess a rephrase of this two lines can help.
>>=20
>> - A link is missing in Section 5.1: [RFC6458] defines the constants =
SCTP_ADDR_AVAILABLE,=85.
>>=20
>> Best
>> ________________________________________
>> Von: tsvwg [tsvwg-bounces@ietf.org]&quot; im Auftrag von =
&quot;gorry@erg.abdn.ac.uk [gorry@erg.abdn.ac.uk]
>> Gesendet: Mittwoch, 29. Oktober 2014 15:01
>> An: tsvwg@ietf.org
>> Cc: gorry@erg.abdn.ac.uk
>> Betreff: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To =
conclude 19th November, 2014
>>=20
>> TSVWG,
>>=20
>> This is the start of a WGLC on "Quick Failover Algorithm in SCTP".
>> https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08
>>=20
>> This WGLC will last until Wednesday, 19th November, 2014, this =
includes
>> the period of the coming IETF meeting.
>>=20
>> A good note to the list is "I have read this version of the draft,
>> and I approve (or support) its progression to RFC". The chairs
>> request notes to the list showing support to get a sense of the WG.
>>=20
>> Of course, you can ask for alternate text (where you supply the
>> actual replacement text, or convey the meaning sufficiently to the
>> authors) for anywhere in the document that you find unclear or =
troublesome.
>>=20
>> James/Gorry/David
>> TSVWG chairs
>>=20
>>=20
>>=20
>=20
>=20
>=20

