
From nobody Mon Jun  1 02:15:28 2015
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 8FA561A90D1 for <tsvwg@ietfa.amsl.com>; Mon,  1 Jun 2015 02:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.52
X-Spam-Level: 
X-Spam-Status: No, score=0.52 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 umColCwkHlD0 for <tsvwg@ietfa.amsl.com>; Mon,  1 Jun 2015 02:15:25 -0700 (PDT)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 023F41A90D0 for <tsvwg@ietf.org>; Mon,  1 Jun 2015 02:15:24 -0700 (PDT)
Received: by igbjd9 with SMTP id jd9so56388682igb.1 for <tsvwg@ietf.org>; Mon, 01 Jun 2015 02:15:24 -0700 (PDT)
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=9DB3yMtgMWfah3MsChqCQxQZDPOvM9d/d0u0luz01/k=; b=dwandKqoaGYDis9ZR4AZmqm35pYRpSThVZmIGqWiC/cYCpuefQJBPeMqqjyWYRM953 JbN7td0JcVfaG8UwT0g/DllHsSCNp4AXiJfy1oBhm9YMbKugAg9o8o6bx3t1ZXWDoMQs csOBDa82kgxecqcvtAe5tz9AVEM6/c8IFChqc=
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=9DB3yMtgMWfah3MsChqCQxQZDPOvM9d/d0u0luz01/k=; b=LJtEniGI6URw86M17mc4YI8Xl1OdQDOUTVtGo/nQy84Ri0wI/k9aY5cxjwtvahuiJH E+X2tHqNO48Hn51u6e7cc6WooS3mDLKuakEGtZaLhwt3rRAwgda9Pay6pbGShYZj3l92 T4tDuFVUk2GmWl9eioAe2BvDubsDcHbvFyFjY6ExehKYTRAy25hEtS6R9QDRy9B23ak/ XQDgQufzcr+r6eeGwrA/aRxBBwVGhtvPjuod3FzB+QUPt67UKBk5bQUKazMu/REltBML s1T3I9yr/5pmPrSsczNVpRUTpgKquTgsmF3LaA3oPlmFaa/qthyGfLdlzkAZ/2AwGMmC UhSA==
X-Gm-Message-State: ALoCoQm4pMKnsRcUbDGVQTPwbkZrQtCFQ7rDxwE87MHKZ/4ObpYLHhF91XFoafMj7HoWgrNpfaUwZo4bA3d2gkgCsRp3pk7IM2GWRFMCRq4nArj1JBnb18o=
X-Received: by 10.50.79.196 with SMTP id l4mr12225183igx.48.1433150123922; Mon, 01 Jun 2015 02:15:23 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <882B8BE8-D02D-4E46-90B0-FE9CB2E88BF9@telecom-bretagne.eu> <655C07320163294895BBADA28372AF5D483AF02D@FR712WXCHMBA15.zeu.alcatel-lucent.com>
In-Reply-To: <655C07320163294895BBADA28372AF5D483AF02D@FR712WXCHMBA15.zeu.alcatel-lucent.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQL7VJwomcXY3mf3wZzSms+lgcAi+gFhiVv/mzbD6AA=
Date: Mon, 1 Jun 2015 11:15:23 +0200
Message-ID: <cc09d18c32d3d31d456c3c933e6a1f41@mail.gmail.com>
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>, per.hurtig@kau.se,  anna.brunstrom@kau.se, apetlund@simula.no, michawe@ifi.uio.no
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/HooKryhEwrt8Eur5cbdnHamRCrg>
Cc: tcpm@ietf.org, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] [tcpm] draft-ietf-tcpm-rtorestart-07
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: Mon, 01 Jun 2015 09:15:27 -0000

Hi,

Please accept the following - overdue - comments:

General comments on SCTP applicability of the specification:
---------------------------------------------------------------------------=
---

The document is inconsistent in its description of the SCTP aspects
of the proposed algorithm.

Section 1 and general:

The document does say, in the end of Section 1, that the focus of the
document is on TCP "with validity also for SCTP".
However if so, then I think this paragraph should have been the first
paragraph in section 1 rather than the last.
I think that it is confusing that the Abstract (and the title) speaks about
TCP and SCTP, but the introduction text speaks about TCP only.

I think that it would be better for the text of section 1 to be augmented t=
o
speak about TCP _&_ SCTP. With the final paragraph
then telling that in the remaining part of the documents, the focus would b=
e
on TCP (if this is the intend).

(We have the SCTP API section in the end. Not sure how this fits with the
notion of only providing details for TCP)

Alternatively, if the present "TCP only" introduction is kept, I think that
it would be relevant to emphasize in the final paragraph of section 1, that
what has been described above in section 1, is common to TCP and SCTP
(except possibly for the exact word  "dupacks" - but I think one could get
around that).

Still even with the above clarifications, it is unclear to me what the
status of this document is vis-a-vis SCTP.  The detailed SCTP socket API
description is there,
but some of the crucial implementation aspects - e.g. section 5.3., is TCP
only.

But perhaps such inconsistency is ok for experimental ?

Section 3:

The contents of this section is common to TCP and SCTP except for the term
segment which is TCP particular and which would be a packet in SCTP.

Section 4:

Here there is a reference to "similar update to  RFC4960", but at the same
time the word segment is used and further the section 5.3. discussion is
TCP only.


Detailed on Section 7:
---------------------------
As far as I can tell this is exactly what we would like to have for SCTP.


Thanks,

BR, Karen

PS:  It turns out that some SCTP implementations may send two packets right
after RTO thus applying the "allowed to breach CWND with PMTU-1" logic also
immediately following RTO-timeout. This has impact of how delay_ack impacts
the loss recovery time (refer to discussion in section 5.1).  I believe tha=
t
the intent is to have  this eventually be clarified to be incompliant
behavior (also of SCTP), but SCTP then of course has the option to ask for
immediate SACK in this situation, which then again changes the impact of
delay_ack. There also exist SCTP implementations which rigorously follows
TCP semantics and which thus do not breach the CWND right after RTO (only
after receipt of first ACK after RTO) and which today does not deploy the
Immediate SACK extension. For such the delay_ack impact is the RTO loss
recovery as for TCP. The latter behavior is the right RFC4960 implementatio=
n
(at least I would argue that), but possibly not the "right" future SCTP
implementation.


>-----Original Message-----
>From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Scharf, Michael
>(Michael)
>Sent: Monday, May 18, 2015 11:22 AM
>To: per.hurtig@kau.se; anna.brunstrom@kau.se; apetlund@simula.no;
>michawe@ifi.uio.no
>Cc: tcpm@ietf.org
>Subject: Re: [tcpm] draft-ietf-tcpm-rtorestart-07
>
>Authors,
>
>These (mostly editorial) comments are the only WGLC comments for draft-
>ietf-tcpm-rtorestart-07 that I am aware of. Could you please discuss how t=
o
>address them?
>
>Thanks
>
>Michael
>
>
>
>> -----Original Message-----
>> From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Nicolas Kuhn
>> Sent: Thursday, May 07, 2015 5:00 PM
>> To: tcpm@ietf.org
>> Subject: [tcpm] draft-ietf-tcpm-rtorestart-07
>>
>> Hi all,
>>
>> I had a look at this draft-ietf-tcpm-rtorestart-07 draft.
>> I have some minor comments on the document.
>>
>>
>###########################################################
>##
>>
>> - "The RTO Restart (RTOR) mechanism described in this document makes
>> the
>>    RTO slightly more aggressive when the number of outstanding segments
>>    is too small for fast retransmit to work, in an attempt to enable
>>    faster loss recovery for all segments while being robust to
>>    reordering."
>>
>> The RTO is not aggressive ; but the retransmission scheme ruled by RTO
>> expirations is.
>> I would recommend to rephrase that.
>>
>>
>###########################################################
>##
>>
>> - =E2=80=9C   The RTO Restart (RTOR) mechanism described in this documen=
t makes
>> the
>>    RTO slightly [=E2=80=A6] highly varying RTTs, e.g. mobile networks."
>>
>> This whole paragraph comes to early in the document, as the reader has
>> no clear idea about what RTOR is actually doing. I propose to add that
>> in a dedicated sub- section in Section 5.
>>
>>
>###########################################################
>##
>>
>> - =E2=80=9C 3 RTO Restart Overview=E2=80=9D -> should it not be =E2=80=
=9C3- RTO Overview and
>> rationale of RTOR =E2=80=9C or something equivalent ?
>> It is confusing, as you do not actually present RTOR.
>>
>> Also, in this section 3:
>> The first paragraph finishes with =E2=80=9CHence,  in most situations, t=
he
>> time before a retransmission is triggered is equal to "RTO + RTT=E2=80=
=9D.=E2=80=9D
>> But the example to illustrate it comes after - I think things should
>> moved around to:
>> 1- introduce the classic RTO
>> 2- explain the rationale of classic RTO
>> 3- example to show that RTO+RTT is common
>> 4- more parameters could affect that (2 outstanding segments; other
>> factors)
>> 5- conclusion on =E2=80=9Chence, RTO+RTT is common for application limit=
ed
>> traffic"
>>
>> I would propose to introduce a ToC for this section 3:
>>
>> 3- RTO Overview and rationale of RTOR
>>   3-1. Experienced RTO is RTO+RTT
>>   3-2. RTO safety margin
>>   3-3. Rationale of RTOR: when fast retransmit is not possible
>>
>>
>###########################################################
>##
>>
>> Section 4 : should focus on the description of the algorithm only.
>>
>> I would keep
>> =E2=80=9C
>> This approach makes the RTO more
>>    aggressive than the standardized approach in [RFC6298] but still
>>    conforms to the requirement in [RFC6298] that segments must not be
>>    retransmitted earlier than RTO seconds after their original
>>    transmission.
>> "
>>
>> for the discussion section (at this stage of the reading, the reader
>> still does not know exactly what RTOR is actually doing).
>>
>>
>###########################################################
>##
>>
>> Section 4: "it will prevent RTOR
>>    from being more aggressive and potentially causing RTOs instead of
>>    fast retransmits.=E2=80=9D
>>
>> More aggressive than what ? Has the "four" being experimentally
>> obtained ?
>> I think more discussion is required on this parameter.
>>
>> Regards,
>>
>> Nicolas
>> _______________________________________________
>> tcpm mailing list
>> tcpm@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcpm
>_______________________________________________
>tcpm mailing list
>tcpm@ietf.org
>https://www.ietf.org/mailman/listinfo/tcpm


From nobody Mon Jun  1 04:34:12 2015
Return-Path: <lars@netapp.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 285B41A0113 for <tsvwg@ietfa.amsl.com>; Mon,  1 Jun 2015 04:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.511
X-Spam-Level: 
X-Spam-Status: No, score=-5.511 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_HI=-5, 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 pJT7uD-7L1iH for <tsvwg@ietfa.amsl.com>; Mon,  1 Jun 2015 04:34:07 -0700 (PDT)
Received: from mx143.netapp.com (mx143.netapp.com [216.240.21.24]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D19081A00EE for <tsvwg@ietf.org>; Mon,  1 Jun 2015 04:34:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.13,532,1427785200"; d="scan'208";a="45317189"
Received: from hioexcmbx02-prd.hq.netapp.com ([10.122.105.35]) by mx143-out.netapp.com with ESMTP; 01 Jun 2015 04:33:42 -0700
Received: from HIOEXCMBX01-PRD.hq.netapp.com (10.122.105.34) by hioexcmbx02-prd.hq.netapp.com (10.122.105.35) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Mon, 1 Jun 2015 04:33:41 -0700
Received: from HIOEXCMBX01-PRD.hq.netapp.com ([10.122.105.34]) by hioexcmbx01-prd.hq.netapp.com ([10.122.105.34]) with mapi id 15.00.1076.000; Mon, 1 Jun 2015 04:33:41 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [tsvwg] Review of draft-ietf-tsvwg-rfc5405bis-02.txt
Thread-Index: AQHQfcF7khB0IV5Y40KoUkCu4qu/7Z2YN3IA
Date: Mon, 1 Jun 2015 11:33:40 +0000
Message-ID: <90F4C15A-A48A-4183-9026-5CC0EB71293C@netapp.com>
References: <20150408122559.24328.89341.idtracker@ietfa.amsl.com> <5538E62E.2070404@ericsson.com>
In-Reply-To: <5538E62E.2070404@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.2100)
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.122.56.79]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2AFF389E19E7074B9904410673B20727@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/G8JKQ7XfwYD8vV3mJBSge0Ad4_A>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-rfc5405bis@tools.ietf.org" <draft-ietf-tsvwg-rfc5405bis@tools.ietf.org>
Subject: Re: [tsvwg] Review of draft-ietf-tsvwg-rfc5405bis-02.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: Mon, 01 Jun 2015 11:34:10 -0000

Hi,

sorry it took me so long to get back to this.

On 2015-4-23, at 14:31, Magnus Westerlund <magnus.westerlund@ericsson.com> =
wrote:
> 1. Section 3.1.1:
>=20
>   Applications that support an uncontrolled or unadaptive transmission
>   behavior SHOULD NOT do so by default and SHOULD instead require users
>   to explicitly enable this mode of operation.
>=20
> I think on could add as an alternative to be integrated with resource res=
ervation system so that this mode is only engaged after having been granted=
 the resources.

That is what the text in the same paragraph before the lines you quoted is =
about. Maybe we could be clearer that the guideline above is for transmissi=
on over the wider Internet?

> 2. Section 3.1.2:
>=20
>   Applications that at any time exchange only a few UDP datagrams with
>   a destination SHOULD still control their transmission behavior by not
>   sending on average more than one UDP datagram per round-trip time
>   (RTT) to a destination.
>=20
> In the discussions around the RTP circuit breakers we have found that thi=
s basic rule has a quite significant corner case that we need to discuss. A=
s RTT -> 0, the allowed rate goes to infinity. Now RTT will not go to infin=
ity, but I think we have an potential issue already on a LAN. Assuming a RT=
T of 2 ms, you are allowed to send 500 packets a second. Just by a 1400 byt=
es MSS, that is 5.6 mbps. If you have a lan supporting 9k Ethernet payload,=
 then your supported non-congestion controlled rate becomes 36 mbps. A numb=
er of instances of an application behaving like this will clearly cause iss=
ues in quite a lot of LANs.

Right, but is 5.6Mbps an issue on a LAN? Remember that if there is loss, th=
e calculated RTT will increase, and the rate therefore decrease. When there=
 is no loss and the RTT is 2ms, obviously the LAN can sustain that traffic.=
 (TFTP is basically operating in this way, and doesn't seem to create huge =
issues on LANs.)

> So the issue is really that any application that send sufficient number o=
f packets per seconds also needs to be congestion controlled, even if they =
are of a one packet per RTT type.

Right. There is some text in the beginning of 3.1 that tries to say so:

   It is important to stress that an
   application SHOULD perform congestion control over all UDP traffic it
   sends to a destination, independently from how it generates this
   traffic.  For example, an application that forks multiple worker
   processes or otherwise uses multiple sockets to generate UDP
   datagrams SHOULD perform congestion control over the aggregate
   traffic.

Maybe that's not clear enough?

> This should be clarified, and possibly some guidance on what to frequent =
really is. An application sending 10 packets per seconds to a destination, =
even if only one per RTT clearly can sample the path well enough to have a =
proper CC.

Fair point. Should we then introduce some limit on pps that is considered "=
low data rate" and for everything above that say "use CC"? What limit shoul=
d we pick?

> 3. Section 3.1.3:
>=20
>   Even low data-volume UDP flows may benefit from rate control, e.g.,
>   an application that sends three copies of a packet to improve
>   robustness to loss is RECOMMENDED to pace out those three packets
>   over several RTTs, to reduce the probability that all three packets
>   will be lost due to the same congestion event.
>=20
> I would suggest that one changes "rate control" in the first line of the =
above paragraph to "packet pacing" as that is what being discussed. Usage o=
f rate control is to easily misinterpreted to mean not the packet rate, but=
 also the total bit-rate.

Done, thanks.

> 4. Section 3.1.5:
>=20
>   Applications that support an
>   uncontrolled or unadaptive transmission behavior SHOULD NOT do so by
>   default and SHOULD instead require users to explicitly enable this
>   mode of operation.
>=20
> Same comment as in comment 1 above.

Same answer :-) Should we maybe point to the text in 3.1 or repeat it here?

> 5. Section 3.4:
>=20
>   Application developers SHOULD implement additional checks
>   where data integrity is important, e.g., through a Cyclic Redundancy
>   Check (CRC) included with the data to verify the integrity of an
>   entire object/file sent over the UDP service.
>=20
> I wonder if we should clarify this recommendation on additional checks. I=
 think CRCs are good ways to verify that non-malicous changes has occured t=
o the payload, but CRC may not be appropriate to "entire object/file" where=
 better detection mechanisms may be needed that supports longer object bett=
er. Unless people would use a really long CRC polynom, I think keyed or non=
-keyed cryptographic hashes are more appropriate recommendation for object =
level changes, and if it can be keyed also protect against malicious change=
s.

CRC is given as an example. I'm adding "e.g., through a Cyclic Redundancy C=
heck (CRC) or keyed or non-keyed cryptographic hash included with the data =
to verify the integrity of an entire object/file sent over the UDP service.=
"

> 6. Section 3.5:
>=20
>    When an application is deployed in a
>   controlled network environment, the deployer SHOULD investigate
>   whether the target environment allows applications to use longer
>   intervals, or whether it offers mechanisms to explicitly control
>   middlebox state timeout durations, for example, using Middlebox
>   Communications (MIDCOM) [RFC3303], Next Steps in Signaling (NSIS)
>   [RFC5973], or Universal Plug and Play (UPnP) [UPnP].
>=20
> Add Port Control Protocol to the list?

Done.

> 7. Section 4:
>=20
>   The IETF has defined a reliable multicast framework [RFC3048] and
>   several building blocks to aid the designers of multicast
>   applications, such as [RFC3738] or [RFC4654].  Anycast senders must
>   be aware that successive messages sent to the same anycast IP address
>   may be delivered to different anycast nodes, i.e., arrive at
>   different locations in the topology.
>=20
> I think this paragraph needs to be split into two parts. As the first sen=
tence and the Anycast one appears quite unrelated.

Done.

> 8. Section 6:
>=20
> The IETF standard for securing RTP [RFC3550]
>   communication sessions over UDP is the Secure Real-time Transport
>   Protocol (SRTP) [RFC3711].
>=20
> I think this sentence needs to be changed and primarily reference RFC7201=
. I would rather propose something like:
>=20
> There exist a number of security options for RTP [RFC3550] over UDP, espe=
cially to accomplish key-management, see [RFC7201]. These options covers ma=
ny different usages, including point-to-point, centralized group communicat=
ion as well as multicast.

Changed.

Thanks!

Lars


From nobody Tue Jun  2 02:15:07 2015
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 4F8841B29B4 for <tsvwg@ietfa.amsl.com>; Tue,  2 Jun 2015 02:15:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.46
X-Spam-Level: 
X-Spam-Status: No, score=-2.46 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, 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 tnpZWxdSvq-i for <tsvwg@ietfa.amsl.com>; Tue,  2 Jun 2015 02:15:04 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0B661B29B2 for <tsvwg@ietf.org>; Tue,  2 Jun 2015 02:15:03 -0700 (PDT)
Received: from s4de8nsazdfe010.bmbg.telekom.de ([10.175.246.202]) by tcmail11.telekom.de with ESMTP; 02 Jun 2015 11:15:01 +0200
X-IronPort-AV: E=Sophos;i="5.13,538,1427752800"; d="scan'208";a="681916179"
Received: from he113445.emea1.cds.t-internal.com ([10.134.93.105]) by q4de8nsa015.bmbg.telekom.de with ESMTP/TLS/AES128-SHA; 02 Jun 2015 11:15:01 +0200
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113445.emea1.cds.t-internal.com ([::1]) with mapi; Tue, 2 Jun 2015 11:15:00 +0200
From: <Ruediger.Geib@telekom.de>
To: <swmike@swm.pp.se>
Date: Tue, 2 Jun 2015 11:14:59 +0200
Thread-Topic: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
Thread-Index: AdCaU/OLdEqJx3XJQ52Qa6FOcI3SYACvMxCA
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se>
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/pSys6vhq6lUKCDz9OhWrxYkPe6A>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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, 02 Jun 2015 09:15:06 -0000

Hi Mikael,

thanks for your proposal. Indeed, transport of LE(Scavenger) by a DSCP 000x=
x? at DiffServ-Intercon interfaces was the only suitable solution I imagine=
d myself.

Brian quotes RFC3662 below. Now if an AF class is used to implement LE with=
in a domain, that's still not resulting in a globally non ambiguous DSCP. T=
his may justify a re-write to 000xx0 at a DiffServ-Intercon interface if th=
e latter is enhanced by text at least reserving these DSCPs for LE.=20

There should be no unknown DSCPs with AF like syntax, if DSCPs 000xx0 indic=
ate LE at DiffServ-Intercon interfaces and unknown DSCPs face a rewrite of =
DSCP bits 0-2 to zero (bleaching). Then every unknown AF like DSCP will be =
made LE.=20
I just note that then bleaching removes the necessity to rewrite the AF_DSC=
Ps_used_for_LE at a sending interconnection interface.

Regards,

Ruediger


-----Urspr=FCngliche Nachricht-----
Von: tsvwg [mailto:tsvwg-bounces@ietf.org] Im Auftrag von Mikael Abrahamsso=
n
Gesendet: Freitag, 29. Mai 2015 23:11
An: Brian E Carpenter
Cc: tsvwg@ietf.org
Betreff: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class=
 / CS1

On Sat, 30 May 2015, Brian E Carpenter wrote:

> Firstly, note that RFC 3662 is very intentionally not standards-track=20
> and does not recommend a DSCP value. To me, this discussion seems to=20
> mix up two orthogonal concepts:
>
> 1. What the PHB for a scavenger class actually is (or in Mikael's=20
> suggestion to AQM, what the PHB set is, since mention of priority=20
> implies several members of a PHB set, like AFxy).
>
> 2. What DSCP values happen to be used for this PHB set. Despite the=20
> confusion introduced by RFC 3662, those values don't have to ones=20
> already used for other purposes, especially not CSx. Actually the text=20
> makes it clear that the DSCPs recommended for AFxy should be=20
> considered:
>
>   If a CS PHB is used, note that this configuration will violate the
>   "SHOULD" of section 4.2.2.2 of RFC 2474 [RFC2474] since CS1 will have
>   a less timely forwarding than CS0.  An operator's goal of providing
>   an LE PDB is sufficient cause for violating the SHOULD.  If an AF PHB
>   is used, it must be configured and a DSCP assigned such that it does
>   not violate the "MUST" of paragraph three of section 2 of RFC 2597
>   [RFC2597] which provides for a "minimum amount of forwarding
>   resources".

I was only talking about what the 6 DSCP bits should be for this to ever st=
art to work widely across the Internet. My suggestion is 000xx0 and the rec=
ommendation is to only bleach the first three bits at ISP interconnects ins=
tead of all 6 bits (which is the most commonly done at this time). This is =
backwards compatible with CS0/BE and it's also backwards compatible with de=
fault queuing behaviour when doing automatic IP precedence -> 802.1p and th=
e recommended 4 queue ethernet prioritization (where CS1 and
CS2 is lower than CS0 and CS3).

--=20
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Tue Jun  2 04:44:32 2015
Return-Path: <magnus.westerlund@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 11F4A1B2D32 for <tsvwg@ietfa.amsl.com>; Tue,  2 Jun 2015 04:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 QDFaRaxNgpSC for <tsvwg@ietfa.amsl.com>; Tue,  2 Jun 2015 04:44:28 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F38B1B2D38 for <tsvwg@ietf.org>; Tue,  2 Jun 2015 04:44:27 -0700 (PDT)
X-AuditID: c1b4fb25-f79b66d000001131-13-556d9719f5a7
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 80.73.04401.9179D655; Tue,  2 Jun 2015 13:44:25 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.71) with Microsoft SMTP Server id 14.3.210.2; Tue, 2 Jun 2015 13:44:24 +0200
Message-ID: <556D9717.3050800@ericsson.com>
Date: Tue, 2 Jun 2015 13:44:23 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
References: <20150408122559.24328.89341.idtracker@ietfa.amsl.com> <5538E62E.2070404@ericsson.com> <90F4C15A-A48A-4183-9026-5CC0EB71293C@netapp.com>
In-Reply-To: <90F4C15A-A48A-4183-9026-5CC0EB71293C@netapp.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHLMWRmVeSWpSXmKPExsUyM+Jvra7k9NxQg/v39S1WH5rLaPHidQ+L xbE3d9kcmD2WLPnJ5DHj0xc2jy+XP7MFMEdx2aSk5mSWpRbp2yVwZdxf/Ja9YJZJxabb71kb GM9odjFycEgImEi8vVvaxcgJZIpJXLi3nq2LkYtDSOAoo8SWuTOhnGWMEovmn2EGqeIV0JaY 0LaDHcRmEVCRuD73HZjNJmAhcfNHIxuILSoQJTH18ToWiHpBiZMzn4DZIkD1m+efBqtnFmhh lPh3OwvEFhZwlDh1cT8TxLLJjBIz584HG8QpYCdxv/EwM8ilzAL2Eg+2lkH0yks0b50Ndo8Q 0D0NTR2sExgFZyFZNwuhYxaSjgWMzKsYRYtTi5Ny042M9VKLMpOLi/Pz9PJSSzYxAgP44Jbf qjsYL79xPMQowMGoxMOrwJcbKsSaWFZcmXuIUZqDRUmc17MrJFRIID2xJDU7NbUgtSi+qDQn tfgQIxMHp1QDo+ri70vlDcVL5nqdOGPB17vUqjbZe0+SbYClaKR/6hoBkedzb2ue8Zu4uuBH XN09ndc/J1qziD+/093iszREQ/zPfufoBv46u+yHRok3r/yfUqrDdylE/pi5L6dSY22o3fed RW+1fGbMnhf3g0uAO22CyF6nerFnG7ICFyW/KW0pbeLNiV2gxFKckWioxVxUnAgATVzVEUEC AAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/ESDjFRBwiQOK4ssk6dy3d6_OowQ>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-rfc5405bis@tools.ietf.org" <draft-ietf-tsvwg-rfc5405bis@tools.ietf.org>
Subject: Re: [tsvwg] Review of draft-ietf-tsvwg-rfc5405bis-02.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, 02 Jun 2015 11:44:31 -0000

Hi,

Please see inline. Snipped dealt with issues.

Eggert, Lars skrev den 2015-06-01 13:33:
> Hi,
>
> sorry it took me so long to get back to this.
>
> On 2015-4-23, at 14:31, Magnus Westerlund
> <magnus.westerlund@ericsson.com> wrote:
>> 1. Section 3.1.1:
>>
>> Applications that support an uncontrolled or unadaptive
>> transmission behavior SHOULD NOT do so by default and SHOULD
>> instead require users to explicitly enable this mode of operation.
>>
>> I think on could add as an alternative to be integrated with
>> resource reservation system so that this mode is only engaged after
>> having been granted the resources.
>
> That is what the text in the same paragraph before the lines you
> quoted is about. Maybe we could be clearer that the guideline above
> is for transmission over the wider Internet?

My point is that one can reinforce that if one assumes reserved path 
capacity, one actually needs to ensure it. Just assuming without having 
methods for verifying it is not good.

>
>> 2. Section 3.1.2:
>>
>> Applications that at any time exchange only a few UDP datagrams
>> with a destination SHOULD still control their transmission behavior
>> by not sending on average more than one UDP datagram per round-trip
>> time (RTT) to a destination.
>>
>> In the discussions around the RTP circuit breakers we have found
>> that this basic rule has a quite significant corner case that we
>> need to discuss. As RTT -> 0, the allowed rate goes to infinity.
>> Now RTT will not go to infinity, but I think we have an potential
>> issue already on a LAN. Assuming a RTT of 2 ms, you are allowed to
>> send 500 packets a second. Just by a 1400 bytes MSS, that is 5.6
>> mbps. If you have a lan supporting 9k Ethernet payload, then your
>> supported non-congestion controlled rate becomes 36 mbps. A number
>> of instances of an application behaving like this will clearly
>> cause issues in quite a lot of LANs.
>
> Right, but is 5.6Mbps an issue on a LAN? Remember that if there is
> loss, the calculated RTT will increase, and the rate therefore
> decrease. When there is no loss and the RTT is 2ms, obviously the LAN
> can sustain that traffic. (TFTP is basically operating in this way,
> and doesn't seem to create huge issues on LANs.)

5,6 mbps can clearly be significantly above your fair share. I am also 
worried that you will shave of a factor of 20 from the assumed RTT and 
suddenly you saturate a 100 mbps lan with just that stream. Sure, loss 
equals delay in ack and thus reduced rate. But, please do remember that 
if the RTT and packet size and amount of data to deliver support a 
higher than available bandwidth this protocol will contribute 
substantially to persistent loss as it doesn't tune itself to how much 
it overshoot.

The reason we commented on this, was that in RTP and the circuit breaker 
we don't have the lock step mechanism of TFTP, instead  a loss is just a 
loss. And because the RTT is short the circuit breaker becomes disabled. 
So this is highly dependent on the context and what your bulk transfer 
application is doing.

>
>> So the issue is really that any application that send sufficient
>> number of packets per seconds also needs to be congestion
>> controlled, even if they are of a one packet per RTT type.
>
> Right. There is some text in the beginning of 3.1 that tries to say
> so:
>
> It is important to stress that an application SHOULD perform
> congestion control over all UDP traffic it sends to a destination,
> independently from how it generates this traffic.  For example, an
> application that forks multiple worker processes or otherwise uses
> multiple sockets to generate UDP datagrams SHOULD perform congestion
> control over the aggregate traffic.
>
> Maybe that's not clear enough?

That is not what I am talking about. In my case we have a single process 
sending a single stream of packets. The issue is that one packet per RTT 
is still potentially to much.

>
>> This should be clarified, and possibly some guidance on what to
>> frequent really is. An application sending 10 packets per seconds
>> to a destination, even if only one per RTT clearly can sample the
>> path well enough to have a proper CC.
>
> Fair point. Should we then introduce some limit on pps that is
> considered "low data rate" and for everything above that say "use
> CC"? What limit should we pick?

Yes, this is the difficult, but I think above 50 pps (i.e. one per 20 
ms) is high enough rate that it appears reasonable to require CC.


>
>> 4. Section 3.1.5:
>>
>> Applications that support an uncontrolled or unadaptive
>> transmission behavior SHOULD NOT do so by default and SHOULD
>> instead require users to explicitly enable this mode of operation.
>>
>> Same comment as in comment 1 above.
>
> Same answer :-) Should we maybe point to the text in 3.1 or repeat it
> here?

I think it depends on how big the resulting text is. If small I think 
repeat makes sense, if not reference.

>
>> 5. Section 3.4:
>>
>> Application developers SHOULD implement additional checks where
>> data integrity is important, e.g., through a Cyclic Redundancy
>> Check (CRC) included with the data to verify the integrity of an
>> entire object/file sent over the UDP service.
>>
>> I wonder if we should clarify this recommendation on additional
>> checks. I think CRCs are good ways to verify that non-malicous
>> changes has occured to the payload, but CRC may not be appropriate
>> to "entire object/file" where better detection mechanisms may be
>> needed that supports longer object better. Unless people would use
>> a really long CRC polynom, I think keyed or non-keyed cryptographic
>> hashes are more appropriate recommendation for object level
>> changes, and if it can be keyed also protect against malicious
>> changes.
>
> CRC is given as an example. I'm adding "e.g., through a Cyclic
> Redundancy Check (CRC) or keyed or non-keyed cryptographic hash
> included with the data to verify the integrity of an entire
> object/file sent over the UDP service."

Yes, that looks good.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Wed Jun  3 15:56:13 2015
Return-Path: <paulej@packetizer.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 7169E1A890C for <tsvwg@ietfa.amsl.com>; Wed,  3 Jun 2015 15:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.113
X-Spam-Level: 
X-Spam-Status: No, score=-0.113 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, 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 bK2H98g-rNP2 for <tsvwg@ietfa.amsl.com>; Wed,  3 Jun 2015 15:56:10 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B39961A8A67 for <tsvwg@ietf.org>; Wed,  3 Jun 2015 15:56:10 -0700 (PDT)
Received: from [192.168.1.20] (cpe-098-122-181-215.nc.res.rr.com [98.122.181.215] (may be forged)) (authenticated bits=0) by dublin.packetizer.com (8.14.9/8.14.9) with ESMTP id t53Mu9pi011536 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 3 Jun 2015 18:56:09 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1433372169; bh=4hF+/owVzN+OdZXEsHuOw+rPQUxep6rVBc2xFjNHamE=; h=From:To:Subject:Date:Reply-To; b=MaizBOnD5UH45YvxcICWkpHm1+FlUPFU34OFDjI8sFFsaROqRmrXip4dvZcYPeykF z2pjKINpjvHfEqqZfYMPbuDIjIKTru3zhnhmg16i38GKBg3HdNb7MFKxl90hzc43sL B+CfSqrDZQriGXIaZgJmRK5HVMKEWgacZqmnAx7Y=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Date: Wed, 03 Jun 2015 22:56:23 +0000
Message-Id: <em7b942bb6-735f-4287-9ce1-d76df8f6497d@sydney>
User-Agent: eM_Client/6.0.22344.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/cVu_IAnI5O-ENrT6SXhkGIgLea8>
Subject: [tsvwg] Fw: [apps-discuss] James Polk
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
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, 03 Jun 2015 22:56:12 -0000

For the benefit of those not on the apps-discuss list...

------ Forwarded Message ------
From: "Alissa Cooper" <alissa@cooperw.in>
To: apps-discuss@ietf.org
Sent: 6/2/2015 5:14:42 PM
Subject: [apps-discuss] James Polk

I wanted to let you know that our colleague and friend James Polk passed=
=20
away last week. James participated in the IETF for over a decade. Over=20
the years he made many valuable contributions that spanned the areas,=20
with particular focus on SIP, emergency services, geolocation, and=20
differentiated services. Beyond his technical work, he sought to make=20
improvements in the role of WG chair and the IETF overall. I think we=20
all knew him as a fierce defender of the solutions he believed in who=20
also had a softer side. He will be missed at the IETF and at Cisco.

Please keep James' family in your thoughts.

Alissa
_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss


From nobody Thu Jun  4 02:54:36 2015
Return-Path: <lars@netapp.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 083A21A0025 for <tsvwg@ietfa.amsl.com>; Thu,  4 Jun 2015 02:54:35 -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_50=0.8, RCVD_IN_DNSWL_HI=-5, 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 mIXWi_I5m18E for <tsvwg@ietfa.amsl.com>; Thu,  4 Jun 2015 02:54:32 -0700 (PDT)
Received: from mx143.netapp.com (mx143.netapp.com [216.240.21.24]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A0FE1A0004 for <tsvwg@ietf.org>; Thu,  4 Jun 2015 02:54:32 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.13,552,1427785200";  d="asc'?scan'208";a="45985000"
Received: from hioexcmbx07-prd.hq.netapp.com ([10.122.105.40]) by mx143-out.netapp.com with ESMTP; 04 Jun 2015 02:54:16 -0700
Received: from HIOEXCMBX01-PRD.hq.netapp.com (10.122.105.34) by hioexcmbx07-prd.hq.netapp.com (10.122.105.40) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Thu, 4 Jun 2015 02:54:16 -0700
Received: from HIOEXCMBX01-PRD.hq.netapp.com ([10.122.105.34]) by hioexcmbx01-prd.hq.netapp.com ([10.122.105.34]) with mapi id 15.00.1076.000; Thu, 4 Jun 2015 02:54:16 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [tsvwg] Review of draft-ietf-tsvwg-rfc5405bis-02.txt
Thread-Index: AQHQfcF7khB0IV5Y40KoUkCu4qu/7Z2YN3IAgAGVVICAAwXjAA==
Date: Thu, 4 Jun 2015 09:54:15 +0000
Message-ID: <59AD6DC4-8A6F-4569-905E-78A98DF53367@netapp.com>
References: <20150408122559.24328.89341.idtracker@ietfa.amsl.com> <5538E62E.2070404@ericsson.com> <90F4C15A-A48A-4183-9026-5CC0EB71293C@netapp.com> <556D9717.3050800@ericsson.com>
In-Reply-To: <556D9717.3050800@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.2100)
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.122.56.79]
Content-Type: multipart/signed; boundary="Apple-Mail=_54B06302-8409-4DC2-825F-B87EDE32539F"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/M7cPxJNjqB-6Q_BN2yJgo6Iv7Cs>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-rfc5405bis@tools.ietf.org" <draft-ietf-tsvwg-rfc5405bis@tools.ietf.org>
Subject: Re: [tsvwg] Review of draft-ietf-tsvwg-rfc5405bis-02.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: Thu, 04 Jun 2015 09:54:35 -0000

--Apple-Mail=_54B06302-8409-4DC2-825F-B87EDE32539F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi,

On 2015-6-2, at 14:44, Magnus Westerlund =
<magnus.westerlund@ericsson.com> wrote:
> Eggert, Lars skrev den 2015-06-01 13:33:
>> On 2015-4-23, at 14:31, Magnus Westerlund
>> <magnus.westerlund@ericsson.com> wrote:
>>> 1. Section 3.1.1:
>>>=20
>>> Applications that support an uncontrolled or unadaptive
>>> transmission behavior SHOULD NOT do so by default and SHOULD
>>> instead require users to explicitly enable this mode of operation.
>>>=20
>>> I think on could add as an alternative to be integrated with
>>> resource reservation system so that this mode is only engaged after
>>> having been granted the resources.
>>=20
>> That is what the text in the same paragraph before the lines you
>> quoted is about. Maybe we could be clearer that the guideline above
>> is for transmission over the wider Internet?
>=20
> My point is that one can reinforce that if one assumes reserved path =
capacity, one actually needs to ensure it. Just assuming without having =
methods for verifying it is not good.

ah, got it. I added "and they SHOULD verify that sufficient path =
capacity has been reserved for them" to the end of the last sentence.

>>> 2. Section 3.1.2:
>>>=20
>>> Applications that at any time exchange only a few UDP datagrams
>>> with a destination SHOULD still control their transmission behavior
>>> by not sending on average more than one UDP datagram per round-trip
>>> time (RTT) to a destination.
>>>=20
>>> In the discussions around the RTP circuit breakers we have found
>>> that this basic rule has a quite significant corner case that we
>>> need to discuss. As RTT -> 0, the allowed rate goes to infinity.
>>> Now RTT will not go to infinity, but I think we have an potential
>>> issue already on a LAN. Assuming a RTT of 2 ms, you are allowed to
>>> send 500 packets a second. Just by a 1400 bytes MSS, that is 5.6
>>> mbps. If you have a lan supporting 9k Ethernet payload, then your
>>> supported non-congestion controlled rate becomes 36 mbps. A number
>>> of instances of an application behaving like this will clearly
>>> cause issues in quite a lot of LANs.
>>=20
>> Right, but is 5.6Mbps an issue on a LAN? Remember that if there is
>> loss, the calculated RTT will increase, and the rate therefore
>> decrease. When there is no loss and the RTT is 2ms, obviously the LAN
>> can sustain that traffic. (TFTP is basically operating in this way,
>> and doesn't seem to create huge issues on LANs.)
>=20
> 5,6 mbps can clearly be significantly above your fair share.

Sure, but then there would be loss, and the computed RTT would increase =
and the bandwidth would become reduced.

> I am also worried that you will shave of a factor of 20 from the =
assumed RTT and suddenly you saturate a 100 mbps lan with just that =
stream.

But only for at 1/20th RTT, because after that, you would start seeing =
loss and the rate would reduce.

> Sure, loss equals delay in ack and thus reduced rate. But, please do =
remember that if the RTT and packet size and amount of data to deliver =
support a higher than available bandwidth this protocol will contribute =
substantially to persistent loss as it doesn't tune itself to how much =
it overshoot.

Right. But having one message per RTT outstanding and adapting the RTT =
based on what is measured does tune the rate to the path =
characteristics. It's not great, but it should prevent causing =
persistent congestion.

> The reason we commented on this, was that in RTP and the circuit =
breaker we don't have the lock step mechanism of TFTP, instead  a loss =
is just a loss. And because the RTT is short the circuit breaker becomes =
disabled. So this is highly dependent on the context and what your bulk =
transfer application is doing.

I'm not sure I follow the example here?

>>> So the issue is really that any application that send sufficient
>>> number of packets per seconds also needs to be congestion
>>> controlled, even if they are of a one packet per RTT type.
>>=20
>> Right. There is some text in the beginning of 3.1 that tries to say
>> so:
>>=20
>> It is important to stress that an application SHOULD perform
>> congestion control over all UDP traffic it sends to a destination,
>> independently from how it generates this traffic.  For example, an
>> application that forks multiple worker processes or otherwise uses
>> multiple sockets to generate UDP datagrams SHOULD perform congestion
>> control over the aggregate traffic.
>>=20
>> Maybe that's not clear enough?
>=20
> That is not what I am talking about. In my case we have a single =
process sending a single stream of packets. The issue is that one packet =
per RTT is still potentially to much.

I think this document (silently) assumes that "too much" means "packet =
loss is seen." It seems that in your case, you have a rate that you =
consider "too much", but there is no packet loss yet?

>>> This should be clarified, and possibly some guidance on what to
>>> frequent really is. An application sending 10 packets per seconds
>>> to a destination, even if only one per RTT clearly can sample the
>>> path well enough to have a proper CC.
>>=20
>> Fair point. Should we then introduce some limit on pps that is
>> considered "low data rate" and for everything above that say "use
>> CC"? What limit should we pick?
>=20
> Yes, this is the difficult, but I think above 50 pps (i.e. one per 20 =
ms) is high enough rate that it appears reasonable to require CC.

OK. I personally have no strong view here, if the WG has one. (I do have =
a mild displeasure at having to introduce some magic constant, but I can =
totally live with this if we agree on one.)

WG, what do you think?

Lars

--Apple-Mail=_54B06302-8409-4DC2-825F-B87EDE32539F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAlVwIEYACgkQIWcjmsUTWRq94wCfY9dkK2lu9STgeIWtaucWdKyj
EzIAn0XTxnbA1SbJpf99vgEnE/0h9isC
=Fw4w
-----END PGP SIGNATURE-----

--Apple-Mail=_54B06302-8409-4DC2-825F-B87EDE32539F--


From nobody Thu Jun 11 04:58:29 2015
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 034411ACDC6; Thu, 11 Jun 2015 04:58:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.012
X-Spam-Level: 
X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 1wwKDAqm-2Bg; Thu, 11 Jun 2015 04:58:26 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 3D2341ACDBE; Thu, 11 Jun 2015 04:58:26 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id BA0601B001AB; Thu, 11 Jun 2015 12:58:27 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Thu, 11 Jun 2015 12:57:23 +0100
Message-ID: <22ef29b3a8ed578cdeead82532cd6796.squirrel@erg.abdn.ac.uk>
Date: Thu, 11 Jun 2015 12:57:23 +0100
From: gorry@erg.abdn.ac.uk
To: karen.nielsen@tieto.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/4NFf1T9CeOJG_nmxprDmMri_EiQ>
Cc: tsvwg@ietf.org
Subject: [tsvwg] Finishing: draft-ietf-tsvwg-sctp-failover
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: Thu, 11 Jun 2015 11:58:28 -0000

Karen,

There is some editorial work needed to prepare
draft-ietf-tsvwg-sctp-failover for IESG review. The RFC 2119 usage
generally now looks good. Can I encourage you (Karen) as the document
editor to take the XML and provide the final edits needed to finish this.

I believe the WG was promised it would be sent to the IESG before IETF-93,
which means starting a WGLC in a week or two.

Best wishes,

Gorry & David
(tsvwg co-chairs)

---

As I recall the proposed next steps from the last IETF meeting were:

•  All technical issues raised including standards language, are (believed
to have been) resolved. &#8232;
•  BUT... some re-structuring would still be beneficial, given PS &#8232;
•  Next step would be a -11 revision:
&#8232; – Implement the agreed technical resolutions&#8232; – Still
improve language and some restructuring

Extract from notes of meeting:

          Michael: If the heartbeat is not disabled by the user, then must
            send these faster. If not, then follow the user. If you make the
            text explicit, then OK.
          Michael: There is a change to the security model, it is not only
            faster, but with permanent failover, STCP moves the traffic away
            permanently from the first path if there is a traffic peak.
          Karen: The draft also proposes a mode with permanent switch over,
            we will document the changes and the security implications.
          Gorry: The security section was short, this should address that.
            The abstract should mention the API exists as a separate section.

          Karen: We received comments suggesting we remove the discussion of
            CC - since this document removes this.
          Gorry: I suggest you may leave the text marked "RFC Editor to
Remove",
            so the IETF and IESG knows that CC changes were discussed, and
            that there was consensus that this change was agreed.
          David Black: Please change the lower-case "should" to an "ought
to"¯.

          Karen: We do not think this should update RFC 4960.
          Gorry: First, is implementation optional for a compliant SCTP
stack?
          Karen: Yes, optional
          Gorry: Are you updating the base mechanisms that you expect base
            implementer to read this?
          Randal Stewart: You would not want to update RFC 4960,
            because that would make existing implementations non compliant.
            I do not think this document should update RFC 4960.
          David: Is there a hidden "SHOULD"¯ here?
            Is the text clear that this is based on one way to implement
            RFC4960, but this builds on one specific way to do this.
          Randal: There are reasons that an implementation does not want the
            dormant state specified in the base spec. This is an
            implementation choice needed for this specific spec.
          Chairs: We seem to have agreement this will not update RFC 4960.
&#8232;



From nobody Thu Jun 11 07:29:08 2015
Return-Path: <magnus.westerlund@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 9ED4B1A002A for <tsvwg@ietfa.amsl.com>; Thu, 11 Jun 2015 07:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 LhGxLRjz4mkn for <tsvwg@ietfa.amsl.com>; Thu, 11 Jun 2015 07:29:04 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 097C41A004C for <tsvwg@ietf.org>; Thu, 11 Jun 2015 07:29:03 -0700 (PDT)
X-AuditID: c1b4fb25-f79b66d000001131-66-55799b2d5532
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 14.98.04401.D2B99755; Thu, 11 Jun 2015 16:29:02 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.26) with Microsoft SMTP Server id 14.3.210.2; Thu, 11 Jun 2015 16:29:01 +0200
Message-ID: <55799B2B.5060207@ericsson.com>
Date: Thu, 11 Jun 2015 16:28:59 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
References: <20150408122559.24328.89341.idtracker@ietfa.amsl.com> <5538E62E.2070404@ericsson.com> <90F4C15A-A48A-4183-9026-5CC0EB71293C@netapp.com> <556D9717.3050800@ericsson.com> <59AD6DC4-8A6F-4569-905E-78A98DF53367@netapp.com>
In-Reply-To: <59AD6DC4-8A6F-4569-905E-78A98DF53367@netapp.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrPLMWRmVeSWpSXmKPExsUyM+Jvra7e7MpQg+4ZTBarD81ltHjxuofF 4tibu2wOzB5Llvxk8pjx6Qubx5fLn9kCmKO4bFJSczLLUov07RK4Mr7P2MZS0K9ZsXNqP2sD 4yeFLkZODgkBE4m5B/8xQthiEhfurWfrYuTiEBI4yihxZskLKGc5o0TP1NPMIFW8AtoS/f83 MIHYLAKqErc/r2QFsdkELCRu/mhkA7FFBaIkpj5exwJRLyhxcuYTMFtEQEVi8/zT7CA2s0AL o8S/21kgtrCAo8Spi/uZIJY9ZZQ41bgd7CROATuJpztagRZwADXYSzzYWgbRKy/RvHU22D1C QPc0NHWwTmAUnIVk3SyEjllIOhYwMq9iFC1OLU7KTTcy1kstykwuLs7P08tLLdnECAzhg1t+ q+5gvPzG8RCjAAejEg/vgtcVoUKsiWXFlbmHGKU5WJTEeWdszgsVEkhPLEnNTk0tSC2KLyrN SS0+xMjEwSnVwCinfEh7/g7TyZ9/7DkY4P1k3bOO11vY5l4v3RHsF9G6gKsvtDHcL43lvff5 SdfPLVhUnR3Euj9+y/bXpVs3WTIy+bzWWxKvmx5Trhn7/cPLyO33D52ZtzJ4y5usS4+9ZYTn KL8vLvpzYI3oP83tS6ZOsN7FWGSj+2d9l2r51wMrQtgK4xccWzVBiaU4I9FQi7moOBEAQlO7 OEICAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/zyllpRBUI_omZo8cFCTVsZLaIXQ>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-rfc5405bis@tools.ietf.org" <draft-ietf-tsvwg-rfc5405bis@tools.ietf.org>
Subject: Re: [tsvwg] Review of draft-ietf-tsvwg-rfc5405bis-02.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: Thu, 11 Jun 2015 14:29:06 -0000

Eggert, Lars skrev den 2015-06-04 11:54:
> On 2015-6-2, at 14:44, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
>> Eggert, Lars skrev den 2015-06-01 13:33:
>>> On 2015-4-23, at 14:31, Magnus Westerlund
>>> <magnus.westerlund@ericsson.com> wrote:

>>>> 1. Section 3.1.1:

> ah, got it. I added "and they SHOULD verify that sufficient path
> capacity has been reserved for them" to the end of the last
> sentence.

Great!

>
>>>> 2. Section 3.1.2:
>>>>
>>>> Applications that at any time exchange only a few UDP datagrams
>>>> with a destination SHOULD still control their transmission behavior
>>>> by not sending on average more than one UDP datagram per round-trip
>>>> time (RTT) to a destination.
>>>>
>>>> In the discussions around the RTP circuit breakers we have found
>>>> that this basic rule has a quite significant corner case that we
>>>> need to discuss. As RTT -> 0, the allowed rate goes to infinity.
>>>> Now RTT will not go to infinity, but I think we have an potential
>>>> issue already on a LAN. Assuming a RTT of 2 ms, you are allowed to
>>>> send 500 packets a second. Just by a 1400 bytes MSS, that is 5.6
>>>> mbps. If you have a lan supporting 9k Ethernet payload, then your
>>>> supported non-congestion controlled rate becomes 36 mbps. A number
>>>> of instances of an application behaving like this will clearly
>>>> cause issues in quite a lot of LANs.
>>>
>>> Right, but is 5.6Mbps an issue on a LAN? Remember that if there is
>>> loss, the calculated RTT will increase, and the rate therefore
>>> decrease. When there is no loss and the RTT is 2ms, obviously the LAN
>>> can sustain that traffic. (TFTP is basically operating in this way,
>>> and doesn't seem to create huge issues on LANs.)
>>
>> 5,6 mbps can clearly be significantly above your fair share.
>
> Sure, but then there would be loss, and the computed RTT would
increase and the bandwidth would become reduced.

Assuming that they either have lock step mechanism or samples frequently 
the RTT. If one has infrequent RTT sampling, then the sampled RTT may 
not reflect the congested state, and thus provide no help in detecting 
the congestion occurance, thus no back off.

>
>> I am also worried that you will shave of a factor of 20 from the
assumed RTT and suddenly you saturate a 100 mbps lan with just that stream.
>
> But only for at 1/20th RTT, because after that, you would start
> seeingloss and the rate would reduce.
>
>> Sure, loss equals delay in ack and thus reduced rate. But, please
>> doremember that if the RTT and packet size and amount of data to deliver
>> support a higher than available bandwidth this protocol will contribute
 >> substantially to persistent loss as it doesn't tune itself to how
 >> much it overshoot.
>
> Right. But having one message per RTT outstanding and adapting the
> RTT
based on what is measured does tune the rate to the path
characteristics. It's not great, but it should prevent causing
persistent congestion.

Sure, if you actually have a method that really ensures that it has one 
and only one packet outstanding and then an accurate enough RTT 
estimator to deal with any re-transmissions then it is self limiting.

>
>> The reason we commented on this, was that in RTP and the circuit
breaker we don't have the lock step mechanism of TFTP, instead a loss is
just a loss. And because the RTT is short the circuit breaker becomes
disabled. So this is highly dependent on the context and what your bulk
transfer application is doing.
>
> I'm not sure I follow the example here?

I think you need to look at Section 4.1 of 
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/

That draft derives from the UDP guidelines that we basically turn off 
the forward path circuit breaker if less than one RTP packet per RTT 
where sent. The RTT sampling is done using RTCP, so it may be as 
infrequent as on average every 5 seconds.

The intention with turning the circuit breaker off if so that when 
transmission of RTP packets are infrequent as single or very small 
number of packet losses should not trigger the circuit breaker.

So basically we have turned the one 1 per RTT rule into a fence that 
actually allows quite high rates. And due to how the measurements are 
done it is insensitive to congestion events.

What I think may be needed in the UDP guidelines is to clarify that if 
one applies the no more than one per RTT, that actually have to do 
frequent sampling, or be some lock step protocol which thus would be 
self limiting in the face of congestion.

It is not okay to apply once per RTT as a rule of thumb.

(Damm, I hate it when I make it more difficult for myself)

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Jun 11 08:43:29 2015
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 D567D1B2B5D for <tsvwg@ietfa.amsl.com>; Thu, 11 Jun 2015 08:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.611
X-Spam-Level: 
X-Spam-Status: No, score=-3.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_81=0.6, 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 7tJQGTVpYOSm for <tsvwg@ietfa.amsl.com>; Thu, 11 Jun 2015 08:43:25 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 335A01B2B5C for <tsvwg@ietf.org>; Thu, 11 Jun 2015 08:43:25 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 57E711B001C5; Thu, 11 Jun 2015 16:43:25 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Thu, 11 Jun 2015 16:42:22 +0100
Message-ID: <76313ab743052d8b51bed61e232bf791.squirrel@erg.abdn.ac.uk>
In-Reply-To: <55799B2B.5060207@ericsson.com>
References: <20150408122559.24328.89341.idtracker@ietfa.amsl.com> <5538E62E.2070404@ericsson.com> <90F4C15A-A48A-4183-9026-5CC0EB71293C@netapp.com> <556D9717.3050800@ericsson.com> <59AD6DC4-8A6F-4569-905E-78A98DF53367@netapp.com> <55799B2B.5060207@ericsson.com>
Date: Thu, 11 Jun 2015 16:42:22 +0100
From: gorry@erg.abdn.ac.uk
To: "Magnus Westerlund" <magnus.westerlund@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/tkzKyDleyhqFPCUT1OTnmxIqHJQ>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-rfc5405bis@tools.ietf.org" <draft-ietf-tsvwg-rfc5405bis@tools.ietf.org>
Subject: Re: [tsvwg] Review of draft-ietf-tsvwg-rfc5405bis-02.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: Thu, 11 Jun 2015 15:43:28 -0000

See a thought at the end.

> Eggert, Lars skrev den 2015-06-04 11:54:
>> On 2015-6-2, at 14:44, Magnus Westerlund
>> <magnus.westerlund@ericsson.com> wrote:
>>> Eggert, Lars skrev den 2015-06-01 13:33:
>>>> On 2015-4-23, at 14:31, Magnus Westerlund
>>>> <magnus.westerlund@ericsson.com> wrote:
>
>>>>> 1. Section 3.1.1:
>
>> ah, got it. I added "and they SHOULD verify that sufficient path
>> capacity has been reserved for them" to the end of the last
>> sentence.
>
> Great!
>
WFM also.
>>
>>>>> 2. Section 3.1.2:
>>>>>
>>>>> Applications that at any time exchange only a few UDP datagrams
>>>>> with a destination SHOULD still control their transmission behavior
>>>>> by not sending on average more than one UDP datagram per round-trip
>>>>> time (RTT) to a destination.
>>>>>
>>>>> In the discussions around the RTP circuit breakers we have found
>>>>> that this basic rule has a quite significant corner case that we
>>>>> need to discuss. As RTT -> 0, the allowed rate goes to infinity.
>>>>> Now RTT will not go to infinity, but I think we have an potential
>>>>> issue already on a LAN. Assuming a RTT of 2 ms, you are allowed to
>>>>> send 500 packets a second. Just by a 1400 bytes MSS, that is 5.6
>>>>> mbps. If you have a lan supporting 9k Ethernet payload, then your
>>>>> supported non-congestion controlled rate becomes 36 mbps. A number
>>>>> of instances of an application behaving like this will clearly
>>>>> cause issues in quite a lot of LANs.
>>>>
>>>> Right, but is 5.6Mbps an issue on a LAN? Remember that if there is
>>>> loss, the calculated RTT will increase, and the rate therefore
>>>> decrease. When there is no loss and the RTT is 2ms, obviously the LAN
>>>> can sustain that traffic. (TFTP is basically operating in this way,
>>>> and doesn't seem to create huge issues on LANs.)
>>>
>>> 5,6 mbps can clearly be significantly above your fair share.
>>
>> Sure, but then there would be loss, and the computed RTT would
> increase and the bandwidth would become reduced.
>
> Assuming that they either have lock step mechanism or samples frequently
> the RTT. If one has infrequent RTT sampling, then the sampled RTT may
> not reflect the congested state, and thus provide no help in detecting
> the congestion occurance, thus no back off.
>
>>
>>> I am also worried that you will shave of a factor of 20 from the
> assumed RTT and suddenly you saturate a 100 mbps lan with just that
> stream.
>>
>> But only for at 1/20th RTT, because after that, you would start
>> seeingloss and the rate would reduce.
>>
>>> Sure, loss equals delay in ack and thus reduced rate. But, please
>>> doremember that if the RTT and packet size and amount of data to
>>> deliver
>>> support a higher than available bandwidth this protocol will contribute
>  >> substantially to persistent loss as it doesn't tune itself to how
>  >> much it overshoot.
>>
>> Right. But having one message per RTT outstanding and adapting the
>> RTT
> based on what is measured does tune the rate to the path
> characteristics. It's not great, but it should prevent causing
> persistent congestion.
>
> Sure, if you actually have a method that really ensures that it has one
> and only one packet outstanding and then an accurate enough RTT
> estimator to deal with any re-transmissions then it is self limiting.
>
>>
>>> The reason we commented on this, was that in RTP and the circuit
> breaker we don't have the lock step mechanism of TFTP, instead a loss is
> just a loss. And because the RTT is short the circuit breaker becomes
> disabled. So this is highly dependent on the context and what your bulk
> transfer application is doing.
>>
>> I'm not sure I follow the example here?
>
> I think you need to look at Section 4.1 of
> https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/
>
> That draft derives from the UDP guidelines that we basically turn off
> the forward path circuit breaker if less than one RTP packet per RTT
> where sent. The RTT sampling is done using RTCP, so it may be as
> infrequent as on average every 5 seconds.
>
> The intention with turning the circuit breaker off if so that when
> transmission of RTP packets are infrequent as single or very small
> number of packet losses should not trigger the circuit breaker.
>
> So basically we have turned the one 1 per RTT rule into a fence that
> actually allows quite high rates. And due to how the measurements are
> done it is insensitive to congestion events.
>
> What I think may be needed in the UDP guidelines is to clarify that if
> one applies the no more than one per RTT, that actually have to do
> frequent sampling, or be some lock step protocol which thus would be
> self limiting in the face of congestion.
>
> It is not okay to apply once per RTT as a rule of thumb.
>
> (Damm, I hate it when I make it more difficult for myself)
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Färögatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>

My researchers have been experimenting the RTCP circuit breaker, and came
across a similar problem: I think the problem we saw (large allowed rates
for low RTT) was not a problem specifically with low RTT, it was more the
time to REACT to an overload can become much larger than predicted by the
actual path RTT.

When a flow measures loss (and RTT) less often than every RTT, the Circuit
Breaker can still predict a reasonable safe rate. However, the source
continues to send for (multiple times) the measurement period. So an RTCP
report every few seconds over a path with a few mS of delay actually
creates as much damage to other flows as a flow would with a RTT of
several seconds, because for this time it continues to ignore the
congestion it experienced.

To put it another way, I wonder whether the recommendation should be one
packet per Max (RTT, rate adjustment interval)l (may need a better term)
rather, than one packet per path RTT.  If a flow operates by checking for
loss (or whatever congestion metric) for each packet ack'ed then this is
of course the same as one packet per RTT.

Gorry





From nucent@gmail.com  Thu Jun 11 23:11:35 2015
Return-Path: <nucent@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 4016F1A6FBB; Thu, 11 Jun 2015 23:11:35 -0700 (PDT)
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 s43V7D77Rx_l; Thu, 11 Jun 2015 23:11:32 -0700 (PDT)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B329F1A6F7C; Thu, 11 Jun 2015 23:11:32 -0700 (PDT)
Received: by obbqz1 with SMTP id qz1so17161117obb.3; Thu, 11 Jun 2015 23:11:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CPBUPO9kpe6oqi5WrpfyDlSdX0+iJG+5du5nArseNHo=; b=jYbGlWcd56aRuDa2bqclczAcra7bhmn3F3X1qNiLfEx4q5iih32NQhSbTlpnY3+Blc NNt6DVXqjbqZyDFXuUHqD0SkTm5pm/JYoqz3IP9tUj+viC+JKcjd/WWLfw9sNb8dT0zv LwoVtBjkLRW4SDGe9QaD6pynf6N4Qjftt0Tz0sQhhXlxpY9jTiYNzQKr43gEsVHBseu8 44b64J1Q9KpRwhJhljThvQw7vKYjZdEHAvLPo6nU2Ib2PQFf4H7whuCqtILEX1z9mWw7 UBDloQftAoAzWuflVounv3jbCmTG6lU/d1nc8hzmXIsZlz/yaPWevj7LLJFEVF1qSDo2 Iqiw==
MIME-Version: 1.0
X-Received: by 10.202.53.136 with SMTP id c130mr10353953oia.2.1434089492057; Thu, 11 Jun 2015 23:11:32 -0700 (PDT)
Received: by 10.60.37.67 with HTTP; Thu, 11 Jun 2015 23:11:31 -0700 (PDT)
In-Reply-To: <CAN1WL5pFOnvQh3L3z3jR=3=cyJdjQD=MFXtykYU7n-iA8eyWsg@mail.gmail.com>
References: <201506041134264013761@cnnic.cn> <CAN1WL5pFOnvQh3L3z3jR=3=cyJdjQD=MFXtykYU7n-iA8eyWsg@mail.gmail.com>
Date: Fri, 12 Jun 2015 14:11:31 +0800
Message-ID: <CAN1WL5odXiLTvR_r1VGw5-9XRg8310ZJ1AH-+CmsxPGNACEw5A@mail.gmail.com>
From: Linlin Zhou <nucent@gmail.com>
To: qinxiaowei@cnnic.cn
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/FpDsYiOAxLK8QJ5bJodbLXcKABU>
Cc: tsv-area@ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] Fw: Fw: I-D Action: draft-qin-tsvwg-uatnut-00.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: Fri, 12 Jun 2015 06:14:04 -0000

Hi Xiaowei,

- Regardless of the UATN approach you mentioned in the document, I
feel like this is something like a reverse CDN. So I am wondering why
CDN providers do not have motivation to to this work? Is it technical
issues or not a problem at all.

- According to the report in [1], throughput measurements
   from over 1.5 million mobile devices have shown that compared with an
   average downstream throughput of over 1860 Kbps, the average upstream
   throughput is only about 430 Kbps.  This is because of the adoption
   of cache techniques such as CDNs to acelerate downloading large
   content that moves the "content" closer to end users.

I think the numbers you listed are not enough to prove the conclusion.
Do you have more detailed examples?

- typo in Figure 5
No arrow III is indicated in the paragraph.

> From: qinxiaowei@cnnic.cn
> Date: 2015-05-29 11:47
> To: tsvwg; tsv-area
> Subject: Fw: Fw: I-D Action: draft-qin-tsvwg-uatnut-00.txt
> Dear all,
> I proposed an approach to upload acceleration transport network for upstream
> traffics, and the drafts was submitted.
>
> This is the link, http://datatracker.ietf.org/doc/draft-qin-tsvwg-uatnut/
>
> Any comments are welcome.
>
> Regards,
>
> Xiaowei Qin
>
>
> From: internet-drafts
> Date: 2015-05-29 11:16
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-qin-tsvwg-uatnut-00.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>   Title           : Upload Acceleration Transport Network for Upstream
> Traffics
> Authors         : Xiaowei Qin
>                           Ning Kong
>                           Xiaodong Lee
> Filename        : draft-qin-tsvwg-uatnut-00.txt
> Pages           : 12
> Date            : 2015-05-28
>
> Abstract:
>    Photos, videos and other upstream traffics generated by end users are
>    rapidly increasing these days and expected to continue doing so in
>    the future.  A lot of factors, such as long round-trip-time (RTT),
>    low robustness of delivery, and transport bottlenecks, etc., lead to
>    low upload rate, which cause poor user experiences.  This draft
>    discusses an Upload Acceleration Transport Network(UATN) for upstream
>    traffics that use distributed cache servers and separates the upload
>    transaction into two parts for greater network efficiency.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-qin-tsvwg-uatnut/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-qin-tsvwg-uatnut-00
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@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 Fri Jun 12 03:17:31 2015
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 453D11A9048 for <tsvwg@ietfa.amsl.com>; Fri, 12 Jun 2015 03:17:30 -0700 (PDT)
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 q5554oYyTBcy for <tsvwg@ietfa.amsl.com>; Fri, 12 Jun 2015 03:17:26 -0700 (PDT)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E08271A8F4A for <tsvwg@ietf.org>; Fri, 12 Jun 2015 03:17:25 -0700 (PDT)
Received: by igbpi8 with SMTP id pi8so9632912igb.0 for <tsvwg@ietf.org>; Fri, 12 Jun 2015 03:17:25 -0700 (PDT)
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=5Xfr4+dBVS+zerdBg3e1e2vuMvsYzd/6tIhicgaKByE=; b=rjbqIYMIegoJ5ce1fcIIh0Ejv1N6WuQH1rPN0hbMKpGgiy/z/8Iv3Jb031PLBBmLTo nSHi5lnlRjUxuMaAlm831Z9a6wTYQ2ANxeCY/YzrTmy9XCYgMKWkMPDfmLjgAXBeXB0K iLG1SWy8uRIKdcNtmjgw6WnSECMyd670VnZbU=
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=5Xfr4+dBVS+zerdBg3e1e2vuMvsYzd/6tIhicgaKByE=; b=Ox37wC9wiq/HP1ejLz6lD3kPQakC84RgCE5ysB4W78VdqqKFu38xKGera+cQScWaKe UR/wwQ3F/CLRzJnEsRJg8ZH56u+StVV7hcJ8K9ulh86yhVcnSmnm7lqY2/kCG7U1v554 SeN9SlUOa2NxKE90tz2FxDGcHqfe4x3Mzft8L8L7fh1nkJaGL5TSFZtAOCddMy4DV46w IQvXmQwPnNC8tGOQnQnnwQoKm+h7vf/9HjXs4uI8nKfQbFuWAuCHAO4NAftEYTHPdxWA yyxIdCHOYd8UjEYIv8mywwLsk4E3CgdZndX02wzZaDsu8dvhjeYsF9ztRMh3Mzur9DMF 7iAg==
X-Gm-Message-State: ALoCoQmIKADOsVxQmq1DmZa0uFovAyQVk5/5Ftfb+HsKZ20BdmhQ16sPEaq2NjA9zRQiG4xRjcb6HIBmecKb1ELNjM8W3Euo0QEe87VpfO/yj/4cxEtMLQ0=
X-Received: by 10.43.173.70 with SMTP id ob6mr15547573icc.45.1434104245356; Fri, 12 Jun 2015 03:17:25 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <22ef29b3a8ed578cdeead82532cd6796.squirrel@erg.abdn.ac.uk>
In-Reply-To: <22ef29b3a8ed578cdeead82532cd6796.squirrel@erg.abdn.ac.uk>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIR9svzEEVafzZC4ftyDiLkwCyUO50mA9pg
Date: Fri, 12 Jun 2015 12:17:24 +0200
Message-ID: <faf12687ee4cdfe05ef62842274bafa3@mail.gmail.com>
To: gorry@erg.abdn.ac.uk, Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
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/Moz7DW9x6rt96_EBLqAhkCShG1c>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Finishing: draft-ietf-tsvwg-sctp-failover
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, 12 Jun 2015 10:17:30 -0000

HI Gorry,

Yes,

Things have been complicated here...

I have started working on the update.
We should aim to have a document version out next week for the wg.

BR, Karen

>-----Original Message-----
>From: gorry@erg.abdn.ac.uk [mailto:gorry@erg.abdn.ac.uk]
>Sent: Thursday, June 11, 2015 1:57 PM
>To: karen.nielsen@tieto.com
>Cc: tsvwg@ietf.org
>Subject: Finishing: draft-ietf-tsvwg-sctp-failover
>
>Karen,
>
>There is some editorial work needed to prepare
draft-ietf-tsvwg-sctp-failover
>for IESG review. The RFC 2119 usage generally now looks good. Can I
>encourage you (Karen) as the document editor to take the XML and provide
>the final edits needed to finish this.
>
>I believe the WG was promised it would be sent to the IESG before
IETF-93,
>which means starting a WGLC in a week or two.
>
>Best wishes,
>
>Gorry & David
>(tsvwg co-chairs)
>
>---
>
>As I recall the proposed next steps from the last IETF meeting were:
>
>=E2=80=A2 =C2=A0All technical issues raised including standards language, =
are
(believed to
>have been) resolved. &#8232; =E2=80=A2 =C2=A0BUT... some re-structuring wo=
uld still be
>beneficial, given PS &#8232; =E2=80=A2 =C2=A0Next step would be a -11 revi=
sion:
>&#8232; =E2=80=93 Implement the agreed technical resolutions&#8232; =E2=80=
=93 Still
improve
>language and some restructuring
>
>Extract from notes of meeting:
>
>          Michael: If the heartbeat is not disabled by the user, then
must
>            send these faster. If not, then follow the user. If you make
the
>            text explicit, then OK.
>          Michael: There is a change to the security model, it is not
only
>            faster, but with permanent failover, STCP moves the traffic
away
>            permanently from the first path if there is a traffic peak.
>          Karen: The draft also proposes a mode with permanent switch
over,
>            we will document the changes and the security implications.
>          Gorry: The security section was short, this should address
that.
>            The abstract should mention the API exists as a separate
section.
>
>          Karen: We received comments suggesting we remove the discussion
of
>            CC - since this document removes this.
>          Gorry: I suggest you may leave the text marked "RFC Editor to
Remove",
>            so the IETF and IESG knows that CC changes were discussed,
and
>            that there was consensus that this change was agreed.
>          David Black: Please change the lower-case "should" to an "ought
to"=C5=A5.
>
>          Karen: We do not think this should update RFC 4960.
>          Gorry: First, is implementation optional for a compliant SCTP
stack?
>          Karen: Yes, optional
>          Gorry: Are you updating the base mechanisms that you expect
base
>            implementer to read this?
>          Randal Stewart: You would not want to update RFC 4960,
>            because that would make existing implementations non
compliant.
>            I do not think this document should update RFC 4960.
>          David: Is there a hidden "SHOULD"=C5=A5 here?
>            Is the text clear that this is based on one way to implement
>            RFC4960, but this builds on one specific way to do this.
>          Randal: There are reasons that an implementation does not want
the
>            dormant state specified in the base spec. This is an
>            implementation choice needed for this specific spec.
>          Chairs: We seem to have agreement this will not update RFC
4960.
>&#8232;
>


From nobody Sat Jun 13 08:24:50 2015
Return-Path: <jsaldana@unizar.es>
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 C314A1A702F for <tsvwg@ietfa.amsl.com>; Sat, 13 Jun 2015 08:24:47 -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 AhBgHEkeBj5s for <tsvwg@ietfa.amsl.com>; Sat, 13 Jun 2015 08:24:45 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E9ED1A0068 for <tsvwg@ietf.org>; Sat, 13 Jun 2015 08:24:44 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id t5DFOYNk025509 for <tsvwg@ietf.org>; Sat, 13 Jun 2015 17:24:34 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tsvwg@ietf.org>
References: <20150613151622.6198.4033.idtracker@ietfa.amsl.com>
In-Reply-To: <20150613151622.6198.4033.idtracker@ietfa.amsl.com>
Date: Sat, 13 Jun 2015 17:24:40 +0200
Message-ID: <000001d0a5ed$110ab150$332013f0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQHRW9SbVcMSMGs2SCSLBM03qlKn+52pIgnw
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/UgvN8zWM5-v574kwepeC4qXMHFQ>
Subject: [tsvwg] RV: New Version Notification for draft-saldana-tsvwg-tcmtf-09.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: Sat, 13 Jun 2015 15:24:47 -0000

Hi all,

We have just submitted a new version of the TCM (Tunneling, Compressing =
and Multiplexing) draft.

Best regards,

Jose

> -----Mensaje original-----
> De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Enviado el: s=C3=A1bado, 13 de junio de 2015 17:16
> Para: Dan Wing; Fernando Pascual Blanco; Julian Fernandez Navajas; =
Julian
> Fernandez Navajas; Muthu Arul Mozhi Perumal; Fernando Pascual Blanco; =
Jose
> Saldana; Dan Wing; Muthu Arul Mozhi Perumal; Jose Saldana
> Asunto: New Version Notification for draft-saldana-tsvwg-tcmtf-09.txt
>=20
>=20
> A new version of I-D, draft-saldana-tsvwg-tcmtf-09.txt has been =
successfully
> submitted by Jose Saldana and posted to the IETF repository.
>=20
> Name:		draft-saldana-tsvwg-tcmtf
> Revision:	09
> Title:		Tunneling Compressing and Multiplexing (TCM) Traffic Flows.
> Reference Model
> Document date:	2015-06-12
> Group:		Individual Submission
> Pages:		27
> URL:            =
https://www.ietf.org/internet-drafts/draft-saldana-tsvwg-tcmtf-09.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
> Htmlized:       =
https://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-09
> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-tcmtf-09
>=20
> Abstract:
>    Tunneling, Compressing and Multiplexing (TCM) is a method for
>    improving the bandwidth utilization of network segments that carry
>    multiple small-packet flows in parallel sharing a common path.  The
>    method combines different protocols for header compression,
>    multiplexing, and tunneling over a network path for the purpose of
>    reducing the bandwidth.  The amount of packets per second can also =
be
>    reduced.
>=20
>    This document describes the TCM framework and the different options
>    which can be used for each layer (header compression, multiplexing
>    and tunneling).
>=20
>=20
>=20
>=20
> 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.
>=20
> The IETF Secretariat



From nobody Sat Jun 13 08:25:42 2015
Return-Path: <jsaldana@unizar.es>
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 5B1E11A9078 for <tsvwg@ietfa.amsl.com>; Sat, 13 Jun 2015 08:25:41 -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 X48HT7TCwBBL for <tsvwg@ietfa.amsl.com>; Sat, 13 Jun 2015 08:25:40 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE4BE1A9072 for <tsvwg@ietf.org>; Sat, 13 Jun 2015 08:25:39 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id t5DFPVX8027195; Sat, 13 Jun 2015 17:25:31 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tsvwg@ietf.org>
References: <20150613152104.2871.28908.idtracker@ietfa.amsl.com>
In-Reply-To: <20150613152104.2871.28908.idtracker@ietfa.amsl.com>
Date: Sat, 13 Jun 2015 17:25:37 +0200
Message-ID: <000201d0a5ed$32fe4060$98fac120$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQF+gLjLESzSx5AuysSGOmlTUBsmT55O2LMA
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/mw6PtMAm3Nn8BzEnrVmts-2_Xr8>
Subject: [tsvwg] RV: New Version Notification for draft-suznjevic-tsvwg-mtd-tcmtf-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: Sat, 13 Jun 2015 15:25:41 -0000

Hi all,

We have also submitted a new version of the "delay limits" draft.

Best regards,

Jose

> -----Mensaje original-----
> De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Enviado el: s=C3=A1bado, 13 de junio de 2015 17:21
> Para: Mirko Suznjevic; Jose Saldana; Mirko Suznjevic; Jose Saldana
> Asunto: New Version Notification for =
draft-suznjevic-tsvwg-mtd-tcmtf-05.txt
>=20
>=20
> A new version of I-D, draft-suznjevic-tsvwg-mtd-tcmtf-05.txt
> has been successfully submitted by Jose Saldana and posted to the IETF
> repository.
>=20
> Name:		draft-suznjevic-tsvwg-mtd-tcmtf
> Revision:	05
> Title:		Delay Limits and Multiplexing Policies to be employed with =
Tunneling
> Compressing and Multiplexing Traffic Flows
> Document date:	2015-06-13
> Group:		Individual Submission
> Pages:		18
> URL:            =
https://www.ietf.org/internet-drafts/draft-suznjevic-tsvwg-mtd-tcmtf-
> 05.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
> Htmlized:       =
https://tools.ietf.org/html/draft-suznjevic-tsvwg-mtd-tcmtf-05
> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-05
>=20
> Abstract:
>    This document contains recommendations to be taken into account =
when
>    using methods which optimize bandwidth utilization through =
Tunneling
>    Compressing and Multiplexing (TCM) traffic flows over a network =
path.
>    Different multiplexing policies and implementation issues which are
>    service and link specific are discussed.  Additionally, this =
document
>    describes policies which can be used for detecting, classifying, =
and
>    choosing the network flows suitable for optimization by using TCM.
>    Finally, recommendations of maximum tolerable delays to be added by
>    optimization techniques are reported.  Recommendations are =
presented
>    only for network services for which such bandwidth optimization
>    techniques are applicable (i.e., services with low payload to =
header
>    size ratio, which will also be denoted as "small-packet flows").
>=20
>=20
>=20
>=20
> 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.
>=20
> The IETF Secretariat



From nobody Mon Jun 15 00:47:14 2015
Return-Path: <qinxiaowei@cnnic.cn>
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 B2FCF1B2AD9; Mon, 15 Jun 2015 00:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level: 
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, 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 XzwF2xLGB6-h; Mon, 15 Jun 2015 00:47:08 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 432761A1AC1; Mon, 15 Jun 2015 00:47:03 -0700 (PDT)
Received: from CNNIC-PC (unknown [218.241.119.111]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0BpcZXxgn5Vk0ZvBw--.4027S2; Mon, 15 Jun 2015 15:46:57 +0800 (CST)
Date: Mon, 15 Jun 2015 15:46:51 +0800
From: "qinxiaowei@cnnic.cn" <qinxiaowei@cnnic.cn>
To: "Linlin Zhou" <nucent@gmail.com>
References: <201506041134264013761@cnnic.cn>,  <CAN1WL5pFOnvQh3L3z3jR=3=cyJdjQD=MFXtykYU7n-iA8eyWsg@mail.gmail.com>,  <CAN1WL5odXiLTvR_r1VGw5-9XRg8310ZJ1AH-+CmsxPGNACEw5A@mail.gmail.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 136[cn]
Mime-Version: 1.0
Message-ID: <2015061515465115580522@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart312232570750_=----"
X-CM-TRANSID: AQAAf0BpcZXxgn5Vk0ZvBw--.4027S2
X-Coremail-Antispam: 1UD129KBjvJXoWxGF47Gw4fJFW8GrWUGr4fGrg_yoWrXr47pa yUXr95KrWUA3Wftw1kZ3WrXr95u3ykW3y3KFn8Gr1Uu398CFyIgr17KrWFya47XrnIgFs0 vr4Uuw1Ykws5ZrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUdmb7Iv0xC_Cr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Xr0_Ar1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Cr0_Gr1UM28EF7xvwVC2z280aVAFwI0_GcCE3s1l84ACjcxK6I 8E87Iv6xkF7I0E14v26rxl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAaz4v2 6cxKscIFY7kG0wAqx4xG6xAIxVCFxsxG0wAqx4xG6I80eVA0xI0YY7vIx2IE14AGzxvEb7 x7Mc02F40Ex2IqxVA2YxCjr7Iv64kEw24lYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2 jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvY0x0EwIxGrwACY4xI67 k04243AVAKzVAKj4xxM4xvF2IEb7IF0Fy26I8I3I1l7480Y4vEI4kI2Ix0rVAqx4xJMxkI ecxEwVAFwVW8CwCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c 02F40E14v26r106r1rMI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jrv_ JF1lIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7 CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAF wI0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8JwCE64xvF2IEb7IF0Fy7YxBIda VFxhVjvjDU0xZFpf9x07j79N3UUUUU=
X-CM-SenderInfo: xtlq5x5drzvxw6fq0xffof0/
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/NlYKeSZKyUd35NsCwp1tkqOpYMc>
Cc: tsv-area <tsv-area@ietf.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-qin-tsvwg-uatnut-00.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: Mon, 15 Jun 2015 07:47:11 -0000

This is a multi-part message in MIME format.

------=_001_NextPart312232570750_=----
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

aGksIExpbmxpbg0KVGhhbmtzIGFnYWluIGZvciB5b3UgcmV2aWV3IGFuZCBzdWdnZXN0aW9uLg0K
DQo+SSB0aGluayB0aGUgbnVtYmVycyB5b3UgbGlzdGVkIGFyZSBub3QgZW5vdWdoIHRvIHByb3Zl
IHRoZSBjb25jbHVzaW9uLiANCj5EbyB5b3UgaGF2ZSBtb3JlIGRldGFpbGVkIGV4YW1wbGVzPw0K
DQpUaGUgdGVzdCBpcyBvbmx5IGZvciBtb2JpbGUgZGV2aWNlcywgYW5kIHRoZSB0aGUgcmVwb3J0
IGNvbWVzIGZyb206IA0KaHR0cDovL3Rlc3RteWlwaG9uZS5jb20vc3RhdHMuDQoNClRoaXMgaXMg
dGhlIGxhdGVzdCBzdGF0czoNCkRvd25sb2FkOg0KRG93bmxvYWQgdGVzdHMgdGFrZW4gMywxNDAs
MjU3IA0KQXZlcmFnZSBzcGVlZCAzNTg1LjQ0IGticHMNClVwbG9hZDoNClVwbG9hZCB0ZXN0cyB0
YWtlbiA3MDgsMTU4DQpBdmVyYWdlIHNwZWVkIDYzMC41NiBrYnBzDQoNCkluIG9yZGVyIHRvIHZh
bGlkYXRlIHRoZSBhbmFseXNpcyBkZXNjcmliZWQgYWJvdmUsIEkgaGF2ZSBhbHNvIHRha2UgYSBw
cmFjdGljYWwgbWVhc3VyZW1lbnQgaW4gQ2hpbmEgTW9iaWxlIExhYnMgKGxvY2F0ZWQgaW4gQmVp
amluZykgd2hpY2ggaXMgdGhlIGRlcGFydG1lbnQgb2YgdGhlIENoaW5hIE1vYmlsZSBMaW1pdGVk
LiBBIGRhdGEgc2VydmVyIGRlcGxveWVkIGluIFNoZW56aGVuLCBzaXR1YXRlZCBpbW1lZGlhdGVs
eSBub3J0aCBvZiBIb25nIEtvbmcgKGFib3V0IDI1MDAga2lsb21ldGVycyBhd2F5IGZyb20gQmVp
amluZykgaXMgdXNlZCB0byBjb250aW51b3VzbHkgd2FpdCBmb3IgcGFja2V0cyBmcm9tIG1vYmls
ZSBkZXZpY2VzLiANClRoZSBtb2JpbGUgZGV2aWNlcyBpcyBjb25uZWN0ZWQgdG8gSW50ZXJuZXQg
dmlhIFRELUxURSwgYW5kIGNvbnRlbnQgZ2VuZXJhdGVkIGJ5IG1vYmlsZSBkZXZpY2VzIGlzIGRp
cmVjdGx5IHVwbG9hZGVkIHRvIHRoZSByZWNlaXZlciB3aXRob3V0IGFueSBhY2NlbGVyYXRpb24g
cHJvY2Vzc2luZy4gVGhlIGF2ZXJhZ2UgdXBzdHJlYW0gdGhyb3VnaHB1dCBpcyBhYm91dCAxODAg
a2Jwcy4gDQpJIGFsc28gZGVwbG95IGEgZGF0YSBzZXJ2ZXIgaW4gQmVpamluZywgIHRoZSBhdmVy
YWdlIHVwc3RyZWFtIHRocm91Z2hwdXQgY2FuIGJlIHVwIHRvIDg2MCBrYnBzLiANClRoZXJlZm9y
ZSwgIm1vdmluZyBjb250ZW50IGNsb3NlciB0byBlbmQgdXNlcnMgcmVzdWx0cyBpbiBncmVhdGVy
IG5ldHdvcmsgZWZmaWNpZW5jeSwgaW5jcmVhc2VkIHJvYnVzdG5lc3Mgb2YgZGVsaXZlcnksIGFu
ZCBsb3dlciBsYXRlbmN5Lg0KDQo+UmVnYXJkbGVzcyBvZiB0aGUgVUFUTiBhcHByb2FjaCB5b3Ug
bWVudGlvbmVkIGluIHRoZSBkb2N1bWVudCwgSQ0KPmZlZWwgbGlrZSB0aGlzIGlzIHNvbWV0aGlu
ZyBsaWtlIGEgcmV2ZXJzZSBDRE4uIFNvIEkgYW0gd29uZGVyaW5nIHdoeQ0KPkNETiBwcm92aWRl
cnMgZG8gbm90IGhhdmUgbW90aXZhdGlvbiB0byB0byB0aGlzIHdvcms/IElzIGl0IHRlY2huaWNh
bA0KPmlzc3VlcyBvciBub3QgYSBwcm9ibGVtIGF0IGFsbC4NCg0KVGhlIGV4aXN0aW5nIENETiBp
cyB1c2VkIHRvIGRpc3RyaWJ1dGUgY29udGVudCB0byBlbmQgdXNlcnMsIGhvd2V2ZXIsIG1heSBu
b3QgZGlyZWN0bHkgcmVjZWl2ZSB0aGUgY29udGVudCBnZW5lcmF0ZWQgYnkgZW5kIHVzZXJzLiAg
Rm9yIGV4YW1wbGUsIGluIGRvd25sb2FkaW5n77yMd2hlbiB0aGUgdXNlciB0eXBlcyBhIFVSTCBp
bnRvIGhpcy9oZXIgYnJvd3NlciwgdGhlIHJlcXVlc3Qgd2lsbCBiZSByZWRpcmVjdGVkIHRvIHRo
ZSBDRE4gdGhyb3VnaCDigJxDTkFNReKAnSBieSB0aGUgRE5TLg0KSG93ZXZlciwgaW4gdXBsb2Fk
aW5nLCBhICJtZWNoYW5pc20iIGlzIG5lZWRlZCB0byByZWRpcmVjdCB0aGUgcmVxdWVzdHMgb2Yg
ZW5kIHVzZXJzIHRvIFVBVE4uICBUaGF0IGlzIHRvIHNheSwgdGhlIHJlcXVlc3Qgb2YgdXBsb2Fk
aW5nIGNvbnRlbnQgdG8gZGF0YSBjZW50ZXIgd2lsbCBiZSByZWRpcmVjdGVkIHRvIGFuIGFwcHJv
cHJpYXRlIEVkZ2UgU2VydmVyIHRvIHNlcnZlIHRoaXMgdXBsb2FkaW5nLg0KDQpSZWdhcmRzLA0K
WGlhb3dlaSBRaW4NCiANCg0KDQoNCiANCkZyb206IExpbmxpbiBaaG91DQpEYXRlOiAyMDE1LTA2
LTEyIDE0OjExDQpUbzogcWlueGlhb3dlaQ0KQ0M6IHRzdndnOyB0c3YtYXJlYQ0KU3ViamVjdDog
UmU6IEZ3OiBGdzogSS1EIEFjdGlvbjogZHJhZnQtcWluLXRzdndnLXVhdG51dC0wMC50eHQNCkhp
IFhpYW93ZWksDQogDQotIFJlZ2FyZGxlc3Mgb2YgdGhlIFVBVE4gYXBwcm9hY2ggeW91IG1lbnRp
b25lZCBpbiB0aGUgZG9jdW1lbnQsIEkNCmZlZWwgbGlrZSB0aGlzIGlzIHNvbWV0aGluZyBsaWtl
IGEgcmV2ZXJzZSBDRE4uIFNvIEkgYW0gd29uZGVyaW5nIHdoeQ0KQ0ROIHByb3ZpZGVycyBkbyBu
b3QgaGF2ZSBtb3RpdmF0aW9uIHRvIHRvIHRoaXMgd29yaz8gSXMgaXQgdGVjaG5pY2FsDQppc3N1
ZXMgb3Igbm90IGEgcHJvYmxlbSBhdCBhbGwuDQogDQotIEFjY29yZGluZyB0byB0aGUgcmVwb3J0
IGluIFsxXSwgdGhyb3VnaHB1dCBtZWFzdXJlbWVudHMNCiAgIGZyb20gb3ZlciAxLjUgbWlsbGlv
biBtb2JpbGUgZGV2aWNlcyBoYXZlIHNob3duIHRoYXQgY29tcGFyZWQgd2l0aCBhbg0KICAgYXZl
cmFnZSBkb3duc3RyZWFtIHRocm91Z2hwdXQgb2Ygb3ZlciAxODYwIEticHMsIHRoZSBhdmVyYWdl
IHVwc3RyZWFtDQogICB0aHJvdWdocHV0IGlzIG9ubHkgYWJvdXQgNDMwIEticHMuICBUaGlzIGlz
IGJlY2F1c2Ugb2YgdGhlIGFkb3B0aW9uDQogICBvZiBjYWNoZSB0ZWNobmlxdWVzIHN1Y2ggYXMg
Q0ROcyB0byBhY2VsZXJhdGUgZG93bmxvYWRpbmcgbGFyZ2UNCiAgIGNvbnRlbnQgdGhhdCBtb3Zl
cyB0aGUgImNvbnRlbnQiIGNsb3NlciB0byBlbmQgdXNlcnMuDQogDQpJIHRoaW5rIHRoZSBudW1i
ZXJzIHlvdSBsaXN0ZWQgYXJlIG5vdCBlbm91Z2ggdG8gcHJvdmUgdGhlIGNvbmNsdXNpb24uDQpE
byB5b3UgaGF2ZSBtb3JlIGRldGFpbGVkIGV4YW1wbGVzPw0KIA0KLSB0eXBvIGluIEZpZ3VyZSA1
DQpObyBhcnJvdyBJSUkgaXMgaW5kaWNhdGVkIGluIHRoZSBwYXJhZ3JhcGguDQogDQo+IEZyb206
IHFpbnhpYW93ZWlAY25uaWMuY24NCj4gRGF0ZTogMjAxNS0wNS0yOSAxMTo0Nw0KPiBUbzogdHN2
d2c7IHRzdi1hcmVhDQo+IFN1YmplY3Q6IEZ3OiBGdzogSS1EIEFjdGlvbjogZHJhZnQtcWluLXRz
dndnLXVhdG51dC0wMC50eHQNCj4gRGVhciBhbGwsDQo+IEkgcHJvcG9zZWQgYW4gYXBwcm9hY2gg
dG8gdXBsb2FkIGFjY2VsZXJhdGlvbiB0cmFuc3BvcnQgbmV0d29yayBmb3IgdXBzdHJlYW0NCj4g
dHJhZmZpY3MsIGFuZCB0aGUgZHJhZnRzIHdhcyBzdWJtaXR0ZWQuDQo+DQo+IFRoaXMgaXMgdGhl
IGxpbmssIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtcWluLXRzdndnLXVh
dG51dC8NCj4NCj4gQW55IGNvbW1lbnRzIGFyZSB3ZWxjb21lLg0KPg0KPiBSZWdhcmRzLA0KPg0K
PiBYaWFvd2VpIFFpbg0KPg0KPg0KPiBGcm9tOiBpbnRlcm5ldC1kcmFmdHMNCj4gRGF0ZTogMjAx
NS0wNS0yOSAxMToxNg0KPiBUbzogaS1kLWFubm91bmNlQGlldGYub3JnDQo+IFN1YmplY3Q6IEkt
RCBBY3Rpb246IGRyYWZ0LXFpbi10c3Z3Zy11YXRudXQtMDAudHh0DQo+DQo+IEEgTmV3IEludGVy
bmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cw0K
PiBkaXJlY3Rvcmllcy4NCj4NCj4gICBUaXRsZSAgICAgICAgICAgOiBVcGxvYWQgQWNjZWxlcmF0
aW9uIFRyYW5zcG9ydCBOZXR3b3JrIGZvciBVcHN0cmVhbQ0KPiBUcmFmZmljcw0KPiBBdXRob3Jz
ICAgICAgICAgOiBYaWFvd2VpIFFpbg0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgIE5pbmcg
S29uZw0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgIFhpYW9kb25nIExlZQ0KPiBGaWxlbmFt
ZSAgICAgICAgOiBkcmFmdC1xaW4tdHN2d2ctdWF0bnV0LTAwLnR4dA0KPiBQYWdlcyAgICAgICAg
ICAgOiAxMg0KPiBEYXRlICAgICAgICAgICAgOiAyMDE1LTA1LTI4DQo+DQo+IEFic3RyYWN0Og0K
PiAgICBQaG90b3MsIHZpZGVvcyBhbmQgb3RoZXIgdXBzdHJlYW0gdHJhZmZpY3MgZ2VuZXJhdGVk
IGJ5IGVuZCB1c2VycyBhcmUNCj4gICAgcmFwaWRseSBpbmNyZWFzaW5nIHRoZXNlIGRheXMgYW5k
IGV4cGVjdGVkIHRvIGNvbnRpbnVlIGRvaW5nIHNvIGluDQo+ICAgIHRoZSBmdXR1cmUuICBBIGxv
dCBvZiBmYWN0b3JzLCBzdWNoIGFzIGxvbmcgcm91bmQtdHJpcC10aW1lIChSVFQpLA0KPiAgICBs
b3cgcm9idXN0bmVzcyBvZiBkZWxpdmVyeSwgYW5kIHRyYW5zcG9ydCBib3R0bGVuZWNrcywgZXRj
LiwgbGVhZCB0bw0KPiAgICBsb3cgdXBsb2FkIHJhdGUsIHdoaWNoIGNhdXNlIHBvb3IgdXNlciBl
eHBlcmllbmNlcy4gIFRoaXMgZHJhZnQNCj4gICAgZGlzY3Vzc2VzIGFuIFVwbG9hZCBBY2NlbGVy
YXRpb24gVHJhbnNwb3J0IE5ldHdvcmsoVUFUTikgZm9yIHVwc3RyZWFtDQo+ICAgIHRyYWZmaWNz
IHRoYXQgdXNlIGRpc3RyaWJ1dGVkIGNhY2hlIHNlcnZlcnMgYW5kIHNlcGFyYXRlcyB0aGUgdXBs
b2FkDQo+ICAgIHRyYW5zYWN0aW9uIGludG8gdHdvIHBhcnRzIGZvciBncmVhdGVyIG5ldHdvcmsg
ZWZmaWNpZW5jeS4NCj4NCj4NCj4gVGhlIElFVEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9y
IHRoaXMgZHJhZnQgaXM6DQo+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0
LXFpbi10c3Z3Zy11YXRudXQvDQo+DQo+IFRoZXJlJ3MgYWxzbyBhIGh0bWxpemVkIHZlcnNpb24g
YXZhaWxhYmxlIGF0Og0KPiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtcWluLXRz
dndnLXVhdG51dC0wMA0KPg0KPg0KPiBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291
cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQo+IHVudGlsIHRoZSBo
dG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcu
DQo+DQo+IEludGVybmV0LURyYWZ0cyBhcmUgYWxzbyBhdmFpbGFibGUgYnkgYW5vbnltb3VzIEZU
UCBhdDoNCj4gZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCj4NCj4gX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gSS1ELUFubm91bmNl
IG1haWxpbmcgbGlzdA0KPiBJLUQtQW5ub3VuY2VAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pLWQtYW5ub3VuY2UNCj4gSW50ZXJuZXQtRHJhZnQgZGly
ZWN0b3JpZXM6IGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwNCj4gb3IgZnRwOi8vZnRw
LmlldGYub3JnL2lldGYvMXNoYWRvdy1zaXRlcy50eHQNCg==

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

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DUTF-8"><style>body { line-height: 1.5; }blockquote { margin-top: 0px; =
margin-bottom: 0px; margin-left: 0.5em; }body { font-size: 10.5pt; font-fa=
mily: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91; color: rgb(0, 0, 0); line-heig=
ht: 1.5; }</style></head><body>=0A<div><span></span>hi, Linlin</div><div>T=
hanks again for you review and suggestion.</div><div><br></div><div><span =
style=3D"font-size: 10.5pt; line-height: 1.5; background-color: window;">&=
gt;</span><span style=3D"background-color: rgba(0, 0, 0, 0);">I think the =
numbers you listed are not enough to prove the conclusion.=0A<br></span>&g=
t;<span style=3D"background-color: rgba(0, 0, 0, 0);">Do you have more det=
ailed examples?</span></div><div><br></div><div><div><span style=3D"backgr=
ound-color: rgba(0, 0, 0, 0);">The test is only for mobile devices, and th=
e the report comes from:&nbsp;</span></div><div><span style=3D"background-=
color: rgba(0, 0, 0, 0);">http://testmyiphone.com/stats.</span></div><div>=
<span style=3D"font-size: 10.5pt; line-height: 1.5; background-color: rgba=
(0, 0, 0, 0);"><br></span></div><div><span style=3D"font-size: 10.5pt; lin=
e-height: 1.5; background-color: rgba(0, 0, 0, 0);">This is the&nbsp;</spa=
n><span style=3D"background-color: rgba(0, 0, 0, 0);">latest&nbsp;</span><=
span style=3D"font-size: 10.5pt; line-height: 1.5; background-color: rgba(=
0, 0, 0, 0);">stats:</span></div><div></div><div><span style=3D"font-famil=
y: 'Arial, Helvetica, sans-serif'; font-size: 16px; background-color: rgba=
(0, 0, 0, 0);">Download:</span></div><div><span style=3D"font-family: 'Ari=
al, Helvetica, sans-serif'; font-size: 16px; background-color: rgba(0, 0, =
0, 0);">Download tests taken	3,140,257&nbsp;<br>Average speed	3585.44 kbps=
</span></div><div><span style=3D"background-color: rgba(0, 0, 0, 0); font-=
size: 10.5pt; line-height: 1.5;">Upload:</span></div><div><span style=3D"f=
ont-family: 'Arial, Helvetica, sans-serif'; font-size: 16px; line-height: =
24px;">Upload tests taken 708,158</span><br style=3D"font-family: 'Arial, =
Helvetica, sans-serif'; font-size: 16px; line-height: 24px;"><span style=
=3D"font-family: 'Arial, Helvetica, sans-serif'; font-size: 16px; line-hei=
ght: 24px;">Av</span><span style=3D"font-family: 'Arial, Helvetica, sans-s=
erif'; font-size: 16px; line-height: 24px; background-color: window;">erag=
e speed 630.56 kbps</span></div></div><div><br></div><div><div><span style=
=3D"background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.=
5;">In order to validate the analysis described above, I have also take a =
practical measurement in China Mobile Labs (located in Beijing) which is t=
he department of the China Mobile Limited. A data server deployed in Shenz=
hen, situated immediately north of Hong Kong (about 2500 kilometers away f=
rom Beijing) is used to continuously wait for packets from mobile devices.=
&nbsp;</span></div><div><span style=3D"background-color: rgba(0, 0, 0, 0);=
">The mobile devices is connected to Internet via TD-LTE, and&nbsp;</span>=
<span style=3D"font-size: 10.5pt; line-height: 1.5; background-color: wind=
ow;">content generated by mobile devices is directly uploaded to the recei=
ver without any acceleration processing.&nbsp;</span><span style=3D"backgr=
ound-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">The av=
erage upstream throughput is about <b>180 kbps</b>.&nbsp;</span></div><div=
><span style=3D"font-size: 10.5pt; line-height: 1.5; background-color: win=
dow;">I also deploy a data server in Beijing, &nbsp;t</span><span style=3D=
"font-size: 10.5pt; line-height: 1.5; background-color: window;">he averag=
e upstream throughput can be up to<b> 860 kbps.</b>&nbsp;</span></div></di=
v><div><span style=3D"font-size: 10.5pt; line-height: 1.5; background-colo=
r: window;">Therefore, "m</span><span lang=3D"EN-US" style=3D"font-size: 1=
0.5pt; line-height: 1.5; background-color: window;">oving content closer t=
o end users results in greater network efficiency,&nbsp;</span><span style=
=3D"font-size: 10.5pt; line-height: 1.5; background-color: window;">increa=
sed robustness of delivery, and lower latency.</span></div><div><span styl=
e=3D"font-size: 10.5pt; line-height: 1.5; background-color: window;"><br><=
/span></div><div><div><span style=3D"font-size: 10.5pt; line-height: 1.5; =
background-color: window;">&gt;</span>Regardless of the UATN approach you =
mentioned in the document, I</div><div><span style=3D"font-size: 10.5pt; l=
ine-height: 1.5; background-color: window;">&gt;</span>feel like this is s=
omething like a reverse CDN. So I am wondering why</div><div><span style=
=3D"font-size: 10.5pt; line-height: 1.5; background-color: window;">&gt;</=
span>CDN providers do not have motivation to to this work? Is it technical=
</div><div><span style=3D"font-size: 10.5pt; line-height: 1.5; background-=
color: window;">&gt;</span>issues or not a problem at all.</div></div><div=
><span style=3D"font-size: 10.5pt; line-height: 1.5; background-color: win=
dow;"><br></span></div><div><span style=3D"background-color: rgba(0, 0, 0,=
 0);">The existing CDN is used to distribute content to end users, however=
, may not directly receive the content generated by end users. &nbsp;</spa=
n><span style=3D"background-color: rgba(0, 0, 0, 0); font-size: 10.5pt; li=
ne-height: 1.5;">For example, in downloading=EF=BC=8Cwhen the user types a=
 URL into his/her browser, the request will be redirected to the CDN throu=
gh =E2=80=9CCNAME=E2=80=9D by the DNS.</span></div><div><span style=3D"bac=
kground-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;">How=
ever, in uploading, a "mechanism"  is needed to redirect the requests of e=
nd users to UATN. &nbsp;</span><span style=3D"background-color: rgba(0, 0,=
 0, 0); font-size: 10.5pt; line-height: 1.5;">That is to say, the request =
of uploading content to data center will be redirected to an appropriate E=
dge Server to serve this uploading.</span></div><div><span style=3D"backgr=
ound-color: rgba(0, 0, 0, 0); font-size: 10.5pt; line-height: 1.5;"><br></=
span></div><div>Regards,</div><div>Xiaowei Qin</div><div>&nbsp;</div><div>=
<br></div><hr style=3D"width: 210px; height: 1px; display: none;" color=3D=
"#b5c4df" size=3D"1" align=3D"left">=0A<div><span></span></div>=0A<blockqu=
ote style=3D"margin-top: 0px; margin-bottom: 0px; margin-left: 0.5em;"><di=
v>&nbsp;</div><div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;pad=
ding:3.0pt 0cm 0cm 0cm"><div style=3D"PADDING-RIGHT: 8px; PADDING-LEFT: 8p=
x; FONT-SIZE: 12px;FONT-FAMILY:tahoma;COLOR:#000000; BACKGROUND: #efefef; =
PADDING-BOTTOM: 8px; PADDING-TOP: 8px"><div><b>From:</b>&nbsp;<a href=3D"m=
ailto:nucent@gmail.com">Linlin Zhou</a></div><div><b>Date:</b>&nbsp;2015-0=
6-12&nbsp;14:11</div><div><b>To:</b>&nbsp;<a href=3D"mailto:qinxiaowei@cnn=
ic.cn">qinxiaowei</a></div><div><b>CC:</b>&nbsp;<a href=3D"mailto:tsvwg@ie=
tf.org">tsvwg</a>; <a href=3D"mailto:tsv-area@ietf.org">tsv-area</a></div>=
<div><b>Subject:</b>&nbsp;Re: Fw: Fw: I-D Action: draft-qin-tsvwg-uatnut-0=
0.txt</div></div></div><div><div>Hi Xiaowei,</div>=0A<div>&nbsp;</div>=0A<=
div>- Regardless of the UATN approach you mentioned in the document, I</di=
v>=0A<div>feel like this is something like a reverse CDN. So I am wonderin=
g why</div>=0A<div>CDN providers do not have motivation to to this work? I=
s it technical</div>=0A<div>issues or not a problem at all.</div>=0A<div>&=
nbsp;</div>=0A<div>- According to the report in [1], throughput measuremen=
ts</div>=0A<div>&nbsp;&nbsp; from over 1.5 million mobile devices have sho=
wn that compared with an</div>=0A<div>&nbsp;&nbsp; average downstream thro=
ughput of over 1860 Kbps, the average upstream</div>=0A<div>&nbsp;&nbsp; t=
hroughput is only about 430 Kbps.&nbsp; This is because of the adoption</d=
iv>=0A<div>&nbsp;&nbsp; of cache techniques such as CDNs to acelerate down=
loading large</div>=0A<div>&nbsp;&nbsp; content that moves the "content" c=
loser to end users.</div>=0A<div>&nbsp;</div>=0A<div>I think the numbers y=
ou listed are not enough to prove the conclusion.</div>=0A<div>Do you have=
 more detailed examples?</div>=0A<div>&nbsp;</div>=0A<div>- typo in Figure=
 5</div>=0A<div>No arrow III is indicated in the paragraph.</div>=0A<div>&=
nbsp;</div>=0A<div>&gt; From: qinxiaowei@cnnic.cn</div>=0A<div>&gt; Date: =
2015-05-29 11:47</div>=0A<div>&gt; To: tsvwg; tsv-area</div>=0A<div>&gt; S=
ubject: Fw: Fw: I-D Action: draft-qin-tsvwg-uatnut-00.txt</div>=0A<div>&gt=
; Dear all,</div>=0A<div>&gt; I proposed an approach to upload acceleratio=
n transport network for upstream</div>=0A<div>&gt; traffics, and the draft=
s was submitted.</div>=0A<div>&gt;</div>=0A<div>&gt; This is the link, htt=
p://datatracker.ietf.org/doc/draft-qin-tsvwg-uatnut/</div>=0A<div>&gt;</di=
v>=0A<div>&gt; Any comments are welcome.</div>=0A<div>&gt;</div>=0A<div>&g=
t; Regards,</div>=0A<div>&gt;</div>=0A<div>&gt; Xiaowei Qin</div>=0A<div>&=
gt;</div>=0A<div>&gt;</div>=0A<div>&gt; From: internet-drafts</div>=0A<div=
>&gt; Date: 2015-05-29 11:16</div>=0A<div>&gt; To: i-d-announce@ietf.org</=
div>=0A<div>&gt; Subject: I-D Action: draft-qin-tsvwg-uatnut-00.txt</div>=
=0A<div>&gt;</div>=0A<div>&gt; A New Internet-Draft is available from the =
on-line Internet-Drafts</div>=0A<div>&gt; directories.</div>=0A<div>&gt;</=
div>=0A<div>&gt;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; : Upload Acceleration Transport Network for Upstream<=
/div>=0A<div>&gt; Traffics</div>=0A<div>&gt; Authors&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; : Xiaowei Qin</div>=0A<div>&gt;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ning Ko=
ng</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; Xiaodong Lee</div>=0A<div>&gt; Filename&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : draft-qin-tsvwg-uatnut-00.txt</div>=
=0A<div>&gt; Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; : 12</div>=0A<div>&gt; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; : 2015-05-28</div>=0A<div>&gt;</div>=0A<div>&gt; =
Abstract:</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp; Photos, videos and other ups=
tream traffics generated by end users are</div>=0A<div>&gt;&nbsp;&nbsp;&nb=
sp; rapidly increasing these days and expected to continue doing so in</di=
v>=0A<div>&gt;&nbsp;&nbsp;&nbsp; the future.&nbsp; A lot of factors, such =
as long round-trip-time (RTT),</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp; low rob=
ustness of delivery, and transport bottlenecks, etc., lead to</div>=0A<div=
>&gt;&nbsp;&nbsp;&nbsp; low upload rate, which cause poor user experiences=
.&nbsp; This draft</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp; discusses an Upload=
 Acceleration Transport Network(UATN) for upstream</div>=0A<div>&gt;&nbsp;=
&nbsp;&nbsp; traffics that use distributed cache servers and separates the=
 upload</div>=0A<div>&gt;&nbsp;&nbsp;&nbsp; transaction into two parts for=
 greater network efficiency.</div>=0A<div>&gt;</div>=0A<div>&gt;</div>=0A<=
div>&gt; The IETF datatracker status page for this draft is:</div>=0A<div>=
&gt; https://datatracker.ietf.org/doc/draft-qin-tsvwg-uatnut/</div>=0A<div=
>&gt;</div>=0A<div>&gt; There's also a htmlized version available at:</div=
>=0A<div>&gt; https://tools.ietf.org/html/draft-qin-tsvwg-uatnut-00</div>=
=0A<div>&gt;</div>=0A<div>&gt;</div>=0A<div>&gt; Please note that it may t=
ake a couple of minutes from the time of submission</div>=0A<div>&gt; unti=
l the htmlized version and diff are available at tools.ietf.org.</div>=0A<=
div>&gt;</div>=0A<div>&gt; Internet-Drafts are also available by anonymous=
 FTP at:</div>=0A<div>&gt; ftp://ftp.ietf.org/internet-drafts/</div>=0A<di=
v>&gt;</div>=0A<div>&gt; _______________________________________________</=
div>=0A<div>&gt; I-D-Announce mailing list</div>=0A<div>&gt; I-D-Announce@=
ietf.org</div>=0A<div>&gt; https://www.ietf.org/mailman/listinfo/i-d-annou=
nce</div>=0A<div>&gt; Internet-Draft directories: http://www.ietf.org/shad=
ow.html</div>=0A<div>&gt; or ftp://ftp.ietf.org/ietf/1shadow-sites.txt</di=
v>=0A</div></blockquote>=0A</body></html>
------=_001_NextPart312232570750_=------



From nobody Mon Jun 15 00:47:39 2015
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 663411A8894 for <tsvwg@ietfa.amsl.com>; Mon, 15 Jun 2015 00:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.511
X-Spam-Level: 
X-Spam-Status: No, score=-1.511 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 v8aRViOhJZgD for <tsvwg@ietfa.amsl.com>; Mon, 15 Jun 2015 00:47:36 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id E63481B33E9 for <tsvwg@ietf.org>; Mon, 15 Jun 2015 00:47:21 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id A26B61B0024A for <tsvwg@ietf.org>; Mon, 15 Jun 2015 08:47:22 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Mon, 15 Jun 2015 08:46:15 +0100
Message-ID: <b21d37374a385ae5caddcaea18d8a5cd.squirrel@erg.abdn.ac.uk>
Date: Mon, 15 Jun 2015 08:46:15 +0100
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
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/S9OwBvYTV_k_3djSd7XuZqWp8iE>
Subject: [tsvwg] Agenda request for the TSVWG meeting in Prague
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: Mon, 15 Jun 2015 07:47:38 -0000

It is time to start building the TSVWG meeting agenda for the Prague IETF
meeting.

• As usual, if you edit a WG draft, please contact the chairs and let us
know whether we should expect a short update or whether you think you
could benefit from a longer slot to discuss issues.

• If you would like to present other work in tsvwg, please send an email
to the Chairs asap - so things can be discussed on the list prior to the
meeting.Note: please be sure to embed "tsvwg"in the filename of all new
drafts.

Please send requests as soon as possible.

Thanks!

Gorry & David
(tsvwg Co-Chairs)


From nobody Mon Jun 15 15:19:54 2015
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 5BC5D1B2CD3 for <tsvwg@ietfa.amsl.com>; Mon, 15 Jun 2015 15:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, 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 VmEH3SLq9ikN for <tsvwg@ietfa.amsl.com>; Mon, 15 Jun 2015 15:19:49 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 765981B2CCE for <tsvwg@ietf.org>; Mon, 15 Jun 2015 15:19:49 -0700 (PDT)
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com [10.106.48.159]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t5FMJl43030264 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <tsvwg@ietf.org>; Mon, 15 Jun 2015 18:19:48 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com t5FMJl43030264
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1434406788; bh=KVwIPDy/jSmVfNsLULvT2aZ7SjY=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=FAI0UdD5s8RZ2fq6se7ReG4pW1q1BTLYqRf389tyVkmhvISqyZpVkGH77p7/ScM3v bAmIvfiQcskZjKXsWwxqh2dN2P5OFfqJXX5YQsokMi/4jxaG/srsLCEMBRj8zVySU6 JqdvdZu0wxFa2XzYBpYKAdBhJMb5EUgeqapRTahY=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com t5FMJl43030264
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd55.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Mon, 15 Jun 2015 18:19:36 -0400
Received: from mxhub09.corp.emc.com (mxhub09.corp.emc.com [10.254.92.104]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t5FMJb0I025319 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Mon, 15 Jun 2015 18:19:37 -0400
Received: from MXHUB205.corp.emc.com (10.253.68.31) by mxhub09.corp.emc.com (10.254.92.104) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 15 Jun 2015 18:19:36 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.123]) by MXHUB205.corp.emc.com ([10.253.68.31]) with mapi id 14.03.0224.002; Mon, 15 Jun 2015 18:19:36 -0400
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Third and FINAL call for volunteers, Nomcom 2015-2016
Thread-Index: AQHQp1IFhTbFAEsY10CCHKhno7+MRJ2uI86Q
Date: Mon, 15 Jun 2015 22:19:35 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949360B378183@MX104CL02.corp.emc.com>
References: <20150615095928.18576.6993.idtracker@ietfa.amsl.com>
In-Reply-To: <20150615095928.18576.6993.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.57]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/IVwNiSmJVzEc-Poox_JEA4-W4so>
Subject: [tsvwg] FW: Third and FINAL call for volunteers, Nomcom 2015-2016
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: Mon, 15 Jun 2015 22:19:52 -0000

LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IElFVEYtQW5ub3VuY2UgW21haWx0bzpp
ZXRmLWFubm91bmNlLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBOb21Db20gQ2hhaXIg
MjAxNQ0KU2VudDogTW9uZGF5LCBKdW5lIDE1LCAyMDE1IDU6NTkgQU0NClRvOiBJRVRGIEFubm91
bmNlbWVudCBMaXN0DQpDYzogaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogVGhpcmQgYW5kIEZJTkFM
IGNhbGwgZm9yIHZvbHVudGVlcnMsIE5vbWNvbSAyMDE1LTIwMTYNCg0KKioqUmVtaW5kZXI6IERl
YWRsaW5lIGZvciB2b2x1bnRlZXJpbmcgZm9yIE5vbWNvbSBpcyBpbiBPTkUgV0VFSy4qKioNCg0K
VGhlIElFVEYgbm9tY29tIGFwcG9pbnRzIGZvbGtzIHRvIGZpbGwgdGhlIG9wZW4gc2xvdHMgb24g
dGhlIElBT0MsIHRoZSBJQUIsDQphbmQgdGhlIElFU0cuDQoNClRlbiB2b3RpbmcgbWVtYmVycyBm
b3IgdGhlIG5vbWNvbSBhcmUgc2VsZWN0ZWQgaW4gYSB2ZXJpZmlhYmx5IHJhbmRvbQ0Kd2F5IGZy
b20gYSBwb29sIG9mIHZvbHVudGVlcnMuIFRoZSBtb3JlIHZvbHVudGVlcnMsIHRoZSBiZXR0ZXIg
Y2hhbmNlIHdlDQpoYXZlIG9mIGNob29zaW5nIGEgcmFuZG9tIHlldCByZXByZXNlbnRhdGl2ZSBj
cm9zcyBzZWN0aW9uIG9mIHRoZSBJRVRGDQpwb3B1bGF0aW9uLg0KDQpUaGUgZGV0YWlscyBvZiB0
aGUgb3BlcmF0aW9uIG9mIHRoZSBub21jb20gY2FuIGJlIGZvdW5kIGluIFJGQyA3NDM3LA0KYW5k
IEJDUDEwL1JGQzM3OTcgZGV0YWlscyB0aGUgc2VsZWN0aW9uIGFsZ29yaXRobS4NCg0KVm9sdW50
ZWVycyBtdXN0IGhhdmUgYXR0ZW5kZWQgMyBvZiB0aGUgcGFzdCA1IElFVEYgbWVldGluZ3MuICBB
cyBzcGVjaWZpZWQgDQppbiBSRkMgNzQzNywgdGhhdCBtZWFucyB0aHJlZSBvdXQgb2YgdGhlIGZp
dmUgcGFzdCBtZWV0aW5ncyB1cCB0byB0aGUgdGltZQ0KdGhpcyBlbWFpbCBhbm5vdW5jZW1lbnQg
Z29lcyBvdXQgdG8gc3RhcnQgdGhlIHNvbGljaXRhdGlvbiBvZiB2b2x1bnRlZXJzLg0KVGhlIGZp
dmUgbWVldGluZ3Mgb3V0IG9mIHdoaWNoIHlvdSBtdXN0IGhhdmUgYXR0ZW5kZWQgKnRocmVlKg0K
YXJlOg0KDQpJRVRGIDg4IChWYW5jb3V2ZXIpLCBcDQogICAgICAgICA4OSAoTG9uZG9uKSwgICAg
ICAgXA0KICAgICAgICAgOTAgKFRvcm9udG8pLCAgICAgICAgICoqKiBBTlkgVEhSRUUhDQogICAg
ICAgICA5MSAoSG9ub2x1bHUpLCAgICAgLw0KICAgICAgICAgOTIgKERhbGxhcykgICAgICAgIC8N
Cg0KSWYgeW91IHF1YWxpZnksIHBsZWFzZSB2b2x1bnRlZXIuICAgSG93ZXZlciwgbXVjaCBhcyB3
ZSB3YW50IHRoaXMsIGJlZm9yZQ0KeW91IGRlY2lkZSB0byB2b2x1bnRlZXIsIHBsZWFzZSBiZSBz
dXJlIHlvdSBhcmUgd2lsbGluZyB0byBmb3JnbyBhcHBvaW50bWVudA0KdG8gYW55IG9mIHRoZSBw
b3NpdGlvbnMgZm9yIHdoaWNoIHRoaXMgbm9tY29tIGlzIHJlc3BvbnNpYmxlLg0KDQoNCkFzIG9m
IHRvZGF5LCB3ZSBoYXZlIDE1MSBjb25maXJtZWQgdm9sdW50ZWVycy4gNzIgb2YgdGhvc2Ugd2hv
IHRpY2tlZCB0aGUNCmJveCBvbiB0aGUgcmVnaXN0cmF0aW9uIGZvcm0gZm9yIEhhd2FpaSwgRGFs
bGFzIGFuZCBQcmFndWUgaGF2ZSBzdGlsbCBub3QNCnJlc3BvbmRlZC4NCg0KSWYgeW91IGJlbGll
dmUgeW91IGhhdmUgdm9sdW50ZWVyZWQsIGFuZCB5b3VyIG5hbWUgaXMgTk9UIGJlbG93LCBwbGVh
c2UNCmNvbnRhY3QgbWUgYXMgc29vbiBhcyBwb3NzaWJsZS4NCg0KVGhhbmsgeW91IGZvciB2b2x1
bnRlZXJpbmchDQoNClRoZSBsaXN0IG9mIHBlb3BsZSBhbmQgcG9zdHMgd2hvc2UgdGVybXMgZW5k
IHdpdGggdGhlIE1hcmNoIDIwMTYgSUVURg0KbWVldGluZywgYW5kIHRodXMgdGhlIHBvc2l0aW9u
cyBmb3Igd2hpY2ggdGhpcyBub21jb20gaXMgcmVzcG9uc2libGUsIGFyZQ0KDQpJQU9DOg0KTm8g
dGVybXMgZXhwaXJlIGF0IHRoaXMgdGltZS4NCg0KSUFCOg0KTWFyeSBCYXJuZXMNCkpvZSBIaWxk
ZWJyYW5kDQpUZWQgSGFyZGllDQpFcmlrIE5vcmRtYXJrDQpCcmlhbiBUcmFtbWVsbA0KTWFyYyBC
bGFuY2hldA0KDQpJRVNHOg0KQWxpc3NhIENvb3BlciAoQVJUKQ0KQmFycnkgTGVpYmEgKEFSVCkN
CkJyaWFuIEhhYmVybWFuIChJbnRlcm5ldCkNCkJlbm9pdCBDbGFpc2UgKE9wZXJhdGlvbnMgYW5k
IE1hbmFnZW1lbnQpDQpBbGlhIEF0bGFzIChSb3V0aW5nKQ0KS2F0aGxlZW4gTW9yaWFydHkgKFNl
Y3VyaXR5KQ0KTWFydGluIFN0aWVtZXJsaW5nIChUcmFuc3BvcnQpDQoNClRoZSBBcHBsaWNhdGlv
bnMgIGFuZCBSZWFsLVRpbWUgKEFSVCkgYXJlYSBpcyB0aGUgZXhwZWN0ZWQgbmV3IGFyZWENCnJl
c3VsdGluZyBmcm9tIHRoZSBtZXJnZSBvZiB0aGUgQVBQIGFuZCBSQUkgYXJlYXMuDQpBbGwgYXBw
b2ludG1lbnRzIGFyZSBmb3IgMiB5ZWFycy4NClRoZSBBUlQgYW5kIFJvdXRpbmcgYXJlYXMgaGF2
ZSAzIEFEcyBhbmQgdGhlIEdlbmVyYWwgYXJlYSBoYXMgMTsgYWxsIG90aGVyIGFyZWFzIGhhdmUg
MiBBRHMuDQpUaHVzLCBhbGwgYXJlYXMgaGF2ZSBhdCBsZWFzdCBvbmUgY29udGludWluZyBBRC4N
Cg0KDQpUaGUgcHJpbWFyeSBhY3Rpdml0eSBmb3IgdGhpcyBub21jb20gd2lsbCBiZWdpbiBpbiBK
dWx5IDIwMTUgYW5kIHNob3VsZCBiZQ0KY29tcGxldGVkIGluIEphbnVhcnkgMjAxNi4gICBUaGUg
bm9tY29tIHdpbGwgaGF2ZSByZWd1bGFybHkgc2NoZWR1bGVkDQpjb25mZXJlbmNlIGNhbGxzIHRv
IGVuc3VyZSBwcm9ncmVzcy4gKFdlIG1pZ2h0IGRvZ2Zvb2QgV2ViUlRDKQ0KVGhlcmUgd2lsbCBi
ZSBhY3Rpdml0aWVzIHRvIGNvbGxlY3QgcmVxdWlyZW1lbnRzIGZyb20gdGhlIGNvbW11bml0eSwg
cmV2aWV3DQpjYW5kaWRhdGUgcXVlc3Rpb25uYWlyZXMsIHJldmlldyBmZWVkYmFjayBmcm9tIGNv
bW11bml0eSBtZW1iZXJzIGFib3V0DQpjYW5kaWRhdGVzLCBhbmQgdGFsayB0byBjYW5kaWRhdGVz
Lg0KDQpUaHVzLCBiZWluZyBhIG5vbWNvbSBtZW1iZXIgZG9lcyByZXF1aXJlIHNvbWUgdGltZSBj
b21taXRtZW50OyBidXQgaXQgaXMgYWxzbw0KYSB2ZXJ5IHJld2FyZGluZyBleHBlcmllbmNlLg0K
DQpJdCBpcyB2ZXJ5IGltcG9ydGFudCB0aGF0IHlvdSBiZSBhYmxlIHRvIGF0dGVuZCBJRVRGOTQg
KFlva29oYW1hKSB0byBjb25kdWN0IGludGVydmlld3MuDQpCZWluZyBhdCBJRVRGOTMgKFByYWd1
ZSkgaXMgdXNlZnVsIGZvciBvcmllbnRhdGlvbi4gIEJlaW5nIGF0IElFVEY5NSBpcyBub3QgZXNz
ZW50aWFsLg0KDQpQbGVhc2Ugdm9sdW50ZWVyIGJ5IHNlbmRpbmcgbWUgYW4gZW1haWwgYmVmb3Jl
IDExOjU5IHBtIENFVCAoVVRDICsyIGhvdXJzKQ0KSnVuZSAyMiwgMjAxNSwgYXMgZm9sbG93czoN
Cg0KVG86IG5vbWNvbS1jaGFpci0yMDE1QGlldGYub3JnDQpTdWJqZWN0OiBOb21jb20gMjAxNS0x
NiBWb2x1bnRlZXINCg0KUGxlYXNlIGluY2x1ZGUgdGhlIGZvbGxvd2luZyBpbmZvcm1hdGlvbiBp
biB0aGUgZW1haWwgYm9keToNCg0KWW91ciBGdWxsIE5hbWU6IF9fX19fX19fX18NCiAgICAvLyBh
cyB5b3Ugd3JpdGUgaXQgb24gdGhlIElFVEYgcmVnaXN0cmF0aW9uIGZvcm0NCkN1cnJlbnQgUHJp
bWFyeSBBZmZpbGlhdGlvbjoNCiAgICAvLyBUeXBpY2FsbHkgd2hhdCBnb2VzIGluIHRoZSBDb21w
YW55IGZpZWxkDQogICAgLy8gaW4gdGhlIElFVEYgUmVnaXN0cmF0aW9uIEZvcm0NCkVtYWlsczog
X19fX19fX19fX19fX19fDQogICAvLyBBbGwgZW1haWwgYWRkcmVzc2VzIHVzZWQgdG8gcmVnaXN0
ZXIgZm9yIHRoZSBwYXN0IDUgSUVURiBtZWV0aW5ncw0KICAgLy8gUHJlZmVycmVkIGVtYWlsIGFk
ZHJlc3MgZmlyc3QNClRlbGVwaG9uZTogX19fX19fX19fX19fX19fX19fX19fX18NCiAgICAvLyBG
b3IgY29uZmlybWF0aW9uIGlmIHNlbGVjdGVkDQoNCllvdSBzaG91bGQgZXhwZWN0IGFuIGVtYWls
IHJlc3BvbnNlIGZyb20gbWUgd2l0aGluIDMgYnVzaW5lc3MgZGF5cyBzdGF0aW5nDQp3aGV0aGVy
IG9yIG5vdCB5b3UgYXJlIHF1YWxpZmllZC4gIElmIHlvdSBkb24ndCByZWNlaXZlIHRoaXMgcmVz
cG9uc2UsDQpwbGVhc2UgcmUtc2VuZCB5b3VyIGVtYWlsIHdpdGggdGhlIHRhZyAiUkVTRU5EIiIg
YWRkZWQgdG8gdGhlIHN1YmplY3QgbGluZS4NCg0KSWYgeW91IGFyZSBub3QgeWV0IHN1cmUgaWYg
eW91IHdvdWxkIGxpa2UgdG8gdm9sdW50ZWVyLCBwbGVhc2UgY29uc2lkZXINCnRoYXQgbm9tY29t
IG1lbWJlcnMgcGxheSBhIHZlcnkgaW1wb3J0YW50IHJvbGUgaW4gc2hhcGluZyB0aGUgbGVhZGVy
c2hpcA0Kb2YgdGhlIElFVEYuICBRdWVzdGlvbnMgYnkgZW1haWwgb3Igdm9pY2UgYXJlIHdlbGNv
bWUuDQpWb2x1bnRlZXJpbmcgZm9yIHRoZSBub21jb20gaXMgYSBncmVhdCB3YXkgdG8gY29udHJp
YnV0ZSB0byB0aGUgSUVURiENCg0KWW91IHdpbGwgZmluZCBhIGRldGFpbGVkIHRpbWVsaW5lIG9u
IHRoZSBub21jb20gd2ViIHNpdGUgYXQ6DQogICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9y
Zy9ub21jb20vMjAxNS8NCg0KVGhhbmsgeW91IQ0KSGFyYWxkIEFsdmVzdHJhbmQNCmh0YStub21j
b21AYWx2ZXN0cmFuZC5ubw0Kbm9tY29tLWNoYWlyLTIwMTVAaWV0Zi5vcmcNCg0KDQo9PT09PSAg
cXVhbGlmaWVkIHZvbHVudGVlcnMgc28gZmFyLCBpbiBhbHBoYWJldGljYWwgb3JkZXIgYnkgZmly
c3QgbmFtZQ0KQWRhbSBNb250dmlsbGUNCkFkcmlhbiBGYXJyZWwNCkFORFJFVyBEb2xnYW5vdw0K
QW5kcmV3IE5ld3Rvbg0KQW5keSBCaWVybWFuDQpBTk0gWmFoZWR1enphbWFuIFNhcmtlcg0KQW5v
b3AgR2hhbndhbmkNCkFudGhvbnkgTmFkYWxpbg0KQXJpIEtlcmFuZW4NCkJlbm5vIE92ZXJlaW5k
ZXINCkJlcm5hcmQgQWJvYmENCkJodW1pcCBLSEFTTkFCSVNIDQpCaW5nIExpdQ0KQm9yamUgT2hs
bWFuDQpDYXJsIE1vYmVyZw0KQ2FybG9zIE1hcnRpbmV6DQpDZW5naXogQWxhZXR0aW5vZ2x1DQpD
aGFybGVzIEVja2VsDQpDaGFybGVzIFBlcmtpbnMNCkNocmlzIEJvd2Vycw0KQ2hyaXN0ZXIgSG9s
bWJlcmcNCkNocmlzdGlhbiBIdWl0ZW1hDQpDaHJpc3RpYW4gTydGbGFoZXJ0eQ0KQ29uZyBMaXUN
CkNvcmlubmEgU2NobWl0dA0KQ3VsbGVuIEplbm5pbmdzDQpEYW1pZW4gU2F1Y2V6DQpEYW5pZWxl
IENlY2NhcmVsbGkNCkRhcGVuZyBMaXUNCkRhdmlkIENvbnJhZA0KRGF2aWQgTGFtcGFydGVyDQpE
YXZpZCBNYW5kZWxiZXJnDQpEYXZpZCBTaW5pY3JvcGUNCkRlYW4gQm9nZGFub3ZpYw0KRGVyZWsg
QXRraW5zDQpEaHJ1diBEaG9keQ0KRGltaXRyaSBQYXBhZGltaXRyaW91DQpEb25hbGQgRWFzdGxh
a2UgM3JkDQpFZHdhcmQgTGVtb24NCkVsaW90IExlYXINCkVtaWwgSXZvdg0KRXJpYyBHcmF5DQpF
cmljIFZ5bmNrZQ0KRmFuZ3dlaSBIdQ0KRmVybmFuZG8gR29udA0KRnJlZCBCYWtlcg0KR2Vvcmdl
IE1pY2hhZWxzb24NCkdlb3JnZSBTd2FsbG93DQpHZW9yZ2lvcyBLYXJhZ2lhbm5pcw0KR29uemFs
byBTYWxndWVpcm8NCkdyZWdvcnkgTWlyc2t5DQpIYW5uZXMgR3JlZGxlcg0KSG9uZ3l1IExpDQpI
dWFpbW8gQ2hlbg0KSWduYXMgQmFnZG9uYXMNCkphc29uIFdlaWwNCkplYW4tTWFyYyBWYWxpbg0K
SmVhbi1NaWNoZWwgQ29tYmVzDQpKZXN1cyBNYXJpYSBNYXJ0aW4gR2FyY2lhDQpKb2VsIEhhbHBl
cm4NCkpvaG4gQnJhZGxleQ0KSm9obiBCcnpvem93c2tpDQpKb2huIERyYWtlDQpKb2huIE1hdHRz
c29uDQpKb2huIFNjdWRkZXINCkpvbiBIdWRzb24NCkpvbiBNaXRjaGVsbA0Kam91bmkga29yaG9u
ZW4NCkthcmVuIE8nRG9ub2dodWUNCktlaXRoIE1vb3JlDQpLZW5uZXRoIEdyYXkNCktlbnQgV2F0
c2VuDQpLZXBlbmcgTGkNCktleXVyIFBhdGVsDQpMYXVyZW50IENpYXZhZ2xpYQ0KTGVlIEhvd2Fy
ZA0KTGlhbmcgWGlhDQpMaW5kYSBEdW5iYXINCkxpbmdsaSBEZW5nDQpMaXhpYSBaaGFuZw0KTHVj
eSBMeW5jaA0KTHVpZ2kgSWFubm9uZQ0KTWFjaCBDSEVODQpNYWdudXMgV2VzdGVybHVuZA0KTWFo
YWxpbmdhbSBNYW5pDQpNYXJrIFRvd25zbGV5DQpNYXR0aGV3IEJvY2NpDQpNYXR0aGV3IExlcGlu
c2tpDQpNZWhtZXQgRXJzdWUNCk1pY2hhZWwgSm9uZXMNCk1pY2hhZWwgU3RKb2hucw0KTWluIFll
DQpuYWxpbmkgZWxraW5zDQpOYW5jeSBDYW0tV2luZ2V0DQpOYXRoYW4gRWdnZQ0KTmllbCBIYXJw
ZXINCk5pbmcgS29uZw0KTmluZyBab25nDQpPbGUgSmFjb2JzZW4NCk9sZSBUcsO4YW4NClBhc2Nh
bCBUaHViZXJ0DQpQYXRyaWNrIE1jTWFudXMNClBhdWwgV291dGVycw0KUGVuZyBGYW4NClBldGVy
IEtvY2gNClBldGVyIFllZQ0KUMOlbC1FcmlrIE1hcnRpbnNlbg0KUUlOIFdVDQpSaWNoIFNhbHoN
ClJpY2hhcmQgQmFybmVzDQpSb2JieSBTaW1wc29uDQpSb24gQm9uaWNhDQpSb3NzIENhbGxvbg0K
U2FsdmF0b3JlIExvcmV0bw0KU2FtIEsuIEFsZHJpbg0KU2FuamF5IE1pc2hyYQ0KU2NvdHQgTWFu
c2ZpZWxkDQpTaGVuZyBKaWFuZw0KU0hVQ0hFTkcgTElVDQpTaW1vbiBQZXJyZWF1bHQNClNyaSBH
dW5kYXZlbGxpDQpTdGVwaGFuIFdlbmdlcg0KU3RlcGhlbiBLZW50DQpTdGV2ZSBEb25vdmFuDQpT
dGV2ZSBPbHNoYW5za3kNClN0ZXZlbiBXcmlnaHQNClN1aGFzIE5hbmRha3VtYXINClN1cmVzaCBL
cmlzaG5hbg0KU3VzYW4gSGFyZXMNClRob21hcyBOYWRlYXUNClRob21hcyBXYWxzaA0KVGltIFdp
Y2luc2tpDQpUaW1vdGh5IFRlcnJpYmVycnkNClRpbmEgKFRpbmcpIFRzb3UgKFpvdSkNClRJUlVN
QUxFU1dBUiBSRUREWSBLT05EQQ0KVG9iaWFzIEdvbmRyb20NClRvZXJsZXNzIEVja2VydA0KVG9t
b2hpcm8gRnVqaXNha2kNClRvbnkgSGFuc2VuDQpVbWEgQ2h1bmR1cmkNClZpYyBMaXUNClZpamF5
IEd1cmJhbmkNCldhcnJlbiBLdW1hcmkNCldhc3NpbSBIYWRkYWQNCldpam5hbmRzIElKc2JyYW5k
DQpYdWZlbmcgTGl1DQpZaSBaaGFvDQpZaWhvbmcgSHVhbmcNCllpemhvdSBMaQ0KWXVhbmxvbmcg
SmlhbmcNClpoYW9odWkgWmhhbmcNCg0KDQo=


From nobody Mon Jun 15 18:38:32 2015
Return-Path: <qinxiaowei@cnnic.cn>
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 560311A6EED for <tsvwg@ietfa.amsl.com>; Mon, 15 Jun 2015 18:38:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level: 
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, 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 Ke9qq4au4cSZ for <tsvwg@ietfa.amsl.com>; Mon, 15 Jun 2015 18:38:29 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id BECB41A1A8D for <tsvwg@ietf.org>; Mon, 15 Jun 2015 18:38:28 -0700 (PDT)
Received: from CNNIC-PC (unknown [218.241.119.126]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0BpcJQEfn9V8SlwBw--.4009S2; Tue, 16 Jun 2015 09:38:12 +0800 (CST)
Date: Tue, 16 Jun 2015 09:38:06 +0800
From: "qinxiaowei@cnnic.cn" <qinxiaowei@cnnic.cn>
To: david.black <david.black@emc.com>,  gorry <gorry@erg.abdn.ac.uk>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 136[cn]
Mime-Version: 1.0
Message-ID: <2015061609380655266421@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart165504658223_=----"
X-CM-TRANSID: AQAAf0BpcJQEfn9V8SlwBw--.4009S2
X-Coremail-Antispam: 1UD129KBjvdXoW7GFyUJw1fWr4ftF1fAFW5ZFb_yoWftrgE9r ya9Fy09w4qkF4xKr4SkFyagFnag397K3WUtrWDWFnxXryrZF4DJrnrW3Z3Xw1fXr4UXwn0 gFnFga48uw43WjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUbBxFF20E14v26r1j6r4UM7CY07I20VC2zVCF04k26cxKx2IYs7xG 6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rwA2F7IY1VAKz4vEj48ve4kI8w A2z4x0Y4vE2Ix0cI8IcVAFwI0_Ar0_tr1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Cr0_ Gr1UM28EF7xvwVC2z280aVAFwI0_Gr1j6F4UJwA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_Cr 1j6rxdM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVC2j2CEjI02ccxYII8I67AEr4CY 67k08wAqx4xG6I8I3I0E8cIF7480aVAKz4kxMcIj6xIIjxv20xvE14v26r1j6r18McIj6I 8E87Iv67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lF7I2 1c0EjII2zVCS5cI20VAGYxC7M4xvF2IEb7IF0Fy264kE64k0F24lc7CjxVAKzI0EY4vE52 x082I5MxkIecxEwVAFwVWkMxAIw28IcxkI7VAKI48JMxC20s026xCaFVCjc4AY6r1j6r4U MI8I3I0E5I8CrVAFwI0_JrI_JrWlx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67 AKxVWUAVWUtwCIc40Y0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0 cI8IcVCY1x0267AKxVWUJVW8JwCI42IY6xAIw20EY4v20xvaj40_WFyUJVCq3wCI42IY6I 8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E14v26r1j6r4UMVCEFcxC0VAYjxAx ZFUvcSsGvfC2KfnxnUUI43ZEXa7VUUPfQtUUUUU==
X-CM-SenderInfo: xtlq5x5drzvxw6fq0xffof0/
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/rfQtO8fjIxMaOsBSwSWSnfLi200>
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] Agenda request for the TSVWG meeting in Prague
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, 16 Jun 2015 01:38:31 -0000

This is a multi-part message in MIME format.

------=_001_NextPart165504658223_=----
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

RGVhciBHb3JyeSAmIERhdmlkLCANCg0KSSB3b3VsZCBsaWtlIHRvIGhhdmUgYSAxNS1taW51dGUg
dGltZSBzbG90ICB0byBwcmVzZW50IHRoZSBVQVROIHRvIG91ciBmb2xrcyBpbiB0aGUgUHJhZ3Vl
IElFVEYgbWVldGluZy4gDQogIEkgaGF2ZSBhbHJlYWR5IHByb3Bvc2VkIGFuIGFwcHJvYWNoIHRv
IFVwbG9hZCBBY2NlbGVyYXRpb24gVHJhbnNwb3J0IE5ldHdvcmsoVUFUTikgZm9yIHVwc3RyZWFt
IHRyYWZmaWNzLCBhbmQgdGhlIGRyYWZ0cyB3YXMgc3VibWl0dGVkLiAgDQogICBUaGlzIGlzIHRo
ZSBsaW5rLCBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1xaW4tdHN2d2ct
dWF0bnV0Lw0KDQpSZWdhcmRzLA0KWGlhb3dlaSBRaW4NCg0KDQoNCkl0IGlzIHRpbWUgdG8gc3Rh
cnQgYnVpbGRpbmcgdGhlIFRTVldHIG1lZXRpbmcgYWdlbmRhIGZvciB0aGUgUHJhZ3VlIElFVEYK
bWVldGluZy4KwpUgQXMgdXN1YWwsIGlmIHlvdSBlZGl0IGEgV0cgZHJhZnQsIHBsZWFzZSBjb250
YWN0IHRoZSBjaGFpcnMgYW5kIGxldCB1cwprbm93IHdoZXRoZXIgd2Ugc2hvdWxkIGV4cGVjdCBh
IHNob3J0IHVwZGF0ZSBvciB3aGV0aGVyIHlvdSB0aGluayB5b3UKY291bGQgYmVuZWZpdCBmcm9t
IGEgbG9uZ2VyIHNsb3QgdG8gZGlzY3VzcyBpc3N1ZXMuCsKVIElmIHlvdSB3b3VsZCBsaWtlIHRv
IHByZXNlbnQgb3RoZXIgd29yayBpbiB0c3Z3ZywgcGxlYXNlIHNlbmQgYW4gZW1haWwKdG8gdGhl
IENoYWlycyBhc2FwIC0gc28gdGhpbmdzIGNhbiBiZSBkaXNjdXNzZWQgb24gdGhlIGxpc3QgcHJp
b3IgdG8gdGhlCm1lZXRpbmcuTm90ZTogcGxlYXNlIGJlIHN1cmUgdG8gZW1iZWQgInRzdndnImlu
IHRoZSBmaWxlbmFtZSBvZiBhbGwgbmV3CmRyYWZ0cy4KUGxlYXNlIHNlbmQgcmVxdWVzdHMgYXMg
c29vbiBhcyBwb3NzaWJsZS4KVGhhbmtzIQpHb3JyeSAmIERhdmlkCih0c3Z3ZyBDby1DaGFpcnMp
DQoNCg0K

------=_001_NextPart165504658223_=----
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3Dutf-8"><style>body { line-height: 1.5; }body { font-size: 10.5pt; font=
-family: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91; color: rgb(0, 0, 0); line-h=
eight: 1.5; }</style></head><body>=0A<div><span></span><div>Dear&nbsp;<spa=
n style=3D"line-height: inherit; white-space: pre-wrap;">Gorry &amp; David=
, </span></div><div><span style=3D"font-size: 10.5pt; line-height: inherit=
; background-color: window; white-space: pre-wrap;"><br></span></div><div>=
<span style=3D"font-size: 10.5pt; line-height: inherit; background-color: =
window; white-space: pre-wrap;"> I would like to have a 15-minute time slo=
t </span><span style=3D"font-size: 10.5pt; line-height: 1.5; background-co=
lor: window;">&nbsp;</span><span style=3D"font-size: 10.5pt; line-height: =
1.5; background-color: window;">to&nbsp;</span><span style=3D"font-size: 1=
0.5pt; line-height: inherit; background-color: window; white-space: pre-wr=
ap;">present the </span><span style=3D"font-size: 10.5pt; line-height: 1.5=
; background-color: window;">UATN to our folks&nbsp;</span><span style=3D"=
font-size: 10.5pt; line-height: inherit; background-color: window; white-s=
pace: pre-wrap;">in the Prague IETF meeting.&nbsp;</span></div><div><span =
style=3D"font-size: 10.5pt; line-height: 1.5; background-color: window;"><=
span style=3D"white-space: pre-wrap;">&nbsp;   </span>I have already propo=
sed an approach to U</span><span style=3D"font-size: 10.5pt; line-height: =
1.5; background-color: window;">pload Acceleration Transport Network(UATN)=
 for upstream traffics, and&nbsp;</span><span style=3D"font-size: 10.5pt; =
line-height: 1.5; background-color: window;">the drafts was submitted. &nb=
sp;</span></div><div><span style=3D"font-size: 10.5pt; line-height: 1.5; b=
ackground-color: window;">&nbsp; &nbsp;This is the link,&nbsp;</span><span=
 style=3D"font-size: 10.5pt; line-height: 1.5; background-color: window;">=
https://datatracker.ietf.org/doc/draft-qin-tsvwg-uatnut/</span></div><bloc=
kquote style=3D"margin-top: 0px; margin-bottom: 0px; margin-left: 0.5em;">=
<div class=3D"FoxDiv20150616091628531109"><div><div><div><br></div></div><=
div>Regards,</div></div><div>Xiaowei Qin</div></div></blockquote></div><di=
v><br></div><div><br></div><div><br></div>=0A<div><pre class=3D"wordwrap" =
style=3D"margin-bottom: 0px; padding: 0px; border: 0px; font-family: Couri=
er, 'Courier New', monospace; font-size: 13px; font-stretch: inherit; line=
-height: inherit; vertical-align: baseline; white-space: pre-wrap; word-wr=
ap: break-word;">It is time to start building the TSVWG meeting agenda for=
 the Prague IETF=0Ameeting.=0A=C2=95 As usual, if you edit a WG draft, ple=
ase contact the chairs and let us=0Aknow whether we should expect a short =
update or whether you think you=0Acould benefit from a longer slot to disc=
uss issues.=0A=C2=95 If you would like to present other work in tsvwg, ple=
ase send an email=0Ato the Chairs asap - so things can be discussed on the=
 list prior to the=0Ameeting.Note: please be sure to embed "tsvwg"in the f=
ilename of all new=0Adrafts.=0APlease send requests as soon as possible.=
=0AThanks!=0AGorry &amp; David=0A(tsvwg Co-Chairs)</pre></div><hr style=3D=
"width: 210px; height: 1px; display: none;" color=3D"#b5c4df" size=3D"1" a=
lign=3D"left">=0A<div><span></span></div>=0A</body></html>
------=_001_NextPart165504658223_=------



From nobody Tue Jun 16 01:32:56 2015
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 8C1AF1A8764 for <tsvwg@ietfa.amsl.com>; Tue, 16 Jun 2015 01:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 HGRirOaseAak for <tsvwg@ietfa.amsl.com>; Tue, 16 Jun 2015 01:32:50 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 0673C1A6EE6 for <tsvwg@ietf.org>; Tue, 16 Jun 2015 01:32:50 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 664051B0024A for <tsvwg@ietf.org>; Tue, 16 Jun 2015 09:32:52 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Tue, 16 Jun 2015 09:31:45 +0100
Message-ID: <8516948da62467bc10e344ceb920ef87.squirrel@erg.abdn.ac.uk>
Date: Tue, 16 Jun 2015 09:31:45 +0100
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
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/v8vccIThEbSENBrF_neHNNMHGI4>
Subject: [tsvwg] TSVWG Status Update June 2015
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, 16 Jun 2015 08:32:53 -0000

The list below shows the WG Chairs view of the status of the TSV working
group documents as we see it. Please check below and comment on drafts
using the list. Please do send any corrections/omissions to the chairs.

Gorry & David
(TSVWG Chairs)
June 2015

-------------------------------------------------------------------
Document recently published:

RFC 7496 draft-ietf-tsvwg-sctp-prpolicies - Additional Policies for the
Partially Reliable Stream Control Transmission Protocol Extension -
Document Shepherd: Gorry
-------------------------------------------------------------------
IDs in RFC Editor Queue (http://www.rfc-editor.org/queue.html) :

draft-ietf-tsvwg-sctp-dtls-encaps - PS - Document Shepherd: Gorry
Replaces: draft-tuexen-tsvwg-sctp-dtls-encaps-01
WG adopted 13/12/2013. Support {AB, IR, SL, MB, TD}
[Milestone: Jan 2014, PS] Implemented in Firefox (FF21).
Required by RTCweb. Comments received.
WGLC ended 28th February 2014.
Comments from Joe Touch (draft updated)
Review comments and revised ID published.
Eric Rescorla has reviewed this.
All authors confirmed no IPR
Write-up submitted, Comments and revised ID.
IESG evaluation: Completed.
RFC Editor: MISSREF - waiting for draft-ietf-tsvwg-ndata
---
draft-ietf-tsvwg-port-use - Document Shepherd: Gorry
Replaces: draft-touch-tsvwg-port-use-00
- Intended to be advice to protocol designers needing a port.
5 people looked at this document, Prague IETF-80
Individual -01 July 2011
IETF-81 insufficient feedback from WG at this time.
IETF-82, discussed.
Adopted by WG Presented IETF-86, March 2013
Milestone updated to June 2014
Mar 2014, Chairs WGLC to be started after current WG actions.
- IANA review comments received
- Sent review requests to RAI, APPS, and SEC areas during 1st WGLC.
+ Comments May 2014: Paul Hoffman; Lars Eggert; IANA; David Black;
5 Jun 2014, WGLC completed - comments received.
Revised ID after WGLC; Elliot OK with changes;
Working Group Last Call for comments 14/10/2014, concluded 29/10/2014:
Reviewers EL, GF, DB.
All appropriate IPR disclosures have been declared 30-10-2014.
Write-up submitted. LC comments received, and revised ID submitted.
IESG evaluation: On agenda of 2015-02-19 IESG telechat, discuss to be
resolved.
Approved for publication 5th May 2015
----------------------------------------------------------
IDs in IESG evaluation:
---
None
-------------------------------------------------------------------
WG Drafts with Chairs:
-------------------------------------------------------------------
Awaiting WGLC:
Review needed by D. Black:
draft-ietf-tsvwg-rfc5405bis - BCP -  Document Shepherd: David
formerly draft-eggert-tsvwg-rfc5405bis - Individual,  ‘Multicast UDP
Guidelines’ incorporated
Mar 2014, the ADs proposed the WG re-open the UDP Guidelines RFC for
update to include this work and other topics.
The authors of both drafts agreed to progress this work.
Presented IETF-90, Hum supporting adoption, none against.
++ Brian Trammel agreed to review this.
++ Jana agreed to review this.
++ Magnus Westerlund agreed to review this (comments)
Adopted as a TSVWG work item.
DUE: Please comment on list (revised ID needed)
---
Review needed by D. Black:
draft-ietf-tsvwg-circuit-breaker - BCP - Document Shepherd: David
- (Editor: Gorry Fairhurst)
Call for WG adoption issued - August 2014, adopted 28th Aug.
Current target is BCP, will re-evaluate (BCP vs. INFO) when draft is ready
for WGLC.
++ Colin Perkins to be asked to review.
DUE: Revised ID needed after Dallas IETF (Comments)
DUE: WGLC expected - please comment on list.

-------------------------------------------------------------------
WG Drafts
---
draft-ietf-tsvwg-sctp-failover - Document Shepherd: Gorry
Replaces: draft-nishida-tsvwg-sctp-failover
Individual-00 Presented in Prague, IETF-80.
- Understood not to conflict with draft-tuexen-tsvwg-sctp-multipath
- PF has been implemented in FreeBSD; Linux SCTP implements partially,
that they intend to implement full support and have no comments to the
technical solution; Ericsson have an implementation;
Adopted by WG 26/6/2012. [Milestone: Jul 2013, EXP]
Thought ready for WGLC, four people volunteered to review.
Review done by GF with a view to the milestone becoming PS.
++ Committed reviewers : Michael Tuexen (more if possible)
Milestone request submitted to AD/IESG
Implementation status:
PF has been coded into FreeBSD.
This feature is supported in Ericsson in-house SCTP SW implementation.
It is partially implemented in Linux SCTP SW (July 2014) with the intent
to implement.
WGLC concluded 19th November, 2014. No issues with protocol design.
Revised ID issued after Shepherd review. Protocol spec reviewed by M Tuexen.
DUE: Revised ID needed with editorial work needed on protocol spec and be
sure this is unambiguous (reminder sent: 11-Jun-2015).
DUE: Writeup being prepared by shepherd (confirming WGLC will be needed).
---
draft-ietf-tsvwg-sctp-ndata - PS - Document Shepherd: Gorry
- replaces: draft-stewart-tsvwg-sctp-ndata-03 Nov 2013,
Adopted , intended for publication as a PS RFC
Mar 2014, 5-6 people had read.
Name was changed (proposed at IETF-90), Interleaved data
Header was made smaller.
Work needed:
• Describe how it works! (Possible Errata to fix RFC 4960)
• Describe Stream Schedulers
–  Address comments received on the mailing list.
• Clarification of use-case.
• Make clear what also applies when regular DATA chunks are used.
++ Magnus Westerlund will review
++ Karen Neilson will review
DUE: Revised ID needed (expected June or early July 2015)
DUE: WGLC expected after next revision - please comment on list.
---
draft-tsvwg-gre-in-udp-encap - PS - Document Contact: Gorry (Document
Shepherd: David)
- replaces: draft-yong-tsvwg-gre-in-udp-encap
Dec 2013, Adopted , intended for publication as a PS RFC
Feb 2014, discussion of scope and applicability of circuit breakers
Mar 2014 consider MUST implement, SHOULD use in these environments for CB
Revised ID expected for Dallas (was Honolulu) with initial adaptation and
discuss generalization in meeting.
DUE: Revised ID needed to address congestion control and UDP Zero Checksum
for IPv6.  Revised text has been adapted from MPLS-in-UDP RFC 7510, but
needs further adaptation for GRE (vs. MPLS).
DUE: Scope of deployability to be discussed with decision on how to
proceed (for Prague meeting)
---
draft-ietf-tsvwg-diffserv-intercon - Info- Document Contact: David
(Document Shepherd: Gorry)
formerly: draft-geib-tsvwg-diffserv-interco
DiffServ interconnection classes
New ID presented in Atlanta, IETF-85.
ID presented in Orlando, IETF-86, Mar 2013. Mar 2014, intended scope
unclear at IETF London Adoption call to be considered, but scope needs to
be first refined and a revised draft is necessary to avoid implications of
broader applicability.
July 2014 - ID presented in Toronto. Strong hum of support to work on
this, but a revised draft is needed first.
WG adoption call completed 2014-12-01.
DUE: Please comment on list (revised ID needed)
---
draft-ietf-tsvwg-ecn-encap-guidelines - Document Shepherd: David
replaced draft-briscoe-tsvwg-ecn-encap-guidelines
-00 Presented in Prague, IETF-80.
- comments at IETF-80 (see minutes)
New ID presented in Atlanta, IETF-85. ID presented in IETF-88,89
-  forward an appropriate message (perhaps your note to the mailing list
for approval to adopt) to ieee-ietf-coord@ietf.org)
++ Reviewers: Andrew McGregor, Dirk Kutscher, Richard Sheffnegger, Brian
Trammell, Gorry.
Mar 2014, WG Call for adoption started, to end 4th March 2014
19 for, 1 against. 8 echoed on the list
Adoption call concluded and document adopted.
- ecn-encap-guidelines and AQM are the main new things they need to know
about.
on <http://www.ietf.org/proceedings/86/train-3.html>IEEE802.1Q)
Liaison sent to IEEE 802 (Nov  24, 2014).
DUE: Liaison to be sent to 3GPP (June 2015).
DUE: Revised ID needed, next version to be presented to IETF INT Area.
DUE: Please comment on list.
---
draft-ietf-tsvwg-natsupp - Document Shepherd: David
Replaces: draft-stewart-natsupp-tsvwg
Dependency from BEHAVE WG (no longer applicable).
Adopted as a work item 21 Sept 2010 (Gorry).
WG -00, 29/11/2010 Uploaded as: draft-ietf-natsupp-tsvwg
Authors restructured draft (-03)
Added support for single and multi-homed support.
IETF-86: 3 people in meeting had read -04 or -05.
Feb 2014, Authors please update following comments and align to related
draft on SCTP NAT (conflicts found in language)
Authors expected to produce a single document to replace both.
++ Dan Wing has committed to review this.
++ Fred Baker has committed to review this.
Separated the simpler case for single-homed use - this separation should
be clear.
March 2015 document restructured and merged with draft-ietf-tsvwg-sctpnat
March 2015, initial review by Gorry - need to consider helping NAT vendors
access the recommendations.
Comments from Gorry, Karen with Minor NiTs
DUE: Revised ID-needed.
Chairs Note: Plan to start a WGLC, once text is stable.
---
draft-ietf-tsvwg-behave-requirements-update - Document Shepherd: David
Replaces: draft-ietf-behave-requirements-update-00
Nov 2013, Former BEHAVE WG work item intended for publication as a BCP
Mar 2014, Irene R reviewed this and found no conflict with SCTP drafts.
Some suggestions (in no particular order) for a shepherd:
++ Dave Thaler, may review, as former behave co-chair
++ David Harrington, has been around in behave, and he knows how to do
this and volunteered multiple times.
++ Ask Jana to review this.
++ Dan has committed to review this.
Chairs: Check intention and planned timeline.
DUE: Please comment on list
-------------------------------------------------------------------
Expired WG documents:
---
draft-ietf-tsvwg-intserv-multiple-tspec - Document Shepherd: David
WG interest in this topic recorded at IETF-78.
Charter update needed to progress this work.
5 Reviews needed to determine energy/technical direction.
WG -05 (presented in Beijing, IETF-79)
WG -06 (presented in Prague, IETF-80)
2 reviews from RSVP-DIR received (Bruce Davie, ?)
2 additional reviews promised (Ken Carlberg, Francois LeF)
Chairs asked AD for a Charter update (IESG agreed)
Draft discussed at IETF-80, and request to update charter agreed
- AD advised 4 named reviewers will be required
Adopted for progression as PS, for May 2012
- New name: 'RSVP Multiple Instance'.
Draft is now expired and dead.
Draft authors will request replacement with
draft-polk-rsvp-multi-instance-object (and WG adoption call for that draft
in Honolulu, IETF-91)
---
draft-ietf-tsvwg-rsvp-app-id-vv-profiles - Document Shepherd: David
Replaces: draft-polk-tsvwg-rsvp-app-id-vv-profiles
-01 Presented in Beijing, IETF-79.
-02, 14-Mar-2011
Presented IETF-80.
Seek to coordinate with music with partner ID:
draft-polk-mmusic-traffic-class-for-sdp
Gorry liaised with MMUSIC WG Chairs on companion draft (norm ref from this
tsvwg draft).
Adopted as a TSVWG work item, December 2013, [Milestone Jul 2013].
This will update a RFC 2872 (PS).
Presented at IETF-86,
Mar 2013 (no comments)
Expected ready for WGLC (waiting on MMUSIC)
DUE: Reviewers are needed to prepare for a WGLC (expired)
---
draft-ietf-tsvwg-rtcweb-qos - PS - Document Shepherd: David
- Replaces: draft-dhesikan-tsvwg-rtcweb-qos
- RTCweb and QoS Markings
- Authors requested TSVWG adoption.
- Who has read the draft? (lots 10's of people)
25-Mar-2014, Adopted by tsvwg
- Who thinks it is important to do work in the IETF? (Many)
I-D updated after initial TSVWG feedback
Mar 2014, Adoption call (strong support in WG meeting London)
Adoption call concluded 24 Match 2014: intended as a PS RFC for Sept 2014
++ Magnus agreed to review this.
Early OPS-Dir review received from Fred Baker.
Related draft Oct 2014, DART draft (draft-ietf-dart-dscp-rtp): IETF LC
completed.
DUE: Revised draft (David had concall w/authors on Jan 22).  Current draft
has expired.
---
-------------------------------------------------------------------
The following have received recent discussion at TSVWG meetings or on
the list. Inclusion in the list below does not indicate support for
these specific drafts and other contributions are also warmly welcomed.
---------------------------------------------------------------

Authors have request to be considered for adoption:
---
draft-wing-tsvwg-turn-flowdata-00.txt
- Individual (no decision to adopt at this time)
- QoS-aspects to be discussed in tsvwg (thought to also be relevant to
TURN WG)
Comments welcome on tsvwg list.
----
draft-wei-tsvwg-tunnel-congestion-feedback
- Thought to fall within TSVWG charter, comments welcome on tsvwg list.
- IETF 91: Authors will work w/Bob Briscoe, who has a related individual
draft for conex, on feedback mechanisms.  Goal is concrete action taken
based on detected problems that can be used from other drafts by
reference.  Also have to deal with possibility of dropped packets within
tunnel.
---
draft-lai-tsvwg-normalizer
- Thought to fall within TSVWG charter
- Presented IETF-88, comments welcome on tsvwg list.
---
Other drafts and work items linked to TSVWG:
---
draft-ietf-tsvwg-sctpnat - Document Shepherd: Gorry
Will replace: draft-ietf-behave-sctpnat-03.txt Adopted Nov 2013.
Former BEHAVE WG work item that defines SCTP NAT support
Feb 2014, Author update following comments and align to related draft on
SCTP NAT (conflicts found in language)
Chairs: - authors have requested a single document to replace both.
Document replaced by: draft-ietf-tsvwg-natsupp
---
Liaisons:
ITU-T Study Group 12 Liaison on QoS Classes & markings for interconnection
IEEE liaison to support L2/L3 work on ECN marking
3GPP liaison to support L2/L3 work on ECN marking
=====================================================================


From nobody Tue Jun 16 13:54:11 2015
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 372451B34ED for <tsvwg@ietfa.amsl.com>; Tue, 16 Jun 2015 13:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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, 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 OuUb0JzJWXXy for <tsvwg@ietfa.amsl.com>; Tue, 16 Jun 2015 13:54:07 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 283EC1B34EC for <tsvwg@ietf.org>; Tue, 16 Jun 2015 13:54:06 -0700 (PDT)
Received: from maildlpprd52.lss.emc.com (maildlpprd52.lss.emc.com [10.106.48.156]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t5GKrude026338 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 16 Jun 2015 16:53:57 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com t5GKrude026338
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1434488037; bh=0DbxPzm/iTQq4/5XK8GfVb5BzmU=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=H8xzh+/XZBPpF49EDNvnj5YFAl8L/+Iz96nA8BnoyFvIi0gsCaZp4ho6Dd8rUf0W5 /GUOCBC4vMXOOO0i8JZ+WZBHO8lzyhu+WtlxCZ8ATfZVBQL3eUjRxnmTNGXSTPjS3s 8DPAD+VdgfdkNs7KUMBABagv66H57g9s1wVMf/wM=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com t5GKrude026338
Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd52.lss.emc.com (RSA Interceptor); Tue, 16 Jun 2015 16:54:09 -0400
Received: from mxhub22.corp.emc.com (mxhub22.corp.emc.com [128.222.70.134]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t5GKrciQ032487 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 16 Jun 2015 16:53:38 -0400
Received: from MXHUB102.corp.emc.com (10.253.58.15) by mxhub22.corp.emc.com (128.222.70.134) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 16 Jun 2015 16:53:37 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.123]) by MXHUB102.corp.emc.com ([::1]) with mapi id 14.03.0224.002; Tue, 16 Jun 2015 16:53:37 -0400
From: "Black, David" <david.black@emc.com>
To: "qinxiaowei@cnnic.cn" <qinxiaowei@cnnic.cn>
Thread-Topic: Re:[tsvwg] Agenda request for the TSVWG meeting in Prague
Thread-Index: AQHQp9UhLNO+9bUrx0u5zaFEA+QEXZ2vkysg
Date: Tue, 16 Jun 2015 20:53:37 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949360B3796CF@MX104CL02.corp.emc.com>
References: <2015061609380655266421@cnnic.cn>
In-Reply-To: <2015061609380655266421@cnnic.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.57]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D243277949360B3796CFMX104CL02corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd53.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/XppSKjeItVzGHsx1Rui5wt5RTb0>
Cc: gorry <gorry@erg.abdn.ac.uk>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] Agenda request for the TSVWG meeting in Prague
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, 16 Jun 2015 20:54:10 -0000

--_000_CE03DB3D7B45C245BCA0D243277949360B3796CFMX104CL02corpem_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

RGVhciBYaWFvd2VpLA0KDQpGaXJzdCBvZiBhbGwsIHdlIChXRyBjaGFpcnMpIHdhbnQgdG8gdGhh
bmsgeW91IGZvciBzZXR0aW5nIGEgZ29vZCBleGFtcGxlDQpvZiBob3cgdG8gZ28gYWJvdXQgYnJp
bmdpbmcgaWRlYXMgZm9yIG5ldyB3b3JrIHRvIHRoZSBJRVRGLiAgVGhlIC0wMA0KVUFUTiBkcmFm
dCB3YXMgc3VibWl0dGVkIHdlbGwgYmVmb3JlIHRoZSAyLXdlZWsgcHJlLW1lZXRpbmcgY3V0b2Zm
LA0KdGhlIHN1Ym1pc3Npb24gd2FzIGFubm91bmNlZCB0byB0aGUgcmVsZXZhbnQgbWFpbGluZyBs
aXN0cywgYW5kIHRoZXJl4oCZcw0KYmVlbiBzb21lIGRpc2N1c3Npb24gb24gdGhlIGxpc3RzLg0K
DQpBbGwgb2YgdGhvc2Ugc3RlcHMgYXJlIGFwcHJlY2lhdGVkLCBhbmQgYXJlIG11Y2ggYmV0dGVy
IHRoYW4gdGhlDQphbHRlcm5hdGl2ZSBhcHByb2FjaCBvZiBzdWJtaXR0aW5nIGEgLTAwIGRyYWZ0
IHJpZ2h0IGF0IHRoZSAyLXdlZWsNCnByZS1tZWV0aW5nIGN1dG9mZiBhbmQgdGhlbiBpbW1lZGlh
dGVseSBhc2tpbmcgZm9yIGFnZW5kYSB0aW1lLiAgVGhlDQpXRyBjaGFpcnMgdXN1YWxseSB0dXJu
IGRvd24gdGhlIGxhdHRlciBzb3J0IG9mIHJlcXVlc3QsIGFzIHdlIHdhbnQgdG8NCnNlZSBzb21l
IGxldmVsIG9mIGludGVyZXN0IGluIHRoZSBwcm9wb3NlZCBhY3Rpdml0eSBiYXNlZCBvbiBsaXN0
DQpkaXNjdXNzaW9uLg0KDQpUdXJuaW5nIHRvIHRoZSBVQVROIGRyYWZ0IGl0c2VsZiwgd2UgKFdH
IGNoYWlycykgaGF2ZSBhIGZldyBjb25jZXJuczoNCg0KLSBXZeKAmXJlIG5vdCBzdXJlIHdoZXRo
ZXIgdGhpcyBkcmFmdCBiZWxvbmdzIGluIHRoZSBUU1YgQXJlYSB2cy4gdGhlIEFSVA0KICAgICAg
QXJlYS4gIEFzIGEgQ0ROLXJlbGF0ZWQgZHJhZnQsIGl0IG1heSBiZWxvbmcgb3ZlciBpbiBBUlQs
IGF0IHRoYXTigJlzDQp0aGUgSUVURiBBcmVhIGludG8gd2hpY2ggdGhlIENETkkgV0cgd2FzIHJl
Y2VudGx5IG1vdmVkLg0KLSBXZSBoYXZlbuKAmXQgc2VlbiBhbnkgaW50ZXJlc3QgZXhwcmVzc2Vk
IGluIHRoaXMgd29yayBmcm9tIHBlb3BsZSBvdGhlcg0KICAgICAgdGhhbiB0aGUgYXV0aG9ycyBl
aXRoZXIgaGVyZSBvciBvbiB0aGUgYXBwcy1kaXNjdXNzIGxpc3QgKGluIEFSVCkuDQpXZeKAmWxs
IGNvbnRpbnVlIHRvIHdhdGNoIHRoZSBtYWlsaW5nIGxpc3RzLg0KLSBXZeKAmXJlIHVuY2xlYXIg
b24gd2hhdCBwcm90b2NvbCBvciBvdGhlciBzcGVjaWZpY2F0aW9uIHdvcmsgdGhlIGRyYWZ0DQpp
cyBzdWdnZXN0aW5nIHRoYXQgdGhlIElFVEYgKGFuZCBzcGVjaWZpY2FsbHkgVFNWV0cpIHVuZGVy
dGFrZSwNCmFzIFNlY3Rpb24gNCBzYXlzOg0KDQo0LiAgTmV3IFByb3RvY29sIENvbnNpZGVyYXRp
b25zDQoNCiAgIFRoaXMgZG9jdW1lbnQgZG9lcyBub3QgY2FsbCBmb3IgY2hhbmdlcyBvciBhZGRp
dGlvbnM6IGFueSBuZXcNCiAgIHNlc3Npb24sIHRyYW5zcG9ydCBvciBuZXR3b3JrIHByb3RvY29s
czsgbmV3IHByb3RvY29scyBmb3IgZGVsaXZlcmluZw0KICAgY29udGVudCBmcm9tIGEgVUFUTiB0
byBhbiBFbmQgVXNlci9Vc2VyIGFnZW50OyBuZXcgcHJvdG9jb2xzIGZvcg0KICAgaW5nZXN0aW9u
IG9mIGNvbnRlbnQgYmV0d2VlbiBhIFVBVE4gYW5kIGEgVVNQLg0KDQogICAgICAoaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXFpbi10c3Z3Zy11YXRudXQtMDAjc2VjdGlvbi00KQ0K
DQpXZeKAmWQgYXBwcmVjaWF0ZSBzb21lIGNsYXJpZmljYXRpb24gb24gdGhlIGxhdHRlciBjb25j
ZXJuLCBhbmQgd2XigJlsbA0KY29udGludWUgdG8gd2F0Y2ggbWFpbGluZyBsaXN0IGRpc2N1c3Np
b24sIGJ1dCBpdOKAmXMgbm90IGFwcHJvcHJpYXRlIHRvDQpwdXQgdGhlIFVBVE4gZHJhZnQgb24g
dGhlIHRzdndnIGFnZW5kYSBhdCB0aGlzIHRpbWUuICBUaGUgYWdlbmRhIHdpbGwNCmV2b2x2ZSBi
ZXR3ZWVuIG5vdyBhbmQgdGhlIFByYWd1ZSBtZWV0aW5nLCBzbyB0aGVyZSBtYXkgYmUgYW4gb3Bw
b3J0dW5pdHkNCnRvIGFkZCB0aW1lIGZvciB0aGUgZHJhZnQgbGF0ZXIgb24uDQoNClRoYW5rcywN
Ci0tRGF2aWQgYW5kIEdvcnJ5ICh0c3Z3ZyBjaGFpcnMpDQoNCkZyb206IHFpbnhpYW93ZWlAY25u
aWMuY24gW21haWx0bzpxaW54aWFvd2VpQGNubmljLmNuXQ0KU2VudDogTW9uZGF5LCBKdW5lIDE1
LCAyMDE1IDk6MzggUE0NClRvOiBCbGFjaywgRGF2aWQ7IGdvcnJ5DQpDYzogdHN2d2cNClN1Ympl
Y3Q6IFJlOlt0c3Z3Z10gQWdlbmRhIHJlcXVlc3QgZm9yIHRoZSBUU1ZXRyBtZWV0aW5nIGluIFBy
YWd1ZQ0KDQpEZWFyIEdvcnJ5ICYgRGF2aWQsDQoNCg0KSSB3b3VsZCBsaWtlIHRvIGhhdmUgYSAx
NS1taW51dGUgdGltZSBzbG90ICB0byBwcmVzZW50IHRoZSBVQVROIHRvIG91ciBmb2xrcyBpbiB0
aGUgUHJhZ3VlIElFVEYgbWVldGluZy4NCiAgSSBoYXZlIGFscmVhZHkgcHJvcG9zZWQgYW4gYXBw
cm9hY2ggdG8gVXBsb2FkIEFjY2VsZXJhdGlvbiBUcmFuc3BvcnQgTmV0d29yayhVQVROKSBmb3Ig
dXBzdHJlYW0gdHJhZmZpY3MsIGFuZCB0aGUgZHJhZnRzIHdhcyBzdWJtaXR0ZWQuDQogICBUaGlz
IGlzIHRoZSBsaW5rLCBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1xaW4t
dHN2d2ctdWF0bnV0Lw0KDQpSZWdhcmRzLA0KWGlhb3dlaSBRaW4NCg0KDQoNCg0KSXQgaXMgdGlt
ZSB0byBzdGFydCBidWlsZGluZyB0aGUgVFNWV0cgbWVldGluZyBhZ2VuZGEgZm9yIHRoZSBQcmFn
dWUgSUVURg0KDQptZWV0aW5nLg0KDQrigKIgQXMgdXN1YWwsIGlmIHlvdSBlZGl0IGEgV0cgZHJh
ZnQsIHBsZWFzZSBjb250YWN0IHRoZSBjaGFpcnMgYW5kIGxldCB1cw0KDQprbm93IHdoZXRoZXIg
d2Ugc2hvdWxkIGV4cGVjdCBhIHNob3J0IHVwZGF0ZSBvciB3aGV0aGVyIHlvdSB0aGluayB5b3UN
Cg0KY291bGQgYmVuZWZpdCBmcm9tIGEgbG9uZ2VyIHNsb3QgdG8gZGlzY3VzcyBpc3N1ZXMuDQoN
CuKAoiBJZiB5b3Ugd291bGQgbGlrZSB0byBwcmVzZW50IG90aGVyIHdvcmsgaW4gdHN2d2csIHBs
ZWFzZSBzZW5kIGFuIGVtYWlsDQoNCnRvIHRoZSBDaGFpcnMgYXNhcCAtIHNvIHRoaW5ncyBjYW4g
YmUgZGlzY3Vzc2VkIG9uIHRoZSBsaXN0IHByaW9yIHRvIHRoZQ0KDQptZWV0aW5nLk5vdGU6IHBs
ZWFzZSBiZSBzdXJlIHRvIGVtYmVkICJ0c3Z3ZyJpbiB0aGUgZmlsZW5hbWUgb2YgYWxsIG5ldw0K
DQpkcmFmdHMuDQoNClBsZWFzZSBzZW5kIHJlcXVlc3RzIGFzIHNvb24gYXMgcG9zc2libGUuDQoN
ClRoYW5rcyENCg0KR29ycnkgJiBEYXZpZA0KDQoodHN2d2cgQ28tQ2hhaXJzKQ0KDQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0K

--_000_CE03DB3D7B45C245BCA0D243277949360B3796CFMX104CL02corpem_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OkNvdXJpZXI7DQoJcGFub3NlLTE6MiA3IDQgOSAyIDIgNSAyIDQgNDt9
DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvdXJpZXI7DQoJcGFub3NlLTE6MiA3IDQgOSAy
IDIgNSAyIDQgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3Nl
LTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhv
bWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250
LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQpAZm9u
dC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJNaWNyb3NvZnQgWWFIZWkiOw0KCXBhbm9zZS0xOjIgMTEg
NSAzIDIgMiA0IDIgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlxATWljcm9zb2Z0
IFlhSGVpIjsNCglwYW5vc2UtMToyIDExIDUgMyAyIDIgNCAyIDIgNDt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1z
b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs
b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj
b3JhdGlvbjp1bmRlcmxpbmU7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28t
c3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJn
aW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ291
cmllciBOZXciO30NCnNwYW4uSFRNTFByZWZvcm1hdHRlZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6
IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28t
c3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQiOw0KCWZvbnQtZmFtaWx5OkNvbnNvbGFzO30N
CnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZv
bnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7DQoJZm9udC13ZWlnaHQ6bm9y
bWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0KCXRleHQtZGVjb3JhdGlvbjpub25lIG5vbmU7fQ0K
Lk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXpl
OjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFy
Z2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpX
b3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo
YXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRp
Zl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0
Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0Pjwv
eG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUi
IHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5EZWFyIFhpYW93ZWksPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
O2NvbG9yOmJsYWNrIj5GaXJzdCBvZiBhbGwsIHdlIChXRyBjaGFpcnMpIHdhbnQgdG8gdGhhbmsg
eW91IGZvciBzZXR0aW5nIGEgZ29vZCBleGFtcGxlPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPm9mIGhvdyB0byBnbyBhYm91
dCBicmluZ2luZyBpZGVhcyBmb3IgbmV3IHdvcmsgdG8gdGhlIElFVEYuJm5ic3A7IFRoZSAtMDA8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+VUFUTiBkcmFmdCB3YXMgc3VibWl0dGVkIHdlbGwgYmVmb3JlIHRoZSAyLXdlZWsg
cHJlLW1lZXRpbmcgY3V0b2ZmLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj50aGUgc3VibWlzc2lvbiB3YXMgYW5ub3VuY2Vk
IHRvIHRoZSByZWxldmFudCBtYWlsaW5nIGxpc3RzLCBhbmQgdGhlcmXigJlzPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPmJl
ZW4gc29tZSBkaXNjdXNzaW9uIG9uIHRoZSBsaXN0cy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2si
PkFsbCBvZiB0aG9zZSBzdGVwcyBhcmUgYXBwcmVjaWF0ZWQsIGFuZCBhcmUgbXVjaCBiZXR0ZXIg
dGhhbiB0aGU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZx
dW90Oztjb2xvcjpibGFjayI+YWx0ZXJuYXRpdmUgYXBwcm9hY2ggb2Ygc3VibWl0dGluZyBhIC0w
MCBkcmFmdCByaWdodCBhdCB0aGUgMi13ZWVrPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPnByZS1tZWV0aW5nIGN1dG9mZiBh
bmQgdGhlbiBpbW1lZGlhdGVseSBhc2tpbmcgZm9yIGFnZW5kYSB0aW1lLiZuYnNwOyBUaGU8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpi
bGFjayI+V0cgY2hhaXJzIHVzdWFsbHkgdHVybiBkb3duIHRoZSBsYXR0ZXIgc29ydCBvZiByZXF1
ZXN0LCBhcyB3ZSB3YW50IHRvPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291
cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPnNlZSBzb21lIGxldmVsIG9mIGludGVyZXN0IGlu
IHRoZSBwcm9wb3NlZCBhY3Rpdml0eSBiYXNlZCBvbiBsaXN0PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPmRpc2N1c3Npb24u
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29s
b3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5UdXJuaW5nIHRvIHRoZSBVQVROIGRyYWZ0IGl0c2Vs
Ziwgd2UgKFdHIGNoYWlycykgaGF2ZSBhIGZldyBjb25jZXJuczo8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPi0gV2XigJlyZSBub3Qgc3VyZSB3aGV0aGVyIHRoaXMgZHJhZnQgYmVsb25ncyBpbiB0
aGUgVFNWIEFyZWEgdnMuIHRoZSBBUlQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IEFyZWEuJm5ic3A7IEFzIGEgQ0ROLXJlbGF0ZWQgZHJhZnQsIGl0IG1heSBiZWxvbmcg
b3ZlciBpbiBBUlQsIGF0IHRoYXTigJlzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtaW5kZW50Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNr
Ij50aGUgSUVURiBBcmVhIGludG8gd2hpY2ggdGhlIENETkkgV0cgd2FzIHJlY2VudGx5IG1vdmVk
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2Nv
bG9yOmJsYWNrIj4tIFdlIGhhdmVu4oCZdCBzZWVuIGFueSBpbnRlcmVzdCBleHByZXNzZWQgaW4g
dGhpcyB3b3JrIGZyb20gcGVvcGxlIG90aGVyPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyB0aGFuIHRoZSBhdXRob3JzIGVpdGhlciBoZXJlIG9yIG9uIHRoZSBhcHBzLWRp
c2N1c3MgbGlzdCAoaW4gQVJUKS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0idGV4dC1pbmRlbnQ6LjVpbiI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPldl
4oCZbGwgY29udGludWUgdG8gd2F0Y2ggdGhlIG1haWxpbmcgbGlzdHMuPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPi0gV2Xi
gJlyZSB1bmNsZWFyIG9uIHdoYXQgcHJvdG9jb2wgb3Igb3RoZXIgc3BlY2lmaWNhdGlvbiB3b3Jr
IHRoZSBkcmFmdDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJ0ZXh0LWluZGVudDouNWluIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+aXMgc3VnZ2VzdGlu
ZyB0aGF0IHRoZSBJRVRGIChhbmQgc3BlY2lmaWNhbGx5IFRTVldHKSB1bmRlcnRha2UsPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtaW5kZW50
Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5hcyBTZWN0aW9uIDQgc2F5czo8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idGV4dC1pbmRlbnQ6LjVp
biI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmll
ciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWluZGVudDouNWluIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+NC4mbmJzcDsgTmV3IFByb3RvY29sIENvbnNpZGVyYXRpb25zPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtaW5kZW50Oi41aW4i
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idGV4dC1pbmRlbnQ6LjVpbiI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPiZuYnNwOyZuYnNwOyBUaGlzIGRvY3VtZW50IGRvZXMgbm90IGNhbGwgZm9yIGNoYW5n
ZXMgb3IgYWRkaXRpb25zOiBhbnkgbmV3PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtaW5kZW50Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNr
Ij4mbmJzcDsmbmJzcDsgc2Vzc2lvbiwgdHJhbnNwb3J0IG9yIG5ldHdvcmsgcHJvdG9jb2xzOyBu
ZXcgcHJvdG9jb2xzIGZvciBkZWxpdmVyaW5nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtaW5kZW50Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJs
YWNrIj4mbmJzcDsmbmJzcDsgY29udGVudCBmcm9tIGEgVUFUTiB0byBhbiBFbmQgVXNlci9Vc2Vy
IGFnZW50OyBuZXcgcHJvdG9jb2xzIGZvcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWluZGVudDouNWluIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFj
ayI+Jm5ic3A7Jm5ic3A7IGluZ2VzdGlvbiBvZiBjb250ZW50IGJldHdlZW4gYSBVQVROIGFuZCBh
IFVTUC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90
Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyAoPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXFpbi10c3Z3
Zy11YXRudXQtMDAjc2VjdGlvbi00Ij5odHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
cWluLXRzdndnLXVhdG51dC0wMCNzZWN0aW9uLTQ8L2E+KTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFj
ayI+V2XigJlkIGFwcHJlY2lhdGUgc29tZSBjbGFyaWZpY2F0aW9uIG9uIHRoZSBsYXR0ZXIgY29u
Y2VybiwgYW5kIHdl4oCZbGw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Y29udGludWUgdG8gd2F0Y2ggbWFpbGluZyBsaXN0
IGRpc2N1c3Npb24sIGJ1dCBpdOKAmXMgbm90IGFwcHJvcHJpYXRlIHRvPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPnB1dCB0
aGUgVUFUTiBkcmFmdCBvbiB0aGUgdHN2d2cgYWdlbmRhIGF0IHRoaXMgdGltZS4mbmJzcDsgVGhl
IGFnZW5kYSB3aWxsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBO
ZXcmcXVvdDs7Y29sb3I6YmxhY2siPmV2b2x2ZSBiZXR3ZWVuIG5vdyBhbmQgdGhlIFByYWd1ZSBt
ZWV0aW5nLCBzbyB0aGVyZSBtYXkgYmUgYW4gb3Bwb3J0dW5pdHk8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+dG8gYWRkIHRp
bWUgZm9yIHRoZSBkcmFmdCBsYXRlciBvbi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+VGhhbmtzLDxicj4NCi0tRGF2aWQgYW5kIEdvcnJ5ICh0c3Z3ZyBjaGFpcnMpPC9z
cGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1s
ZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0K
PGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3Bh
ZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+IHFpbnhpYW93ZWlAY25uaWMuY24gW21haWx0bzpxaW54aWFvd2VpQGNubmljLmNu
XQ0KPGJyPg0KPGI+U2VudDo8L2I+IE1vbmRheSwgSnVuZSAxNSwgMjAxNSA5OjM4IFBNPGJyPg0K
PGI+VG86PC9iPiBCbGFjaywgRGF2aWQ7IGdvcnJ5PGJyPg0KPGI+Q2M6PC9iPiB0c3Z3Zzxicj4N
CjxiPlN1YmplY3Q6PC9iPiBSZTpbdHN2d2ddIEFnZW5kYSByZXF1ZXN0IGZvciB0aGUgVFNWV0cg
bWVldGluZyBpbiBQcmFndWU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQt
ZmFtaWx5OiZxdW90O01pY3Jvc29mdCBZYUhlaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOmJsYWNrIj5EZWFyJm5ic3A7R29ycnkgJmFtcDsgRGF2aWQsDQo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtNaWNyb3NvZnQgWWFIZWkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjaztiYWNrZ3JvdW5kOndoaXRlIj48
YnI+DQo8YnI+DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7TWljcm9zb2Z0IFlhSGVpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZx
dW90O01pY3Jvc29mdCBZYUhlaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJs
YWNrO2JhY2tncm91bmQ6d2hpdGUiPkkgd291bGQgbGlrZSB0byBoYXZlIGEgMTUtbWludXRlIHRp
bWUgc2xvdCAmbmJzcDt0byZuYnNwO3ByZXNlbnQgdGhlIFVBVE4gdG8gb3VyIGZvbGtzJm5ic3A7
aW4gdGhlIFByYWd1ZSBJRVRGIG1lZXRpbmcuJm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O01pY3Jvc29mdCBZYUhlaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtNaWNyb3NvZnQgWWFIZWkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjpibGFjaztiYWNrZ3JvdW5kOndoaXRlIj4mbmJzcDsgSSBoYXZl
IGFscmVhZHkgcHJvcG9zZWQgYW4gYXBwcm9hY2ggdG8gVXBsb2FkIEFjY2VsZXJhdGlvbiBUcmFu
c3BvcnQgTmV0d29yayhVQVROKSBmb3IgdXBzdHJlYW0gdHJhZmZpY3MsIGFuZCZuYnNwO3RoZSBk
cmFmdHMgd2FzIHN1Ym1pdHRlZC4NCiAmbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7TWljcm9zb2Z0IFlhSGVpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O01pY3Jvc29mdCBZYUhlaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOmJsYWNrO2JhY2tncm91bmQ6d2hpdGUiPiZuYnNwOyAmbmJzcDtUaGlz
IGlzIHRoZSBsaW5rLCZuYnNwOzxhIGhyZWY9Imh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
ZG9jL2RyYWZ0LXFpbi10c3Z3Zy11YXRudXQvIj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1xaW4tdHN2d2ctdWF0bnV0LzwvYT48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7TWljcm9zb2Z0IFlhSGVpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi1sZWZ0OjYuMHB0Ij4NCjxkaXY+DQo8ZGl2
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtNaWNyb3NvZnQgWWFIZWkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtNaWNyb3NvZnQgWWFIZWkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+UmVnYXJkcyw8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O01pY3Jvc29m
dCBZYUhlaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5YaWFvd2Vp
IFFpbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtNaWNyb3NvZnQgWWFIZWkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7TWljcm9zb2Z0IFlhSGVpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O01pY3Jvc29mdCBZYUhlaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cHJlIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpiYXNlbGluZTtm
b250LXN0cmV0Y2g6IGluaGVyaXQ7bGluZS1oZWlnaHQ6aW5oZXJpdDt3aGl0ZS1zcGFjZTpwcmUt
d3JhcDt3b3JkLXdyYXA6IGJyZWFrLXdvcmQiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDb3Vy
aWVyO2NvbG9yOmJsYWNrIj5JdCBpcyB0aW1lIHRvIHN0YXJ0IGJ1aWxkaW5nIHRoZSBUU1ZXRyBt
ZWV0aW5nIGFnZW5kYSBmb3IgdGhlIFByYWd1ZSBJRVRGPG86cD48L286cD48L3NwYW4+PC9wcmU+
DQo8cHJlIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpiYXNlbGluZSI+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OkNvdXJpZXI7Y29sb3I6YmxhY2siPm1lZXRpbmcuPG86cD48L286cD48L3NwYW4+PC9w
cmU+DQo8cHJlIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpiYXNlbGluZSI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OkNvdXJpZXI7Y29sb3I6YmxhY2siPuKAoiBBcyB1c3VhbCwgaWYgeW91IGVkaXQg
YSBXRyBkcmFmdCwgcGxlYXNlIGNvbnRhY3QgdGhlIGNoYWlycyBhbmQgbGV0IHVzPG86cD48L286
cD48L3NwYW4+PC9wcmU+DQo8cHJlIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpiYXNlbGluZSI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNvdXJpZXI7Y29sb3I6YmxhY2siPmtub3cgd2hldGhlciB3
ZSBzaG91bGQgZXhwZWN0IGEgc2hvcnQgdXBkYXRlIG9yIHdoZXRoZXIgeW91IHRoaW5rIHlvdTxv
OnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZSBzdHlsZT0idmVydGljYWwtYWxpZ246YmFzZWxp
bmUiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDb3VyaWVyO2NvbG9yOmJsYWNrIj5jb3VsZCBi
ZW5lZml0IGZyb20gYSBsb25nZXIgc2xvdCB0byBkaXNjdXNzIGlzc3Vlcy48bzpwPjwvbzpwPjwv
c3Bhbj48L3ByZT4NCjxwcmUgc3R5bGU9InZlcnRpY2FsLWFsaWduOmJhc2VsaW5lIj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6Q291cmllcjtjb2xvcjpibGFjayI+4oCiIElmIHlvdSB3b3VsZCBs
aWtlIHRvIHByZXNlbnQgb3RoZXIgd29yayBpbiB0c3Z3ZywgcGxlYXNlIHNlbmQgYW4gZW1haWw8
bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmUgc3R5bGU9InZlcnRpY2FsLWFsaWduOmJhc2Vs
aW5lIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q291cmllcjtjb2xvcjpibGFjayI+dG8gdGhl
IENoYWlycyBhc2FwIC0gc28gdGhpbmdzIGNhbiBiZSBkaXNjdXNzZWQgb24gdGhlIGxpc3QgcHJp
b3IgdG8gdGhlPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlIHN0eWxlPSJ2ZXJ0aWNhbC1h
bGlnbjpiYXNlbGluZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNvdXJpZXI7Y29sb3I6Ymxh
Y2siPm1lZXRpbmcuTm90ZTogcGxlYXNlIGJlIHN1cmUgdG8gZW1iZWQgJnF1b3Q7dHN2d2cmcXVv
dDtpbiB0aGUgZmlsZW5hbWUgb2YgYWxsIG5ldzxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHBy
ZSBzdHlsZT0idmVydGljYWwtYWxpZ246YmFzZWxpbmUiPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTpDb3VyaWVyO2NvbG9yOmJsYWNrIj5kcmFmdHMuPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8
cHJlIHN0eWxlPSJ2ZXJ0aWNhbC1hbGlnbjpiYXNlbGluZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OkNvdXJpZXI7Y29sb3I6YmxhY2siPlBsZWFzZSBzZW5kIHJlcXVlc3RzIGFzIHNvb24gYXMg
cG9zc2libGUuPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlIHN0eWxlPSJ2ZXJ0aWNhbC1h
bGlnbjpiYXNlbGluZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNvdXJpZXI7Y29sb3I6Ymxh
Y2siPlRoYW5rcyE8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmUgc3R5bGU9InZlcnRpY2Fs
LWFsaWduOmJhc2VsaW5lIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q291cmllcjtjb2xvcjpi
bGFjayI+R29ycnkgJmFtcDsgRGF2aWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmUgc3R5
bGU9InZlcnRpY2FsLWFsaWduOmJhc2VsaW5lIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q291
cmllcjtjb2xvcjpibGFjayI+KHRzdndnIENvLUNoYWlycyk8bzpwPjwvbzpwPjwvc3Bhbj48L3By
ZT4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtNaWNyb3NvZnQgWWFIZWkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+DQo8aHIgc2l6ZT0iMSIgd2lkdGg9IjIxMCIgc3R5
bGU9IndpZHRoOjE1Ny41cHQiIG5vc2hhZGU9IiIgc3R5bGU9ImNvbG9yOiNCNUM0REYiIGFsaWdu
PSJsZWZ0Ij4NCjwvc3Bhbj48L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+
DQo=

--_000_CE03DB3D7B45C245BCA0D243277949360B3796CFMX104CL02corpem_--


From nobody Tue Jun 16 15:21:57 2015
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 E75CC1AC429 for <tsvwg@ietfa.amsl.com>; Tue, 16 Jun 2015 15:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, 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 yV3KMuaD84Ch for <tsvwg@ietfa.amsl.com>; Tue, 16 Jun 2015 15:21:53 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3669D1ABD35 for <tsvwg@ietf.org>; Tue, 16 Jun 2015 15:21:53 -0700 (PDT)
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 t5GMLpRM027204 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 16 Jun 2015 18:21:51 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com t5GMLpRM027204
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1434493311; bh=sePjco1Z6c+dgIUkAkS1lKIzRFk=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=QBgV9Je6K6CReKbPWnSPdK28MyWkE6ec8icZyXWkwJ+XFTOZXINzKzDxz9tvW8DGr r/vJnZy7zNn1UO+3Z5ZGHErg7p6OcQU+tFibq+WN3qmcqkGLeTyyO4sN5cQD+8Mbj+ CZrX5X5Vhq4aEvSMCI/OwksGzBCmf+VEhuo8DoD4=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com t5GMLpRM027204
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd54.lss.emc.com (RSA Interceptor); Tue, 16 Jun 2015 18:21:20 -0400
Received: from mxhub06.corp.emc.com (mxhub06.corp.emc.com [128.222.70.203]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t5GMLZYQ026225 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 16 Jun 2015 18:21:36 -0400
Received: from MXHUB207.corp.emc.com (10.253.68.33) by mxhub06.corp.emc.com (128.222.70.203) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 16 Jun 2015 18:21:35 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.123]) by MXHUB207.corp.emc.com ([10.253.68.33]) with mapi id 14.03.0224.002; Tue, 16 Jun 2015 18:21:34 -0400
From: "Black, David" <david.black@emc.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>, "swmike@swm.pp.se" <swmike@swm.pp.se>
Thread-Topic: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
Thread-Index: AdCZ+RaNtSi8mJFTQn+UwuqogDAGaAANtuSAABBreAAAAPQVAACwLAGAAtHHEQA=
Date: Tue, 16 Jun 2015 22:21:34 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.57]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/hnTbd2nx5o5HPeneTMeXZ7xxwE8>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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, 16 Jun 2015 22:21:56 -0000

<WG chair hat OFF>

As the "designated victim" at the front of the room for this draft in Dalla=
s
(and one of the draft authors), I understood the request to be for a single
scavenger PHB and DSCP. I concur that 3 AF-like drop probabilities could be
additional nice-to-have functionality, although I think what's essential he=
re
is scavenging of resources otherwise unused for best-effort (or better)
forwarding, for which a single PHB and recommended DSCP would suffice.

We do have a PHB definition in RFC 3662 (LE PHB).  Unfortunately, RFC 3662'=
s
selection of CS1 as the default DSCP has turned out to be a poor choice in=
=20
20/20 hindsight- this text that Brian quoted from RFC 3662 wound up
foreshadowing the problems to come:

      If a CS PHB is used, note that this configuration will violate the
      "SHOULD" of section 4.2.2.2 of RFC 2474 [RFC2474] since CS1 will have
      a less timely forwarding than CS0.  An operator's goal of providing
      an LE PDB is sufficient cause for violating the SHOULD.

See the discussion of the LE PHB and CS1 in the DART draft (at the RFC Edit=
or)
for a summary of the unfortunate state of the world in this area:

	https://tools.ietf.org/html/draft-ietf-dart-dscp-rtp-10

I like Mikael's suggestion of 000xx0 as the place to look for a recommended
DSCP to replace CS1, as that removes the obvious risks of priority inversio=
n
for equipment that only pays attention to the most significant 3 bits of
the DSCP field.

For the Diffserv Intercon draft, I'd prefer to start with just one of those
codepoints, e.g., 000010, define it for the LE PHB for network interconnect=
ion
and suggest that the DSCP be preserved across each network domain (here,
"preserved" means to use that DSCP at domain egress, not necessarily within
the domain).  This would be in addition to the current traffic classes in
the draft, not a replacement.

Beyond that, I'd support a (hopefully short) draft that
	- updates RFC 3662 to change the recommended DSCP for the LE PHB
		from CS1 to 000010,
	- recognizes and allows for continued use of CS1 where deployed, and
	- updates other RFCs (e.g., 4592, 5127) accordingly as needed.
I don't think the Diffserv Intercon draft is a good vehicle for doing that
- a short free-standing draft would be better (IMHO), and that draft would
likely be referenced by the Diffserv Intercon draft if scavenger class text
is added to that draft.

</WG chair hat OFF>

Thanks,
--David


> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Ruediger.Geib@telekom.de
> Sent: Tuesday, June 02, 2015 5:15 AM
> To: swmike@swm.pp.se
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger cla=
ss /
> CS1
>=20
> Hi Mikael,
>=20
> thanks for your proposal. Indeed, transport of LE(Scavenger) by a DSCP 00=
0xx?
> at DiffServ-Intercon interfaces was the only suitable solution I imagined
> myself.
>=20
> Brian quotes RFC3662 below. Now if an AF class is used to implement LE wi=
thin
> a domain, that's still not resulting in a globally non ambiguous DSCP. Th=
is
> may justify a re-write to 000xx0 at a DiffServ-Intercon interface if the
> latter is enhanced by text at least reserving these DSCPs for LE.
>=20
> There should be no unknown DSCPs with AF like syntax, if DSCPs 000xx0 ind=
icate
> LE at DiffServ-Intercon interfaces and unknown DSCPs face a rewrite of DS=
CP
> bits 0-2 to zero (bleaching). Then every unknown AF like DSCP will be mad=
e LE.
> I just note that then bleaching removes the necessity to rewrite the
> AF_DSCPs_used_for_LE at a sending interconnection interface.
>=20
> Regards,
>=20
> Ruediger
>=20
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: tsvwg [mailto:tsvwg-bounces@ietf.org] Im Auftrag von Mikael Abrahams=
son
> Gesendet: Freitag, 29. Mai 2015 23:11
> An: Brian E Carpenter
> Cc: tsvwg@ietf.org
> Betreff: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger cla=
ss /
> CS1
>=20
> On Sat, 30 May 2015, Brian E Carpenter wrote:
>=20
> > Firstly, note that RFC 3662 is very intentionally not standards-track
> > and does not recommend a DSCP value. To me, this discussion seems to
> > mix up two orthogonal concepts:
> >
> > 1. What the PHB for a scavenger class actually is (or in Mikael's
> > suggestion to AQM, what the PHB set is, since mention of priority
> > implies several members of a PHB set, like AFxy).
> >
> > 2. What DSCP values happen to be used for this PHB set. Despite the
> > confusion introduced by RFC 3662, those values don't have to ones
> > already used for other purposes, especially not CSx. Actually the text
> > makes it clear that the DSCPs recommended for AFxy should be
> > considered:
> >
> >   If a CS PHB is used, note that this configuration will violate the
> >   "SHOULD" of section 4.2.2.2 of RFC 2474 [RFC2474] since CS1 will have
> >   a less timely forwarding than CS0.  An operator's goal of providing
> >   an LE PDB is sufficient cause for violating the SHOULD.  If an AF PHB
> >   is used, it must be configured and a DSCP assigned such that it does
> >   not violate the "MUST" of paragraph three of section 2 of RFC 2597
> >   [RFC2597] which provides for a "minimum amount of forwarding
> >   resources".
>=20
> I was only talking about what the 6 DSCP bits should be for this to ever =
start
> to work widely across the Internet. My suggestion is 000xx0 and the
> recommendation is to only bleach the first three bits at ISP interconnect=
s
> instead of all 6 bits (which is the most commonly done at this time). Thi=
s is
> backwards compatible with CS0/BE and it's also backwards compatible with
> default queuing behaviour when doing automatic IP precedence -> 802.1p an=
d the
> recommended 4 queue ethernet prioritization (where CS1 and
> CS2 is lower than CS0 and CS3).
>=20
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Tue Jun 16 17:55:41 2015
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 92BBD1B34CF for <tsvwg@ietfa.amsl.com>; Tue, 16 Jun 2015 17:55:40 -0700 (PDT)
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 CCJoNH6vVGsr for <tsvwg@ietfa.amsl.com>; Tue, 16 Jun 2015 17:55:38 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E9541B32CF for <tsvwg@ietf.org>; Tue, 16 Jun 2015 17:55:38 -0700 (PDT)
Received: by pdbnf5 with SMTP id nf5so25831103pdb.2 for <tsvwg@ietf.org>; Tue, 16 Jun 2015 17:55:37 -0700 (PDT)
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=GvvDEx4LRv/Lc/dNDP7F/VtoRA6acCibLkuTarDhWZo=; b=RLTEA7yVhTPPuxq601RdfHurY4bP1MZ+pUQgGqU4QEcOXUaLDkNGE+gPmH6R/iFOpj /YxC6hrXCCgH0qqTf0PVZ4pQo+aE+ORHp1CWbVVDCvmdptxCalR1Fh2Dxm6DDF6dkfqi JaLDSnFXdBVNXl9uN5V3i+pUAnYePVMM4Ziz3f2nnfCbBB7hvDeUj/7dcYyQUdCEh/6c HD4DOXrLWwzr+8jz0rs8XsfUMwGqZ+LGsGfET35isza6ymSFvF5OKus3ojPDt4yUjHAV zoXBTzAQ+vmFlKKosbKjrCia/NLSg9lt6YjRm6UMNfUQ4yYTRJh4AVEkoN8cnmOnvmTU xryw==
X-Received: by 10.70.47.138 with SMTP id d10mr5338015pdn.137.1434502537658; Tue, 16 Jun 2015 17:55:37 -0700 (PDT)
Received: from ?IPv6:2406:e007:516f:1:28cc:dc4c:9703:6781? ([2406:e007:516f:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id ks7sm2611938pbc.34.2015.06.16.17.55.33 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Jun 2015 17:55:36 -0700 (PDT)
Message-ID: <5580C588.9070008@gmail.com>
Date: Wed, 17 Jun 2015 12:55:36 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>,  "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>, "swmike@swm.pp.se" <swmike@swm.pp.se>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/n3KloNe0b_OGTF-WgRi7nPc76nk>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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, 17 Jun 2015 00:55:40 -0000

Hi David,
On 17/06/2015 10:21, Black, David wrote:
> <WG chair hat OFF>
>=20
> As the "designated victim" at the front of the room for this draft in D=
allas
> (and one of the draft authors), I understood the request to be for a si=
ngle
> scavenger PHB and DSCP. I concur that 3 AF-like drop probabilities coul=
d be
> additional nice-to-have functionality, although I think what's essentia=
l here
> is scavenging of resources otherwise unused for best-effort (or better)=

> forwarding, for which a single PHB and recommended DSCP would suffice.
>=20
> We do have a PHB definition in RFC 3662 (LE PHB).  Unfortunately, RFC 3=
662's
> selection of CS1 as the default DSCP has turned out to be a poor choice=
 in=20
> 20/20 hindsight- this text that Brian quoted from RFC 3662 wound up
> foreshadowing the problems to come:
>=20
>       If a CS PHB is used, note that this configuration will violate th=
e
>       "SHOULD" of section 4.2.2.2 of RFC 2474 [RFC2474] since CS1 will =
have
>       a less timely forwarding than CS0.  An operator's goal of providi=
ng
>       an LE PDB is sufficient cause for violating the SHOULD.
>=20
> See the discussion of the LE PHB and CS1 in the DART draft (at the RFC =
Editor)
> for a summary of the unfortunate state of the world in this area:
>=20
> 	https://tools.ietf.org/html/draft-ietf-dart-dscp-rtp-10
>=20
> I like Mikael's suggestion of 000xx0 as the place to look for a recomme=
nded
> DSCP to replace CS1, as that removes the obvious risks of priority inve=
rsion
> for equipment that only pays attention to the most significant 3 bits o=
f
> the DSCP field.
>=20
> For the Diffserv Intercon draft, I'd prefer to start with just one of t=
hose
> codepoints, e.g., 000010, define it for the LE PHB for network intercon=
nection
> and suggest that the DSCP be preserved across each network domain (here=
,
> "preserved" means to use that DSCP at domain egress, not necessarily wi=
thin
> the domain).  This would be in addition to the current traffic classes =
in
> the draft, not a replacement.
>=20
> Beyond that, I'd support a (hopefully short) draft that
> 	- updates RFC 3662 to change the recommended DSCP for the LE PHB
> 		from CS1 to 000010,
> 	- recognizes and allows for continued use of CS1 where deployed, and
> 	- updates other RFCs (e.g., 4592, 5127) accordingly as needed.
> I don't think the Diffserv Intercon draft is a good vehicle for doing t=
hat
> - a short free-standing draft would be better (IMHO), and that draft wo=
uld
> likely be referenced by the Diffserv Intercon draft if scavenger class =
text
> is added to that draft.

I think that is very reasonable technically, but there's a slight process=

complication. 000010 is in the RFC2474 'standards action' range, so the
short draft would have to be standards track with a downref to RFC3662,
as well as formally updating it.

    Brian

>=20
> </WG chair hat OFF>
>=20
> Thanks,
> --David
>=20
>=20
>> -----Original Message-----
>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of
>> Ruediger.Geib@telekom.de
>> Sent: Tuesday, June 02, 2015 5:15 AM
>> To: swmike@swm.pp.se
>> Cc: tsvwg@ietf.org
>> Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger =
class /
>> CS1
>>
>> Hi Mikael,
>>
>> thanks for your proposal. Indeed, transport of LE(Scavenger) by a DSCP=
 000xx?
>> at DiffServ-Intercon interfaces was the only suitable solution I imagi=
ned
>> myself.
>>
>> Brian quotes RFC3662 below. Now if an AF class is used to implement LE=
 within
>> a domain, that's still not resulting in a globally non ambiguous DSCP.=
 This
>> may justify a re-write to 000xx0 at a DiffServ-Intercon interface if t=
he
>> latter is enhanced by text at least reserving these DSCPs for LE.
>>
>> There should be no unknown DSCPs with AF like syntax, if DSCPs 000xx0 =
indicate
>> LE at DiffServ-Intercon interfaces and unknown DSCPs face a rewrite of=
 DSCP
>> bits 0-2 to zero (bleaching). Then every unknown AF like DSCP will be =
made LE.
>> I just note that then bleaching removes the necessity to rewrite the
>> AF_DSCPs_used_for_LE at a sending interconnection interface.
>>
>> Regards,
>>
>> Ruediger
>>
>>
>> -----Urspr=C3=BCngliche Nachricht-----
>> Von: tsvwg [mailto:tsvwg-bounces@ietf.org] Im Auftrag von Mikael Abrah=
amsson
>> Gesendet: Freitag, 29. Mai 2015 23:11
>> An: Brian E Carpenter
>> Cc: tsvwg@ietf.org
>> Betreff: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger =
class /
>> CS1
>>
>> On Sat, 30 May 2015, Brian E Carpenter wrote:
>>
>>> Firstly, note that RFC 3662 is very intentionally not standards-track=

>>> and does not recommend a DSCP value. To me, this discussion seems to
>>> mix up two orthogonal concepts:
>>>
>>> 1. What the PHB for a scavenger class actually is (or in Mikael's
>>> suggestion to AQM, what the PHB set is, since mention of priority
>>> implies several members of a PHB set, like AFxy).
>>>
>>> 2. What DSCP values happen to be used for this PHB set. Despite the
>>> confusion introduced by RFC 3662, those values don't have to ones
>>> already used for other purposes, especially not CSx. Actually the tex=
t
>>> makes it clear that the DSCPs recommended for AFxy should be
>>> considered:
>>>
>>>   If a CS PHB is used, note that this configuration will violate the
>>>   "SHOULD" of section 4.2.2.2 of RFC 2474 [RFC2474] since CS1 will ha=
ve
>>>   a less timely forwarding than CS0.  An operator's goal of providing=

>>>   an LE PDB is sufficient cause for violating the SHOULD.  If an AF P=
HB
>>>   is used, it must be configured and a DSCP assigned such that it doe=
s
>>>   not violate the "MUST" of paragraph three of section 2 of RFC 2597
>>>   [RFC2597] which provides for a "minimum amount of forwarding
>>>   resources".
>>
>> I was only talking about what the 6 DSCP bits should be for this to ev=
er start
>> to work widely across the Internet. My suggestion is 000xx0 and the
>> recommendation is to only bleach the first three bits at ISP interconn=
ects
>> instead of all 6 bits (which is the most commonly done at this time). =
This is
>> backwards compatible with CS0/BE and it's also backwards compatible wi=
th
>> default queuing behaviour when doing automatic IP precedence -> 802.1p=
 and the
>> recommended 4 queue ethernet prioritization (where CS1 and
>> CS2 is lower than CS0 and CS3).
>>
>> --
>> Mikael Abrahamsson    email: swmike@swm.pp.se
>=20
>=20


From nobody Wed Jun 17 00:12:08 2015
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 91C151A1A7D for <tsvwg@ietfa.amsl.com>; Wed, 17 Jun 2015 00:12:07 -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 7MiPjMYB6Zq9 for <tsvwg@ietfa.amsl.com>; Wed, 17 Jun 2015 00:12:05 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 240891A1A7C for <tsvwg@ietf.org>; Wed, 17 Jun 2015 00:12:05 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 705231B0013D; Wed, 17 Jun 2015 08:12:03 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Wed, 17 Jun 2015 08:11:00 +0100
Message-ID: <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk>
In-Reply-To: <5580C588.9070008@gmail.com>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com> <5580C588.9070008@gmail.com>
Date: Wed, 17 Jun 2015 08:11:00 +0100
From: gorry@erg.abdn.ac.uk
To: "Brian E Carpenter" <brian.e.carpenter@gmail.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/T1wmKklPmkL-sFIRO_Y4m5yrMK8>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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, 17 Jun 2015 07:12:07 -0000

See below.

> Hi David,
> On 17/06/2015 10:21, Black, David wrote:
>> <WG chair hat OFF>
>>
>> As the "designated victim" at the front of the room for this draft in
>> Dallas
>> (and one of the draft authors), I understood the request to be for a
>> single
>> scavenger PHB and DSCP. I concur that 3 AF-like drop probabilities could
>> be
>> additional nice-to-have functionality, although I think what's essential
>> here
>> is scavenging of resources otherwise unused for best-effort (or better)
>> forwarding, for which a single PHB and recommended DSCP would suffice.
>>
>> We do have a PHB definition in RFC 3662 (LE PHB).  Unfortunately, RFC
>> 3662's
>> selection of CS1 as the default DSCP has turned out to be a poor choice
>> in
>> 20/20 hindsight- this text that Brian quoted from RFC 3662 wound up
>> foreshadowing the problems to come:
>>
>>       If a CS PHB is used, note that this configuration will violate the
>>       "SHOULD" of section 4.2.2.2 of RFC 2474 [RFC2474] since CS1 will
>> have
>>       a less timely forwarding than CS0.  An operator's goal of
>> providing
>>       an LE PDB is sufficient cause for violating the SHOULD.
>>
>> See the discussion of the LE PHB and CS1 in the DART draft (at the RFC
>> Editor)
>> for a summary of the unfortunate state of the world in this area:
>>
>> 	https://tools.ietf.org/html/draft-ietf-dart-dscp-rtp-10
>>
>> I like Mikael's suggestion of 000xx0 as the place to look for a
>> recommended
>> DSCP to replace CS1, as that removes the obvious risks of priority
>> inversion
>> for equipment that only pays attention to the most significant 3 bits of
>> the DSCP field.
>>
>> For the Diffserv Intercon draft, I'd prefer to start with just one of
>> those
>> codepoints, e.g., 000010, define it for the LE PHB for network
>> interconnection
>> and suggest that the DSCP be preserved across each network domain (here,
>> "preserved" means to use that DSCP at domain egress, not necessarily
>> within
>> the domain).  This would be in addition to the current traffic classes
>> in
>> the draft, not a replacement.
>>
>> Beyond that, I'd support a (hopefully short) draft that
>> 	- updates RFC 3662 to change the recommended DSCP for the LE PHB
>> 		from CS1 to 000010,
>> 	- recognizes and allows for continued use of CS1 where deployed, and
>> 	- updates other RFCs (e.g., 4592, 5127) accordingly as needed.
>> I don't think the Diffserv Intercon draft is a good vehicle for doing
>> that
>> - a short free-standing draft would be better (IMHO), and that draft
>> would
>> likely be referenced by the Diffserv Intercon draft if scavenger class
>> text
>> is added to that draft.
>
> I think that is very reasonable technically, but there's a slight process
> complication. 000010 is in the RFC2474 'standards action' range, so the
> short draft would have to be standards track with a downref to RFC3662,
> as well as formally updating it.
>
>     Brian
>
I'd be happy to contribute to this work.

As co-chair: I think the short separate standards-track draft would then
be the appropriate thing to do. This could be done quickly ***IF*** we get
a firm consensus  from the community to do this.

Gorry

>>
>> </WG chair hat OFF>
>>
>> Thanks,
>> --David
>>
>>
>>> -----Original Message-----
>>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of
>>> Ruediger.Geib@telekom.de
>>> Sent: Tuesday, June 02, 2015 5:15 AM
>>> To: swmike@swm.pp.se
>>> Cc: tsvwg@ietf.org
>>> Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger
>>> class /
>>> CS1
>>>
>>> Hi Mikael,
>>>
>>> thanks for your proposal. Indeed, transport of LE(Scavenger) by a DSCP
>>> 000xx?
>>> at DiffServ-Intercon interfaces was the only suitable solution I
>>> imagined
>>> myself.
>>>
>>> Brian quotes RFC3662 below. Now if an AF class is used to implement LE
>>> within
>>> a domain, that's still not resulting in a globally non ambiguous DSCP.
>>> This
>>> may justify a re-write to 000xx0 at a DiffServ-Intercon interface if
>>> the
>>> latter is enhanced by text at least reserving these DSCPs for LE.
>>>
>>> There should be no unknown DSCPs with AF like syntax, if DSCPs 000xx0
>>> indicate
>>> LE at DiffServ-Intercon interfaces and unknown DSCPs face a rewrite of
>>> DSCP
>>> bits 0-2 to zero (bleaching). Then every unknown AF like DSCP will be
>>> made LE.
>>> I just note that then bleaching removes the necessity to rewrite the
>>> AF_DSCPs_used_for_LE at a sending interconnection interface.
>>>
>>> Regards,
>>>
>>> Ruediger
>>>
>>>
>>> -----UrsprĆ¼ngliche Nachricht-----
>>> Von: tsvwg [mailto:tsvwg-bounces@ietf.org] Im Auftrag von Mikael
>>> Abrahamsson
>>> Gesendet: Freitag, 29. Mai 2015 23:11
>>> An: Brian E Carpenter
>>> Cc: tsvwg@ietf.org
>>> Betreff: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger
>>> class /
>>> CS1
>>>
>>> On Sat, 30 May 2015, Brian E Carpenter wrote:
>>>
>>>> Firstly, note that RFC 3662 is very intentionally not standards-track
>>>> and does not recommend a DSCP value. To me, this discussion seems to
>>>> mix up two orthogonal concepts:
>>>>
>>>> 1. What the PHB for a scavenger class actually is (or in Mikael's
>>>> suggestion to AQM, what the PHB set is, since mention of priority
>>>> implies several members of a PHB set, like AFxy).
>>>>
>>>> 2. What DSCP values happen to be used for this PHB set. Despite the
>>>> confusion introduced by RFC 3662, those values don't have to ones
>>>> already used for other purposes, especially not CSx. Actually the text
>>>> makes it clear that the DSCPs recommended for AFxy should be
>>>> considered:
>>>>
>>>>   If a CS PHB is used, note that this configuration will violate the
>>>>   "SHOULD" of section 4.2.2.2 of RFC 2474 [RFC2474] since CS1 will
>>>> have
>>>>   a less timely forwarding than CS0.  An operator's goal of providing
>>>>   an LE PDB is sufficient cause for violating the SHOULD.  If an AF
>>>> PHB
>>>>   is used, it must be configured and a DSCP assigned such that it does
>>>>   not violate the "MUST" of paragraph three of section 2 of RFC 2597
>>>>   [RFC2597] which provides for a "minimum amount of forwarding
>>>>   resources".
>>>
>>> I was only talking about what the 6 DSCP bits should be for this to
>>> ever start
>>> to work widely across the Internet. My suggestion is 000xx0 and the
>>> recommendation is to only bleach the first three bits at ISP
>>> interconnects
>>> instead of all 6 bits (which is the most commonly done at this time).
>>> This is
>>> backwards compatible with CS0/BE and it's also backwards compatible
>>> with
>>> default queuing behaviour when doing automatic IP precedence -> 802.1p
>>> and the
>>> recommended 4 queue ethernet prioritization (where CS1 and
>>> CS2 is lower than CS0 and CS3).
>>>
>>> --
>>> Mikael Abrahamsson    email: swmike@swm.pp.se
>>
>>
>


From nobody Wed Jun 17 23:59:51 2015
Return-Path: <prvs=0611869f3b=per.hurtig@kau.se>
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 844F71A0104; Wed, 17 Jun 2015 23:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level: 
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3] 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 31MZW3Low6DK; Wed, 17 Jun 2015 23:59:47 -0700 (PDT)
Received: from nasse.dc.kau.se (smtp.kau.se [193.10.220.39]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 331AD1B3060; Wed, 17 Jun 2015 23:59:46 -0700 (PDT)
X-Spam-Processed: mail.kau.se, Thu, 18 Jun 2015 08:59:37 +0200 (not processed: spam filter heuristic analysis disabled)
X-MDRemoteIP: 130.243.29.53
X-MDHelo: nod050.wlanp.kau.se
X-MDArrival-Date: Thu, 18 Jun 2015 08:59:37 +0200
X-Authenticated-Sender: per.hurtig@kau.se
X-Return-Path: per.hurtig@kau.se
X-Envelope-From: per.hurtig@kau.se
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_48A4FE79-D605-4292-95B1-77E6D6DA92BB"; protocol="application/pgp-signature"; micalg=pgp-sha256
X-Pgp-Agent: GPGMail 2.5
From: Per Hurtig <per.hurtig@kau.se>
In-Reply-To: <cc09d18c32d3d31d456c3c933e6a1f41@mail.gmail.com>
Date: Thu, 18 Jun 2015 08:59:31 +0200
Message-Id: <CDDC3A04-3F6B-471D-90C0-1A009D8EC80A@kau.se>
References: <882B8BE8-D02D-4E46-90B0-FE9CB2E88BF9@telecom-bretagne.eu> <655C07320163294895BBADA28372AF5D483AF02D@FR712WXCHMBA15.zeu.alcatel-lucent.com> <cc09d18c32d3d31d456c3c933e6a1f41@mail.gmail.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/X4tq7OUBbM3gpbgXFygcBSsujr4>
Cc: tcpm@ietf.org, "Scharf, Michael \(Michael\)" <michael.scharf@alcatel-lucent.com>, tsvwg <tsvwg@ietf.org>, Michael Welzl <michawe@ifi.uio.no>, apetlund@simula.no
Subject: Re: [tsvwg] [tcpm] draft-ietf-tcpm-rtorestart-07
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: Thu, 18 Jun 2015 06:59:50 -0000

--Apple-Mail=_48A4FE79-D605-4292-95B1-77E6D6DA92BB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Karen,

We agree that SCTP seems forgotten in the document. We have now =
re-writen the introduction to address both TCP and SCTP. We also end the =
introduction saying that the rest of the document will focus on TCP, =
with an exception for Section 7 (the SCTP API). If we were to describe =
RTOR for TCP and SCTP without violating any terminology (for any of the =
protocols) we believe that the document would be unnecessarily long and =
very hard to read.


Cheers,
Per

> On 01 Jun 2015, at 11:15, Karen Elisabeth Egede Nielsen =
<karen.nielsen@tieto.com> wrote:
>=20
> Hi,
>=20
> Please accept the following - overdue - comments:
>=20
> General comments on SCTP applicability of the specification:
> =
--------------------------------------------------------------------------=
----
>=20
> The document is inconsistent in its description of the SCTP aspects
> of the proposed algorithm.
>=20
> Section 1 and general:
>=20
> The document does say, in the end of Section 1, that the focus of the
> document is on TCP "with validity also for SCTP".
> However if so, then I think this paragraph should have been the first
> paragraph in section 1 rather than the last.
> I think that it is confusing that the Abstract (and the title) speaks =
about
> TCP and SCTP, but the introduction text speaks about TCP only.
>=20
> I think that it would be better for the text of section 1 to be =
augmented to
> speak about TCP _&_ SCTP. With the final paragraph
> then telling that in the remaining part of the documents, the focus =
would be
> on TCP (if this is the intend).
>=20
> (We have the SCTP API section in the end. Not sure how this fits with =
the
> notion of only providing details for TCP)
>=20
> Alternatively, if the present "TCP only" introduction is kept, I think =
that
> it would be relevant to emphasize in the final paragraph of section 1, =
that
> what has been described above in section 1, is common to TCP and SCTP
> (except possibly for the exact word  "dupacks" - but I think one could =
get
> around that).
>=20
> Still even with the above clarifications, it is unclear to me what the
> status of this document is vis-a-vis SCTP.  The detailed SCTP socket =
API
> description is there,
> but some of the crucial implementation aspects - e.g. section 5.3., is =
TCP
> only.
>=20
> But perhaps such inconsistency is ok for experimental ?
>=20
> Section 3:
>=20
> The contents of this section is common to TCP and SCTP except for the =
term
> segment which is TCP particular and which would be a packet in SCTP.
>=20
> Section 4:
>=20
> Here there is a reference to "similar update to  RFC4960", but at the =
same
> time the word segment is used and further the section 5.3. discussion =
is
> TCP only.
>=20
>=20
> Detailed on Section 7:
> ---------------------------
> As far as I can tell this is exactly what we would like to have for =
SCTP.
>=20
>=20
> Thanks,
>=20
> BR, Karen
>=20
> PS:  It turns out that some SCTP implementations may send two packets =
right
> after RTO thus applying the "allowed to breach CWND with PMTU-1" logic =
also
> immediately following RTO-timeout. This has impact of how delay_ack =
impacts
> the loss recovery time (refer to discussion in section 5.1).  I =
believe that
> the intent is to have  this eventually be clarified to be incompliant
> behavior (also of SCTP), but SCTP then of course has the option to ask =
for
> immediate SACK in this situation, which then again changes the impact =
of
> delay_ack. There also exist SCTP implementations which rigorously =
follows
> TCP semantics and which thus do not breach the CWND right after RTO =
(only
> after receipt of first ACK after RTO) and which today does not deploy =
the
> Immediate SACK extension. For such the delay_ack impact is the RTO =
loss
> recovery as for TCP. The latter behavior is the right RFC4960 =
implementation
> (at least I would argue that), but possibly not the "right" future =
SCTP
> implementation.
>=20
>=20
>> -----Original Message-----
>> From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Scharf, =
Michael
>> (Michael)
>> Sent: Monday, May 18, 2015 11:22 AM
>> To: per.hurtig@kau.se; anna.brunstrom@kau.se; apetlund@simula.no;
>> michawe@ifi.uio.no
>> Cc: tcpm@ietf.org
>> Subject: Re: [tcpm] draft-ietf-tcpm-rtorestart-07
>>=20
>> Authors,
>>=20
>> These (mostly editorial) comments are the only WGLC comments for =
draft-
>> ietf-tcpm-rtorestart-07 that I am aware of. Could you please discuss =
how to
>> address them?
>>=20
>> Thanks
>>=20
>> Michael
>>=20
>>=20
>>=20
>>> -----Original Message-----
>>> From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Nicolas Kuhn
>>> Sent: Thursday, May 07, 2015 5:00 PM
>>> To: tcpm@ietf.org
>>> Subject: [tcpm] draft-ietf-tcpm-rtorestart-07
>>>=20
>>> Hi all,
>>>=20
>>> I had a look at this draft-ietf-tcpm-rtorestart-07 draft.
>>> I have some minor comments on the document.
>>>=20
>>>=20
>> ###########################################################
>> ##
>>>=20
>>> - "The RTO Restart (RTOR) mechanism described in this document makes
>>> the
>>>   RTO slightly more aggressive when the number of outstanding =
segments
>>>   is too small for fast retransmit to work, in an attempt to enable
>>>   faster loss recovery for all segments while being robust to
>>>   reordering."
>>>=20
>>> The RTO is not aggressive ; but the retransmission scheme ruled by =
RTO
>>> expirations is.
>>> I would recommend to rephrase that.
>>>=20
>>>=20
>> ###########################################################
>> ##
>>>=20
>>> - =E2=80=9C   The RTO Restart (RTOR) mechanism described in this =
document makes
>>> the
>>>   RTO slightly [=E2=80=A6] highly varying RTTs, e.g. mobile =
networks."
>>>=20
>>> This whole paragraph comes to early in the document, as the reader =
has
>>> no clear idea about what RTOR is actually doing. I propose to add =
that
>>> in a dedicated sub- section in Section 5.
>>>=20
>>>=20
>> ###########################################################
>> ##
>>>=20
>>> - =E2=80=9C 3 RTO Restart Overview=E2=80=9D -> should it not be =
=E2=80=9C3- RTO Overview and
>>> rationale of RTOR =E2=80=9C or something equivalent ?
>>> It is confusing, as you do not actually present RTOR.
>>>=20
>>> Also, in this section 3:
>>> The first paragraph finishes with =E2=80=9CHence,  in most =
situations, the
>>> time before a retransmission is triggered is equal to "RTO + =
RTT=E2=80=9D.=E2=80=9D
>>> But the example to illustrate it comes after - I think things should
>>> moved around to:
>>> 1- introduce the classic RTO
>>> 2- explain the rationale of classic RTO
>>> 3- example to show that RTO+RTT is common
>>> 4- more parameters could affect that (2 outstanding segments; other
>>> factors)
>>> 5- conclusion on =E2=80=9Chence, RTO+RTT is common for application =
limited
>>> traffic"
>>>=20
>>> I would propose to introduce a ToC for this section 3:
>>>=20
>>> 3- RTO Overview and rationale of RTOR
>>>  3-1. Experienced RTO is RTO+RTT
>>>  3-2. RTO safety margin
>>>  3-3. Rationale of RTOR: when fast retransmit is not possible
>>>=20
>>>=20
>> ###########################################################
>> ##
>>>=20
>>> Section 4 : should focus on the description of the algorithm only.
>>>=20
>>> I would keep
>>> =E2=80=9C
>>> This approach makes the RTO more
>>>   aggressive than the standardized approach in [RFC6298] but still
>>>   conforms to the requirement in [RFC6298] that segments must not be
>>>   retransmitted earlier than RTO seconds after their original
>>>   transmission.
>>> "
>>>=20
>>> for the discussion section (at this stage of the reading, the reader
>>> still does not know exactly what RTOR is actually doing).
>>>=20
>>>=20
>> ###########################################################
>> ##
>>>=20
>>> Section 4: "it will prevent RTOR
>>>   from being more aggressive and potentially causing RTOs instead of
>>>   fast retransmits.=E2=80=9D
>>>=20
>>> More aggressive than what ? Has the "four" being experimentally
>>> obtained ?
>>> I think more discussion is required on this parameter.
>>>=20
>>> Regards,
>>>=20
>>> Nicolas
>>> _______________________________________________
>>> tcpm mailing list
>>> tcpm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcpm
>> _______________________________________________
>> tcpm mailing list
>> tcpm@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcpm


--Apple-Mail=_48A4FE79-D605-4292-95B1-77E6D6DA92BB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJVgmxYAAoJEMzXVkqMT/z2t/cH/AsqfNBXT7Zk3CNfFehAU5bw
ni9Mh3gvvhW0U4w2s8IddJ0aqHhSrAbPm6t7AgPrUJUSbcAC/jQ+e5Ts0lglT4tn
Tjcl0twW4bSGs82T0xV/DgxE+82b99qGlTg/lj4btqYD92yVULtIzEzPpwPIvM9u
YvpCKcj5qaBlXrqDTJm0MRUJi9AJliWguxWHf1z78Boo5y7zWdcFKAT75X8HIIJE
ni+zlorOrUA3yKwhgaDNUw5iMqBRb6ImQ2N1JUBkoddMWB00bzvi1oOfNq8t/lxq
GpzgeCrimdzi1vsIFtdocpLFlgLnJ/gKhIWrjafTMsOj5oAQbR3PSlbUuGK7inw=
=2+bH
-----END PGP SIGNATURE-----

--Apple-Mail=_48A4FE79-D605-4292-95B1-77E6D6DA92BB--


From nobody Thu Jun 18 00:29:05 2015
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 D92191A09C9 for <tsvwg@ietfa.amsl.com>; Thu, 18 Jun 2015 00:29:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.779
X-Spam-Level: 
X-Spam-Status: No, score=-0.779 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, J_CHICKENPOX_34=0.6, 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 Zk5sBRcZEy9h for <tsvwg@ietfa.amsl.com>; Thu, 18 Jun 2015 00:29:02 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFE371A079D for <tsvwg@ietf.org>; Thu, 18 Jun 2015 00:29:01 -0700 (PDT)
Received: by iecrd14 with SMTP id rd14so49368487iec.3 for <tsvwg@ietf.org>; Thu, 18 Jun 2015 00:29:01 -0700 (PDT)
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=i7CQDQ6UVGldvY7wWxspjRNlr5sMMJkDafNGk/AddRU=; b=K/DVSW62ffGiOQyxtp1RWxBfXDE81yc3fgOKatmkcdGEbnaZ8hG2IfrDqYafVEkfrB aWhWaRwnjxZ9FO6XRNruYA5abnP+hLp187ysKYvywnnZD+l8nIbGfJw8+47GFjzn9yBN y1WmGO+BIGhsVGZJugDps1r9jF6LajIl7ZcAU=
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=i7CQDQ6UVGldvY7wWxspjRNlr5sMMJkDafNGk/AddRU=; b=Puc04tZepLWURx0JN2TiPng8lBFkWyLTqgWLXwL0MF8QBuqZIkWCskAO7H0mkENq9b Z2deLWTm4GAmzWPahuekk4B1FE/Ko8aH2dcStFQ375+rMXcr2XVc8dR9JUMjRyw47iLV ibfBw6xKfm6/aS52jac28IpM11imUOnoTbqyZPZcqfWyEqnC5LOU7iAhU+vmjvNT8Iup +Zqj9mkTZGZZTBTz3wBtDlZjKe3embPYN9bAhEMJEhMvGuTiOSHfGRUA4DlSYLT6WcmR FBIT5qqk8ZU7fmTnAVG/j7ThzK0Et9W2MkIAzIRHCPeEEaO75wzIAgp+t95Ol+b/9/dq gamA==
X-Gm-Message-State: ALoCoQkN+GRIsEe7hYRHUd0vy7OBdR1eVB0Zs/nQa+ByKtOh7Ogy7wHc/N+iVZCfUt4iZ+Zb06WoMUxaz+hOO8RFc2JzGMDuHzCUestTey4g20pimgw2tLw=
X-Received: by 10.107.46.226 with SMTP id u95mr12360326iou.68.1434612541375; Thu, 18 Jun 2015 00:29:01 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <882B8BE8-D02D-4E46-90B0-FE9CB2E88BF9@telecom-bretagne.eu> <655C07320163294895BBADA28372AF5D483AF02D@FR712WXCHMBA15.zeu.alcatel-lucent.com> <cc09d18c32d3d31d456c3c933e6a1f41@mail.gmail.com> <CDDC3A04-3F6B-471D-90C0-1A009D8EC80A@kau.se>
In-Reply-To: <CDDC3A04-3F6B-471D-90C0-1A009D8EC80A@kau.se>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQL7VJwomcXY3mf3wZzSms+lgcAi+gFhiVv/AYKNx7sB3lM3Sps2cpMg
Date: Thu, 18 Jun 2015 09:29:00 +0200
Message-ID: <64074bfb5bd45b8b1052f032f07f202e@mail.gmail.com>
To: Per Hurtig <per.hurtig@kau.se>
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/26PZ7dhotfbhqwkp-cTJvTwCp08>
Cc: tcpm@ietf.org, "Scharf, Michael \(Michael\)" <michael.scharf@alcatel-lucent.com>, tsvwg <tsvwg@ietf.org>, Michael Welzl <michawe@ifi.uio.no>, apetlund@simula.no
Subject: Re: [tsvwg] [tcpm] draft-ietf-tcpm-rtorestart-07
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: Thu, 18 Jun 2015 07:29:05 -0000

Hi,

Thanks for taking my comments into consideration !

I think the described approach with a common TCP&SCTP introduction sounds
good
and given that I agree that it is viable to leave the SCTP details out.

BR, Karen

>-----Original Message-----
>From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Per Hurtig
>Sent: Thursday, June 18, 2015 9:00 AM
>To: Karen Elisabeth Egede Nielsen
>Cc: tcpm@ietf.org; Scharf, Michael (Michael); tsvwg; Michael Welzl;
>apetlund@simula.no
>Subject: Re: [tsvwg] [tcpm] draft-ietf-tcpm-rtorestart-07
>
>Hi Karen,
>
>We agree that SCTP seems forgotten in the document. We have now re-
>writen the introduction to address both TCP and SCTP. We also end the
>introduction saying that the rest of the document will focus on TCP, with
>an
>exception for Section 7 (the SCTP API). If we were to describe RTOR for TC=
P
>and SCTP without violating any terminology (for any of the protocols) we
>believe that the document would be unnecessarily long and very hard to
>read.
>
>
>Cheers,
>Per
>
>> On 01 Jun 2015, at 11:15, Karen Elisabeth Egede Nielsen
><karen.nielsen@tieto.com> wrote:
>>
>> Hi,
>>
>> Please accept the following - overdue - comments:
>>
>> General comments on SCTP applicability of the specification:
>> ----------------------------------------------------------------------
>> --------
>>
>> The document is inconsistent in its description of the SCTP aspects of
>> the proposed algorithm.
>>
>> Section 1 and general:
>>
>> The document does say, in the end of Section 1, that the focus of the
>> document is on TCP "with validity also for SCTP".
>> However if so, then I think this paragraph should have been the first
>> paragraph in section 1 rather than the last.
>> I think that it is confusing that the Abstract (and the title) speaks
>> about TCP and SCTP, but the introduction text speaks about TCP only.
>>
>> I think that it would be better for the text of section 1 to be
>> augmented to speak about TCP _&_ SCTP. With the final paragraph then
>> telling that in the remaining part of the documents, the focus would
>> be on TCP (if this is the intend).
>>
>> (We have the SCTP API section in the end. Not sure how this fits with
>> the notion of only providing details for TCP)
>>
>> Alternatively, if the present "TCP only" introduction is kept, I think
>> that it would be relevant to emphasize in the final paragraph of
>> section 1, that what has been described above in section 1, is common
>> to TCP and SCTP (except possibly for the exact word  "dupacks" - but I
>> think one could get around that).
>>
>> Still even with the above clarifications, it is unclear to me what the
>> status of this document is vis-a-vis SCTP.  The detailed SCTP socket
>> API description is there, but some of the crucial implementation
>> aspects - e.g. section 5.3., is TCP only.
>>
>> But perhaps such inconsistency is ok for experimental ?
>>
>> Section 3:
>>
>> The contents of this section is common to TCP and SCTP except for the
>> term segment which is TCP particular and which would be a packet in SCTP=
.
>>
>> Section 4:
>>
>> Here there is a reference to "similar update to  RFC4960", but at the
>> same time the word segment is used and further the section 5.3.
>> discussion is TCP only.
>>
>>
>> Detailed on Section 7:
>> ---------------------------
>> As far as I can tell this is exactly what we would like to have for SCTP=
.
>>
>>
>> Thanks,
>>
>> BR, Karen
>>
>> PS:  It turns out that some SCTP implementations may send two packets
>> right after RTO thus applying the "allowed to breach CWND with PMTU-1"
>> logic also immediately following RTO-timeout. This has impact of how
>> delay_ack impacts the loss recovery time (refer to discussion in
>> section 5.1).  I believe that the intent is to have  this eventually
>> be clarified to be incompliant behavior (also of SCTP), but SCTP then
>> of course has the option to ask for immediate SACK in this situation,
>> which then again changes the impact of delay_ack. There also exist
>> SCTP implementations which rigorously follows TCP semantics and which
>> thus do not breach the CWND right after RTO (only after receipt of
>> first ACK after RTO) and which today does not deploy the Immediate
>> SACK extension. For such the delay_ack impact is the RTO loss recovery
>> as for TCP. The latter behavior is the right RFC4960 implementation
>> (at least I would argue that), but possibly not the "right" future SCTP
>implementation.
>>
>>
>>> -----Original Message-----
>>> From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Scharf,
>>> Michael
>>> (Michael)
>>> Sent: Monday, May 18, 2015 11:22 AM
>>> To: per.hurtig@kau.se; anna.brunstrom@kau.se; apetlund@simula.no;
>>> michawe@ifi.uio.no
>>> Cc: tcpm@ietf.org
>>> Subject: Re: [tcpm] draft-ietf-tcpm-rtorestart-07
>>>
>>> Authors,
>>>
>>> These (mostly editorial) comments are the only WGLC comments for
>>> draft-
>>> ietf-tcpm-rtorestart-07 that I am aware of. Could you please discuss
>>> how to address them?
>>>
>>> Thanks
>>>
>>> Michael
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Nicolas Kuhn
>>>> Sent: Thursday, May 07, 2015 5:00 PM
>>>> To: tcpm@ietf.org
>>>> Subject: [tcpm] draft-ietf-tcpm-rtorestart-07
>>>>
>>>> Hi all,
>>>>
>>>> I had a look at this draft-ietf-tcpm-rtorestart-07 draft.
>>>> I have some minor comments on the document.
>>>>
>>>>
>>>
>###########################################################
>>> ##
>>>>
>>>> - "The RTO Restart (RTOR) mechanism described in this document makes
>>>> the
>>>>   RTO slightly more aggressive when the number of outstanding segments
>>>>   is too small for fast retransmit to work, in an attempt to enable
>>>>   faster loss recovery for all segments while being robust to
>>>>   reordering."
>>>>
>>>> The RTO is not aggressive ; but the retransmission scheme ruled by
>>>> RTO expirations is.
>>>> I would recommend to rephrase that.
>>>>
>>>>
>>>
>###########################################################
>>> ##
>>>>
>>>> - =E2=80=9C   The RTO Restart (RTOR) mechanism described in this docum=
ent
>makes
>>>> the
>>>>   RTO slightly [=E2=80=A6] highly varying RTTs, e.g. mobile networks."
>>>>
>>>> This whole paragraph comes to early in the document, as the reader
>>>> has no clear idea about what RTOR is actually doing. I propose to
>>>> add that in a dedicated sub- section in Section 5.
>>>>
>>>>
>>>
>###########################################################
>>> ##
>>>>
>>>> - =E2=80=9C 3 RTO Restart Overview=E2=80=9D -> should it not be =E2=80=
=9C3- RTO Overview and
>>>> rationale of RTOR =E2=80=9C or something equivalent ?
>>>> It is confusing, as you do not actually present RTOR.
>>>>
>>>> Also, in this section 3:
>>>> The first paragraph finishes with =E2=80=9CHence,  in most situations,=
 the
>>>> time before a retransmission is triggered is equal to "RTO + RTT=E2=80=
=9D.=E2=80=9D
>>>> But the example to illustrate it comes after - I think things should
>>>> moved around to:
>>>> 1- introduce the classic RTO
>>>> 2- explain the rationale of classic RTO
>>>> 3- example to show that RTO+RTT is common
>>>> 4- more parameters could affect that (2 outstanding segments; other
>>>> factors)
>>>> 5- conclusion on =E2=80=9Chence, RTO+RTT is common for application lim=
ited
>>>> traffic"
>>>>
>>>> I would propose to introduce a ToC for this section 3:
>>>>
>>>> 3- RTO Overview and rationale of RTOR  3-1. Experienced RTO is
>>>> RTO+RTT  3-2. RTO safety margin  3-3. Rationale of RTOR: when fast
>>>> retransmit is not possible
>>>>
>>>>
>>>
>###########################################################
>>> ##
>>>>
>>>> Section 4 : should focus on the description of the algorithm only.
>>>>
>>>> I would keep
>>>> =E2=80=9C
>>>> This approach makes the RTO more
>>>>   aggressive than the standardized approach in [RFC6298] but still
>>>>   conforms to the requirement in [RFC6298] that segments must not be
>>>>   retransmitted earlier than RTO seconds after their original
>>>>   transmission.
>>>> "
>>>>
>>>> for the discussion section (at this stage of the reading, the reader
>>>> still does not know exactly what RTOR is actually doing).
>>>>
>>>>
>>>
>###########################################################
>>> ##
>>>>
>>>> Section 4: "it will prevent RTOR
>>>>   from being more aggressive and potentially causing RTOs instead of
>>>>   fast retransmits.=E2=80=9D
>>>>
>>>> More aggressive than what ? Has the "four" being experimentally
>>>> obtained ?
>>>> I think more discussion is required on this parameter.
>>>>
>>>> Regards,
>>>>
>>>> Nicolas
>>>> _______________________________________________
>>>> tcpm mailing list
>>>> tcpm@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/tcpm
>>> _______________________________________________
>>> tcpm mailing list
>>> tcpm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcpm


From nobody Fri Jun 19 00:23:10 2015
Return-Path: <qinxiaowei@cnnic.cn>
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 15E3C1A6FFF for <tsvwg@ietfa.amsl.com>; Fri, 19 Jun 2015 00:23:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.61
X-Spam-Level: 
X-Spam-Status: No, score=-0.61 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_LETTER=-2, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, SPF_HELO_PASS=-0.001, 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 PWC9uD7BbotK for <tsvwg@ietfa.amsl.com>; Fri, 19 Jun 2015 00:23:02 -0700 (PDT)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id AF6871A6F10 for <tsvwg@ietf.org>; Fri, 19 Jun 2015 00:23:00 -0700 (PDT)
Received: from CNNIC-PC (unknown [218.241.103.131]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0DJ0ZVBw4NVCqxzBw--.4305S2; Fri, 19 Jun 2015 15:22:41 +0800 (CST)
Date: Fri, 19 Jun 2015 15:22:34 +0800
From: "qinxiaowei@cnnic.cn" <qinxiaowei@cnnic.cn>
To: david.black <david.black@emc.com>
References: <2015061609380655266421@cnnic.cn>,  <CE03DB3D7B45C245BCA0D243277949360B3796CF@MX104CL02.corp.emc.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 136[cn]
Mime-Version: 1.0
Message-ID: <2015061915223473892022@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart217547876082_=----"
X-CM-TRANSID: AQAAf0DJ0ZVBw4NVCqxzBw--.4305S2
X-Coremail-Antispam: 1UD129KBjvJXoWxZrW5WryxGFWfGryxAF1xGrg_yoWrury3pa yFgFZxKF4kJa97Xw1kJw1xJryS9393Kw43Ja15tryDA398KF1IkF17Jr1UXr98Cr1rXF1Y qryqvan8Ga4vyrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUULCb7Iv0xC_Kw4lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Xr0_Ar1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Cr0_Gr1UM28EF7xvwVC2z280aVAFwI0_Cr1j6rxdM28EF7xvwV C2z280aVCY1x0267AKxVW0oVCq3wAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40Eb7x2 x7xS6ryj6rWUMc02F40En4AKxVAvwIkv4cxYr24l5I8CrVAqjxCE14ACF2xKxwAqx4xG64 kEw2xG04xIwI0_Jr0_Gr1l5I8CrVCF0I0E4I0vr24l5I8CrVC2j2CEjI02ccxYII8I67AE r4CY67k08wAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6x CaFVCjc4AY6r1j6r4UM4x0Y48IcxkI7VAKI48JM4xvF2IEb7IF0Fy264kE64k0F24lFcxC 0VAYjxAxZF0Ex2IqxwCjr7xvwVCIw2I0I7xG6c02F41lc2xSY4AK67AK6r4xMxAIw28Icx kI7VAKI48JMxC20s026xCaFVCjc4AY6r1j6r4UMI8I3I0E5I8CrVAFwI0_JrI_JrWlx2Iq xVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUAVWUtwCIc40Y0x0EwIxGrwCI42 IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AKxVWUJVW8JwCI42IY 6xAIw20EY4v20xvaj40_WFyUJVCq3wCI42IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87 Iv6xkF7I0E14v26r1j6r4UMVCEFcxC0VAYjxAxZFUvcSsGvfC2KfnxnUUI43ZEXa7IU5Wy I5UUUUU==
X-CM-SenderInfo: xtlq5x5drzvxw6fq0xffof0/
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/S5xEK6iuwMr-H5J8sOxbmLmvwKw>
Cc: gorry <gorry@erg.abdn.ac.uk>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] Agenda request for the TSVWG meeting in Prague
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, 19 Jun 2015 07:23:09 -0000

This is a multi-part message in MIME format.

------=_001_NextPart217547876082_=----
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

RGVhciBEYXZpZCAsDQpUaGFua3MgZm9yIHlvdSBsZXR0ZXIuDQoNClBlcmhhcHMgVUFUTiBpcyBh
biBuZXcgaWRlYXMsIHNvIGhhcyBub3QgYXR0cmFjdGVkIHBlb3BsZSdzIGNvbmNlcm5zIHVwIHRv
IG5vdy4gSU1PLCBhcyBtb2JpbGUgZGV2aWNlcyBkZXZlbG9waW5nLCBob3dldmVyLCB0aGUgVUFU
TiB3aWxsIGJlIHVzZWQgd2lkZWx5IGluIHRoZSBmdXR1cmUuDQoNCj4gIFdl4oCZcmUgdW5jbGVh
ciBvbiB3aGF0IHByb3RvY29sIG9yIG90aGVyIHNwZWNpZmljYXRpb24gd29yayB0aGUgZHJhZnQg
aXMgc3VnZ2VzdGluZyB0aGF0IHRoZSBJRVRGIChhbmQgc3BlY2lmaWNhbGx5IFRTVldHKSB1bmRl
cnRha2UsIGFzIFNlY3Rpb24gNCBzYXlzOg0KPiA0LiAgTmV3IFByb3RvY29sIENvbnNpZGVyYXRp
b25zDQogPiBUaGlzIGRvY3VtZW50IGRvZXMgbm90IGNhbGwgZm9yIGNoYW5nZXMgb3IgYWRkaXRp
b25zOiBhbnkgbmV3IHNlc3Npb24sIHRyYW5zcG9ydCBvciBuZXR3b3JrIHByb3RvY29sczsgbmV3
IHByb3RvY29scyBmb3IgZGVsaXZlcmluZyBjb250ZW50IGZyb20gYSBVQVROIHRvIGFuIEVuZCBV
c2VyL1VzZXIgYWdlbnQ7IA0KPiBuZXcgcHJvdG9jb2xzIGZvciBpbmdlc3Rpb24gb2YgY29udGVu
dCBiZXR3ZWVuIGEgVUFUTiBhbmQgYSBVU1AuDQoNCi0gTWFueSBleGlzdGluZyBVcGxvYWQgU2Vy
dmljZSBQcm92aWRlcnMoVVNQcykgaGF2ZSBkZXBsb3llZCBvciBhcmUgZGVwbG95aW5nIHRoZWly
IG93biB1cGxvYWQgYWNjZWxlcmF0aW9uIG5ldHdvcmtzLCBvciBhcmUgc2NhbGluZyB1cCB0aGVp
ciBkYXRhIHNlcnZlcnMgaW5mcmFzdHJ1Y3R1cmUgdG8gZXhwYW5kIHVwc3RyZWFtIHRocm91Z2hw
dXQgdG8gaW1wcm92ZSB1c2VyIGV4cGVyaWVuY2UuIEhvd2V2ZXIsIG5vIHN0YW5kYXJkcyBvciBv
cGVuIHNwZWNpZmljYXRpb25zIGN1cnJlbnRseSBleGlzdCB0byBmYWNpbGl0YXRlIHN1Y2ggYWNj
ZWxlcmF0aW9uIGFwcHJvYWNoLiAgSU1PLCBJRVRGIG1heSBuZWVkIHRvIGdpdmUgYSAiZnJhbWV3
b3JrIiBkb2N1bWVudCBwcm92aWRpbmcgYSBkZXNjcmlwdGlvbiBvZiB0aGUgVXBsb2FkIEFjY2Vs
ZXJhdGlvbiBUcmFuc3BvcnQgTmV0d29yayhVQVROKSBhbmQgaG93IGl0IHdvcmtzLiBTbyB0aGF0
IGVuZCB1c2VycyBjYW4gdXNlIHRoZSBVQVROIHJlZ2FyZGxlc3Mgb2YgdGhhdCBFbmQgVXNlcidz
IGxvY2F0aW9uIG9yIGF0dGFjaG1lbnQgbmV0d29yay4gDQotIFRoZXJlIGFscmVhZHkgZXhpc3Rz
IHRyYW5zcG9ydCBwcm90b2NvbHMgYmV0d2VlbiBlbmQgdXNlciBhbmQgZGF0YSBjZW50ZXIsIHNv
LCBJTU8gLCBVQVROIGNhbiB1c2UgdGhlIGV4aXN0aW5nIHRyYW5zcG9ydCBwcm90b2NvbHMgdG8g
YXZvaWQgZGVmaW5pbmcgbmV3IHByb3RvY29scy4gSG93ZXZlciwgaXQgbmVlZHMgdG8gcG9pbnQg
b3V0IHdoaWNoIHRyYW5zcG9ydCBwcm90b2NvbC8gcHJvdG9jb2xzIGNhbiBiZSB1c2VkLg0KLUVz
cGVjaWFsbHksIGluIGV4aXN0aW5nIENETnMsIGNvbnRlbnQgaXMgbW92ZWQgdG8gRWRnZSBTZXJ2
ZXJzIGFoZWFkIG9mIHRpbWUgb3Igc2NoZWR1bGVkIHRpbWUsIGFuZCB0aGUgZGF0YSB0cmFuc21p
c3Npb24gc2VydmljZSBpcyAiZnJvbSBvbmUgc2VydmVyIHRvIG1hbnkgZW5kIHVzZXJzIi4gVGhl
IHVwbG9hZGluZyBvZiBlbmQgdXNlcnMgaXMgdW5leHBlY3RlZCBhbmQgdGhlIGRhdGEgdHJhbnNt
aXNzaW9uIGlzICJmcm9tIG1hbnkgZW5kIHVzZXJzIHRvIG9uZSBkYXRhIHNlcnZlciIuIFNvLCBV
QVROIGl0c2VsZiBtYXkgbmVlZCBhIG5ldyB0cmFuc3BvcnQgcHJvdG9jb2wgZm9yIG1vdmluZyBj
b250ZW50IG92ZXIgdGhlIGxvbmctaGF1bCBJbnRlcm5ldCB3aXRoIGhpZ2ggcmVsaWFiaWxpdHkg
YW5kIHBlcmZvcm1hbmNlLg0KDQpiZXN0IHdpc2hlcw0KWGlhb3dlaSBRaW4gDQpGcm9tOiBCbGFj
aywgRGF2aWQNCkRhdGU6IDIwMTUtMDYtMTcgMDQ6NTMNClRvOiBxaW54aWFvd2VpQGNubmljLmNu
DQpDQzogdHN2d2c7IGdvcnJ5OyBCbGFjaywgRGF2aWQNClN1YmplY3Q6IFJFOiBSZTpbdHN2d2dd
IEFnZW5kYSByZXF1ZXN0IGZvciB0aGUgVFNWV0cgbWVldGluZyBpbiBQcmFndWUNCkRlYXIgWGlh
b3dlaSwNCiANCkZpcnN0IG9mIGFsbCwgd2UgKFdHIGNoYWlycykgd2FudCB0byB0aGFuayB5b3Ug
Zm9yIHNldHRpbmcgYSBnb29kIGV4YW1wbGUNCm9mIGhvdyB0byBnbyBhYm91dCBicmluZ2luZyBp
ZGVhcyBmb3IgbmV3IHdvcmsgdG8gdGhlIElFVEYuICBUaGUgLTAwDQpVQVROIGRyYWZ0IHdhcyBz
dWJtaXR0ZWQgd2VsbCBiZWZvcmUgdGhlIDItd2VlayBwcmUtbWVldGluZyBjdXRvZmYsDQp0aGUg
c3VibWlzc2lvbiB3YXMgYW5ub3VuY2VkIHRvIHRoZSByZWxldmFudCBtYWlsaW5nIGxpc3RzLCBh
bmQgdGhlcmXigJlzDQpiZWVuIHNvbWUgZGlzY3Vzc2lvbiBvbiB0aGUgbGlzdHMuDQogDQpBbGwg
b2YgdGhvc2Ugc3RlcHMgYXJlIGFwcHJlY2lhdGVkLCBhbmQgYXJlIG11Y2ggYmV0dGVyIHRoYW4g
dGhlDQphbHRlcm5hdGl2ZSBhcHByb2FjaCBvZiBzdWJtaXR0aW5nIGEgLTAwIGRyYWZ0IHJpZ2h0
IGF0IHRoZSAyLXdlZWsNCnByZS1tZWV0aW5nIGN1dG9mZiBhbmQgdGhlbiBpbW1lZGlhdGVseSBh
c2tpbmcgZm9yIGFnZW5kYSB0aW1lLiAgVGhlDQpXRyBjaGFpcnMgdXN1YWxseSB0dXJuIGRvd24g
dGhlIGxhdHRlciBzb3J0IG9mIHJlcXVlc3QsIGFzIHdlIHdhbnQgdG8NCnNlZSBzb21lIGxldmVs
IG9mIGludGVyZXN0IGluIHRoZSBwcm9wb3NlZCBhY3Rpdml0eSBiYXNlZCBvbiBsaXN0DQpkaXNj
dXNzaW9uLg0KIA0KVHVybmluZyB0byB0aGUgVUFUTiBkcmFmdCBpdHNlbGYsIHdlIChXRyBjaGFp
cnMpIGhhdmUgYSBmZXcgY29uY2VybnM6DQogDQotIFdl4oCZcmUgbm90IHN1cmUgd2hldGhlciB0
aGlzIGRyYWZ0IGJlbG9uZ3MgaW4gdGhlIFRTViBBcmVhIHZzLiB0aGUgQVJUDQogICAgICBBcmVh
LiAgQXMgYSBDRE4tcmVsYXRlZCBkcmFmdCwgaXQgbWF5IGJlbG9uZyBvdmVyIGluIEFSVCwgYXQg
dGhhdOKAmXMNCnRoZSBJRVRGIEFyZWEgaW50byB3aGljaCB0aGUgQ0ROSSBXRyB3YXMgcmVjZW50
bHkgbW92ZWQuDQotIFdlIGhhdmVu4oCZdCBzZWVuIGFueSBpbnRlcmVzdCBleHByZXNzZWQgaW4g
dGhpcyB3b3JrIGZyb20gcGVvcGxlIG90aGVyDQogICAgICB0aGFuIHRoZSBhdXRob3JzIGVpdGhl
ciBoZXJlIG9yIG9uIHRoZSBhcHBzLWRpc2N1c3MgbGlzdCAoaW4gQVJUKS4NCldl4oCZbGwgY29u
dGludWUgdG8gd2F0Y2ggdGhlIG1haWxpbmcgbGlzdHMuDQotIFdl4oCZcmUgdW5jbGVhciBvbiB3
aGF0IHByb3RvY29sIG9yIG90aGVyIHNwZWNpZmljYXRpb24gd29yayB0aGUgZHJhZnQNCmlzIHN1
Z2dlc3RpbmcgdGhhdCB0aGUgSUVURiAoYW5kIHNwZWNpZmljYWxseSBUU1ZXRykgdW5kZXJ0YWtl
LA0KYXMgU2VjdGlvbiA0IHNheXM6DQogDQo0LiAgTmV3IFByb3RvY29sIENvbnNpZGVyYXRpb25z
DQogDQogICBUaGlzIGRvY3VtZW50IGRvZXMgbm90IGNhbGwgZm9yIGNoYW5nZXMgb3IgYWRkaXRp
b25zOiBhbnkgbmV3DQogICBzZXNzaW9uLCB0cmFuc3BvcnQgb3IgbmV0d29yayBwcm90b2NvbHM7
IG5ldyBwcm90b2NvbHMgZm9yIGRlbGl2ZXJpbmcNCiAgIGNvbnRlbnQgZnJvbSBhIFVBVE4gdG8g
YW4gRW5kIFVzZXIvVXNlciBhZ2VudDsgbmV3IHByb3RvY29scyBmb3INCiAgIGluZ2VzdGlvbiBv
ZiBjb250ZW50IGJldHdlZW4gYSBVQVROIGFuZCBhIFVTUC4NCiANCiAgICAgIChodHRwczovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtcWluLXRzdndnLXVhdG51dC0wMCNzZWN0aW9uLTQpDQog
DQpXZeKAmWQgYXBwcmVjaWF0ZSBzb21lIGNsYXJpZmljYXRpb24gb24gdGhlIGxhdHRlciBjb25j
ZXJuLCBhbmQgd2XigJlsbA0KY29udGludWUgdG8gd2F0Y2ggbWFpbGluZyBsaXN0IGRpc2N1c3Np
b24sIGJ1dCBpdOKAmXMgbm90IGFwcHJvcHJpYXRlIHRvDQpwdXQgdGhlIFVBVE4gZHJhZnQgb24g
dGhlIHRzdndnIGFnZW5kYSBhdCB0aGlzIHRpbWUuICBUaGUgYWdlbmRhIHdpbGwNCmV2b2x2ZSBi
ZXR3ZWVuIG5vdyBhbmQgdGhlIFByYWd1ZSBtZWV0aW5nLCBzbyB0aGVyZSBtYXkgYmUgYW4gb3Bw
b3J0dW5pdHkNCnRvIGFkZCB0aW1lIGZvciB0aGUgZHJhZnQgbGF0ZXIgb24uDQogDQpUaGFua3Ms
DQotLURhdmlkIGFuZCBHb3JyeSAodHN2d2cgY2hhaXJzKQ0KIA0KRnJvbTogcWlueGlhb3dlaUBj
bm5pYy5jbiBbbWFpbHRvOnFpbnhpYW93ZWlAY25uaWMuY25dIA0KU2VudDogTW9uZGF5LCBKdW5l
IDE1LCAyMDE1IDk6MzggUE0NClRvOiBCbGFjaywgRGF2aWQ7IGdvcnJ5DQpDYzogdHN2d2cNClN1
YmplY3Q6IFJlOlt0c3Z3Z10gQWdlbmRhIHJlcXVlc3QgZm9yIHRoZSBUU1ZXRyBtZWV0aW5nIGlu
IFByYWd1ZQ0KIA0KRGVhciBHb3JyeSAmIERhdmlkLCANCg0KDQpJIHdvdWxkIGxpa2UgdG8gaGF2
ZSBhIDE1LW1pbnV0ZSB0aW1lIHNsb3QgIHRvIHByZXNlbnQgdGhlIFVBVE4gdG8gb3VyIGZvbGtz
IGluIHRoZSBQcmFndWUgSUVURiBtZWV0aW5nLiANCiAgSSBoYXZlIGFscmVhZHkgcHJvcG9zZWQg
YW4gYXBwcm9hY2ggdG8gVXBsb2FkIEFjY2VsZXJhdGlvbiBUcmFuc3BvcnQgTmV0d29yayhVQVRO
KSBmb3IgdXBzdHJlYW0gdHJhZmZpY3MsIGFuZCB0aGUgZHJhZnRzIHdhcyBzdWJtaXR0ZWQuICAN
CiAgIFRoaXMgaXMgdGhlIGxpbmssIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LXFpbi10c3Z3Zy11YXRudXQvDQogDQpSZWdhcmRzLA0KWGlhb3dlaSBRaW4NCiANCiANCiAN
Ckl0IGlzIHRpbWUgdG8gc3RhcnQgYnVpbGRpbmcgdGhlIFRTVldHIG1lZXRpbmcgYWdlbmRhIGZv
ciB0aGUgUHJhZ3VlIElFVEZtZWV0aW5nLuKAoiBBcyB1c3VhbCwgaWYgeW91IGVkaXQgYSBXRyBk
cmFmdCwgcGxlYXNlIGNvbnRhY3QgdGhlIGNoYWlycyBhbmQgbGV0IHVza25vdyB3aGV0aGVyIHdl
IHNob3VsZCBleHBlY3QgYSBzaG9ydCB1cGRhdGUgb3Igd2hldGhlciB5b3UgdGhpbmsgeW91Y291
bGQgYmVuZWZpdCBmcm9tIGEgbG9uZ2VyIHNsb3QgdG8gZGlzY3VzcyBpc3N1ZXMu4oCiIElmIHlv
dSB3b3VsZCBsaWtlIHRvIHByZXNlbnQgb3RoZXIgd29yayBpbiB0c3Z3ZywgcGxlYXNlIHNlbmQg
YW4gZW1haWx0byB0aGUgQ2hhaXJzIGFzYXAgLSBzbyB0aGluZ3MgY2FuIGJlIGRpc2N1c3NlZCBv
biB0aGUgbGlzdCBwcmlvciB0byB0aGVtZWV0aW5nLk5vdGU6IHBsZWFzZSBiZSBzdXJlIHRvIGVt
YmVkICJ0c3Z3ZyJpbiB0aGUgZmlsZW5hbWUgb2YgYWxsIG5ld2RyYWZ0cy5QbGVhc2Ugc2VuZCBy
ZXF1ZXN0cyBhcyBzb29uIGFzIHBvc3NpYmxlLlRoYW5rcyFHb3JyeSAmIERhdmlkKHRzdndnIENv
LUNoYWlycykNCg0KDQo=

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

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DUTF-8"><style>body { line-height: 1.5; }blockquote { margin-top: 0px; =
margin-bottom: 0px; margin-left: 0.5em; }p { margin-top: 0px; margin-botto=
m: 0px; }div.foxdiv20150619134458969989 { }body { font-size: 10.5pt; font-=
family: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91; color: rgb(0, 0, 0); line-he=
ight: 1.5; }</style></head><body>=0A<!--[if gte mso 9]><xml>=0A<o:shapedef=
aults v:ext=3D"edit" spidmax=3D"1026" ></o:shapedefaults>=0A</xml><![endif=
]--><!--[if gte mso 9]><xml>=0A<o:shapelayout v:ext=3D"edit">=0A<o:idmap v=
:ext=3D"edit" data=3D"1" ></o:idmap>=0A</o:shapelayout></xml><![endif]-->=
=0A<div><span></span>Dear&nbsp;<span style=3D"line-height: 19px;">David</s=
pan><span style=3D"line-height: 19px;">&nbsp;,</span></div><div><span styl=
e=3D"font-family: &quot;" courier=3D"" new'";=3D"" font-size:=3D"" 13px;=
=3D"" color:=3D"" rgb(0,=3D"" 0,=3D"" 0);=3D"" background-color:=3D"" rgb(=
255,=3D"" 255,=3D"" 255);=3D"" font-weight:=3D"" normal;=3D"" font-style:=
=3D"" normal;text-decoration:=3D"" none;'=3D"">Thanks for you letter.</spa=
n></div><div><span style=3D"font-family: &quot;" courier=3D"" new'";=3D"" =
font-size:=3D"" 13px;=3D"" color:=3D"" rgb(0,=3D"" 0,=3D"" 0);=3D"" backgr=
ound-color:=3D"" rgb(255,=3D"" 255,=3D"" 255);=3D"" font-weight:=3D"" norm=
al;=3D"" font-style:=3D"" normal;text-decoration:=3D"" none;'=3D""><br></s=
pan></div><div><span style=3D"background-color: rgba(0, 0, 0, 0);">Perhaps=
 UATN is an new ideas, so has not attracted people's concerns up to now.&n=
bsp;</span><span style=3D"background-color: rgba(0, 0, 0, 0); font-size: 1=
0.5pt; line-height: 1.5;">IMO, as mobile devices developing, however, the =
UATN will be used widely in the future.</span></div><div><br></div><div><s=
pan style=3D"font-family: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91, Tahoma; li=
ne-height: normal; font-size: 10.5pt; background-color: window;">&gt;</spa=
n><span style=3D"font-family: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91, Tahoma=
; line-height: normal; font-size: 10.5pt; background-color: window;">&nbsp=
;</span><span style=3D"font-size: 10.5pt; line-height: 1.5; background-col=
or: window;">&nbsp;We=E2=80=99re unclear on what protocol or other specifi=
cation work the draft&nbsp;</span><span style=3D"text-indent: 0.5in; font-=
size: 10.5pt; line-height: 1.5; background-color: window;">is suggesting t=
hat the IETF (and specifically TSVWG) undertake,&nbsp;</span><span style=
=3D"text-indent: 0.5in; font-size: 10.5pt; line-height: 1.5; background-co=
lor: window;">as Section 4 says:</span></div><div><span style=3D"font-fami=
ly: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91, Tahoma; line-height: normal; fon=
t-size: 10.5pt; background-color: window;">&gt;</span><span style=3D"font-=
family: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91, Tahoma; line-height: normal;=
 font-size: 10.5pt; background-color: window;">&nbsp;</span><span style=3D=
"background-color: window; font-size: 10.5pt; line-height: 1.5; text-inden=
t: 0.5in;">4.&nbsp; New Protocol Considerations</span></div><div><span sty=
le=3D"background-color: window; font-size: 10.5pt; line-height: 1.5; text-=
indent: 0.5in;">&nbsp;</span><span style=3D"font-family: =E5=BE=AE=E8=BD=
=AF=E9=9B=85=E9=BB=91, Tahoma; line-height: normal; font-size: 10.5pt; bac=
kground-color: window;">&gt;</span><span style=3D"font-family: =E5=BE=AE=
=E8=BD=AF=E9=9B=85=E9=BB=91, Tahoma; line-height: normal; font-size: 10.5p=
t; background-color: window;">&nbsp;</span><span style=3D"font-size: 10.5p=
t; line-height: 1.5; background-color: window; text-indent: 0.5in;">This d=
ocument does not call for changes or additions: any new</span><span style=
=3D"font-size: 10.5pt; line-height: 1.5; text-indent: 0.5in; background-co=
lor: window;">&nbsp;session, transport or network protocols; new protocols=
 for delivering</span><span style=3D"font-size: 10.5pt; line-height: 1.5; =
text-indent: 0.5in; background-color: window;">&nbsp;content from a UATN t=
o an End User/User agent;&nbsp;</span></div><div><span style=3D"font-famil=
y: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91, Tahoma; line-height: normal; font=
-size: 10.5pt; background-color: window;">&gt;</span><span style=3D"font-f=
amily: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91, Tahoma; line-height: normal; =
font-size: 10.5pt; background-color: window;">&nbsp;</span><span style=3D"=
font-size: 10.5pt; line-height: 1.5; text-indent: 0.5in; background-color:=
 window;">new protocols&nbsp;</span><span style=3D"font-size: 10.5pt; line=
-height: 1.5; text-indent: 0.5in; background-color: window;">for&nbsp;</sp=
an><span style=3D"font-size: 10.5pt; line-height: 1.5; text-indent: 0.5in;=
 background-color: window;">ingestion of content between a UATN and a USP.=
</span></div><div><span style=3D"background-color: rgba(0, 0, 0, 0); font-=
size: 10.5pt; line-height: 1.5;"><br></span></div><div><span style=3D"font=
-family: 'Courier New'; font-size: 13px; line-height: 19px; background-col=
or: window;">-</span><span style=3D"font-family: 'Courier New'; font-size:=
 13px; line-height: 19px; background-color: window;">&nbsp;</span><span st=
yle=3D"background-color: rgba(0, 0, 0, 0);">Many existing Upload Service P=
roviders(USPs) have deployed or are deploying their own upload acceleratio=
n networks, or are scaling up their data servers infrastructure to expand =
upstream throughput to improve user experience. However, no standards or o=
pen specifications currently exist to facilitate such acceleration approac=
h. &nbsp;IMO, IETF may need to give a "framework" document providing a des=
cription of the Upload Acceleration Transport Network(UATN) and how it wor=
ks. So that end users can use the UATN regardless of that End User's locat=
ion or attachment network.&nbsp;</span></div><div><span style=3D"font-fami=
ly: 'Courier New'; font-size: 13px; line-height: 19px;">-&nbsp;</span><spa=
n style=3D"font-family: ''; font-size: 10.5pt; line-height: 1.5; backgroun=
d-color: window;">There already exists transport protocols between end use=
r and data center, so, IMO , UATN can use the existing transport protocols=
 to avoid defining new protocols. However, it needs to point out which tra=
nsport protocol/ protocols can be used.</span></div><div><span style=3D"fo=
nt-family: 'Courier New'; font-size: 13px; line-height: 19px; background-c=
olor: window;">-</span>Especially, in existing CDNs, content is moved to E=
dge Servers ahead of time or scheduled time, and the data transmission ser=
vice is "from one server to many end users". The uploading of end users is=
 unexpected and the data transmission is "from many end users to one data =
server". So, UATN itself may need a new transport protocol for moving cont=
ent over the long-haul Internet with high reliability and performance.</di=
v><div><br></div><div><span style=3D"color: rgb(51, 51, 51); font-family: =
arial, tahoma, 'Microsoft Yahei', =E5=AE=8B=E4=BD=93, sans-serif; font-siz=
e: 16px; line-height: 32px; background-color: window;">best wishes</span><=
/div><div>Xiaowei Qin<span style=3D"font-size: 10.5pt; line-height: 1.5; b=
ackground-color: window;">&nbsp;</span></div><blockquote style=3D"margin-t=
op: 0px; margin-bottom: 0px; margin-left: 0.5em;"><div style=3D"border:non=
e;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><div style=3D"=
PADDING-RIGHT: 8px; PADDING-LEFT: 8px; FONT-SIZE: 12px;FONT-FAMILY:tahoma;=
COLOR:#000000; BACKGROUND: #efefef; PADDING-BOTTOM: 8px; PADDING-TOP: 8px"=
><div><b>From:</b>&nbsp;<a href=3D"mailto:david.black@emc.com" style=3D"co=
lor: blue; text-decoration: underline;">Black, David</a></div><div><b>Date=
:</b>&nbsp;2015-06-17&nbsp;04:53</div><div><b>To:</b>&nbsp;<a href=3D"mail=
to:qinxiaowei@cnnic.cn" style=3D"color: blue; text-decoration: underline;"=
>qinxiaowei@cnnic.cn</a></div><div><b>CC:</b>&nbsp;<a href=3D"mailto:tsvwg=
@ietf.org" style=3D"color: blue; text-decoration: underline;">tsvwg</a>; <=
a href=3D"mailto:gorry@erg.abdn.ac.uk" style=3D"color: blue; text-decorati=
on: underline;">gorry</a>; <a href=3D"mailto:david.black@emc.com" style=3D=
"color: blue; text-decoration: underline;">Black, David</a></div><div><b>S=
ubject:</b>&nbsp;RE: Re:[tsvwg] Agenda request for the TSVWG meeting in Pr=
ague</div></div></div><div><div class=3D"FoxDiv20150619134458969989">=0A<!=
--[if gte mso 9]><xml>=0A<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" =
></o:shapedefaults>=0A</xml><![endif]--><!--[if gte mso 9]><xml>=0A<o:shap=
elayout v:ext=3D"edit">=0A<o:idmap v:ext=3D"edit" data=3D"1" ></o:idmap>=
=0A</o:shapelayout></xml><![endif]-->=0A<div class=3D"WordSection1" style=
=3D"page: WordSection1;">=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0i=
n 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span=
 style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black=
">Dear Xiaowei,<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"ma=
rgin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', s=
erif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;=
;color:black"><o:p>&nbsp;</o:p></span></p>=0A<p class=3D"MsoNormal" style=
=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Rom=
an', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New=
&quot;;color:black">First of all, we (WG chairs) want to thank you for set=
ting a good example<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=
=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Rom=
an', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New=
&quot;;color:black">of how to go about bringing ideas for new work to the =
IETF.&nbsp; The -00<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=
=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Rom=
an', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New=
&quot;;color:black">UATN draft was submitted well before the 2-week pre-me=
eting cutoff,<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"marg=
in: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', ser=
if;"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;c=
olor:black">the submission was announced to the relevant mailing lists, an=
d there=E2=80=99s<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"=
margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman',=
 serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;;color:black">been some discussion on the lists.<o:p></o:p></span></p>=
=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12=
pt; font-family: 'Times New Roman', serif;"><span style=3D"font-size:10.0p=
t;font-family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span=
></p>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-siz=
e: 12pt; font-family: 'Times New Roman', serif;"><span style=3D"font-size:=
10.0pt;font-family:&quot;Courier New&quot;;color:black">All of those steps=
 are appreciated, and are much better than the<o:p></o:p></span></p>=0A<p =
class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; fo=
nt-family: 'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font=
-family:&quot;Courier New&quot;;color:black">alternative approach of submi=
tting a -00 draft right at the 2-week<o:p></o:p></span></p>=0A<p class=3D"=
MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family=
: 'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black">pre-meeting cutoff and then immediatel=
y asking for agenda time.&nbsp; The<o:p></o:p></span></p>=0A<p class=3D"Ms=
oNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;;color:black">WG chairs usually turn down the latter s=
ort of request, as we want to<o:p></o:p></span></p>=0A<p class=3D"MsoNorma=
l" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times=
 New Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Cou=
rier New&quot;;color:black">see some level of interest in the proposed act=
ivity based on list<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=
=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Rom=
an', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New=
&quot;;color:black">discussion.<o:p></o:p></span></p>=0A<p class=3D"MsoNor=
mal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Tim=
es New Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>=0A<p class=3D"M=
soNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family:=
 'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&q=
uot;Courier New&quot;;color:black">Turning to the UATN draft itself, we (W=
G chairs) have a few concerns:<o:p></o:p></span></p>=0A<p class=3D"MsoNorm=
al" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>=0A<p class=3D"Ms=
oNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;;color:black">- We=E2=80=99re not sure whether this dr=
aft belongs in the TSV Area vs. the ART<o:p></o:p></span></p>=0A<p class=
=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-fa=
mily: 'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Courier New&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are=
a.&nbsp; As a CDN-related draft, it may belong over in ART, at that=E2=80=
=99s<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"text-indent: =
0.5in; margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;;color:black">the IETF Area into which the CDNI WG was recently m=
oved.<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><sp=
an style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:bla=
ck">- We haven=E2=80=99t seen any interest expressed in this work from peo=
ple other<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"=
><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color=
:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; than the authors either here or on =
the apps-discuss list (in ART).<o:p></o:p></span></p>=0A<p class=3D"MsoNor=
mal" style=3D"text-indent: 0.5in; margin: 0in 0in 0.0001pt; font-size: 12p=
t; font-family: 'Times New Roman', serif;"><span style=3D"font-size:10.0pt=
;font-family:&quot;Courier New&quot;;color:black">We=E2=80=99ll continue t=
o watch the mailing lists.<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times Ne=
w Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courie=
r New&quot;;color:black">- We=E2=80=99re unclear on what protocol or other=
 specification work the draft<o:p></o:p></span></p>=0A<p class=3D"MsoNorma=
l" style=3D"text-indent: 0.5in; margin: 0in 0in 0.0001pt; font-size: 12pt;=
 font-family: 'Times New Roman', serif;"><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Courier New&quot;;color:black">is suggesting that the IET=
F (and specifically TSVWG) undertake,<o:p></o:p></span></p>=0A<p class=3D"=
MsoNormal" style=3D"text-indent: 0.5in; margin: 0in 0in 0.0001pt; font-siz=
e: 12pt; font-family: 'Times New Roman', serif;"><span style=3D"font-size:=
10.0pt;font-family:&quot;Courier New&quot;;color:black">as Section 4 says:=
<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"text-indent: 0.5i=
n; margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roma=
n', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&=
quot;;color:black"><o:p>&nbsp;</o:p></span></p>=0A<p class=3D"MsoNormal" s=
tyle=3D"text-indent: 0.5in; margin: 0in 0in 0.0001pt; font-size: 12pt; fon=
t-family: 'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">4.&nbsp; New Protocol Consider=
ations<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"text-indent=
: 0.5in; margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times Ne=
w Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courie=
r New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>=0A<p class=3D"MsoNor=
mal" style=3D"text-indent: 0.5in; margin: 0in 0in 0.0001pt; font-size: 12p=
t; font-family: 'Times New Roman', serif;"><span style=3D"font-size:10.0pt=
;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp; This docume=
nt does not call for changes or additions: any new<o:p></o:p></span></p>=
=0A<p class=3D"MsoNormal" style=3D"text-indent: 0.5in; margin: 0in 0in 0.0=
001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black">&nb=
sp;&nbsp; session, transport or network protocols; new protocols for deliv=
ering<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"text-indent:=
 0.5in; margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New=
 Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courier=
 New&quot;;color:black">&nbsp;&nbsp; content from a UATN to an End User/Us=
er agent; new protocols for<o:p></o:p></span></p>=0A<p class=3D"MsoNormal"=
 style=3D"text-indent: 0.5in; margin: 0in 0in 0.0001pt; font-size: 12pt; f=
ont-family: 'Times New Roman', serif;"><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp; ingestion of co=
ntent between a UATN and a USP.<o:p></o:p></span></p>=0A<p class=3D"MsoNor=
mal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Tim=
es New Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>=0A<p class=3D"M=
soNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family:=
 'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&q=
uot;Courier New&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (<a href=
=3D"https://tools.ietf.org/html/draft-qin-tsvwg-uatnut-00#section-4" style=
=3D"color: blue; text-decoration: underline;">https://tools.ietf.org/html/=
draft-qin-tsvwg-uatnut-00#section-4</a>)<o:p></o:p></span></p>=0A<p class=
=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-fa=
mily: 'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>=0A<p =
class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; fo=
nt-family: 'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font=
-family:&quot;Courier New&quot;;color:black">We=E2=80=99d appreciate some =
clarification on the latter concern, and we=E2=80=99ll<o:p></o:p></span></=
p>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif;"><span style=3D"font-size:10.=
0pt;font-family:&quot;Courier New&quot;;color:black">continue to watch mai=
ling list discussion, but it=E2=80=99s not appropriate to<o:p></o:p></span=
></p>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-siz=
e: 12pt; font-family: 'Times New Roman', serif;"><span style=3D"font-size:=
10.0pt;font-family:&quot;Courier New&quot;;color:black">put the UATN draft=
 on the tsvwg agenda at this time.&nbsp; The agenda will<o:p></o:p></span>=
</p>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size=
: 12pt; font-family: 'Times New Roman', serif;"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Courier New&quot;;color:black">evolve between now =
and the Prague meeting, so there may be an opportunity<o:p></o:p></span></=
p>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif;"><span style=3D"font-size:10.=
0pt;font-family:&quot;Courier New&quot;;color:black">to add time for the d=
raft later on.<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"mar=
gin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', se=
rif;"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black"><o:p>&nbsp;</o:p></span></p>=0A<div>=0A<div>=0A<p class=3D"Ms=
oNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;;color:black">Thanks,<br>=0A--David and Gorry (tsvwg c=
hairs)</span><span style=3D"font-size:11.0pt;font-family:&quot;Courier New=
&quot;;color:black"><o:p></o:p></span></p>=0A</div>=0A</div>=0A<p class=3D=
"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-famil=
y: 'Times New Roman', serif;"><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>=0A<div s=
tyle=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt=
">=0A<div>=0A<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padd=
ing:3.0pt 0in 0in 0in">=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-seri=
f&quot;">From:</span></b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;"> qinxiaowei@cnnic.cn [mailto:qinxiao=
wei@cnnic.cn]=0A<br>=0A<b>Sent:</b> Monday, June 15, 2015 9:38 PM<br>=0A<b=
>To:</b> Black, David; gorry<br>=0A<b>Cc:</b> tsvwg<br>=0A<b>Subject:</b> =
Re:[tsvwg] Agenda request for the TSVWG meeting in Prague<o:p></o:p></span=
></p>=0A</div>=0A</div>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p>&n=
bsp;</o:p></p>=0A<div>=0A<div>=0A<p class=3D"MsoNormal" style=3D"margin: 0=
in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">=
<span style=3D"font-size:10.5pt;font-family:&quot;Microsoft YaHei&quot;,&q=
uot;sans-serif&quot;;color:black">Dear&nbsp;Gorry &amp; David,=0A<o:p></o:=
p></span></p>=0A</div>=0A<div>=0A<p class=3D"MsoNormal" style=3D"margin: 0=
in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">=
<span style=3D"font-size:10.5pt;font-family:&quot;Microsoft YaHei&quot;,&q=
uot;sans-serif&quot;;color:black;background:white"><br>=0A<br>=0A</span><s=
pan style=3D"font-size:10.5pt;font-family:&quot;Microsoft YaHei&quot;,&quo=
t;sans-serif&quot;;color:black"><o:p></o:p></span></p>=0A</div>=0A<div>=0A=
<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;=
 font-family: 'Times New Roman', serif;"><span style=3D"font-size:10.5pt;f=
ont-family:&quot;Microsoft YaHei&quot;,&quot;sans-serif&quot;;color:black;=
background:white">I would like to have a 15-minute time slot &nbsp;to&nbsp=
;present the UATN to our folks&nbsp;in the Prague IETF meeting.&nbsp;</spa=
n><span style=3D"font-size:10.5pt;font-family:&quot;Microsoft YaHei&quot;,=
&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>=0A</div>=0A<div=
>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 1=
2pt; font-family: 'Times New Roman', serif;"><span style=3D"font-size:10.5=
pt;font-family:&quot;Microsoft YaHei&quot;,&quot;sans-serif&quot;;color:bl=
ack;background:white">&nbsp; I have already proposed an approach to Upload=
 Acceleration Transport Network(UATN) for upstream traffics, and&nbsp;the =
drafts was submitted.=0A &nbsp;</span><span style=3D"font-size:10.5pt;font=
-family:&quot;Microsoft YaHei&quot;,&quot;sans-serif&quot;;color:black"><o=
:p></o:p></span></p>=0A</div>=0A<div>=0A<p class=3D"MsoNormal" style=3D"ma=
rgin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', s=
erif;"><span style=3D"font-size:10.5pt;font-family:&quot;Microsoft YaHei&q=
uot;,&quot;sans-serif&quot;;color:black;background:white">&nbsp; &nbsp;Thi=
s is the link,&nbsp;<a href=3D"https://datatracker.ietf.org/doc/draft-qin-=
tsvwg-uatnut/" style=3D"color: blue; text-decoration: underline;">https://=
datatracker.ietf.org/doc/draft-qin-tsvwg-uatnut/</a></span><span style=3D"=
font-size:10.5pt;font-family:&quot;Microsoft YaHei&quot;,&quot;sans-serif&=
quot;;color:black"><o:p></o:p></span></p>=0A</div>=0A<blockquote style=3D"=
margin-left: 6pt; margin-top: 0px;">=0A<div>=0A<div>=0A<div>=0A<div>=0A<p =
class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; fo=
nt-family: 'Times New Roman', serif;"><span style=3D"font-size:10.5pt;font=
-family:&quot;Microsoft YaHei&quot;,&quot;sans-serif&quot;;color:black"><o=
:p>&nbsp;</o:p></span></p>=0A</div>=0A</div>=0A<div>=0A<p class=3D"MsoNorm=
al" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;"><span style=3D"font-size:10.5pt;font-family:&quot;Mi=
crosoft YaHei&quot;,&quot;sans-serif&quot;;color:black">Regards,<o:p></o:p=
></span></p>=0A</div>=0A</div>=0A<div>=0A<p class=3D"MsoNormal" style=3D"m=
argin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><span style=3D"font-size:10.5pt;font-family:&quot;Microsoft YaHei&=
quot;,&quot;sans-serif&quot;;color:black">Xiaowei Qin<o:p></o:p></span></p=
>=0A</div>=0A</div>=0A</blockquote>=0A</div>=0A<div>=0A<p class=3D"MsoNorm=
al" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;"><span style=3D"font-size:10.5pt;font-family:&quot;Mi=
crosoft YaHei&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p><=
/span></p>=0A</div>=0A<div>=0A<p class=3D"MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><sp=
an style=3D"font-size:10.5pt;font-family:&quot;Microsoft YaHei&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>=0A</div>=0A<di=
v>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif;"><span style=3D"font-size:10.=
5pt;font-family:&quot;Microsoft YaHei&quot;,&quot;sans-serif&quot;;color:b=
lack"><o:p>&nbsp;</o:p></span></p>=0A</div>=0A<div>=0A<pre style=3D"vertic=
al-align: baseline; font-stretch: inherit; line-height: inherit; white-spa=
ce: pre-wrap; word-wrap: break-word; margin: 0in 0in 0.0001pt; font-size: =
10pt; font-family: 'Courier New';"><span style=3D"font-family:Courier;colo=
r:black">It is time to start building the TSVWG meeting agenda for the Pra=
gue IETF<o:p></o:p></span></pre>=0A<pre style=3D"vertical-align: baseline;=
 margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><=
span style=3D"font-family:Courier;color:black">meeting.<o:p></o:p></span><=
/pre>=0A<pre style=3D"vertical-align: baseline; margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';"><span style=3D"font-family:C=
ourier;color:black">=E2=80=A2 As usual, if you edit a WG draft, please con=
tact the chairs and let us<o:p></o:p></span></pre>=0A<pre style=3D"vertica=
l-align: baseline; margin: 0in 0in 0.0001pt; font-size: 10pt; font-family:=
 'Courier New';"><span style=3D"font-family:Courier;color:black">know whet=
her we should expect a short update or whether you think you<o:p></o:p></s=
pan></pre>=0A<pre style=3D"vertical-align: baseline; margin: 0in 0in 0.000=
1pt; font-size: 10pt; font-family: 'Courier New';"><span style=3D"font-fam=
ily:Courier;color:black">could benefit from a longer slot to discuss issue=
s.<o:p></o:p></span></pre>=0A<pre style=3D"vertical-align: baseline; margi=
n: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span s=
tyle=3D"font-family:Courier;color:black">=E2=80=A2 If you would like to pr=
esent other work in tsvwg, please send an email<o:p></o:p></span></pre>=0A=
<pre style=3D"vertical-align: baseline; margin: 0in 0in 0.0001pt; font-siz=
e: 10pt; font-family: 'Courier New';"><span style=3D"font-family:Courier;c=
olor:black">to the Chairs asap - so things can be discussed on the list pr=
ior to the<o:p></o:p></span></pre>=0A<pre style=3D"vertical-align: baselin=
e; margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"=
><span style=3D"font-family:Courier;color:black">meeting.Note: please be s=
ure to embed "tsvwg"in the filename of all new<o:p></o:p></span></pre>=0A<=
pre style=3D"vertical-align: baseline; margin: 0in 0in 0.0001pt; font-size=
: 10pt; font-family: 'Courier New';"><span style=3D"font-family:Courier;co=
lor:black">drafts.<o:p></o:p></span></pre>=0A<pre style=3D"vertical-align:=
 baseline; margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courie=
r New';"><span style=3D"font-family:Courier;color:black">Please send reque=
sts as soon as possible.<o:p></o:p></span></pre>=0A<pre style=3D"vertical-=
align: baseline; margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: '=
Courier New';"><span style=3D"font-family:Courier;color:black">Thanks!<o:p=
></o:p></span></pre>=0A<pre style=3D"vertical-align: baseline; margin: 0in=
 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span style=
=3D"font-family:Courier;color:black">Gorry &amp; David<o:p></o:p></span></=
pre>=0A<pre style=3D"vertical-align: baseline; margin: 0in 0in 0.0001pt; f=
ont-size: 10pt; font-family: 'Courier New';"><span style=3D"font-family:Co=
urier;color:black">(tsvwg Co-Chairs)<o:p></o:p></span></pre>=0A</div>=0A<d=
iv class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;=
 font-family: 'Times New Roman', serif;"><span style=3D"font-size:10.5pt;f=
ont-family:&quot;Microsoft YaHei&quot;,&quot;sans-serif&quot;;color:black"=
>=0A<hr size=3D"1" width=3D"210" style=3D"width:157.5pt" noshade=3D"" alig=
n=3D"left">=0A</span></div>=0A</div>=0A</div>=0A</div></div></blockquote>=
=0A</body></html>
------=_001_NextPart217547876082_=------




From nobody Fri Jun 19 04:27:43 2015
Return-Path: <Kevin.Smith@vodafone.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 41A581A8984 for <tsvwg@ietfa.amsl.com>; Fri, 19 Jun 2015 04:27:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 GgBgYopIbTXa for <tsvwg@ietfa.amsl.com>; Fri, 19 Jun 2015 04:27:40 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.168]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FEEC1A8960 for <tsvwg@ietf.org>; Fri, 19 Jun 2015 04:27:40 -0700 (PDT)
Received: from [85.158.138.179] by server-8.bemta-3.messagelabs.com id 64/06-10593-AACF3855; Fri, 19 Jun 2015 11:27:38 +0000
X-Env-Sender: Kevin.Smith@vodafone.com
X-Msg-Ref: server-14.tower-169.messagelabs.com!1434713258!13412291!1
X-Originating-IP: [195.232.244.135]
X-StarScan-Received: 
X-StarScan-Version: 6.13.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22372 invoked from network); 19 Jun 2015 11:27:38 -0000
Received: from mailout03.vodafone.com (HELO mailout03.vodafone.com) (195.232.244.135) by server-14.tower-169.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP;  19 Jun 2015 11:27:38 -0000
Received: from mailint03.vodafone.com (mailint03.vodafone.com [195.232.244.200]) by mailout03.vodafone.com (Postfix) with ESMTP id 3mCdCZ3B7Zz17HLl for <tsvwg@ietf.org>; Fri, 19 Jun 2015 13:27:38 +0200 (CEST)
Received: from mailint03.vodafone.com (localhost [127.0.0.1]) by mailint03.vodafone.com (Postfix) with ESMTP id 3mCdCZ278gz16KBW for <tsvwg@ietf.org>; Fri, 19 Jun 2015 13:27:38 +0200 (CEST)
Received: from VOEXC06W.internal.vodafone.com (voexc06w.dc-ratingen.de [145.230.101.26]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailint03.vodafone.com (Postfix) with ESMTPS id 3mCdCZ24YHz16KyT for <tsvwg@ietf.org>; Fri, 19 Jun 2015 13:27:38 +0200 (CEST)
Received: from VOEXC26W.internal.vodafone.com (145.230.103.198) by VOEXC06W.internal.vodafone.com (145.230.101.26) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 19 Jun 2015 13:27:37 +0200
Received: from VOEXM17W.internal.vodafone.com ([169.254.1.186]) by voexc26w ([145.230.103.198]) with mapi id 14.03.0224.002; Fri, 19 Jun 2015 13:27:37 +0200
From: "Smith, Kevin, (R&D) Vodafone Group" <Kevin.Smith@vodafone.com>
To: "tsvwg IETF list (tsvwg@ietf.org)" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] FW: [saag] Request for review: new version 'Network Management of Encrypted Traffic'
Thread-Index: AdCqgs9ypfQ47Qx/TPSpgd7v63O9mg==
Date: Fri, 19 Jun 2015 11:27:36 +0000
Message-ID: <A4BAAB326B17CE40B45830B745F70F108E06FF45@VOEXM17W.internal.vodafone.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/J_8U02_7fQys7WczELTRZ5c3AqE>
Subject: [tsvwg] FW: [saag] Request for review: new version 'Network Management of Encrypted Traffic'
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, 19 Jun 2015 11:27:42 -0000

Hi,=20
I've just posted this to SAAG, any comments from the transport group member=
s would be kindly appreciated.
Many thanks
Kevin

-----Original Message-----
From: Smith, Kevin, (R&D) Vodafone Group=20
Sent: 19 June 2015 12:25
To: saag@ietf.org
Subject: [saag] Request for review: new version 'Network Management of Encr=
ypted Traffic'

Hi all,

Please may I ask for review of the updated version of 'Network Management o=
f Encrypted Traffic' [1]  - thanks for the previous feedback. Issues can be=
 raised on this thread or via [2].

[1] http://tools.ietf.org/html/draft-smith-encrypted-traffic-management-02=
=20
[2] https://github.com/Kevsy/encrypted-traffic-management/issues=20

All best,
Kevin


From nobody Thu Jun 25 11:02:07 2015
Return-Path: <wwwrun@rfc-editor.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 5DFB31A9067 for <tsvwg@ietfa.amsl.com>; Thu, 25 Jun 2015 11:02:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level: 
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 VjY0wM3mjLNc for <tsvwg@ietfa.amsl.com>; Thu, 25 Jun 2015 11:02:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id E942B1A906F for <tsvwg@ietf.org>; Thu, 25 Jun 2015 11:02:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 42C03180207; Thu, 25 Jun 2015 10:59:10 -0700 (PDT)
To: randall@lakerest.net, spencerdawkins.ietf@gmail.com, mls.ietf@gmail.com, gorry@erg.abdn.ac.uk, david.black@emc.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150625175910.42C03180207@rfc-editor.org>
Date: Thu, 25 Jun 2015 10:59:10 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/4hYY7hxpLM3a8vfWmHl-HQYGwr8>
Cc: rfc-editor@rfc-editor.org, j.pourtet@gmail.com, tsvwg@ietf.org
Subject: [tsvwg] [Technical Errata Reported] RFC4960 (4400)
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Jun 2015 18:02:06 -0000

The following errata report has been submitted for RFC4960,
"Stream Control Transmission Protocol".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4960&eid=4400

--------------------------------------
Type: Technical
Reported by: Julien Pourtet <j.pourtet@gmail.com>

Section: 5.1.6.

Original Text
-------------
                                    /-- INIT ACK [Veri Tag=Tag_A,
                                   /             I-Tag=Tag_Z,
    (Cancel T1-init timer) <------/              Cookie_Z, & other info]
                                         (destroy temp TCB)
    COOKIE ECHO [Cookie_Z] ------\
    (Start T1-init timer)         \
    (Enter COOKIE-ECHOED state)    \---> (build TCB enter ESTABLISHED
                                          state)
                                   /---- COOKIE-ACK
                                  /
    (Cancel T1-init timer, <-----/

Corrected Text
--------------
                                    /-- INIT ACK [Veri Tag=Tag_A,
                                   /             I-Tag=Tag_Z,
    (Cancel T1-init timer) <------/              Cookie_Z, & other info]
                                         (destroy temp TCB)
    COOKIE ECHO [Cookie_Z] ------\
    (Start T1-cookie timer)       \
    (Enter COOKIE-ECHOED state)    \---> (build TCB enter ESTABLISHED
                                          state)
                                   /---- COOKIE-ACK
                                  /
    (Cancel T1-cookie timer, <---/

Notes
-----
Upon reception of an INIT ACK Endpoint A should start the T1-cookie timer, not the T1-init timer. Reception of a COOKIE-ACK cancels The T1-cookie timer, not the T1-init timer.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC4960 (draft-ietf-tsvwg-2960bis-05)
--------------------------------------
Title               : Stream Control Transmission Protocol
Publication Date    : September 2007
Author(s)           : R. Stewart, Ed.
Category            : PROPOSED STANDARD
Source              : Transport Area Working Group
Area                : Transport
Stream              : IETF
Verifying Party     : IESG


From nobody Thu Jun 25 11:31:10 2015
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 AE6551A8785 for <tsvwg@ietfa.amsl.com>; Thu, 25 Jun 2015 11:31:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, 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 P9ItxQW3PxcU for <tsvwg@ietfa.amsl.com>; Thu, 25 Jun 2015 11:31:02 -0700 (PDT)
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 77B141A875D for <tsvwg@ietf.org>; Thu, 25 Jun 2015 11:31:02 -0700 (PDT)
Received: from [192.168.1.200] (p508F1827.dip0.t-ipconnect.de [80.143.24.39]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id BEB311C0B3E77; Thu, 25 Jun 2015 20:30:58 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <20150625175910.42C03180207@rfc-editor.org>
Date: Thu, 25 Jun 2015 20:30:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C43A74C1-E569-4306-B6E3-55C82B335096@lurchi.franken.de>
References: <20150625175910.42C03180207@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/c7UzPK6sho605LFV7xI-YtEVdFo>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg <tsvwg@ietf.org>, Martin Stiemerling <mls.ietf@gmail.com>, "Randall R. Stewart" <randall@lakerest.net>, j.pourtet@gmail.com
Subject: Re: [tsvwg] [Technical Errata Reported] RFC4960 (4400)
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Jun 2015 18:31:04 -0000

> On 25 Jun 2015, at 19:59, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC4960,
> "Stream Control Transmission Protocol".
>=20
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3D4960&eid=3D4400
>=20
> --------------------------------------
> Type: Technical
> Reported by: Julien Pourtet <j.pourtet@gmail.com>
>=20
> Section: 5.1.6.
>=20
> Original Text
> -------------
>                                    /-- INIT ACK [Veri Tag=3DTag_A,
>                                   /             I-Tag=3DTag_Z,
>    (Cancel T1-init timer) <------/              Cookie_Z, & other =
info]
>                                         (destroy temp TCB)
>    COOKIE ECHO [Cookie_Z] ------\
>    (Start T1-init timer)         \
>    (Enter COOKIE-ECHOED state)    \---> (build TCB enter ESTABLISHED
>                                          state)
>                                   /---- COOKIE-ACK
>                                  /
>    (Cancel T1-init timer, <-----/
>=20
> Corrected Text
> --------------
>                                    /-- INIT ACK [Veri Tag=3DTag_A,
>                                   /             I-Tag=3DTag_Z,
>    (Cancel T1-init timer) <------/              Cookie_Z, & other =
info]
>                                         (destroy temp TCB)
>    COOKIE ECHO [Cookie_Z] ------\
>    (Start T1-cookie timer)       \
>    (Enter COOKIE-ECHOED state)    \---> (build TCB enter ESTABLISHED
>                                          state)
>                                   /---- COOKIE-ACK
>                                  /
>    (Cancel T1-cookie timer, <---/
>=20
> Notes
> -----
> Upon reception of an INIT ACK Endpoint A should start the T1-cookie =
timer, not the T1-init timer. Reception of a COOKIE-ACK cancels The =
T1-cookie timer, not the T1-init timer.
Yes, that is a bug in the specification.=20

Best regards
Michael
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC4960 (draft-ietf-tsvwg-2960bis-05)
> --------------------------------------
> Title               : Stream Control Transmission Protocol
> Publication Date    : September 2007
> Author(s)           : R. Stewart, Ed.
> Category            : PROPOSED STANDARD
> Source              : Transport Area Working Group
> Area                : Transport
> Stream              : IETF
> Verifying Party     : IESG
>=20
>=20


From nobody Thu Jun 25 23:37:20 2015
Return-Path: <swmike@swm.pp.se>
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 4C2DD1B3401 for <tsvwg@ietfa.amsl.com>; Thu, 25 Jun 2015 23:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, 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 WHjbZGGURw2u for <tsvwg@ietfa.amsl.com>; Thu, 25 Jun 2015 23:37:17 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 531C51B3400 for <tsvwg@ietf.org>; Thu, 25 Jun 2015 23:37:17 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 2C0AEA1; Fri, 26 Jun 2015 08:37:15 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1435300635; bh=+DdOC2vXh8bU+D7/l6KnXb8SwFM5OPfzpOSiF52pgog=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=QV0Pryr1Ew66+4JBotif7Ea0OSnn0/T1T/CObchHrFvUhC7hBFZtfVxCtT/LxI1pC h7eRNOnv4ozHTzHdLbDkscdfb6PtfJgWLwOWJfUvkxigKjELI0xP7816zqr2PtyWrT APV3ZOqWQTVpvNgmK8q4ep3PNddqG41tyJnubHKo=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 22BD29F; Fri, 26 Jun 2015 08:37:15 +0200 (CEST)
Date: Fri, 26 Jun 2015 08:37:15 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: gorry@erg.abdn.ac.uk
In-Reply-To: <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk>
Message-ID: <alpine.DEB.2.02.1506260829330.9487@uplift.swm.pp.se>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se>  <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com> <5580C588.9070008@gmail.com> <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/b5Nceh5AzEl4eOBsQ_LTyq5wioE>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Jun 2015 06:37:19 -0000

On Wed, 17 Jun 2015, gorry@erg.abdn.ac.uk wrote:

> As co-chair: I think the short separate standards-track draft would then 
> be the appropriate thing to do. This could be done quickly ***IF*** we 
> get a firm consensus from the community to do this.

If you want to reach out to the "community", I would suggest to for 
instance reach out to the nanog (https://www.nanog.org/list) mailing list 
and ask for feedback there. You'd be more likely to find people who will 
actually implement this there, than on this mailing list. You'd get a much 
wider audience who will tell you if this is deployable in the real world 
with real world equipment and real world configuration, and asking real 
world operators if this is something they could imagine implementing.

Those are the people who will decide what DSCP bit bleaching is done at 
peering borders and customer connections for instance, which is key to 
getting this deployed.

It would also be interesting to hear from equipment vendors, especially 
ones that make BNGs, which kind of bleaching functionality is available in 
existing equipment. Is it possible to just bleach precedence bits on most 
platforms? I'd imagine it is, but it would be interesting to know.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Jun 26 00:22:53 2015
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 A6B3B1B34AD for <tsvwg@ietfa.amsl.com>; Fri, 26 Jun 2015 00:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.46
X-Spam-Level: 
X-Spam-Status: No, score=-2.46 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, 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 pXmiqP2hbGtP for <tsvwg@ietfa.amsl.com>; Fri, 26 Jun 2015 00:22:50 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C2B31B2FDD for <tsvwg@ietf.org>; Fri, 26 Jun 2015 00:22:48 -0700 (PDT)
Received: from q4de8psa169.blf.telekom.de ([10.151.13.200]) by tcmail21.telekom.de with ESMTP; 26 Jun 2015 09:22:34 +0200
X-IronPort-AV: E=Sophos;i="5.13,683,1427752800"; d="scan'208";a="857697602"
Received: from he113656.emea1.cds.t-internal.com ([10.134.99.16]) by q4de8psazkj.blf.telekom.de with ESMTP/TLS/AES128-SHA; 26 Jun 2015 09:22:32 +0200
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113656.emea1.cds.t-internal.com ([10.134.99.16]) with mapi; Fri, 26 Jun 2015 09:22:32 +0200
From: <Ruediger.Geib@telekom.de>
To: <swmike@swm.pp.se>
Date: Fri, 26 Jun 2015 09:22:31 +0200
Thread-Topic: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
Thread-Index: AdCv2pMMpF6TNAe0QlmDDy7p3AkmrwAAZ/Eg
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F505290F292B@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com> <5580C588.9070008@gmail.com> <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk> <alpine.DEB.2.02.1506260829330.9487@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1506260829330.9487@uplift.swm.pp.se>
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/bRpyFrXm89-s3ZJXqrSI75-NRKM>
Cc: gorry@erg.abdn.ac.uk, tsvwg@ietf.org
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Jun 2015 07:22:51 -0000

Hi Mikael,

I've asked my colleagues visiting RIPE and NANOG meetings for Diffserv Inte=
rconnection related contacts, but feedback was limited. I guess there's som=
e truth in what you say - developers and more so operational staff hardly p=
articipates in IETF work.

If you are aware of DiffServ Interconnection related agreements of NANOG pl=
ease let me know. I think there's nothing discussed by RIPE.

You wrote:

   It would also be interesting to hear from equipment vendors, especially=
=20
   ones that make BNGs, which kind of bleaching functionality is available=
=20
   in existing equipment. Is it possible to just bleach precedence bits=20
   on most platforms? I'd imagine it is, but it would be interesting to kno=
w.

Bleaching of "Ip precedence bits" is not within scope of Diffserv Intercon =
and it will stay out of scope (it is an informational draft and it cannot a=
nd is not supposed to change standards).

Carrier representatives interested in a standard allowing to remark, say, r=
anges of DSCPs (bleaching by precedence is bad wording) should collectively=
 draft a suitable document. I guess, if at all, this is only picked up by s=
tandardization if a significant number of provider representatives express =
interest. If you know some more provider representatives willing to co-auth=
or such a draft, please let me know.=20

I've had some text related to the issue in very early versions of the draft=
.=20

Regards,

Ruediger


From nobody Fri Jun 26 01:33:56 2015
Return-Path: <swmike@swm.pp.se>
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 076ED1A0115 for <tsvwg@ietfa.amsl.com>; Fri, 26 Jun 2015 01:33:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.361
X-Spam-Level: 
X-Spam-Status: No, score=-3.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, J_CHICKENPOX_21=0.6, 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 9JWyOkqCATXy for <tsvwg@ietfa.amsl.com>; Fri, 26 Jun 2015 01:33:52 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A17B1A010F for <tsvwg@ietf.org>; Fri, 26 Jun 2015 01:33:52 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 7386BA2; Fri, 26 Jun 2015 10:33:50 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1435307630; bh=B/xd4vTdCn9ykjXjUcYlB+7WGlKiil+bm5iLhOC8Mso=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=vgc0+3GZVtc/OWqn4KHymsVK9vYOZ02sUdbzNrcc90tKYshjJ8YUguCIEMO/b6VyV S05EZuaM/pJL6FIexoPCCnLoKKMq/h2Rgae2JL0bDTNRQ6LSO24uovv8aXRYhVWGni SivP9eNccl/FmPlOED7HQyM6AqU6e+ujhu5fCHK0=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 5E2BAA1; Fri, 26 Jun 2015 10:33:50 +0200 (CEST)
Date: Fri, 26 Jun 2015 10:33:50 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ruediger.Geib@telekom.de
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F505290F292B@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Message-ID: <alpine.DEB.2.02.1506261011340.9487@uplift.swm.pp.se>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se>  <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com> <5580C588.9070008@gmail.com> <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk> <alpine.DEB.2.02.1506260829330.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F292B@HE111643.EMEA1.CDS.T-INTERNAL.COM>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/VnGrGB2mWTCD3HTQq-xfN1zstvw>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Jun 2015 08:33:55 -0000

On Fri, 26 Jun 2015, Ruediger.Geib@telekom.de wrote:

> I've asked my colleagues visiting RIPE and NANOG meetings for Diffserv 
> Interconnection related contacts, but feedback was limited. I guess 
> there's some truth in what you say - developers and more so operational 
> staff hardly participates in IETF work.

I don't understand what "Diffserv Interconnection related contacts" would 
be. This would most likely be handled by peering managers and IP 
network architects that do the rest of the network design.

> If you are aware of DiffServ Interconnection related agreements of NANOG 
> please let me know. I think there's nothing discussed by RIPE.

In the operational community things are done largely by interpersonal 
connections and discussions on mailing lists that then create de-facto 
ways of doing things.

> Bleaching of "Ip precedence bits" is not within scope of Diffserv 
> Intercon and it will stay out of scope (it is an informational draft and 
> it cannot and is not supposed to change standards).

Right now most ISPs will bleach all 6 bits for Internet traffic. My 
proposal was to come up with a solution that allowed them to bleach the CS 
bits.

> Carrier representatives interested in a standard allowing to remark, 
> say, ranges of DSCPs (bleaching by precedence is bad wording) should 
> collectively draft a suitable document. I guess, if at all, this is only 
> picked up by standardization if a significant number of provider 
> representatives express interest. If you know some more provider 
> representatives willing to co-author such a draft, please let me know.

I have already suggested what I think would be achievable in real life. I 
am willing to bring this to nanog and ask for opinions from the 
operational community.

> I've had some text related to the issue in very early versions of the draft.

I propose that what I want to do isn't applicable to your draft, I just 
realised I had jumped into the discussion without reading it. I now have 
quickly scanned through it, and your text isn't applicable to Internet 
peering at all.

So what I want to achieve would need a new document. I have no idea how it 
applies to all the other documents out there because there are just too 
many for someone not focusing on this area, to overlook. I have been 
architecting Internet backbones for 15 years.

I would like to see a document that applies to Internet traffic only, 
scavenger class and BE only, that basically proposes to bleach CS bits and 
leave the rest of the bits intact, and then suggests how to configure 
queuing behavior for Internet access to take this into account. It should 
be an operational document which includes deployment cases and how to 
configure this using commonly used equipment.

I think the disconnect here is that in the IETF DSCP and the rest is 
considered transport, but by most operators, DSCP and queuing behaviour is 
done by IP engineers and IP architects. These people go to v6ops, 
potentially to 6man, routing protocol WG:s and similar IP control and 
forwarding groups, they don't really attend what IETF calls transport. I 
also get the feeling that people in here don't really attend NANOG or 
other places where the people who actually forward packets and configure 
queues attend. So we have two groups who never interact.

So there is really a need for TSV-OPS or something, that actually talks 
about how to implement what's in the DSCP related documents, and the IETF 
needs to somehow try to attract operational people in there. I have non 
idea how to achieve this.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Jun 26 03:18:55 2015
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 1D4931A8FD4 for <tsvwg@ietfa.amsl.com>; Fri, 26 Jun 2015 03:18:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.26
X-Spam-Level: 
X-Spam-Status: No, score=-3.26 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_MED=-2.3, 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 f5oau6iNi6j1 for <tsvwg@ietfa.amsl.com>; Fri, 26 Jun 2015 03:18:51 -0700 (PDT)
Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D08B1A8F50 for <tsvwg@ietf.org>; Fri, 26 Jun 2015 03:18:49 -0700 (PDT)
Received: from s4de8nsazdfe010.bmbg.telekom.de ([10.175.246.202]) by tcmail91.telekom.de with ESMTP; 26 Jun 2015 12:18:47 +0200
X-IronPort-AV: E=Sophos;i="5.13,683,1427752800"; d="scan'208";a="696811054"
Received: from he113470.emea1.cds.t-internal.com ([10.134.93.128]) by q4de8nsa015.bmbg.telekom.de with ESMTP/TLS/AES128-SHA; 26 Jun 2015 12:18:45 +0200
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113470.emea1.cds.t-internal.com ([::1]) with mapi; Fri, 26 Jun 2015 12:18:45 +0200
From: <Ruediger.Geib@telekom.de>
To: <swmike@swm.pp.se>
Date: Fri, 26 Jun 2015 12:18:45 +0200
Thread-Topic: AW: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
Thread-Index: AdCv6yWbnB1sMTprSzmYbzvqETs6mAABg7tw
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F505290F2B1C@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com> <5580C588.9070008@gmail.com> <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk> <alpine.DEB.2.02.1506260829330.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F292B@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1506261011340.9487@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1506261011340.9487@uplift.swm.pp.se>
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/gHeYTpZGFxKlQjBgrgxgqItFB70>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Jun 2015 10:18:54 -0000

Hi Mikael,

if you attend the Prague IETF, let's meet there and discuss ways forward.

I note that DiffServ-Intercon doesn't meet your operational requirements. I=
t is closer to reach mine (in Germany Ethernet and IP QoS interconnections =
are discussed with the regulator).
=20
Starting new work with use cases certainly is a good idea. I share some of =
your interests, but I also note that we have differing views on others. So =
I'm happy to provide support where our interests overlap. That's bleaching =
and rewriting of DSCP ranges, both at interconnection.

IETF welcomes provider input also in TSVWG. I'm happy for every provider re=
presentative joining me in discussing operation related DiffServ issues in =
TSVWG. Once we are too many, a TSV OPS related WG may be helpful.

Regards,

Ruediger


-----Urspr=FCngliche Nachricht-----
Von: Mikael Abrahamsson [mailto:swmike@swm.pp.se]=20
Gesendet: Freitag, 26. Juni 2015 10:34
An: Geib, R=FCdiger
Cc: tsvwg@ietf.org
Betreff: Re: AW: [tsvwg] draft diffserv-intercon: Handling of a scavenger c=
lass / CS1

On Fri, 26 Jun 2015, Ruediger.Geib@telekom.de wrote:

> I've asked my colleagues visiting RIPE and NANOG meetings for Diffserv=20
> Interconnection related contacts, but feedback was limited. I guess=20
> there's some truth in what you say - developers and more so=20
> operational staff hardly participates in IETF work.

I don't understand what "Diffserv Interconnection related contacts" would b=
e. This would most likely be handled by peering managers and IP network arc=
hitects that do the rest of the network design.

> If you are aware of DiffServ Interconnection related agreements of=20
> NANOG please let me know. I think there's nothing discussed by RIPE.

In the operational community things are done largely by interpersonal conne=
ctions and discussions on mailing lists that then create de-facto ways of d=
oing things.

> Bleaching of "Ip precedence bits" is not within scope of Diffserv=20
> Intercon and it will stay out of scope (it is an informational draft=20
> and it cannot and is not supposed to change standards).

Right now most ISPs will bleach all 6 bits for Internet traffic. My proposa=
l was to come up with a solution that allowed them to bleach the CS bits.

> Carrier representatives interested in a standard allowing to remark,=20
> say, ranges of DSCPs (bleaching by precedence is bad wording) should=20
> collectively draft a suitable document. I guess, if at all, this is=20
> only picked up by standardization if a significant number of provider=20
> representatives express interest. If you know some more provider=20
> representatives willing to co-author such a draft, please let me know.

I have already suggested what I think would be achievable in real life. I a=
m willing to bring this to nanog and ask for opinions from the operational =
community.

> I've had some text related to the issue in very early versions of the dra=
ft.

I propose that what I want to do isn't applicable to your draft, I just rea=
lised I had jumped into the discussion without reading it. I now have quick=
ly scanned through it, and your text isn't applicable to Internet peering a=
t all.

So what I want to achieve would need a new document. I have no idea how it =
applies to all the other documents out there because there are just too man=
y for someone not focusing on this area, to overlook. I have been architect=
ing Internet backbones for 15 years.

I would like to see a document that applies to Internet traffic only, scave=
nger class and BE only, that basically proposes to bleach CS bits and leave=
 the rest of the bits intact, and then suggests how to configure queuing be=
havior for Internet access to take this into account. It should be an opera=
tional document which includes deployment cases and how to configure this u=
sing commonly used equipment.

I think the disconnect here is that in the IETF DSCP and the rest is consid=
ered transport, but by most operators, DSCP and queuing behaviour is done b=
y IP engineers and IP architects. These people go to v6ops, potentially to =
6man, routing protocol WG:s and similar IP control and forwarding groups, t=
hey don't really attend what IETF calls transport. I also get the feeling t=
hat people in here don't really attend NANOG or other places where the peop=
le who actually forward packets and configure queues attend. So we have two=
 groups who never interact.

So there is really a need for TSV-OPS or something, that actually talks abo=
ut how to implement what's in the DSCP related documents, and the IETF need=
s to somehow try to attract operational people in there. I have non idea ho=
w to achieve this.

--=20
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Jun 26 05:45:29 2015
Return-Path: <swmike@swm.pp.se>
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 661501B2D3E for <tsvwg@ietfa.amsl.com>; Fri, 26 Jun 2015 05:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.961
X-Spam-Level: 
X-Spam-Status: No, score=-3.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, 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 HgtM_88lwLDV for <tsvwg@ietfa.amsl.com>; Fri, 26 Jun 2015 05:45:25 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51EC11B2D32 for <tsvwg@ietf.org>; Fri, 26 Jun 2015 05:45:25 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 2F973A1; Fri, 26 Jun 2015 14:45:23 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1435322723; bh=KWxXERzAZOesDIiFe+pLg/Qk+ntD1lqotCPGlOqJE6E=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=p1yFTVbS7irFo/+3Umrtc1ENMHF5M4kO56arHWJ4BAhCcSk1wXLjhpKeuFHkHWcqP Qv9SlAE+1QKxqhKNILw8GcO87nwVMgO/Mndaj9j9YQ08206z7lCUjonjYzVzNyxCv3 EWck5l5Q4mH69N5g7acITt0nPfyBCbarAojP42nI=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 26CB49F; Fri, 26 Jun 2015 14:45:23 +0200 (CEST)
Date: Fri, 26 Jun 2015 14:45:23 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ruediger.Geib@telekom.de
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F505290F2B1C@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Message-ID: <alpine.DEB.2.02.1506261438350.9487@uplift.swm.pp.se>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se>  <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com> <5580C588.9070008@gmail.com> <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk> <alpine.DEB.2.02.1506260829330.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F292B@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1506261011340.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F2B1C@HE111643.EMEA1.CDS.T-INTERNAL.COM>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/ZJr8_G4_JCuzsbarPMaxlxhvlUY>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Jun 2015 12:45:27 -0000

On Fri, 26 Jun 2015, Ruediger.Geib@telekom.de wrote:

> IETF welcomes provider input also in TSVWG. I'm happy for every provider 
> representative joining me in discussing operation related DiffServ 
> issues in TSVWG. Once we are too many, a TSV OPS related WG may be 
> helpful.

Most operators have no idea this work is going on here. You can say you're 
welcoming participation all you want, but if you actually want 
participation then you have to reach out.

It also has to be relevant and understandable. Your document, whilst I'm 
sure it's perfectly correct and makes a lot of sense to matter experts, is 
TL;DR; (Too Long, Didn't Read), for most people who just want their 
networks to work and customers not complain.

So yes, let's meet up in Prague and discuss this. I think what we need is 
a different document than diffserv-intercon because most in there just 
isn't applicable to Internet peering interconnects.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Sun Jun 28 01:08:08 2015
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 02CB41ACDCC for <tsvwg@ietfa.amsl.com>; Sun, 28 Jun 2015 01:08:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.511
X-Spam-Level: 
X-Spam-Status: No, score=-0.511 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 s-AcM3KGxLjF for <tsvwg@ietfa.amsl.com>; Sun, 28 Jun 2015 01:08:05 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id D26701ACDCB for <tsvwg@ietf.org>; Sun, 28 Jun 2015 01:08:04 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 2AEF61B001CD for <tsvwg@ietf.org>; Sun, 28 Jun 2015 09:07:30 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Sun, 28 Jun 2015 09:06:51 +0100
Message-ID: <6bc4276dab1d3c104d858112f017dad1.squirrel@erg.abdn.ac.uk>
Date: Sun, 28 Jun 2015 09:06:51 +0100
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
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/T9byzgyzgRLKPfiqanZluZv3Lmk>
Subject: [tsvwg] ** DRAFT Agenda being built for Prague **
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: <https://mailarchive.ietf.org/arch/browse/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, 28 Jun 2015 08:08:07 -0000

Here is the current Agenda for TSVWG - if you are on the list and have not
confirmed to the Chairs - please send an email. We will then allocate
timing to presentation slots.

Best wishes,

Gorry & David
(TSV WG Co-Chairs)

    ---------------------------------------------
    tsvwg Session 1 (2:00:00)
    Thursday, Afternoon Session II 1520-1720
    Room Name: Karlin I/II size: 125
    ---------------------------------------------
    tsvwg Session 2 (2:00:00)
    Wednesday, Afternoon Session III 1740-1940
    Room Name: Congress Hall III size: 225
    ---------------------------------------------

TSVWG Meeting at IETF 93, Prague, CZ
WG Chairs: Gorry Fairhurst and David Black
Note Taker 1: <??>
Note Taker 2: <??>
Jabber Scribe: <??>

1. Agenda

2. Status/updates (WG Chairs) - 15 minutes

   http://www.arkko.com/tools/allstats/jamespolk.html

   Additional Policies for the PR Extension of SCTP (RFC 7496)

   Recommendations for Transport Port Number Uses(RFC-Ed)
   draft-ietf-tsvwg-port-use
.
   DTLS Encapsulation of SCTP Packets (RFC-Ed)
   draft-ietf-tsvwg-sctp-dtls-encaps

   NAT Behavioral Requirements Updates
   draft-ietf-tsvwg-behave-requirements-update

   RSVP Application-ID Profiles for Voice and Video Streams
   draft-ietf-tsvwg-rsvp-app-id-vv-profiles

   Charter & Milestones - 5 minutes

3. WG Coordination (Activities related to TSV in other areas) - 5 minutes

   Chairs - Encapsulation Considerations
   draft-rtg-dt-encap

   Chairs - The Benefits to Applications of using ECN (past WGLC)
   draft-ietf-aqm-ecn-benefits

   <??? - other drafts that should be mentioned?>

4. WG Drafts (Protocols)

4.1 G Fairhurst / L Eggert - UDP Usage Guidelines - 10 minutes
    draft-ietf-tsvwg-rfc5405bis

4.2 Lucy Yong or Tom Herbert - Generic UDP Encapsulation for IP Tunneling
    draft-ietf-tsvwg-gre-in-udp-encap

4.3 Gorry Fairhurst - Network Transport Circuit Breakers
    draft-ietf-tsvwg-circuit-breaker

5. WG Drafts (SCTP)

5.1 Michael Tuexen - Stream Schedulers and and User Message Interleaving
for SCTP
    draft-ietf-tsvwg-sctp-ndata

5.2 Karen Neilson - Quick Failover Algorithm in SCTP - 10 minutes
    draft-ietf-tsvwg-sctp-failover

5.3 Michael Tuexen - SCTP Network Address Translation Support
    draft-ietf-tsvwg-natsupp

6. WG Drafts (DiffServ/Network)

6.1 ??? - Guidelines for adding Congestion Notification to Protocols that
Encapsulate IP
    draft-ietf-tsvwg-ecn-encap-guidelines

6.2 ??? - DSCP and other packet markings for RTCWeb QoS
    draft-ietf-tsvwg-rtcweb-qos
6.3 Ruediger Geib - DiffServ interconnection classes and practice
    draft-ietf-tsvwg-diffserv-intercon

6.4 David Black - Discussion of Scavenger Class support in DS
    Individual: <draft TBD>

Note 1: Please contact the WG Chairs with agenda items. New work to be
brought
to this group requires prior discussion on the tsvwg mailing list.

Note 2: ??? - If you would like to confirm the agenda slot, please send a
note with the
presenter name to the WG Chairs (tsvwg-chairs@ietf.org)

Draft 28 June 2015.


From nobody Mon Jun 29 00:01:14 2015
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 8DBE61A1BA7 for <tsvwg@ietfa.amsl.com>; Mon, 29 Jun 2015 00:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.56
X-Spam-Level: 
X-Spam-Status: No, score=-0.56 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_MED=-2.3, 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 PupKQywrdtib for <tsvwg@ietfa.amsl.com>; Mon, 29 Jun 2015 00:01:10 -0700 (PDT)
Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 132611A1BA4 for <tsvwg@ietf.org>; Mon, 29 Jun 2015 00:01:08 -0700 (PDT)
Received: from q4de8psa169.blf.telekom.de ([10.151.13.200]) by tcmail41.telekom.de with ESMTP; 29 Jun 2015 09:00:50 +0200
X-IronPort-AV: E=Sophos;i="5.13,697,1427752800"; d="scan'208";a="858998915"
Received: from he111628.emea1.cds.t-internal.com ([10.134.93.20]) by q4de8psazkj.blf.telekom.de with ESMTP/TLS/AES128-SHA; 29 Jun 2015 09:00:49 +0200
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE111628.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 29 Jun 2015 09:00:47 +0200
From: <Ruediger.Geib@telekom.de>
To: <swmike@swm.pp.se>
Date: Mon, 29 Jun 2015 09:00:46 +0200
Thread-Topic: AW: AW: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
Thread-Index: AdCwDfgcRQ6eO6ebQPuExtK73jgRIwCI2i6A
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F505290F2DFB@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com> <5580C588.9070008@gmail.com> <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk> <alpine.DEB.2.02.1506260829330.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F292B@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1506261011340.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F2B1C@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1506261438350.9487@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1506261438350.9487@uplift.swm.pp.se>
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/7nMd9BSY_7BGOa6ZZjqq3-AwfRU>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Jun 2015 07:01:12 -0000

Mikael,

it took a while to make progress on DiffServ Intercon. You say=20

     So yes, let's meet up in Prague and discuss this. I think what we=20
     need is a different document than diffserv-intercon because most=20
     in there just isn't applicable to Internet peering interconnects.

Do you say:

- there's no need for interconnection based on QoS classes - just forward=20
  limited DSCP information to an access and that's fine? Or is your=20
  statement no DSCP or IP-Precedence based QoS differentiation in the IP=20
  backbone (and only default forwarding there), limit QoS to the access?
- you'd like to support QoS interconnection, but set up individual DSCP=20
  based PHB mapping tables per interconnection? In that case, no new=20
  standard is required.=20
- You just need bleaching to Default - that's a separate issue which has be=
en=20
  removed from DiffServ-Intercon as part of WG consent. It is a pre-requisi=
te=20
  of DiffServ-Intercon, but not an issue handled by it.
- You look for a rewrite of ranges of DSCPs ("treatment of IP precedence")
  - this is out of scope, as it is a standards track issue touching the
  fundaments of DiffServ. DiffServ Intercon also works well if IP-Precedenc=
e=20
  rewrite occurs.=20

General claims like "isn't applicable to Internet-peering" aren't helpful, =
if you don't tell us what is applicable to internet peering. DiffServ-Inter=
con has been applicable to the QoS interconnection agreements I've been inv=
olved in so far.=20

If you are able to provide something which isn't TL;DR, I'd appreciate your=
 submission before cut-off. I'd also appreciate your indication what needs =
to be removed from draft diffserv-intercon to increase op-folk attention.

I repeat that I've talked with my RIPE/NANOG colleagues to get feedback - t=
hey came back only with one or two names with whom to discuss QoS interconn=
ection. And I never got any useful response (positive or negative) from tho=
se.

Regards,

Ruediger


From nobody Mon Jun 29 00:37:53 2015
Return-Path: <swmike@swm.pp.se>
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 383EB1A6FBC for <tsvwg@ietfa.amsl.com>; Mon, 29 Jun 2015 00:37:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.039
X-Spam-Level: *
X-Spam-Status: No, score=1.039 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, 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 AaYUUBE7PUwt for <tsvwg@ietfa.amsl.com>; Mon, 29 Jun 2015 00:37:50 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E4A91A6F7B for <tsvwg@ietf.org>; Mon, 29 Jun 2015 00:37:50 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id AEEE7A1; Mon, 29 Jun 2015 09:37:47 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1435563467; bh=DPwRHT1rz7eIr0wGYKdP8WZfOowiC1v4YoT24qBh02c=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=yFjBAWS8arRVudbdCJgpJwd7d3iafgUVmEUDYn/871GX9LA6FSSTlf/sWkjz8Hqdf /j4JZM/F2bhO9QVeOl7spKHQI3M1i14eTvbaYOmTcyIWL8DcfMEI8qfuCnFqdx9oLh ZQNfFY8WX5RUqEKZjgOUee04K/ifwKHcfgP5PsTw=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A562A9F; Mon, 29 Jun 2015 09:37:47 +0200 (CEST)
Date: Mon, 29 Jun 2015 09:37:47 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ruediger.Geib@telekom.de
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F505290F2DFB@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Message-ID: <alpine.DEB.2.02.1506290904460.9487@uplift.swm.pp.se>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se>  <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com> <5580C588.9070008@gmail.com> <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk> <alpine.DEB.2.02.1506260829330.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F292B@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1506261011340.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F2B1C@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1506261438350.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F2DFB@HE111643.EMEA1.CDS.T-INTERNAL.COM>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/5bsUxyeS43xfTwQLQJxM3FLwRSQ>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Jun 2015 07:37:52 -0000

On Mon, 29 Jun 2015, Ruediger.Geib@telekom.de wrote:

> I repeat that I've talked with my RIPE/NANOG colleagues to get feedback 
> - they came back only with one or two names with whom to discuss QoS 
> interconnection. And I never got any useful response (positive or 
> negative) from those.

This is the problem, that's not how to do this, the way to do this is to 
announce an idea on the nanog mailing list and see who might be 
interested.

As far as I read your document, it has nothing in it about how to 
incrementally get an Internet-wide scavenger class operationally deployed 
over time. To me it reads more like a document for business VPN 
Carriers-Carrier services style interconnect/interworking. It has no 
operational advice at all in it on how to deal with DDoS, how to configure 
access equipment, how to set up queuing strategies on different kinds of 
equipment, listing what equipment might do what, etc.

I suggested how to actually make this incrementally and widely deployable 
across the world, and that is to aim for a 000xxx style scavenger class. 
This seems to not work for some reason that is unclear to me, your 
document doesn't seem to be operational at all, it doesn't propose 
something that is operationally deployable on the wider Internet, so 
that's why I think we would need another document for this purpose. If 
that is not a goal we can agree on, then there is no need to write one.

So just to sum up: I'm sure your document is fine for what it intends to 
do, it just doesn't answer any of the concerns an IP network 
engineer/architect might have about implementing this on an Internet 
peering link where there is little or no control over what traffic will 
pass or what this traffic might do to the rest of their network. It 
suggests a way to do something with no operational analysis or risk 
mitigation at all.

The first thing that will pop into any good IP architects head nowadays 
will be "oh, what happens to my network when I get 200 gigabits/s of 64 
byte packets marked EF from that 5 million strong DDoS-drone network all 
across the world, aimed for my customer base?"

The answer to that is "I'll bleach DSCP it because that's the only way to 
handle it". So in order to get a scavenger class actually deployable, you 
have to come up with something that means they can relax the bleaching a 
little bit by some operators, but their infrastructure would still treat 
the traffic the same. You also have to take into account that a lot of 
core IP network equipment can't do DSCP mapping very well. This kind of 
functionality makes equipment more expensive and thus less likely to exist 
widely.

-- 
Mikael Abrahamsson email: swmike@swm.pp.se


From nobody Mon Jun 29 01:51:05 2015
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 E06AA1A219E for <tsvwg@ietfa.amsl.com>; Mon, 29 Jun 2015 01:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level: 
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, 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 jsXtg1d1ATeg for <tsvwg@ietfa.amsl.com>; Mon, 29 Jun 2015 01:51:02 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B17E51A219B for <tsvwg@ietf.org>; Mon, 29 Jun 2015 01:51:00 -0700 (PDT)
Received: from s4de8nsazdfe010.bmbg.telekom.de ([10.175.246.202]) by tcmail21.telekom.de with ESMTP; 29 Jun 2015 10:50:57 +0200
X-IronPort-AV: E=Sophos;i="5.13,698,1427752800"; d="scan'208";a="697747861"
Received: from he111630.emea1.cds.t-internal.com ([10.134.93.22]) by q4de8nsa015.bmbg.telekom.de with ESMTP/TLS/AES128-SHA; 29 Jun 2015 10:50:58 +0200
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE111630.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 29 Jun 2015 10:50:57 +0200
From: <Ruediger.Geib@telekom.de>
To: <swmike@swm.pp.se>
Date: Mon, 29 Jun 2015 10:50:55 +0200
Thread-Topic: AW: AW: AW: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
Thread-Index: AdCyPoEUrjx3ZGJcQjej9EIeXsyzaQABei/w
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F505290F2F2B@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50513613DD9@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1505291422130.9487@uplift.swm.pp.se> <5568CF68.9020406@gmail.com> <alpine.DEB.2.02.1505292256170.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505136148FE@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CE03DB3D7B45C245BCA0D243277949360B3798B8@MX104CL02.corp.emc.com> <5580C588.9070008@gmail.com> <538a059f43eb8a2c2bd42453de21d6f2.squirrel@erg.abdn.ac.uk> <alpine.DEB.2.02.1506260829330.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F292B@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1506261011340.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F2B1C@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1506261438350.9487@uplift.swm.pp.se> <CA7A7C64CC4ADB458B74477EA99DF6F505290F2DFB@HE111643.EMEA1.CDS.T-INTERNAL.COM> <alpine.DEB.2.02.1506290904460.9487@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1506290904460.9487@uplift.swm.pp.se>
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/UoF9d5w9QI2LyB6ZLEYSlDTSVBE>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft diffserv-intercon: Handling of a scavenger class / CS1
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Jun 2015 08:51:05 -0000

Hi Mikael,

ok, understood, I'm relaxed.

The relation of Diffserv intercon to scavenger is

- if there is a scavenger class, how should Diffserv intercon handle it=20
  (will add text about a 000 xx0 DSCP)? Otherwise Diffserv Intercon=20
  says, bleaching may occur for any unexpected DSCP.

- work on a scavenger class standard needs to be done in a=20
  separate draft. That's WG consensus and Gorry Fairhurst said during=20
  the last meeting:
  "Scavenger support document been discussed before, if there is=20
  renewed interest, then we should take it up again.=20
  As an individual contributor, I would be interested.=20
  If you are also interested in this topic, please talk to the=20
  WG chairs."

- operational issues may be relevant for a bleaching discussion.=20
  A bleaching standard is out of scope of Diffserv Intercon (thats=20
  WG consensus). I think to recall interest in work on bleaching=20
  by others too.

Then I'm happy to meet you in Prague.=20

Regards,

Ruediger=20

-----Urspr=FCngliche Nachricht-----
Von: Mikael Abrahamsson [mailto:swmike@swm.pp.se]=20
Gesendet: Montag, 29. Juni 2015 09:38
An: Geib, R=FCdiger
Cc: tsvwg@ietf.org
Betreff: Re: AW: AW: AW: [tsvwg] draft diffserv-intercon: Handling of a sca=
venger class / CS1

On Mon, 29 Jun 2015, Ruediger.Geib@telekom.de wrote:

> I repeat that I've talked with my RIPE/NANOG colleagues to get=20
> feedback
> - they came back only with one or two names with whom to discuss QoS=20
> interconnection. And I never got any useful response (positive or
> negative) from those.

This is the problem, that's not how to do this, the way to do this is to an=
nounce an idea on the nanog mailing list and see who might be interested.

As far as I read your document, it has nothing in it about how to increment=
ally get an Internet-wide scavenger class operationally deployed over time.=
 To me it reads more like a document for business VPN Carriers-Carrier serv=
ices style interconnect/interworking. It has no operational advice at all i=
n it on how to deal with DDoS, how to configure access equipment, how to se=
t up queuing strategies on different kinds of equipment, listing what equip=
ment might do what, etc.

I suggested how to actually make this incrementally and widely deployable a=
cross the world, and that is to aim for a 000xxx style scavenger class.=20
This seems to not work for some reason that is unclear to me, your document=
 doesn't seem to be operational at all, it doesn't propose something that i=
s operationally deployable on the wider Internet, so that's why I think we =
would need another document for this purpose. If that is not a goal we can =
agree on, then there is no need to write one.

So just to sum up: I'm sure your document is fine for what it intends to do=
, it just doesn't answer any of the concerns an IP network engineer/archite=
ct might have about implementing this on an Internet peering link where the=
re is little or no control over what traffic will pass or what this traffic=
 might do to the rest of their network. It suggests a way to do something w=
ith no operational analysis or risk mitigation at all.

The first thing that will pop into any good IP architects head nowadays wil=
l be "oh, what happens to my network when I get 200 gigabits/s of 64 byte p=
ackets marked EF from that 5 million strong DDoS-drone network all across t=
he world, aimed for my customer base?"

The answer to that is "I'll bleach DSCP it because that's the only way to h=
andle it". So in order to get a scavenger class actually deployable, you ha=
ve to come up with something that means they can relax the bleaching a litt=
le bit by some operators, but their infrastructure would still treat the tr=
affic the same. You also have to take into account that a lot of core IP ne=
twork equipment can't do DSCP mapping very well. This kind of functionality=
 makes equipment more expensive and thus less likely to exist widely.

--
Mikael Abrahamsson email: swmike@swm.pp.se


From nobody Tue Jun 30 08:50:18 2015
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 5C1051ACD41 for <tsvwg@ietfa.amsl.com>; Tue, 30 Jun 2015 08:50:06 -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 3FlQvuH7QXSB for <tsvwg@ietfa.amsl.com>; Tue, 30 Jun 2015 08:50:04 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id C80C21ACD30 for <tsvwg@ietf.org>; Tue, 30 Jun 2015 08:49:49 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 03E6E1B001CC; Tue, 30 Jun 2015 16:49:47 +0100 (BST)
Received: from 213.174.117.243 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Tue, 30 Jun 2015 16:48:39 +0100
Message-ID: <749b3ac50afdc81996ec4a0351cde1b0.squirrel@erg.abdn.ac.uk>
Date: Tue, 30 Jun 2015 16:48:39 +0100
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
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/-GCkBsRzEsNWuYsxvmPr0GArKbY>
Subject: [tsvwg] New draft: draft-khademi-alternativebackoff-ecn-00.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: <https://mailarchive.ietf.org/arch/browse/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, 30 Jun 2015 15:50:06 -0000

A group of us have been working together to get better than current ECN
using a simple sender side change (this is not intended to compete with
work on Accurate ECN) and only the existing router ECN marking.

Please see the draft below, and do send comments and questions to this
list. In particular we'd like to know if others have interest in this work
being presented to the TSV WG.

Gorry
(just an individual author)

> Begin forwarded message:
>
> Resent-From: <michawe@ifi.uio.no>
> From: <internet-drafts@ietf.org>
> To: Michael Welzl <michawe@ifi.uio.no>, Grenville Armitage
<garmitage@swin.edu.au>, Michael Welzl <michawe@ifi.uio.no>, Gorry
Fairhurst <gorry@erg.abdn.ac.uk>, Naeem Khademi <naeemk@ifi.uio.no>,
Godred Fairhurst <gorry@erg.abdn.ac.uk>, Grenville Armitage
<garmitage@swin.edu.au>, "Naeem Khademi" <naeemk@ifi.uio.no>
> Subject: New Version Notification for
draft-khademi-alternativebackoff-ecn-00.txt
> Date: 30. juni 2015 kl. 16.08.27 CEST
>
>
> A new version of I-D, draft-khademi-alternativebackoff-ecn-00.txt
> has been successfully submitted by Michael Welzl and posted to the
> IETF repository.
>
> Name:		draft-khademi-alternativebackoff-ecn
> Revision:	00
> Title:		TCP Alternative Backoff with ECN (ABE)
> Document date:	2015-06-30
> Group:		Individual Submission
> Pages:		6
> URL:           
https://www.ietf.org/internet-drafts/draft-khademi-alternativebackoff-ecn-00.txt
> Status:        
https://datatracker.ietf.org/doc/draft-khademi-alternativebackoff-ecn/
> Htmlized:      
https://tools.ietf.org/html/draft-khademi-alternativebackoff-ecn-00
>
>
> Abstract:
>   This memo updates the TCP sender-side reaction to a congestion
>   notification received via Explicit Congestion Notification (ECN).
>   The updated method is less conservative than the TCP reaction in
>   response to loss.  The intention is to achieve good throughput when
>   the queue at the bottleneck is smaller than the bandwidth-delay-
>   product of the connection.  This is more likely when an Active Queue
>   Management (AQM) mechanism has ECN-marked a packet than when a packet
>   was lost.  Future versions of this document will discuss SCTP as well
>   as other transports using ECN.
>
>
>
>
> 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 Tue Jun 30 16:42:23 2015
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 9307A1B2A8E for <tsvwg@ietfa.amsl.com>; Tue, 30 Jun 2015 16:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, 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 8wLXtLyRNRH7 for <tsvwg@ietfa.amsl.com>; Tue, 30 Jun 2015 16:42:21 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0A1D1B2A7F for <tsvwg@ietf.org>; Tue, 30 Jun 2015 16:42:20 -0700 (PDT)
Received: from maildlpprd02.lss.emc.com (maildlpprd02.lss.emc.com [10.253.24.34]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t5UNgJQj018686 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <tsvwg@ietf.org>; Tue, 30 Jun 2015 19:42:19 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com t5UNgJQj018686
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1435707739; bh=E6tv0IjFPTmElJdP2GSwH9UWe5g=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=Z9N2xCSrCySeDavvYmCe2lRKSrH3R8sAqo/SSQODcN+4uOkejx1cYFMx2eR1LUMmF UrQkJ3ipW2lnGRNPDJoLLU9fglZ7ErxyUWvju8yPGxp4Hxo8V076H5Qv1BuuzyRX50 BvoLTL8PTEbYXA6T9c9JvbascsSOtQatKYCu3Yas=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com t5UNgJQj018686
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd02.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Tue, 30 Jun 2015 19:41:58 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t5UNgCsP006957 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Tue, 30 Jun 2015 19:42:13 -0400
Received: from MXHUB103.corp.emc.com (10.253.50.16) by mxhub24.corp.emc.com (128.222.70.136) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 30 Jun 2015 19:42:12 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.107]) by MXHUB103.corp.emc.com ([::1]) with mapi id 14.03.0224.002; Tue, 30 Jun 2015 19:42:11 -0400
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: draft-ietf-tsvwg-rsvp-app-id-vv-profiles - interest?
Thread-Index: AdCzjl0VJLQc+n4DTDCxAbRTaV1xuA==
Date: Tue, 30 Jun 2015 23:42:10 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493613FF0AD7@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.81]
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: DLM_1, public
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/qHQykx85WuHMD3DwePY2NL5KWqE>
Subject: [tsvwg] draft-ietf-tsvwg-rsvp-app-id-vv-profiles - interest?
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Jun 2015 23:42:22 -0000

The tsvwg and mmusic WGs have two related drafts that have expired.  Noting=
 a dearth of community engagement, the authors have raised the question as =
to whether interest still exists in these drafts and whether the work shoul=
d continue.  The drafts are:

draft-ietf-tsvwg-rsvp-app-id-vv-profiles
draft-ietf-mmusic-traffic-class-for-sdp
=20
The intent of these drafts is to allow for fine-grained classification of t=
raffic flows by introducing a "traffic class label" such as "conversational=
.video.immersive" or "broadcast.video.surveillance" that can be signaled to=
 various entities in the network.  Within SDP, the labels can be used by ce=
rtain network elements like SBCs to assist in prioritization of media flows=
 or DSCP marking at network edges, identification of various types of flows=
 active in the network, to give instructions to endpoints on how to signal =
traffic classification to network elements (e.g., via RSVP), or to instruct=
 endpoints as to which DSCP value to apply to traffic flows (assuming a loc=
al mapping is defined), etc.  The companion work in tsvwg is targeted at us=
e of the traffic class label concept within RSVP, allowing a network router=
 or switch to better determine how to handle RSVP requests, to map a given =
traffic classes label to a specific DSCP value (facilitates proper remarkin=
g of flows), etc.

If there's interest in pursuing this work, please post to the list or let t=
he WG chairs know.  Absent interest, draft-ietf-tsvwg-rsvp-app-id-vv-profil=
es will likely be removed from the tsvwg WG's list of planned work sometime=
 after the Prague meeting.

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 Tue Jun 30 23:56:48 2015
Return-Path: <lars@netapp.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 B23231AD2F2 for <tsvwg@ietfa.amsl.com>; Tue, 30 Jun 2015 23:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level: 
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 0oF998898Ib2 for <tsvwg@ietfa.amsl.com>; Tue, 30 Jun 2015 23:56:45 -0700 (PDT)
Received: from mx143.netapp.com (mx143.netapp.com [216.240.21.24]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBA0C1AD2EC for <tsvwg@ietf.org>; Tue, 30 Jun 2015 23:56:44 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.15,383,1432623600"; d="scan'208";a="51794197"
Received: from hioexcmbx03-prd.hq.netapp.com ([10.122.105.36]) by mx143-out.netapp.com with ESMTP; 30 Jun 2015 23:56:35 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx03-prd.hq.netapp.com (10.122.105.36) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Tue, 30 Jun 2015 23:56:29 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::6843:58b6:e8e4:4968%21]) with mapi id 15.00.1076.000; Tue, 30 Jun 2015 23:56:29 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Gorry Fairhust <gorry@erg.abdn.ac.uk>
Thread-Topic: [tsvwg] New draft: draft-khademi-alternativebackoff-ecn-00.txt
Thread-Index: AQHQs0x0NCHm6Ar2AkmlvNLGYr+13J3GpNoA
Date: Wed, 1 Jul 2015 06:56:29 +0000
Message-ID: <A64EDE1E-C5B7-44B5-9368-62386C0D2D2A@netapp.com>
References: <749b3ac50afdc81996ec4a0351cde1b0.squirrel@erg.abdn.ac.uk>
In-Reply-To: <749b3ac50afdc81996ec4a0351cde1b0.squirrel@erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.2102)
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.122.56.79]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4DBA3451B206CB44B9678D15BC32CD0F@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/dkruafks9VWftQOT9y3oE05Y83I>
Cc: "draft-bensley-tcpm-dctcp@tools.ietf.org" <draft-bensley-tcpm-dctcp@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] New draft: draft-khademi-alternativebackoff-ecn-00.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: <https://mailarchive.ietf.org/arch/browse/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, 01 Jul 2015 06:56:46 -0000

How does this interact with DCTCP?

On 2015-6-30, at 17:48, gorry@erg.abdn.ac.uk wrote:
>=20
> A group of us have been working together to get better than current ECN
> using a simple sender side change (this is not intended to compete with
> work on Accurate ECN) and only the existing router ECN marking.
>=20
> Please see the draft below, and do send comments and questions to this
> list. In particular we'd like to know if others have interest in this wor=
k
> being presented to the TSV WG.
>=20
> Gorry
> (just an individual author)
>=20
>> Begin forwarded message:
>>=20
>> Resent-From: <michawe@ifi.uio.no>
>> From: <internet-drafts@ietf.org>
>> To: Michael Welzl <michawe@ifi.uio.no>, Grenville Armitage
> <garmitage@swin.edu.au>, Michael Welzl <michawe@ifi.uio.no>, Gorry
> Fairhurst <gorry@erg.abdn.ac.uk>, Naeem Khademi <naeemk@ifi.uio.no>,
> Godred Fairhurst <gorry@erg.abdn.ac.uk>, Grenville Armitage
> <garmitage@swin.edu.au>, "Naeem Khademi" <naeemk@ifi.uio.no>
>> Subject: New Version Notification for
> draft-khademi-alternativebackoff-ecn-00.txt
>> Date: 30. juni 2015 kl. 16.08.27 CEST
>>=20
>>=20
>> A new version of I-D, draft-khademi-alternativebackoff-ecn-00.txt
>> has been successfully submitted by Michael Welzl and posted to the
>> IETF repository.
>>=20
>> Name:		draft-khademi-alternativebackoff-ecn
>> Revision:	00
>> Title:		TCP Alternative Backoff with ECN (ABE)
>> Document date:	2015-06-30
>> Group:		Individual Submission
>> Pages:		6
>> URL:          =20
> https://www.ietf.org/internet-drafts/draft-khademi-alternativebackoff-ecn=
-00.txt
>> Status:       =20
> https://datatracker.ietf.org/doc/draft-khademi-alternativebackoff-ecn/
>> Htmlized:     =20
> https://tools.ietf.org/html/draft-khademi-alternativebackoff-ecn-00
>>=20
>>=20
>> Abstract:
>>  This memo updates the TCP sender-side reaction to a congestion
>>  notification received via Explicit Congestion Notification (ECN).
>>  The updated method is less conservative than the TCP reaction in
>>  response to loss.  The intention is to achieve good throughput when
>>  the queue at the bottleneck is smaller than the bandwidth-delay-
>>  product of the connection.  This is more likely when an Active Queue
>>  Management (AQM) mechanism has ECN-marked a packet than when a packet
>>  was lost.  Future versions of this document will discuss SCTP as well
>>  as other transports using ECN.
>>=20
>>=20
>>=20
>>=20
>> 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.
>>=20
>> The IETF Secretariat
>>=20
>=20

