
From brian.e.carpenter@gmail.com  Fri Mar  1 00:40:06 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0915F21F857B for <tsvwg@ietfa.amsl.com>; Fri,  1 Mar 2013 00:40:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.504
X-Spam-Level: 
X-Spam-Status: No, score=-99.504 tagged_above=-999 required=5 tests=[AWL=-0.583, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4IMizzt3eNg6 for <tsvwg@ietfa.amsl.com>; Fri,  1 Mar 2013 00:40:05 -0800 (PST)
Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5699421F8556 for <tsvwg@ietf.org>; Fri,  1 Mar 2013 00:40:05 -0800 (PST)
Received: by mail-we0-f182.google.com with SMTP id t57so2327024wey.27 for <tsvwg@ietf.org>; Fri, 01 Mar 2013 00:40:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=25PSeWFw+i70X5vL4ca24fvbeBIwWm72S4xEx66SnHE=; b=MUqzBdoqJDLyAmvupysCU5WDOsO8Wji7CGnP3+LlJO0vJkIrt1IYutFPe5bWR7BwqB SwkAt761sF7jSFPQm3M82dr9zK2n9LrwYO+5vy4lZbh7Abg9AivUhSDSfza5NDYvbfp/ CUbptl6JVknJ6rvnOwIl0cEcgBRa4uo+vawqSrnp05r1FCM66cibHn7qCiC2R0qXSlVy CTuVMq6uMrnpSFvNaGo3ztI1VWIUvX+K9nfNMPL1I0IuMrE6hRy8ocWVGspCTO51LoR8 gbtLAeFCJndgsxI8q27YrO7Dv1zwN+4XMsSDWx8l8Ho4xzBs3t7zH7sCZBVyB6F8CdFk J7qA==
X-Received: by 10.194.83.105 with SMTP id p9mr15883784wjy.56.1362127204487; Fri, 01 Mar 2013 00:40:04 -0800 (PST)
Received: from [192.168.1.65] (host-2-101-189-92.as13285.net. [2.101.189.92]) by mx.google.com with ESMTPS id bs6sm20436340wib.4.2013.03.01.00.40.02 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Mar 2013 00:40:03 -0800 (PST)
Message-ID: <51306970.2080705@gmail.com>
Date: Fri, 01 Mar 2013 08:40:16 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7128F9F7414@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7128F9F7414@MX15A.corp.emc.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] David Black's comments on draft-geib-tsvwg-diffserv-intercon-
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2013 08:40:06 -0000

On 28/02/2013 23:09, Black, David wrote:
...
> The introduction should explain more about copying of the "IP Precedence Bits"
> to the MPLS TC or Ethernet P-Bits - the crucial thing that needs to be stated
> is that the bits involved are the first 3 bits in the DSCP, and the values
> for the recommended DSCPs for AF and EF were chosen in part based on this
> consideration, so that EF has a higher priority than AF (and most other
> traffic) when this is done.  This is described in Section 5, but should
> also be explained in the introduction. 

It should also, IMHO, be made clear that this is a bit of a hack,
originally intended for the benefit of legacy IPv4 routers that were
not diffserv-aware. The correct technique is a mapping table from
DSCP to 3-bit value, not a dumb mask.

   Brian

From Ruediger.Geib@telekom.de  Fri Mar  1 04:11:18 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1272721F89B2 for <tsvwg@ietfa.amsl.com>; Fri,  1 Mar 2013 04:11:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.749
X-Spam-Level: 
X-Spam-Status: No, score=-0.749 tagged_above=-999 required=5 tests=[AWL=-2.500, BAYES_00=-2.599, GB_SUMOF=5, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPOWJJOZ5Avl for <tsvwg@ietfa.amsl.com>; Fri,  1 Mar 2013 04:11:17 -0800 (PST)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id A057421F87C5 for <tsvwg@ietf.org>; Fri,  1 Mar 2013 04:11:15 -0800 (PST)
Received: from he111629.emea1.cds.t-internal.com ([10.134.93.21]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 01 Mar 2013 13:10:35 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE111629.emea1.cds.t-internal.com ([::1]) with mapi; Fri, 1 Mar 2013 13:10:35 +0100
From: <Ruediger.Geib@telekom.de>
To: <david.black@emc.com>
Date: Fri, 1 Mar 2013 13:10:33 +0100
Thread-Topic: [tsvwg] David Black's comments on draft-geib-tsvwg-diffserv-intercon-
Thread-Index: Ac4WCJ1gu0g8jPPJSvG1oWa000MbIgAYT8aw
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A301D05@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE7128F9F7414@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7128F9F7414@MX15A.corp.emc.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] David Black's comments on	draft-geib-tsvwg-diffserv-intercon-
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2013 12:11:18 -0000

Hello David,

thanks for your comments. Your statements and my replies are marked as foll=
ows below:

[DB] David Black
[RG] R=FCdiger Geib

Regards,

R=FCdiger

########################

[DB] These comments are as an individual - <WG co-chair hat off>

[DB] In general, this is a valuable contribution, including the specific
     proposal of the 4 diffserv interconnect classes.  It may be a good
     idea to add a mapping from the current RFC 4594 classes into
     these classes as a complement to the current PHB-oriented material.

[RG] I agree. We should clarify the role of RFC5127.

[DB] Abstract and Introduction: A possible tsvwg direction forward is to
     revise RFC 5127 to focus on network internals and produce a separate
     RFC for interconnection of network edges - that separation is
     consistent with the discussion in Section 3 of this draft about
     mapping between internal and interconnection schemes.

     That distinction between schemes is crucial, IMHO - it's in the
     second paragraph of this draft's introduction, but could use some
     more emphasis. OTOH, I'd remove the text that focuses this draft
     on revising RFC 5127, as that may not be the most effective path
     forward, although it'd probably be ok to retain some of the language
     in the introduction about concepts in this draft being relevant to
     a revision of RFC 5127.

[RG] Yes, we should clarify how to make progress on DiffServ-Intercon and
RFC 5127. I think, both are linked. If both progress apart, some text
should explain why they are kept apart. I'd also expect that
DiffServ-Intercon would make faster progress if kept separate from RFC5127.

[DB] The introduction should explain more about copying of the "IP Preceden=
ce
     Bits" to the MPLS TC or Ethernet P-Bits - the crucial thing that
     needs to be stated is that the bits involved are the first 3 bits
     in the DSCP, and the values for the recommended DSCPs for AF and EF
     were chosen in part based on this consideration, so that EF has a
     higher priority than AF (and most other traffic) when this is done.
     This is described in Section 5, but should also be explained in the
     introduction.

[RG] You are correct, the first three bits of the DSCP are important, not
the IP Precedence class concept. Any other term is allright with me. I'll
change that for version -03.


[DB] The last paragraph on p.3 indicates that internal PHBs and codepoints
     may be added later - I don't think that would be a good idea.  Rather,
     it'd be better (IMHO) to focus this draft on the interconnect problem
     to keep it cleanly separated from the RFC 4594 update discussion that
     also affects RFC 5127. That paragraph could also use some minor
     rephrasing to avoid any implication that this draft has priority on
     use of MPLS TC space - talking about other uses as peer users of that
     space would be better than the current "leave some MPLS TC codespace"
     language.

[RG] The internal classes don't need to be part of DiffServ-Intercon. Some
guidance on mapping of these internal classes may be given and I wouldn't
exclude using CS6 for EBGP. Some routers may not be able to use anything
else but CS6 for internal traffic. But that's rather an infomative addition
than my core interest.
This draft should not say that more MPLS TCs are required than those
four indicated. There are no other Intercon-classes I think about. I'll
try to change text (but I'm no native spreaker).

{DB] It's recently been discovered that draft-ietf-idr-sla-exchange-00.txt
     is related to this work, so that draft should be mentioned.  The
     idr-sla-exchange draft is rather descriptive, in contrast to this
     diffserv interconnect draft being prescriptive.

[RG] I guess a reference is possible, but I will have to check how far
that goes. I have to discuss that internally, as one of the IDR
old hands is from the company I work for.

[DB] The middle bullet in the list at the end of section 3 isn't
     quite right. There are only 8 codepoints available for DSCP encoding
     in MPLS and Ethernet, but some PHBs (e.g., AF) can consume more than
     one codepoint.  The last bullet at the end of section 3 is unclear
     on whether this is about DSCPs, MPLS (and Ethernet) codepoints,
     or both.

[RG] Let's disuss that: An offered class AF3 consumes one MPLS TC
(e.g. 3). However PHBs AF31 and AF32 if offered could consume 2 MPLS
TCs, say 3 and 2. And if ECN is to be supported for a class AF4, than
an additional MPLS TC would be required: in the example AF4 corresponds
to MPLS TC 4 not-CM and MPLS TC 7 may indicate AF4 CM. 8 is the sum of
DSCP and ECN.
The last section refers to both, DSCP and MPLS TC, I will clarify.

[DB] The first 3 paragraphs of section 4 feel like they belong in a
     related work section, possibly an appendix, which would also be
     a good place for a longer discussion of Y.1566, which is the basis
     for a lot of this material.

[RG] Can be moved. Maintaining the information is important, but not
making it part of the proposed solution. I'd like to add interworking
guidance.

[DB] I'm not sure I understand the point of Section 6, and would
     suggest removing it.

[RG] Let me think about that. I've used wrong terminology (forwarding
and AQM is meant where I speak of conditioning - sorry, very sloppy
of me). I want to get rid of discussions why a class "Streaming Audio"
is mapped into a class "Multimedia" in my professional life. I'd rather
like to have a discussion  about class properties and SLA expectations.
As "avoid giving application names to DiffServ classes" is standard
guidance given by networking engineers, I'm not the only one suffering.
That's motivates this "QoS standardisation pitfalls" section.
It may be made informational and I try to reword. But it should be kept.


[DB] I would also combine sections 5 and 7 into a single section.

{RG] Will do so in version -03.


From sebastien.jobert@orange.com  Fri Mar  1 04:42:07 2013
Return-Path: <sebastien.jobert@orange.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E85BB21F8ADB for <tsvwg@ietfa.amsl.com>; Fri,  1 Mar 2013 04:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rlvBcjtr2xUK for <tsvwg@ietfa.amsl.com>; Fri,  1 Mar 2013 04:42:07 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 8DDE621F8B1D for <tsvwg@ietf.org>; Fri,  1 Mar 2013 04:42:06 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 3A3B4324558; Fri,  1 Mar 2013 13:42:05 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 1F7764C06D; Fri,  1 Mar 2013 13:42:05 +0100 (CET)
Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Fri, 1 Mar 2013 13:42:04 +0100
From: <sebastien.jobert@orange.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
Thread-Topic: New version notification draft-geib-tsvwg-diffserv-intercon-02.txt
Thread-Index: Ac4TSjIrWVcoB5h5Q2+YBmDr3UIOBgACJ1JwAJhuw0AAA3+sUAAmxJ1w
Date: Fri, 1 Mar 2013 12:42:03 +0000
Message-ID: <5512_1362141725_5130A21D_5512_302_1_7F67B91079F7C74F9DAB55FC7872661E0B0A17@PEXCVZYM12.corporate.adroot.infra.ftgroup>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50167B9AF69@HE111643.EMEA1.CDS.T-INTERNAL.COM> <526_1362057197_512F57EC_526_12045_1_7F67B91079F7C74F9DAB55FC7872661E0B0400@PEXCVZYM12.corporate.adroot.infra.ftgroup> <CA7A7C64CC4ADB458B74477EA99DF6F5016A301943@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A301943@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.19.124517
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] New version notification	draft-geib-tsvwg-diffserv-intercon-02.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2013 12:42:08 -0000

Thanks R=FCdiger for your feedback.

A few additional points below based on your answer.
The other points are clear for me now.


[RG] ITU class critcal (network management) is mentioned in the DiffServ-In=
tercon introduction:... An example for an internal PHB may be CS6...
I'm happy to expand on that, given there's support.

[SJ] I am not sure that such class would necessarily be open to interconnec=
tion. My main suggestion was not necessarily to add this class, but rather =
to understand why the two documents (ITU Y.1566 and this draft) were slight=
ly different. Now it is clear, you clarified that the purpose is to have ev=
erything aligned.


[RG] Good point, I may be unclear here. I'd expect the classes to be suppor=
ted. Class
definitions should stay qualitative. Class properties should be standardise=
d. The PHBs
should be maintained in the sense that if received with different codepoint=
s at
interconnection, they should leave with different codepoints on interconnec=
tion. So
treating different PHBs of one class only as one class is allright.
The minimum expectation then is support of a class a specified, if the Inte=
rcon class
and codepoint scheme is used. I don't think there should be an obligation t=
o support
all four classes that's a SHOULD at best. I guess the draft needs to say th=
at.

[SJ] I agree that class definition must remain qualitative. However, it is =
not fully clear to me what you mean when you say that "the class properties=
 should be standardized". Personally, as I mentioned, I believe that it wil=
l be extremely difficult (not to say impossible) to agree on a common behav=
ior, since various network operators have in general different configuratio=
ns/policies. SLA expectations should not be part of this document IMHO, sin=
ce it is a topic to be discussed between operators, on a case by case basis=
 and depending on the context. Could you clarify your view on this point? F=
or instance, do you expect that if an operator implements one of the class =
defined, then this operator must implement exactly the PHB mentioned in the=
 draft in all the network nodes? Is there freedom left to the operator? Is =
there any plan to include aspects related to SLA in this draft?


Thanks.

BR,

S=E9bastien

-----Message d'origine-----
De=A0: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]=20
Envoy=E9=A0: jeudi 28 f=E9vrier 2013 16:47
=C0=A0: JOBERT Sebastien OLNC/OLN
Cc=A0: tsvwg@ietf.org
Objet=A0: RE: New version notification draft-geib-tsvwg-diffserv-intercon-0=
2.txt

Hello Sebastien,

thanks for your comments. Your statements and my replies are marked as foll=
ows below:

[SJ] Sebastien Jobert
[RG] R=FCdiger Geib

Regards,

R=FCdiger

----------

     [SJ] Page 6, you mention 4 classes (Class Priority, Bulk inelastic, As=
sured, Default)
     with a reference to Y.1566. However, in Y.1566, the 4 classes correspo=
nding to
     "Ordinary Packet Service QoS Classes" are not the same (e.g. Critical =
/ network management
     class is missing in your IETF draft), and it seems that you actually m=
ixed classes
     mentioned as "auxiliary Packet Service QoS Classes" in Y.1566 (e.g. Bu=
lk inelastic
     belongs to this second set in Y.1566). Is there a reason for this? Sho=
uld the two
     documents be aligned?

[RG] DiffServ-Intercon and Y.1566 should be aligned (and I'd add GSMA IR.34=
 and MEF 23.1).
ITU reached agreement on those classes all carriers support ("ordinary") an=
d some which
see some support ("auxiliary"). ITU worked with full consensus here, not wi=
th rough
consensus. That's why I included class Bulk Inealstic in the IETF work more=
 prominently
(but look for section 6 of Y.1566, it is proposed there too). ITU class cri=
tcal (network management)
is mentioned in the DiffServ-Intercon introduction:...An example for an int=
ernal PHB may be CS6...
I'm happy to expand on that, given there's support.

     [SJ] Page 7, you say that: "At interconnection points, the following P=
HBs should be
     accepted between interconnected parties:" Does it imply that it is exp=
ected that all
     the operators implement exactly these PHBs in their network in each no=
de? It seems
     quite difficult for me to mandate that all the networks behave the sam=
e way, since
     various network operators have in general different configurations/pol=
icies. I thought
     that the original proposal was simply to define a set of codepoints fo=
r interconnection
     points, but leave the actual network behavior as operator-specific (wh=
ich is quite
     reasonable). Did I misunderstand something?

[RG] Good point, I may be unclear here. I'd expect the classes to be suppor=
ted. Class
definitions should stay qualitative. Class properties should be standardise=
d. The PHBs
should be maintained in the sense that if received with different codepoint=
s at
interconnection, they should leave with different codepoints on interconnec=
tion. So
treating different PHBs of one class only as one class is allright.
The minimum expectation then is support of a class a specified, if the Inte=
rcon class
and codepoint scheme is used. I don't think there should be an obligation t=
o support
all four classes that's a SHOULD at best. I guess the draft needs to say th=
at.


     [SJ] You mention the term "conditioning" at several places in your dra=
ft; could
     you define precisely what is meant by this? For instance, is it referr=
ing to
     the properties of one particular class of service? Else?

[RG] Good point and I obviously need to expand terminology. By conditioning=
 I meant
scheduling & Active Queue Management (if any). And here "conditioning" does=
n't apply
 - that has been a late change and an ill formulated one. Sorry for causing
confusion.
In fact, what's needed is something "QoS forwarding". I'm open for better s=
uggestions.


     [SJ] About MPLS TC or Ethernet P-Bits and IP precedence, I'll tend to =
think that
     referencing the old IP precedence mechanism may not be the most effect=
ive way to
     explain what is suggested (and done in practice) - you might perhaps s=
imply
     mention that the first 3 bits of the DSCP are used, it might be cleare=
r. I
     would personally suggest not talking about IP precedence at all.

[RG] Good idea. If the WG reaches conensus that the first 3 bits of the DSC=
Ps are used
to the purpose I specify (and in fact: specification follows implementation=
 here)
I'm happy to rewrite the draft without refering to IP-precedence. I'll add =
that to the
presentation.

     [SJ] Finally, I wonder if a possible revision of RFC5127 might include=
 most of
     the aspects discussed in this draft. Indeed, the classes (treatment ag=
gregates)
     described in RFC5127 should ideally be aligned with this draft. Also, =
current
     RFC5127 contains a section 5 called "Treatment Aggregates and Inter-Pr=
ovider
     Relationships". This could potentially be a place where to put some of=
 the
     considerations on interconnection points.

[RG] Basically you are right. But to me RFC5127 requires a rewrite also wit=
hout the
contents of DiffServ-Intercon. I'd be very unhappy if consensus was reached=
 on
DiffServ-Intercon but the all is delayed because there's no consensus
on a RFC5127 rewrite. I'm open for a discussion however.






___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From svshah@cisco.com  Fri Mar  1 09:10:27 2013
Return-Path: <svshah@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4757221F8E67; Fri,  1 Mar 2013 09:10:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uwQEB9MGH8Rj; Fri,  1 Mar 2013 09:10:26 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id D046921F8B96; Fri,  1 Mar 2013 09:10:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11233; q=dns/txt; s=iport; t=1362157801; x=1363367401; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=qL2HwGxrYjOZZC/eRpNVrFreDEXuqSJuImXSW+QuRoE=; b=SWDOz8ywI1y9uUCogKn8YksScYZOo+dq2ydTTUiECKIM7eBAtp8buFGz 4QnkRd9tNPQjy785uYcbmC+Ob5r8ads1TrkzmiTktuBkUMpVh5+SRJQ7g +CfMK4Ih1s6h9W/saOilH+WI9KIzch1SwXuemXXi4jIJLSX3ht8wY+mzd U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAKffMFGtJV2c/2dsb2JhbABBA8I7fhZzgh8BAQEDATotCwcFBwYBCBEEAQEBChQJKBEUCQgCBA4FCId5AwkGDLdSDYk9BIxFgRGBFiEFCwcGC4JOYQOUZo0whRiDCIFpPg
X-IronPort-AV: E=Sophos;i="4.84,762,1355097600"; d="scan'208";a="182721728"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP; 01 Mar 2013 17:09:59 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r21H9xNl014336 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 1 Mar 2013 17:09:59 GMT
Received: from xmb-aln-x10.cisco.com ([169.254.5.82]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 11:09:59 -0600
From: "Shitanshu Shah (svshah)" <svshah@cisco.com>
To: "Black, David" <david.black@emc.com>
Thread-Topic: I-D Action: draft-ietf-idr-sla-exchange-00.txt
Thread-Index: AQHOFQxM0cBFOjlbZk+SD9PaSGdNOZiOQWGAgAGuRKCAAQPsAA==
Date: Fri, 1 Mar 2013 17:09:58 +0000
Message-ID: <F5C7FB9548FA6A4B8538AFEF6199B0ED151CB750@xmb-aln-x10.cisco.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7128F9F7443@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.1.130117
x-originating-ip: [10.21.86.81]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8A4CF12916048445BF336164A46EF274@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "idr@ietf.org" <idr@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-ietf-idr-sla-exchange-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2013 17:10:27 -0000

Hi David,

Please find response inline ##svshah

On 2/28/13 6:03 PM, "Black, David" <david.black@emc.com> wrote:

>(+tsvwg list)
>
>For context this is about the relationship of
>draft-ietf-idr-sla-exchange-00
>and draft-geib-tsvwg-diffserv-intercon-02.  Both are currently on the
>tsvwg
>WG agenda for Monday afternoon in Orlando (idr conflicts w/tsvarea on Wed,
>so the idr session won't work well for looking at both drafts).  The
>purpose
>of this note is to start some discussion in preparation for that session.
>
>This message is sent as an individual with <tsvwg WG co-chair hat OFF>.
>
>The drafts appear to be aimed at different, but overlapping use cases -
>the idr-sla-exchange draft appears to be primarily concerned with
>provider-customer relationships and purchased destination (AS) specific
>service (e.g., see Section 7).  The diffserv-intercon draft is primarily
>concerned with interconnection of carrier networks - while that's
>primarily
>a provider-provider case that appears to be of less interest to the
>idr-sla-exchange draft, both the provider-customer and purchased service
>(e.g., in the form of transit) cases may occur in provider-provider
>relationships.


##svshah, While provider-customer relationships and purchased destination
service has been primary motivation for the idr-sla-exchange, the proposal
is generic enough to support any AS to any AS including (not limited to),

- provider-provider
- Site-Site with one Customer's own multi-site network


>
>As already noted in the thread, the drafts support rather different SLA
>frameworks among networks:
>
>- idr-sla-exchange is descriptive and broad - it anticipates a plethora

##svshah, well plethora may be too extreme. The intention is not to exclude
any parameter that limits describing SLA.

The key is to be able to describe SLA through in band signaling without
requiring administrators have multi-level manual interaction to get SLA
of interest.


>	of possible multi-class SLA specifications that may need to be
>	described based on specific contracts with customers and other
>	network operators.  It includes bandwidth thresholds and remarking
>	instructions for a variety of marking mechanisms (e.g., diffserv,=09
>	Ethernet priority).
>- diffserv-intercon prescribes a single multi-class SLA specification
>	and a single set of diffserv PHBs (which have preferred DSCPs)
>	intended for widespread use by a single carrier.

##svshah, one of the key value adds from diffserv-intercon is standardizing
preferred inter-connection DSCPs. I personally think that is useful.

To define QoS SLA, though I think we need more than just a definition of
PHBs.
The intention of idr-sla-exchange draft is not to standardize DSCP and PHBs
(which should come from Diffserv standards outside the context of
sla-exchange
draft) but the intention is to convey SLA parameters, in-band, based on
those
standards.

Exception - In non-diffserv domains, SLA exchange may be based on other
types
of standards (e.g. MPLS, Ethernet .1q).. Or in cases like Site-Site (within
one Customer's domain), the class definition may be more granular than just
a code-point.


>
>Based on the above, the drafts could well be complementary, although more
>discussion of the relationship among them seems like a good idea in
>Orlando.
>
>In addition, I concur with Brian's conclusion on the idr-sla-exchange
>draft:
>
>> >> I think this draft needs to be discussed in TSVWG before it goes
>> >> much further. A consistent model for QoS metric signaling is needed
>> >> before we standardize a mapping onto IDR.
>
>In particular the various rates in that idr-sla-exchange draft appear to
>be
>inventing a new rate-based QoS specification framework, and the draft
>isn't
>particularly precise job of specifying it (as Brian's comments point out).
>
>This sort of work is not new to IETF, e.g., see the FLOWSPEC concept in
>RFC 2210, and the QSPEC concept in RFC 5975, which reuses the basic
>FLOWSPEC concept in a completely different protocol framework.

##svshah, Thanks for the reference. It is desirable to re-use any existing
specification that can meet the needs. I'll be happy to evaluate them. I'll
take a look at the specification.


Regards,
Shitanshu



>
>Thanks,
>--David
>
>> -----Original Message-----
>> From: Shitanshu Shah (svshah) [mailto:svshah@cisco.com]
>> Sent: Wednesday, February 27, 2013 7:00 PM
>> To: Black, David; Brian E Carpenter; draft-ietf-idr-sla-
>> exchange.all@tools.ietf.org
>> Cc: tsvwg-chairs@ietf.org; idr@ietf.org
>> Subject: Re: I-D Action: draft-ietf-idr-sla-exchange-00.txt
>> Importance: High
>>=20
>>=20
>> Hi David,
>>=20
>> In the context of this discussion, couple of important points of
>> motivation/consideration for sla-exchange draft
>>=20
>> - It is critical to have Diffserv support in SLA exchange. However, at
>>the
>> same time, it should not be limited to Diffserv only. The SLA exchange
>> language in draft-ietf-idr-sla-exchange-00.txt should work for other
>>types
>> of classification rules as well
>>=20
>> - Current stat of SLA exchange draft does not intend to standardize any
>> code-point or PHB. Rather defined language in the draft merely refers
>> standards defined outside the context. You have precisely captured in
>>your
>> comments that
>> SLA exchange draft is more descriptive in contrast to diffserv-intercon
>> which is more prescriptive
>>=20
>> An additional note, SLA exchange may be among nodes in the same
>> administrative domain or across. To support earlier use-case, draft
>>should
>> not have to mandate traffic class definition exchanged be based on
>> specific standards only.
>>=20
>>=20
>> Unfortunately, I will not be able to make it to IETF this time.
>>However, I
>> know Keyur (co-author) will be there and possibly other co-authors of
>>the
>> draft. It surely will be good to have a conversation among key people
>>and
>> as per outcome, we can have a further follow-up?
>>=20
>> Regards,
>> Shitanshu
>>=20
>>=20
>>=20
>> On 2/27/13 9:01 AM, "Black, David" <david.black@emc.com> wrote:
>>=20
>> >With my tsvwg WG co-chair hat on, I strongly concur with Brian that
>>this
>> >idr-sla-exchange draft needs to be discussed in the tsvwg WG.  In
>>Orlando,
>> >the tsvwg WG meeting expects to take up:
>> >
>> >  draft-geib-tsvwg-diffserv-intercon-02.txt
>> >  https://datatracker.ietf.org/doc/draft-geib-tsvwg-diffserv-intercon/
>> >
>> >which is considerably more prescriptive, in contrast to the
>> >idr-sla-exchange draft's descriptive approach.
>> >
>> >While that diffserv-intercon draft is not a WG draft, the tsvwg WG does
>> >intend to do work in this area, so some coordination to have a single
>> >overall approach seems advisable.  This does *not* imply a priori that
>> >we need to select one draft and drop the other, and I surely do not
>>want
>> >to work on BGP details in tsvwg ;-).
>> >
>> >Unfortunately the idr and tsvarea (Transport Area open meeting)
>>sessions
>> >conflict on Wednesday morning in Orlando - would it make sense to take
>>an
>> >initial look at this idr-sla-exchange draft during the Monday afternoon
>> >tsvwg session where there are conflicts with any routing WG meeting,
>>and
>> >perhaps have key people talk privately afterwards ?
>> >
>> >Thanks,
>> >--David (tsvwg WG co-chair)
>> >----------------------------------------------------
>> >David L. Black, Distinguished Engineer
>> >EMC Corporation, 176 South St., Hopkinton, MA  01748
>> >+1 (508) 293-7953             FAX: +1 (508) 293-7786
>> >david.black@emc.com        Mobile: +1 (978) 394-7754
>> >----------------------------------------------------
>> >
>> >> -----Original Message-----
>> >> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>> >> Sent: Monday, January 07, 2013 10:25 AM
>> >> To: draft-ietf-idr-sla-exchange.all@tools.ietf.org
>> >> Cc: tsvwg-chairs@ietf.org; idr@ietf.org
>> >> Subject: Re: I-D Action: draft-ietf-idr-sla-exchange-00.txt
>> >>
>> >> Hi,
>> >>
>> >> I don't understand which reference model for inter-domain SLAs
>> >> is being used here. There is an arbitrary list of element types
>> >> (IP_DSCP,  MPLS_TC,  802_1Q_COS, 802_1Q_DEI, PHB_ID) and then
>> >> an arbitrary list of some QoS metrics. Presumably some of those
>> >> metrics map on to some of the element types, but it isn't obvious
>> >> and I am certain there are gaps.
>> >>
>> >> I don't think you can answer this with the text at the end of
>> >> Section 6:
>> >>
>> >> >   There are well-defined recommendations that exist for traffic
>>class
>> >> >   mapping between two technologies.  Receiver MAY use those defined
>> >> >   recommendations for traffic class mapping or MAY define its own
>>as
>> >> >   per its network Traffic Class service definition to map to
>> >>advertised
>> >> >   Traffic Classes.  It is completely up to the receiver how to
>>define
>> >> >   such traffic class mapping.
>> >>
>> >> Firstly, if there are such recommendations, they should be given as
>> >> references. Secondly, why was the arbitrary set of QoS metrics chosen
>> >> and how do we know that they are necessary and sufficient? (For
>> >> example, I don't see any metric for drop rate, and for some traffic
>> >> classes that is an important metric.)
>> >>
>> >> I think this draft needs to be discussed in TSVWG before it goes
>> >> much further. A consistent model for QoS metric signalling is needed
>> >> before we standardise a mapping onto IDR.
>> >>
>> >> Nits
>> >> ----
>> >>
>> >> [RFC2474], [RFC2475]  and [RFC3140] are listed as references
>> >> (presumably for IP_DSCP and PHB_ID) but they are not cited in the
>> >> text. That will not get through the final ID-nits check.
>> >>
>> >> Also [RFC2475] is listed as a Normative reference, but it should
>> >> be Informative.
>> >>
>> >> Why is [RFC3552] listed as a reference?
>> >>
>> >> Why is *obsoleted* [RFC1771] listed as a reference?
>> >>
>> >> Why is [RFC4760] *not* listed, since this needs to work for IPv6?
>> >>
>> >> The English in this draft is quite painful in many places. Here
>> >> is one sentence chosen at random:
>> >>
>> >> >   Taking same voice service as an
>> >> >   example, given Provider already may provision definition of EF
>>code-
>> >> >   point for such, signaling this code-point traffic class from PE
>>to
>> >>CE
>> >> >   along with low latency service definition, omits administrator at
>> >>the
>> >> >   CE to worry about such translation.
>> >>
>> >> I'm guessing that this means:
>> >>
>> >>    Taking voice service as an
>> >>    example, a given provider might already provision the EF code-
>> >>    point for such traffic. Signaling the code-point for this traffic
>> >>class
>> >> from PE to CE,
>> >>    with a low latency service definition, would avoid manual
>>operations
>> >>by the
>> >> administrator at the
>> >>    CE.
>> >>
>> >> Please run ID-nits and fix the 2 errors and 11 warnings.
>> >>
>> >> Regards
>> >>    Brian Carpenter
>> >
>>=20
>


From jmpolk@cisco.com  Fri Mar  1 11:24:37 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40C5021E809E for <tsvwg@ietfa.amsl.com>; Fri,  1 Mar 2013 11:24:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.455
X-Spam-Level: 
X-Spam-Status: No, score=-110.455 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nI0feUF9jpIP for <tsvwg@ietfa.amsl.com>; Fri,  1 Mar 2013 11:24:36 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 9A78021E803F for <tsvwg@ietf.org>; Fri,  1 Mar 2013 11:24:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=738; q=dns/txt; s=iport; t=1362165876; x=1363375476; h=message-id:date:to:from:subject:cc:mime-version; bh=5nA4BwKCqPDIbm1W/Cre919Q4nkUmajkpwYxmw8/Udw=; b=YZaR5REw+mj1YUugPFH3ey5AE5UafTgq6p6xj0Ik+jg7aD7T8nN1Rqkk MXk3xUwm5Vo/7mp0pc54YKUHPerF4gMEVvIqkcsPo6xawZUgXrsrvnwCP gkPirhXJQ4TL1g8B5hNpnQsL3z9RLrkLVLl3830odNeAqMbS3DMESrAko 8=;
X-IronPort-AV: E=Sophos;i="4.84,762,1355097600"; d="scan'208";a="182757342"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-2.cisco.com with ESMTP; 01 Mar 2013 19:24:36 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) (authenticated bits=0) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r21JOaD0012741 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Mar 2013 19:24:36 GMT
Message-Id: <201303011924.r21JOaD0012741@rcdn-core-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 01 Mar 2013 13:24:31 -0600
To: tsvwg@ietf.org
From: James Polk <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Subject: [tsvwg] New versions of MULTI_TSPEC and MULTI_INSTANCE
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2013 19:24:37 -0000

TSVWG

(with my individual hat on)

I have updated one WG item (MULTI_TSPEC), as well as the individual 
item (MULTI_INSTANCE) that was proposed to replace. MULTI_TSPEC has 
been presented in several meetings, with MULTI_INSTANCE presented for 
the first time in Atlanta. I think the MULTI_INSTANCE draft is a 
better solution, but am willing to go with what the WG has previously 
had interest in making a WG item (MULTI_TSPEC). I do not want to keep 
both efforts churning, so I ask, which effort do we progress?

http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-intserv-multiple-tspec-02.txt
or
http://www.ietf.org/internet-drafts/draft-polk-rsvp-multi-instance-object-01.txt

(with my individual hat on)

James


From jmpolk@cisco.com  Fri Mar  1 11:33:13 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C21221E809E for <tsvwg@ietfa.amsl.com>; Fri,  1 Mar 2013 11:33:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.458
X-Spam-Level: 
X-Spam-Status: No, score=-110.458 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HwOhbgSKQ65O for <tsvwg@ietfa.amsl.com>; Fri,  1 Mar 2013 11:33:12 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9AE21E803F for <tsvwg@ietf.org>; Fri,  1 Mar 2013 11:33:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=627; q=dns/txt; s=iport; t=1362166392; x=1363375992; h=message-id:date:to:from:subject:mime-version; bh=RTbCmLgcZGW/rU9YjM8fiqvt3+7/Mw02y90IhpylKVY=; b=ZHo4nz/UZjBcDOwQA/4K3RWnb2KpEhzwoGy3CCLBPOmgOIUd/8xJKsgx 1mERypFNlYS6vU4Ttc+q+mc3Ubt8MbC4UoS/SAfh516Bd5Klc8JxdXcbO Pfqr828twlOVup/jRIsGU9JQau0tsxvjuyw0mzgr0YmmdOyvFUTZETJ9y Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj0FANUBMVGtJXG//2dsb2JhbABEhgi9MxZzgl4CViUVHwpgiAoMoDCgWI86gyoDiGueQ4Mn
X-IronPort-AV: E=Sophos;i="4.84,762,1355097600"; d="scan'208";a="182816591"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-3.cisco.com with ESMTP; 01 Mar 2013 19:33:12 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) (authenticated bits=0) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r21JXBIG019615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Fri, 1 Mar 2013 19:33:12 GMT
Message-Id: <201303011933.r21JXBIG019615@rcdn-core2-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 01 Mar 2013 13:33:11 -0600
To: tsvwg@ietf.org
From: James Polk <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Subject: [tsvwg] New rev of RSVP Application-ID Profiles
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2013 19:33:13 -0000

TSVWG

(with my individual hat on)

I've updated the RSVP Application-ID Profiles draft, with it becoming 
a WG item since Atlanta.
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-app-id-vv-profiles-00.txt 


I believe this effort has reached the point of

- it's had the mix of profiles included,

and, barring any review finding nits

- is clean enough for final WG review

This effort is related to the Traffic Class Label (TCL) effort 
currently progressing in MMUSIC

http://www.ietf.org/internet-drafts/draft-ietf-mmusic-traffic-class-for-sdp-03.txt

(with my individual hat on)

James


From ietf-ipr@ietf.org  Mon Mar  4 22:24:22 2013
Return-Path: <ietf-ipr@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF7521F884A; Mon,  4 Mar 2013 22:24:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.108
X-Spam-Level: 
X-Spam-Status: No, score=-102.108 tagged_above=-999 required=5 tests=[AWL=0.492, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s2RHQV7NdC4S; Mon,  4 Mar 2013 22:24:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BB9C921F87F5; Mon,  4 Mar 2013 22:24:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-ipr@ietf.org>
To: lars.eggert@nokia.com,gorry@erg.abdn.ac.uk
X-Test-IDTracker: no
X-IETF-IDTracker: 4.41
Message-ID: <20130305062421.31674.22687.idtracker@ietfa.amsl.com>
Date: Mon, 04 Mar 2013 22:24:21 -0800
Cc: gorry@erg.abdn.ac.uk, tsvwg@ietf.org, jmpolk@cisco.com, ipr-announce@ietf.org
Subject: [tsvwg] IPR Disclosure: SSH Communications Security Corp's Statement about	IPR related to RFC 5405
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Mar 2013 06:24:22 -0000

Dear Lars Eggert, Gorry Fairhurst:

 An IPR disclosure that pertains to your RFC entitled "Unicast UDP Usage
Guidelines for Application Designers" (RFC5405) was submitted to the IETF
Secretariat on 2013-02-23 and has been posted on the "IETF Page of Intellec=
tual
Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1988/). The =
title
of the IPR disclosure is "SSH Communications Security Corp's Statement abou=
t IPR
related to RFC 5405."");

The IETF Secretariat


From john@jlc.net  Wed Mar  6 01:15:28 2013
Return-Path: <john@jlc.net>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1D2321F875A; Wed,  6 Mar 2013 01:15:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.166
X-Spam-Level: 
X-Spam-Status: No, score=-106.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pE0n1lhrbM6c; Wed,  6 Mar 2013 01:15:26 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 800CA21F8615; Wed,  6 Mar 2013 01:15:26 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 45A1733C21; Wed,  6 Mar 2013 04:15:10 -0500 (EST)
Date: Wed, 6 Mar 2013 04:15:10 -0500
From: John Leslie <john@jlc.net>
To: ietf@ietf.org
Message-ID: <20130306091510.GA45477@verdi>
References: <20130221162137.31566.7988.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130221162137.31566.7988.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.4.1i
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-byte-pkt-congest-09.txt> (Byte and Packet Congestion Notification) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2013 09:15:28 -0000

The IESG <iesg-secretary@ietf.org> wrote:
> 
> The IESG has received a request from the Transport Area Working Group WG
> (tsvwg) to consider the following document:
> - 'Byte and Packet Congestion Notification'
>   <draft-ietf-tsvwg-byte-pkt-congest-09.txt> as Best Current Practice
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-03-07. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.

   This document has a rather long history in TSVWG, and IMHO deserves
to be published as is, but not as a Best Current Practice.

   Fundamentally, it updates RFC 2309 (an Informational document) to
deprecate a practice which seems essentially unused, and goes into detail
appropriate to an academic paper about the theoretical basis for doing
this.

   According to the document writeup I find in the datatracker:
] 
] This document is intended as BCP. (This was discussed at IETF-81 and that
] the status changed from Informational to BCP, because the draft provides
] guidance to implementors and people configuring routers and hosts).

   I cannot find any minutes for that WG meeting. I am willing to believe
Gorry that such a recommendation happened at that meeting (where I was not
present), but I do not find it to have been discussed on-list at all.

   I do not agree that its major purpose is to provide such advice, nor
do I see how "implementors and people configuring" would be likely to
get clear advice from a 43-page document that reads like an academic
paper. For one example:

> Abstract
>    This document provides recommendations of best current practice for
>    dropping or marking packets using active queue management (AQM) such
>    as random early detection (RED) or pre-congestion notification (PCN).
>    We give three strong recommendations: (1) packet size should be taken
>    into account when transports read and respond to congestion
>    indications...

   "Packet size should be taken into account when transports read and
respond to congestion indications" is simply too vague. There has been
on-list discussion of what this might mean; but it has not resulted in
clear, concise advice to implementors.

   In no sense do I believe it worth holding up this document any longer
to add "clear advice" -- I believe that would only add years to the delay.
The document deserves to be published, but with Informational status so
folks don't spend their time trying to interpret its "advice".

--
John Leslie <john@jlc.net>

From gorry@erg.abdn.ac.uk  Wed Mar  6 01:50:06 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB29B21F874B; Wed,  6 Mar 2013 01:50:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.953
X-Spam-Level: 
X-Spam-Status: No, score=-105.953 tagged_above=-999 required=5 tests=[AWL=0.646, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ibJrmJWhTYBn; Wed,  6 Mar 2013 01:50:06 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8C121F862E; Wed,  6 Mar 2013 01:50:02 -0800 (PST)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 627DA2B4275; Wed,  6 Mar 2013 09:50:01 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Wed, 6 Mar 2013 09:50:01 -0000
Message-ID: <0d5d7917f96062137ef225dd365559fe.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <20130306091510.GA45477@verdi>
References: <20130221162137.31566.7988.idtracker@ietfa.amsl.com> <20130306091510.GA45477@verdi>
Date: Wed, 6 Mar 2013 09:50:01 -0000
From: gorry@erg.abdn.ac.uk
To: "John Leslie" <john@jlc.net>
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: ietf@ietf.org, tsv-ads@ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-byte-pkt-congest-09.txt> (Byte and Packet Congestion Notification) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2013 09:50:06 -0000

Thanks for the note. I'd like to respond on the question of intended
status. I hope this may allow others to also comment.

The discussion on the proposed milestone was at  IETF-81, Quebec City,
http://tools.ietf.org/wg/tsvwg/minutes?item=minutes81.html.  This was
followed-up with the ADs, with a result that the document milestone
proposed BCP status.

I do note that this updates an Informational draft, and do not know of
other normative dependencies.

Now is the correct time to check the standards status if this needs to be
reviewed.  As I understand, this is an AD decision.

Gorry
(tsvwg Co-Chair)

> The IESG <iesg-secretary@ietf.org> wrote:
>>
>> The IESG has received a request from the Transport Area Working Group WG
>> (tsvwg) to consider the following document:
>> - 'Byte and Packet Congestion Notification'
>>   <draft-ietf-tsvwg-byte-pkt-congest-09.txt> as Best Current Practice
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-03-07. Exceptionally, comments may
>> be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>
>    This document has a rather long history in TSVWG, and IMHO deserves
> to be published as is, but not as a Best Current Practice.
>
>    Fundamentally, it updates RFC 2309 (an Informational document) to
> deprecate a practice which seems essentially unused, and goes into detail
> appropriate to an academic paper about the theoretical basis for doing
> this.
>
>    According to the document writeup I find in the datatracker:
> ]
> ] This document is intended as BCP. (This was discussed at IETF-81 and
> that
> ] the status changed from Informational to BCP, because the draft provides
> ] guidance to implementors and people configuring routers and hosts).
>
>    I cannot find any minutes for that WG meeting. I am willing to believe
> Gorry that such a recommendation happened at that meeting (where I was not
> present), but I do not find it to have been discussed on-list at all.
>
>    I do not agree that its major purpose is to provide such advice, nor
> do I see how "implementors and people configuring" would be likely to
> get clear advice from a 43-page document that reads like an academic
> paper. For one example:
>
>> Abstract
>>    This document provides recommendations of best current practice for
>>    dropping or marking packets using active queue management (AQM) such
>>    as random early detection (RED) or pre-congestion notification (PCN).
>>    We give three strong recommendations: (1) packet size should be taken
>>    into account when transports read and respond to congestion
>>    indications...
>
>    "Packet size should be taken into account when transports read and
> respond to congestion indications" is simply too vague. There has been
> on-list discussion of what this might mean; but it has not resulted in
> clear, concise advice to implementors.
>
>    In no sense do I believe it worth holding up this document any longer
> to add "clear advice" -- I believe that would only add years to the delay.
> The document deserves to be published, but with Informational status so
> folks don't spend their time trying to interpret its "advice".
>
> --
> John Leslie <john@jlc.net>
>



From Ruediger.Geib@telekom.de  Wed Mar  6 01:54:45 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDF2321F8581; Wed,  6 Mar 2013 01:54:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ymlPEzh4AG8Z; Wed,  6 Mar 2013 01:54:43 -0800 (PST)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id 0E97A21F8573; Wed,  6 Mar 2013 01:54:40 -0800 (PST)
Received: from he113676.emea1.cds.t-internal.com ([10.134.99.29]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 06 Mar 2013 10:54:39 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113676.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 6 Mar 2013 10:54:39 +0100
From: <Ruediger.Geib@telekom.de>
To: <david.black@emc.com>
Date: Wed, 6 Mar 2013 10:54:38 +0100
Thread-Topic: I-D Action: draft-ietf-idr-sla-exchange-00.txt
Thread-Index: AQHOFQxM0cBFOjlbZk+SD9PaSGdNOZiOQWGAgAGuRKCACH2t0A==
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A457467@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE7128F9F7114@MX15A.corp.emc.com> <F5C7FB9548FA6A4B8538AFEF6199B0ED151CA9A3@xmb-aln-x10.cisco.com> <8D3D17ACE214DC429325B2B98F3AE7128F9F7443@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7128F9F7443@MX15A.corp.emc.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: idr@ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-idr-sla-exchange-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2013 09:54:45 -0000

David,

I agree, relationship between both documents needs more discussion.
As diffserv-intercon already refers to work of Thomas Knoll, a
future reference to idr-sla-exchange certainly isn't an issue.
But I'd prefer to look at both as separate activities which
may benefit from each other for the time being.

Regards,

R=FCdiger


-----Original Message-----
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of B=
lack, David
Sent: Friday, March 01, 2013 3:03 AM
To: Shitanshu Shah (svshah)
Cc: idr@ietf.org; tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-idr-sla-exchange-00.txt

<snip>

This message is sent as an individual with <tsvwg WG co-chair hat OFF>.

The drafts appear to be aimed at different, but overlapping use cases -
the idr-sla-exchange draft appears to be primarily concerned with
provider-customer relationships and purchased destination (AS) specific
service (e.g., see Section 7).  The diffserv-intercon draft is primarily
concerned with interconnection of carrier networks - while that's primarily
a provider-provider case that appears to be of less interest to the
idr-sla-exchange draft, both the provider-customer and purchased service
(e.g., in the form of transit) cases may occur in provider-provider
relationships.

As already noted in the thread, the drafts support rather different SLA
frameworks among networks:

- idr-sla-exchange is descriptive and broad - it anticipates a plethora
        of possible multi-class SLA specifications that may need to be
        described based on specific contracts with customers and other
        network operators.  It includes bandwidth thresholds and remarking
        instructions for a variety of marking mechanisms (e.g., diffserv,
        Ethernet priority).
- diffserv-intercon prescribes a single multi-class SLA specification
        and a single set of diffserv PHBs (which have preferred DSCPs)
        intended for widespread use by a single carrier.

Based on the above, the drafts could well be complementary, although more
discussion of the relationship among them seems like a good idea in Orlando=
.

<snip>

From Ruediger.Geib@telekom.de  Wed Mar  6 04:41:47 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2146021F86F5 for <tsvwg@ietfa.amsl.com>; Wed,  6 Mar 2013 04:41:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EVvXgLkn6gcm for <tsvwg@ietfa.amsl.com>; Wed,  6 Mar 2013 04:41:46 -0800 (PST)
Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) by ietfa.amsl.com (Postfix) with ESMTP id 58E6721F86F4 for <tsvwg@ietf.org>; Wed,  6 Mar 2013 04:41:46 -0800 (PST)
Received: from he111631.emea1.cds.t-internal.com ([10.134.93.23]) by tcmail41.telekom.de with ESMTP/TLS/AES128-SHA; 06 Mar 2013 13:41:44 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE111631.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 6 Mar 2013 13:41:44 +0100
From: <Ruediger.Geib@telekom.de>
To: <brian.e.carpenter@gmail.com>
Date: Wed, 6 Mar 2013 13:41:43 +0100
Thread-Topic: [tsvwg] David Black's comments on draft-geib-tsvwg-diffserv-intercon-
Thread-Index: Ac4WWGYwoUDrlp29Ssy19SLtkpfEFQEDj5gA
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A4575C6@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE7128F9F7414@MX15A.corp.emc.com> <51306970.2080705@gmail.com>
In-Reply-To: <51306970.2080705@gmail.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] David Black's comments on	draft-geib-tsvwg-diffserv-intercon-
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2013 12:41:47 -0000

Brian,

while that may have been the original intention, it took years until router=
 vendors
supported a mapping table from DSCP to 3-bit value. But that's not all. MPL=
S networks
may be operated with Pen-ultimate Hop Popping, meaning that public IP traff=
ic passes
the last MPLS hop without a label. In that case full DSCP based classificat=
ion is
not desireable, the forwarding should be class based (i.e. 3-bit based).

Regards,

R=FCdiger


-----Original Message-----
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of B=
rian E Carpenter
Sent: Friday, March 01, 2013 9:40 AM
To: Black, David
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] David Black's comments on draft-geib-tsvwg-diffserv-in=
tercon-

On 28/02/2013 23:09, Black, David wrote:
...
> The introduction should explain more about copying of the "IP Precedence =
Bits"
> to the MPLS TC or Ethernet P-Bits - the crucial thing that needs to be st=
ated
> is that the bits involved are the first 3 bits in the DSCP, and the value=
s
> for the recommended DSCPs for AF and EF were chosen in part based on this
> consideration, so that EF has a higher priority than AF (and most other
> traffic) when this is done.  This is described in Section 5, but should
> also be explained in the introduction.

It should also, IMHO, be made clear that this is a bit of a hack,
originally intended for the benefit of legacy IPv4 routers that were
not diffserv-aware. The correct technique is a mapping table from
DSCP to 3-bit value, not a dumb mask.

   Brian

From Ruediger.Geib@telekom.de  Wed Mar  6 05:19:15 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9063D21F851E for <tsvwg@ietfa.amsl.com>; Wed,  6 Mar 2013 05:19:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QZKtVD-w4Ffh for <tsvwg@ietfa.amsl.com>; Wed,  6 Mar 2013 05:19:15 -0800 (PST)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id B2D5521F84F2 for <tsvwg@ietf.org>; Wed,  6 Mar 2013 05:19:14 -0800 (PST)
Received: from he111628.emea1.cds.t-internal.com ([10.134.93.20]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 06 Mar 2013 14:19:12 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE111628.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 6 Mar 2013 14:19:12 +0100
From: <Ruediger.Geib@telekom.de>
To: <sebastien.jobert@orange.com>
Date: Wed, 6 Mar 2013 14:19:12 +0100
Thread-Topic: New version notification draft-geib-tsvwg-diffserv-intercon-02.txt
Thread-Index: Ac4TSjIrWVcoB5h5Q2+YBmDr3UIOBgACJ1JwAJhuw0AAA3+sUAAmxJ1wAQLieYA=
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A457645@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50167B9AF69@HE111643.EMEA1.CDS.T-INTERNAL.COM> <526_1362057197_512F57EC_526_12045_1_7F67B91079F7C74F9DAB55FC7872661E0B0400@PEXCVZYM12.corporate.adroot.infra.ftgroup> <CA7A7C64CC4ADB458B74477EA99DF6F5016A301943@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5512_1362141725_5130A21D_5512_302_1_7F67B91079F7C74F9DAB55FC7872661E0B0A17@PEXCVZYM12.corporate.adroot.infra.ftgroup>
In-Reply-To: <5512_1362141725_5130A21D_5512_302_1_7F67B91079F7C74F9DAB55FC7872661E0B0A17@PEXCVZYM12.corporate.adroot.infra.ftgroup>
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
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] New version notification	draft-geib-tsvwg-diffserv-intercon-02.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2013 13:19:15 -0000

Hello Sebastien,

<snip>

  [RG] Good point, I may be unclear here. I'd expect the classes to be supp=
orted. Class
  definitions should stay qualitative. Class properties should be standardi=
sed. The PHBs
  should be maintained in the sense that if received with different codepoi=
nts at
  interconnection, they should leave with different codepoints on interconn=
ection. So
  treating different PHBs of one class only as one class is allright.
  The minimum expectation then is support of a class a specified, if the In=
tercon class
  and codepoint scheme is used. I don't think there should be an obligation=
 to support
  all four classes that's a SHOULD at best. I guess the draft needs to say =
that.

  [SJ] I agree that class definition must remain qualitative. However, it i=
s not fully
  clear to me what you mean when you say that "the class properties should =
be standardized".
  Personally, as I mentioned, I believe that it will be extremely difficult=
 (not to say
  impossible) to agree on a common behavior, since various network operator=
s have in general
  different configurations/policies. SLA expectations should not be part of=
 this document
  IMHO, since it is a topic to be discussed between operators, on a case by=
 case basis and
  depending on the context. Could you clarify your view on this point? For =
instance, do
  you expect that if an operator implements one of the class defined, then =
this operator
  must implement exactly the PHB mentioned in the draft in all the network =
nodes? Is there
  freedom left to the operator? Is there any plan to include aspects relate=
d to SLA in
  this draft?

[RG2] SLAs perfromance specifications will stay bilateral. I personally ref=
use to work on
performance-budget-sharing approaches in whatever standards body before ope=
rational practice
has paved a reasonable road to standardisation. It's to early for something=
 like that today.
And IETF doesn't do that anyway, and I respect that.

[RG2] It is important to be aware that a class may be designed for traffic =
with specific
properties at Interconnection points, if two interconnecting parties work b=
y per
class engineering.
What I'd like to avoid is someone looking at traffic requirements like "ver=
y low loss"
for IPTV traffic and then pick a peer network class at interconnection offe=
ring very low
loss based on the assumption of a moderate percentage of random RED drops r=
esulting in
fast load reduction. I avoided to write "mainly UDP traffic in a class opti=
mised for
TCP transport" here - using UDP/TCP to describe classes could be misleading=
.
There's a SLA however in place between interconnecting parties, which will =
fix service
performance. Text may be added to state, that it is the matter of a network
provider how to produce a class which has been agreed at an interconnection=
 point.
Network internal Best Effort transport and overprovisioning is an example o=
f a
valid option.

Regards,

R=FCdiger



From david.black@emc.com  Wed Mar  6 07:08:34 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE0EE21F8BF0 for <tsvwg@ietfa.amsl.com>; Wed,  6 Mar 2013 07:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4VnrsCP9bX7u for <tsvwg@ietfa.amsl.com>; Wed,  6 Mar 2013 07:08:33 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id B5E3021F8C0C for <tsvwg@ietf.org>; Wed,  6 Mar 2013 07:08:33 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r26F8HnM027315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Mar 2013 10:08:21 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 6 Mar 2013 10:08:05 -0500
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r26F84TR018645; Wed, 6 Mar 2013 10:08:04 -0500
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub13.corp.emc.com ([128.222.70.234]) with mapi; Wed, 6 Mar 2013 10:08:03 -0500
From: "Black, David" <david.black@emc.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>, "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>
Date: Wed, 6 Mar 2013 10:08:03 -0500
Thread-Topic: [tsvwg] David Black's comments	on draft-geib-tsvwg-diffserv-intercon-
Thread-Index: Ac4WWGYwoUDrlp29Ssy19SLtkpfEFQEDj5gAAAVEHSA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71290DCD1F1@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7128F9F7414@MX15A.corp.emc.com> <51306970.2080705@gmail.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A4575C6@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A4575C6@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] David Black's comments	on	draft-geib-tsvwg-diffserv-intercon-
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2013 15:08:35 -0000

Ok, so Brian's "bit of a hack" may not have been the ideal words, and I've =
done far
worse in email ;-), but he's absolutely correct that full mapping of indivi=
dual DSCP
values is the "right answer" for this.  Nonetheless, as Ruediger points out=
, between
gear w/o diffserv support and MPLS PHP, there are "running code" benefits i=
n practice
from assigning DSCPs in a fashion that keeps the original IPv4 use of the f=
irst 3
bits of the DSCP field in mind.

That sort of explanation would probably be useful in the draft.

Thanks,
--David

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Ruediger.Geib@telekom.de
> Sent: Wednesday, March 06, 2013 7:42 AM
> To: brian.e.carpenter@gmail.com
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] David Black's comments on draft-geib-tsvwg-diffserv-
> intercon-
>=20
> Brian,
>=20
> while that may have been the original intention, it took years until rout=
er vendors
> supported a mapping table from DSCP to 3-bit value. But that's not all. M=
PLS networks
> may be operated with Pen-ultimate Hop Popping, meaning that public IP tra=
ffic passes
> the last MPLS hop without a label. In that case full DSCP based classific=
ation is
> not desireable, the forwarding should be class based (i.e. 3-bit based).
>=20
> Regards,
>=20
> R=FCdiger
>=20
>=20
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> Sent: Friday, March 01, 2013 9:40 AM
> To: Black, David
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] David Black's comments on draft-geib-tsvwg-diffserv-
> intercon-
>=20
> On 28/02/2013 23:09, Black, David wrote:
> ...
> > The introduction should explain more about copying of the "IP Precedenc=
e
> Bits"
> > to the MPLS TC or Ethernet P-Bits - the crucial thing that needs to be =
stated
> > is that the bits involved are the first 3 bits in the DSCP, and the val=
ues
> > for the recommended DSCPs for AF and EF were chosen in part based on th=
is
> > consideration, so that EF has a higher priority than AF (and most other
> > traffic) when this is done.  This is described in Section 5, but should
> > also be explained in the introduction.
>=20
> It should also, IMHO, be made clear that this is a bit of a hack,
> originally intended for the benefit of legacy IPv4 routers that were
> not diffserv-aware. The correct technique is a mapping table from
> DSCP to 3-bit value, not a dumb mask.
>=20
>    Brian


From preethi.cis@gmail.com  Wed Mar  6 10:26:35 2013
Return-Path: <preethi.cis@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E5A21F8A1C for <tsvwg@ietfa.amsl.com>; Wed,  6 Mar 2013 10:26:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level: 
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nbLzNYhfuSMo for <tsvwg@ietfa.amsl.com>; Wed,  6 Mar 2013 10:26:35 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8131821F89E2 for <tsvwg@ietf.org>; Wed,  6 Mar 2013 10:26:24 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id wz12so6355969pbc.31 for <tsvwg@ietf.org>; Wed, 06 Mar 2013 10:26:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:user-agent:date:subject:from:to:message-id:thread-topic :mime-version:content-type; bh=JYoD08sXra0cTfPoScgBoMlL7TvAURynGYuOiIKb3FA=; b=gbqeGLqZKpqZo80L+U1ta1ZeA+gf7quT6EJGWs6/c+GiWEHsvfMEAFoBHZ8Qv4YUn0 tPlASAQNVMulmjAw55QgyQ87MtqiUuTvyoZWKclkgQmmqDFNYb0NiwE/CHMFtJ0K51dW CvCJpj/hZudoTI3xcPNxR9b6OY68Cxb2nw1MOX1GrV+jh7oB2a1oslJZOL91u6mp/uEr +hDC1SCzrLS0QGOSEyziUptKnMT3X+IHhtaPQj0mY/fH/5yds7Dzc6J26pmwadw4r4rR lPVPHhgm5sTlzNo/F5PhpdEySjBUjjGKxf3F5gfCdqf2KrZ4PjzBvHrjHBKzriVe4Az2 hmXg==
X-Received: by 10.68.203.9 with SMTP id km9mr42221429pbc.191.1362594384138; Wed, 06 Mar 2013 10:26:24 -0800 (PST)
Received: from [10.33.22.215] (128-107-239-234.cisco.com. [128.107.239.234]) by mx.google.com with ESMTPS id eg1sm21356158pbb.33.2013.03.06.10.26.22 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 06 Mar 2013 10:26:23 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.2.1.120420
Date: Wed, 06 Mar 2013 10:26:19 -0800
From: Preethi Natarajan <preethi.cis@gmail.com>
To: <tsvwg@ietf.org>, <iccrg@irtf.org>
Message-ID: <CD5CCA4B.22E14%preethi.cis@gmail.com>
Thread-Topic: PIE Simulation Code
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3445410382_13533825"
Subject: [tsvwg] PIE Simulation Code
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2013 18:26:35 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3445410382_13533825
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi all,

Few weeks ago, the PIE (Proportional Integral Controller Enhanced) AQM
scheme was described in this initial draft --
http://tools.ietf.org/html/draft-pan-tsvwg-pie-00.

As follow up, the corresponding pseudocode and ns-2 simulation code + README
can be found here -- ftp://ftpeng.cisco.com/fred/ropan/

Best,
Preethi (on behalf of co-authors).



--B_3445410382_13533825
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>Hi all,</div><div><br></div>=
<div>Few weeks ago, the PIE (Proportional Integral Controller Enhanced) AQM =
scheme was described in this initial draft --&nbsp;<a href=3D"http://tools.iet=
f.org/html/draft-pan-tsvwg-pie-00">http://tools.ietf.org/html/draft-pan-tsvw=
g-pie-00</a>.</div><div><br></div><div>As follow up, the corresponding pseud=
ocode and ns-2 simulation code + README can be found here --&nbsp;<a href=3D"f=
tp://ftpeng.cisco.com/fred/ropan">ftp://ftpeng.cisco.com/fred/ropan</a>/</di=
v><div><br></div><div>Best,</div><div>Preethi (on behalf of co-authors).</di=
v></body></html>

--B_3445410382_13533825--



From jmpolk@cisco.com  Wed Mar  6 21:17:03 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1061E21F8633 for <tsvwg@ietfa.amsl.com>; Wed,  6 Mar 2013 21:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.772
X-Spam-Level: 
X-Spam-Status: No, score=-108.772 tagged_above=-999 required=5 tests=[AWL=1.828, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e+-+-TGWB3Mq for <tsvwg@ietfa.amsl.com>; Wed,  6 Mar 2013 21:17:02 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id BC15221F84B1 for <tsvwg@ietf.org>; Wed,  6 Mar 2013 21:17:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1957; q=dns/txt; s=iport; t=1362633421; x=1363843021; h=message-id:date:to:from:subject:mime-version; bh=k6t1HnWPo9UHb7ttqlvbxOxlOqQmIxPjtvTAS09KJf0=; b=U61FBfJePtstAyil6n51uE9vpeGXqsx4D8k0TrvqjiHDcwo5dIXJtKH0 daPnJjDMIATd00uiE0v7Xe9hGo2iK2u1kNs5SU1jmhW+bKzLcv50vlY7Z o4MWWGjo4fbDyDA/aTbYzVT7O4It1cXYFbl9XN948/wHYrLaWK45OFeex w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHYiOFGtJXG8/2dsb2JhbABDxioWc4JqAlYlFR8KYIgKDJlzoU6NW4FOgyoDiGyeT4MogVM
X-IronPort-AV: E=Sophos;i="4.84,800,1355097600"; d="scan'208";a="184701139"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-8.cisco.com with ESMTP; 07 Mar 2013 05:17:01 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) (authenticated bits=0) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r275H1YU028686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Thu, 7 Mar 2013 05:17:01 GMT
Message-Id: <201303070517.r275H1YU028686@rcdn-core2-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 06 Mar 2013 23:17:01 -0600
To: tsvwg@ietf.org
From: James Polk <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Subject: [tsvwg] RFC 4594-update revised
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2013 05:17:03 -0000

TSVWG

(with my individual hat on)

Apologies for getting this announcement out this late, but this just 
yesterday showed up in the archives - and I didn't want to point to 
something and have 'nothing' appear (other than an error message).

The only thing I changed in this version was add a new section with a 
high level of what I'm proposing needs to be changed in RFC 4594. The 
section is 1.6, and is a page and a half long. It became obvious that 
rewriting RFC 4594 was not only a beast to write but a beast to read.

Comments are encouraged and welcome.

I will be presenting this draft in our Thursday session (3:30-4:30pm).

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

     Title         : Standard Configuration of DiffServ Service Classes
     Author(s)     : J. Polk
     Filename      : draft-polk-tsvwg-rfc4594-update
     Pages         : 74
     Date          : March 5, 2013

    This document describes service classes configured with DiffServ and
    identifies how they are used and how to construct them using
    Differentiated Services Code Points (DSCPs), traffic conditioners,
    Per-Hop Behaviors (PHBs), and Active Queue Management (AQM)
    mechanisms.  There is no intrinsic requirement that particular
    DSCPs, traffic conditioners, PHBs, and AQM be used for a certain
    service class, but for consistent behavior under the same network
    conditions, configuring networks as described here is appropriate.

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

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

<ftp://ftp.ietf.org/internet-drafts/draft-polk-tsvwg-rfc4594-update>

James


From sebastien.jobert@orange.com  Thu Mar  7 01:16:41 2013
Return-Path: <sebastien.jobert@orange.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E018D21F89AA for <tsvwg@ietfa.amsl.com>; Thu,  7 Mar 2013 01:16:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ci1dGwmM47Uq for <tsvwg@ietfa.amsl.com>; Thu,  7 Mar 2013 01:16:39 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id BDB1321F8995 for <tsvwg@ietf.org>; Thu,  7 Mar 2013 01:16:38 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 242D218C9E9; Thu,  7 Mar 2013 10:16:37 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 0249C4C05D; Thu,  7 Mar 2013 10:16:37 +0100 (CET)
Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Thu, 7 Mar 2013 10:16:36 +0100
From: <sebastien.jobert@orange.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
Thread-Topic: New version notification draft-geib-tsvwg-diffserv-intercon-02.txt
Thread-Index: Ac4TSjIrWVcoB5h5Q2+YBmDr3UIOBgACJ1JwAJhuw0AAA3+sUAAmxJ1wAQLieYAAKqicEA==
Date: Thu, 7 Mar 2013 09:16:36 +0000
Message-ID: <6624_1362647797_51385AF5_6624_2971_1_7F67B91079F7C74F9DAB55FC7872661E0B21A2@PEXCVZYM12.corporate.adroot.infra.ftgroup>
References: <CA7A7C64CC4ADB458B74477EA99DF6F50167B9AF69@HE111643.EMEA1.CDS.T-INTERNAL.COM> <526_1362057197_512F57EC_526_12045_1_7F67B91079F7C74F9DAB55FC7872661E0B0400@PEXCVZYM12.corporate.adroot.infra.ftgroup> <CA7A7C64CC4ADB458B74477EA99DF6F5016A301943@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5512_1362141725_5130A21D_5512_302_1_7F67B91079F7C74F9DAB55FC7872661E0B0A17@PEXCVZYM12.corporate.adroot.infra.ftgroup> <CA7A7C64CC4ADB458B74477EA99DF6F5016A457645@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A457645@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.7.82421
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] New version notification	draft-geib-tsvwg-diffserv-intercon-02.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2013 09:16:42 -0000

Thanks R=FCdiger for the clarifications. I think we are in line.
SLA are to be discussed on a case-by-case basis, and we are looking here at=
 a generic description of the interconnection classes which do not force im=
plementations in the networks. As you mentioned, there are indeed several w=
ays to ensure that one particular class meets certain traffic requirements =
(overprovisioning been one example).

Thanks.

BR,

S=E9bastien

-----Message d'origine-----
De=A0: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]=20
Envoy=E9=A0: mercredi 6 mars 2013 14:19
=C0=A0: JOBERT Sebastien OLNC/OLN
Cc=A0: tsvwg@ietf.org
Objet=A0: RE: New version notification draft-geib-tsvwg-diffserv-intercon-0=
2.txt

Hello Sebastien,

<snip>

  [RG] Good point, I may be unclear here. I'd expect the classes to be supp=
orted. Class
  definitions should stay qualitative. Class properties should be standardi=
sed. The PHBs
  should be maintained in the sense that if received with different codepoi=
nts at
  interconnection, they should leave with different codepoints on interconn=
ection. So
  treating different PHBs of one class only as one class is allright.
  The minimum expectation then is support of a class a specified, if the In=
tercon class
  and codepoint scheme is used. I don't think there should be an obligation=
 to support
  all four classes that's a SHOULD at best. I guess the draft needs to say =
that.

  [SJ] I agree that class definition must remain qualitative. However, it i=
s not fully
  clear to me what you mean when you say that "the class properties should =
be standardized".
  Personally, as I mentioned, I believe that it will be extremely difficult=
 (not to say
  impossible) to agree on a common behavior, since various network operator=
s have in general
  different configurations/policies. SLA expectations should not be part of=
 this document
  IMHO, since it is a topic to be discussed between operators, on a case by=
 case basis and
  depending on the context. Could you clarify your view on this point? For =
instance, do
  you expect that if an operator implements one of the class defined, then =
this operator
  must implement exactly the PHB mentioned in the draft in all the network =
nodes? Is there
  freedom left to the operator? Is there any plan to include aspects relate=
d to SLA in
  this draft?

[RG2] SLAs perfromance specifications will stay bilateral. I personally ref=
use to work on
performance-budget-sharing approaches in whatever standards body before ope=
rational practice
has paved a reasonable road to standardisation. It's to early for something=
 like that today.
And IETF doesn't do that anyway, and I respect that.

[RG2] It is important to be aware that a class may be designed for traffic =
with specific
properties at Interconnection points, if two interconnecting parties work b=
y per
class engineering.
What I'd like to avoid is someone looking at traffic requirements like "ver=
y low loss"
for IPTV traffic and then pick a peer network class at interconnection offe=
ring very low
loss based on the assumption of a moderate percentage of random RED drops r=
esulting in
fast load reduction. I avoided to write "mainly UDP traffic in a class opti=
mised for
TCP transport" here - using UDP/TCP to describe classes could be misleading.
There's a SLA however in place between interconnecting parties, which will =
fix service
performance. Text may be added to state, that it is the matter of a network
provider how to produce a class which has been agreed at an interconnection=
 point.
Network internal Best Effort transport and overprovisioning is an example o=
f a
valid option.

Regards,

R=FCdiger



___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From gorry@erg.abdn.ac.uk  Thu Mar  7 07:42:32 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD8EA21F8D63 for <tsvwg@ietfa.amsl.com>; Thu,  7 Mar 2013 07:42:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.276
X-Spam-Level: 
X-Spam-Status: No, score=-106.276 tagged_above=-999 required=5 tests=[AWL=0.323, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jaLuqtg3EEtR for <tsvwg@ietfa.amsl.com>; Thu,  7 Mar 2013 07:42:31 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 360C821F8D72 for <tsvwg@ietf.org>; Thu,  7 Mar 2013 07:42:31 -0800 (PST)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 5A4222B4438; Thu,  7 Mar 2013 15:42:30 +0000 (GMT)
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id BE0552B4438 for <tsvwg@ietf.org>; Thu,  7 Mar 2013 15:42:29 +0000 (GMT)
Message-ID: <5138B565.2090601@erg.abdn.ac.uk>
Date: Thu, 07 Mar 2013 15:42:29 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: tsvwg WG <tsvwg@ietf.org>
References: <D4D47BCFFE5A004F95D707546AC0D7E91F793D03@SACEXCMBX01-PRD.hq.netapp.com>
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F793D03@SACEXCMBX01-PRD.hq.netapp.com>
X-Forwarded-Message-Id: <D4D47BCFFE5A004F95D707546AC0D7E91F793D03@SACEXCMBX01-PRD.hq.netapp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [tsvwg] tsvwg slides, please!
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2013 15:42:32 -0000

Hi,

since TSVWG is on Monday, I will need copies of slides from *ALL* 
presenters by *** 6PM on Sunday *** (local time Orlando) to upload them.

We have a packed agenda, please be sure to slides ahead of the meeting 
if you wish to use slides in your Agenda slot!

Thanks,

Gorry


-- 
Prof Gorry Fairhurst, School of Engineering, University of Aberdeen.
The University of Aberdeen is a charity registered in Scotland,
No SC013683.

From ietfc@btconnect.com  Thu Mar  7 10:00:49 2013
Return-Path: <ietfc@btconnect.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B616821F8992 for <tsvwg@ietfa.amsl.com>; Thu,  7 Mar 2013 10:00:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOBebct+bLYe for <tsvwg@ietfa.amsl.com>; Thu,  7 Mar 2013 10:00:49 -0800 (PST)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe006.messaging.microsoft.com [216.32.180.189]) by ietfa.amsl.com (Postfix) with ESMTP id B70A621F8A05 for <tsvwg@ietf.org>; Thu,  7 Mar 2013 10:00:45 -0800 (PST)
Received: from mail103-co1-R.bigfish.com (10.243.78.229) by CO1EHSOBE038.bigfish.com (10.243.66.103) with Microsoft SMTP Server id 14.1.225.23; Thu, 7 Mar 2013 18:00:45 +0000
Received: from mail103-co1 (localhost [127.0.0.1])	by mail103-co1-R.bigfish.com (Postfix) with ESMTP id 045CD560177; Thu,  7 Mar 2013 18:00:45 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -20
X-BigFish: PS-20(zz98dI9371I542I1432Izz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzz8275ch1033IL17326ah8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah304l1155h)
Received: from mail103-co1 (localhost.localdomain [127.0.0.1]) by mail103-co1 (MessageSwitch) id 1362679243279908_18261; Thu,  7 Mar 2013 18:00:43 +0000 (UTC)
Received: from CO1EHSMHS011.bigfish.com (unknown [10.243.78.229])	by mail103-co1.bigfish.com (Postfix) with ESMTP id 4083D180063; Thu,  7 Mar 2013 18:00:43 +0000 (UTC)
Received: from DB3PRD0710HT001.eurprd07.prod.outlook.com (157.56.253.85) by CO1EHSMHS011.bigfish.com (10.243.66.21) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 7 Mar 2013 18:00:43 +0000
Received: from AMXPRD0111HT004.eurprd01.prod.exchangelabs.com (157.56.250.117) by pod51017.outlook.com (10.255.75.36) with Microsoft SMTP Server (TLS) id 14.16.275.6; Thu, 7 Mar 2013 18:00:33 +0000
Message-ID: <00d801ce1b5d$2567ef40$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: John Leslie <john@jlc.net>
References: <20130221162137.31566.7988.idtracker@ietfa.amsl.com> <20130306091510.GA45477@verdi>
Date: Thu, 7 Mar 2013 17:56:33 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.250.117]
X-FOPE-CRA-SourceIpAddress: 157.56.253.85
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: ietfc@btconnect.com
X-FOPE-BFA-RECEIVER: tsvwg@ietf.org
X-FOPE-BFA-RECEIVER: john@jlc.net
X-OriginatorOrg: btconnect.com
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-byte-pkt-congest-09.txt>(Byte and Packet Congestion Notification) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2013 18:00:49 -0000

----- Original Message -----
From: "John Leslie" <john@jlc.net>
To: <ietf@ietf.org>
Cc: <tsvwg@ietf.org>
Sent: Wednesday, March 06, 2013 9:15 AM
> The IESG <iesg-secretary@ietf.org> wrote:
> >
> > The IESG has received a request from the Transport Area Working
Group WG
> > (tsvwg) to consider the following document:
> > - 'Byte and Packet Congestion Notification'
> >   <draft-ietf-tsvwg-byte-pkt-congest-09.txt> as Best Current
Practice
> >
> > The IESG plans to make a decision in the next few weeks, and
solicits
> > final comments on this action. Please send substantive comments to
the
> > ietf@ietf.org mailing lists by 2013-03-07. Exceptionally, comments
may be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
>
>    This document has a rather long history in TSVWG, and IMHO deserves
> to be published as is, but not as a Best Current Practice.
>
>    Fundamentally, it updates RFC 2309 (an Informational document) to
> deprecate a practice which seems essentially unused, and goes into
detail
> appropriate to an academic paper about the theoretical basis for doing
> this.
>
>    According to the document writeup I find in the datatracker:
> ]
> ] This document is intended as BCP. (This was discussed at IETF-81 and
that
> ] the status changed from Informational to BCP, because the draft
provides
> ] guidance to implementors and people configuring routers and hosts).
>
>    I cannot find any minutes for that WG meeting. I am willing to
believe
> Gorry that such a recommendation happened at that meeting (where I was
not
> present), but I do not find it to have been discussed on-list at all.

John

I agree that minutes for IETF81 appear not to have been circulated but
they are available at

http://tools.ietf.org/wg/tsvwg/minutes?item=minutes81.html

and do record the discussion and its outcome.

The agreement of the change in status to BCP was reported to the list in
passing, 7 Sep 2011, and provoked no comment, no discussion.

And the WGLC last call clearly stated BCP as did Bob's summary of the
updates.

So we knew about it, if we wanted to, and did not comment.

Tom Petch


>
>    I do not agree that its major purpose is to provide such advice,
nor
> do I see how "implementors and people configuring" would be likely to
> get clear advice from a 43-page document that reads like an academic
> paper. For one example:
>
> > Abstract
> >    This document provides recommendations of best current practice
for
> >    dropping or marking packets using active queue management (AQM)
such
> >    as random early detection (RED) or pre-congestion notification
(PCN).
> >    We give three strong recommendations: (1) packet size should be
taken
> >    into account when transports read and respond to congestion
> >    indications...
>
>    "Packet size should be taken into account when transports read and
> respond to congestion indications" is simply too vague. There has been
> on-list discussion of what this might mean; but it has not resulted in
> clear, concise advice to implementors.
>
>    In no sense do I believe it worth holding up this document any
longer
> to add "clear advice" -- I believe that would only add years to the
delay.
> The document deserves to be published, but with Informational status
so
> folks don't spend their time trying to interpret its "advice".
>
> --
> John Leslie <john@jlc.net>
>



From karagian@cs.utwente.nl  Fri Mar  8 23:47:58 2013
Return-Path: <karagian@cs.utwente.nl>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B03FA21F856F for <tsvwg@ietfa.amsl.com>; Fri,  8 Mar 2013 23:47:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.503
X-Spam-Level: 
X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8B6IQBcZy5s7 for <tsvwg@ietfa.amsl.com>; Fri,  8 Mar 2013 23:47:57 -0800 (PST)
Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by ietfa.amsl.com (Postfix) with ESMTP id 023BC21F8569 for <tsvwg@ietf.org>; Fri,  8 Mar 2013 23:47:56 -0800 (PST)
Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.2.328.9; Sat, 9 Mar 2013 08:47:56 +0100
Received: from EXMBX23.ad.utwente.nl ([169.254.3.16]) by EXHUB02.ad.utwente.nl ([130.89.4.229]) with mapi id 14.02.0328.009; Sat, 9 Mar 2013 08:47:54 +0100
From: <karagian@cs.utwente.nl>
To: <bob.briscoe@bt.com>
Thread-Topic: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03
Thread-Index: AQHNuG567zXDhOEf1EmojaHb3rIjiJfaAz+MgAEb9QCAABFxXIAGi4cpgLwHTEqAAAB8MQ==
Date: Sat, 9 Mar 2013 07:47:53 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F4F36DDC8@EXMBX23.ad.utwente.nl>
References: <87644A58-0C27-4F5A-B09B-BD8EC1F9A10A@g11.org.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F2CC12597@EXMBX01.ad.utwente.nl> <D245A17A-F851-4707-A081-12D65C4AC0AF@g11.org.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F2CC1797D@EXMBX04.ad.utwente.nl>, <201211091623.qA9GMxVm013855@bagheera.jungle.bt.co.uk>
In-Reply-To: <201211091623.qA9GMxVm013855@bagheera.jungle.bt.co.uk>
Accept-Language: nl-NL, en-US
Content-Language: nl-NL
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mimectl: Produced By Microsoft Exchange V14.2.247.1
x-originating-ip: [86.91.134.3]
Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DDC8EXMBX23adutwent_"
MIME-Version: 1.0
Cc: philip.eardley@bt.com, anuragb@cisco.com, tsvwg@ietf.org
Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Mar 2013 07:47:59 -0000

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

Hi Bob,

Thanks for your comments!

In the below email you propose to introduce the description of a policy-bas=
ed admission control (PBAC) architecture in order to respond to the answer =
about on-path vs off-path policy.
In my opinion if it is to introduce a new policy-based admission control (P=
BAC) architecture to be used in the context of PCN, then this should be don=
e in another document and not in the draft-ietf-tsvwg-rsvp-pcn.

Regarding the answer about on-path vs off-path policy, in draft-ietf-tsvwg-=
rsvp-pcn-04 I have included the argumentation that I proposed as answer to =
the comment on-path vs off-path signaling provided by Ken, and which he act=
ually agreed with!

Best regards,
Georgios


> -----Original Message-----
> From: Bob Briscoe [mailto:bob.briscoe@bt.com<https://xs.utwente.nl/owa/re=
dir.aspx?C=3DNbum9aHfj0KVa6QWoWQdUmsGWht4ps8IsUqKQDAPZNk0j8fbXNgdf5bdf_jZa7=
dRLDi6AlK6wy0.&URL=3Dmailto%3abob.briscoe%40bt.com>]
> Sent: vrijdag 9 november 2012 16:33
> To: Karagiannis, G. (EWI)
> Cc: carlberg@g11.org.uk; anuragb@cisco.com; tsvwg@ietf.org; EARDLEY, Phil
> Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03
>
> Georgios,
>
> I shall post my full review of this draft in the next few days (needs typ=
ing up -
> currently scribbled on a paper copy). This email is solely in response to=
 your
> answer about on-path vs off-path policy.
>
> At 18:55 04/11/2012, karagian@cs.utwente.nl wrote:
> >So in this case an additional signaling protocol will be needed to be
> >specified that covers the signaling between the PCN-egress-node and the
> >centralized node and between PCN-ingress-node and the centralized node.
> >In PCN we decdided to only focus on the specification of the signaling
> >protocol that completes the feedback loop from PCN-egress-node to
> >PCN-ingress-node and to focus on the signaling protocol used between
> >the edge nodes and the centralized node.
>
> When I/we originally designed CL-PCN over RSVP (2005), the idea was that =
it
> would fit with the policy-based admission control (PBAC) architecture of
> RFC2753. In this architecture, an Intserv node at the ingress to a domain=
 is
> the policy enforcement point (PEP), and it refers to a logically centrali=
sed
> 'policy decision point' (PDP) for decisions on which flows to block/termi=
nate,
> typically using COPS.
>
> To make this doc fit the PBAC framework, all we have to do is:
> * Describe the PCN-ingress only as the PCN-ingress and not as the decisio=
n
> point (find 'decision' throughout doc and fix).
> * Add a section saying the PCN-ingress can refer flow admission and
> termination decisions to a central decision point (using e.g. COPS), whic=
h will
> respond to the PCN-ingress as per RFC2753. (Alternatively the PCN-ingress
> could itself be the policy decision point.)
> * Refer to this new PBAC section from Section 3.11 giving the admission
> decision procedure.
>
> * Some people might think this means COPS will need new protocol
> elements to carry PCN marking rates to the policy decision point. But PCN
> marking rates are irrelevant to the policy decision: the PCN-ingress just=
 uses
> PCN to determine whether it needs to block or terminate, and it refers to=
 the
> policy decision point for which flows to block/terminate.
>
> * Unfortunately, neither of the two PCN system descriptions [RFC6661,
> RFC6662] describe a PBAC-based case. The architecture [RFC5559] refers to
> the PBAC framework [RFC2753] but unfortunately doesn't spell out how it
> fits. Originally, I referenced PBAC from RFC5559, but just as the PCN w-g=
 was
> closing I realised that (some?) others in the PCN w-g were working under =
the
> assumption that the only way to talk to a centralised policy node was fro=
m
> the egress, possibly without being aware of the contents of RFC2753.
>
> I think it's OK to introduce a new architectural arrangement in this RSVP=
 doc,
> given RFC2753 is specific to the way RSVP works.
>
>
> Bob


--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DDC8EXMBX23adutwent_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <0D331B7005B09846A0A9BD2EAB13D0B9@exchange.utwente.nl>
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr" xmlns:o=3D"urn:schemas-microsoft-com:office:office">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style>.EmailQuote {
	BORDER-LEFT: #800000 2px solid; PADDING-LEFT: 4pt; MARGIN-LEFT: 1pt
}
</style><style id=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body ocsi=3D"0" fPStyle=3D"1">
<font size=3D"2"><span style=3D"FONT-SIZE: 10pt"></span></font>
<div style=3D"FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZ=
E: 10pt">
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><font =
size=3D"2">Hi Bob,<o:p></o:p></font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><o:p><=
font size=3D"2">&nbsp;</font></o:p></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><font =
size=3D"2">Thanks for your comments!<o:p></o:p></font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><o:p><=
font size=3D"2">&nbsp;</font></o:p></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><font =
size=3D"2">In the below email you propose to introduce the description of a=
 policy-based admission control (PBAC) architecture
 in order to respond to the answer about on-path vs off-path policy. <o:p><=
/o:p></font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><font =
size=3D"2">In my opinion if it is to introduce a new policy-based admission=
 control (PBAC) architecture to be used in the
 context of PCN, then this should be done&nbsp;in another document and not&=
nbsp;in the draft-ietf-tsvwg-rsvp-pcn.<o:p></o:p></font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><o:p><=
font size=3D"2">&nbsp;</font></o:p></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><font =
size=3D"2">Regarding the answer about on-path vs off-path policy, in draft-=
ietf-tsvwg-rsvp-pcn-04&nbsp;I have included the argumentation
 that I proposed as answer to the comment on-path vs off-path signaling pro=
vided by Ken, and which he actually agreed with!<o:p></o:p></font></span></=
p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><o:p><=
font size=3D"2">&nbsp;</font></o:p></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><font =
size=3D"2">Best regards,<o:p></o:p></font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><font =
size=3D"2">Georgios<o:p></o:p></font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><o:p><=
font size=3D"2">&nbsp;</font></o:p></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><o:p><=
font size=3D"2">&nbsp;</font></o:p></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US"><font =
size=3D"2">&gt; -----Original Message-----<br>
&gt; From: Bob Briscoe [</font><a href=3D"https://xs.utwente.nl/owa/redir.a=
spx?C=3DNbum9aHfj0KVa6QWoWQdUmsGWht4ps8IsUqKQDAPZNk0j8fbXNgdf5bdf_jZa7dRLDi=
6AlK6wy0.&amp;URL=3Dmailto%3abob.briscoe%40bt.com" target=3D"_blank"><font =
color=3D"#0000ff" size=3D"2">mailto:bob.briscoe@bt.com</font></a><font size=
=3D"2">]<br>
&gt; Sent: vrijdag 9 november 2012 16:33<br>
&gt; To: Karagiannis, G. (EWI)<br>
&gt; Cc: carlberg@g11.org.uk; anuragb@cisco.com; tsvwg@ietf.org; EARDLEY, P=
hil<br>
&gt; Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03<br>
&gt; <br>
&gt; Georgios,<br>
&gt; <br>
&gt; I shall post my full review of this draft in the next few days (needs =
typing up -<br>
&gt; currently scribbled on a paper copy). This email is solely in response=
 to your<br>
&gt; answer about on-path vs off-path policy.<br>
&gt; <br>
&gt; At 18:55 04/11/2012, karagian@cs.utwente.nl wrote:<br>
&gt; &gt;So in this case an additional signaling protocol will be needed to=
 be<br>
&gt; &gt;specified that covers the signaling between the PCN-egress-node an=
d the<br>
&gt; &gt;centralized node and between PCN-ingress-node and the centralized =
node.<br>
&gt; &gt;In PCN we decdided to only focus on the specification of the signa=
ling<br>
&gt; &gt;protocol that completes the feedback loop from PCN-egress-node to<=
br>
&gt; &gt;PCN-ingress-node and to focus on the signaling protocol used betwe=
en<br>
&gt; &gt;the edge nodes and the centralized node.<br>
&gt; <br>
&gt; When I/we originally designed CL-PCN over RSVP (2005), the idea was th=
at it<br>
&gt; would fit with the policy-based admission control (PBAC) architecture =
of<br>
&gt; RFC2753. In this architecture, an Intserv node at the ingress to a dom=
ain is<br>
&gt; the policy enforcement point (PEP), and it refers to a logically centr=
alised<br>
&gt; 'policy decision point' (PDP) for decisions on which flows to block/te=
rminate,<br>
&gt; typically using COPS.<br>
&gt; <br>
&gt; To make this doc fit the PBAC framework, all we have to do is:<br>
&gt; * Describe the PCN-ingress only as the PCN-ingress and not as the deci=
sion<br>
&gt; point (find 'decision' throughout doc and fix).<br>
&gt; * Add a section saying the PCN-ingress can refer flow admission and<br=
>
&gt; termination decisions to a central decision point (using e.g. COPS), w=
hich will<br>
&gt; respond to the PCN-ingress as per RFC2753. (Alternatively the PCN-ingr=
ess<br>
&gt; could itself be the policy decision point.)<br>
&gt; * Refer to this new PBAC section from Section 3.11 giving the admissio=
n<br>
&gt; decision procedure.<br>
&gt; <br>
&gt; * Some people might think this means COPS will need new protocol<br>
&gt; elements to carry PCN marking rates to the policy decision point. But =
PCN<br>
&gt; marking rates are irrelevant to the policy decision: the PCN-ingress j=
ust uses<br>
&gt; PCN to determine whether it needs to block or terminate, and it refers=
 to the<br>
&gt; policy decision point for which flows to block/terminate.<br>
&gt; <br>
&gt; * Unfortunately, neither of the two PCN system descriptions [RFC6661,<=
br>
&gt; RFC6662] describe a PBAC-based case. The architecture [RFC5559] refers=
 to<br>
&gt; the PBAC framework [RFC2753] but unfortunately doesn't spell out how i=
t<br>
&gt; fits. Originally, I referenced PBAC from RFC5559, but just as the PCN =
w-g was<br>
&gt; closing I realised that (some?) others in the PCN w-g were working und=
er the<br>
&gt; assumption that the only way to talk to a centralised policy node was =
from<br>
&gt; the egress, possibly without being aware of the contents of RFC2753.<b=
r>
&gt; <br>
&gt; I think it's OK to introduce a new architectural arrangement in this R=
SVP doc,<br>
&gt; given RFC2753 is specific to the way RSVP works.<br>
&gt; <br>
&gt; <br>
&gt; Bob</font></span></p>
<div><font size=3D"2"><span style=3D"FONT-SIZE: 10pt">&nbsp;</div>
</span></font></div>
</body>
</html>

--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DDC8EXMBX23adutwent_--

From karagian@cs.utwente.nl  Sat Mar  9 01:42:03 2013
Return-Path: <karagian@cs.utwente.nl>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EA2821F84BB; Sat,  9 Mar 2013 01:42:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.203
X-Spam-Level: 
X-Spam-Status: No, score=-0.203 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545,  HTML_MESSAGE=0.001, J_CHICKENPOX_44=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RLfaAyWh+2ni; Sat,  9 Mar 2013 01:42:01 -0800 (PST)
Received: from EXEDGE01.ad.utwente.nl (exedge01.ad.utwente.nl [130.89.5.48]) by ietfa.amsl.com (Postfix) with ESMTP id 47C0221F8415; Sat,  9 Mar 2013 01:41:59 -0800 (PST)
Received: from EXHUB01.ad.utwente.nl (130.89.4.228) by EXEDGE01.ad.utwente.nl (130.89.5.48) with Microsoft SMTP Server (TLS) id 14.2.328.9; Sat, 9 Mar 2013 10:42:53 +0100
Received: from EXMBX23.ad.utwente.nl ([169.254.3.16]) by EXHUB01.ad.utwente.nl ([130.89.4.228]) with mapi id 14.02.0328.009; Sat, 9 Mar 2013 10:41:57 +0100
From: <karagian@cs.utwente.nl>
To: <bob.briscoe@bt.com>, <anuragb@cisco.com>
Thread-Topic: Redundant aggregate reservations: draft-ietf-tsvwg-rsvp-pcn-03
Thread-Index: AQHNwzIz0DiUx9R5AUqjyGs4URlrFZidzamOgAAAn5k=
Date: Sat, 9 Mar 2013 09:41:56 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F4F36DE10@EXMBX23.ad.utwente.nl>
References: <87222982-329F-43DF-BFD8-9D3705AFE101@mimectl> <E728D0E3C41E644A96A7CCA61863BED4081DE009@xmb-aln-x12.cisco.com> <201211141251.qAECpsn0005426@bagheera.jungle.bt.co.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F2ED8FEDF@EXMBX04.ad.utwente.nl>, <201211151307.qAFD7RA0009392@bagheera.jungle.bt.co.uk>
In-Reply-To: <201211151307.qAFD7RA0009392@bagheera.jungle.bt.co.uk>
Accept-Language: nl-NL, en-US
Content-Language: nl-NL
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mimectl: Produced By Microsoft Exchange V14.2.247.1
x-originating-ip: [86.91.134.3]
Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DE10EXMBX23adutwent_"
MIME-Version: 1.0
Cc: pcn@ietf.org, philip.eardley@bt.com, tsvwg@ietf.org, rsvp-dir@ietfa.amsl.com
Subject: Re: [tsvwg] Redundant aggregate reservations: draft-ietf-tsvwg-rsvp-pcn-03
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Mar 2013 09:42:03 -0000

--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DE10EXMBX23adutwent_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi  Bob,

Thanks for your comments!

Before answering to your comments I would like to emphasize that I strongly=
 agree with the analysis done by Francois in the following email (with an a=
dditional email sent by me) on the two options of accomplishing RSVP over P=
CN signaling support:

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

In addition to that, we agree with the proposal of Francois of choosing opt=
ion (A)  since the RFC4860 operations has been thought through and there ha=
s been some implementation of RSVP Aggregation, so we have some confidence =
that the solution can deal with the more challenging situations (rerouting =
in core, failure of an ingress edge, failure of an egress edge, rerouting t=
owards a different edge,=85).

Therefore, we have used the argumentation provided by Francois in Section 1=
.2 of (new draft version) draft-ietf-tsvwg-rsvp-pcn-04 to justify why RFC48=
60 should be used to accomplish the RSVP over PCN signaling support.

After mentioning the above I will try to answer your comments below, in lin=
e!



> From: Bob Briscoe [mailto:bob.briscoe@bt.com]
>  Sent: donderdag 15 november 2012 14:08
> To: Karagiannis, G. (EWI); anuragb@cisco.com
> Cc: carlberg@g11.org.uk; anuragb@cisco.com; tsvwg@ietf.org; philip.eardle=
y@bt.com;
> PCN IETF list; rsvp-dir@ietfa.amsl.com
> Subject: Redundant aggregate reservations: draft-ietf-tsvwg-rsvp-pcn-03
> Georgios, Anurag,

> Below is the main point of my review, arguing that aggregate reservations
> are redundant. I'm reviewing as:
> - a member of the RSVP directorate
> - one of the early PCN design team
> - a co-author of draft-lefaucheur-rsvp-ecn-01, on which this draft is bas=
ed.

> I would have missed any decision to use aggregate reservations.
> Pls point me to the relevant discussion (e.g. Subject line / date).

> I admit I tuned out of much of the later PCN signalling discussion.
> I found the whole exercise of abstracting PCN away from specific signalli=
ng
> protocols highly tedious; it meant we couldn't sensibly address important
> issues like message reliability, timeliness etc.

> Nonetheless, here's why I believe RSVP aggregation is redundant:

> PCN edge-nodes support the concept of an ingress-egress aggregate in thei=
r
> own internal tables, but they don't need to refer to an aggregate on the
> wire{Note 1}. PCN-ingress and PCN-egress nodes intrinscially know which
> e2e reservations belong to which aggregate by grouping together those
> e2e reservations with the same next hop or previous hop respectively.

Georgios: This is an additional functionality that needs to be supported by=
 the PCN-ingress-nodes and PCN-egress-nodes. This is already provided by RF=
C 4860. Please see the argumentation given above of why we should choose RF=
C 4860 instead of defining a new solution.

> {Note 1: except in one case described later - but it doesn't require
> all the other baggage of aggregate reservations}

Georgios: New aggregation related features are required. These aggregation =
related features are provided by RFC 4860.  Please see the argumentation gi=
ven above why we should choose RFC 4860 instead of defining a new solution.


=3D=3DBackground=3D=3D
> Aggregate reservations [RFC3175, RFC4860] are designed to reduce the
> state required on interior nodes. Interior nodes still require state
> per aggregate reservation, but only reservation state, not classification
> and scheduling state [RFC3175, Section 1.4.1 last para].

Georgios: This is only one of the goals of using RFC3175, RFC4860, the othe=
r one is to aggregate and provide all the required protocol operations to a=
chieve the aggregation of e2e RSVP flows/states into RSVP aggregated flows/=
states.  The latter needs to also be accomplished within the PCN context, w=
here the states associated to the e2e flows need to be matched to the Ingre=
ss-Egress-Aggregate state. Therefore in the PCN context it is needed to add=
 the required protocol operation at PCN edge nodes to achieve this. These a=
dditional aggregation based protocol operations are already provided by RFC=
 4860.  Please see the argumentation given above of why we should choose RF=
C 4860 instead of defining a new solution for this purpose.


>I n contrast, as you correctly point out (in Section 2.1.7), PCN requires
> absolutely no reservation-related state on interior nodes.

Georgios: Agree with the above. This can be accomplished, see (new draft ve=
rsion) draft-ietf-tsvwg-rsvp-pcn-04, by configuring the PCN-interior-nodes =
to distinguish neither RSVP generic aggregated sessions and their associate=
d messages [RFC4860], nor e2e RSVP sessions and their associated messages [=
RFC2205].


> =3D=3DDisadvantages=3D=3D
> Requiring PCN to use aggregate reservations has the following three
> disadvantages and no advantages:

> 1) Redundant Processing
> The PATH message between aggregator and deaggregator in rsvp-pcn-03
> (triggered by an E2E PathErr message from deaggregator to aggregator)
> is redundant, and just doubles the processing required at the PCN-edge-no=
des
> (if this isn't obvious, I spell it out separately for PATH & RESV message=
s below).

Georgios: The load and processing of the Aggregated PATH and Aggregated RES=
V messages compared to the processing of the total load and processing of e=
2e RSVP messages is to be neglected.

> 2) Reduced Resilience
> Not only is an aggregate PATH redundant, it actually reduces resilience.
> Because an aggregate PATH is pinned to interior routers. Therefore, when
> routing changes, it is more complex and slower to move to the new route.
> By not pinning to interior routers, PCN was designed to 'just work' over
> interior routing changes - with no need for any changes to the RSVP PATHs=
.
> (But it would still detect overload after a re-route and terminate or
> rate-reduce flows if necessary.)

Georgios: I agree with Francois, when saying that the drawbacks pointed out=
 by Bob are probably not as serious as Bob suggested, given that the Aggreg=
ated RSVP signaling would be ignored by interior nodes. In particular, we d=
on't see why aggregate RSVP signaling would impact rerouting inside the PCN=
 core since packets from individual sessions would be routed independently =
of the reservation.


> 3) Extra Latency
> A further disadvantage is the extra latency required for the first reserv=
ation
> that sets up an aggregate. This is two ingress-egress round trips minus t=
he
> round trip time from egress to destination (or one ingress-egress round t=
rip
> if it is greater). This will rarely add to latency on heavily used
> ingress-egress aggregates, but it will occur frequently on all the
> 'long-tail' (lightly used) ingress-egress aggregates.

Georgios: This is only required for the first reservation that sets up an a=
ggregate, which will not occur often. This means that this extra latency is=
 to be neglected.


> =3D=3DPATH=3D=3D

> With RFC 3175 or 4860 aggregate paths, the aggregator forwards the e2e PA=
TH
> messages with IP protocol number RSVP-E2E-IGNORE and the deaggregator cha=
nges
> them back to RSVP before forwarding onward. Also the aggregator sends an
> aggregate PATH message, which is processed by each interior node and by
> the deaggregator.

> On a path across a PCN region, given interior nodes ignore aggregate
> PATH messages as well, the only PCN nodes that handle aggregate messages
> are the aggregator and the deaggregator. The aggregator and deaggregator
> process all the e2e PATH messages anyway, so if we require the aggregator
> to add up all the e2e PATH messages and form them into an aggregate PATH
> message, this is just extra redundant work for both PCN-edge-nodes.

Georgios: But also in the PCN context it is needed to maintain information =
about which e2e flows are associated with a Ingress-Egress-Aggregate, such =
that when a severe congestion occurs the ingress could release the accurate=
 number of the selected e2e flows that are associated with the same Ingress=
-Egress-Aggregate.
So an additional protocol operation has to be specified and implemented in =
the PCN edge nodes to maintain this association between e2e flows and the I=
ngress-Egress-Aggregate states. These additional aggregation based protocol=
 operations are already provided by RFC 4860.  Please see the argumentation=
 given above of why we should choose RFC 4860 instead of defining a new sol=
ution for this purpose.



> =3D=3DRESV=3D=3D

> The deaggregator unicasts e2e RESV messages to the previous RSVP hop,
> which is the aggregator. Therefore, if we require the deaggregator
> to add up all the RESV messages and form them into an aggregate
> RESV message, this is just redundant work for both PCN-edge-nodes,
> because they both already process all the e2e RESV messages anyway,
> and no other node uses the aggregate RESV messages.

Georgios: The answer given above related to the Aggregated PATH message hol=
ds also for the Aggregated RESV message.

> =3D=3DPCN object=3D=3D

> This raises the question of how the PCN-egress communicates the
> various marking rates (the PCN object) to the PCN-ingress. There
> are two possibilities:
> i) the PCN-egress includes a current PCN object in each e2e RESV
> that it returns to the PCN-ingress. The PCN-ingress strips the
> PCN object out before forwarding the RESV back to the previous
> RSVP hop.

> ii) the PCN-egress attaches a PCN object to an aggregate reservation,
> as in pcn-rsvp-03.

> Either are possible, because a PCN object carries information about marki=
ng
> probabilities, and PCN works on the assumption that the marking probabili=
ty
> of an ingress-egress aggregate is the same as the marking probability of
> the flows within the aggregate. A PCN object can be contained either
> in an e2e RESV or an aggregate RESV as long as the PCN-ingress can
> associate an e2e RESV with the correct aggregate (which it can, because
> it maintains an internal table of mappings between e2e reservations
> and their aggregates).

> Which of the two is best is a question of message timing...


> * For e2e admission decisions, the PCN object is only needed at the time
> each e2e RESV is sent, so option i) makes sense.

> * For flow rate reduction or flow termination decisions, the deaggregator
> needs to regularly send PCN objects to the ingress.

> The PCN-egress is sending regular e2e RESV refresh messages to the PCN-in=
gress,
> so a PCN object can be included in each of these. To ensure that PCN obje=
cts
>  are sent often enough, I suggest the PCN-egress also maintains a timer p=
er
> ingress-egress aggregate which it resets every time it sends a PCN object
> for that IEA. If the timer expires, the PCN-egress sends a PCN object
> to the PCN-egress even thought it was not triggered by an e2e RESV refres=
h.
> We could require the SESSION object in this message to refer to either of=
:
> a) any one of the e2e SESSIONs in the aggregate,
> b) the aggregate.

> In case (a), the message would need to somehow tell the ingress not to fo=
rward
> this RESV refresh to the RSVP previous hop.

> In case (b) in the PCN-ingress table of mappings between e2e SESSIONs and
> aggregate SESSIONs, it would include an entry for the aggregate that maps
> to itself. If the result of the look-up is the same as the input, it know=
s
> not to forward the RESV refresh further.

> The wire protocol doesn't need to identify whether the SESSION is an aggr=
egate
> or not. This is the one case I mentioned at the start {Note 1} where an a=
ggregate
> is referred to on the wire.

Georgios: I do not agree, using e2e RESV to carry the PCN object has severe=
 drawbacks.
In particular, what happens in the situation where there is a change of rou=
te for a given e2e RSVP reservation/session (i.e. changing its PCN-ingress-=
node and/or PCN-egress-node)  right when the PCN-egress-node decides to use=
 a e2e RSVP signalling message (associated with this e2e RSVP session) to n=
otify the aggregate PCN information (PCN admission control and/or flow term=
ination information) to the PCN-ingress-node?
In this situation it is possible that the aggregated PCN information (the P=
CN object) will not be received by the right PCN-ingress-node, having as im=
plication that the congestion in the PCN domain will not be solved accurate=
ly and in time!
This problem cannot occur when an Aggregated RESV message is used to carry =
the PCN object.



> In summary, PCN already reduces reservation state and processing to nothi=
ng
> on interior nodes. Adding aggregate reservations to PCN requires more pro=
cessing
> and state, it unnecessarily pins routes to interior nodes and adds unnece=
ssary latency.

Georgios: As I already mentioned above, we agree with the proposal of Franc=
ois of choosing option (A)  since the RFC4860 operations has been thought t=
hrough and there has been some implementation of RSVP Aggregation, so we ha=
ve some confidence that the solution can deal with the more challenging sit=
uations (rerouting in core, failure of an ingress edge, failure of an egres=
s edge, rerouting towards a different edge,=85).

Therefore, we have used the argumentation provided by Francois in Section 1=
.2 of (new draft version) draft-ietf-tsvwg-rsvp-pcn-04 to justify why RFC48=
60 should be used to accomplish the RSVP over PCN signaling support.

Best regards,
Georgios


--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DE10EXMBX23adutwent_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <5D3259ABF0B91B4890E35371E7CF4EDC@exchange.utwente.nl>
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr" xmlns:o=3D"urn:schemas-microsoft-com:office:office">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style id=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body ocsi=3D"0" fPStyle=3D"1">
<div style=3D"FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZ=
E: 10pt">
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Hi
<span style=3D"mso-spacerun: yes">&nbsp;</span>Bob,</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Thanks for your comments!<=
/font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"></span>&nbsp;</p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Before answering to your c=
omments I would like to emphasize that I strongly agree with the analysis d=
one by Francois in the following email (with
 an additional email sent by me) on the two options of accomplishing RSVP o=
ver PCN signaling support:</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"></span>&nbsp;</p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><a href=3D"http://www.ietf.org/mail-archive=
/web/tsvwg/current/msg11601.html" target=3D"_blank"><font color=3D"#0000ff"=
 size=3D"2">http://www.ietf.org/mail-archive/web/tsvwg/current/msg11601.htm=
l</font></a></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><a href=3D"http://www.ietf.org/mail-archive=
/web/tsvwg/current/msg11602.html" target=3D"_blank"><font color=3D"#0000ff"=
 size=3D"2">http://www.ietf.org/mail-archive/web/tsvwg/current/msg11602.htm=
l</font></a></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">In addition to that, we ag=
ree with the proposal of Francois of choosing option (A)<span style=3D"mso-=
spacerun: yes">&nbsp;
</span>since the </font></span><span style=3D"FONT-SIZE: 12pt; mso-fareast-=
font-family: 'Times New Roman'; mso-fareast-language: NL" lang=3D"EN-US">RF=
C4860 operations has been thought through and there has been some implement=
ation of RSVP Aggregation, so we have
 some confidence that the solution can deal with the more challenging situa=
tions (rerouting in core, failure of an ingress edge, failure of an egress =
edge, rerouting towards a different edge,=85).<o:p></o:p></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-SIZE: 12pt; mso-fareast-font-family: 'Times =
New Roman'; mso-fareast-language: NL" lang=3D"EN-US"><o:p>&nbsp;</o:p></spa=
n></p>
<p style=3D"TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><=
span lang=3D"EN-US"><font size=3D"2">Therefore, we have used the argumentat=
ion provided by Francois in Section 1.2 of (new draft version) draft-ietf-t=
svwg-rsvp-pcn-04 to justify why RFC4860
 should be used to accomplish the RSVP over PCN signaling support.</font></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">After mentioning the above=
 I will try to answer your comments below, in line!</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; From: Bob Briscoe [ma=
ilto:bob.briscoe@bt.com]
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt;<span style=3D"mso-spa=
cerun: yes">&nbsp;
</span>Sent: donderdag 15 november 2012 14:08</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; To: Karagiannis, G. (=
EWI); anuragb@cisco.com</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Cc: carlberg@g11.org.=
uk; anuragb@cisco.com; tsvwg@ietf.org; philip.eardley@bt.com;
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; PCN IETF list; rsvp-d=
ir@ietfa.amsl.com</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Subject: Redundant ag=
gregate reservations: draft-ietf-tsvwg-rsvp-pcn-03</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Georgios, Anurag,</fo=
nt></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Below is the main poi=
nt of my review, arguing that aggregate reservations
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; are redundant. I'm re=
viewing as:</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; - a member of the RSV=
P directorate</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; - one of the early PC=
N design team</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; - a co-author of draf=
t-lefaucheur-rsvp-ecn-01, on which this draft is based.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; I would have missed a=
ny decision to use aggregate reservations.
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Pls point me to the r=
elevant discussion (e.g. Subject line / date).</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; I admit I tuned out o=
f much of the later PCN signalling discussion.
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; I found the whole exe=
rcise of abstracting PCN away from specific signalling
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; protocols highly tedi=
ous; it meant we couldn't sensibly address important
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; issues like message r=
eliability, timeliness etc.
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Nonetheless, here's w=
hy I believe RSVP aggregation is redundant:</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; PCN edge-nodes suppor=
t the concept of an ingress-egress aggregate in their
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; own internal tables, =
but they don't need to refer to an aggregate on the
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; wire{Note 1}. PCN-ing=
ress and PCN-egress nodes intrinscially know which
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; e2e reservations belo=
ng to which aggregate by grouping together those
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; e2e reservations with=
 the same next hop or previous hop respectively.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios: This is an addit=
ional functionality that needs to be supported by the PCN-ingress-nodes and=
 PCN-egress-nodes. This is already provided
 by RFC 4860. Please see the argumentation given above of why we should cho=
ose RFC 4860 instead of defining a new solution.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; {Note 1: except in on=
e case described later - but it doesn't require
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; all the other baggage=
 of aggregate reservations}</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios: New aggregation =
related features are required. These aggregation related features are provi=
ded by RFC 4860.
<span style=3D"mso-spacerun: yes">&nbsp;</span>Please see the argumentation=
 given above why we should choose RFC 4860 instead of defining a new soluti=
on.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">=3D=3DBackground=3D=3D</fo=
nt></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Aggregate reservation=
s [RFC3175, RFC4860] are designed to reduce the
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; state required on int=
erior nodes. Interior nodes still require state
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; per aggregate reserva=
tion, but only reservation state, not classification
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; and scheduling state =
[RFC3175, Section 1.4.1 last para].</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios: This is only one=
 of the goals of using RFC3175, RFC4860, the other one is to aggregate and =
provide all the required protocol operations
 to achieve the aggregation of e2e RSVP flows/states into RSVP aggregated f=
lows/states.
<span style=3D"mso-spacerun: yes">&nbsp;</span>The latter needs to also be =
accomplished within the PCN context, where the states associated to the e2e=
 flows need to be matched to the Ingress-Egress-Aggregate state. Therefore =
in the PCN context it is needed to add
 the required protocol operation at PCN edge nodes to achieve this. These a=
dditional aggregation based protocol operations are already provided by RFC=
 4860.
<span style=3D"mso-spacerun: yes">&nbsp;</span>Please see the argumentation=
 given above of why we should choose RFC 4860 instead of defining a new sol=
ution for this purpose.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt;I n contrast, as you c=
orrectly point out (in Section 2.1.7), PCN requires
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; absolutely no reserva=
tion-related state on interior nodes.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios: Agree with the a=
bove. This can be accomplished, see (new draft version) draft-ietf-tsvwg-rs=
vp-pcn-04, by configuring the PCN-interior-nodes
 to distinguish neither RSVP generic aggregated sessions and their associat=
ed messages [RFC4860], nor e2e RSVP sessions and their associated messages =
[RFC2205].</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; =3D=3DDisadvantages=
=3D=3D</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Requiring PCN to use =
aggregate reservations has the following three
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; disadvantages and no =
advantages:</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; 1) Redundant Processi=
ng</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; The PATH message betw=
een aggregator and deaggregator in rsvp-pcn-03
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; (triggered by an E2E =
PathErr message from deaggregator to aggregator)
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; is redundant, and jus=
t doubles the processing required at the PCN-edge-nodes
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; (if this isn't obviou=
s, I spell it out separately for PATH &amp; RESV messages below).
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios: The load and pro=
cessing of the Aggregated PATH and Aggregated RESV messages compared to the=
 processing of the total load and processing
 of e2e RSVP messages is to be neglected.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; 2) Reduced Resilience=
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Not only is an aggreg=
ate PATH redundant, it actually reduces resilience.
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Because an aggregate =
PATH is pinned to interior routers. Therefore, when
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; routing changes, it i=
s more complex and slower to move to the new route.
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; By not pinning to int=
erior routers, PCN was designed to 'just work' over
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; interior routing chan=
ges - with no need for any changes to the RSVP PATHs.
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; (But it would still d=
etect overload after a re-route and terminate or
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; rate-reduce flows if =
necessary.)</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios: I agree with Fra=
ncois, when saying that the drawbacks pointed out by Bob are probably not a=
s serious as Bob suggested, given that the
 Aggregated RSVP signaling would be ignored by interior nodes. In particula=
r, we don't see why aggregate RSVP signaling would impact rerouting inside =
the PCN core since packets from individual sessions would be routed indepen=
dently of the reservation.
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; 3) Extra Latency</fon=
t></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; A further disadvantag=
e is the extra latency required for the first reservation
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; that sets up an aggre=
gate. This is two ingress-egress round trips minus the
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; round trip time from =
egress to destination (or one ingress-egress round trip
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; if it is greater). Th=
is will rarely add to latency on heavily used
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; ingress-egress aggreg=
ates, but it will occur frequently on all the
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; 'long-tail' (lightly =
used) ingress-egress aggregates.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios: This is only req=
uired for the first reservation that sets up an aggregate, which will not o=
ccur often. This means that this extra latency
 is to be neglected.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; =3D=3DPATH=3D=3D</fon=
t></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; With RFC 3175 or 4860=
 aggregate paths, the aggregator forwards the e2e PATH
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; messages with IP prot=
ocol number RSVP-E2E-IGNORE and the deaggregator changes
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; them back to RSVP bef=
ore forwarding onward. Also the aggregator sends an
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; aggregate PATH messag=
e, which is processed by each interior node and by
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; the deaggregator.</fo=
nt></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; On a path across a PC=
N region, given interior nodes ignore aggregate
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; PATH messages as well=
, the only PCN nodes that handle aggregate messages
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; are the aggregator an=
d the deaggregator. The aggregator and deaggregator
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; process all the e2e P=
ATH messages anyway, so if we require the aggregator
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; to add up all the e2e=
 PATH messages and form them into an aggregate PATH
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; message, this is just=
 extra redundant work for both PCN-edge-nodes.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios: But also in the =
PCN context it is needed to maintain information about which e2e flows are =
associated with a Ingress-Egress-Aggregate,
 such that when a severe congestion occurs the ingress could release the ac=
curate number of the selected e2e flows that are associated with the same I=
ngress-Egress-Aggregate.
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">So an additional protocol =
operation has to be specified and implemented in the PCN edge nodes to main=
tain this association between e2e flows and
 the Ingress-Egress-Aggregate states. These additional aggregation based pr=
otocol operations are already provided by RFC 4860.
<span style=3D"mso-spacerun: yes">&nbsp;</span>Please see the argumentation=
 given above of why we should choose RFC 4860 instead of defining a new sol=
ution for this purpose.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; =3D=3DRESV=3D=3D</fon=
t></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; The deaggregator unic=
asts e2e RESV messages to the previous RSVP hop,
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; which is the aggregat=
or. Therefore, if we require the deaggregator
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; to add up all the RES=
V messages and form them into an aggregate
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; RESV message, this is=
 just redundant work for both PCN-edge-nodes,
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; because they both alr=
eady process all the e2e RESV messages anyway,
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; and no other node use=
s the aggregate RESV messages.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios: The answer given=
 above related to the Aggregated PATH message holds also for the Aggregated=
 RESV message.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; =3D=3DPCN object=3D=
=3D</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; This raises the quest=
ion of how the PCN-egress communicates the
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; various marking rates=
 (the PCN object) to the PCN-ingress. There
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; are two possibilities=
:</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; i) the PCN-egress inc=
ludes a current PCN object in each e2e RESV
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; that it returns to th=
e PCN-ingress. The PCN-ingress strips the
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; PCN object out before=
 forwarding the RESV back to the previous
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; RSVP hop.</font></spa=
n></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; ii) the PCN-egress at=
taches a PCN object to an aggregate reservation,
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; as in pcn-rsvp-03.</f=
ont></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Either are possible, =
because a PCN object carries information about marking
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; probabilities, and PC=
N works on the assumption that the marking probability
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; of an ingress-egress =
aggregate is the same as the marking probability of
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; the flows within the =
aggregate. A PCN object can be contained either
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; in an e2e RESV or an =
aggregate RESV as long as the PCN-ingress can
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; associate an e2e RESV=
 with the correct aggregate (which it can, because
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; it maintains an inter=
nal table of mappings between e2e reservations
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; and their aggregates)=
.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; Which of the two is b=
est is a question of message timing...</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; * For e2e admission d=
ecisions, the PCN object is only needed at the time
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; each e2e RESV is sent=
, so option i) makes sense.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; * For flow rate reduc=
tion or flow termination decisions, the deaggregator
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; needs to regularly se=
nd PCN objects to the ingress.
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; The PCN-egress is sen=
ding regular e2e RESV refresh messages to the PCN-ingress,
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; so a PCN object can b=
e included in each of these. To ensure that PCN objects
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt;<span style=3D"mso-spa=
cerun: yes">&nbsp;
</span>are sent often enough, I suggest the PCN-egress also maintains a tim=
er per
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; ingress-egress aggreg=
ate which it resets every time it sends a PCN object
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; for that IEA. If the =
timer expires, the PCN-egress sends a PCN object
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; to the PCN-egress eve=
n thought it was not triggered by an e2e RESV refresh.
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; We could require the =
SESSION object in this message to refer to either of:</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; a) any one of the e2e=
 SESSIONs in the aggregate,
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; b) the aggregate.</fo=
nt></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; In case (a), the mess=
age would need to somehow tell the ingress not to forward
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; this RESV refresh to =
the RSVP previous hop.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; In case (b) in the PC=
N-ingress table of mappings between e2e SESSIONs and
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; aggregate SESSIONs, i=
t would include an entry for the aggregate that maps
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; to itself. If the res=
ult of the look-up is the same as the input, it knows
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; not to forward the RE=
SV refresh further.
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; The wire protocol doe=
sn't need to identify whether the SESSION is an aggregate
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; or not. This is the o=
ne case I mentioned at the start {Note 1} where an aggregate
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; is referred to on the=
 wire.</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios: I do not agree, =
using e2e RESV to carry the PCN object has severe drawbacks.</font></span><=
/p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">In particular, what happen=
s in the situation where there is a change of route for a given e2e RSVP re=
servation/session (i.e. changing its PCN-ingress-node
 and/or PCN-egress-node) <span style=3D"mso-spacerun: yes">&nbsp;</span>rig=
ht when the PCN-egress-node decides to use a e2e RSVP signalling message (a=
ssociated with this e2e RSVP session) to notify the aggregate PCN informati=
on (PCN admission control and/or flow termination
 information) to the PCN-ingress-node?</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">In this situation it is po=
ssible that the aggregated PCN information (the PCN object) will not be rec=
eived by the right PCN-ingress-node, having
 as implication that the congestion in the PCN domain will not be solved ac=
curately and in time!</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">This problem cannot occur =
when an Aggregated RESV message is used to carry the PCN object.</font></sp=
an></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><span style=3D"mso-spacerun: yes"><font siz=
e=3D"2"></font></span></span>&nbsp;</p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; In summary, PCN alrea=
dy reduces reservation state and processing to nothing
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; on interior nodes. Ad=
ding aggregate reservations to PCN requires more processing
</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">&gt; and state, it unneces=
sarily pins routes to interior nodes and adds unnecessary latency.</font></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios: As I already men=
tioned above, we agree with the proposal of Francois of choosing option (A)=
<span style=3D"mso-spacerun: yes">&nbsp;
</span>since the </font></span><span style=3D"FONT-SIZE: 12pt; mso-fareast-=
font-family: 'Times New Roman'; mso-fareast-language: NL" lang=3D"EN-US">RF=
C4860 operations has been thought through and there has been some implement=
ation of RSVP Aggregation, so we have
 some confidence that the solution can deal with the more challenging situa=
tions (rerouting in core, failure of an ingress edge, failure of an egress =
edge, rerouting towards a different edge,=85).<o:p></o:p></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span style=3D"FONT-SIZE: 12pt; mso-fareast-font-family: 'Times =
New Roman'; mso-fareast-language: NL" lang=3D"EN-US"><o:p>&nbsp;</o:p></spa=
n></p>
<p style=3D"TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal"><=
span lang=3D"EN-US"><font size=3D"2">Therefore, we have used the argumentat=
ion provided by Francois in Section 1.2 of (new draft version) draft-ietf-t=
svwg-rsvp-pcn-04 to justify why RFC4860
 should be used to accomplish the RSVP over PCN signaling support.</font></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Best regards,</font></span=
></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><font size=3D"2">Georgios</font></span></p>
<p style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt" class=3D"MsoNormal" alig=
n=3D"left"><span lang=3D"EN-US"><o:p><font size=3D"2">&nbsp;</font></o:p></=
span></p>
</div>
</body>
</html>

--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DE10EXMBX23adutwent_--

From karagian@cs.utwente.nl  Sat Mar  9 04:04:56 2013
Return-Path: <karagian@cs.utwente.nl>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D76C21F85E8; Sat,  9 Mar 2013 04:04:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.353
X-Spam-Level: 
X-Spam-Status: No, score=-0.353 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzs4GYFqx+SB; Sat,  9 Mar 2013 04:04:51 -0800 (PST)
Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3C73E21F85E2; Sat,  9 Mar 2013 04:04:49 -0800 (PST)
Received: from EXHUB01.ad.utwente.nl (130.89.4.228) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.2.328.9; Sat, 9 Mar 2013 13:04:50 +0100
Received: from EXMBX23.ad.utwente.nl ([169.254.3.16]) by EXHUB01.ad.utwente.nl ([130.89.4.228]) with mapi id 14.02.0328.009; Sat, 9 Mar 2013 13:04:47 +0100
From: <karagian@cs.utwente.nl>
To: <bob.briscoe@bt.com>
Thread-Topic: [PCN] FW: New Version Notification - draft-ietf-tsvwg-rsvp-pcn-03.txt
Thread-Index: AQHNw3kdbC91oYHb1EeHisclQ9W2lZid85/pgAACBIM=
Date: Sat, 9 Mar 2013 12:04:46 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F4F36DE81@EXMBX23.ad.utwente.nl>
References: <20121011194603.11308.61516.idtracker@ietfa.amsl.com> <FF1A9612A94D5C4A81ED7DE1039AB80F2CBFBEAD@EXMBX04.ad.utwente.nl>, <201211152135.qAFLZ95f010718@bagheera.jungle.bt.co.uk>
In-Reply-To: <201211152135.qAFLZ95f010718@bagheera.jungle.bt.co.uk>
Accept-Language: nl-NL, en-US
Content-Language: nl-NL
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mimectl: Produced By Microsoft Exchange V14.2.247.1
x-originating-ip: [86.91.134.3]
Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DE81EXMBX23adutwent_"
MIME-Version: 1.0
Cc: pcn@ietf.org, anuragb@cisco.com, tsvwg@ietf.org, rsvp-dir@ietfa.amsl.com
Subject: Re: [tsvwg] [PCN] FW: New Version Notification - draft-ietf-tsvwg-rsvp-pcn-03.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Mar 2013 12:04:56 -0000

--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DE81EXMBX23adutwent_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Bob,



Thanks for your comments!
Please see in line!



> -----Original Message-----
> From: Bob Briscoe [mailto:bob.briscoe@bt.com]
> Sent: donderdag 15 november 2012 22:35
> To: Karagiannis, G. (EWI); Anurag Bhargava (anuragb)
> Cc: pcn@ietf.org<mailto:pcn@ietf.org>; tsvwg@ietf.org<mailto:tsvwg@ietf.o=
rg>; rsvp-dir@ietfa.amsl.com<mailto:rsvp-dir@ietfa.amsl.com>
> Subject: Re: [PCN] FW: New Version Notification - draft-ietf-tsvwg-rsvp-p=
cn-
> 03.txt
>
> Georgios & Anurag,
>
> Thank you for this draft. Below is my review, as:
> - a member of the RSVP directorate
> - one of the PCN design team
> - a co-author of draft-lefaucheur-rsvp-ecn, on which this draft is based.
>
> I have already sent my main technical concerns in two separate emails,
> summarised below (but I suggest we use the separate threads to discuss):
>
> 1. It would be easy to allow for an off-path policy-decision point (PDP),=
 as per
> RFC2753 (policy-based admission control (PBAC) framework)

Georgios: I replied to your above proposal in a previous email!
>
> 2. PCN already reduces reservation state and processing to nothing on
> interior nodes. Adding aggregate reservations to PCN adds 3 disadvantages
> and no advantages:
> - it requires more processing and state in interior nodes and boundary-
> nodes
> - it unnecessarily pins routes to interior nodes and
> - it adds unnecessary latency.



Georgios: I answered to the thread mentioned above in a previous email sent=
 today! However, I would like to again emphasize that I strongly agree with=
 the analysis done by Francois (together with my additional email) in the f=
ollowing email on the two options of accomplishing RSVP over PCN signaling =
support:
http://www.ietf.org/mail-archive/web/tsvwg/current/msg11601.html
http://www.ietf.org/mail-archive/web/tsvwg/current/msg11602.html

In addition to that, we agree with the proposal of Francois of choosing opt=
ion (A)  since the RFC4860 operations has been thought through and there ha=
s been some implementation of RSVP Aggregation, so we have some confidence =
that the solution can deal with the more challenging situations (rerouting =
in core, failure of an ingress edge, failure of an egress edge, rerouting t=
owards a different edge,=85).

Therefore, we have used the argumentation provided by Francois in Section 1=
.2 of (new draft version) draft-ietf-tsvwg-rsvp-pcn-04 to justify why RFC48=
60 should be used to accomplish the RSVP over PCN signaling support.

>
> This email reviews comprehensibility and raises a large number of lesser
> technical concerns (26 to be precise), as well as editorial nits (many of=
 which
> may be irrelevant if I'm right about the major technical concerns).
>
> =3D=3DGeneral style=3D=3D
> I didn't find the style useful at all. Sections 1, 2 & 3 defer everything
> meaningful into pointers to other RFCs. This makes it incomprehensible,
> even if you know all the references intimately.
> Lixia's suggestion that you refer to the specific sections of other RFCs =
won't
> be enough.
>
> An RFC should be understandable without re-reading its references (reader=
s
> should have read them, but they shouldn't be expected to remember every
> detail).



Georgios: We have severely restructured the (new draft) draft-ietf-tsvwg-rs=
vp-pcn-04. We believe that the above comment has been worked out!



>
> I have to say we are moving very slowly, and backwards. When Francois Le
> Faucheur first wrote the ancestor to this draft (7 years ago!), I could
> understand it immediately, and in half the pages it covered nearly everyt=
hing
> in this draft and covered the gaps I have listed below. [In the interests=
 of full
> disclosure: I became a co-author of draft-lefaucheur-tsvwg-rsvp-ecn-00,
> nonetheless Francois's pre-00 draft was more comprehensible and complete
> than this one, even before the co-authors did the first reviews.]

Georgios: I do not agree! Note that draft-lefaucheur-tsvwg-rsvp-ecn-00 does=
 not follow the PCN signaling requirements defined in [RFC6663] and it does=
 not how it can support the PCN edge behaviors as specified in [RFC6661] an=
d [RFC6662]. While draft-ietf-tsvwg-rsvp-pcn-04 certainly does this.



>
> This draft says very little itself, but ends up much longer. For example =
Section
> 3 tediously repeats content-free text like:
> "<Title>
> In this document it is considered that for <Title> the same methods can b=
e
> used as the ones described in <reference>".
>
> Not only section 3; sections 1 & 2 also rely wholly on references, making
> them just as incomprehensible. I also agree with the other reviewers'
> suggestions to focus the introduction initially on what this draft adds, =
and
> move the background material after that.
>
> In summary: avoid phrases like "the same methods as" or "standard RSVP
> aggregation [...] procedures are used". Instead just say directly how it =
works.



Georgios: We have severely restructured and re-edited the (new draft) draft=
-ietf-tsvwg-rsvp-pcn-04. We believe that the above comment has been worked =
out!



>
>
> =3D=3DNormative & Technical Points=3D=3D
>
> =3D=3DGaps=3D=3D
>
> * How an aggregate reservation is created vs. how one is used if it is al=
ready
> present



Georgios: Done: Added the following text in Section 2.1 to address this iss=
ue:
=93The procedures for aggregation of E2E reservations over generic aggregat=
e RSVP reservations are the same as the procedures specified in Section 4 o=
f [RFC4860].



>
> * How next hop addresses are discovered (a PCN domain is only one RSVP
> hop unlike with RSVP aggregation, so although the process is similar, thi=
s
> needs to be described explicitly)



Georgios: This is explained in the (new draft) draft-ietf-tsvwg-rsvp-pcn-04=
. In particular, the PCN-domain is considered as being only one RSVP hop (f=
or Generic aggregated RSVP or e2e RSVP). This means that the next RSVP hop =
for the Aggregator in the downstream direction is the Deaggregator and the =
 next RSVP hop for the Deaggregator in the upstream direction
is the Aggregator. Furthermore, it is considered that for the determination=
 of the Deaggregator, the same methods can be used as the ones described in=
 Section 4 of [RFC4860].

>
> * How PCN interior nodes ignore RSVP messages:
> - by configuration?
> - or by the PCN-ingress switching aggregate PATH messages to IP protocol
> number RSVP-E2E-IGNORE (which isn't strictly the right name but would hav=
e
> the right effect)?
>



Georgios: We mentioned in the new version of the draft that the PCN interio=
r nodes ignore aggregated and e2e RSVP messages by configuration.



> * Error conditions, for instance when messages don't contain the expected
> objects, e.g. [draft-lefaucheur-tsvwg-rsvp-ecn-01, page 6 bullet 1].



Georgios: Please note that the PCN object is carried using the Aggregated R=
ESV message, and not the e2e RESV message, meaning that the above issue is =
not relevant.

>
> * How per-node state is maintained and the interaction with RSVP soft sta=
te
> refresh messages is not discussed. PCN-related state is unlike other RSVP
> state, in that it continually varies (it is controlled by a varying signa=
l).
> Therefore it needs to be clear that the fields of the PCN object reflect =
the
> current value when sent, not their original value, which is what an RSVP
> implementer would normally expect.



Georgios: Please note that the PCN object is carried using the Aggregated R=
ESV message, and not the e2e RESV message, meaning that the above issue is =
not relevant.

>
> =3D=3DSpecific sections=3D=3D
>
> 1. Introduction
>
> " This document, and according to [RFC4860] MAY also be used end-to-end
> directly by end-systems attached to a Diffserv network.
> "
> No. See RFC5559 for PCN applicability - there is insufficient aggregation=
 for
> PCN to work effectively e2e. The PCN applicability statement in RFC5559
> should be stated here instead: PCN is only applicable to links with
> aggregation levels where the bit-rate of the largest flow is tens of time=
s
> smaller than the smallest available link rate in the PCN region.



Georgios: We removed the paragraph pointed out above!



>
> OLD:
> In this document it is considered that the PCN-nodes MUST be able to
> support the functionality specified in [RFC5670], [RFC5559],
> [RFC6660], [RFC6661], [RFC6662].
> NEW:
> To comply with this specification, PCN-nodes MUST be able to
> support the functionality specified in [RFC5670], [RFC5559]
> [RFC6660], and either [RFC6661] or [RFC6662].



Georgios: Done!



>
> Section 2.1 first para:
> " In addition, in this document it is considered that the PCN-boundary
> nodes are able to distinguish and process (1) RSVP SESSIONS for
> generic aggregated sessions and their messages according to
> [RFC4860], (2) e2e RSVP sessions and messages according to [RFC2205].
> "
> Say how (by the addresses that the RSVP messages are addressed to).



Georgios: Done! We added text to address this point: =93In addition, to com=
ply with this specification it is considered that the PCN-boundary nodes ar=
e able to distinguish by using the addresses that the RSVP messages are add=
ressed to,=94

>
> " Furthermore, it is considered that the PCN-interior-nodes are not
> able to distinguish neither RSVP generic aggregated sessions and
> their associated messages [RFC4860], nor e2e RSVP sessions and their
> associated messages [RFC2205].
> "
> Say how (see two possibilities in 'Gaps' above). This is also not
> explained in Sections 2.1.7., 3.2 & 3.7, which are all meant to be about =
this.

Georgios: Done! We added the required information in all the mentioned plac=
es. In particular we mentioned that:

=93Furthermore, it is considered that by configuration the PCN-interior-nod=
es are not able to distinguish neither RSVP generic
aggregated sessions and their associated messages [RFC4860], nor e2e RSVP s=
essions and their associated messages [RFC2205].=94

>
> Section 2.1 bottom of p11:
> "The RSVP SESSION object for generic
> aggregate reservations is based on the RSVP SESSION object specified
> in [RFC4860] augmented with the following information:
>
> o) the IPv4 DestAddress, IPv6 DestAddress SHOULD be set to the IPv4
> or IPv6 destination addresses, respectively, of the Deaggregator
> (PCN-egress-node)
> "
> Say how - see 'Gaps' above - the whole process of RFC4860 (e2e PATH,
> e2e PathErr, aggregate PATH) finds the right address, but this needs
> to be described because in PCN the RSVP hop is across multiple IP
> nodes (the whole PCN-domain), unlike with RSVP aggregation.



Georgios: Done! We have addressed this point, see also gaps above. In the n=
ew version of the draft we replaced the above bullet with:

    o) the IPv4 DestAddress, IPv6 DestAddress MUST be set to the IPv4
       or IPv6 destination addresses, respectively, of the Deaggregator
      (PCN-egress-node), see [RFC4860]. Note that the PCN-domain is
       considered as being only one RSVP hop (for Generic aggregated
       RSVP or e2e RSVP). This means that the next RSVP hop for the
       Aggregator in the downstream direction is the Deaggregator and
       the  next RSVP hop for the Deaggregator in the upstream direction
       is the Aggregator. Furthermore, it is considered that for the
       determination of the Deaggregator, the same methods can be used
       as the ones described in Section 4 of [RFC4860].

>
> Section 2.1.2.
> " The PCN-traffic (e.g., e2e microflows) belonging to an ingress-
> egress-aggregate can be classified only at the PCN-boundary-nodes
> using the combination of (1) PCN-BA (i.e., combination of the DSCP
> and ECN fields), (2) IP addresses of the specific pair of PCN-
> boundary-nodes used by a ingress-egress-aggregate.
> [...]
> Moreover, the PCN-traffic (e.g., e2e microflows)
> belonging to a RSVP generic aggregated reservation can be classified
> only at the PCN-boundary-nodes (i.e., Aggregator and Deaggregator) by
> using the RSVP SESSION object for RSVP generic aggregated
> reservations, see [RFC4860].
> "
> Are you assuming a tunnel? You haven't said so? Otherwise the traffic
> doesn't contain the PCN-boundary-node addresses.



Georgios: Done! We added information saying that it is
   considered that tunnels need to be used between Aggregators and
   Deaggregators, using the same procedures as specified in Section 4 of
   [RFC4860].



>
> Section 2.1.8. Inter-domain Routes
>
> PCN charter scope precludes inter-domain considerations. I personally
> would happy to have discussion of inter-domain matters in here, but
> it will not be complete, because we would need to discuss security &
> integrity of PCN objects, but the PCN charter precluded that.



Georgios: Done! We changed this section as below:

The PCN-charter scope precludes inter-domain considerations. However, for s=
olving inter-domain routes changes associated with the operation of the RSV=
P messages, the same methods SHOULD be used as the ones described in [RFC48=
60] and in Section 1.4.7 of [RFC3175].



>
> Section 2.1.10. Multi-level Aggregation
> " PCN does not consider multi-level aggregations within the PCN domain.
> "
> You have referenced generic aggregate reservations throughout
> [RFC4680], rather than just aggregate reservations [RFC3175]. I
> understand the difference is that RFC4860 supports e.g. multiple
> levels of precedence. So why say we don't consider multi-level aggregatio=
n?



Georgios: Done! We replaced the old text with the following one:
PCN does not consider multi-level aggregations within the PCN domain. There=
fore, the PCN-interior-nodes are not supporting multi-level aggregation pro=
cedures. However, the Aggregator and Deaggregator SHOULD support the multi-=
level aggregation procedures specified in [RFC4860] and in Section 1.4.9 of=
 [RFC3175].



>
> Section 3.1
> " o) The e2e RSVP reservation session associated with an e2e Path
> message that arrives at the external interface of the PCN-
> ingress-node is mapped/matched onto an existing RSVP generic
> aggregation reservation state.
> "
> You haven't said how the existing aggregate is created in the first
> place (see 'Gaps' above).



Georgios: Done! See the gaps description above!



>
> Section 3.1 (twice)
> " A new error code
> "PCN-domain rejects e2e reservation" MUST be augmented to the
> RSVP error codes to inform the sender that a PCN domains rejects
> the e2e reservation request.
> "
> Disagree. The regular error code "01: Admission Control failure"
> should be used, so that end-system implementations understand that
> the call has been blocked.
> It should also use the regular "Sub-code =3D 2: Requested bandwidth
> unavailable".
>
> If the PCN-ingress uses a different code, it will imply to other RSVP
> nodes including end-systems that admission control did not fail. If
> it uses the 01 error code but a different sub-code it will imply that
> AC failed, but not because of insufficient bandwidth.
>
> PCN is one (of many) mechanisms to determine whether a reservation
> should be blocked. For other nodes, it is not relevant to describe
> the mechanism (PCN) that was used to determine that there was
> insufficient bandwidth.



Georgios: Done! We changed the above mentioned text with:
The admission or rejection procedure of a PCN-flow into the PCN-domain is d=
efined in detail in: [RFC6661] and [RFC6662].
If the Aggregator is not able to admit the e2e microflow it SHOULD then gen=
erate an e2e PathErr message using standard e2e RSVP procedures [RFC4495]. =
This e2e PathErr message is sent to the originating sender of the e2e Path =
message. The e2e RSVP error code "01: Admission Control failure" and the "S=
ub-code =3D 2: Requested bandwidth unavailable " specified in Appendix B of=
 [RFC2205] SHOULD be used for this purpose.

>
> Section 3.1
> " o) If for the same ingress-egress-aggregated and the same RSVP
> generic aggregated reservation then (1) the PCN-admission-
> state and/or (2) the state for the RSVP generic aggregated
> reservation are/is "block", the flow SHOULD NOT be
> admitted
> [...]
> The way of how the PCN-admission-state is maintained is specified in
> [RFC6661] and [RFC6662]. The way of how the RSVP generic aggregated
> reservation state is maintained is specified in [RFC4860].
> "
> As discussed in my email arguing against aggregate reservations, the
> e2e RESV message can carry an up-to-date PCN object for the
> PCN-ingress to decide whether to admit the flow signalled by the same
> message, given the PCN-ingress already handles e2e RESV messages.
> There is no need to rely on admission state determined earlier, given
> the PCN-egress already sends an e2e RESV message to the PCN-ingress
> at admission time.



Georgios: Note that using e2eRESV to carry the PCN object has severe drawba=
cks, see above and the previous emails sent by me today. Moreover, the desc=
ription that you Bob provide above, on PCN admission control is not in line=
 with what is defined in the current PCN edge behaviour drafts.



>
> Section 3.2 and 3.7 (and 2.1.7).
> Neither section says how interior nodes are arranged to ignore RSVP
> messages (see 'Gaps' earlier which suggests two possible approaches).



Georgios: Done, see Gaps description above!



>
> Section 3.8 (last sentence)
> " The address of the PCN-ingress-
> node is the one specified in the same ingress-egress-aggregate."
> I cannot work out how



Georgios: Done! We have added the following text:

It is considered that the ingress-egress-aggregate state stores both IP add=
resses of the PCN-ingress-node, i.e., Aggregator, and of the IP-egress-node=
, i.e., Deaggregator.



>
> Section 3.11
> Separation of the policy enforcement role of the PCN-ingress from a
> policy decision role (that may be off-path) will need to be added to
> the first bullet of this section (see other email).



Georgios: We disagree with this comment! We think that the description of s=
uch a policy-based admission control (PBAC) architecture is not in the scop=
e of this draft. See also my previous email sent today!
We however, tried to work out this comment by including the following text:

    =93o)  If the Decision Point is not collocated with the PCN-ingress-
        node, then other procedures need to be specified of handling the
        Aggregated Resv Message by the Aggregating router, i.e., PCN-
        ingress-node. These procedures are out of the scope of this
        document.

    o)  If the Decision point is collocated with the PCN-ingress-node,
        then the PCN-ingress-node (i.e. Aggregator) ..=94



>
> Section 3.11
> " However, based on a local policy, the Aggregator could use
> other procedures of terminating microflows.
> "
> Please delete. Policy determines /which/ flows are terminated, not
> /how/ the termination procedure works.



Georgios: Done! We tried to work out this comment by modifying the text as =
follows:
=93However, based on a local policy, the Aggregator could use other ways of=
 selecting which microflows should be terminated.=94



>
> Section 3.12
> I don't understand the purpose of this section - section 3.11 seems
> to have already said everything that section 3.12 says.



Georgios: We re-edit the section to satisfy the above comment!



>
> Section 3.13
> Say why an aggregate reservation would need to be removed:
> - no e2e reservations left in the aggregate?
> - such severe pre-congestion that every flow in the aggregated has to
> be terminated (!!!???)
>



Georgios: Done! We reedited the section to comply with this comment!

> Section 4. Protocol Elements
> " The protocol elements in this document are using the protocol
> Elements defined in [RFC4860], augmented with the following rules:
> "
> This doc uses a number of protocol elements from the base RSVP spec,
> not just the extras defined in RFC4860.
>
> BTW, protocol elements are generally called classes in RSVP documents
> (and instances of them are called objects). Also the grammar and
> capitalisation in this sentence is pretty poor.



Georgios: Please note that we used the same terms (related to protocol elem=
ents) as the ones used in RFC4860 and RFC3175.

>
> Section 4. Protocol Elements
> The first two bullets are inappropriate here and more appropriate to sect=
ion
> 3.



Georgios: These two bullets are used i this section to increase the clarity=
 of the specification!



>
> Section 4.1 PCN Object
>
> I don't see why the PCN object needs to contain the IP addresses of
> the PCN-ingress and PCN-egress. These will be in the SESSION object
> earlier in the list of RSVP objects, and RFC2205 says that the
> SESSION object defines the session for the other objects that follow.
> This also means we don't need different PCN objects for IPv4 & IPv6.



Georgios: We provided text in the new draft draft-ietf-tsvwg-rsvp-pcn-04, t=
hat emphasizes that according to [RFC6663] the report should carry the iden=
tifier of the PCN-ingress-node and the identifier of the PCN-egress-node (t=
ypically their IP addresses).
This means that the different types for PCN objects for IPv4 & IPv6 are nee=
ded.



>
> Section 4.1 PCN Object
>
> s/rate/fraction/
> I don't think you mean rate, which implies with respect to time. I
> think you mean the fraction of bytes in packets with each marking
> relative to the total bytes in PCN marked packets.



Georgios: It is rate (respect to time), please see [RFC6663] and [RFC6661] =
and [RFC6662].



>
> Section 4.1 PCN Object
>
> I suggest that the PCN object always reports the fractions of all
> three non-zero values of the PCN (aka ECN) field, even for single
> marking (SM) mode that doesn't use one of the codepoints. Then
> PCN-egress implementations and the PCN object on the wire can be the
> same for both SM & CL modes (I think), and only the ingress has to be

> different.



Georgios: Sorry, but the above description is not in line with RFC6663] and=
 [RFC6661] and [RFC6662].

>
> Section 4.1 PCN Object (and IANA Considerations)
>
> IANA need to be told the high order 2 bits of the Class-Num, to
> exploit the Unknown Class rules of [RFC2205, section 3.10]. I suggest
> the Class-Num is 10bbbbbb, so that any node outside a PCN domain that
> receives a PCN object and doesn't understand it will strip it off and
> forward the remainder of the RSVP message. Ideally we would want the
> RSVP message (with or without the PCN object) to be forwarded and an
> error message raised, but that option is not available; RSVP only
> allows an error message to be raised when it discards a whole message.



Georgios: Please note that the PCN object is carried by the Aggregated RESV=
 message. This message does not go out the PCN domain. Thus the above descr=
ibed issue is not relevant for this draft.



>
> Section 4.1 PCN Object
>
> The section defines a PCN CL Flow IDs object. It's not clear whether
> it is meant to be a different object from the PCN object, or an
> extension to it. I think it would be clearer to make it a separate
> RSVP object, although in theory a PCN-ingress could work out that a
> PCN CL Flow IDs object is included, by a calculation from the object
> length (because the base PCN object is always a fixed length).
>
> I don't see the point of the LENGTH field (for the number of flow ID
> objects), given RSVP gives the length of an object in octets, from
> which the number of flow ID objects can be derived (divide by 16 for
> IPv4 or divide by 40 for IPv6). Also RSVP objects have to align on 4
> octet boundaries.



Georgios: Please note that the PCN CL Flow IDs object is considered to be a=
 different PCN object, since its frequency and functionality is very much d=
ifferent than the frequency and functionality of the other PCN objects.
Regarding the length, I do not understand the comment, since such length fi=
eld is necessary, due to e.g., variable length of the object.



>
>
>
> =3D=3DEditorial Nits=3D=3D
>
> Globally:
> s/In this document it is considered that.../
> /To comply with this specification.../



Georgios: Done!



>
> Abstract:
> s/specifies the extensions to/
> /specifies extensions to/



Georgios: Done!



>
> 1. Intro
> s/collocated/
> /colocated/
> s/extensions to the Generic Aggregated RSVP [RFC4860] for the support of/
> /extensions to Generic Aggregated RSVP [RFC4860] for support of/



Georgios: Done!



>
> OLD
> Furthermore, this document and according to [RFC4860], in absence of
> e2e RSVP flows, a variety of policies (not defined in this document)
> can be used at the Aggregator to set the DSCP of packets passing into
> the aggregation region and how they are mapped onto generic aggregate
> reservations. These policies are not described in this document but
> are a matter of local configuration.
> NEW
> In a similar way to [RFC4860], the Aggregator can detect flows
> based on policy
> (not defined in this document) rather than using e2e RSVP flow
> signalling. Then
> it can map them onto aggregate reservations and set the DSCP of
> the packets of
> these flows as they pass into the aggregation region.



Georgios: The above mentioned paragraph is deleted completely from the draf=
t!



>
> Section 1.1. Terminology
>
> " Ingress-egress-aggregate (IEA):
> [...]
> combination of (1) fields), (2) IP addresses of the
> "
> Some text appears to be missing here.
>
> Section 1.1. Terminology
> OLD:
> t-recvFail
> An ingress-egress-aggregate timer that is used at
> The Decision point (in this document at the PCN-
> ingress-node) which when expires raises an alarm to
> management, and activates the PCN-ingress-node to
> block the admission of new PCN-flows. This timer
> expires when it value is equal to T-fail and is
> reset when a report, i.e., RSVP aggregated RESV
> message, is received for a RSVP generic aggregated
> reservation (which is matched to one
> ingress-egress-aggregate).
> NEW:
> t-recvFail
> A timer per ingress-egress-aggregate that the
> PCN-ingress-node
> sets every time it receives an RSVP RESV message for that
> ingress-egress-aggregate. When its value reaches T-fail
> it is assumed that the PCN-ingress has lost
> contact with the
> PCN-egress. Therefore the PCN-ingress blocks
> admission of new
> PCN-flows into that aggregate and raises a
> management alarm.
> REASONING:
> The order in which the clauses were written made it hard to
> understand, there was nothing to say what it measured, and it wasn't
> clear what scope was implied by "it blocks PCN-flows".



Georgios: Done! Please note that we also replaced =93RSVP RESV=94 with =93R=
SVP Aggregated RESV=94.



>
> Section 1.1 Terminology
>
> Underscores (e.g t_meas) are often used in the terminology section,
> whereas hyphens (e.g. t-meas) are used in the body text.



Georgios: Done!



>
> Section 2.1 Overview
>
> There is no Section 2.2, so all the sub-sections of 2.1.X could be promot=
ed.



Georgios: Done!



>
> Section 2.1.1
> s/used, SHOULD/used SHOULD/



Georgios: Done!



>
> Section 2.1.2.
> OLD:
> The PCN-traffic is marked using PCN-marking and is classified using
> The PCN-BA (i.e., combination of the DSCP and ECN fields).
> NEW:
> The PCN-ingress marks a PCN-BA useing PCN-marking (i.e.,
> combination of the DSCP and ECN fields), which interior nodes use to
> classify PCN-traffic.
> REASONING:
> Avoid passive verbs - ambiguous.



Georgios: Done!



>
> Section 2.1.3
> s/for the determination of/to determine the address of/

Georgios: Done!



>
> Section 2.1.4
> " o) PCN-ingress-node MUST use one or more policies to estimate whether
> an e2e RSVP reservation session associated with an e2e Path
> message that arrives at the external interface of the PCN-ingress-
> node can be mapped onto an existing RSVP generic aggregation
> reservation state.
> "
> This is a straightforward mapping function, it shouldn't involve policy.

> Also mappings are deterministic - the word estimate is wrong.



Georgios: We replaced the words =93to estimate=94 with =93to determine=94



>
> Section 3.1
> " o) If the timer t-recvFail expires [...]
> o) If the timer t-recvFail does NOT expire [...]
> "
> Switch the order of these two bullets, to describe the normal
> (successful) behaviour first.



Georgios: Done!



>
> Section 3.1
>
> s/ingress-egress-aggregated/
> /ingress-egress-aggregate/
> s/then (1)/
> /(1)



Georgios: Done!



> [However, I suggest earlier that the technical sense should be
> substantially changed, possibly making these editorial changes irrelevant=
.]
>
> Section 3.8.
> OLD:
> The PCN object is specified in
> this document and is used for the report of the data measured by
> the PCN-egress-node, for a particular ingress-egress-aggregate,
> see [RFC6661], and [RFC6662].
> NEW:
> The PCN-egress-node reports the marking probabilities it measures for
> a particular ingress-egress-aggregate in a PCN object, as specified in
> Section 4 (see also [RFC6661], and [RFC6662]).
> REASONING:
> Poor sentence order.



Georgios: Done! Re-edited!



>
> Section 3.11.
> s/associated to one ingress-egress-aggregate/
> /associated with one ingress-egress-aggregate/



Georgios: Done!



>
> Section 3.15
> Repeats Section 2.1.9. Unnecessary.



Georgios: The context of the two sections is slightly different! Therefore,=
 I would like to leave them!



>
> Section 4.
> s/by an PCN-egress node/
> /by a PCN-egress node/



Georgios: Done!



Best regards,
Georgios





--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DE81EXMBX23adutwent_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <167779B49D20F24484B717785C3F3FE9@exchange.utwente.nl>
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style>.EmailQuote {
	BORDER-LEFT: #800000 2px solid; PADDING-LEFT: 4pt; MARGIN-LEFT: 1pt
}
</style><style id=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body ocsi=3D"0" fPStyle=3D"1">
<font size=3D"2"><span style=3D"FONT-SIZE: 10pt"></span></font>
<div style=3D"FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZ=
E: 10pt">
<p>Hi Bob,</p>
<p>&nbsp;</p>
<p>Thanks for your comments!<br>
Please see in line!</p>
<p>&nbsp;</p>
<p>&gt; -----Original Message-----<br>
&gt; From: Bob Briscoe [mailto:bob.briscoe@bt.com]<br>
&gt; Sent: donderdag 15 november 2012 22:35<br>
&gt; To: Karagiannis, G. (EWI); Anurag Bhargava (anuragb)<br>
&gt; Cc: <a href=3D"mailto:pcn@ietf.org" target=3D"_blank">pcn@ietf.org</a>=
; <a href=3D"mailto:tsvwg@ietf.org" target=3D"_blank">
tsvwg@ietf.org</a>; <a href=3D"mailto:rsvp-dir@ietfa.amsl.com" target=3D"_b=
lank">rsvp-dir@ietfa.amsl.com</a><br>
&gt; Subject: Re: [PCN] FW: New Version Notification - draft-ietf-tsvwg-rsv=
p-pcn-<br>
&gt; 03.txt<br>
&gt; <br>
&gt; Georgios &amp; Anurag,<br>
&gt; <br>
&gt; Thank you for this draft. Below is my review, as:<br>
&gt; - a member of the RSVP directorate<br>
&gt; - one of the PCN design team<br>
&gt; - a co-author of draft-lefaucheur-rsvp-ecn, on which this draft is bas=
ed.<br>
&gt; <br>
&gt; I have already sent my main technical concerns in two separate emails,=
<br>
&gt; summarised below (but I suggest we use the separate threads to discuss=
):<br>
&gt; <br>
&gt; 1. It would be easy to allow for an off-path policy-decision point (PD=
P), as per<br>
&gt; RFC2753 (policy-based admission control (PBAC) framework)</p>
<p>Georgios: I replied to your above proposal in a previous email!<br>
&gt; <br>
&gt; 2. PCN already reduces reservation state and processing to nothing on<=
br>
&gt; interior nodes. Adding aggregate reservations to PCN adds 3 disadvanta=
ges<br>
&gt; and no advantages:<br>
&gt; - it requires more processing and state in interior nodes and boundary=
-<br>
&gt; nodes<br>
&gt; - it unnecessarily pins routes to interior nodes and<br>
&gt; - it adds unnecessary latency.</p>
<p>&nbsp;</p>
<p>Georgios: I answered to the thread mentioned above in a previous email s=
ent today! However, I would like to again emphasize that I strongly agree w=
ith the analysis done by Francois (together with my additional email) in th=
e following email on the two options
 of accomplishing RSVP over PCN signaling support:<br>
<a href=3D"http://www.ietf.org/mail-archive/web/tsvwg/current/msg11601.html=
" target=3D"_blank">http://www.ietf.org/mail-archive/web/tsvwg/current/msg1=
1601.html</a><br>
<a href=3D"http://www.ietf.org/mail-archive/web/tsvwg/current/msg11602.html=
" target=3D"_blank">http://www.ietf.org/mail-archive/web/tsvwg/current/msg1=
1602.html</a></p>
<p>In addition to that, we agree with the proposal of Francois of choosing =
option (A)&nbsp; since the RFC4860 operations has been thought through and =
there has been some implementation of RSVP Aggregation, so we have some con=
fidence that the solution can deal with
 the more challenging situations (rerouting in core, failure of an ingress =
edge, failure of an egress edge, rerouting towards a different edge,=85).</=
p>
<p>Therefore, we have used the argumentation provided by Francois in Sectio=
n 1.2 of (new draft version) draft-ietf-tsvwg-rsvp-pcn-04 to justify why RF=
C4860 should be used to accomplish the RSVP over PCN signaling support.</p>
<p><br>
&gt; <br>
&gt; This email reviews comprehensibility and raises a large number of less=
er<br>
&gt; technical concerns (26 to be precise), as well as editorial nits (many=
 of which<br>
&gt; may be irrelevant if I'm right about the major technical concerns).<br=
>
&gt; <br>
&gt; =3D=3DGeneral style=3D=3D<br>
&gt; I didn't find the style useful at all. Sections 1, 2 &amp; 3 defer eve=
rything<br>
&gt; meaningful into pointers to other RFCs. This makes it incomprehensible=
,<br>
&gt; even if you know all the references intimately.<br>
&gt; Lixia's suggestion that you refer to the specific sections of other RF=
Cs won't<br>
&gt; be enough.<br>
&gt; <br>
&gt; An RFC should be understandable without re-reading its references (rea=
ders<br>
&gt; should have read them, but they shouldn't be expected to remember ever=
y<br>
&gt; detail).</p>
<p>&nbsp;</p>
<p>Georgios: We have severely restructured the (new draft) draft-ietf-tsvwg=
-rsvp-pcn-04. We believe that the above comment has been worked out!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; I have to say we are moving very slowly, and backwards. When Francois =
Le<br>
&gt; Faucheur first wrote the ancestor to this draft (7 years ago!), I coul=
d<br>
&gt; understand it immediately, and in half the pages it covered nearly eve=
rything<br>
&gt; in this draft and covered the gaps I have listed below. [In the intere=
sts of full<br>
&gt; disclosure: I became a co-author of draft-lefaucheur-tsvwg-rsvp-ecn-00=
,<br>
&gt; nonetheless Francois's pre-00 draft was more comprehensible and comple=
te<br>
&gt; than this one, even before the co-authors did the first reviews.]</p>
<p>Georgios: I do not agree! Note that draft-lefaucheur-tsvwg-rsvp-ecn-00 d=
oes not follow the PCN signaling requirements defined in [RFC6663] and it d=
oes not how it can support the PCN edge behaviors as specified in [RFC6661]=
 and [RFC6662]. While draft-ietf-tsvwg-rsvp-pcn-04
 certainly does this.</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; This draft says very little itself, but ends up much longer. For examp=
le Section<br>
&gt; 3 tediously repeats content-free text like:<br>
&gt; &quot;&lt;Title&gt;<br>
&gt; In this document it is considered that for &lt;Title&gt; the same meth=
ods can be<br>
&gt; used as the ones described in &lt;reference&gt;&quot;.<br>
&gt; <br>
&gt; Not only section 3; sections 1 &amp; 2 also rely wholly on references,=
 making<br>
&gt; them just as incomprehensible. I also agree with the other reviewers'<=
br>
&gt; suggestions to focus the introduction initially on what this draft add=
s, and<br>
&gt; move the background material after that.<br>
&gt; <br>
&gt; In summary: avoid phrases like &quot;the same methods as&quot; or &quo=
t;standard RSVP<br>
&gt; aggregation [...] procedures are used&quot;. Instead just say directly=
 how it works.</p>
<p>&nbsp;</p>
<p>Georgios: We have severely restructured and re-edited the (new draft) dr=
aft-ietf-tsvwg-rsvp-pcn-04. We believe that the above comment has been work=
ed out!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; <br>
&gt; =3D=3DNormative &amp; Technical Points=3D=3D<br>
&gt; <br>
&gt; =3D=3DGaps=3D=3D<br>
&gt; <br>
&gt; * How an aggregate reservation is created vs. how one is used if it is=
 already<br>
&gt; present</p>
<p>&nbsp;</p>
<p>Georgios: Done: Added the following text in Section 2.1 to address this =
issue:<br>
=93The procedures for aggregation of E2E reservations over generic aggregat=
e RSVP reservations are the same as the procedures specified in Section 4 o=
f [RFC4860].
</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; * How next hop addresses are discovered (a PCN domain is only one RSVP=
<br>
&gt; hop unlike with RSVP aggregation, so although the process is similar, =
this<br>
&gt; needs to be described explicitly)</p>
<p>&nbsp;</p>
<p>Georgios: This is explained in the (new draft) draft-ietf-tsvwg-rsvp-pcn=
-04. In particular, the PCN-domain is considered as being only one RSVP hop=
 (for Generic aggregated RSVP or e2e RSVP). This means that the next RSVP h=
op for the Aggregator in the downstream
 direction is the Deaggregator and the&nbsp; next RSVP hop for the Deaggreg=
ator in the upstream direction
<br>
is the Aggregator. Furthermore, it is considered that for the determination=
 of the Deaggregator, the same methods can be used as the ones described in=
 Section 4 of [RFC4860].&nbsp;
</p>
<p><br>
&gt; <br>
&gt; * How PCN interior nodes ignore RSVP messages:<br>
&gt; - by configuration?<br>
&gt; - or by the PCN-ingress switching aggregate PATH messages to IP protoc=
ol<br>
&gt; number RSVP-E2E-IGNORE (which isn't strictly the right name but would =
have<br>
&gt; the right effect)?<br>
&gt; </p>
<p>&nbsp;</p>
<p>Georgios: We mentioned in the new version of the draft that the PCN inte=
rior nodes ignore aggregated and e2e RSVP messages by configuration.
</p>
<p>&nbsp;</p>
<p>&gt; * Error conditions, for instance when messages don't contain the ex=
pected<br>
&gt; objects, e.g. [draft-lefaucheur-tsvwg-rsvp-ecn-01, page 6 bullet 1].</=
p>
<p>&nbsp;</p>
<p>Georgios: Please note that the PCN object is carried using the Aggregate=
d RESV message, and not the e2e RESV message, meaning that the above issue =
is not relevant.
</p>
<p><br>
&gt; <br>
&gt; * How per-node state is maintained and the interaction with RSVP soft =
state<br>
&gt; refresh messages is not discussed. PCN-related state is unlike other R=
SVP<br>
&gt; state, in that it continually varies (it is controlled by a varying si=
gnal).<br>
&gt; Therefore it needs to be clear that the fields of the PCN object refle=
ct the<br>
&gt; current value when sent, not their original value, which is what an RS=
VP<br>
&gt; implementer would normally expect.</p>
<p>&nbsp;</p>
<p>Georgios: Please note that the PCN object is carried using the Aggregate=
d RESV message, and not the e2e RESV message, meaning that the above issue =
is not relevant.</p>
<p><br>
&gt; <br>
&gt; =3D=3DSpecific sections=3D=3D<br>
&gt; <br>
&gt; 1. Introduction<br>
&gt; <br>
&gt; &quot; This document, and according to [RFC4860] MAY also be used end-=
to-end<br>
&gt; directly by end-systems attached to a Diffserv network.<br>
&gt; &quot;<br>
&gt; No. See RFC5559 for PCN applicability - there is insufficient aggregat=
ion for<br>
&gt; PCN to work effectively e2e. The PCN applicability statement in RFC555=
9<br>
&gt; should be stated here instead: PCN is only applicable to links with<br=
>
&gt; aggregation levels where the bit-rate of the largest flow is tens of t=
imes<br>
&gt; smaller than the smallest available link rate in the PCN region.</p>
<p>&nbsp;</p>
<p>Georgios: We removed the paragraph pointed out above!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; OLD:<br>
&gt; In this document it is considered that the PCN-nodes MUST be able to<b=
r>
&gt; support the functionality specified in [RFC5670], [RFC5559],<br>
&gt; [RFC6660], [RFC6661], [RFC6662].<br>
&gt; NEW:<br>
&gt; To comply with this specification, PCN-nodes MUST be able to<br>
&gt; support the functionality specified in [RFC5670], [RFC5559]<br>
&gt; [RFC6660], and either [RFC6661] or [RFC6662].</p>
<p>&nbsp;</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 2.1 first para:<br>
&gt; &quot; In addition, in this document it is considered that the PCN-bou=
ndary<br>
&gt; nodes are able to distinguish and process (1) RSVP SESSIONS for<br>
&gt; generic aggregated sessions and their messages according to<br>
&gt; [RFC4860], (2) e2e RSVP sessions and messages according to [RFC2205].<=
br>
&gt; &quot;<br>
&gt; Say how (by the addresses that the RSVP messages are addressed to).</p=
>
<p>&nbsp;</p>
<p>Georgios: Done! We added text to address this point: =93In addition, to =
comply with this specification it is considered that the PCN-boundary nodes=
 are able to distinguish by using the addresses that the RSVP messages are =
addressed to,=94</p>
<p><br>
&gt; <br>
&gt; &quot; Furthermore, it is considered that the PCN-interior-nodes are n=
ot<br>
&gt; able to distinguish neither RSVP generic aggregated sessions and<br>
&gt; their associated messages [RFC4860], nor e2e RSVP sessions and their<b=
r>
&gt; associated messages [RFC2205].<br>
&gt; &quot;<br>
&gt; Say how (see two possibilities in 'Gaps' above). This is also not<br>
&gt; explained in Sections 2.1.7., 3.2 &amp; 3.7, which are all meant to be=
 about this.</p>
<p><br>
Georgios: Done! We added the required information in all the mentioned plac=
es. In particular we mentioned that:</p>
<p>=93Furthermore, it is considered that by configuration the PCN-interior-=
nodes are not able to distinguish neither RSVP generic
<br>
aggregated sessions and their associated messages [RFC4860], nor e2e RSVP s=
essions and their associated messages [RFC2205].=94</p>
<p><br>
&gt; <br>
&gt; Section 2.1 bottom of p11:<br>
&gt; &quot;The RSVP SESSION object for generic<br>
&gt; aggregate reservations is based on the RSVP SESSION object specified<b=
r>
&gt; in [RFC4860] augmented with the following information:<br>
&gt; <br>
&gt; o) the IPv4 DestAddress, IPv6 DestAddress SHOULD be set to the IPv4<br=
>
&gt; or IPv6 destination addresses, respectively, of the Deaggregator<br>
&gt; (PCN-egress-node)<br>
&gt; &quot;<br>
&gt; Say how - see 'Gaps' above - the whole process of RFC4860 (e2e PATH,<b=
r>
&gt; e2e PathErr, aggregate PATH) finds the right address, but this needs<b=
r>
&gt; to be described because in PCN the RSVP hop is across multiple IP<br>
&gt; nodes (the whole PCN-domain), unlike with RSVP aggregation.</p>
<p>&nbsp;</p>
<p>Georgios: Done! We have addressed this point, see also gaps above. In th=
e new version of the draft we replaced the above bullet with:</p>
<p>&nbsp;&nbsp;&nbsp; o) the IPv4 DestAddress, IPv6 DestAddress MUST be set=
 to the IPv4 <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or IPv6 destination addresses, respect=
ively, of the Deaggregator <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (PCN-egress-node), see [RFC4860]. Note that =
the PCN-domain is <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; considered as being only one RSVP hop =
(for Generic aggregated <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RSVP or e2e RSVP). This means that the=
 next RSVP hop for the <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Aggregator in the downstream direction=
 is the Deaggregator and <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the&nbsp; next RSVP hop for the Deaggr=
egator in the upstream direction <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is the Aggregator. Furthermore, it is =
considered that for the <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; determination of the Deaggregator, the=
 same methods can be used <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; as the ones described in Section 4 of =
[RFC4860].&nbsp; </p>
<p><br>
&gt; <br>
&gt; Section 2.1.2.<br>
&gt; &quot; The PCN-traffic (e.g., e2e microflows) belonging to an ingress-=
<br>
&gt; egress-aggregate can be classified only at the PCN-boundary-nodes<br>
&gt; using the combination of (1) PCN-BA (i.e., combination of the DSCP<br>
&gt; and ECN fields), (2) IP addresses of the specific pair of PCN-<br>
&gt; boundary-nodes used by a ingress-egress-aggregate.<br>
&gt; [...]<br>
&gt; Moreover, the PCN-traffic (e.g., e2e microflows)<br>
&gt; belonging to a RSVP generic aggregated reservation can be classified<b=
r>
&gt; only at the PCN-boundary-nodes (i.e., Aggregator and Deaggregator) by<=
br>
&gt; using the RSVP SESSION object for RSVP generic aggregated<br>
&gt; reservations, see [RFC4860].<br>
&gt; &quot;<br>
&gt; Are you assuming a tunnel? You haven't said so? Otherwise the traffic<=
br>
&gt; doesn't contain the PCN-boundary-node addresses.</p>
<p>&nbsp;</p>
<p>Georgios: Done! We added information saying that it is <br>
&nbsp;&nbsp; considered that tunnels need to be used between Aggregators an=
d&nbsp; <br>
&nbsp;&nbsp; Deaggregators, using the same procedures as specified in Secti=
on 4 of <br>
&nbsp;&nbsp; [RFC4860].</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 2.1.8. Inter-domain Routes<br>
&gt; <br>
&gt; PCN charter scope precludes inter-domain considerations. I personally<=
br>
&gt; would happy to have discussion of inter-domain matters in here, but<br=
>
&gt; it will not be complete, because we would need to discuss security &am=
p;<br>
&gt; integrity of PCN objects, but the PCN charter precluded that.</p>
<p>&nbsp;</p>
<p>Georgios: Done! We changed this section as below:</p>
<p>The PCN-charter scope precludes inter-domain considerations. However, fo=
r solving inter-domain routes changes associated with the operation of the =
RSVP messages, the same methods SHOULD be used as the ones described in [RF=
C4860] and in Section 1.4.7 of [RFC3175].
</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 2.1.10. Multi-level Aggregation<br>
&gt; &quot; PCN does not consider multi-level aggregations within the PCN d=
omain.<br>
&gt; &quot;<br>
&gt; You have referenced generic aggregate reservations throughout<br>
&gt; [RFC4680], rather than just aggregate reservations [RFC3175]. I<br>
&gt; understand the difference is that RFC4860 supports e.g. multiple<br>
&gt; levels of precedence. So why say we don't consider multi-level aggrega=
tion?</p>
<p>&nbsp;</p>
<p>Georgios: Done! We replaced the old text with the following one:<br>
PCN does not consider multi-level aggregations within the PCN domain. There=
fore, the PCN-interior-nodes are not supporting multi-level aggregation pro=
cedures. However, the Aggregator and Deaggregator SHOULD support the multi-=
level aggregation procedures specified
 in [RFC4860] and in Section 1.4.9 of [RFC3175]. </p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 3.1<br>
&gt; &quot; o) The e2e RSVP reservation session associated with an e2e Path=
<br>
&gt; message that arrives at the external interface of the PCN-<br>
&gt; ingress-node is mapped/matched onto an existing RSVP generic<br>
&gt; aggregation reservation state.<br>
&gt; &quot;<br>
&gt; You haven't said how the existing aggregate is created in the first<br=
>
&gt; place (see 'Gaps' above).</p>
<p>&nbsp;</p>
<p>Georgios: Done! See the gaps description above!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 3.1 (twice)<br>
&gt; &quot; A new error code<br>
&gt; &quot;PCN-domain rejects e2e reservation&quot; MUST be augmented to th=
e<br>
&gt; RSVP error codes to inform the sender that a PCN domains rejects<br>
&gt; the e2e reservation request.<br>
&gt; &quot;<br>
&gt; Disagree. The regular error code &quot;01: Admission Control failure&q=
uot;<br>
&gt; should be used, so that end-system implementations understand that<br>
&gt; the call has been blocked.<br>
&gt; It should also use the regular &quot;Sub-code =3D 2: Requested bandwid=
th<br>
&gt; unavailable&quot;.<br>
&gt; <br>
&gt; If the PCN-ingress uses a different code, it will imply to other RSVP<=
br>
&gt; nodes including end-systems that admission control did not fail. If<br=
>
&gt; it uses the 01 error code but a different sub-code it will imply that<=
br>
&gt; AC failed, but not because of insufficient bandwidth.<br>
&gt; <br>
&gt; PCN is one (of many) mechanisms to determine whether a reservation<br>
&gt; should be blocked. For other nodes, it is not relevant to describe<br>
&gt; the mechanism (PCN) that was used to determine that there was<br>
&gt; insufficient bandwidth.</p>
<p>&nbsp;</p>
<p>Georgios: Done! We changed the above mentioned text with:<br>
The admission or rejection procedure of a PCN-flow into the PCN-domain is d=
efined in detail in: [RFC6661] and [RFC6662].
<br>
If the Aggregator is not able to admit the e2e microflow it SHOULD then gen=
erate an e2e PathErr message using standard e2e RSVP procedures [RFC4495]. =
This e2e PathErr message is sent to the originating sender of the e2e Path =
message. The e2e RSVP error code
 &quot;01: Admission Control failure&quot; and the &quot;Sub-code =3D 2: Re=
quested bandwidth unavailable &quot; specified in Appendix B of [RFC2205] S=
HOULD be used for this purpose.
</p>
<p><br>
&gt; <br>
&gt; Section 3.1<br>
&gt; &quot; o) If for the same ingress-egress-aggregated and the same RSVP<=
br>
&gt; generic aggregated reservation then (1) the PCN-admission-<br>
&gt; state and/or (2) the state for the RSVP generic aggregated<br>
&gt; reservation are/is &quot;block&quot;, the flow SHOULD NOT be<br>
&gt; admitted<br>
&gt; [...]<br>
&gt; The way of how the PCN-admission-state is maintained is specified in<b=
r>
&gt; [RFC6661] and [RFC6662]. The way of how the RSVP generic aggregated<br=
>
&gt; reservation state is maintained is specified in [RFC4860].<br>
&gt; &quot;<br>
&gt; As discussed in my email arguing against aggregate reservations, the<b=
r>
&gt; e2e RESV message can carry an up-to-date PCN object for the<br>
&gt; PCN-ingress to decide whether to admit the flow signalled by the same<=
br>
&gt; message, given the PCN-ingress already handles e2e RESV messages.<br>
&gt; There is no need to rely on admission state determined earlier, given<=
br>
&gt; the PCN-egress already sends an e2e RESV message to the PCN-ingress<br=
>
&gt; at admission time.</p>
<p>&nbsp;</p>
<p>Georgios: Note that using e2eRESV to carry the PCN object has severe dra=
wbacks, see above and the previous emails sent by me today. Moreover, the d=
escription that you Bob provide above, on PCN admission control is not in l=
ine with what is defined in the
 current PCN edge behaviour drafts.</p>
<p>&nbsp;</p>
<p><br>
&gt; <br>
&gt; Section 3.2 and 3.7 (and 2.1.7).<br>
&gt; Neither section says how interior nodes are arranged to ignore RSVP<br=
>
&gt; messages (see 'Gaps' earlier which suggests two possible approaches).<=
/p>
<p>&nbsp;</p>
<p>Georgios: Done, see Gaps description above!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 3.8 (last sentence)<br>
&gt; &quot; The address of the PCN-ingress-<br>
&gt; node is the one specified in the same ingress-egress-aggregate.&quot;<=
br>
&gt; I cannot work out how</p>
<p>&nbsp;</p>
<p>Georgios: Done! We have added the following text:</p>
<p>It is considered that the ingress-egress-aggregate state stores both IP =
addresses of the PCN-ingress-node, i.e., Aggregator, and of the IP-egress-n=
ode, i.e., Deaggregator.</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 3.11<br>
&gt; Separation of the policy enforcement role of the PCN-ingress from a<br=
>
&gt; policy decision role (that may be off-path) will need to be added to<b=
r>
&gt; the first bullet of this section (see other email).</p>
<p>&nbsp;</p>
<p>Georgios: We disagree with this comment! We think that the description o=
f such a policy-based admission control (PBAC) architecture is not in the s=
cope of this draft. See also my previous email sent today!<br>
We however, tried to work out this comment by including the following text:=
</p>
<p>&nbsp;&nbsp;&nbsp; =93o)&nbsp; If the Decision Point is not collocated w=
ith the PCN-ingress-<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; node, then other procedures need=
 to be specified of handling the <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Aggregated Resv Message by the A=
ggregating router, i.e., PCN-<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ingress-node. These procedures a=
re out of the scope of this <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; document.</p>
<p>&nbsp;&nbsp;&nbsp; o)&nbsp; If the Decision point is collocated with the=
 PCN-ingress-node, <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; then the PCN-ingress-node (i.e. =
Aggregator) ..=94&nbsp; </p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 3.11<br>
&gt; &quot; However, based on a local policy, the Aggregator could use<br>
&gt; other procedures of terminating microflows.<br>
&gt; &quot;<br>
&gt; Please delete. Policy determines /which/ flows are terminated, not<br>
&gt; /how/ the termination procedure works.</p>
<p>&nbsp;</p>
<p>Georgios: Done! We tried to work out this comment by modifying the text =
as follows:<br>
=93However, based on a local policy, the Aggregator could use other ways of=
 selecting which microflows should be terminated.=94</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 3.12<br>
&gt; I don't understand the purpose of this section - section 3.11 seems<br=
>
&gt; to have already said everything that section 3.12 says.</p>
<p>&nbsp;</p>
<p>Georgios: We re-edit the section to satisfy the above comment!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 3.13<br>
&gt; Say why an aggregate reservation would need to be removed:<br>
&gt; - no e2e reservations left in the aggregate?<br>
&gt; - such severe pre-congestion that every flow in the aggregated has to<=
br>
&gt; be terminated (!!!???)<br>
&gt; </p>
<p>&nbsp;</p>
<p>Georgios: Done! We reedited the section to comply with this comment!</p>
<p><br>
&gt; Section 4. Protocol Elements<br>
&gt; &quot; The protocol elements in this document are using the protocol<b=
r>
&gt; Elements defined in [RFC4860], augmented with the following rules:<br>
&gt; &quot;<br>
&gt; This doc uses a number of protocol elements from the base RSVP spec,<b=
r>
&gt; not just the extras defined in RFC4860.<br>
&gt; <br>
&gt; BTW, protocol elements are generally called classes in RSVP documents<=
br>
&gt; (and instances of them are called objects). Also the grammar and<br>
&gt; capitalisation in this sentence is pretty poor.</p>
<p>&nbsp;</p>
<p>Georgios: Please note that we used the same terms (related to protocol e=
lements) as the ones used in RFC4860 and RFC3175.</p>
<p><br>
&gt; <br>
&gt; Section 4. Protocol Elements<br>
&gt; The first two bullets are inappropriate here and more appropriate to s=
ection<br>
&gt; 3.</p>
<p>&nbsp;</p>
<p>Georgios: These two bullets are used i this section to increase the clar=
ity of the specification!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 4.1 PCN Object<br>
&gt; <br>
&gt; I don't see why the PCN object needs to contain the IP addresses of<br=
>
&gt; the PCN-ingress and PCN-egress. These will be in the SESSION object<br=
>
&gt; earlier in the list of RSVP objects, and RFC2205 says that the<br>
&gt; SESSION object defines the session for the other objects that follow.<=
br>
&gt; This also means we don't need different PCN objects for IPv4 &amp; IPv=
6.</p>
<p>&nbsp;</p>
<p>Georgios: We provided text in the new draft draft-ietf-tsvwg-rsvp-pcn-04=
, that emphasizes that according to [RFC6663] the report should carry the i=
dentifier of the PCN-ingress-node and the identifier of the PCN-egress-node=
 (typically their IP addresses).<br>
This means that the different types for PCN objects for IPv4 &amp; IPv6 are=
 needed.</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 4.1 PCN Object<br>
&gt; <br>
&gt; s/rate/fraction/<br>
&gt; I don't think you mean rate, which implies with respect to time. I<br>
&gt; think you mean the fraction of bytes in packets with each marking<br>
&gt; relative to the total bytes in PCN marked packets.</p>
<p>&nbsp;</p>
<p>Georgios: It is rate (respect to time), please see [RFC6663] and [RFC666=
1] and [RFC6662].</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 4.1 PCN Object<br>
&gt; <br>
&gt; I suggest that the PCN object always reports the fractions of all<br>
&gt; three non-zero values of the PCN (aka ECN) field, even for single<br>
&gt; marking (SM) mode that doesn't use one of the codepoints. Then<br>
&gt; PCN-egress implementations and the PCN object on the wire can be the<b=
r>
&gt; same for both SM &amp; CL modes (I think), and only the ingress has to=
 be</p>
<p>&gt; different.</p>
<p>&nbsp;</p>
<p>Georgios: Sorry, but the above description is not in line with RFC6663] =
and [RFC6661] and [RFC6662].</p>
<p><br>
&gt; <br>
&gt; Section 4.1 PCN Object (and IANA Considerations)<br>
&gt; <br>
&gt; IANA need to be told the high order 2 bits of the Class-Num, to<br>
&gt; exploit the Unknown Class rules of [RFC2205, section 3.10]. I suggest<=
br>
&gt; the Class-Num is 10bbbbbb, so that any node outside a PCN domain that<=
br>
&gt; receives a PCN object and doesn't understand it will strip it off and<=
br>
&gt; forward the remainder of the RSVP message. Ideally we would want the<b=
r>
&gt; RSVP message (with or without the PCN object) to be forwarded and an<b=
r>
&gt; error message raised, but that option is not available; RSVP only<br>
&gt; allows an error message to be raised when it discards a whole message.=
</p>
<p>&nbsp;</p>
<p>Georgios: Please note that the PCN object is carried by the Aggregated R=
ESV message. This message does not go out the PCN domain. Thus the above de=
scribed issue is not relevant for this draft.</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 4.1 PCN Object<br>
&gt; <br>
&gt; The section defines a PCN CL Flow IDs object. It's not clear whether<b=
r>
&gt; it is meant to be a different object from the PCN object, or an<br>
&gt; extension to it. I think it would be clearer to make it a separate<br>
&gt; RSVP object, although in theory a PCN-ingress could work out that a<br=
>
&gt; PCN CL Flow IDs object is included, by a calculation from the object<b=
r>
&gt; length (because the base PCN object is always a fixed length).<br>
&gt; <br>
&gt; I don't see the point of the LENGTH field (for the number of flow ID<b=
r>
&gt; objects), given RSVP gives the length of an object in octets, from<br>
&gt; which the number of flow ID objects can be derived (divide by 16 for<b=
r>
&gt; IPv4 or divide by 40 for IPv6). Also RSVP objects have to align on 4<b=
r>
&gt; octet boundaries.</p>
<p>&nbsp;</p>
<p>Georgios: Please note that the PCN CL Flow IDs object is considered to b=
e a different PCN object, since its frequency and functionality is very muc=
h different than the frequency and functionality of the other PCN objects.
<br>
Regarding the length, I do not understand the comment, since such length fi=
eld is necessary, due to e.g., variable length of the object.</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; <br>
&gt; <br>
&gt; =3D=3DEditorial Nits=3D=3D<br>
&gt; <br>
&gt; Globally:<br>
&gt; s/In this document it is considered that.../<br>
&gt; /To comply with this specification.../</p>
<p>&nbsp;</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Abstract:<br>
&gt; s/specifies the extensions to/<br>
&gt; /specifies extensions to/</p>
<p>&nbsp;</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; 1. Intro<br>
&gt; s/collocated/<br>
&gt; /colocated/<br>
&gt; s/extensions to the Generic Aggregated RSVP [RFC4860] for the support =
of/<br>
&gt; /extensions to Generic Aggregated RSVP [RFC4860] for support of/</p>
<p>&nbsp;</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; OLD<br>
&gt; Furthermore, this document and according to [RFC4860], in absence of<b=
r>
&gt; e2e RSVP flows, a variety of policies (not defined in this document)<b=
r>
&gt; can be used at the Aggregator to set the DSCP of packets passing into<=
br>
&gt; the aggregation region and how they are mapped onto generic aggregate<=
br>
&gt; reservations. These policies are not described in this document but<br=
>
&gt; are a matter of local configuration.<br>
&gt; NEW<br>
&gt; In a similar way to [RFC4860], the Aggregator can detect flows<br>
&gt; based on policy<br>
&gt; (not defined in this document) rather than using e2e RSVP flow<br>
&gt; signalling. Then<br>
&gt; it can map them onto aggregate reservations and set the DSCP of<br>
&gt; the packets of<br>
&gt; these flows as they pass into the aggregation region.</p>
<p>&nbsp;</p>
<p>Georgios: The above mentioned paragraph is deleted completely from the d=
raft!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 1.1. Terminology<br>
&gt; <br>
&gt; &quot; Ingress-egress-aggregate (IEA):<br>
&gt; [...]<br>
&gt; combination of (1) fields), (2) IP addresses of the<br>
&gt; &quot;<br>
&gt; Some text appears to be missing here.<br>
&gt; <br>
&gt; Section 1.1. Terminology<br>
&gt; OLD:<br>
&gt; t-recvFail<br>
&gt; An ingress-egress-aggregate timer that is used at<br>
&gt; The Decision point (in this document at the PCN-<br>
&gt; ingress-node) which when expires raises an alarm to<br>
&gt; management, and activates the PCN-ingress-node to<br>
&gt; block the admission of new PCN-flows. This timer<br>
&gt; expires when it value is equal to T-fail and is<br>
&gt; reset when a report, i.e., RSVP aggregated RESV<br>
&gt; message, is received for a RSVP generic aggregated<br>
&gt; reservation (which is matched to one<br>
&gt; ingress-egress-aggregate).<br>
&gt; NEW:<br>
&gt; t-recvFail<br>
&gt; A timer per ingress-egress-aggregate that the<br>
&gt; PCN-ingress-node<br>
&gt; sets every time it receives an RSVP RESV message for that<br>
&gt; ingress-egress-aggregate. When its value reaches T-fail<br>
&gt; it is assumed that the PCN-ingress has lost<br>
&gt; contact with the<br>
&gt; PCN-egress. Therefore the PCN-ingress blocks<br>
&gt; admission of new<br>
&gt; PCN-flows into that aggregate and raises a<br>
&gt; management alarm.<br>
&gt; REASONING:<br>
&gt; The order in which the clauses were written made it hard to<br>
&gt; understand, there was nothing to say what it measured, and it wasn't<b=
r>
&gt; clear what scope was implied by &quot;it blocks PCN-flows&quot;.</p>
<p>&nbsp;</p>
<p>Georgios: Done! Please note that we also replaced =93RSVP RESV=94 with =
=93RSVP Aggregated RESV=94.</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 1.1 Terminology<br>
&gt; <br>
&gt; Underscores (e.g t_meas) are often used in the terminology section,<br=
>
&gt; whereas hyphens (e.g. t-meas) are used in the body text.</p>
<p>&nbsp;</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 2.1 Overview<br>
&gt; <br>
&gt; There is no Section 2.2, so all the sub-sections of 2.1.X could be pro=
moted.</p>
<p>&nbsp;</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 2.1.1<br>
&gt; s/used, SHOULD/used SHOULD/</p>
<p>&nbsp;</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 2.1.2.<br>
&gt; OLD:<br>
&gt; The PCN-traffic is marked using PCN-marking and is classified using<br=
>
&gt; The PCN-BA (i.e., combination of the DSCP and ECN fields).<br>
&gt; NEW:<br>
&gt; The PCN-ingress marks a PCN-BA useing PCN-marking (i.e.,<br>
&gt; combination of the DSCP and ECN fields), which interior nodes use to<b=
r>
&gt; classify PCN-traffic.<br>
&gt; REASONING:<br>
&gt; Avoid passive verbs - ambiguous.</p>
<p>&nbsp;</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 2.1.3<br>
&gt; s/for the determination of/to determine the address of/<br>
</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 2.1.4<br>
&gt; &quot; o) PCN-ingress-node MUST use one or more policies to estimate w=
hether<br>
&gt; an e2e RSVP reservation session associated with an e2e Path<br>
&gt; message that arrives at the external interface of the PCN-ingress-<br>
&gt; node can be mapped onto an existing RSVP generic aggregation<br>
&gt; reservation state.<br>
&gt; &quot;<br>
&gt; This is a straightforward mapping function, it shouldn't involve polic=
y.</p>
<p>&gt; Also mappings are deterministic - the word estimate is wrong.</p>
<p>&nbsp;</p>
<p>Georgios: We replaced the words =93to estimate=94 with =93to determine=
=94</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 3.1<br>
&gt; &quot; o) If the timer t-recvFail expires [...]<br>
&gt; o) If the timer t-recvFail does NOT expire [...]<br>
&gt; &quot;<br>
&gt; Switch the order of these two bullets, to describe the normal<br>
&gt; (successful) behaviour first.</p>
<p>&nbsp;</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 3.1<br>
&gt; <br>
&gt; s/ingress-egress-aggregated/<br>
&gt; /ingress-egress-aggregate/<br>
&gt; s/then (1)/<br>
&gt; /(1)</p>
<p>&nbsp;</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; [However, I suggest earlier that the technical sense should be<br>
&gt; substantially changed, possibly making these editorial changes irrelev=
ant.]<br>
&gt; <br>
&gt; Section 3.8.<br>
&gt; OLD:<br>
&gt; The PCN object is specified in<br>
&gt; this document and is used for the report of the data measured by<br>
&gt; the PCN-egress-node, for a particular ingress-egress-aggregate,<br>
&gt; see [RFC6661], and [RFC6662].<br>
&gt; NEW:<br>
&gt; The PCN-egress-node reports the marking probabilities it measures for<=
br>
&gt; a particular ingress-egress-aggregate in a PCN object, as specified in=
<br>
&gt; Section 4 (see also [RFC6661], and [RFC6662]).<br>
&gt; REASONING:<br>
&gt; Poor sentence order.</p>
<p>&nbsp;</p>
<p>Georgios: Done! Re-edited!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 3.11.<br>
&gt; s/associated to one ingress-egress-aggregate/<br>
&gt; /associated with one ingress-egress-aggregate/</p>
<p>&nbsp;</p>
<p>Georgios: Done!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 3.15<br>
&gt; Repeats Section 2.1.9. Unnecessary.</p>
<p>&nbsp;</p>
<p>Georgios: The context of the two sections is slightly different! Therefo=
re, I would like to leave them!</p>
<p>&nbsp;</p>
<p>&gt; <br>
&gt; Section 4.<br>
&gt; s/by an PCN-egress node/<br>
&gt; /by a PCN-egress node/</p>
<p>&nbsp;</p>
<p>Georgios: Done! </p>
<p>&nbsp;</p>
<p>Best regards,<br>
Georgios</p>
<p>&nbsp;</p>
<p><font size=3D"2"><span style=3D"FONT-SIZE: 10pt">&nbsp;</p>
</span></font></div>
</body>
</html>

--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DE81EXMBX23adutwent_--

From david.black@emc.com  Sat Mar  9 10:15:29 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BAF521F8652 for <tsvwg@ietfa.amsl.com>; Sat,  9 Mar 2013 10:15:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GDs7yf7QXtyS for <tsvwg@ietfa.amsl.com>; Sat,  9 Mar 2013 10:15:26 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5243E21F8634 for <tsvwg@ietf.org>; Sat,  9 Mar 2013 10:15:26 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r29IFIqV017009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 9 Mar 2013 13:15:18 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Sat, 9 Mar 2013 13:14:56 -0500
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r29IEtW3028806; Sat, 9 Mar 2013 13:14:56 -0500
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Sat, 9 Mar 2013 13:14:55 -0500
From: "Black, David" <david.black@emc.com>
To: "karagian@cs.utwente.nl" <karagian@cs.utwente.nl>, "bob.briscoe@bt.com" <bob.briscoe@bt.com>
Date: Sat, 9 Mar 2013 13:14:53 -0500
Thread-Topic: RSVP PCN and PBAC
Thread-Index: AQHNuG567zXDhOEf1EmojaHb3rIjiJfaAz+MgAEb9QCAABFxXIAGi4cpgLwHTEqAAAB8MYAArcNQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71290DCD874@MX15A.corp.emc.com>
References: <87644A58-0C27-4F5A-B09B-BD8EC1F9A10A@g11.org.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F2CC12597@EXMBX01.ad.utwente.nl> <D245A17A-F851-4707-A081-12D65C4AC0AF@g11.org.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F2CC1797D@EXMBX04.ad.utwente.nl>, <201211091623.qA9GMxVm013855@bagheera.jungle.bt.co.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F4F36DDC8@EXMBX23.ad.utwente.nl>
In-Reply-To: <FF1A9612A94D5C4A81ED7DE1039AB80F4F36DDC8@EXMBX23.ad.utwente.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8D3D17ACE214DC429325B2B98F3AE71290DCD874MX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "philip.eardley@bt.com" <philip.eardley@bt.com>, "anuragb@cisco.com" <anuragb@cisco.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: [tsvwg] RSVP PCN and PBAC
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Mar 2013 18:15:29 -0000

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

Hi Georgios,

<WG co-chair hat OFF>

I think you've missed the point here:

> In my opinion if it is to introduce a new policy-based admission control =
(PBAC)
> architecture to be used in the context of PCN, then this should be done i=
n another
> document and not in the draft-ietf-tsvwg-rsvp-pcn.

I do not believe that Bob is asking that this draft add a PBAC architecture=
, but rather that minor changes be made so that this draft is consistent wi=
th the PBAC architectural approach:

>> To make this doc fit the PBAC framework, all we have to do is:
>> * Describe the PCN-ingress only as the PCN-ingress and not as the decisi=
on
>> point (find 'decision' throughout doc and fix).
>> * Add a section saying the PCN-ingress can refer flow admission and
>> termination decisions to a central decision point (using e.g. COPS), whi=
ch will
>> respond to the PCN-ingress as per RFC2753. (Alternatively the PCN-ingres=
s
>> could itself be the policy decision point.)
>> * Refer to this new PBAC section from Section 3.11 giving the admission
>> decision procedure.

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

From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of k=
aragian@cs.utwente.nl
Sent: Saturday, March 09, 2013 2:48 AM
To: bob.briscoe@bt.com
Cc: philip.eardley@bt.com; anuragb@cisco.com; tsvwg@ietf.org
Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03

Hi Bob,

Thanks for your comments!

In the below email you propose to introduce the description of a policy-bas=
ed admission control (PBAC) architecture in order to respond to the answer =
about on-path vs off-path policy.
In my opinion if it is to introduce a new policy-based admission control (P=
BAC) architecture to be used in the context of PCN, then this should be don=
e in another document and not in the draft-ietf-tsvwg-rsvp-pcn.

Regarding the answer about on-path vs off-path policy, in draft-ietf-tsvwg-=
rsvp-pcn-04 I have included the argumentation that I proposed as answer to =
the comment on-path vs off-path signaling provided by Ken, and which he act=
ually agreed with!

Best regards,
Georgios


> -----Original Message-----
> From: Bob Briscoe [mailto:bob.briscoe@bt.com<https://xs.utwente.nl/owa/re=
dir.aspx?C=3DNbum9aHfj0KVa6QWoWQdUmsGWht4ps8IsUqKQDAPZNk0j8fbXNgdf5bdf_jZa7=
dRLDi6AlK6wy0.&URL=3Dmailto%3abob.briscoe%40bt.com>]
> Sent: vrijdag 9 november 2012 16:33
> To: Karagiannis, G. (EWI)
> Cc: carlberg@g11.org.uk; anuragb@cisco.com; tsvwg@ietf.org; EARDLEY, Phil
> Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03
>
> Georgios,
>
> I shall post my full review of this draft in the next few days (needs typ=
ing up -
> currently scribbled on a paper copy). This email is solely in response to=
 your
> answer about on-path vs off-path policy.
>
> At 18:55 04/11/2012, karagian@cs.utwente.nl wrote:
> >So in this case an additional signaling protocol will be needed to be
> >specified that covers the signaling between the PCN-egress-node and the
> >centralized node and between PCN-ingress-node and the centralized node.
> >In PCN we decdided to only focus on the specification of the signaling
> >protocol that completes the feedback loop from PCN-egress-node to
> >PCN-ingress-node and to focus on the signaling protocol used between
> >the edge nodes and the centralized node.
>
> When I/we originally designed CL-PCN over RSVP (2005), the idea was that =
it
> would fit with the policy-based admission control (PBAC) architecture of
> RFC2753. In this architecture, an Intserv node at the ingress to a domain=
 is
> the policy enforcement point (PEP), and it refers to a logically centrali=
sed
> 'policy decision point' (PDP) for decisions on which flows to block/termi=
nate,
> typically using COPS.
>
> To make this doc fit the PBAC framework, all we have to do is:
> * Describe the PCN-ingress only as the PCN-ingress and not as the decisio=
n
> point (find 'decision' throughout doc and fix).
> * Add a section saying the PCN-ingress can refer flow admission and
> termination decisions to a central decision point (using e.g. COPS), whic=
h will
> respond to the PCN-ingress as per RFC2753. (Alternatively the PCN-ingress
> could itself be the policy decision point.)
> * Refer to this new PBAC section from Section 3.11 giving the admission
> decision procedure.
>
> * Some people might think this means COPS will need new protocol
> elements to carry PCN marking rates to the policy decision point. But PCN
> marking rates are irrelevant to the policy decision: the PCN-ingress just=
 uses
> PCN to determine whether it needs to block or terminate, and it refers to=
 the
> policy decision point for which flows to block/terminate.
>
> * Unfortunately, neither of the two PCN system descriptions [RFC6661,
> RFC6662] describe a PBAC-based case. The architecture [RFC5559] refers to
> the PBAC framework [RFC2753] but unfortunately doesn't spell out how it
> fits. Originally, I referenced PBAC from RFC5559, but just as the PCN w-g=
 was
> closing I realised that (some?) others in the PCN w-g were working under =
the
> assumption that the only way to talk to a centralised policy node was fro=
m
> the egress, possibly without being aware of the contents of RFC2753.
>
> I think it's OK to introduce a new architectural arrangement in this RSVP=
 doc,
> given RFC2753 is specific to the way RSVP works.
>
>
> Bob


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style id=3DowaParaStyle><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:1.0pt;
	margin-bottom:.0001pt;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>Hi Georgios,<o:p></o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fam=
ily:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'=
>&lt;WG co-chair hat OFF&gt;<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New";color:black'>I think you&#8217;ve missed the point =
here:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10=
.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New"=
;color:black'>&gt; In my opinion if it is to introduce a new policy-based a=
dmission control (PBAC)<o:p></o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:10.0pt;font-family:"Courier New";color:black'>&gt; architec=
ture to be used in the context of PCN, then this should be done&nbsp;in ano=
ther<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:"Courier New";color:black'>&gt; document and not&nbsp;in th=
e draft-ietf-tsvwg-rsvp-pcn.<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New";color:black'>I do not believe that Bob is asking th=
at this draft add a PBAC architecture, but rather that minor changes be mad=
e so that this draft is consistent with the PBAC architectural approach:<o:=
p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3D=
MsoNormal>&gt;&gt; To make this doc fit the PBAC framework, all we have to =
do is:<o:p></o:p></p><p class=3DMsoNormal>&gt;&gt; * Describe the PCN-ingre=
ss only as the PCN-ingress and not as the decision<o:p></o:p></p><p class=
=3DMsoNormal>&gt;&gt; point (find 'decision' throughout doc and fix).<o:p><=
/o:p></p><p class=3DMsoNormal>&gt;&gt; * Add a section saying the PCN-ingre=
ss can refer flow admission and<o:p></o:p></p><p class=3DMsoNormal>&gt;&gt;=
 termination decisions to a central decision point (using e.g. COPS), which=
 will<o:p></o:p></p><p class=3DMsoNormal>&gt;&gt; respond to the PCN-ingres=
s as per RFC2753. (Alternatively the PCN-ingress<o:p></o:p></p><p class=3DM=
soNormal>&gt;&gt; could itself be the policy decision point.)<o:p></o:p></p=
><p class=3DMsoNormal>&gt;&gt; * Refer to this new PBAC section from Sectio=
n 3.11 giving the admission<o:p></o:p></p><p class=3DMsoNormal>&gt;&gt; dec=
ision procedure.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><d=
iv><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courie=
r New";color:black'>Thanks,<br>--David<br>---------------------------------=
-------------------<br>David L. Black, Distinguished Engineer<br>EMC Corpor=
ation, 176 South St., Hopkinton, MA&nbsp; 01748<br>+1 (508) 293-7953&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FAX: +1 (=
508) 293-7786<br>david.black@emc.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Mobile: +1 (978) 394-7754<br>------------------------------------------=
----------</span><span style=3D'font-size:11.0pt;font-family:"Courier New";=
color:black'><o:p></o:p></span></p></div><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:=
p></span></p><div style=3D'border:none;border-left:solid blue 1.5pt;padding=
:0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF=
 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'fo=
nt-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span sty=
le=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> tsvwg-bounces@ie=
tf.org [mailto:tsvwg-bounces@ietf.org] <b>On Behalf Of </b>karagian@cs.utwe=
nte.nl<br><b>Sent:</b> Saturday, March 09, 2013 2:48 AM<br><b>To:</b> bob.b=
riscoe@bt.com<br><b>Cc:</b> philip.eardley@bt.com; anuragb@cisco.com; tsvwg=
@ietf.org<br><b>Subject:</b> Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03<o:p><=
/o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew";color:black'>Hi Bob,<o:p></o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier Ne=
w";color:black'>Thanks for your comments!<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-family:"Courier New";color:black'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-f=
amily:"Courier New";color:black'>In the below email you propose to introduc=
e the description of a policy-based admission control (PBAC) architecture i=
n order to respond to the answer about on-path vs off-path policy. <o:p></o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fam=
ily:"Courier New";color:black'>In my opinion if it is to introduce a new po=
licy-based admission control (PBAC) architecture to be used in the context =
of PCN, then this should be done&nbsp;in another document and not&nbsp;in t=
he draft-ietf-tsvwg-rsvp-pcn.<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Couri=
er New";color:black'>Regarding the answer about on-path vs off-path policy,=
 in draft-ietf-tsvwg-rsvp-pcn-04&nbsp;I have included the argumentation tha=
t I proposed as answer to the comment on-path vs off-path signaling provide=
d by Ken, and which he actually agreed with!<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-family:"Courier New";color:black'><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New";color:black'>Best regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New"=
;color:black'>Georgios<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier New";color:black'><o:=
p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0=
pt;font-family:"Courier New";color:black'>&gt; -----Original Message-----<b=
r>&gt; From: Bob Briscoe [</span><span style=3D'font-family:"Courier New";c=
olor:black'><a href=3D"https://xs.utwente.nl/owa/redir.aspx?C=3DNbum9aHfj0K=
Va6QWoWQdUmsGWht4ps8IsUqKQDAPZNk0j8fbXNgdf5bdf_jZa7dRLDi6AlK6wy0.&amp;URL=
=3Dmailto%3abob.briscoe%40bt.com" target=3D"_blank"><span style=3D'font-siz=
e:10.0pt'>mailto:bob.briscoe@bt.com</span></a></span><span style=3D'font-si=
ze:10.0pt;font-family:"Courier New";color:black'>]<br>&gt; Sent: vrijdag 9 =
november 2012 16:33<br>&gt; To: Karagiannis, G. (EWI)<br>&gt; Cc: carlberg@=
g11.org.uk; anuragb@cisco.com; tsvwg@ietf.org; EARDLEY, Phil<br>&gt; Subjec=
t: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03<br>&gt; <br>&gt; Georgios,<br>&=
gt; <br>&gt; I shall post my full review of this draft in the next few days=
 (needs typing up -<br>&gt; currently scribbled on a paper copy). This emai=
l is solely in response to your<br>&gt; answer about on-path vs off-path po=
licy.<br>&gt; <br>&gt; At 18:55 04/11/2012, karagian@cs.utwente.nl wrote:<b=
r>&gt; &gt;So in this case an additional signaling protocol will be needed =
to be<br>&gt; &gt;specified that covers the signaling between the PCN-egres=
s-node and the<br>&gt; &gt;centralized node and between PCN-ingress-node an=
d the centralized node.<br>&gt; &gt;In PCN we decdided to only focus on the=
 specification of the signaling<br>&gt; &gt;protocol that completes the fee=
dback loop from PCN-egress-node to<br>&gt; &gt;PCN-ingress-node and to focu=
s on the signaling protocol used between<br>&gt; &gt;the edge nodes and the=
 centralized node.<br>&gt; <br>&gt; When I/we originally designed CL-PCN ov=
er RSVP (2005), the idea was that it<br>&gt; would fit with the policy-base=
d admission control (PBAC) architecture of<br>&gt; RFC2753. In this archite=
cture, an Intserv node at the ingress to a domain is<br>&gt; the policy enf=
orcement point (PEP), and it refers to a logically centralised<br>&gt; 'pol=
icy decision point' (PDP) for decisions on which flows to block/terminate,<=
br>&gt; typically using COPS.<br>&gt; <br>&gt; To make this doc fit the PBA=
C framework, all we have to do is:<br>&gt; * Describe the PCN-ingress only =
as the PCN-ingress and not as the decision<br>&gt; point (find 'decision' t=
hroughout doc and fix).<br>&gt; * Add a section saying the PCN-ingress can =
refer flow admission and<br>&gt; termination decisions to a central decisio=
n point (using e.g. COPS), which will<br>&gt; respond to the PCN-ingress as=
 per RFC2753. (Alternatively the PCN-ingress<br>&gt; could itself be the po=
licy decision point.)<br>&gt; * Refer to this new PBAC section from Section=
 3.11 giving the admission<br>&gt; decision procedure.<br>&gt; <br>&gt; * S=
ome people might think this means COPS will need new protocol<br>&gt; eleme=
nts to carry PCN marking rates to the policy decision point. But PCN<br>&gt=
; marking rates are irrelevant to the policy decision: the PCN-ingress just=
 uses<br>&gt; PCN to determine whether it needs to block or terminate, and =
it refers to the<br>&gt; policy decision point for which flows to block/ter=
minate.<br>&gt; <br>&gt; * Unfortunately, neither of the two PCN system des=
criptions [RFC6661,<br>&gt; RFC6662] describe a PBAC-based case. The archit=
ecture [RFC5559] refers to<br>&gt; the PBAC framework [RFC2753] but unfortu=
nately doesn't spell out how it<br>&gt; fits. Originally, I referenced PBAC=
 from RFC5559, but just as the PCN w-g was<br>&gt; closing I realised that =
(some?) others in the PCN w-g were working under the<br>&gt; assumption tha=
t the only way to talk to a centralised policy node was from<br>&gt; the eg=
ress, possibly without being aware of the contents of RFC2753.<br>&gt; <br>=
&gt; I think it's OK to introduce a new architectural arrangement in this R=
SVP doc,<br>&gt; given RFC2753 is specific to the way RSVP works.<br>&gt; <=
br>&gt; <br>&gt; Bob</span><span style=3D'color:black'><o:p></o:p></span></=
p><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p></div></div></d=
iv></div></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE71290DCD874MX15Acorpemccom_--

From karagian@cs.utwente.nl  Sat Mar  9 11:28:25 2013
Return-Path: <karagian@cs.utwente.nl>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7A421F8714 for <tsvwg@ietfa.amsl.com>; Sat,  9 Mar 2013 11:28:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.428
X-Spam-Level: 
X-Spam-Status: No, score=-0.428 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96ljfGvkfNWU for <tsvwg@ietfa.amsl.com>; Sat,  9 Mar 2013 11:28:23 -0800 (PST)
Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by ietfa.amsl.com (Postfix) with ESMTP id BA49821F870C for <tsvwg@ietf.org>; Sat,  9 Mar 2013 11:28:21 -0800 (PST)
Received: from EXHUB01.ad.utwente.nl (130.89.4.228) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.2.328.9; Sat, 9 Mar 2013 20:28:22 +0100
Received: from EXMBX23.ad.utwente.nl ([169.254.3.16]) by EXHUB01.ad.utwente.nl ([130.89.4.228]) with mapi id 14.02.0328.009; Sat, 9 Mar 2013 20:28:20 +0100
From: <karagian@cs.utwente.nl>
To: <david.black@emc.com>, <bob.briscoe@bt.com>
Thread-Topic: RSVP PCN and PBAC
Thread-Index: AQHOHPISb30xrFOgvkmKX1/6hXUsRZidvLytgAAB48g=
Date: Sat, 9 Mar 2013 19:28:19 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F4F36DF07@EXMBX23.ad.utwente.nl>
References: <87644A58-0C27-4F5A-B09B-BD8EC1F9A10A@g11.org.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F2CC12597@EXMBX01.ad.utwente.nl> <D245A17A-F851-4707-A081-12D65C4AC0AF@g11.org.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F2CC1797D@EXMBX04.ad.utwente.nl>, <201211091623.qA9GMxVm013855@bagheera.jungle.bt.co.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F4F36DDC8@EXMBX23.ad.utwente.nl>, <8D3D17ACE214DC429325B2B98F3AE71290DCD874@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290DCD874@MX15A.corp.emc.com>
Accept-Language: nl-NL, en-US
Content-Language: nl-NL
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mimectl: Produced By Microsoft Exchange V14.2.247.1
x-originating-ip: [86.91.134.3]
Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DF07EXMBX23adutwent_"
MIME-Version: 1.0
Cc: philip.eardley@bt.com, anuragb@cisco.com, tsvwg@ietf.org
Subject: Re: [tsvwg] RSVP PCN and PBAC
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Mar 2013 19:28:25 -0000

--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DF07EXMBX23adutwent_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi David,



Thanks for your comment!

What I meant is that Bob would like to see a description of PCN based PBAC =
framework in the RSVP over PCN draft

that is not realy specified in any other PCN documents.

In my opinion the RSVP over PCN draft is not the draft that should introduc=
e such a PBAC framework.



Best regards,

Georgios









________________________________
Van: Black, David [david.black@emc.com]
Verzonden: zaterdag 9 maart 2013 19:14
To: Karagiannis, G. (EWI); bob.briscoe@bt.com
Cc: philip.eardley@bt.com; anuragb@cisco.com; tsvwg@ietf.org
Onderwerp: RSVP PCN and PBAC

Hi Georgios,

<WG co-chair hat OFF>

I think you=92ve missed the point here:

> In my opinion if it is to introduce a new policy-based admission control =
(PBAC)
> architecture to be used in the context of PCN, then this should be done i=
n another
> document and not in the draft-ietf-tsvwg-rsvp-pcn.

I do not believe that Bob is asking that this draft add a PBAC architecture=
, but rather that minor changes be made so that this draft is consistent wi=
th the PBAC architectural approach:

>> To make this doc fit the PBAC framework, all we have to do is:
>> * Describe the PCN-ingress only as the PCN-ingress and not as the decisi=
on
>> point (find 'decision' throughout doc and fix).
>> * Add a section saying the PCN-ingress can refer flow admission and
>> termination decisions to a central decision point (using e.g. COPS), whi=
ch will
>> respond to the PCN-ingress as per RFC2753. (Alternatively the PCN-ingres=
s
>> could itself be the policy decision point.)
>> * Refer to this new PBAC section from Section 3.11 giving the admission
>> decision procedure.

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

From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of k=
aragian@cs.utwente.nl
Sent: Saturday, March 09, 2013 2:48 AM
To: bob.briscoe@bt.com
Cc: philip.eardley@bt.com; anuragb@cisco.com; tsvwg@ietf.org
Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03

Hi Bob,

Thanks for your comments!

In the below email you propose to introduce the description of a policy-bas=
ed admission control (PBAC) architecture in order to respond to the answer =
about on-path vs off-path policy.
In my opinion if it is to introduce a new policy-based admission control (P=
BAC) architecture to be used in the context of PCN, then this should be don=
e in another document and not in the draft-ietf-tsvwg-rsvp-pcn.

Regarding the answer about on-path vs off-path policy, in draft-ietf-tsvwg-=
rsvp-pcn-04 I have included the argumentation that I proposed as answer to =
the comment on-path vs off-path signaling provided by Ken, and which he act=
ually agreed with!

Best regards,
Georgios


> -----Original Message-----
> From: Bob Briscoe [mailto:bob.briscoe@bt.com<https://xs.utwente.nl/owa/re=
dir.aspx?C=3DNbum9aHfj0KVa6QWoWQdUmsGWht4ps8IsUqKQDAPZNk0j8fbXNgdf5bdf_jZa7=
dRLDi6AlK6wy0.&URL=3Dmailto%3abob.briscoe%40bt.com>]
> Sent: vrijdag 9 november 2012 16:33
> To: Karagiannis, G. (EWI)
> Cc: carlberg@g11.org.uk; anuragb@cisco.com; tsvwg@ietf.org; EARDLEY, Phil
> Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03
>
> Georgios,
>
> I shall post my full review of this draft in the next few days (needs typ=
ing up -
> currently scribbled on a paper copy). This email is solely in response to=
 your
> answer about on-path vs off-path policy.
>
> At 18:55 04/11/2012, karagian@cs.utwente.nl wrote:
> >So in this case an additional signaling protocol will be needed to be
> >specified that covers the signaling between the PCN-egress-node and the
> >centralized node and between PCN-ingress-node and the centralized node.
> >In PCN we decdided to only focus on the specification of the signaling
> >protocol that completes the feedback loop from PCN-egress-node to
> >PCN-ingress-node and to focus on the signaling protocol used between
> >the edge nodes and the centralized node.
>
> When I/we originally designed CL-PCN over RSVP (2005), the idea was that =
it
> would fit with the policy-based admission control (PBAC) architecture of
> RFC2753. In this architecture, an Intserv node at the ingress to a domain=
 is
> the policy enforcement point (PEP), and it refers to a logically centrali=
sed
> 'policy decision point' (PDP) for decisions on which flows to block/termi=
nate,
> typically using COPS.
>
> To make this doc fit the PBAC framework, all we have to do is:
> * Describe the PCN-ingress only as the PCN-ingress and not as the decisio=
n
> point (find 'decision' throughout doc and fix).
> * Add a section saying the PCN-ingress can refer flow admission and
> termination decisions to a central decision point (using e.g. COPS), whic=
h will
> respond to the PCN-ingress as per RFC2753. (Alternatively the PCN-ingress
> could itself be the policy decision point.)
> * Refer to this new PBAC section from Section 3.11 giving the admission
> decision procedure.
>
> * Some people might think this means COPS will need new protocol
> elements to carry PCN marking rates to the policy decision point. But PCN
> marking rates are irrelevant to the policy decision: the PCN-ingress just=
 uses
> PCN to determine whether it needs to block or terminate, and it refers to=
 the
> policy decision point for which flows to block/terminate.
>
> * Unfortunately, neither of the two PCN system descriptions [RFC6661,
> RFC6662] describe a PBAC-based case. The architecture [RFC5559] refers to
> the PBAC framework [RFC2753] but unfortunately doesn't spell out how it
> fits. Originally, I referenced PBAC from RFC5559, but just as the PCN w-g=
 was
> closing I realised that (some?) others in the PCN w-g were working under =
the
> assumption that the only way to talk to a centralised policy node was fro=
m
> the egress, possibly without being aware of the contents of RFC2753.
>
> I think it's OK to introduce a new architectural arrangement in this RSVP=
 doc,
> given RFC2753 is specific to the way RSVP works.
>
>
> Bob


--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DF07EXMBX23adutwent_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <BD936C287755E2459A303F58DC5DCC69@exchange.utwente.nl>
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style>@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12=
pt
}
LI.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12=
pt
}
DIV.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12=
pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P.emailquote {
	BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in;=
 MARGIN: 0in 0in 0pt 1pt; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; FONT-FAMIL=
Y: "Times New=20
Roman","serif"; FONT-SIZE: 12pt; BORDER-TOP: medium none; BORDER-RIGHT: med=
ium none; PADDING-TOP: 0in
}
LI.emailquote {
	BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in;=
 MARGIN: 0in 0in 0pt 1pt; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; FONT-FAMIL=
Y: "Times New=20
Roman","serif"; FONT-SIZE: 12pt; BORDER-TOP: medium none; BORDER-RIGHT: med=
ium none; PADDING-TOP: 0in
}
DIV.emailquote {
	BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in;=
 MARGIN: 0in 0in 0pt 1pt; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; FONT-FAMIL=
Y: "Times New=20
Roman","serif"; FONT-SIZE: 12pt; BORDER-TOP: medium none; BORDER-RIGHT: med=
ium none; PADDING-TOP: 0in
}
SPAN.EmailStyle19 {
	FONT-STYLE: normal; FONT-FAMILY: "Courier New"; COLOR: black; FONT-WEIGHT:=
 normal; TEXT-DECORATION: none
}
.MsoChpDefault {
	FONT-SIZE: 10pt
}
DIV.WordSection1 {
=09
}
</style><style id=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body lang=3D"EN-US" vlink=3D"purple" link=3D"blue" ocsi=3D"0" fPStyle=3D"1=
">
<div style=3D"FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZ=
E: 10pt">
<p>Hi David,</p>
<p>&nbsp;</p>
<p>Thanks for your comment!<br>
</p>
<p>What I meant is that Bob would like to see a description of PCN based PB=
AC framework in the RSVP over PCN draft
</p>
<p>that is not realy&nbsp;specified in any other PCN documents. </p>
<p>In my opinion the RSVP over PCN draft is not the draft that should intro=
duce such a PBAC framework.</p>
<p>&nbsp;</p>
<p>Best regards,</p>
<p>Georgios</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<hr tabindex=3D"-1">
<div style=3D"DIRECTION: ltr" id=3D"divRpF794886"><font color=3D"#000000" s=
ize=3D"2" face=3D"Tahoma"><b>Van:</b> Black, David [david.black@emc.com]<br=
>
<b>Verzonden:</b> zaterdag 9 maart 2013 19:14<br>
<b>To:</b> Karagiannis, G. (EWI); bob.briscoe@bt.com<br>
<b>Cc:</b> philip.eardley@bt.com; anuragb@cisco.com; tsvwg@ietf.org<br>
<b>Onderwerp:</b> RSVP PCN and PBAC<br>
</font><br>
</div>
<div></div>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">Hi Georgios,</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">&lt;WG co-chair hat OFF&gt;</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">I think you=92ve missed the point here:</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">&gt; In my opinion if it is to introduce a new policy=
-based admission control (PBAC)</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">&gt; architecture to be used in the context of PCN, t=
hen this should be done&nbsp;in another</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">&gt; document and not&nbsp;in the draft-ietf-tsvwg-rs=
vp-pcn.</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">I do not believe that Bob is asking that this draft a=
dd a PBAC architecture, but rather that minor changes be made so that this =
draft is consistent with the PBAC architectural
 approach:</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p class=3D"MsoNormal">&gt;&gt; To make this doc fit the PBAC framework, al=
l we have to do is:</p>
<p class=3D"MsoNormal">&gt;&gt; * Describe the PCN-ingress only as the PCN-=
ingress and not as the decision</p>
<p class=3D"MsoNormal">&gt;&gt; point (find 'decision' throughout doc and f=
ix).</p>
<p class=3D"MsoNormal">&gt;&gt; * Add a section saying the PCN-ingress can =
refer flow admission and</p>
<p class=3D"MsoNormal">&gt;&gt; termination decisions to a central decision=
 point (using e.g. COPS), which will</p>
<p class=3D"MsoNormal">&gt;&gt; respond to the PCN-ingress as per RFC2753. =
(Alternatively the PCN-ingress</p>
<p class=3D"MsoNormal">&gt;&gt; could itself be the policy decision point.)=
</p>
<p class=3D"MsoNormal">&gt;&gt; * Refer to this new PBAC section from Secti=
on 3.11 giving the admission</p>
<p class=3D"MsoNormal">&gt;&gt; decision procedure.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">Thanks,<br>
--David<br>
----------------------------------------------------<br>
David L. Black, Distinguished Engineer<br>
EMC Corporation, 176 South St., Hopkinton, MA&nbsp; 01748<br>
&#43;1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; FAX: &#43;1 (508) 293-7786<br>
david.black@emc.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile: &#43;=
1 (978) 394-7754<br>
----------------------------------------------------</span><span style=3D"F=
ONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: 11pt"></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt"></span>&nbsp;</p>
<div style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; PA=
DDING-BOTTOM: 0in; PADDING-LEFT: 4pt; PADDING-RIGHT: 0in; BORDER-TOP: mediu=
m none; BORDER-RIGHT: medium none; PADDING-TOP: 0in">
<div>
<div style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING=
-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1p=
t solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class=3D"MsoNormal"><b><span style=3D"FONT-FAMILY: 'Tahoma','sans-serif'=
; FONT-SIZE: 10pt">From:</span></b><span style=3D"FONT-FAMILY: 'Tahoma','sa=
ns-serif'; FONT-SIZE: 10pt"> tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@i=
etf.org]
<b>On Behalf Of </b>karagian@cs.utwente.nl<br>
<b>Sent:</b> Saturday, March 09, 2013 2:48 AM<br>
<b>To:</b> bob.briscoe@bt.com<br>
<b>Cc:</b> philip.eardley@bt.com; anuragb@cisco.com; tsvwg@ietf.org<br>
<b>Subject:</b> Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">Hi Bob,</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">Thanks for your comments!</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">In the below email you propose to introduce the descr=
iption of a policy-based admission control (PBAC) architecture in order to =
respond to the answer about on-path
 vs off-path policy. </span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">In my opinion if it is to introduce a new policy-base=
d admission control (PBAC) architecture to be used in the context of PCN, t=
hen this should be done&nbsp;in another document
 and not&nbsp;in the draft-ietf-tsvwg-rsvp-pcn.</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">Regarding the answer about on-path vs off-path policy=
, in draft-ietf-tsvwg-rsvp-pcn-04&nbsp;I have included the argumentation th=
at I proposed as answer to the comment on-path
 vs off-path signaling provided by Ken, and which he actually agreed with!<=
/span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">Best regards,</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">Georgios</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">&gt; -----Original Message-----<br>
&gt; From: Bob Briscoe [</span><span style=3D"FONT-FAMILY: 'Courier New'; C=
OLOR: black"><a href=3D"https://xs.utwente.nl/owa/redir.aspx?C=3DNbum9aHfj0=
KVa6QWoWQdUmsGWht4ps8IsUqKQDAPZNk0j8fbXNgdf5bdf_jZa7dRLDi6AlK6wy0.&amp;URL=
=3Dmailto%3abob.briscoe%40bt.com" target=3D"_blank"><span style=3D"FONT-SIZ=
E: 10pt">mailto:bob.briscoe@bt.com</span></a></span><span style=3D"FONT-FAM=
ILY: 'Courier New'; COLOR: black; FONT-SIZE: 10pt">]<br>
&gt; Sent: vrijdag 9 november 2012 16:33<br>
&gt; To: Karagiannis, G. (EWI)<br>
&gt; Cc: carlberg@g11.org.uk; anuragb@cisco.com; tsvwg@ietf.org; EARDLEY, P=
hil<br>
&gt; Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03<br>
&gt; <br>
&gt; Georgios,<br>
&gt; <br>
&gt; I shall post my full review of this draft in the next few days (needs =
typing up -<br>
&gt; currently scribbled on a paper copy). This email is solely in response=
 to your<br>
&gt; answer about on-path vs off-path policy.<br>
&gt; <br>
&gt; At 18:55 04/11/2012, karagian@cs.utwente.nl wrote:<br>
&gt; &gt;So in this case an additional signaling protocol will be needed to=
 be<br>
&gt; &gt;specified that covers the signaling between the PCN-egress-node an=
d the<br>
&gt; &gt;centralized node and between PCN-ingress-node and the centralized =
node.<br>
&gt; &gt;In PCN we decdided to only focus on the specification of the signa=
ling<br>
&gt; &gt;protocol that completes the feedback loop from PCN-egress-node to<=
br>
&gt; &gt;PCN-ingress-node and to focus on the signaling protocol used betwe=
en<br>
&gt; &gt;the edge nodes and the centralized node.<br>
&gt; <br>
&gt; When I/we originally designed CL-PCN over RSVP (2005), the idea was th=
at it<br>
&gt; would fit with the policy-based admission control (PBAC) architecture =
of<br>
&gt; RFC2753. In this architecture, an Intserv node at the ingress to a dom=
ain is<br>
&gt; the policy enforcement point (PEP), and it refers to a logically centr=
alised<br>
&gt; 'policy decision point' (PDP) for decisions on which flows to block/te=
rminate,<br>
&gt; typically using COPS.<br>
&gt; <br>
&gt; To make this doc fit the PBAC framework, all we have to do is:<br>
&gt; * Describe the PCN-ingress only as the PCN-ingress and not as the deci=
sion<br>
&gt; point (find 'decision' throughout doc and fix).<br>
&gt; * Add a section saying the PCN-ingress can refer flow admission and<br=
>
&gt; termination decisions to a central decision point (using e.g. COPS), w=
hich will<br>
&gt; respond to the PCN-ingress as per RFC2753. (Alternatively the PCN-ingr=
ess<br>
&gt; could itself be the policy decision point.)<br>
&gt; * Refer to this new PBAC section from Section 3.11 giving the admissio=
n<br>
&gt; decision procedure.<br>
&gt; <br>
&gt; * Some people might think this means COPS will need new protocol<br>
&gt; elements to carry PCN marking rates to the policy decision point. But =
PCN<br>
&gt; marking rates are irrelevant to the policy decision: the PCN-ingress j=
ust uses<br>
&gt; PCN to determine whether it needs to block or terminate, and it refers=
 to the<br>
&gt; policy decision point for which flows to block/terminate.<br>
&gt; <br>
&gt; * Unfortunately, neither of the two PCN system descriptions [RFC6661,<=
br>
&gt; RFC6662] describe a PBAC-based case. The architecture [RFC5559] refers=
 to<br>
&gt; the PBAC framework [RFC2753] but unfortunately doesn't spell out how i=
t<br>
&gt; fits. Originally, I referenced PBAC from RFC5559, but just as the PCN =
w-g was<br>
&gt; closing I realised that (some?) others in the PCN w-g were working und=
er the<br>
&gt; assumption that the only way to talk to a centralised policy node was =
from<br>
&gt; the egress, possibly without being aware of the contents of RFC2753.<b=
r>
&gt; <br>
&gt; I think it's OK to introduce a new architectural arrangement in this R=
SVP doc,<br>
&gt; given RFC2753 is specific to the way RSVP works.<br>
&gt; <br>
&gt; <br>
&gt; Bob</span><span style=3D"COLOR: black"></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; C=
OLOR: black; FONT-SIZE: 10pt"></span>&nbsp;</p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F36DF07EXMBX23adutwent_--

From david.black@emc.com  Sat Mar  9 14:02:45 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA4CA21F8763 for <tsvwg@ietfa.amsl.com>; Sat,  9 Mar 2013 14:02:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.349
X-Spam-Level: 
X-Spam-Status: No, score=-102.349 tagged_above=-999 required=5 tests=[AWL=-0.251, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BAD_LINEBREAK=0.5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zYxKtFHd1SD0 for <tsvwg@ietfa.amsl.com>; Sat,  9 Mar 2013 14:02:27 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id BD40921F875A for <tsvwg@ietf.org>; Sat,  9 Mar 2013 14:02:22 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r29M2EJw027604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 9 Mar 2013 17:02:14 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sat, 9 Mar 2013 17:02:01 -0500
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r29M208h018118; Sat, 9 Mar 2013 17:02:01 -0500
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub13.corp.emc.com ([128.222.70.234]) with mapi; Sat, 9 Mar 2013 17:02:00 -0500
From: "Black, David" <david.black@emc.com>
To: "'karagian@cs.utwente.nl'" <karagian@cs.utwente.nl>, "'bob.briscoe@bt.com'" <bob.briscoe@bt.com>
Date: Sat, 9 Mar 2013 17:01:59 -0500
Thread-Topic: RSVP PCN and PBAC
Thread-Index: AQHOHPISb30xrFOgvkmKX1/6hXUsRZidvLytgAAB48iAACrvUA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71290DEE214@MX15A.corp.emc.com>
In-Reply-To: <FF1A9612A94D5C4A81ED7DE1039AB80F4F36DF07@EXMBX23.ad.utwente.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8D3D17ACE214DC429325B2B98F3AE71290DEE214MX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "'philip.eardley@bt.com'" <philip.eardley@bt.com>, "'anuragb@cisco.com'" <anuragb@cisco.com>, "'tsvwg@ietf.org'" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RSVP PCN and PBAC
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Mar 2013 22:02:45 -0000

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

SGkgR2Vvcmdpb3MsDQoNCihTdGlsbCBwb3N0aW5nIGFzIGFuIGluZGl2aWR1YWwsIG5vdCBhIFdH
IGNvLWNoYWlyKQ0KDQpUaGVuIEkgZ3Vlc3Mgd2UgZGlzYWdyZWUgb24gd2hhdCBhIGZyYW1ld29y
ayBpcywgYmVjYXVzZSBJIGFncmVlIHRoYXQgYSBmdWxsIFBCQUMgZnJhbWV3b3JrIHNob3VsZCBu
b3QgYmUgZGVzY3JpYmVkIGluIHRoaXMgZHJhZnQsIGJ1dCBJIGRvbid0IHZpZXcgdGhlIGNoYW5n
ZXMgdGhhdCBCb2IgaXMgYXNraW5nIGZvciAocHJpbWFyaWx5IHRvIHBvaW50IG91dCB0aGF0IHRo
ZSBQQ04gZWRnZSBhbmQgdGhlIGRlY2lzaW9uIHBvaW50IG1heSBiZSBzZXBhcmF0ZSkgYXMgY29t
aW5nIGNsb3NlIHRvIGRlc2NyaWJpbmcgc3VjaCBhIGZyYW1ld29yay4NCg0KVGhhbmtzLCAtLURh
dmlkICsrK1NlbnQgZnJvbSBCbGFja2JlcnJ5DQoNCkZyb206IGthcmFnaWFuQGNzLnV0d2VudGUu
bmwgW21haWx0bzprYXJhZ2lhbkBjcy51dHdlbnRlLm5sXQ0KU2VudDogU2F0dXJkYXksIE1hcmNo
IDA5LCAyMDEzIDAyOjI4IFBNDQpUbzogQmxhY2ssIERhdmlkOyBib2IuYnJpc2NvZUBidC5jb20g
PGJvYi5icmlzY29lQGJ0LmNvbT4NCkNjOiBwaGlsaXAuZWFyZGxleUBidC5jb20gPHBoaWxpcC5l
YXJkbGV5QGJ0LmNvbT47IGFudXJhZ2JAY2lzY28uY29tIDxhbnVyYWdiQGNpc2NvLmNvbT47IHRz
dndnQGlldGYub3JnIDx0c3Z3Z0BpZXRmLm9yZz4NClN1YmplY3Q6IFJFOiBSU1ZQIFBDTiBhbmQg
UEJBQw0KDQoNCkhpIERhdmlkLA0KDQoNCg0KVGhhbmtzIGZvciB5b3VyIGNvbW1lbnQhDQoNCldo
YXQgSSBtZWFudCBpcyB0aGF0IEJvYiB3b3VsZCBsaWtlIHRvIHNlZSBhIGRlc2NyaXB0aW9uIG9m
IFBDTiBiYXNlZCBQQkFDIGZyYW1ld29yayBpbiB0aGUgUlNWUCBvdmVyIFBDTiBkcmFmdA0KDQp0
aGF0IGlzIG5vdCByZWFseSBzcGVjaWZpZWQgaW4gYW55IG90aGVyIFBDTiBkb2N1bWVudHMuDQoN
CkluIG15IG9waW5pb24gdGhlIFJTVlAgb3ZlciBQQ04gZHJhZnQgaXMgbm90IHRoZSBkcmFmdCB0
aGF0IHNob3VsZCBpbnRyb2R1Y2Ugc3VjaCBhIFBCQUMgZnJhbWV3b3JrLg0KDQoNCg0KQmVzdCBy
ZWdhcmRzLA0KDQpHZW9yZ2lvcw0KDQoNCg0KDQoNCg0KDQoNCg0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NClZhbjogQmxhY2ssIERhdmlkIFtkYXZpZC5ibGFja0BlbWMuY29tXQ0K
VmVyem9uZGVuOiB6YXRlcmRhZyA5IG1hYXJ0IDIwMTMgMTk6MTQNClRvOiBLYXJhZ2lhbm5pcywg
Ry4gKEVXSSk7IGJvYi5icmlzY29lQGJ0LmNvbQ0KQ2M6IHBoaWxpcC5lYXJkbGV5QGJ0LmNvbTsg
YW51cmFnYkBjaXNjby5jb207IHRzdndnQGlldGYub3JnDQpPbmRlcndlcnA6IFJTVlAgUENOIGFu
ZCBQQkFDDQoNCkhpIEdlb3JnaW9zLA0KDQo8V0cgY28tY2hhaXIgaGF0IE9GRj4NCg0KSSB0aGlu
ayB5b3XigJl2ZSBtaXNzZWQgdGhlIHBvaW50IGhlcmU6DQoNCj4gSW4gbXkgb3BpbmlvbiBpZiBp
dCBpcyB0byBpbnRyb2R1Y2UgYSBuZXcgcG9saWN5LWJhc2VkIGFkbWlzc2lvbiBjb250cm9sIChQ
QkFDKQ0KPiBhcmNoaXRlY3R1cmUgdG8gYmUgdXNlZCBpbiB0aGUgY29udGV4dCBvZiBQQ04sIHRo
ZW4gdGhpcyBzaG91bGQgYmUgZG9uZSBpbiBhbm90aGVyDQo+IGRvY3VtZW50IGFuZCBub3QgaW4g
dGhlIGRyYWZ0LWlldGYtdHN2d2ctcnN2cC1wY24uDQoNCkkgZG8gbm90IGJlbGlldmUgdGhhdCBC
b2IgaXMgYXNraW5nIHRoYXQgdGhpcyBkcmFmdCBhZGQgYSBQQkFDIGFyY2hpdGVjdHVyZSwgYnV0
IHJhdGhlciB0aGF0IG1pbm9yIGNoYW5nZXMgYmUgbWFkZSBzbyB0aGF0IHRoaXMgZHJhZnQgaXMg
Y29uc2lzdGVudCB3aXRoIHRoZSBQQkFDIGFyY2hpdGVjdHVyYWwgYXBwcm9hY2g6DQoNCj4+IFRv
IG1ha2UgdGhpcyBkb2MgZml0IHRoZSBQQkFDIGZyYW1ld29yaywgYWxsIHdlIGhhdmUgdG8gZG8g
aXM6DQo+PiAqIERlc2NyaWJlIHRoZSBQQ04taW5ncmVzcyBvbmx5IGFzIHRoZSBQQ04taW5ncmVz
cyBhbmQgbm90IGFzIHRoZSBkZWNpc2lvbg0KPj4gcG9pbnQgKGZpbmQgJ2RlY2lzaW9uJyB0aHJv
dWdob3V0IGRvYyBhbmQgZml4KS4NCj4+ICogQWRkIGEgc2VjdGlvbiBzYXlpbmcgdGhlIFBDTi1p
bmdyZXNzIGNhbiByZWZlciBmbG93IGFkbWlzc2lvbiBhbmQNCj4+IHRlcm1pbmF0aW9uIGRlY2lz
aW9ucyB0byBhIGNlbnRyYWwgZGVjaXNpb24gcG9pbnQgKHVzaW5nIGUuZy4gQ09QUyksIHdoaWNo
IHdpbGwNCj4+IHJlc3BvbmQgdG8gdGhlIFBDTi1pbmdyZXNzIGFzIHBlciBSRkMyNzUzLiAoQWx0
ZXJuYXRpdmVseSB0aGUgUENOLWluZ3Jlc3MNCj4+IGNvdWxkIGl0c2VsZiBiZSB0aGUgcG9saWN5
IGRlY2lzaW9uIHBvaW50LikNCj4+ICogUmVmZXIgdG8gdGhpcyBuZXcgUEJBQyBzZWN0aW9uIGZy
b20gU2VjdGlvbiAzLjExIGdpdmluZyB0aGUgYWRtaXNzaW9uDQo+PiBkZWNpc2lvbiBwcm9jZWR1
cmUuDQoNClRoYW5rcywNCi0tRGF2aWQNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0NCkRhdmlkIEwuIEJsYWNrLCBEaXN0aW5ndWlzaGVkIEVuZ2lu
ZWVyDQpFTUMgQ29ycG9yYXRpb24sIDE3NiBTb3V0aCBTdC4sIEhvcGtpbnRvbiwgTUEgIDAxNzQ4
DQorMSAoNTA4KSAyOTMtNzk1MyAgICAgICAgICAgICBGQVg6ICsxICg1MDgpIDI5My03Nzg2DQpk
YXZpZC5ibGFja0BlbWMuY29tICAgICAgICBNb2JpbGU6ICsxICg5NzgpIDM5NC03NzU0DQotLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCkZyb206
IHRzdndnLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0c3Z3Zy1ib3VuY2VzQGlldGYub3JnXSBP
biBCZWhhbGYgT2Yga2FyYWdpYW5AY3MudXR3ZW50ZS5ubA0KU2VudDogU2F0dXJkYXksIE1hcmNo
IDA5LCAyMDEzIDI6NDggQU0NClRvOiBib2IuYnJpc2NvZUBidC5jb20NCkNjOiBwaGlsaXAuZWFy
ZGxleUBidC5jb207IGFudXJhZ2JAY2lzY28uY29tOyB0c3Z3Z0BpZXRmLm9yZw0KU3ViamVjdDog
UmU6IFt0c3Z3Z10gZHJhZnQtaWV0Zi10c3Z3Zy1yc3ZwLXBjbi0wMw0KDQpIaSBCb2IsDQoNClRo
YW5rcyBmb3IgeW91ciBjb21tZW50cyENCg0KSW4gdGhlIGJlbG93IGVtYWlsIHlvdSBwcm9wb3Nl
IHRvIGludHJvZHVjZSB0aGUgZGVzY3JpcHRpb24gb2YgYSBwb2xpY3ktYmFzZWQgYWRtaXNzaW9u
IGNvbnRyb2wgKFBCQUMpIGFyY2hpdGVjdHVyZSBpbiBvcmRlciB0byByZXNwb25kIHRvIHRoZSBh
bnN3ZXIgYWJvdXQgb24tcGF0aCB2cyBvZmYtcGF0aCBwb2xpY3kuDQpJbiBteSBvcGluaW9uIGlm
IGl0IGlzIHRvIGludHJvZHVjZSBhIG5ldyBwb2xpY3ktYmFzZWQgYWRtaXNzaW9uIGNvbnRyb2wg
KFBCQUMpIGFyY2hpdGVjdHVyZSB0byBiZSB1c2VkIGluIHRoZSBjb250ZXh0IG9mIFBDTiwgdGhl
biB0aGlzIHNob3VsZCBiZSBkb25lIGluIGFub3RoZXIgZG9jdW1lbnQgYW5kIG5vdCBpbiB0aGUg
ZHJhZnQtaWV0Zi10c3Z3Zy1yc3ZwLXBjbi4NCg0KUmVnYXJkaW5nIHRoZSBhbnN3ZXIgYWJvdXQg
b24tcGF0aCB2cyBvZmYtcGF0aCBwb2xpY3ksIGluIGRyYWZ0LWlldGYtdHN2d2ctcnN2cC1wY24t
MDQgSSBoYXZlIGluY2x1ZGVkIHRoZSBhcmd1bWVudGF0aW9uIHRoYXQgSSBwcm9wb3NlZCBhcyBh
bnN3ZXIgdG8gdGhlIGNvbW1lbnQgb24tcGF0aCB2cyBvZmYtcGF0aCBzaWduYWxpbmcgcHJvdmlk
ZWQgYnkgS2VuLCBhbmQgd2hpY2ggaGUgYWN0dWFsbHkgYWdyZWVkIHdpdGghDQoNCkJlc3QgcmVn
YXJkcywNCkdlb3JnaW9zDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9t
OiBCb2IgQnJpc2NvZSBbbWFpbHRvOmJvYi5icmlzY29lQGJ0LmNvbTxodHRwczovL3hzLnV0d2Vu
dGUubmwvb3dhL3JlZGlyLmFzcHg/Qz1OYnVtOWFIZmowS1ZhNlFXb1dRZFVtc0dXaHQ0cHM4SXNV
cUtRREFQWk5rMGo4ZmJYTmdkZjViZGZfalphN2RSTERpNkFsSzZ3eTAuJlVSTD1tYWlsdG8lM2Fi
b2IuYnJpc2NvZSU0MGJ0LmNvbT5dDQo+IFNlbnQ6IHZyaWpkYWcgOSBub3ZlbWJlciAyMDEyIDE2
OjMzDQo+IFRvOiBLYXJhZ2lhbm5pcywgRy4gKEVXSSkNCj4gQ2M6IGNhcmxiZXJnQGcxMS5vcmcu
dWs7IGFudXJhZ2JAY2lzY28uY29tOyB0c3Z3Z0BpZXRmLm9yZzsgRUFSRExFWSwgUGhpbA0KPiBT
dWJqZWN0OiBSZTogW3RzdndnXSBkcmFmdC1pZXRmLXRzdndnLXJzdnAtcGNuLTAzDQo+DQo+IEdl
b3JnaW9zLA0KPg0KPiBJIHNoYWxsIHBvc3QgbXkgZnVsbCByZXZpZXcgb2YgdGhpcyBkcmFmdCBp
biB0aGUgbmV4dCBmZXcgZGF5cyAobmVlZHMgdHlwaW5nIHVwIC0NCj4gY3VycmVudGx5IHNjcmli
YmxlZCBvbiBhIHBhcGVyIGNvcHkpLiBUaGlzIGVtYWlsIGlzIHNvbGVseSBpbiByZXNwb25zZSB0
byB5b3VyDQo+IGFuc3dlciBhYm91dCBvbi1wYXRoIHZzIG9mZi1wYXRoIHBvbGljeS4NCj4NCj4g
QXQgMTg6NTUgMDQvMTEvMjAxMiwga2FyYWdpYW5AY3MudXR3ZW50ZS5ubCB3cm90ZToNCj4gPlNv
IGluIHRoaXMgY2FzZSBhbiBhZGRpdGlvbmFsIHNpZ25hbGluZyBwcm90b2NvbCB3aWxsIGJlIG5l
ZWRlZCB0byBiZQ0KPiA+c3BlY2lmaWVkIHRoYXQgY292ZXJzIHRoZSBzaWduYWxpbmcgYmV0d2Vl
biB0aGUgUENOLWVncmVzcy1ub2RlIGFuZCB0aGUNCj4gPmNlbnRyYWxpemVkIG5vZGUgYW5kIGJl
dHdlZW4gUENOLWluZ3Jlc3Mtbm9kZSBhbmQgdGhlIGNlbnRyYWxpemVkIG5vZGUuDQo+ID5JbiBQ
Q04gd2UgZGVjZGlkZWQgdG8gb25seSBmb2N1cyBvbiB0aGUgc3BlY2lmaWNhdGlvbiBvZiB0aGUg
c2lnbmFsaW5nDQo+ID5wcm90b2NvbCB0aGF0IGNvbXBsZXRlcyB0aGUgZmVlZGJhY2sgbG9vcCBm
cm9tIFBDTi1lZ3Jlc3Mtbm9kZSB0bw0KPiA+UENOLWluZ3Jlc3Mtbm9kZSBhbmQgdG8gZm9jdXMg
b24gdGhlIHNpZ25hbGluZyBwcm90b2NvbCB1c2VkIGJldHdlZW4NCj4gPnRoZSBlZGdlIG5vZGVz
IGFuZCB0aGUgY2VudHJhbGl6ZWQgbm9kZS4NCj4NCj4gV2hlbiBJL3dlIG9yaWdpbmFsbHkgZGVz
aWduZWQgQ0wtUENOIG92ZXIgUlNWUCAoMjAwNSksIHRoZSBpZGVhIHdhcyB0aGF0IGl0DQo+IHdv
dWxkIGZpdCB3aXRoIHRoZSBwb2xpY3ktYmFzZWQgYWRtaXNzaW9uIGNvbnRyb2wgKFBCQUMpIGFy
Y2hpdGVjdHVyZSBvZg0KPiBSRkMyNzUzLiBJbiB0aGlzIGFyY2hpdGVjdHVyZSwgYW4gSW50c2Vy
diBub2RlIGF0IHRoZSBpbmdyZXNzIHRvIGEgZG9tYWluIGlzDQo+IHRoZSBwb2xpY3kgZW5mb3Jj
ZW1lbnQgcG9pbnQgKFBFUCksIGFuZCBpdCByZWZlcnMgdG8gYSBsb2dpY2FsbHkgY2VudHJhbGlz
ZWQNCj4gJ3BvbGljeSBkZWNpc2lvbiBwb2ludCcgKFBEUCkgZm9yIGRlY2lzaW9ucyBvbiB3aGlj
aCBmbG93cyB0byBibG9jay90ZXJtaW5hdGUsDQo+IHR5cGljYWxseSB1c2luZyBDT1BTLg0KPg0K
PiBUbyBtYWtlIHRoaXMgZG9jIGZpdCB0aGUgUEJBQyBmcmFtZXdvcmssIGFsbCB3ZSBoYXZlIHRv
IGRvIGlzOg0KPiAqIERlc2NyaWJlIHRoZSBQQ04taW5ncmVzcyBvbmx5IGFzIHRoZSBQQ04taW5n
cmVzcyBhbmQgbm90IGFzIHRoZSBkZWNpc2lvbg0KPiBwb2ludCAoZmluZCAnZGVjaXNpb24nIHRo
cm91Z2hvdXQgZG9jIGFuZCBmaXgpLg0KPiAqIEFkZCBhIHNlY3Rpb24gc2F5aW5nIHRoZSBQQ04t
aW5ncmVzcyBjYW4gcmVmZXIgZmxvdyBhZG1pc3Npb24gYW5kDQo+IHRlcm1pbmF0aW9uIGRlY2lz
aW9ucyB0byBhIGNlbnRyYWwgZGVjaXNpb24gcG9pbnQgKHVzaW5nIGUuZy4gQ09QUyksIHdoaWNo
IHdpbGwNCj4gcmVzcG9uZCB0byB0aGUgUENOLWluZ3Jlc3MgYXMgcGVyIFJGQzI3NTMuIChBbHRl
cm5hdGl2ZWx5IHRoZSBQQ04taW5ncmVzcw0KPiBjb3VsZCBpdHNlbGYgYmUgdGhlIHBvbGljeSBk
ZWNpc2lvbiBwb2ludC4pDQo+ICogUmVmZXIgdG8gdGhpcyBuZXcgUEJBQyBzZWN0aW9uIGZyb20g
U2VjdGlvbiAzLjExIGdpdmluZyB0aGUgYWRtaXNzaW9uDQo+IGRlY2lzaW9uIHByb2NlZHVyZS4N
Cj4NCj4gKiBTb21lIHBlb3BsZSBtaWdodCB0aGluayB0aGlzIG1lYW5zIENPUFMgd2lsbCBuZWVk
IG5ldyBwcm90b2NvbA0KPiBlbGVtZW50cyB0byBjYXJyeSBQQ04gbWFya2luZyByYXRlcyB0byB0
aGUgcG9saWN5IGRlY2lzaW9uIHBvaW50LiBCdXQgUENODQo+IG1hcmtpbmcgcmF0ZXMgYXJlIGly
cmVsZXZhbnQgdG8gdGhlIHBvbGljeSBkZWNpc2lvbjogdGhlIFBDTi1pbmdyZXNzIGp1c3QgdXNl
cw0KPiBQQ04gdG8gZGV0ZXJtaW5lIHdoZXRoZXIgaXQgbmVlZHMgdG8gYmxvY2sgb3IgdGVybWlu
YXRlLCBhbmQgaXQgcmVmZXJzIHRvIHRoZQ0KPiBwb2xpY3kgZGVjaXNpb24gcG9pbnQgZm9yIHdo
aWNoIGZsb3dzIHRvIGJsb2NrL3Rlcm1pbmF0ZS4NCj4NCj4gKiBVbmZvcnR1bmF0ZWx5LCBuZWl0
aGVyIG9mIHRoZSB0d28gUENOIHN5c3RlbSBkZXNjcmlwdGlvbnMgW1JGQzY2NjEsDQo+IFJGQzY2
NjJdIGRlc2NyaWJlIGEgUEJBQy1iYXNlZCBjYXNlLiBUaGUgYXJjaGl0ZWN0dXJlIFtSRkM1NTU5
XSByZWZlcnMgdG8NCj4gdGhlIFBCQUMgZnJhbWV3b3JrIFtSRkMyNzUzXSBidXQgdW5mb3J0dW5h
dGVseSBkb2Vzbid0IHNwZWxsIG91dCBob3cgaXQNCj4gZml0cy4gT3JpZ2luYWxseSwgSSByZWZl
cmVuY2VkIFBCQUMgZnJvbSBSRkM1NTU5LCBidXQganVzdCBhcyB0aGUgUENOIHctZyB3YXMNCj4g
Y2xvc2luZyBJIHJlYWxpc2VkIHRoYXQgKHNvbWU/KSBvdGhlcnMgaW4gdGhlIFBDTiB3LWcgd2Vy
ZSB3b3JraW5nIHVuZGVyIHRoZQ0KPiBhc3N1bXB0aW9uIHRoYXQgdGhlIG9ubHkgd2F5IHRvIHRh
bGsgdG8gYSBjZW50cmFsaXNlZCBwb2xpY3kgbm9kZSB3YXMgZnJvbQ0KPiB0aGUgZWdyZXNzLCBw
b3NzaWJseSB3aXRob3V0IGJlaW5nIGF3YXJlIG9mIHRoZSBjb250ZW50cyBvZiBSRkMyNzUzLg0K
Pg0KPiBJIHRoaW5rIGl0J3MgT0sgdG8gaW50cm9kdWNlIGEgbmV3IGFyY2hpdGVjdHVyYWwgYXJy
YW5nZW1lbnQgaW4gdGhpcyBSU1ZQIGRvYywNCj4gZ2l2ZW4gUkZDMjc1MyBpcyBzcGVjaWZpYyB0
byB0aGUgd2F5IFJTVlAgd29ya3MuDQo+DQo+DQo+IEJvYg0KDQo=

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

PGh0bWwgZGlyPSJsdHIiPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUi
IGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD1XaW5kb3dzLTEyNTIiPg0KPHN0eWxlPkBmb250
LWZhY2Ugew0KCWZvbnQtZmFtaWx5OiBDYWxpYnJpOw0KfQ0KQGZvbnQtZmFjZSB7DQoJZm9udC1m
YW1pbHk6IFRhaG9tYTsNCn0NCkBwYWdlIFdvcmRTZWN0aW9uMSB7bWFyZ2luOiAxLjBpbiAxLjBp
biAxLjBpbiAxLjBpbjsgfQ0KUC5Nc29Ob3JtYWwgew0KCU1BUkdJTjogMGluIDBpbiAwcHQ7IEZP
TlQtRkFNSUxZOiAiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiOyBGT05ULVNJWkU6IDEycHQNCn0N
CkxJLk1zb05vcm1hbCB7DQoJTUFSR0lOOiAwaW4gMGluIDBwdDsgRk9OVC1GQU1JTFk6ICJUaW1l
cyBOZXcgUm9tYW4iLCJzZXJpZiI7IEZPTlQtU0laRTogMTJwdA0KfQ0KRElWLk1zb05vcm1hbCB7
DQoJTUFSR0lOOiAwaW4gMGluIDBwdDsgRk9OVC1GQU1JTFk6ICJUaW1lcyBOZXcgUm9tYW4iLCJz
ZXJpZiI7IEZPTlQtU0laRTogMTJwdA0KfQ0KQTpsaW5rIHsNCglDT0xPUjogYmx1ZTsgVEVYVC1E
RUNPUkFUSU9OOiB1bmRlcmxpbmUNCn0NClNQQU4uTXNvSHlwZXJsaW5rIHsNCglDT0xPUjogYmx1
ZTsgVEVYVC1ERUNPUkFUSU9OOiB1bmRlcmxpbmUNCn0NCkE6dmlzaXRlZCB7DQoJQ09MT1I6IHB1
cnBsZTsgVEVYVC1ERUNPUkFUSU9OOiB1bmRlcmxpbmUNCn0NClNQQU4uTXNvSHlwZXJsaW5rRm9s
bG93ZWQgew0KCUNPTE9SOiBwdXJwbGU7IFRFWFQtREVDT1JBVElPTjogdW5kZXJsaW5lDQp9DQpQ
LmVtYWlscXVvdGUgew0KCUJPUkRFUi1CT1RUT006IG1lZGl1bSBub25lOyBCT1JERVItTEVGVDog
bWVkaXVtIG5vbmU7IFBBRERJTkctQk9UVE9NOiAwaW47IE1BUkdJTjogMGluIDBpbiAwcHQgMXB0
OyBQQURESU5HLUxFRlQ6IDBpbjsgUEFERElORy1SSUdIVDogMGluOyBGT05ULUZBTUlMWTogIlRp
bWVzIE5ldyANClJvbWFuIiwic2VyaWYiOyBGT05ULVNJWkU6IDEycHQ7IEJPUkRFUi1UT1A6IG1l
ZGl1bSBub25lOyBCT1JERVItUklHSFQ6IG1lZGl1bSBub25lOyBQQURESU5HLVRPUDogMGluDQp9
DQpMSS5lbWFpbHF1b3RlIHsNCglCT1JERVItQk9UVE9NOiBtZWRpdW0gbm9uZTsgQk9SREVSLUxF
RlQ6IG1lZGl1bSBub25lOyBQQURESU5HLUJPVFRPTTogMGluOyBNQVJHSU46IDBpbiAwaW4gMHB0
IDFwdDsgUEFERElORy1MRUZUOiAwaW47IFBBRERJTkctUklHSFQ6IDBpbjsgRk9OVC1GQU1JTFk6
ICJUaW1lcyBOZXcgDQpSb21hbiIsInNlcmlmIjsgRk9OVC1TSVpFOiAxMnB0OyBCT1JERVItVE9Q
OiBtZWRpdW0gbm9uZTsgQk9SREVSLVJJR0hUOiBtZWRpdW0gbm9uZTsgUEFERElORy1UT1A6IDBp
bg0KfQ0KRElWLmVtYWlscXVvdGUgew0KCUJPUkRFUi1CT1RUT006IG1lZGl1bSBub25lOyBCT1JE
RVItTEVGVDogbWVkaXVtIG5vbmU7IFBBRERJTkctQk9UVE9NOiAwaW47IE1BUkdJTjogMGluIDBp
biAwcHQgMXB0OyBQQURESU5HLUxFRlQ6IDBpbjsgUEFERElORy1SSUdIVDogMGluOyBGT05ULUZB
TUlMWTogIlRpbWVzIE5ldyANClJvbWFuIiwic2VyaWYiOyBGT05ULVNJWkU6IDEycHQ7IEJPUkRF
Ui1UT1A6IG1lZGl1bSBub25lOyBCT1JERVItUklHSFQ6IG1lZGl1bSBub25lOyBQQURESU5HLVRP
UDogMGluDQp9DQpTUEFOLkVtYWlsU3R5bGUxOSB7DQoJRk9OVC1TVFlMRTogbm9ybWFsOyBGT05U
LUZBTUlMWTogIkNvdXJpZXIgTmV3IjsgQ09MT1I6IGJsYWNrOyBGT05ULVdFSUdIVDogbm9ybWFs
OyBURVhULURFQ09SQVRJT046IG5vbmUNCn0NCi5Nc29DaHBEZWZhdWx0IHsNCglGT05ULVNJWkU6
IDEwcHQNCn0NCkRJVi5Xb3JkU2VjdGlvbjEgew0KCQ0KfQ0KPC9zdHlsZT48c3R5bGUgaWQ9Im93
YVBhcmFTdHlsZSI+UCB7DQoJTUFSR0lOLVRPUDogMHB4OyBNQVJHSU4tQk9UVE9NOiAwcHgNCn0N
Cjwvc3R5bGU+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgdmxpbms9InB1cnBsZSIgbGlu
az0iYmx1ZSIgb2NzaT0iMCIgZlBTdHlsZT0iMSI+PGZvbnQgc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOiMxRjQ5N0QiPg0KSGkgR2Vvcmdpb3MsPGJyPjxicj4oU3RpbGwgcG9zdGluZyBhcyBh
biBpbmRpdmlkdWFsLCBub3QgYSBXRyBjby1jaGFpcik8YnI+PGJyPlRoZW4gSSBndWVzcyB3ZSBk
aXNhZ3JlZSBvbiB3aGF0IGEgZnJhbWV3b3JrIGlzLCBiZWNhdXNlIEkgYWdyZWUgIHRoYXQgYSBm
dWxsIFBCQUMgZnJhbWV3b3JrIHNob3VsZCBub3QgYmUgZGVzY3JpYmVkIGluIHRoaXMgZHJhZnQs
IGJ1dCBJIGRvbid0IHZpZXcgdGhlIGNoYW5nZXMgdGhhdCBCb2IgaXMgYXNraW5nIGZvciAocHJp
bWFyaWx5IHRvIHBvaW50IG91dCB0aGF0IHRoZSBQQ04gZWRnZSBhbmQgdGhlIGRlY2lzaW9uIHBv
aW50IG1heSBiZSBzZXBhcmF0ZSkgYXMgY29taW5nIGNsb3NlIHRvIGRlc2NyaWJpbmcgc3VjaCBh
IGZyYW1ld29yay48YnI+DTxicj5UaGFua3MsIC0tRGF2aWQgKysrU2VudCBmcm9tIEJsYWNrYmVy
cnk8L2ZvbnQ+PGJyPiZuYnNwOzxicj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10
b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxmb250
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4NCjxiPkZyb208L2I+OiBrYXJhZ2lhbkBjcy51dHdlbnRl
Lm5sIFttYWlsdG86a2FyYWdpYW5AY3MudXR3ZW50ZS5ubF0NPGJyPjxiPlNlbnQ8L2I+OiBTYXR1
cmRheSwgTWFyY2ggMDksIDIwMTMgMDI6MjggUE08YnI+PGI+VG88L2I+OiBCbGFjaywgRGF2aWQ7
IGJvYi5icmlzY29lQGJ0LmNvbSAmbHQ7Ym9iLmJyaXNjb2VAYnQuY29tJmd0Ow08YnI+PGI+Q2M8
L2I+OiBwaGlsaXAuZWFyZGxleUBidC5jb20gJmx0O3BoaWxpcC5lYXJkbGV5QGJ0LmNvbSZndDs7
IGFudXJhZ2JAY2lzY28uY29tICZsdDthbnVyYWdiQGNpc2NvLmNvbSZndDs7IHRzdndnQGlldGYu
b3JnICZsdDt0c3Z3Z0BpZXRmLm9yZyZndDsNPGJyPjxiPlN1YmplY3Q8L2I+OiBSRTogUlNWUCBQ
Q04gYW5kIFBCQUMNPGJyPjwvZm9udD4mbmJzcDs8YnI+PC9kaXY+DQoNCjxkaXYgc3R5bGU9IkZP
TlQtRkFNSUxZOiBUYWhvbWE7IERJUkVDVElPTjogbHRyOyBDT0xPUjogIzAwMDAwMDsgRk9OVC1T
SVpFOiAxMHB0Ij4NCjxwPkhpIERhdmlkLDwvcD4NCjxwPiZuYnNwOzwvcD4NCjxwPlRoYW5rcyBm
b3IgeW91ciBjb21tZW50ITxicj4NCjwvcD4NCjxwPldoYXQgSSBtZWFudCBpcyB0aGF0IEJvYiB3
b3VsZCBsaWtlIHRvIHNlZSBhIGRlc2NyaXB0aW9uIG9mIFBDTiBiYXNlZCBQQkFDIGZyYW1ld29y
ayBpbiB0aGUgUlNWUCBvdmVyIFBDTiBkcmFmdA0KPC9wPg0KPHA+dGhhdCBpcyBub3QgcmVhbHkm
bmJzcDtzcGVjaWZpZWQgaW4gYW55IG90aGVyIFBDTiBkb2N1bWVudHMuIDwvcD4NCjxwPkluIG15
IG9waW5pb24gdGhlIFJTVlAgb3ZlciBQQ04gZHJhZnQgaXMgbm90IHRoZSBkcmFmdCB0aGF0IHNo
b3VsZCBpbnRyb2R1Y2Ugc3VjaCBhIFBCQUMgZnJhbWV3b3JrLjwvcD4NCjxwPiZuYnNwOzwvcD4N
CjxwPkJlc3QgcmVnYXJkcyw8L3A+DQo8cD5HZW9yZ2lvczwvcD4NCjxwPiZuYnNwOzwvcD4NCjxw
PiZuYnNwOzwvcD4NCjxwPiZuYnNwOzwvcD4NCjxwPiZuYnNwOzwvcD4NCjxociB0YWJpbmRleD0i
LTEiPg0KPGRpdiBzdHlsZT0iRElSRUNUSU9OOiBsdHIiIGlkPSJkaXZScEY3OTQ4ODYiPjxmb250
IGNvbG9yPSIjMDAwMDAwIiBzaXplPSIyIiBmYWNlPSJUYWhvbWEiPjxiPlZhbjo8L2I+IEJsYWNr
LCBEYXZpZCBbZGF2aWQuYmxhY2tAZW1jLmNvbV08YnI+DQo8Yj5WZXJ6b25kZW46PC9iPiB6YXRl
cmRhZyA5IG1hYXJ0IDIwMTMgMTk6MTQ8YnI+DQo8Yj5Ubzo8L2I+IEthcmFnaWFubmlzLCBHLiAo
RVdJKTsgYm9iLmJyaXNjb2VAYnQuY29tPGJyPg0KPGI+Q2M6PC9iPiBwaGlsaXAuZWFyZGxleUBi
dC5jb207IGFudXJhZ2JAY2lzY28uY29tOyB0c3Z3Z0BpZXRmLm9yZzxicj4NCjxiPk9uZGVyd2Vy
cDo8L2I+IFJTVlAgUENOIGFuZCBQQkFDPGJyPg0KPC9mb250Pjxicj4NCjwvZGl2Pg0KPGRpdj48
L2Rpdj4NCjxkaXY+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9IkZPTlQtRkFNSUxZOiAnQ291cmllciBOZXcnOyBDT0xPUjogYmxh
Y2s7IEZPTlQtU0laRTogMTBwdCI+SGkgR2Vvcmdpb3MsPC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTogJ0NvdXJpZXIgTmV3JzsgQ09MT1I6
IGJsYWNrOyBGT05ULVNJWkU6IDEwcHQiPjwvc3Bhbj4mbmJzcDs8L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6ICdDb3VyaWVyIE5ldyc7IENPTE9SOiBi
bGFjazsgRk9OVC1TSVpFOiAxMHB0Ij4mbHQ7V0cgY28tY2hhaXIgaGF0IE9GRiZndDs8L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9IkZPTlQtRkFNSUxZOiAnQ291
cmllciBOZXcnOyBDT0xPUjogYmxhY2s7IEZPTlQtU0laRTogMTBwdCI+PC9zcGFuPiZuYnNwOzwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTogJ0NvdXJp
ZXIgTmV3JzsgQ09MT1I6IGJsYWNrOyBGT05ULVNJWkU6IDEwcHQiPkkgdGhpbmsgeW914oCZdmUg
bWlzc2VkIHRoZSBwb2ludCBoZXJlOjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6ICdDb3VyaWVyIE5ldyc7IENPTE9SOiBibGFjazsgRk9O
VC1TSVpFOiAxMHB0Ij48L3NwYW4+Jm5ic3A7PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9IkZPTlQtRkFNSUxZOiAnQ291cmllciBOZXcnOyBDT0xPUjogYmxhY2s7IEZPTlQt
U0laRTogMTBwdCI+Jmd0OyBJbiBteSBvcGluaW9uIGlmIGl0IGlzIHRvIGludHJvZHVjZSBhIG5l
dyBwb2xpY3ktYmFzZWQgYWRtaXNzaW9uIGNvbnRyb2wgKFBCQUMpPC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTogJ0NvdXJpZXIgTmV3Jzsg
Q09MT1I6IGJsYWNrOyBGT05ULVNJWkU6IDEwcHQiPiZndDsgYXJjaGl0ZWN0dXJlIHRvIGJlIHVz
ZWQgaW4gdGhlIGNvbnRleHQgb2YgUENOLCB0aGVuIHRoaXMgc2hvdWxkIGJlIGRvbmUmbmJzcDtp
biBhbm90aGVyPC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJG
T05ULUZBTUlMWTogJ0NvdXJpZXIgTmV3JzsgQ09MT1I6IGJsYWNrOyBGT05ULVNJWkU6IDEwcHQi
PiZndDsgZG9jdW1lbnQgYW5kIG5vdCZuYnNwO2luIHRoZSBkcmFmdC1pZXRmLXRzdndnLXJzdnAt
cGNuLjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iRk9OVC1G
QU1JTFk6ICdDb3VyaWVyIE5ldyc7IENPTE9SOiBibGFjazsgRk9OVC1TSVpFOiAxMHB0Ij48L3Nw
YW4+Jm5ic3A7PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9IkZPTlQtRkFN
SUxZOiAnQ291cmllciBOZXcnOyBDT0xPUjogYmxhY2s7IEZPTlQtU0laRTogMTBwdCI+SSBkbyBu
b3QgYmVsaWV2ZSB0aGF0IEJvYiBpcyBhc2tpbmcgdGhhdCB0aGlzIGRyYWZ0IGFkZCBhIFBCQUMg
YXJjaGl0ZWN0dXJlLCBidXQgcmF0aGVyIHRoYXQgbWlub3IgY2hhbmdlcyBiZSBtYWRlIHNvIHRo
YXQgdGhpcyBkcmFmdCBpcyBjb25zaXN0ZW50IHdpdGggdGhlIFBCQUMgYXJjaGl0ZWN0dXJhbA0K
IGFwcHJvYWNoOjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Rk9OVC1GQU1JTFk6ICdDb3VyaWVyIE5ldyc7IENPTE9SOiBibGFjazsgRk9OVC1TSVpFOiAxMHB0
Ij48L3NwYW4+Jm5ic3A7PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyZndDsgVG8gbWFr
ZSB0aGlzIGRvYyBmaXQgdGhlIFBCQUMgZnJhbWV3b3JrLCBhbGwgd2UgaGF2ZSB0byBkbyBpczo8
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7Jmd0OyAqIERlc2NyaWJlIHRoZSBQQ04taW5n
cmVzcyBvbmx5IGFzIHRoZSBQQ04taW5ncmVzcyBhbmQgbm90IGFzIHRoZSBkZWNpc2lvbjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDsmZ3Q7IHBvaW50IChmaW5kICdkZWNpc2lvbicgdGhy
b3VnaG91dCBkb2MgYW5kIGZpeCkuPC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyZndDsg
KiBBZGQgYSBzZWN0aW9uIHNheWluZyB0aGUgUENOLWluZ3Jlc3MgY2FuIHJlZmVyIGZsb3cgYWRt
aXNzaW9uIGFuZDwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDsmZ3Q7IHRlcm1pbmF0aW9u
IGRlY2lzaW9ucyB0byBhIGNlbnRyYWwgZGVjaXNpb24gcG9pbnQgKHVzaW5nIGUuZy4gQ09QUyks
IHdoaWNoIHdpbGw8L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7Jmd0OyByZXNwb25kIHRv
IHRoZSBQQ04taW5ncmVzcyBhcyBwZXIgUkZDMjc1My4gKEFsdGVybmF0aXZlbHkgdGhlIFBDTi1p
bmdyZXNzPC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyZndDsgY291bGQgaXRzZWxmIGJl
IHRoZSBwb2xpY3kgZGVjaXNpb24gcG9pbnQuKTwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZn
dDsmZ3Q7ICogUmVmZXIgdG8gdGhpcyBuZXcgUEJBQyBzZWN0aW9uIGZyb20gU2VjdGlvbiAzLjEx
IGdpdmluZyB0aGUgYWRtaXNzaW9uPC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyZndDsg
ZGVjaXNpb24gcHJvY2VkdXJlLjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzwvcD4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6ICdD
b3VyaWVyIE5ldyc7IENPTE9SOiBibGFjazsgRk9OVC1TSVpFOiAxMHB0Ij5UaGFua3MsPGJyPg0K
LS1EYXZpZDxicj4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS08YnI+DQpEYXZpZCBMLiBCbGFjaywgRGlzdGluZ3Vpc2hlZCBFbmdpbmVlcjxicj4N
CkVNQyBDb3Jwb3JhdGlvbiwgMTc2IFNvdXRoIFN0LiwgSG9wa2ludG9uLCBNQSZuYnNwOyAwMTc0
ODxicj4NCiYjNDM7MSAoNTA4KSAyOTMtNzk1MyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBGQVg6ICYjNDM7MSAo
NTA4KSAyOTMtNzc4Njxicj4NCmRhdmlkLmJsYWNrQGVtYy5jb20mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgTW9iaWxlOiAmIzQzOzEgKDk3OCkgMzk0LTc3NTQ8YnI+
DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPC9z
cGFuPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTogJ0NvdXJpZXIgTmV3JzsgQ09MT1I6IGJsYWNr
OyBGT05ULVNJWkU6IDExcHQiPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTogJ0NvdXJpZXIgTmV3JzsgQ09MT1I6IGJsYWNr
OyBGT05ULVNJWkU6IDEwcHQiPjwvc3Bhbj4mbmJzcDs8L3A+DQo8ZGl2IHN0eWxlPSJCT1JERVIt
Qk9UVE9NOiBtZWRpdW0gbm9uZTsgQk9SREVSLUxFRlQ6IGJsdWUgMS41cHQgc29saWQ7IFBBRERJ
TkctQk9UVE9NOiAwaW47IFBBRERJTkctTEVGVDogNHB0OyBQQURESU5HLVJJR0hUOiAwaW47IEJP
UkRFUi1UT1A6IG1lZGl1bSBub25lOyBCT1JERVItUklHSFQ6IG1lZGl1bSBub25lOyBQQURESU5H
LVRPUDogMGluIj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJCT1JERVItQk9UVE9NOiBtZWRpdW0gbm9u
ZTsgQk9SREVSLUxFRlQ6IG1lZGl1bSBub25lOyBQQURESU5HLUJPVFRPTTogMGluOyBQQURESU5H
LUxFRlQ6IDBpbjsgUEFERElORy1SSUdIVDogMGluOyBCT1JERVItVE9QOiAjYjVjNGRmIDFwdCBz
b2xpZDsgQk9SREVSLVJJR0hUOiBtZWRpdW0gbm9uZTsgUEFERElORy1UT1A6IDNwdCI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6ICdUYWhvbWEnLCdz
YW5zLXNlcmlmJzsgRk9OVC1TSVpFOiAxMHB0Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9
IkZPTlQtRkFNSUxZOiAnVGFob21hJywnc2Fucy1zZXJpZic7IEZPTlQtU0laRTogMTBwdCI+IHRz
dndnLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0c3Z3Zy1ib3VuY2VzQGlldGYub3JnXQ0KPGI+
T24gQmVoYWxmIE9mIDwvYj5rYXJhZ2lhbkBjcy51dHdlbnRlLm5sPGJyPg0KPGI+U2VudDo8L2I+
IFNhdHVyZGF5LCBNYXJjaCAwOSwgMjAxMyAyOjQ4IEFNPGJyPg0KPGI+VG86PC9iPiBib2IuYnJp
c2NvZUBidC5jb208YnI+DQo8Yj5DYzo8L2I+IHBoaWxpcC5lYXJkbGV5QGJ0LmNvbTsgYW51cmFn
YkBjaXNjby5jb207IHRzdndnQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbdHN2
d2ddIGRyYWZ0LWlldGYtdHN2d2ctcnN2cC1wY24tMDM8L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6ICdDb3VyaWVyIE5ldyc7IENPTE9SOiBi
bGFjazsgRk9OVC1TSVpFOiAxMHB0Ij5IaSBCb2IsPC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTogJ0NvdXJpZXIgTmV3JzsgQ09MT1I6IGJs
YWNrIj48L3NwYW4+Jm5ic3A7PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
IkZPTlQtRkFNSUxZOiAnQ291cmllciBOZXcnOyBDT0xPUjogYmxhY2s7IEZPTlQtU0laRTogMTBw
dCI+VGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzITwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6ICdDb3VyaWVyIE5ldyc7IENPTE9SOiBibGFj
ayI+PC9zcGFuPiZuYnNwOzwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJG
T05ULUZBTUlMWTogJ0NvdXJpZXIgTmV3JzsgQ09MT1I6IGJsYWNrOyBGT05ULVNJWkU6IDEwcHQi
PkluIHRoZSBiZWxvdyBlbWFpbCB5b3UgcHJvcG9zZSB0byBpbnRyb2R1Y2UgdGhlIGRlc2NyaXB0
aW9uIG9mIGEgcG9saWN5LWJhc2VkIGFkbWlzc2lvbiBjb250cm9sIChQQkFDKSBhcmNoaXRlY3R1
cmUgaW4gb3JkZXIgdG8gcmVzcG9uZCB0byB0aGUgYW5zd2VyIGFib3V0IG9uLXBhdGgNCiB2cyBv
ZmYtcGF0aCBwb2xpY3kuIDwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iRk9OVC1GQU1JTFk6ICdDb3VyaWVyIE5ldyc7IENPTE9SOiBibGFjazsgRk9OVC1TSVpF
OiAxMHB0Ij5JbiBteSBvcGluaW9uIGlmIGl0IGlzIHRvIGludHJvZHVjZSBhIG5ldyBwb2xpY3kt
YmFzZWQgYWRtaXNzaW9uIGNvbnRyb2wgKFBCQUMpIGFyY2hpdGVjdHVyZSB0byBiZSB1c2VkIGlu
IHRoZSBjb250ZXh0IG9mIFBDTiwgdGhlbiB0aGlzIHNob3VsZCBiZSBkb25lJm5ic3A7aW4gYW5v
dGhlciBkb2N1bWVudA0KIGFuZCBub3QmbmJzcDtpbiB0aGUgZHJhZnQtaWV0Zi10c3Z3Zy1yc3Zw
LXBjbi48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9IkZPTlQt
RkFNSUxZOiAnQ291cmllciBOZXcnOyBDT0xPUjogYmxhY2siPjwvc3Bhbj4mbmJzcDs8L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6ICdDb3VyaWVyIE5l
dyc7IENPTE9SOiBibGFjazsgRk9OVC1TSVpFOiAxMHB0Ij5SZWdhcmRpbmcgdGhlIGFuc3dlciBh
Ym91dCBvbi1wYXRoIHZzIG9mZi1wYXRoIHBvbGljeSwgaW4gZHJhZnQtaWV0Zi10c3Z3Zy1yc3Zw
LXBjbi0wNCZuYnNwO0kgaGF2ZSBpbmNsdWRlZCB0aGUgYXJndW1lbnRhdGlvbiB0aGF0IEkgcHJv
cG9zZWQgYXMgYW5zd2VyIHRvIHRoZSBjb21tZW50IG9uLXBhdGgNCiB2cyBvZmYtcGF0aCBzaWdu
YWxpbmcgcHJvdmlkZWQgYnkgS2VuLCBhbmQgd2hpY2ggaGUgYWN0dWFsbHkgYWdyZWVkIHdpdGgh
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlM
WTogJ0NvdXJpZXIgTmV3JzsgQ09MT1I6IGJsYWNrIj48L3NwYW4+Jm5ic3A7PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9IkZPTlQtRkFNSUxZOiAnQ291cmllciBOZXcnOyBD
T0xPUjogYmxhY2s7IEZPTlQtU0laRTogMTBwdCI+QmVzdCByZWdhcmRzLDwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6ICdDb3VyaWVyIE5l
dyc7IENPTE9SOiBibGFjazsgRk9OVC1TSVpFOiAxMHB0Ij5HZW9yZ2lvczwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6ICdDb3VyaWVyIE5l
dyc7IENPTE9SOiBibGFjayI+PC9zcGFuPiZuYnNwOzwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTogJ0NvdXJpZXIgTmV3JzsgQ09MT1I6IGJsYWNrIj48
L3NwYW4+Jm5ic3A7PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9IkZPTlQt
RkFNSUxZOiAnQ291cmllciBOZXcnOyBDT0xPUjogYmxhY2s7IEZPTlQtU0laRTogMTBwdCI+Jmd0
OyAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCiZndDsgRnJvbTogQm9iIEJyaXNjb2Ug
Wzwvc3Bhbj48c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6ICdDb3VyaWVyIE5ldyc7IENPTE9SOiBi
bGFjayI+PGEgaHJlZj0iaHR0cHM6Ly94cy51dHdlbnRlLm5sL293YS9yZWRpci5hc3B4P0M9TmJ1
bTlhSGZqMEtWYTZRV29XUWRVbXNHV2h0NHBzOElzVXFLUURBUFpOazBqOGZiWE5nZGY1YmRmX2pa
YTdkUkxEaTZBbEs2d3kwLiZhbXA7VVJMPW1haWx0byUzYWJvYi5icmlzY29lJTQwYnQuY29tIiB0
YXJnZXQ9Il9ibGFuayI+PHNwYW4gc3R5bGU9IkZPTlQtU0laRTogMTBwdCI+bWFpbHRvOmJvYi5i
cmlzY29lQGJ0LmNvbTwvc3Bhbj48L2E+PC9zcGFuPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTog
J0NvdXJpZXIgTmV3JzsgQ09MT1I6IGJsYWNrOyBGT05ULVNJWkU6IDEwcHQiPl08YnI+DQomZ3Q7
IFNlbnQ6IHZyaWpkYWcgOSBub3ZlbWJlciAyMDEyIDE2OjMzPGJyPg0KJmd0OyBUbzogS2FyYWdp
YW5uaXMsIEcuIChFV0kpPGJyPg0KJmd0OyBDYzogY2FybGJlcmdAZzExLm9yZy51azsgYW51cmFn
YkBjaXNjby5jb207IHRzdndnQGlldGYub3JnOyBFQVJETEVZLCBQaGlsPGJyPg0KJmd0OyBTdWJq
ZWN0OiBSZTogW3RzdndnXSBkcmFmdC1pZXRmLXRzdndnLXJzdnAtcGNuLTAzPGJyPg0KJmd0OyA8
YnI+DQomZ3Q7IEdlb3JnaW9zLDxicj4NCiZndDsgPGJyPg0KJmd0OyBJIHNoYWxsIHBvc3QgbXkg
ZnVsbCByZXZpZXcgb2YgdGhpcyBkcmFmdCBpbiB0aGUgbmV4dCBmZXcgZGF5cyAobmVlZHMgdHlw
aW5nIHVwIC08YnI+DQomZ3Q7IGN1cnJlbnRseSBzY3JpYmJsZWQgb24gYSBwYXBlciBjb3B5KS4g
VGhpcyBlbWFpbCBpcyBzb2xlbHkgaW4gcmVzcG9uc2UgdG8geW91cjxicj4NCiZndDsgYW5zd2Vy
IGFib3V0IG9uLXBhdGggdnMgb2ZmLXBhdGggcG9saWN5Ljxicj4NCiZndDsgPGJyPg0KJmd0OyBB
dCAxODo1NSAwNC8xMS8yMDEyLCBrYXJhZ2lhbkBjcy51dHdlbnRlLm5sIHdyb3RlOjxicj4NCiZn
dDsgJmd0O1NvIGluIHRoaXMgY2FzZSBhbiBhZGRpdGlvbmFsIHNpZ25hbGluZyBwcm90b2NvbCB3
aWxsIGJlIG5lZWRlZCB0byBiZTxicj4NCiZndDsgJmd0O3NwZWNpZmllZCB0aGF0IGNvdmVycyB0
aGUgc2lnbmFsaW5nIGJldHdlZW4gdGhlIFBDTi1lZ3Jlc3Mtbm9kZSBhbmQgdGhlPGJyPg0KJmd0
OyAmZ3Q7Y2VudHJhbGl6ZWQgbm9kZSBhbmQgYmV0d2VlbiBQQ04taW5ncmVzcy1ub2RlIGFuZCB0
aGUgY2VudHJhbGl6ZWQgbm9kZS48YnI+DQomZ3Q7ICZndDtJbiBQQ04gd2UgZGVjZGlkZWQgdG8g
b25seSBmb2N1cyBvbiB0aGUgc3BlY2lmaWNhdGlvbiBvZiB0aGUgc2lnbmFsaW5nPGJyPg0KJmd0
OyAmZ3Q7cHJvdG9jb2wgdGhhdCBjb21wbGV0ZXMgdGhlIGZlZWRiYWNrIGxvb3AgZnJvbSBQQ04t
ZWdyZXNzLW5vZGUgdG88YnI+DQomZ3Q7ICZndDtQQ04taW5ncmVzcy1ub2RlIGFuZCB0byBmb2N1
cyBvbiB0aGUgc2lnbmFsaW5nIHByb3RvY29sIHVzZWQgYmV0d2Vlbjxicj4NCiZndDsgJmd0O3Ro
ZSBlZGdlIG5vZGVzIGFuZCB0aGUgY2VudHJhbGl6ZWQgbm9kZS48YnI+DQomZ3Q7IDxicj4NCiZn
dDsgV2hlbiBJL3dlIG9yaWdpbmFsbHkgZGVzaWduZWQgQ0wtUENOIG92ZXIgUlNWUCAoMjAwNSks
IHRoZSBpZGVhIHdhcyB0aGF0IGl0PGJyPg0KJmd0OyB3b3VsZCBmaXQgd2l0aCB0aGUgcG9saWN5
LWJhc2VkIGFkbWlzc2lvbiBjb250cm9sIChQQkFDKSBhcmNoaXRlY3R1cmUgb2Y8YnI+DQomZ3Q7
IFJGQzI3NTMuIEluIHRoaXMgYXJjaGl0ZWN0dXJlLCBhbiBJbnRzZXJ2IG5vZGUgYXQgdGhlIGlu
Z3Jlc3MgdG8gYSBkb21haW4gaXM8YnI+DQomZ3Q7IHRoZSBwb2xpY3kgZW5mb3JjZW1lbnQgcG9p
bnQgKFBFUCksIGFuZCBpdCByZWZlcnMgdG8gYSBsb2dpY2FsbHkgY2VudHJhbGlzZWQ8YnI+DQom
Z3Q7ICdwb2xpY3kgZGVjaXNpb24gcG9pbnQnIChQRFApIGZvciBkZWNpc2lvbnMgb24gd2hpY2gg
Zmxvd3MgdG8gYmxvY2svdGVybWluYXRlLDxicj4NCiZndDsgdHlwaWNhbGx5IHVzaW5nIENPUFMu
PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRvIG1ha2UgdGhpcyBkb2MgZml0IHRoZSBQQkFDIGZyYW1l
d29yaywgYWxsIHdlIGhhdmUgdG8gZG8gaXM6PGJyPg0KJmd0OyAqIERlc2NyaWJlIHRoZSBQQ04t
aW5ncmVzcyBvbmx5IGFzIHRoZSBQQ04taW5ncmVzcyBhbmQgbm90IGFzIHRoZSBkZWNpc2lvbjxi
cj4NCiZndDsgcG9pbnQgKGZpbmQgJ2RlY2lzaW9uJyB0aHJvdWdob3V0IGRvYyBhbmQgZml4KS48
YnI+DQomZ3Q7ICogQWRkIGEgc2VjdGlvbiBzYXlpbmcgdGhlIFBDTi1pbmdyZXNzIGNhbiByZWZl
ciBmbG93IGFkbWlzc2lvbiBhbmQ8YnI+DQomZ3Q7IHRlcm1pbmF0aW9uIGRlY2lzaW9ucyB0byBh
IGNlbnRyYWwgZGVjaXNpb24gcG9pbnQgKHVzaW5nIGUuZy4gQ09QUyksIHdoaWNoIHdpbGw8YnI+
DQomZ3Q7IHJlc3BvbmQgdG8gdGhlIFBDTi1pbmdyZXNzIGFzIHBlciBSRkMyNzUzLiAoQWx0ZXJu
YXRpdmVseSB0aGUgUENOLWluZ3Jlc3M8YnI+DQomZ3Q7IGNvdWxkIGl0c2VsZiBiZSB0aGUgcG9s
aWN5IGRlY2lzaW9uIHBvaW50Lik8YnI+DQomZ3Q7ICogUmVmZXIgdG8gdGhpcyBuZXcgUEJBQyBz
ZWN0aW9uIGZyb20gU2VjdGlvbiAzLjExIGdpdmluZyB0aGUgYWRtaXNzaW9uPGJyPg0KJmd0OyBk
ZWNpc2lvbiBwcm9jZWR1cmUuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7ICogU29tZSBwZW9wbGUgbWln
aHQgdGhpbmsgdGhpcyBtZWFucyBDT1BTIHdpbGwgbmVlZCBuZXcgcHJvdG9jb2w8YnI+DQomZ3Q7
IGVsZW1lbnRzIHRvIGNhcnJ5IFBDTiBtYXJraW5nIHJhdGVzIHRvIHRoZSBwb2xpY3kgZGVjaXNp
b24gcG9pbnQuIEJ1dCBQQ048YnI+DQomZ3Q7IG1hcmtpbmcgcmF0ZXMgYXJlIGlycmVsZXZhbnQg
dG8gdGhlIHBvbGljeSBkZWNpc2lvbjogdGhlIFBDTi1pbmdyZXNzIGp1c3QgdXNlczxicj4NCiZn
dDsgUENOIHRvIGRldGVybWluZSB3aGV0aGVyIGl0IG5lZWRzIHRvIGJsb2NrIG9yIHRlcm1pbmF0
ZSwgYW5kIGl0IHJlZmVycyB0byB0aGU8YnI+DQomZ3Q7IHBvbGljeSBkZWNpc2lvbiBwb2ludCBm
b3Igd2hpY2ggZmxvd3MgdG8gYmxvY2svdGVybWluYXRlLjxicj4NCiZndDsgPGJyPg0KJmd0OyAq
IFVuZm9ydHVuYXRlbHksIG5laXRoZXIgb2YgdGhlIHR3byBQQ04gc3lzdGVtIGRlc2NyaXB0aW9u
cyBbUkZDNjY2MSw8YnI+DQomZ3Q7IFJGQzY2NjJdIGRlc2NyaWJlIGEgUEJBQy1iYXNlZCBjYXNl
LiBUaGUgYXJjaGl0ZWN0dXJlIFtSRkM1NTU5XSByZWZlcnMgdG88YnI+DQomZ3Q7IHRoZSBQQkFD
IGZyYW1ld29yayBbUkZDMjc1M10gYnV0IHVuZm9ydHVuYXRlbHkgZG9lc24ndCBzcGVsbCBvdXQg
aG93IGl0PGJyPg0KJmd0OyBmaXRzLiBPcmlnaW5hbGx5LCBJIHJlZmVyZW5jZWQgUEJBQyBmcm9t
IFJGQzU1NTksIGJ1dCBqdXN0IGFzIHRoZSBQQ04gdy1nIHdhczxicj4NCiZndDsgY2xvc2luZyBJ
IHJlYWxpc2VkIHRoYXQgKHNvbWU/KSBvdGhlcnMgaW4gdGhlIFBDTiB3LWcgd2VyZSB3b3JraW5n
IHVuZGVyIHRoZTxicj4NCiZndDsgYXNzdW1wdGlvbiB0aGF0IHRoZSBvbmx5IHdheSB0byB0YWxr
IHRvIGEgY2VudHJhbGlzZWQgcG9saWN5IG5vZGUgd2FzIGZyb208YnI+DQomZ3Q7IHRoZSBlZ3Jl
c3MsIHBvc3NpYmx5IHdpdGhvdXQgYmVpbmcgYXdhcmUgb2YgdGhlIGNvbnRlbnRzIG9mIFJGQzI3
NTMuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEkgdGhpbmsgaXQncyBPSyB0byBpbnRyb2R1Y2UgYSBu
ZXcgYXJjaGl0ZWN0dXJhbCBhcnJhbmdlbWVudCBpbiB0aGlzIFJTVlAgZG9jLDxicj4NCiZndDsg
Z2l2ZW4gUkZDMjc1MyBpcyBzcGVjaWZpYyB0byB0aGUgd2F5IFJTVlAgd29ya3MuPGJyPg0KJmd0
OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgQm9iPC9zcGFuPjxzcGFuIHN0eWxlPSJDT0xPUjogYmxh
Y2siPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
IkZPTlQtRkFNSUxZOiAnVGFob21hJywnc2Fucy1zZXJpZic7IENPTE9SOiBibGFjazsgRk9OVC1T
SVpFOiAxMHB0Ij48L3NwYW4+Jm5ic3A7PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_8D3D17ACE214DC429325B2B98F3AE71290DEE214MX15Acorpemccom_--

From cb.list6@gmail.com  Sat Mar  9 20:42:07 2013
Return-Path: <cb.list6@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C92A221F87D7 for <tsvwg@ietfa.amsl.com>; Sat,  9 Mar 2013 20:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KeNNADk6-SFm for <tsvwg@ietfa.amsl.com>; Sat,  9 Mar 2013 20:42:07 -0800 (PST)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 190B621F87C4 for <tsvwg@ietf.org>; Sat,  9 Mar 2013 20:42:06 -0800 (PST)
Received: by mail-wi0-f171.google.com with SMTP id hn17so357641wib.4 for <tsvwg@ietf.org>; Sat, 09 Mar 2013 20:42:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=942NVQRFtUQ5N5yWDivbq/nh2f6N0hZF3GU1h8Es/nA=; b=ggRcMbL7c+aicnP2BeJ7GRGn82/KQH3NCPJbkXRY5j2ep7YNsgFDOD3HR1DT1+TlKc 3PZeB0ReMF9nC/HWUr/Wibc+kfTxMyqQEi+iEsUxT6DMs74lcLjY4ExQ5SLnfvOBMUlc 4/wk+/Eq7xzcxWWLMEi7GHDXPCCvrmlZpgzduzjj1Q41rAPnFD8D4VuEV5otEUdcAOJ5 X3JqSxLR+ik9Dp1A2yGK1UIgdbS2J8SJhJ82OsRXpFxfJ7PiQPzjv0XkbGyA/v/0/QjD xJq9qMyk8L4+9EErarnqx1nDmeHJVtFFM7QIRyBdAT4blbYOpJS0P5/gxkV1lJ4DPj9d o42g==
MIME-Version: 1.0
X-Received: by 10.194.242.163 with SMTP id wr3mr12234118wjc.35.1362890525965;  Sat, 09 Mar 2013 20:42:05 -0800 (PST)
Received: by 10.194.20.35 with HTTP; Sat, 9 Mar 2013 20:42:05 -0800 (PST)
Date: Sat, 9 Mar 2013 20:42:05 -0800
Message-ID: <CAD6AjGSS=vyATF70fH4JV6XtRF_JfPsk7ase8M=1oY_pS1ihJg@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: tsvwg@ietf.org, draft-thornburgh-adobe-rtmfp@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [tsvwg] feedback on draft-thornburgh-adobe-rtmfp-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Mar 2013 04:42:07 -0000

Hi,

I have some strong concerns about this I-D and RTMFP in general with
regards to how they treat communication between IPv4-only and
IPv6-only systems.

Given the reality that RIPE and APNIC are both out of IPv4, it is
unacceptable to introduce a protocol that bifurcates the Internet into
those that have IPv4 and those that have IPv6.  AFAIK,
draft-thornburgh-adobe-rtmfp-04 only accounts for the ability talk
within a single address family.

Similar solutions like ICE (rfc5245) solve this problem by using TURN,
and the general approach would be to DNS64 / NAT64

I do not believe this I-D should be adopted as WG item and i do not
think it is eligible for standards tracks qualification since it
communicates IPv4 literals / referrals as its fundamental design, thus
not accounting for the scenarios in RFC 6144 and explicitly breaking
network, like mine, that use the proposed standard RFC 6146.


CB

From bhargava.anurag@gmail.com  Sun Mar 10 16:23:51 2013
Return-Path: <bhargava.anurag@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B762F21F8841 for <tsvwg@ietfa.amsl.com>; Sun, 10 Mar 2013 16:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sWYehnkpqzTW for <tsvwg@ietfa.amsl.com>; Sun, 10 Mar 2013 16:23:51 -0700 (PDT)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id DEB8821F8837 for <tsvwg@ietf.org>; Sun, 10 Mar 2013 16:23:50 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id i10so3978841oag.14 for <tsvwg@ietf.org>; Sun, 10 Mar 2013 16:23:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=ibgggLLsr3817cpWNEhrSInovp1t8H76DgP4rbIWKho=; b=XTrZ++e7L5d4EXOOFlM71BiFpNKKsvdO/9ygkEC5nksFkCQqDr2tfUTP+mpX2ly23Q p4p1nYz0QzKskm2EopXAu7WCbZsX9xoeLNh3h3NPetwfXscOVfTPwl4+Xo3e9+mn7nBI aTOh9Hl5hNII/1x3N0+GXIyKD+NURCZJy3gCsoEn9QZo3W+DNMEjN8rSYopXdZFVyr0z QqtOWsLUTZt6Fnrar3woy7G4ckcHHsRqAEqmA4VdYp/alYymOVcog82gjwpk7Jdw9AVx R8JwrOR845iGOG6Z4lPQn6GUC+mjFAfZn4I0hI5J9OmwaLitEoEZZGcvmvv56tMluIRU WBOw==
MIME-Version: 1.0
X-Received: by 10.182.14.39 with SMTP id m7mr6977773obc.96.1362957830355; Sun, 10 Mar 2013 16:23:50 -0700 (PDT)
Received: by 10.182.112.132 with HTTP; Sun, 10 Mar 2013 16:23:50 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290DCD874@MX15A.corp.emc.com>
References: <87644A58-0C27-4F5A-B09B-BD8EC1F9A10A@g11.org.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F2CC12597@EXMBX01.ad.utwente.nl> <D245A17A-F851-4707-A081-12D65C4AC0AF@g11.org.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F2CC1797D@EXMBX04.ad.utwente.nl> <201211091623.qA9GMxVm013855@bagheera.jungle.bt.co.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F4F36DDC8@EXMBX23.ad.utwente.nl> <8D3D17ACE214DC429325B2B98F3AE71290DCD874@MX15A.corp.emc.com>
Date: Sun, 10 Mar 2013 19:23:50 -0400
Message-ID: <CAKK+Tkb7F09XSoHkPRbsgrOWE1AKax-StD-=i67uw7r-7dG2Qw@mail.gmail.com>
From: Anurag Bhargava <bhargava.anurag@gmail.com>
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "anuragb@cisco.com" <anuragb@cisco.com>, "philip.eardley@bt.com" <philip.eardley@bt.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RSVP PCN and PBAC
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Mar 2013 23:23:51 -0000

Hi David,

 The point which is not clear is about the need of admission decision
procedure in this draft.
 Whys does this have to be covered here?

Thx
-Anurag

On Sat, Mar 9, 2013 at 1:14 PM, Black, David <david.black@emc.com> wrote:
> Hi Georgios,
>
>
>
> <WG co-chair hat OFF>
>
>
>
> I think you=92ve missed the point here:
>
>
>
>> In my opinion if it is to introduce a new policy-based admission control
>> (PBAC)
>
>> architecture to be used in the context of PCN, then this should be done =
in
>> another
>
>> document and not in the draft-ietf-tsvwg-rsvp-pcn.
>
>
>
> I do not believe that Bob is asking that this draft add a PBAC architectu=
re,
> but rather that minor changes be made so that this draft is consistent wi=
th
> the PBAC architectural approach:
>
>
>
>>> To make this doc fit the PBAC framework, all we have to do is:
>
>>> * Describe the PCN-ingress only as the PCN-ingress and not as the
>>> decision
>
>>> point (find 'decision' throughout doc and fix).
>
>>> * Add a section saying the PCN-ingress can refer flow admission and
>
>>> termination decisions to a central decision point (using e.g. COPS),
>>> which will
>
>>> respond to the PCN-ingress as per RFC2753. (Alternatively the PCN-ingre=
ss
>
>>> could itself be the policy decision point.)
>
>>> * Refer to this new PBAC section from Section 3.11 giving the admission
>
>>> decision procedure.
>
>
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>
>
>
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> karagian@cs.utwente.nl
> Sent: Saturday, March 09, 2013 2:48 AM
> To: bob.briscoe@bt.com
> Cc: philip.eardley@bt.com; anuragb@cisco.com; tsvwg@ietf.org
> Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03
>
>
>
> Hi Bob,
>
>
>
> Thanks for your comments!
>
>
>
> In the below email you propose to introduce the description of a
> policy-based admission control (PBAC) architecture in order to respond to
> the answer about on-path vs off-path policy.
>
> In my opinion if it is to introduce a new policy-based admission control
> (PBAC) architecture to be used in the context of PCN, then this should be
> done in another document and not in the draft-ietf-tsvwg-rsvp-pcn.
>
>
>
> Regarding the answer about on-path vs off-path policy, in
> draft-ietf-tsvwg-rsvp-pcn-04 I have included the argumentation that I
> proposed as answer to the comment on-path vs off-path signaling provided =
by
> Ken, and which he actually agreed with!
>
>
>
> Best regards,
>
> Georgios
>
>
>
>
>
>> -----Original Message-----
>> From: Bob Briscoe [mailto:bob.briscoe@bt.com]
>> Sent: vrijdag 9 november 2012 16:33
>> To: Karagiannis, G. (EWI)
>> Cc: carlberg@g11.org.uk; anuragb@cisco.com; tsvwg@ietf.org; EARDLEY, Phi=
l
>> Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03
>>
>> Georgios,
>>
>> I shall post my full review of this draft in the next few days (needs
>> typing up -
>> currently scribbled on a paper copy). This email is solely in response t=
o
>> your
>> answer about on-path vs off-path policy.
>>
>> At 18:55 04/11/2012, karagian@cs.utwente.nl wrote:
>> >So in this case an additional signaling protocol will be needed to be
>> >specified that covers the signaling between the PCN-egress-node and the
>> >centralized node and between PCN-ingress-node and the centralized node.
>> >In PCN we decdided to only focus on the specification of the signaling
>> >protocol that completes the feedback loop from PCN-egress-node to
>> >PCN-ingress-node and to focus on the signaling protocol used between
>> >the edge nodes and the centralized node.
>>
>> When I/we originally designed CL-PCN over RSVP (2005), the idea was that
>> it
>> would fit with the policy-based admission control (PBAC) architecture of
>> RFC2753. In this architecture, an Intserv node at the ingress to a domai=
n
>> is
>> the policy enforcement point (PEP), and it refers to a logically
>> centralised
>> 'policy decision point' (PDP) for decisions on which flows to
>> block/terminate,
>> typically using COPS.
>>
>> To make this doc fit the PBAC framework, all we have to do is:
>> * Describe the PCN-ingress only as the PCN-ingress and not as the decisi=
on
>> point (find 'decision' throughout doc and fix).
>> * Add a section saying the PCN-ingress can refer flow admission and
>> termination decisions to a central decision point (using e.g. COPS), whi=
ch
>> will
>> respond to the PCN-ingress as per RFC2753. (Alternatively the PCN-ingres=
s
>> could itself be the policy decision point.)
>> * Refer to this new PBAC section from Section 3.11 giving the admission
>> decision procedure.
>>
>> * Some people might think this means COPS will need new protocol
>> elements to carry PCN marking rates to the policy decision point. But PC=
N
>> marking rates are irrelevant to the policy decision: the PCN-ingress jus=
t
>> uses
>> PCN to determine whether it needs to block or terminate, and it refers t=
o
>> the
>> policy decision point for which flows to block/terminate.
>>
>> * Unfortunately, neither of the two PCN system descriptions [RFC6661,
>> RFC6662] describe a PBAC-based case. The architecture [RFC5559] refers t=
o
>> the PBAC framework [RFC2753] but unfortunately doesn't spell out how it
>> fits. Originally, I referenced PBAC from RFC5559, but just as the PCN w-=
g
>> was
>> closing I realised that (some?) others in the PCN w-g were working under
>> the
>> assumption that the only way to talk to a centralised policy node was fr=
om
>> the egress, possibly without being aware of the contents of RFC2753.
>>
>> I think it's OK to introduce a new architectural arrangement in this RSV=
P
>> doc,
>> given RFC2753 is specific to the way RSVP works.
>>
>>
>> Bob
>
>



--=20
BR,
-Anurag

From david.black@emc.com  Sun Mar 10 18:47:37 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2108821F89AF for <tsvwg@ietfa.amsl.com>; Sun, 10 Mar 2013 18:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-hzgyXstwZQ for <tsvwg@ietfa.amsl.com>; Sun, 10 Mar 2013 18:47:36 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5205721F874D for <tsvwg@ietf.org>; Sun, 10 Mar 2013 18:47:35 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2B1lMoq015601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 10 Mar 2013 21:47:26 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Sun, 10 Mar 2013 21:47:05 -0400
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2B1l4kC016194; Sun, 10 Mar 2013 21:47:04 -0400
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub13.corp.emc.com ([128.222.70.234]) with mapi; Sun, 10 Mar 2013 21:47:04 -0400
From: "Black, David" <david.black@emc.com>
To: Anurag Bhargava <bhargava.anurag@gmail.com>
Date: Sun, 10 Mar 2013 21:46:53 -0400
Thread-Topic: [tsvwg] RSVP PCN and PBAC
Thread-Index: Ac4d5mQ5fzmXr4azR6uL7x1khw+opQAEolmQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71290DCD8E3@MX15A.corp.emc.com>
References: <87644A58-0C27-4F5A-B09B-BD8EC1F9A10A@g11.org.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F2CC12597@EXMBX01.ad.utwente.nl> <D245A17A-F851-4707-A081-12D65C4AC0AF@g11.org.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F2CC1797D@EXMBX04.ad.utwente.nl> <201211091623.qA9GMxVm013855@bagheera.jungle.bt.co.uk> <FF1A9612A94D5C4A81ED7DE1039AB80F4F36DDC8@EXMBX23.ad.utwente.nl> <8D3D17ACE214DC429325B2B98F3AE71290DCD874@MX15A.corp.emc.com> <CAKK+Tkb7F09XSoHkPRbsgrOWE1AKax-StD-=i67uw7r-7dG2Qw@mail.gmail.com>
In-Reply-To: <CAKK+Tkb7F09XSoHkPRbsgrOWE1AKax-StD-=i67uw7r-7dG2Qw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "anuragb@cisco.com" <anuragb@cisco.com>, "philip.eardley@bt.com" <philip.eardley@bt.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RSVP PCN and PBAC
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 01:47:37 -0000

>  The point which is not clear is about the need of admission decision pro=
cedure in this draft.
>  Why does this have to be covered here?

It's not necessary to cover the detailed decision procedure; it should
suffice to state that admission control decisions are necessary, which
the draft already does in this sentence in Section 1.1:

   The
   PCN-egress-nodes measure the rates of differently marked PCN traffic
   in periodic intervals and report these rates to the Decision Points
   for admission control and flow termination; the Decision Points use
   these rates to make decisions.

The following useful sentence is also in that section that could probably
be expanded to deal with Bob's concerns around the possibility of multiple
decision locations:

   If the PCN decision point is not collocated with the PCN-ingress-node
   then additional signalling procedures are required that are out of
   the scope of this document.

Thanks,
--David

> -----Original Message-----
> From: Anurag Bhargava [mailto:bhargava.anurag@gmail.com]
> Sent: Sunday, March 10, 2013 7:24 PM
> To: Black, David
> Cc: karagian@cs.utwente.nl; bob.briscoe@bt.com; philip.eardley@bt.com;
> anuragb@cisco.com; tsvwg@ietf.org
> Subject: Re: [tsvwg] RSVP PCN and PBAC
>=20
> Hi David,
>=20
>  The point which is not clear is about the need of admission decision
> procedure in this draft.
>  Whys does this have to be covered here?
>=20
> Thx
> -Anurag
>=20
> On Sat, Mar 9, 2013 at 1:14 PM, Black, David <david.black@emc.com> wrote:
> > Hi Georgios,
> >
> >
> >
> > <WG co-chair hat OFF>
> >
> >
> >
> > I think you've missed the point here:
> >
> >
> >
> >> In my opinion if it is to introduce a new policy-based admission contr=
ol
> >> (PBAC)
> >
> >> architecture to be used in the context of PCN, then this should be don=
e in
> >> another
> >
> >> document and not in the draft-ietf-tsvwg-rsvp-pcn.
> >
> >
> >
> > I do not believe that Bob is asking that this draft add a PBAC architec=
ture,
> > but rather that minor changes be made so that this draft is consistent =
with
> > the PBAC architectural approach:
> >
> >
> >
> >>> To make this doc fit the PBAC framework, all we have to do is:
> >
> >>> * Describe the PCN-ingress only as the PCN-ingress and not as the
> >>> decision
> >
> >>> point (find 'decision' throughout doc and fix).
> >
> >>> * Add a section saying the PCN-ingress can refer flow admission and
> >
> >>> termination decisions to a central decision point (using e.g. COPS),
> >>> which will
> >
> >>> respond to the PCN-ingress as per RFC2753. (Alternatively the PCN-ing=
ress
> >
> >>> could itself be the policy decision point.)
> >
> >>> * Refer to this new PBAC section from Section 3.11 giving the admissi=
on
> >
> >>> decision procedure.
> >
> >
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > david.black@emc.com        Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >
> >
> >
> > From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf =
Of
> > karagian@cs.utwente.nl
> > Sent: Saturday, March 09, 2013 2:48 AM
> > To: bob.briscoe@bt.com
> > Cc: philip.eardley@bt.com; anuragb@cisco.com; tsvwg@ietf.org
> > Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03
> >
> >
> >
> > Hi Bob,
> >
> >
> >
> > Thanks for your comments!
> >
> >
> >
> > In the below email you propose to introduce the description of a
> > policy-based admission control (PBAC) architecture in order to respond =
to
> > the answer about on-path vs off-path policy.
> >
> > In my opinion if it is to introduce a new policy-based admission contro=
l
> > (PBAC) architecture to be used in the context of PCN, then this should =
be
> > done in another document and not in the draft-ietf-tsvwg-rsvp-pcn.
> >
> >
> >
> > Regarding the answer about on-path vs off-path policy, in
> > draft-ietf-tsvwg-rsvp-pcn-04 I have included the argumentation that I
> > proposed as answer to the comment on-path vs off-path signaling provide=
d by
> > Ken, and which he actually agreed with!
> >
> >
> >
> > Best regards,
> >
> > Georgios
> >
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: Bob Briscoe [mailto:bob.briscoe@bt.com]
> >> Sent: vrijdag 9 november 2012 16:33
> >> To: Karagiannis, G. (EWI)
> >> Cc: carlberg@g11.org.uk; anuragb@cisco.com; tsvwg@ietf.org; EARDLEY, P=
hil
> >> Subject: Re: [tsvwg] draft-ietf-tsvwg-rsvp-pcn-03
> >>
> >> Georgios,
> >>
> >> I shall post my full review of this draft in the next few days (needs
> >> typing up -
> >> currently scribbled on a paper copy). This email is solely in response=
 to
> >> your
> >> answer about on-path vs off-path policy.
> >>
> >> At 18:55 04/11/2012, karagian@cs.utwente.nl wrote:
> >> >So in this case an additional signaling protocol will be needed to be
> >> >specified that covers the signaling between the PCN-egress-node and t=
he
> >> >centralized node and between PCN-ingress-node and the centralized nod=
e.
> >> >In PCN we decdided to only focus on the specification of the signalin=
g
> >> >protocol that completes the feedback loop from PCN-egress-node to
> >> >PCN-ingress-node and to focus on the signaling protocol used between
> >> >the edge nodes and the centralized node.
> >>
> >> When I/we originally designed CL-PCN over RSVP (2005), the idea was th=
at
> >> it
> >> would fit with the policy-based admission control (PBAC) architecture =
of
> >> RFC2753. In this architecture, an Intserv node at the ingress to a dom=
ain
> >> is
> >> the policy enforcement point (PEP), and it refers to a logically
> >> centralised
> >> 'policy decision point' (PDP) for decisions on which flows to
> >> block/terminate,
> >> typically using COPS.
> >>
> >> To make this doc fit the PBAC framework, all we have to do is:
> >> * Describe the PCN-ingress only as the PCN-ingress and not as the deci=
sion
> >> point (find 'decision' throughout doc and fix).
> >> * Add a section saying the PCN-ingress can refer flow admission and
> >> termination decisions to a central decision point (using e.g. COPS), w=
hich
> >> will
> >> respond to the PCN-ingress as per RFC2753. (Alternatively the PCN-ingr=
ess
> >> could itself be the policy decision point.)
> >> * Refer to this new PBAC section from Section 3.11 giving the admissio=
n
> >> decision procedure.
> >>
> >> * Some people might think this means COPS will need new protocol
> >> elements to carry PCN marking rates to the policy decision point. But =
PCN
> >> marking rates are irrelevant to the policy decision: the PCN-ingress j=
ust
> >> uses
> >> PCN to determine whether it needs to block or terminate, and it refers=
 to
> >> the
> >> policy decision point for which flows to block/terminate.
> >>
> >> * Unfortunately, neither of the two PCN system descriptions [RFC6661,
> >> RFC6662] describe a PBAC-based case. The architecture [RFC5559] refers=
 to
> >> the PBAC framework [RFC2753] but unfortunately doesn't spell out how i=
t
> >> fits. Originally, I referenced PBAC from RFC5559, but just as the PCN =
w-g
> >> was
> >> closing I realised that (some?) others in the PCN w-g were working und=
er
> >> the
> >> assumption that the only way to talk to a centralised policy node was =
from
> >> the egress, possibly without being aware of the contents of RFC2753.
> >>
> >> I think it's OK to introduce a new architectural arrangement in this R=
SVP
> >> doc,
> >> given RFC2753 is specific to the way RSVP works.
> >>
> >>
> >> Bob
> >
> >
>=20
>=20
>=20
> --
> BR,
> -Anurag


From internet-drafts@ietf.org  Mon Mar 11 04:58:33 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BC3421F8A18; Mon, 11 Mar 2013 04:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.504
X-Spam-Level: 
X-Spam-Status: No, score=-102.504 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n5jTFMDgAZCF; Mon, 11 Mar 2013 04:58:33 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BD95F21F8A35; Mon, 11 Mar 2013 04:58:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.42
Message-ID: <20130311115831.23223.5521.idtracker@ietfa.amsl.com>
Date: Mon, 11 Mar 2013 04:58:31 -0700
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-udp-encaps-12.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 11:58:33 -0000

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

	Title           : UDP Encapsulation of SCTP Packets for End-Host to End-Ho=
st Communication
	Author(s)       : Michael Tuexen
                          Randall R. Stewart
	Filename        : draft-ietf-tsvwg-sctp-udp-encaps-12.txt
	Pages           : 11
	Date            : 2013-03-11

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

   Please note that this document only describes the functionality
   required within an SCTP stack to add on UDP encapsulation, providing
   only those mechanisms for two end-hosts to communicate with each
   other over UDP ports.  In particular, it does not provide mechanisms
   to determine whether UDP encapsulation is being used by the peer, nor
   the mechanisms for determining which remote UDP port number can be
   used.  These functions are are out of scope for this document.

   This document covers only end-hosts and not tunneling (egress or
   ingress) end-points.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-udp-encaps-12


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


From david.black@emc.com  Mon Mar 11 07:05:23 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF01121F8867 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 07:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MaUlBji1UpG3 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 07:05:21 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 8BE3521F87AD for <tsvwg@ietf.org>; Mon, 11 Mar 2013 07:05:21 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2BE5Jnb009680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Mon, 11 Mar 2013 10:05:20 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Mon, 11 Mar 2013 10:05:09 -0400
Received: from mxhub33.corp.emc.com (mxhub33.corp.emc.com [10.254.93.81]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2BE58FY027055 for <tsvwg@ietf.org>; Mon, 11 Mar 2013 10:05:08 -0400
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub33.corp.emc.com ([::1]) with mapi; Mon, 11 Mar 2013 10:05:08 -0400
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Date: Mon, 11 Mar 2013 10:05:06 -0400
Thread-Topic: RSVP-PCN draft: configuration
Thread-Index: Ac4eYW9hnvBAC9PaTKaX4MePl5AR6A==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71290DCD982@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [tsvwg] RSVP-PCN draft: configuration
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 14:05:23 -0000

<WG co-chair hat OFF>

I noticed a couple of configuration issues in the response to Bob's comment=
:

> > * How PCN interior nodes ignore RSVP messages:
> > - by configuration?
> > - or by the PCN-ingress switching aggregate PATH messages to IP protoco=
l
> > number RSVP-E2E-IGNORE (which isn't strictly the right name but would h=
ave
> > the right effect)?

> Georgios: We mentioned in the new version of the draft that the PCN inter=
ior
> nodes ignore aggregated and e2e RSVP messages by configuration.=20

I think relying on configuration is ok here, as PCN interior nodes really s=
hould
not be doing anything with any RSVP messages whatsoever, and I'm not sure I=
 like
the idea of changing the IP protocol number on ingress and changing it back=
 on
egress.
=20
> > * Error conditions, for instance when messages don't contain the expect=
ed
> > objects, e.g. [draft-lefaucheur-tsvwg-rsvp-ecn-01, page 6 bullet 1].
=20
> Georgios: Please note that the PCN object is carried using the Aggregated=
 RESV
> message, and not the e2e RESV message, meaning that the above issue is no=
t relevant.

In contrast, I do think that there's an actual issue here in that text shou=
ld
be added to specify what a PCN ingress or egress node does when a received
Aggregated RSVP message doesn't contain all of the RSVP objects that are
supposed to be there, or contains unexpected objects.

There also should be some text (which I may have missed) on what happens
when the PCN domain is misconfigured in a fashion that allows an Aggregated
RSVP message to escape the domain - IMHO, the desired behavior is that the
entire Aggregated RSVP message is ignored by a non-PCN node that processes
RSVP, and there needs to be some text on how that happens.

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 karagian@cs.utwente.nl  Mon Mar 11 07:24:19 2013
Return-Path: <karagian@cs.utwente.nl>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA6E21F859C for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 07:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mOfEBKijfT54 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 07:24:17 -0700 (PDT)
Received: from EXEDGE01.ad.utwente.nl (exedge01.ad.utwente.nl [130.89.5.48]) by ietfa.amsl.com (Postfix) with ESMTP id 88FFD21F85ED for <tsvwg@ietf.org>; Mon, 11 Mar 2013 07:24:16 -0700 (PDT)
Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE01.ad.utwente.nl (130.89.5.48) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 11 Mar 2013 15:24:43 +0100
Received: from EXMBX23.ad.utwente.nl ([169.254.3.16]) by EXHUB02.ad.utwente.nl ([130.89.4.229]) with mapi id 14.02.0328.009; Mon, 11 Mar 2013 15:24:14 +0100
From: <karagian@cs.utwente.nl>
To: <david.black@emc.com>, <tsvwg@ietf.org>
Thread-Topic: RSVP-PCN draft: configuration
Thread-Index: Ac4eYW9hnvBAC9PaTKaX4MePl5AR6AAAlpmg
Date: Mon, 11 Mar 2013 14:24:14 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F4F36E3FB@EXMBX23.ad.utwente.nl>
References: <8D3D17ACE214DC429325B2B98F3AE71290DCD982@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290DCD982@MX15A.corp.emc.com>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.89.12.129]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [tsvwg] RSVP-PCN draft: configuration
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 14:24:19 -0000

Hi David,

Thanks, please see in line!


> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf
> Of Black, David
> Sent: maandag 11 maart 2013 15:05
> To: tsvwg@ietf.org
> Subject: [tsvwg] RSVP-PCN draft: configuration
>=20
> <WG co-chair hat OFF>
>=20
> I noticed a couple of configuration issues in the response to Bob's comme=
nt:
>=20
> > > * How PCN interior nodes ignore RSVP messages:
> > > - by configuration?
> > > - or by the PCN-ingress switching aggregate PATH messages to IP
> > > protocol number RSVP-E2E-IGNORE (which isn't strictly the right name
> > > but would have the right effect)?
>=20
> > Georgios: We mentioned in the new version of the draft that the PCN
> > interior nodes ignore aggregated and e2e RSVP messages by configuration=
.
>=20
> I think relying on configuration is ok here, as PCN interior nodes really=
 should
> not be doing anything with any RSVP messages whatsoever, and I'm not sure
> I like the idea of changing the IP protocol number on ingress and changin=
g it
> back on egress.

Georgios: Okay, thanks!

>=20
> > > * Error conditions, for instance when messages don't contain the
> > > expected objects, e.g. [draft-lefaucheur-tsvwg-rsvp-ecn-01, page 6 bu=
llet
> 1].
>=20
> > Georgios: Please note that the PCN object is carried using the
> > Aggregated RESV message, and not the e2e RESV message, meaning that
> the above issue is not relevant.
>=20
> In contrast, I do think that there's an actual issue here in that text sh=
ould be
> added to specify what a PCN ingress or egress node does when a received
> Aggregated RSVP message doesn't contain all of the RSVP objects that are
> supposed to be there, or contains unexpected objects.
>=20
> There also should be some text (which I may have missed) on what happens
> when the PCN domain is misconfigured in a fashion that allows an
> Aggregated RSVP message to escape the domain - IMHO, the desired
> behavior is that the entire Aggregated RSVP message is ignored by a non-
> PCN node that processes RSVP, and there needs to be some text on how
> that happens.

Georgios: Thanks, We will work these comment out in a next version of the d=
raft!

Best regards,
Georgios

>=20
> 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-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From bob.briscoe@bt.com  Mon Mar 11 10:49:02 2013
Return-Path: <bob.briscoe@bt.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D587611E818F for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 10:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06CMM+7KqIeS for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 10:49:01 -0700 (PDT)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.99]) by ietfa.amsl.com (Postfix) with ESMTP id 78AFA11E8187 for <tsvwg@ietf.org>; Mon, 11 Mar 2013 10:49:01 -0700 (PDT)
Received: from EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) by EVMHR68-UKRD.bt.com (10.187.101.23) with Microsoft SMTP Server (TLS) id 8.3.279.1; Mon, 11 Mar 2013 17:48:59 +0000
Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 11 Mar 2013 17:48:57 +0000
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) with Microsoft SMTP Server id 14.2.342.3; Mon, 11 Mar 2013 17:48:55 +0000
Received: from BTP075694.jungle.bt.co.uk ([10.111.108.90])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id r2BHmr8j017777	for <tsvwg@ietf.org>; Mon, 11 Mar 2013 17:48:54 GMT
Message-ID: <201303111748.r2BHmr8j017777@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 11 Mar 2013 17:48:52 +0000
To: tsvwg IETF list <tsvwg@ietf.org>
From: Bob Briscoe <bob.briscoe@bt.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Subject: [tsvwg] Reviewers pls: draft-briscoe-tsvwg-ecn-encap-guidelines-02.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 17:49:03 -0000

tsvwg folks,

"Guidelines for Adding Congestion Notification to Protocols that 
Encapsulate IP"

This draft has been improved with the help of new co-authors:
- John Kaippallimalil, who is working in 3GPP on using ECN in GTP tunnels
- Pat Thaler, who has been adding congestion notification to IEEE 802 networks

We are seeking volunteers to review, who have expertise in tunnelling 
technologies and in the interaction between IP & L2 technologies.

We will also be seeking adoption of this draft onto the tsvwg w-g 
charter of work.

Draft:
<http://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-encap-guidelines-02>
Links to other formats and the abstract in the announcement below.

Brief slides that will be presented in tsvwg at Orlando:
<http://www.bobbriscoe.net/presents/1303ietf/1303ecn-encap-guidelines.pdf>

Cheers



Bob


>From: <internet-drafts@ietf.org>
>To: <bob.briscoe@bt.com>
>CC: <pthaler@broadcom.com>, <john.kaippallimalil@huawei.com>
>Subject: New Version Notification for
>         draft-briscoe-tsvwg-ecn-encap-guidelines-02.txt
>Date: Mon, 25 Feb 2013 16:01:27 -0800
>
>
>A new version of I-D, draft-briscoe-tsvwg-ecn-encap-guidelines-02.txt
>has been successfully submitted by Bob Briscoe and posted to the
>IETF repository.
>
>Filename:       draft-briscoe-tsvwg-ecn-encap-guidelines
>Revision:       02
>Title:          Guidelines for Adding Congestion Notification to 
>Protocols that Encapsulate IP
>Creation date:  2013-02-24
>Group:          Individual Submission
>Number of pages: 27
>URL: 
>http://www.ietf.org/internet-drafts/draft-briscoe-tsvwg-ecn-encap-guidelines-02.txt
>Status: 
>http://datatracker.ietf.org/doc/draft-briscoe-tsvwg-ecn-encap-guidelines
>Htmlized: 
>http://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-encap-guidelines-02
>Diff: 
>http://www.ietf.org/rfcdiff?url2=draft-briscoe-tsvwg-ecn-encap-guidelines-02
>
>Abstract:
>    The purpose of this document is to guide the design of congestion
>    notification in any lower layer or tunnelling protocol that
>    encapsulates IP.  The aim is for explicit congestion signals to
>    propagate consistently from lower layer protocols into IP.  Then the
>    IP internetwork layer can act as a portability layer to carry
>    congestion notification from non-IP-aware congested nodes up to the
>    transport layer (L4).  Following these guidelines should assure
>    interworking between new lower layer congestion notification
>    mechanisms, whether specified by the IETF or other standards bodies.
>
> 
>
>
>
>The IETF Secretariat

________________________________________________________________
Bob Briscoe,                                                  BT 


From touch@isi.edu  Mon Mar 11 11:11:37 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D14811E81C3 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 11:11:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.323
X-Spam-Level: 
X-Spam-Status: No, score=-102.323 tagged_above=-999 required=5 tests=[AWL=-1.726, BAYES_00=-2.599, NORMAL_HTTP_TO_IP=0.001, SARE_HEXOCTDWORD=2, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jGo-LvaC0hIR for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 11:11:30 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id D64A911E81DD for <tsvwg@ietf.org>; Mon, 11 Mar 2013 11:11:30 -0700 (PDT)
Received: from [192.168.1.96] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r2BIAbI7018466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 11 Mar 2013 11:10:47 -0700 (PDT)
Message-ID: <513E1E1E.9060000@isi.edu>
Date: Mon, 11 Mar 2013 11:10:38 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
References: <20130225170557.25596.27309.idtracker@ietfa.amsl.com> <512B9CF1.8030404@isi.edu> <D4D47BCFFE5A004F95D707546AC0D7E91F769029@SACEXCMBX01-PRD.hq.netapp.com>
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F769029@SACEXCMBX01-PRD.hq.netapp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-port-use-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 18:11:37 -0000

Hi, Lars,

Thanks for your review.

Comments below.

Joe

On 2/27/2013 10:35 AM, Eggert, Lars wrote:
> Hi,
>
> I gave this a quick read; here are some comments.
>
> Lars
>
>
>
>    High-level: Somewhere in this document, we should point out strongly
>    that service names are available FCFS w/o IANA assignment, and are
>    therefore MUCH easier to use when a service needs to be rolled out
>    quickly.
>
>
> Section 4., paragraph 4:
>>        0-1023         0x03FF         Well-Known (a.k.a. 'system')
>>        1024-49151     0x0300-0xBFFF  Registered (a.k.a. 'user')
>>        49152-65535    0xC000-0xFFFF  Dynamic/Private
>
>    1024 is 0x400

Yup.

> Section 5., paragraph 6:
>>        http:51509//www.example.com/
>
>    Actually, it would be http://www.example.com:51509/

Yup.

> Section 7.2., paragraph 0:
>>   7.2. How Many Ports?
>
>    You might want to add in this section that in the past, when the port
>    number space was less crowded, multiple ports were assigned for one
>    service, e.g., X11. However, that does not reflect current practice
>    anymore, and the existence of such assignments in the IANA table does
>    not constitute a precedent.

Yes. There are at least two cases of this - one where groups were 
assigned before best practices were widely understood, and another when 
the assignments were not as ardently reviewed.

> Section 7.3., paragraph 5:
>>     >> Developers SHOULD NOT apply for system ports because the
>>     increased privilege they provide is not always enforced.
>
>    Developers CANNOT simply apply for system ports since RFC6335 was
>    published. It very clearly says that the policy is "IETF Review" or
>    "IESG Approval" only, and that a "...request for a System Port number
>    MUST document *both* why using a port number from the Dynamic Ports
>    range is unsuitable *and* why using a port number from the User Ports
>    range is unsuitable for that application.

Developers can apply for a system port by following the processes you 
note. The text above suggests that even though such avenues are 
available, they are probably better avoided anyway.

I will clarify and include some of your points as well in the next revision.

> Section 7.3., paragraph 7:
>>     At some future date, it might be useful to deprecate the distinction
>>     between system and user ports altogether, but merely avoiding system
>>     ports would potentially waste only approximately 180 of 1024 values
>>     (17%).
>
>    You might want to add somewhere in this section that many services
>    that need to bind to a system port go through great lengths in order
>    to drop root privileges as soon as they have bound, in order to reduce
>    their attack surface. So it's actually MORE secure to run on a port >
>    1023.

Yes.

> Section 7.6., paragraph 7:
>>     >> UDP multi-host services SHOULD use multicast rather than
>>     broadcast.
>
>    This suggestion isn't really about port use, and therefore maybe not
>    in scope of this document.

It's about how to use ports, which includes whether to use them for 
broadcast or multicast IMO. I.e., requesting a port solely for broadcast 
has severe limitations.

> Section 7.6., paragraph 8:
>>     Designers should be very careful in creating services over
>>     transports that do not support congestion control or error recovery,
>>     notably UDP. There are several issues that should be considered in
>>     such cases:
>
>    Ditto. As much as I'd like a "how to design an application protocol"
>    BCP, this one isn't it. Much of the UDP-specific stuff is also already
>    discussed in more detail in RFC5405.

I can cite RFC5405. However, this too falls into the kind of advice we 
give for those applying for ports, and the things we check.

This is advice for application designers and how they use ports. It's 
not best-practices for apps in general, but some of those considerations 
come into play when asking for a port assignment.

> Section 7.7., paragraph 4:
>>     Deployments that use ports before deployment complicate IANA
>>     management of the port space. Keep in mind that this recommendation
>>     protects both other parties and you; it helps ensure that your
>>     desired number and service name are available when assigned. The
>>     list of currently unassigned numbers is just that - *currently*
>>     unassigned. It does not reflect pending applications, nor
>>     applications that might arrive before yours. Waiting for an official
>>     IANA assignment reduces the chance that your assignment will
>>     conflict with another deployed service.
>
>    You might want to say something about how long an IANA allocation
>    typically takes to process.

Certainly - will do.

---

From bob.briscoe@bt.com  Mon Mar 11 11:48:27 2013
Return-Path: <bob.briscoe@bt.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E4EC21F8EB9 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 11:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6TKVZg5VvLnZ for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 11:48:26 -0700 (PDT)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.99]) by ietfa.amsl.com (Postfix) with ESMTP id F183721F8EB7 for <tsvwg@ietf.org>; Mon, 11 Mar 2013 11:48:25 -0700 (PDT)
Received: from EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) by EVMHR67-UKRD.bt.com (10.187.101.22) with Microsoft SMTP Server (TLS) id 8.3.279.1; Mon, 11 Mar 2013 18:48:24 +0000
Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) with Microsoft SMTP Server (TLS) id 8.3.279.1; Mon, 11 Mar 2013 18:48:24 +0000
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) with Microsoft SMTP Server id 14.2.342.3; Mon, 11 Mar 2013 18:48:24 +0000
Received: from BTP075694.jungle.bt.co.uk ([10.111.12.171])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id r2BImKif017977; Mon, 11 Mar 2013 18:48:22 GMT
Message-ID: <201303111848.r2BImKif017977@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 11 Mar 2013 18:48:20 +0000
To: t.petch <ietfc@btconnect.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <00d801ce1b5d$2567ef40$4001a8c0@gateway.2wire.net>
References: <20130221162137.31566.7988.idtracker@ietfa.amsl.com> <20130306091510.GA45477@verdi> <00d801ce1b5d$2567ef40$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-byte-pkt-congest-09.txt>(Byte and Packet Congestion Notification) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 18:48:27 -0000

Tom,

Tx for the forensics on the request to switch to BCP from INF, which 
are correct.

I just want to add that the change from INF to BCP required a 
complete re-write to itemise the recommendations clearly and briefly.

On length:

         The average size of all the IETFs BCPs is 41905 Bytes
         (Source: <http://www.rfc-editor.org/bcp-index.html>)

         draft-ietf-tsvwg-byte-pkt-congest-09.txt is 47528 Bytes
         (including the appendix listing all the draft deltas, which 
will be removed by the RFC editor)

Jukka did a great job of cutting down the doc to 26pp (without the 
appendices). The recommendations are all pulled together into the 
first major section, p8-11. Then the second major section justifies 
them in p12-16.

The rest is critique of past advice, which the WG decided to keep, 
because if people in the past thought differently, people in the 
present will jump to the same conclusions and believe they are still 
right, unless we document why ideas changed.


John's point about academic style criticises a sentence in the 
abstract for being too vague. An abstract says what the document is 
about. Most people understand that they have to read a little further 
than the abstract to get to the specific advice.


Bob

At 17:56 07/03/2013, t.petch wrote:
>----- Original Message -----
>From: "John Leslie" <john@jlc.net>
>To: <ietf@ietf.org>
>Cc: <tsvwg@ietf.org>
>Sent: Wednesday, March 06, 2013 9:15 AM
> > The IESG <iesg-secretary@ietf.org> wrote:
> > >
> > > The IESG has received a request from the Transport Area Working
>Group WG
> > > (tsvwg) to consider the following document:
> > > - 'Byte and Packet Congestion Notification'
> > >   <draft-ietf-tsvwg-byte-pkt-congest-09.txt> as Best Current
>Practice
> > >
> > > The IESG plans to make a decision in the next few weeks, and
>solicits
> > > final comments on this action. Please send substantive comments to
>the
> > > ietf@ietf.org mailing lists by 2013-03-07. Exceptionally, comments
>may be
> > > sent to iesg@ietf.org instead. In either case, please retain the
> > > beginning of the Subject line to allow automated sorting.
> >
> >    This document has a rather long history in TSVWG, and IMHO deserves
> > to be published as is, but not as a Best Current Practice.
> >
> >    Fundamentally, it updates RFC 2309 (an Informational document) to
> > deprecate a practice which seems essentially unused, and goes into
>detail
> > appropriate to an academic paper about the theoretical basis for doing
> > this.
> >
> >    According to the document writeup I find in the datatracker:
> > ]
> > ] This document is intended as BCP. (This was discussed at IETF-81 and
>that
> > ] the status changed from Informational to BCP, because the draft
>provides
> > ] guidance to implementors and people configuring routers and hosts).
> >
> >    I cannot find any minutes for that WG meeting. I am willing to
>believe
> > Gorry that such a recommendation happened at that meeting (where I was
>not
> > present), but I do not find it to have been discussed on-list at all.
>
>John
>
>I agree that minutes for IETF81 appear not to have been circulated but
>they are available at
>
>http://tools.ietf.org/wg/tsvwg/minutes?item=minutes81.html
>
>and do record the discussion and its outcome.
>
>The agreement of the change in status to BCP was reported to the list in
>passing, 7 Sep 2011, and provoked no comment, no discussion.
>
>And the WGLC last call clearly stated BCP as did Bob's summary of the
>updates.
>
>So we knew about it, if we wanted to, and did not comment.
>
>Tom Petch
>
>
> >
> >    I do not agree that its major purpose is to provide such advice,
>nor
> > do I see how "implementors and people configuring" would be likely to
> > get clear advice from a 43-page document that reads like an academic
> > paper. For one example:
> >
> > > Abstract
> > >    This document provides recommendations of best current practice
>for
> > >    dropping or marking packets using active queue management (AQM)
>such
> > >    as random early detection (RED) or pre-congestion notification
>(PCN).
> > >    We give three strong recommendations: (1) packet size should be
>taken
> > >    into account when transports read and respond to congestion
> > >    indications...
> >
> >    "Packet size should be taken into account when transports read and
> > respond to congestion indications" is simply too vague. There has been
> > on-list discussion of what this might mean; but it has not resulted in
> > clear, concise advice to implementors.
> >
> >    In no sense do I believe it worth holding up this document any
>longer
> > to add "clear advice" -- I believe that would only add years to the
>delay.
> > The document deserves to be published, but with Informational status
>so
> > folks don't spend their time trying to interpret its "advice".
> >
> > --
> > John Leslie <john@jlc.net>
> >

________________________________________________________________
Bob Briscoe,                                                  BT 


From mthornbu@adobe.com  Mon Mar 11 12:26:45 2013
Return-Path: <mthornbu@adobe.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6036F11E81F0 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 12:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8HJwwGVgB5EG for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 12:26:44 -0700 (PDT)
Received: from exprod6og117.obsmtp.com (exprod6og117.obsmtp.com [64.18.1.39]) by ietfa.amsl.com (Postfix) with ESMTP id E9B8021F8CF0 for <tsvwg@ietf.org>; Mon, 11 Mar 2013 12:26:38 -0700 (PDT)
Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob117.postini.com ([64.18.5.12]) with SMTP ID DSNKUT4v7XmAxgi6enT/QfSrYK8+z3TjomLK@postini.com; Mon, 11 Mar 2013 12:26:44 PDT
Received: from inner-relay-4.eur.adobe.com (inner-relay-4.adobe.com [193.104.215.14]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r2BJNU1v021682; Mon, 11 Mar 2013 12:23:31 -0700 (PDT)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-4.eur.adobe.com (8.12.10/8.12.9) with ESMTP id r2BJQYXL020032; Mon, 11 Mar 2013 12:26:34 -0700 (PDT)
Received: from nambx05.corp.adobe.com ([10.8.189.124]) by nahub02.corp.adobe.com ([10.8.189.98]) with mapi; Mon, 11 Mar 2013 12:26:34 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: Cameron Byrne <cb.list6@gmail.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-thornburgh-adobe-rtmfp@tools.ietf.org" <draft-thornburgh-adobe-rtmfp@tools.ietf.org>
Date: Mon, 11 Mar 2013 12:26:31 -0700
Thread-Topic: [tsvwg] feedback on draft-thornburgh-adobe-rtmfp-04
Thread-Index: Ac4dSaC1lqv99aM+RriymqSO5kUjTgBOjfGA
Message-ID: <02485FF93524F8408ECA9608E47D9F20098C969C06@nambx05.corp.adobe.com>
References: <CAD6AjGSS=vyATF70fH4JV6XtRF_JfPsk7ase8M=1oY_pS1ihJg@mail.gmail.com>
In-Reply-To: <CAD6AjGSS=vyATF70fH4JV6XtRF_JfPsk7ase8M=1oY_pS1ihJg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [tsvwg] feedback on draft-thornburgh-adobe-rtmfp-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 19:26:45 -0000

hi Cameron. thanks for your feedback.

RTMFP is fundamentally an endpoint-to-endpoint transport protocol (like TCP=
), and is typically carried in UDP datagrams. a practical RTMFP implementat=
ion, such as that in Flash Player, will typically have multiple interfaces =
for one protocol instance/entity, including one or more interfaces for dire=
ctly-attached IPv4, one or more for directly-attached IPv6, and potentially=
 one or more TURN proxy interfaces (in the case of Flash Player, a pre-RFC =
version of TURN), all of which can be operable simultaneously.

like any other protocol that runs over IP, RTMFP can't send a datagram dire=
ctly to an IPv6 destination if it only has IPv4 physical interfaces (or vic=
e versa).  DNS64 is applicable to applications that always do DNS lookups t=
o discover the addresses with which to communicate (typically a server of s=
ome sort -- certainly not an ephemeral peer).  in those situations, an appl=
ication using RTMFP would learn the magical translated address with which t=
o communicate and could establish a session in the normal way through the t=
ranslator.  RTMFP's forwarder/redirector mechanism (FIHello/Redirect -- the=
 only chunks containing socket address literals) isn't required for general=
 session establishment.

the forwarder/redirector mechanism enables additional functionality (P2P lo=
okup/introduction and UDP hole-punching support for NAT and firewall traver=
sal) beyond the application types for which the DNS64 approach is intended.

note also that an FIHello or a Redirect could come in an IPv4 packet but co=
ntain IPv6 socket addresses, or vice versa.  a Redirect could contain a mix=
 of IPv4 and IPv6 addresses.  the FIHello mechanism can be used by a server=
 (in a manner similar to how http://cc.rtmfp.net works) to discover the ref=
lexive address of the other address family (if present) of a connected clie=
nt.  an application using RTMFP can also use ICE, if it desires, and share =
the same socket(s) for RTMFP and ICE, since the likelihood of a STUN packet=
 being decryptable/decodable as a valid RTMFP packet is very very small. =20

-michael thornburgh


> From: Cameron Byrne
> Sent: Saturday, March 09, 2013 8:42 PM
>=20
> Hi,
>=20
> I have some strong concerns about this I-D and RTMFP in general with
> regards to how they treat communication between IPv4-only and
> IPv6-only systems.
>=20
> Given the reality that RIPE and APNIC are both out of IPv4, it is
> unacceptable to introduce a protocol that bifurcates the Internet into
> those that have IPv4 and those that have IPv6.  AFAIK,
> draft-thornburgh-adobe-rtmfp-04 only accounts for the ability talk
> within a single address family.
>=20
> Similar solutions like ICE (rfc5245) solve this problem by using TURN,
> and the general approach would be to DNS64 / NAT64
>=20
> I do not believe this I-D should be adopted as WG item and i do not
> think it is eligible for standards tracks qualification since it
> communicates IPv4 literals / referrals as its fundamental design, thus
> not accounting for the scenarios in RFC 6144 and explicitly breaking
> network, like mine, that use the proposed standard RFC 6146.
>=20
>=20
> CB

From gorry@erg.abdn.ac.uk  Mon Mar 11 13:36:40 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5643421F9098 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 13:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cdK8cjN9DeDl for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 13:36:39 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 897EB21F9071 for <tsvwg@ietf.org>; Mon, 11 Mar 2013 13:36:39 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id D75212B44C1; Mon, 11 Mar 2013 20:36:38 +0000 (GMT)
Received: from dhcp-1504.meeting.ietf.org (dhcp-1504.meeting.ietf.org [130.129.21.4]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 146AE2B4265 for <tsvwg@ietf.org>; Mon, 11 Mar 2013 20:36:37 +0000 (GMT)
Message-ID: <513E4053.3090409@erg.abdn.ac.uk>
Date: Mon, 11 Mar 2013 16:36:35 -0400
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: tsvwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [tsvwg] Comment on security considerations of draft-ietf-tsvwg-sctp-sack-immediately
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 20:36:40 -0000

Michael,

Is there  potential extra remote processing/capacity of sending segments 
with the I-bit or not?

(Am I correct in thinking that there is actually little extra work that 
can be forced on a receiver using this bit?)

It may be worth explaining why this is an issue or non-issue in the 
security considerations. If we do this it may be worth noting this, this 
may be better than assuming reviewers are familiar with sctp.

Gorry

From shares@ndzh.com  Mon Mar 11 14:14:27 2013
Return-Path: <shares@ndzh.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C286221F8E05 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 14:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.168
X-Spam-Level: ***
X-Spam-Status: No, score=3.168 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_50=0.001, DOS_OUTLOOK_TO_MX=1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gACFo7tFKXK2 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 14:14:27 -0700 (PDT)
Received: from hickoryhill-consulting.com (unknown [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 1327C21F8CFA for <tsvwg@ietf.org>; Mon, 11 Mar 2013 14:14:26 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=130.129.16.73; 
From: "Susan Hares" <shares@ndzh.com>
To: <tsvwg@ietf.org>
Date: Mon, 11 Mar 2013 17:14:25 -0400
Message-ID: <004e01ce1e9d$694a7870$3bdf6950$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004F_01CE1E7B.E2392690"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac4enL5MzsqPJ8tbTUWJ/DZtR2F3kg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Subject: [tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP need
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 21:14:27 -0000

This is a multipart message in MIME format.

------=_NextPart_000_004F_01CE1E7B.E2392690
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 

To follow-up on the proposal in the RFC5127 changes proposed in the draft

draft-geib-tswf-diffserv-intercon-02.txt, I ask do the carriers need the
RFC5127 network control (CS6 DSCP) to run BGP? 

 

Sue Hares

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>To follow-up =
on the proposal in the RFC5127 changes proposed in the =
draft<o:p></o:p></p><p =
class=3DMsoNormal>draft-geib-tswf-diffserv-intercon-02.txt, I ask do the =
carriers need the RFC5127 network control (CS6 DSCP) to run BGP? =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Sue Hares<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_004F_01CE1E7B.E2392690--


From david.black@emc.com  Mon Mar 11 15:56:49 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDD5521F9105; Mon, 11 Mar 2013 15:56:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q+0hs1sMEa9S; Mon, 11 Mar 2013 15:56:49 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2223221F90F6; Mon, 11 Mar 2013 15:56:48 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2BMuheL002059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Mar 2013 18:56:47 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 11 Mar 2013 18:56:31 -0400
Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2BMuURh010111; Mon, 11 Mar 2013 18:56:30 -0400
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Mon, 11 Mar 2013 18:56:30 -0400
From: "Black, David" <david.black@emc.com>
To: "idr@ietf.org" <idr@ietf.org>
Date: Mon, 11 Mar 2013 18:56:27 -0400
Thread-Topic: [tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP need
Thread-Index: Ac4enL5MzsqPJ8tbTUWJ/DZtR2F3kgADje1g
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71290FA8CA7@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8D3D17ACE214DC429325B2B98F3AE71290FA8CA7MX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: [tsvwg] FW: draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP need
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 22:56:50 -0000

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

(+idr mailing list in the hope of finding more carriers)

This question is specifically whether a Network Control (CS6) interconnect =
traffic class is needed in addition to a Priority (EF) traffic class for ef=
fective support of BGP traffic across carrier network interconnections.

The slide that Sue is referring to takes the position (for discussion) that=
 it is not needed:

http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx

Easy does it on the dead cats and rotten tomatoes, please ...

Thanks,
--David (tsvwg co-chair)

From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of S=
usan Hares
Sent: Monday, March 11, 2013 5:14 PM
To: tsvwg@ietf.org
Subject: [tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP need


To follow-up on the proposal in the RFC5127 changes proposed in the draft
draft-geib-tswf-diffserv-intercon-02.txt, I ask do the carriers need the RF=
C5127 network control (CS6 DSCP) to run BGP?

Sue Hares


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>(+idr mail=
ing list in the hope of finding more carriers)<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";col=
or:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>This question is spe=
cifically whether a Network Control (CS6) interconnect traffic class is nee=
ded in addition to a Priority (EF) traffic class for effective support of B=
GP traffic across carrier network interconnections.<o:p></o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New=
";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:black'>The slide that =
Sue is referring to takes the position (for discussion) that it is not need=
ed:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0=
pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";c=
olor:black'><a href=3D"http://www.ietf.org/proceedings/86/slides/slides-86-=
tsvwg-5.pptx">http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.p=
ptx</a><o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier Ne=
w";color:black'>Easy does it on the dead cats and rotten tomatoes, please .=
..<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0p=
t;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";co=
lor:black'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:10.0pt;font-family:"Courier New";color:black'>--David (tsvwg co-=
chair)</span><span style=3D'font-family:"Courier New";color:black'><o:p></o=
:p></span></p></div></div><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><div=
><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in=
 0in 0in'><p class=3DMsoNormal style=3D'margin-left:.5in'><b><span style=3D=
'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> tsvwg-bounces=
@ietf.org [mailto:tsvwg-bounces@ietf.org] <b>On Behalf Of </b>Susan Hares<b=
r><b>Sent:</b> Monday, March 11, 2013 5:14 PM<br><b>To:</b> tsvwg@ietf.org<=
br><b>Subject:</b> [tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does=
 BGP need<o:p></o:p></span></p></div></div><p class=3DMsoNormal style=3D'ma=
rgin-left:.5in'><o:p>&nbsp;</o:p></p><p class=3DMsoNormal style=3D'margin-l=
eft:.5in'><o:p>&nbsp;</o:p></p><p class=3DMsoNormal style=3D'margin-left:.5=
in'>To follow-up on the proposal in the RFC5127 changes proposed in the dra=
ft<o:p></o:p></p><p class=3DMsoNormal style=3D'margin-left:.5in'>draft-geib=
-tswf-diffserv-intercon-02.txt, I ask do the carriers need the RFC5127 netw=
ork control (CS6 DSCP) to run BGP? <o:p></o:p></p><p class=3DMsoNormal styl=
e=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p><p class=3DMsoNormal style=3D'm=
argin-left:.5in'>Sue Hares<o:p></o:p></p><p class=3DMsoNormal style=3D'marg=
in-left:.5in'><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE71290FA8CA7MX15Acorpemccom_--

From tony.li@tony.li  Mon Mar 11 16:08:26 2013
Return-Path: <tony.li@tony.li>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A969821F907D for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 16:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DmHgOZCNQhLU for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 16:08:26 -0700 (PDT)
Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:64]) by ietfa.amsl.com (Postfix) with ESMTP id 35ABB21F8C69 for <tsvwg@ietf.org>; Mon, 11 Mar 2013 16:08:26 -0700 (PDT)
Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta07.emeryville.ca.mail.comcast.net with comcast id ALY91l0061Y3wxoA7P8SYi; Mon, 11 Mar 2013 23:08:26 +0000
Received: from [10.66.230.38] ([64.236.139.254]) by omta15.emeryville.ca.mail.comcast.net with comcast id AP6E1l0075VXD0o8bP6GtE; Mon, 11 Mar 2013 23:06:24 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290FA8CA7@MX15A.corp.emc.com>
Date: Mon, 11 Mar 2013 16:06:13 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E43753B-0974-430E-936A-3D1A2ED6F4D8@tony.li>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA8CA7@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1363043306; bh=holIoLY0GBtS1TQmgjPLm7MtfB5FLhtDJEijr7vaQUA=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=GOI8HxZ0mHKHMXrLgvUe7k0VKj805GLBJ5q7UCFmpN6LVNiV8A0vZFt0tgBNjM3lh 8s00R7xktmmO6OCD25YrDe1hUS+u9zrsylPNdmb1Pd17bVOyIEBdjUKMT3A7KPDblK Mq8a5cXYInnUyAjPticTTQYUBZh5kqKZYKzpFrJPUmEf/fvcrAa2iXdGflfYcSR3a/ gFZNNXVpOeVkjmPPjBIQg8XGzpnysxEtPB4ze0t1GcSLsml18PiM5CwH00JdRBXaGq uQU8OL1VSc0CHmT7munuglMJuXcSfQ4Na6V5mqQEIZjh9boWnBZhZuAfX9VfmsMVLi h7F5HLrOj1EQg==
Cc: "idr@ietf.org" <idr@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] [Idr] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP need
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 23:08:26 -0000

David,

If a IX fabric were so heavily congested that BGP were subject to =
significant drops, don't you think that would be an issue?  If the =
underlying TCP connection breaks, BGP will withdraw all routes to and =
from that particular neighbor, severely disrupting routing.

IMHO, network control is of more concern than any transit traffic, and =
that every router vendor should simply give network control absolute =
priority anytime any QoS is enabled.  And this shouldn't even be subject =
to user override.

Thus, the only thing that warrants discussing is what we should say for =
those folks who use a layer 2 switching fabric at their IX.

Regards,
Tony



On Mar 11, 2013, at 3:56 PM, "Black, David" <david.black@emc.com> wrote:

> (+idr mailing list in the hope of finding more carriers)
> =20
> This question is specifically whether a Network Control (CS6) =
interconnect traffic class is needed in addition to a Priority (EF) =
traffic class for effective support of BGP traffic across carrier =
network interconnections.
> =20
> The slide that Sue is referring to takes the position (for discussion) =
that it is not needed:
> =20
> http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx
> =20
> Easy does it on the dead cats and rotten tomatoes, please ...
> =20
> Thanks,
> --David (tsvwg co-chair)
> =20
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf =
Of Susan Hares
> Sent: Monday, March 11, 2013 5:14 PM
> To: tsvwg@ietf.org
> Subject: [tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP =
need
> =20
> =20
> To follow-up on the proposal in the RFC5127 changes proposed in the =
draft
> draft-geib-tswf-diffserv-intercon-02.txt, I ask do the carriers need =
the RFC5127 network control (CS6 DSCP) to run BGP?
> =20
> Sue Hares
> =20
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr


From cb.list6@gmail.com  Mon Mar 11 18:52:40 2013
Return-Path: <cb.list6@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EEE621F89E2 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 18:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.318
X-Spam-Level: 
X-Spam-Status: No, score=-1.318 tagged_above=-999 required=5 tests=[AWL=-1.173, BAYES_00=-2.599, FRT_ADOBE2=2.455, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rs4HujtK4UpM for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 18:52:39 -0700 (PDT)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id A4E2621F89DA for <tsvwg@ietf.org>; Mon, 11 Mar 2013 18:52:38 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id x51so4081773wey.4 for <tsvwg@ietf.org>; Mon, 11 Mar 2013 18:52:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=F4V3ULaOswjyPpusgm/a/jcqjERvIiqT5/GXuwajIRg=; b=dvVldU+4efI+VYc/RI6YPmj2OJlBATcGegWbFgYLYhh4gT0JpZvzyoi5i5Sh2hKjIP IVM2NRGG5qb3rUlARX8KyQERPNtFRUb4asMr6sNsxHVXHkiidJF33M48kwu8C5mj4PLx v9A4tVBCUkY0qaYGIZfqDEcvAeQkbQZ99l/e6ml/sIudKFQTVD7CYK4jIKFiE6wHxKj6 20GZ0NzwuXCxukb0/OTY/lhJM5cUYQtxvTta1f7hIOKXvcXGhMC3qFinKJmt3vS/2PPp /gX44cxnxV3lRQ6Q0jIurrNN+kS/LcNI40nfbRo1gsB+MCeNSPi2d/zl/ev4Uf234xWf ow4w==
MIME-Version: 1.0
X-Received: by 10.194.123.103 with SMTP id lz7mr10187354wjb.10.1363053157828;  Mon, 11 Mar 2013 18:52:37 -0700 (PDT)
Received: by 10.194.20.35 with HTTP; Mon, 11 Mar 2013 18:52:37 -0700 (PDT)
In-Reply-To: <02485FF93524F8408ECA9608E47D9F20098C969C06@nambx05.corp.adobe.com>
References: <CAD6AjGSS=vyATF70fH4JV6XtRF_JfPsk7ase8M=1oY_pS1ihJg@mail.gmail.com> <02485FF93524F8408ECA9608E47D9F20098C969C06@nambx05.corp.adobe.com>
Date: Mon, 11 Mar 2013 18:52:37 -0700
Message-ID: <CAD6AjGRrTA9ixBvEAX+6Azi-TZtD=vbRR=D-H6qRkLfs4ROH_g@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Michael Thornburgh <mthornbu@adobe.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-thornburgh-adobe-rtmfp@tools.ietf.org" <draft-thornburgh-adobe-rtmfp@tools.ietf.org>
Subject: Re: [tsvwg] feedback on draft-thornburgh-adobe-rtmfp-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 01:52:40 -0000

Michael,

On Mon, Mar 11, 2013 at 12:26 PM, Michael Thornburgh <mthornbu@adobe.com> w=
rote:
> hi Cameron. thanks for your feedback.
>
> RTMFP is fundamentally an endpoint-to-endpoint transport protocol (like T=
CP), and is typically carried in UDP datagrams. a practical RTMFP implement=
ation, such as that in Flash Player, will typically have multiple interface=
s for one protocol instance/entity, including one or more interfaces for di=
rectly-attached IPv4, one or more for directly-attached IPv6, and potential=
ly one or more TURN proxy interfaces (in the case of Flash Player, a pre-RF=
C version of TURN), all of which can be operable simultaneously.
>

no, i don't think RTMFP is like TCP.  I think it is more akin to ICE, no?

A typical flash player has multiple interfaces?  Can you explain more?
I figure most flash players have one functional interface (not
counting overlay networks like 6to4 that are hazardous)


> like any other protocol that runs over IP, RTMFP can't send a datagram di=
rectly to an IPv6 destination if it only has IPv4 physical interfaces (or v=
ice versa).  DNS64 is applicable to applications that always do DNS lookups=
 to discover the addresses with which to communicate (typically a server of=
 some sort -- certainly not an ephemeral peer).  in those situations, an ap=
plication using RTMFP would learn the magical translated address with which=
 to communicate and could establish a session in the normal way through the=
 translator.  RTMFP's forwarder/redirector mechanism (FIHello/Redirect -- t=
he only chunks containing socket address literals) isn't required for gener=
al session establishment.
>

Right, the lack of DNS lookup (no DNS64) and lack of TURN support are
exactly my object to RTMFP.  These choices result in a design flaw
IMHO.

We cannot bring to this working group or to standards track a protocol
like this.  Especially when we already have ICE.  I know some people
think its funny to say "the great thing about standards is that there
are so many to choose from", but i do not think it is funny.

Is there something specific that RTMFP brings to the table that cannot
be achieved with ICE / TURN / STUN ?  AFAIK, RTMFP is an inferior
subset of ICE.


> the forwarder/redirector mechanism enables additional functionality (P2P =
lookup/introduction and UDP hole-punching support for NAT and firewall trav=
ersal) beyond the application types for which the DNS64 approach is intende=
d.
>
> note also that an FIHello or a Redirect could come in an IPv4 packet but =
contain IPv6 socket addresses, or vice versa.  a Redirect could contain a m=
ix of IPv4 and IPv6 addresses.  the FIHello mechanism can be used by a serv=
er (in a manner similar to how http://cc.rtmfp.net works) to discover the r=
eflexive address of the other address family (if present) of a connected cl=
ient.  an application using RTMFP can also use ICE, if it desires, and shar=
e the same socket(s) for RTMFP and ICE, since the likelihood of a STUN pack=
et being decryptable/decodable as a valid RTMFP packet is very very small.
>

I can't parse any of that.  What is the point you are trying to make?
An RTMFP client can also run ICE?  Ok, why do i need RTMFP client?
Why can't i just run ICE?

In summary, i object to this being a WG document.  There is no clear
reason why we need RTMFP and ICE.  ICE is already the relevant
standard and appears fit for purpose.  RTMFP is not fit for purpose
since it has no mechanism for working in a world with IPv4-only and
IPv6-only hosts that must communicate with one another.  Thus, RTMFP
is a step backwards.

But, please let me know if i am misunderstanding something.  But,
honestly, as a mobile network operator with IPv6-only host i am quite
familiar with RTMFP and i have a strong operational bias against  the
protocol and find it extremely harmful for IPv6 adoption.

Cameron

> -michael thornburgh
>
>
>> From: Cameron Byrne
>> Sent: Saturday, March 09, 2013 8:42 PM
>>
>> Hi,
>>
>> I have some strong concerns about this I-D and RTMFP in general with
>> regards to how they treat communication between IPv4-only and
>> IPv6-only systems.
>>
>> Given the reality that RIPE and APNIC are both out of IPv4, it is
>> unacceptable to introduce a protocol that bifurcates the Internet into
>> those that have IPv4 and those that have IPv6.  AFAIK,
>> draft-thornburgh-adobe-rtmfp-04 only accounts for the ability talk
>> within a single address family.
>>
>> Similar solutions like ICE (rfc5245) solve this problem by using TURN,
>> and the general approach would be to DNS64 / NAT64
>>
>> I do not believe this I-D should be adopted as WG item and i do not
>> think it is eligible for standards tracks qualification since it
>> communicates IPv4 literals / referrals as its fundamental design, thus
>> not accounting for the scenarios in RFC 6144 and explicitly breaking
>> network, like mine, that use the proposed standard RFC 6146.
>>
>>
>> CB

From mthornbu@adobe.com  Mon Mar 11 21:09:09 2013
Return-Path: <mthornbu@adobe.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DFA621F87C4 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 21:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.372
X-Spam-Level: 
X-Spam-Status: No, score=-105.372 tagged_above=-999 required=5 tests=[AWL=-1.228, BAYES_00=-2.599, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z0QVdgyFDL38 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 21:09:08 -0700 (PDT)
Received: from exprod6og102.obsmtp.com (exprod6og102.obsmtp.com [64.18.1.183]) by ietfa.amsl.com (Postfix) with ESMTP id DB0A321F875C for <tsvwg@ietf.org>; Mon, 11 Mar 2013 21:09:03 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob102.postini.com ([64.18.5.12]) with SMTP ID DSNKUT6qXoW9ODZemaA/kjYdBfs0zJIMQ4CV@postini.com; Mon, 11 Mar 2013 21:09:07 PDT
Received: from inner-relay-4.eur.adobe.com (inner-relay-4b [10.128.4.237]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r2C4912h026959; Mon, 11 Mar 2013 21:09:01 -0700 (PDT)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-4.eur.adobe.com (8.12.10/8.12.9) with ESMTP id r2C48xXL026207; Mon, 11 Mar 2013 21:09:00 -0700 (PDT)
Received: from nambx05.corp.adobe.com ([10.8.189.124]) by nahub02.corp.adobe.com ([10.8.189.98]) with mapi; Mon, 11 Mar 2013 21:08:59 -0700
From: Michael Thornburgh <mthornbu@adobe.com>
To: Cameron Byrne <cb.list6@gmail.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-thornburgh-adobe-rtmfp@tools.ietf.org" <draft-thornburgh-adobe-rtmfp@tools.ietf.org>
Date: Mon, 11 Mar 2013 21:08:55 -0700
Thread-Topic: [tsvwg] feedback on draft-thornburgh-adobe-rtmfp-04
Thread-Index: Ac4exEdZpTGYJlqrQXmzrpJLQau1ygAB3meQ
Message-ID: <02485FF93524F8408ECA9608E47D9F20098C969D2B@nambx05.corp.adobe.com>
References: <CAD6AjGSS=vyATF70fH4JV6XtRF_JfPsk7ase8M=1oY_pS1ihJg@mail.gmail.com> <02485FF93524F8408ECA9608E47D9F20098C969C06@nambx05.corp.adobe.com> <CAD6AjGRrTA9ixBvEAX+6Azi-TZtD=vbRR=D-H6qRkLfs4ROH_g@mail.gmail.com>
In-Reply-To: <CAD6AjGRrTA9ixBvEAX+6Azi-TZtD=vbRR=D-H6qRkLfs4ROH_g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [tsvwg] feedback on draft-thornburgh-adobe-rtmfp-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 04:09:09 -0000

replies inline.

> From: Cameron Byrne
> Sent: Monday, March 11, 2013 6:53 PM
>=20
> Michael,
>=20
> On Mon, Mar 11, 2013 at 12:26 PM, Michael Thornburgh <mthornbu@adobe.com>=
 wrote:
> > hi Cameron. thanks for your feedback.
> >
> > RTMFP is fundamentally an endpoint-to-endpoint transport protocol (like=
 TCP), and is typically
> carried in UDP datagrams. a practical RTMFP implementation, such as that =
in Flash Player, will
> typically have multiple interfaces for one protocol instance/entity, incl=
uding one or more interfaces
> for directly-attached IPv4, one or more for directly-attached IPv6, and p=
otentially one or more TURN
> proxy interfaces (in the case of Flash Player, a pre-RFC version of TURN)=
, all of which can be
> operable simultaneously.
> >
>=20
> no, i don't think RTMFP is like TCP.  I think it is more akin to ICE, no?

no. RTMFP is a complete connection-oriented transport protocol, like TCP or=
 SCTP, including parallel message-oriented data flows, flow control, conges=
tion control, variable delivery reliability for messages, etc.  RTMFP sessi=
ons between two endpoints are normally established with a 4-way handshake (=
Figure 8 in Section 3.5.1.1).

the protocol includes additional facilities (the FIHello and Redirect chunk=
s) for implementing P2P lookup/intro, UDP hole-punching, and clustering/loa=
d balancing.
=20
> A typical flash player has multiple interfaces?  Can you explain more?
> I figure most flash players have one functional interface (not
> counting overlay networks like 6to4 that are hazardous)

Flash Player's RTMFP implements one interface each for an IPv4 INADDR_ANY s=
ocket, an IPv6 IN6ADDR_ANY socket, and optionally a (pre-RFC version of) TU=
RN proxy.  the same RTMFP instance/entity/identity can be reached through a=
ny of the socket addresses associated with any of those interfaces.

> > like any other protocol that runs over IP, RTMFP can't send a datagram =
directly to an IPv6
> destination if it only has IPv4 physical interfaces (or vice versa).  DNS=
64 is applicable to
> applications that always do DNS lookups to discover the addresses with wh=
ich to communicate (typically
> a server of some sort -- certainly not an ephemeral peer).  in those situ=
ations, an application using
> RTMFP would learn the magical translated address with which to communicat=
e and could establish a
> session in the normal way through the translator.  RTMFP's forwarder/redi=
rector mechanism
> (FIHello/Redirect -- the only chunks containing socket address literals) =
isn't required for general
> session establishment.
> >
>=20
> Right, the lack of DNS lookup (no DNS64) and lack of TURN support are
> exactly my object to RTMFP.  These choices result in a design flaw
> IMHO.

disagree.  using DNS is for the application, not the transport protocol.  t=
he application uses DNS to discover one (or more) candidate addresses for a=
n endpoint, and gives those addresses to the transport protocol to establis=
h the connection to the endpoint.

RTMFP (like any other UDP-based protocol) can be used with a TURN proxy.  a=
 TURN proxy is simply a remote UDP socket.

> We cannot bring to this working group or to standards track a protocol
> like this.  Especially when we already have ICE.  I know some people
> think its funny to say "the great thing about standards is that there
> are so many to choose from", but i do not think it is funny.

note that at this time, this specification is on the Informational track an=
d documents a vendor-supplied network transport protocol that is in active =
use and is widely deployed in the Internet today.  TSVWG is being informed =
as this working group has a relevant audience that would find RTMFP's featu=
res of interest/value, and that should be informed of the specification's e=
xistence.

> Is there something specific that RTMFP brings to the table that cannot
> be achieved with ICE / TURN / STUN ?  AFAIK, RTMFP is an inferior
> subset of ICE.

RTMFP is a connection-oriented transport protocol.  see my comment above.  =
it is not an "ICE replacement", although ICE should not be needed when usin=
g RTMFP's facilities for P2P lookup/intro & UDP hole-punching.

> > the forwarder/redirector mechanism enables additional functionality (P2=
P lookup/introduction and UDP
> hole-punching support for NAT and firewall traversal) beyond the applicat=
ion types for which the DNS64
> approach is intended.
> >
> > note also that an FIHello or a Redirect could come in an IPv4 packet bu=
t contain IPv6 socket
> addresses, or vice versa.  a Redirect could contain a mix of IPv4 and IPv=
6 addresses.  the FIHello
> mechanism can be used by a server (in a manner similar to how http://cc.r=
tmfp.net works) to discover
> the reflexive address of the other address family (if present) of a conne=
cted client.  an application
> using RTMFP can also use ICE, if it desires, and share the same socket(s)=
 for RTMFP and ICE, since the
> likelihood of a STUN packet being decryptable/decodable as a valid RTMFP =
packet is very very small.
> >
>=20
> I can't parse any of that.  What is the point you are trying to make?
> An RTMFP client can also run ICE?  Ok, why do i need RTMFP client?
> Why can't i just run ICE?

the point is: should you really want to use ICE for setting up RTMFP sessio=
ns (instead of, or in addition to, the facilities RTMFP provides), you can.

> In summary, i object to this being a WG document.  There is no clear
> reason why we need RTMFP and ICE.  ICE is already the relevant
> standard and appears fit for purpose.  RTMFP is not fit for purpose
> since it has no mechanism for working in a world with IPv4-only and
> IPv6-only hosts that must communicate with one another.  Thus, RTMFP
> is a step backwards.

as i mentioned previously, RTMFP works like any other transport protocol in=
 application contexts where DNS64 is appropriate (just like TCP).  RTMFP al=
so has additional features and facilities that can do interesting things in=
 application contexts where DNS64 is not appropriate (like peer-to-peer sce=
narios, where you wouldn't be looking up peers in the DNS anyway).

> But, please let me know if i am misunderstanding something.  But,
> honestly, as a mobile network operator with IPv6-only host i am quite
> familiar with RTMFP and i have a strong operational bias against  the
> protocol and find it extremely harmful for IPv6 adoption.

i think you are misunderstanding what RTMFP is and what it's for.  i hope m=
y statements above have helped change that.  if not, i'll be talking briefl=
y about RTMFP and this I-D in thursday's TSVWG session, and i invite you to=
 read the I-D with my statements in mind (in particular, sections 1, 3.1, 3=
.5 and 3.6).

-michael thornburgh

>=20
> Cameron
>=20
> > -michael thornburgh
> >
> >
> >> From: Cameron Byrne
> >> Sent: Saturday, March 09, 2013 8:42 PM
> >>
> >> Hi,
> >>
> >> I have some strong concerns about this I-D and RTMFP in general with
> >> regards to how they treat communication between IPv4-only and
> >> IPv6-only systems.
> >>
> >> Given the reality that RIPE and APNIC are both out of IPv4, it is
> >> unacceptable to introduce a protocol that bifurcates the Internet into
> >> those that have IPv4 and those that have IPv6.  AFAIK,
> >> draft-thornburgh-adobe-rtmfp-04 only accounts for the ability talk
> >> within a single address family.
> >>
> >> Similar solutions like ICE (rfc5245) solve this problem by using TURN,
> >> and the general approach would be to DNS64 / NAT64
> >>
> >> I do not believe this I-D should be adopted as WG item and i do not
> >> think it is eligible for standards tracks qualification since it
> >> communicates IPv4 literals / referrals as its fundamental design, thus
> >> not accounting for the scenarios in RFC 6144 and explicitly breaking
> >> network, like mine, that use the proposed standard RFC 6146.
> >>
> >>
> >> CB

From wes@mti-systems.com  Mon Mar 11 21:41:00 2013
Return-Path: <wes@mti-systems.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC1A021F85BF for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 21:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R8PPIm-21Dfn for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 21:41:00 -0700 (PDT)
Received: from atl4mhob07.myregisteredsite.com (atl4mhob07.myregisteredsite.com [209.17.115.45]) by ietfa.amsl.com (Postfix) with ESMTP id DD2F821F859C for <tsvwg@ietf.org>; Mon, 11 Mar 2013 21:40:59 -0700 (PDT)
Received: from mailpod.hostingplatform.com (mail.networksolutionsemail.com [205.178.146.50]) by atl4mhob07.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r2C4ew1s005090 for <tsvwg@ietf.org>; Tue, 12 Mar 2013 00:40:58 -0400
Received: (qmail 1704 invoked by uid 0); 12 Mar 2013 04:40:57 -0000
Received: from unknown (HELO ?10.5.0.38?) (wes@mti-systems.com@95.211.10.3) by 0 with ESMTPA; 12 Mar 2013 04:40:57 -0000
Message-ID: <513EB1BD.4010904@mti-systems.com>
Date: Tue, 12 Mar 2013 00:40:29 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: Michael Thornburgh <mthornbu@adobe.com>, Cameron Byrne <cb.list6@gmail.com>
References: <CAD6AjGSS=vyATF70fH4JV6XtRF_JfPsk7ase8M=1oY_pS1ihJg@mail.gmail.com> <02485FF93524F8408ECA9608E47D9F20098C969C06@nambx05.corp.adobe.com> <CAD6AjGRrTA9ixBvEAX+6Azi-TZtD=vbRR=D-H6qRkLfs4ROH_g@mail.gmail.com> <02485FF93524F8408ECA9608E47D9F20098C969D2B@nambx05.corp.adobe.com>
In-Reply-To: <02485FF93524F8408ECA9608E47D9F20098C969D2B@nambx05.corp.adobe.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-thornburgh-adobe-rtmfp@tools.ietf.org" <draft-thornburgh-adobe-rtmfp@tools.ietf.org>
Subject: Re: [tsvwg] feedback on draft-thornburgh-adobe-rtmfp-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 04:41:00 -0000

On 3/12/2013 12:08 AM, Michael Thornburgh wrote:
> 
> note that at this time, this specification is on the Informational
> track and documents a vendor-supplied network transport protocol that
> is in active use and is widely deployed in the Internet today.  TSVWG
> is being informed as this working group has a relevant audience that
> would find RTMFP's features of interest/value, and that should be
> informed of the specification's existence.
> 


And "thank you" Michael (and Adobe) for working on this!

I don't know how it was misunderstood as having anything to do
with ICE and DNS64, but I would suggest actually looking at the
document before throwing stones!


-- 
Wes Eddy
MTI Systems

From cb.list6@gmail.com  Mon Mar 11 22:03:36 2013
Return-Path: <cb.list6@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9226821F8596 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 22:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.412
X-Spam-Level: 
X-Spam-Status: No, score=-2.412 tagged_above=-999 required=5 tests=[AWL=0.187,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O3vO5y6ZcAP4 for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2013 22:03:35 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by ietfa.amsl.com (Postfix) with ESMTP id 7576321F85AC for <tsvwg@ietf.org>; Mon, 11 Mar 2013 22:03:35 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id ez12so1497054wid.12 for <tsvwg@ietf.org>; Mon, 11 Mar 2013 22:03:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=BiNgcbBcYDit3/v3dYkXv8n8JKIFN4ZGcZNxLboNjzc=; b=hgBzMa+VAkpuMH1QegB87K2DvClCaSiOyzGSP3SiqN/82teqLO8pWa1fKyhyWPqY6f +eLJ0pUlM0KiBICzWe+QVCBMGMSx2KNHZ2c3GRmWXXzGtYK3uWylaRPj8xLsP0Eix/AZ Nsep21BoQzeQAzLuBa7UNorYz1naOI4Pk9ndbK9hQMZvmekNdp9KV4OkoarRIwTJ0Qn5 yXnJ8NSDSWE8BmmMeCDuEy5m1G4zWuC3bvqBKiAG4wdo6KJiTDSwPsEfHPvK2rkobYQd WN2fduOGReXzNvwNCfyGIF04TCopUNYeYMdZpUO0/0dlDjZQFPftLg1gQ3W82uE2L/uM at2Q==
MIME-Version: 1.0
X-Received: by 10.194.123.103 with SMTP id lz7mr10761291wjb.10.1363064614488;  Mon, 11 Mar 2013 22:03:34 -0700 (PDT)
Received: by 10.194.20.35 with HTTP; Mon, 11 Mar 2013 22:03:34 -0700 (PDT)
Received: by 10.194.20.35 with HTTP; Mon, 11 Mar 2013 22:03:34 -0700 (PDT)
In-Reply-To: <513EB1BD.4010904@mti-systems.com>
References: <CAD6AjGSS=vyATF70fH4JV6XtRF_JfPsk7ase8M=1oY_pS1ihJg@mail.gmail.com> <02485FF93524F8408ECA9608E47D9F20098C969C06@nambx05.corp.adobe.com> <CAD6AjGRrTA9ixBvEAX+6Azi-TZtD=vbRR=D-H6qRkLfs4ROH_g@mail.gmail.com> <02485FF93524F8408ECA9608E47D9F20098C969D2B@nambx05.corp.adobe.com> <513EB1BD.4010904@mti-systems.com>
Date: Mon, 11 Mar 2013 22:03:34 -0700
Message-ID: <CAD6AjGTGkfa2-Tzagmc8_RPOQAdM-+zzo_eOgub-+657NcCYSA@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Wesley Eddy <wes@mti-systems.com>
Content-Type: multipart/alternative; boundary=089e012281422710ba04d7b336c1
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, draft-thornburgh-adobe-rtmfp@tools.ietf.org
Subject: Re: [tsvwg] feedback on draft-thornburgh-adobe-rtmfp-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 05:03:36 -0000

--089e012281422710ba04d7b336c1
Content-Type: text/plain; charset=ISO-8859-1

On Mar 11, 2013 9:40 PM, "Wesley Eddy" <wes@mti-systems.com> wrote:
>
> On 3/12/2013 12:08 AM, Michael Thornburgh wrote:
> >
> > note that at this time, this specification is on the Informational
> > track and documents a vendor-supplied network transport protocol that
> > is in active use and is widely deployed in the Internet today.  TSVWG
> > is being informed as this working group has a relevant audience that
> > would find RTMFP's features of interest/value, and that should be
> > informed of the specification's existence.
> >
>
>
> And "thank you" Michael (and Adobe) for working on this!
>
> I don't know how it was misunderstood as having anything to do
> with ICE and DNS64, but I would suggest actually looking at the
> document before throwing stones!
>
>

Perhaps i was thinking more generically about rtmp as problematic without
decomposing out rtmfp.

CB
> --
> Wes Eddy
> MTI Systems

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

<p dir=3D"ltr"><br>
On Mar 11, 2013 9:40 PM, &quot;Wesley Eddy&quot; &lt;<a href=3D"mailto:wes@=
mti-systems.com">wes@mti-systems.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On 3/12/2013 12:08 AM, Michael Thornburgh wrote:<br>
&gt; &gt;<br>
&gt; &gt; note that at this time, this specification is on the Informationa=
l<br>
&gt; &gt; track and documents a vendor-supplied network transport protocol =
that<br>
&gt; &gt; is in active use and is widely deployed in the Internet today. =
=A0TSVWG<br>
&gt; &gt; is being informed as this working group has a relevant audience t=
hat<br>
&gt; &gt; would find RTMFP&#39;s features of interest/value, and that shoul=
d be<br>
&gt; &gt; informed of the specification&#39;s existence.<br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt; And &quot;thank you&quot; Michael (and Adobe) for working on this!<br>
&gt;<br>
&gt; I don&#39;t know how it was misunderstood as having anything to do<br>
&gt; with ICE and DNS64, but I would suggest actually looking at the<br>
&gt; document before throwing stones!<br>
&gt;<br>
&gt;</p>
<p dir=3D"ltr">Perhaps i was thinking more generically about rtmp as proble=
matic without decomposing out rtmfp. <br></p>
<p dir=3D"ltr">CB<br>
&gt; --<br>
&gt; Wes Eddy<br>
&gt; MTI Systems<br>
</p>

--089e012281422710ba04d7b336c1--

From Ruediger.Geib@telekom.de  Tue Mar 12 02:50:42 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3E821F86DD for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 02:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.748
X-Spam-Level: 
X-Spam-Status: No, score=-2.748 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jKvrILGtwrf9 for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 02:50:42 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [80.149.113.247]) by ietfa.amsl.com (Postfix) with ESMTP id 8752521F8463 for <tsvwg@ietf.org>; Tue, 12 Mar 2013 02:50:41 -0700 (PDT)
Received: from he111628.emea1.cds.t-internal.com ([10.134.93.20]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 12 Mar 2013 10:50:38 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE111628.emea1.cds.t-internal.com ([::1]) with mapi; Tue, 12 Mar 2013 10:50:38 +0100
From: <Ruediger.Geib@telekom.de>
To: <shares@ndzh.com>
Date: Tue, 12 Mar 2013 10:50:37 +0100
Thread-Topic: [tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP need
Thread-Index: Ac4enL5MzsqPJ8tbTUWJ/DZtR2F3kgAaY3DQ
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A52D91C@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <004e01ce1e9d$694a7870$3bdf6950$@ndzh.com>
In-Reply-To: <004e01ce1e9d$694a7870$3bdf6950$@ndzh.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: multipart/alternative; boundary="_000_CA7A7C64CC4ADB458B74477EA99DF6F5016A52D91CHE111643EMEA1_"
MIME-Version: 1.0
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP need
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 09:50:42 -0000

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

Sue,

I didn't ask any of my internal BGP expert before sending: is eBGP terminat=
ed by an AS border router? If that's a yes in all cases, Cs6 for eBGP isn't=
 an issue. If eBGP traffic is transmitted within an AS, then mapping of cla=
sses is an issue. I'm not a routing expert.

Regards,

R=FCdiger

________________________________
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of S=
usan Hares
Sent: Monday, March 11, 2013 10:14 PM
To: tsvwg@ietf.org
Subject: [tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP need


To follow-up on the proposal in the RFC5127 changes proposed in the draft
draft-geib-tswf-diffserv-intercon-02.txt, I ask do the carriers need the RF=
C5127 network control (CS6 DSCP) to run BGP?

Sue Hares


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19400">
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: pe=
rsonal-compose
}
.MsoChpDefault {
	FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US link=3Dblue vLink=3Dpurple>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D684144509-12032013>Sue,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D684144509-12032013></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D684144509-12032013>I didn't ask any of my&nbsp;internal BGP expert =
before=20
sending: is eBGP terminated by an AS border router? If that's a yes in all=
=20
cases, Cs6 for eBGP isn't an issue. If eBGP traffic is transmitted within a=
n AS,=20
then mapping of classes is an issue. I'm not a routing=20
expert.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D684144509-12032013></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D684144509-12032013>Regards,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D684144509-12032013></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 face=3DArial><SP=
AN=20
class=3D684144509-12032013>R=FCdiger</SPAN></FONT></DIV><FONT color=3D#0000=
ff size=3D2=20
face=3DArial></FONT><BR>
<DIV dir=3Dltr lang=3Dde class=3DOutlookMessageHeader align=3Dleft>
<HR tabIndex=3D-1>
<FONT size=3D2 face=3DTahoma><B>From:</B> tsvwg-bounces@ietf.org=20
[mailto:tsvwg-bounces@ietf.org] <B>On Behalf Of </B>Susan Hares<BR><B>Sent:=
</B>=20
Monday, March 11, 2013 10:14 PM<BR><B>To:</B> tsvwg@ietf.org<BR><B>Subject:=
</B>=20
[tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP=20
need<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DWordSection1>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>To follow-up on the proposal in the RFC5127 changes pr=
oposed=20
in the draft<o:p></o:p></P>
<P class=3DMsoNormal>draft-geib-tswf-diffserv-intercon-02.txt, I ask do the=
=20
carriers need the RFC5127 network control (CS6 DSCP) to run BGP? <o:p></o:p=
></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>Sue Hares<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P></DIV></BODY></HTML>

--_000_CA7A7C64CC4ADB458B74477EA99DF6F5016A52D91CHE111643EMEA1_--

From fred@cisco.com  Tue Mar 12 04:37:26 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3568A21F84CA for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 04:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.486
X-Spam-Level: 
X-Spam-Status: No, score=-110.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ccDLR0qymRo for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 04:37:25 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 438D921F849A for <tsvwg@ietf.org>; Tue, 12 Mar 2013 04:37:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3311; q=dns/txt; s=iport; t=1363088245; x=1364297845; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=PFnAaud9Nm14UvY+je48w63KI9XvjUSW59VfULdhD20=; b=TSaIhC9cOiBwzPW2kVLK0UjMpFVL0v5byxvMT5eZ8XraG1AM4P2ajACr UZY5dZFD9/u+iEPYHoV/T5wMSf4XKaxeVbEiQkh4s/1RSVBPvwa5EYStP gXuguK9/izE2kNkwbYqrfoVIOxRPx6RJ3VtNrE84OajfbF9rJ15kstgCT k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAIwSP1GtJXG//2dsb2JhbABDxGGBShZtB4IqAQQ6UQEqFEInBBuIC55okRWQDBeNQ4EZgxdhA6dKgwqCKA
X-IronPort-AV: E=Sophos;i="4.84,830,1355097600"; d="scan'208";a="183493173"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-9.cisco.com with ESMTP; 12 Mar 2013 11:37:24 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2CBbOeZ002892 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Tue, 12 Mar 2013 11:37:24 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.02.0318.004; Tue, 12 Mar 2013 06:37:24 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Thoughts on AQM
Thread-Index: AQHOHxX3G8oJZ19JKUOZfInmP/1Ydg==
Date: Tue, 12 Mar 2013 11:37:24 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7CBA3B@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.249.208]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4B8690C92981374E9AA83F30DB8899EE@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [tsvwg] Thoughts on AQM
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 11:37:26 -0000

As it turns out, I'm not going to be able to attend the tsvwg meeting, and =
specifically the AQM discussion, Thursday. For some reason I hd it in my he=
ad that it would be this morning, and was looking forward to it. Thursday, =
it conflicts with isis, and I will be presenting in isis.

To that end, let me express the considerations I hold with regard to AQM, R=
ED, CoDel, and other alternatives. Please think of this as me standing at t=
he mike and babbling...

Fred Baker, Random Router Vendor

In my opinion, AQM technologies and the recommendation of RFC 2309 are impo=
rtant to the Internet. As Jim Gettys has commented in the BufferBloat discu=
ssion and documents from RFCs 896 and 970 through SIGCOMM and INFOCOMM in t=
he 1980's and 1990's have discussed, it is in the interest of all applicati=
ons to manage their rate of flow to a dull roar, for for their own benefit =
and for others they compete with. CUBIC and NewReno, in their zeal to achie=
ve maximum bandwidth, drive their traffic outstanding (effective window) to=
 what Dr Jain calls the "cliff", resulting in them frequently having to rec=
over from wasting time and bandwidth. Tools like ECN have not yet been work=
ed out for effective service, but I continue to believe that it should be p=
ossible with experimentation, which is being done in some data center envir=
onments. AQM, whether implemented using signaling or loss, allows the netwo=
rk to communicate to the host about congestion before a catastrophic event =
happens, maximizing good put while and minimizing the impact of one flow on=
 itself and those around it. This is good and should be supported.

RFC 2309 recommends AQM deployment, but doesn't require a specific algorith=
m. That is good, because the prototypical algorithm of the day (RED) is dif=
ficult to use. Van and Kathy have suggested CoDel, Rong Pan and I are inves=
tigating another algorithm called PIE, and there has been ample research on=
 other algorithms. In my opinion, recommendations of specific algorithms ar=
e wisely kept off the table; they make future innovation difficult.

What I think may be of value - and would be willing to contribute to in tsv=
wg - is a set of recommendations regarding the technical use of AQM and con=
gestion control. That document might recommend, for example, that=20

a) Operational deployments SHOULD use AQM procedures.

b) Deployed AQM SHOULD use ECN as well as loss, and set thresholds to mark =
traffic earlier than it is lost. In this way, congestion control can be ach=
ieved in the general case without loss, and loss remains the backup when ne=
eded.

c) AQM algorithms deployed SHOULD not require operational (manual) tuning.

d) AQM algorithms deployed SHOULD be effective on all common Internet traff=
ic, including traffic that uses TCP, SCTP, UDP, and DCCP as transports.

e) TCP congestion control algorithms SHOULD maximize their use of available=
 bandwidth without incurring loss or undue delay when possible. In other wo=
rds, in Jain's language, the TCP/SCTP effective window wants to be greater =
than or equal to the knee, but less than the cliff.=20

There may also be other recommendations, but these address most of the issu=
es I see.

Thanks. I'm sitting down now.=

From carlberg@g11.org.uk  Tue Mar 12 04:46:48 2013
Return-Path: <carlberg@g11.org.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4343E21F8712 for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 04:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.518
X-Spam-Level: 
X-Spam-Status: No, score=-1.518 tagged_above=-999 required=5 tests=[AWL=-1.005, BAYES_20=-0.74, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UcyMQw5ypK+f for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 04:46:47 -0700 (PDT)
Received: from portland.eukhosting.net (portland.eukhosting.net [92.48.97.5]) by ietfa.amsl.com (Postfix) with ESMTP id 965AA21F870E for <tsvwg@ietf.org>; Tue, 12 Mar 2013 04:46:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=g11.org.uk; s=default;  h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=TmTIwcmAlODHSEuGb/gwK4qsxcvEuyJUMEnmMdeCvyo=;  b=VnkXeF6oPZ0XJzFlr2N61PwaWjaoA/bRAuhCEKwN59gLPdulO4JfuZGpP1lXe+w1V3+yMNogkyZSJwaDI8bYpKVG6FdpOPtPLlISZuKZeTJWu4Uy5HRfvO9fcIdf62YQ;
Received: from c-98-218-170-72.hsd1.va.comcast.net ([98.218.170.72]:34152 helo=[10.0.1.20]) by portland.eukhosting.net with esmtps (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <carlberg@g11.org.uk>) id 1UFNfI-000Jao-N9; Tue, 12 Mar 2013 11:46:44 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: ken carlberg <carlberg@g11.org.uk>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7CBA3B@xmb-rcd-x09.cisco.com>
Date: Tue, 12 Mar 2013 07:46:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4F1AAE7-D928-4C58-AD18-E641F82F2A30@g11.org.uk>
References: <8C48B86A895913448548E6D15DA7553B7CBA3B@xmb-rcd-x09.cisco.com>
To: Fred Baker (fred) <fred@cisco.com>
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - portland.eukhosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - g11.org.uk
X-Get-Message-Sender-Via: portland.eukhosting.net: acl_c_relayhosts_text_entry: carlberg@g11.org.uk|g11.org.uk
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] Thoughts on AQM
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 11:46:48 -0000

Fred,

> c) AQM algorithms deployed SHOULD not require operational (manual) =
tuning.

on the particular topic, would you see the eventual need for something =
like next generation COP (rfc-2478) to help manage the AQM algorithm(s)?

-ken


From wes@mti-systems.com  Tue Mar 12 05:08:39 2013
Return-Path: <wes@mti-systems.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 585AC21F85EE for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 05:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N7iyY8QFSS4M for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 05:08:38 -0700 (PDT)
Received: from atl4mhob05.myregisteredsite.com (atl4mhob05.myregisteredsite.com [209.17.115.43]) by ietfa.amsl.com (Postfix) with ESMTP id CD63621F859C for <tsvwg@ietf.org>; Tue, 12 Mar 2013 05:08:38 -0700 (PDT)
Received: from mailpod.hostingplatform.com (mail.networksolutionsemail.com [205.178.146.50]) by atl4mhob05.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r2CC8bMB022317 for <tsvwg@ietf.org>; Tue, 12 Mar 2013 08:08:37 -0400
Received: (qmail 2910 invoked by uid 0); 12 Mar 2013 12:08:37 -0000
Received: from unknown (HELO ?10.11.0.54?) (wes@mti-systems.com@46.165.208.203) by 0 with ESMTPA; 12 Mar 2013 12:08:37 -0000
Message-ID: <513F1AB6.7000908@mti-systems.com>
Date: Tue, 12 Mar 2013 08:08:22 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
References: <8C48B86A895913448548E6D15DA7553B7CBA3B@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7CBA3B@xmb-rcd-x09.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] Thoughts on AQM
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 12:08:39 -0000

On 3/12/2013 7:37 AM, Fred Baker (fred) wrote:
> As it turns out, I'm not going to be able to attend the tsvwg
> meeting, and specifically the AQM discussion, Thursday. For some
> reason I hd it in my head that it would be this morning, and was
> looking forward to it. Thursday, it conflicts with isis, and I will
> be presenting in isis.


The AQM discussion will be in *TSVAREA*, not TSVWG.  I will send a
reply with a couple questions on the tsv-area@ietf.org list.

That said, this was a very welcome email, and very clear and useful
to the ADs; thanks!


-- 
Wes Eddy
MTI Systems

From fred@cisco.com  Tue Mar 12 10:35:45 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2059821F85B1 for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 10:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.467
X-Spam-Level: 
X-Spam-Status: No, score=-110.467 tagged_above=-999 required=5 tests=[AWL=-0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y5SDC6lYGS-I for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 10:35:44 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 52BF121F84FF for <tsvwg@ietf.org>; Tue, 12 Mar 2013 10:35:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1677; q=dns/txt; s=iport; t=1363109744; x=1364319344; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=DSi4EjAW8ZqLPkOPYD/6GWUfGNdWxRcZiHapdkKRedc=; b=TSGNnBgzoYXv8xDoyyWIPQUBiBTWePNWco25Gr4uSwGm7yXU5PetBLgd q4DIyA1j0NhgK5o86oL6v/WZj6pLHm7VfllJURLKDr8iwVSn0mnus0u6C jiqnDr+4iuEumd6P5rr6EL5mhh7IYkMYTAkZZwhBGT3weMHC7VGNzlxzB 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFACZlP1GtJV2c/2dsb2JhbABDxGqBSxZ0gikBAQEDATo/BQsCAQgiFBAyJQIEDgUIAYgFBgyxUI9oF45aAjEHgl9hA6dMgwqCKA
X-IronPort-AV: E=Sophos;i="4.84,832,1355097600"; d="scan'208";a="186686856"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-4.cisco.com with ESMTP; 12 Mar 2013 17:35:43 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r2CHZhRd028512 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 Mar 2013 17:35:43 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Tue, 12 Mar 2013 12:35:43 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: ken carlberg <carlberg@g11.org.uk>
Thread-Topic: [tsvwg] Thoughts on AQM
Thread-Index: AQHOH0gF8Y/u4bR6MUuCqMbSAwptVQ==
Date: Tue, 12 Mar 2013 17:35:43 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7CDCAF@xmb-rcd-x09.cisco.com>
References: <8C48B86A895913448548E6D15DA7553B7CBA3B@xmb-rcd-x09.cisco.com> <B4F1AAE7-D928-4C58-AD18-E641F82F2A30@g11.org.uk>
In-Reply-To: <B4F1AAE7-D928-4C58-AD18-E641F82F2A30@g11.org.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.216.210]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2E29297FE550A84BBBDED440E4CE5842@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] Thoughts on AQM
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 17:35:45 -0000

On Mar 12, 2013, at 7:46 AM, ken carlberg <carlberg@g11.org.uk> wrote:

> Fred,
>=20
>> c) AQM algorithms deployed SHOULD not require operational (manual) tunin=
g.
>=20
> on the particular topic, would you see the eventual need for something li=
ke next generation COP (rfc-2478) to help manage the AQM algorithm(s)?
>=20
> -ken

Are you thinking about 2478 or 2748?

http://www.ietf.org/rfc/rfc2478.txt
2478 The Simple and Protected GSS-API Negotiation Mechanism. E. Baize,
     D. Pinkas. December 1998. (Format: TXT=3D35581 bytes) (Obsoleted by
     RFC4178) (Status: PROPOSED STANDARD)

http://www.ietf.org/rfc/rfc4178.txt
4178 The Simple and Protected Generic Security Service Application
     Program Interface (GSS-API) Negotiation Mechanism. L. Zhu, P. Leach,
     K. Jaganathan, W. Ingersoll. October 2005. (Format: TXT=3D46485 bytes)
     (Obsoletes RFC2478) (Status: PROPOSED STANDARD)


https://tools.ietf.org/html/rfc2748
2748 The COPS (Common Open Policy Service) Protocol. D. Durham, Ed.,
     J. Boyle, R. Cohen, S. Herzog, R. Rajan, A. Sastry. January 2000.
     (Format: TXT=3D90906 bytes) (Updated by RFC4261) (Status: PROPOSED
     STANDARD)

https://tools.ietf.org/html/rfc4261
4261 Common Open Policy Service (COPS) Over Transport Layer Security
     (TLS). J. Walker, A. Kulkarni, Ed.. December 2005. (Format: TXT=3D2866=
2
     bytes) (Updates RFC2748) (Status: PROPOSED STANDARD)


IMHO, the point of it being self-tuning is to not require configuration int=
ervention. That said, trust me, if there is a way to make a simple thing co=
mplex, I'm sure we can find it, and then figure out how to manage it.=

From shares@ndzh.com  Tue Mar 12 10:39:30 2013
Return-Path: <shares@ndzh.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97A1A11E80A3 for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 10:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.956
X-Spam-Level: *
X-Spam-Status: No, score=1.956 tagged_above=-999 required=5 tests=[AWL=1.450,  BAYES_00=-2.599, DOS_OUTLOOK_TO_MX=1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7q5ZPVs4LjdH for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2013 10:39:28 -0700 (PDT)
Received: from hickoryhill-consulting.com (unknown [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 6F09C21F869C for <tsvwg@ietf.org>; Tue, 12 Mar 2013 10:39:28 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=130.129.16.73; 
From: "Susan Hares" <shares@ndzh.com>
To: <Ruediger.Geib@telekom.de>
References: <004e01ce1e9d$694a7870$3bdf6950$@ndzh.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A52D91C@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A52D91C@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Date: Tue, 12 Mar 2013 13:39:26 -0400
Message-ID: <004301ce1f48$8af0db30$a0d29190$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0044_01CE1F27.03E1FA50"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQGdbiik2CEHlLt/GMjUWblbvQvLUAE/HECkmPm5iBA=
X-Authenticated-User: skh@ndzh.com 
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP need
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 17:39:30 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0044_01CE1F27.03E1FA50
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Ruediger:

=20

I given the details to Ruediger Volk and he promises to return and chat =
with
you on the presentation.

=20

The tsvwg =96 group did not differentiate between the two =96 only =
suggested a
BGP peering.  You answered both question.=20

=20

Sue=20

=20

From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]=20
Sent: Tuesday, March 12, 2013 5:51 AM
To: shares@ndzh.com
Cc: tsvwg@ietf.org
Subject: RE: [tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does =
BGP
need

=20

Sue,

=20

I didn't ask any of my internal BGP expert before sending: is eBGP
terminated by an AS border router? If that's a yes in all cases, Cs6 for
eBGP isn't an issue. If eBGP traffic is transmitted within an AS, then
mapping of classes is an issue. I'm not a routing expert.

=20

Regards,

=20

R=FCdiger

=20

  _____ =20

From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf =
Of
Susan Hares
Sent: Monday, March 11, 2013 10:14 PM
To: tsvwg@ietf.org
Subject: [tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP =
need

=20

To follow-up on the proposal in the RFC5127 changes proposed in the =
draft

draft-geib-tswf-diffserv-intercon-02.txt, I ask do the carriers need the
RFC5127 network control (CS6 DSCP) to run BGP?=20

=20

Sue Hares

=20


------=_NextPart_000_0044_01CE1F27.03E1FA50
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Ruediger:<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I given the details to =
Ruediger Volk and he promises to return and chat with you on the =
presentation.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>The tsvwg &#8211; group =
did not differentiate between the two &#8211; only suggested a BGP =
peering.=A0 You answered both question. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Sue =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de] =
<br><b>Sent:</b> Tuesday, March 12, 2013 5:51 AM<br><b>To:</b> =
shares@ndzh.com<br><b>Cc:</b> tsvwg@ietf.org<br><b>Subject:</b> RE: =
[tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP =
need<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Su=
e,</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>I =
didn't ask any of my&nbsp;internal BGP expert before sending: is eBGP =
terminated by an AS border router? If that's a yes in all cases, Cs6 for =
eBGP isn't an issue. If eBGP traffic is transmitted within an AS, then =
mapping of classes is an issue. I'm not a routing expert.</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Re=
gards,</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>R=FC=
diger</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><span lang=3DDE =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><hr =
size=3D2 width=3D"100%" align=3Dcenter></span></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><b><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a =
href=3D"mailto:tsvwg-bounces@ietf.org">tsvwg-bounces@ietf.org</a> [<a =
href=3D"mailto:tsvwg-bounces@ietf.org">mailto:tsvwg-bounces@ietf.org</a>]=
 <b>On Behalf Of </b>Susan Hares<br><b>Sent:</b> Monday, March 11, 2013 =
10:14 PM<br><b>To:</b> <a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a><br><b>Subject:</b> =
[tsvwg] draft-geib-tsvwg-diffserv-intercon-02.txt - does BGP =
need</span><span lang=3DDE style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'><o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>To follow-up =
on the proposal in the RFC5127 changes proposed in the =
draft<o:p></o:p></p><p =
class=3DMsoNormal>draft-geib-tswf-diffserv-intercon-02.txt, I ask do the =
carriers need the RFC5127 network control (CS6 DSCP) to run BGP? =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Sue Hares<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0044_01CE1F27.03E1FA50--


From carlberg@g11.org.uk  Wed Mar 13 05:56:19 2013
Return-Path: <carlberg@g11.org.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3C4821F8CD8 for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 05:56:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level: 
X-Spam-Status: No, score=-2.196 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tdVW97ybrS5S for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 05:56:19 -0700 (PDT)
Received: from portland.eukhosting.net (portland.eukhosting.net [92.48.97.5]) by ietfa.amsl.com (Postfix) with ESMTP id AD51821F8CD3 for <tsvwg@ietf.org>; Wed, 13 Mar 2013 05:56:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=g11.org.uk; s=default;  h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=jltSWbA2CN3RdPubOPo2el9GNfF36dQPo2tNJ6LStP0=;  b=vGAFh+m26fUsS6rYIz9O/QkB0+6CP55o39TXN3JN5WZiuCoi3ecY3l0c9Q81duD8tHzRj73xKE/rbrKYJKGyVX8nstlZFoFF2MK26pPAoTXpPygt9oxnrHzv5qUhXcv8;
Received: from c-98-218-170-72.hsd1.va.comcast.net ([98.218.170.72]:47780 helo=[10.0.1.20]) by portland.eukhosting.net with esmtps (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <carlberg@g11.org.uk>) id 1UFlE6-000FYY-EP; Wed, 13 Mar 2013 12:56:14 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: ken carlberg <carlberg@g11.org.uk>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7CDCAF@xmb-rcd-x09.cisco.com>
Date: Wed, 13 Mar 2013 08:56:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F3F74CA-9501-432C-8B44-04A91357026F@g11.org.uk>
References: <8C48B86A895913448548E6D15DA7553B7CBA3B@xmb-rcd-x09.cisco.com> <B4F1AAE7-D928-4C58-AD18-E641F82F2A30@g11.org.uk> <8C48B86A895913448548E6D15DA7553B7CDCAF@xmb-rcd-x09.cisco.com>
To: Fred Baker (fred) <fred@cisco.com>
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - portland.eukhosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - g11.org.uk
X-Get-Message-Sender-Via: portland.eukhosting.net: acl_c_relayhosts_text_entry: carlberg@g11.org.uk|g11.org.uk
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] Thoughts on AQM
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 12:56:19 -0000

> Are you thinking about 2478 or 2748?
>=20
<snip>
> https://tools.ietf.org/html/rfc2748
> 2748 The COPS (Common Open Policy Service) Protocol. D. Durham, Ed.,
>     J. Boyle, R. Cohen, S. Herzog, R. Rajan, A. Sastry. January 2000.
>     (Format: TXT=3D90906 bytes) (Updated by RFC4261) (Status: PROPOSED
>     STANDARD)
<snip>
>=20
> IMHO, the point of it being self-tuning is to not require =
configuration intervention. That said, trust me, if there is a way to =
make a simple thing complex, I'm sure we can find it, and then figure =
out how to manage it.

mea culpa.  i meant the latter, 2748.  I was thinking about the means of =
maintaining a uniformity of characteristics (eg, algorithms) for the AQM =
deployments within the administrative domain (eg, large and =
topologically disperse enterprise networks, or transits).  This, as =
opposed to AQM at a single ingress/egress point.

cheers,

-ken=

From fred@cisco.com  Wed Mar 13 06:03:37 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A2DE21F89B2 for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 06:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.457
X-Spam-Level: 
X-Spam-Status: No, score=-110.457 tagged_above=-999 required=5 tests=[AWL=-0.085, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yYiYNxeR+9ZL for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 06:03:36 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 6375221F8C10 for <tsvwg@ietf.org>; Wed, 13 Mar 2013 06:03:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=910; q=dns/txt; s=iport; t=1363179816; x=1364389416; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=YVILqoK2EKKQ94mF3y4HU09K3cdxeLT0Ym23T72wX20=; b=GPvD8YwBrCJximudMTnD1DoocY6rB5AXW1/UJ1LvxQoNvRv7CKD8P2vY EhWWgTFCZcNVg50w8Gaanw6y7pBLestRP+cYv4yeKwTXeGwx6SW/WlfQ5 oOWKIAa0/yrEFop7QFBmi6Uoo8lJAN2xaRu+zz18lTBwiGQfbr/GdNeKM k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAAJ4QFGtJV2Y/2dsb2JhbABDh1m9IoFWFnSCKQEBAQMBOj8FCwIBCCIUEDIlAgQOBQiIBgbCCBeOWgIxB4JfYQOnTIMKgig
X-IronPort-AV: E=Sophos;i="4.84,836,1355097600"; d="scan'208";a="183981592"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-9.cisco.com with ESMTP; 13 Mar 2013 13:03:36 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r2DD3aWq032660 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Mar 2013 13:03:36 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Wed, 13 Mar 2013 08:03:35 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: ken carlberg <carlberg@g11.org.uk>
Thread-Topic: [tsvwg] Thoughts on AQM
Thread-Index: AQHOH+srpgZSnl4VeEe2kH8X+bXbGg==
Date: Wed, 13 Mar 2013 13:03:35 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7CFE80@xmb-rcd-x09.cisco.com>
References: <8C48B86A895913448548E6D15DA7553B7CBA3B@xmb-rcd-x09.cisco.com> <B4F1AAE7-D928-4C58-AD18-E641F82F2A30@g11.org.uk> <8C48B86A895913448548E6D15DA7553B7CDCAF@xmb-rcd-x09.cisco.com> <5F3F74CA-9501-432C-8B44-04A91357026F@g11.org.uk>
In-Reply-To: <5F3F74CA-9501-432C-8B44-04A91357026F@g11.org.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.216.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4124C519EE96E84B8EAA6B87B27857D9@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] Thoughts on AQM
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 13:03:37 -0000

On Mar 13, 2013, at 8:56 AM, ken carlberg <carlberg@g11.org.uk>
 wrote:

> mea culpa.  i meant the latter, 2748.  I was thinking about the means of =
maintaining a uniformity of characteristics (eg, algorithms) for the AQM de=
ployments within the administrative domain (eg, large and topologically dis=
perse enterprise networks, or transits).  This, as opposed to AQM at a sing=
le ingress/egress point.

AQM is a class of procedures for managing queue depth. Since every queue in=
 the network requires a drop algorithm (no queue is infinitely deep, even i=
f it appears that way), the question isn't whether such algorithms are nece=
ssary in a given place, it's what kind of algorithm to recommend. I think t=
his would appear in every queue in the network, even if the queue doesn't a=
s a rule become deep; such a queue would simply not normally find itself in=
voking the algorithm.=

From lear@cisco.com  Wed Mar 13 07:23:47 2013
Return-Path: <lear@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF6B21F8E10 for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 07:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.475
X-Spam-Level: 
X-Spam-Status: No, score=-110.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pSwIaQkwPlvx for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 07:23:46 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF1E21F8E0E for <tsvwg@ietf.org>; Wed, 13 Mar 2013 07:23:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=337; q=dns/txt; s=iport; t=1363184626; x=1364394226; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=XImxB55/BgQD9Zbu3Gydz4CjK1QX6uGfw0oZI7AW69s=; b=IEi3Yh9Id5kg+y9Sn2q9HcZfknI5h5xt+yltVgnF+E5kW09Cdt1SlCoA dkaY3UDNL3H0Pp7UZE0fKXd77NtB+uFOuXdltQQ/ru8iILV5S7qOgbLzB WCg8Dz07kgCOF5r7qtsbovmO15QR2v6gV2zQHtUd6MG6jNXlXsB+oSRIT E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AokJALeLQFGtJV2Z/2dsb2JhbABDh1lHvFIEBIFXFnSCU1U2AgUWCwILAwIBAgFLDQgBAQWICwyhBo5VkluBI5AegRMDllaQdoMmIA
X-IronPort-AV: E=Sophos;i="4.84,837,1355097600"; d="scan'208";a="186981442"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 13 Mar 2013 14:23:46 +0000
Received: from rtp-vpn6-1347.cisco.com (rtp-vpn6-1347.cisco.com [10.82.253.72]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2DENjBE011960 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 13 Mar 2013 14:23:45 GMT
Message-ID: <51408BF4.7090304@cisco.com>
Date: Wed, 13 Mar 2013 10:23:48 -0400
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 14:23:47 -0000

I don't have an answer to that question, but Mark Allman from ICIR did
attempt to characterize buffer bloat on the Internet through an
empirical study that appeared in the January edition of CCR.  You can
find a reference to that paper at the following URL:

http://www.sigcomm.org/ccr/papers/2013/January/2427036.2427041

Eliot

From fred@cisco.com  Wed Mar 13 08:28:42 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8919121F8ECC for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 08:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.561
X-Spam-Level: 
X-Spam-Status: No, score=-110.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGeHBGAqfmCr for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 08:28:42 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 84BB721F8ED4 for <tsvwg@ietf.org>; Wed, 13 Mar 2013 08:28:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=905; q=dns/txt; s=iport; t=1363188521; x=1364398121; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=NxQhgwgCKd05t98OIAmQcJVMxs9JD2etVV1tmpL/oJw=; b=J4i1gZjkMMEvRj6Q1adXC3GswK4EU04MDiX59tqBiylHYh9I3alGqvcw tAlc45UuxlU2ZtXXnbfBN1SJ0n85qS955U9J0mLwvAwF8hllSCF/vTmHj CuhoogFFjifDLp7T5bg6bF0lC4cWH/yBs5A4y7s1SWSwurbcFU7CAfl1f E=;
X-IronPort-AV: E=Sophos;i="4.84,837,1355097600"; d="scan'208";a="187039602"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-8.cisco.com with ESMTP; 13 Mar 2013 15:28:16 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r2DFSGpr004281 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Mar 2013 15:28:16 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Wed, 13 Mar 2013 10:28:16 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Eliot Lear <lear@cisco.com>
Thread-Topic: [tsvwg] how much of a problem is buffer bloat today?
Thread-Index: AQHOH/9hgPTgVp5AE0uL3C0CbY0Mfw==
Date: Wed, 13 Mar 2013 15:28:15 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7D020F@xmb-rcd-x09.cisco.com>
References: <51408BF4.7090304@cisco.com>
In-Reply-To: <51408BF4.7090304@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.238.171]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <DE8A31BE0FEAAD4EAF833D990F6730D9@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 15:28:42 -0000

On Mar 13, 2013, at 10:23 AM, Eliot Lear <lear@cisco.com> wrote:

> I don't have an answer to that question, but Mark Allman from ICIR did
> attempt to characterize buffer bloat on the Internet through an
> empirical study that appeared in the January edition of CCR.  You can
> find a reference to that paper at the following URL:
>=20
> http://www.sigcomm.org/ccr/papers/2013/January/2427036.2427041
>=20
> Eliot

Well, yes, he says that in his gigabit FTTH network he doesn't see megabit-=
scale problems.

We know of data center cases; I can't go into listing customers, but think =
of well-known data center operators and ask them about it. That tends to be=
 about the incast problem and what happens when you ask a whole lot of folk=
s a question and they all answer.=20

We know of broadband cases in DSL, Cable Modem, and so on. Ask yourself why=
 Comcast wrote RFC 6057.=

From gorry@erg.abdn.ac.uk  Wed Mar 13 08:36:42 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23EC121F8DE9 for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 08:36:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zJi4mnwrwQGZ for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 08:36:40 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id D11A221F8DE6 for <tsvwg@ietf.org>; Wed, 13 Mar 2013 08:36:39 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 2FE6D2B44CE; Wed, 13 Mar 2013 15:36:39 +0000 (GMT)
Received: from dhcp-1504.meeting.ietf.org (dhcp-1504.meeting.ietf.org [130.129.21.4]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id A08092B4400 for <tsvwg@ietf.org>; Wed, 13 Mar 2013 15:36:37 +0000 (GMT)
Message-ID: <51409D02.3080301@erg.abdn.ac.uk>
Date: Wed, 13 Mar 2013 11:36:34 -0400
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: tsvwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [tsvwg] SCTP SACK-I detailed comments
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 15:36:42 -0000

I've done a fairly detailed read of the above draft, and have some 
specific comments that I'd like to submit as an individual as we head 
towards WGLC.

Gorry
(as an individual)

---

Abstract
- The abstract will be read by people who do not read any other part of 
the document. I think the current abstract is terse. It doesn't say some 
things which I think it should. Missing is a statement that says this 
defines a new chunk flag, called the I-bit, that can be set by the SCTP 
stack or by an application.

Section 1
   "According to [RFC4960] the receiver of a DATA chunk should use
    delayed SACKs."
- I think it is important to say why this is normally the right thing to 
do - e.g. this remains the normal case.

   "In specific situations the delaying of SACKs results in reduced
    performance of the protocol"
- A separate subsection on examples of usage, would be really useful 
(see note on section 4.1), You could then (forward) refer to this here.

Section 4.1
   "Reasons for setting the I-bit include but are not limited to the
    following:"
- Insert commas around /but not limited/?

I think the set of examples provided in 4.1 are really important to 
publishing the spec. However, the current examples are really terse. 
Although they seem good examples, the motivation for using the I-but is 
not clear.

   "o  The application requests to set the I-bit of the last DATA chunk
       of a user message when providing the user message to the SCTP
       implementation (see Section 6)."
- What is the benefit?

   "o  The sender is in the SHUTDOWN-PENDING state."
- Is this that the immediate SACK can then expedite the shutdown of a 
stream?

   "o  The sending of a DATA chunk fills the congestion or receiver
       window."
- An immediate SACK can then allow the sender to transmit the missing 
chunk that will release the congestion/receiver window to send new data?

- I think this it is confusing that we have two lists, one in the second 
part of the introduction, and one in section 4.1. I'd suggest it may be 
useful to have one subsection in the introduction to do this.

- To me, the important aspect that should have been evident in 4.1 was 
that there are two use-cases, one when the I-bit is set by the stack as 
an internal transport function, and one as an application-triggered 
function via the API in section 6.

Section 4.2
   "On reception of an SCTP packet containing a DATA chunk with the I-bit
    set, the receiver SHOULD NOT delay the sending of the corresponding
    SACK chunk and SHOULD send it back immediately."

- This contains two RFC 2119 requirements. I think the two are the same, 
and suggest it is better to have only one. One way to resolve this would 
be to make the second /SHOULD/ read /should/.

Section 6
- It would perhaps avoid ambiguity to say at the very start that the API 
allows the I-bit to be set for any specific data chunk.

   "or the
    sinfo_flags field of the struct sctp_sndrcvinfo structure, which is
    deprecated."
- I think the "or" is confusing, since the second part is deprecated. 
Could we make this a separate statement, by replacing the "or" by a stop 
and starting a new sentence with /The/.

Section 8 (recently noted)
- Section 4.1 implies this need to discuss cost of processing the I-bit 
when in 4.1 it says: "Please note that it is
    irrelevant to the receiver why the sender has set the I-bit."

[RFC6525]
- This seems like an informative reference?


From lars@netapp.com  Wed Mar 13 09:15:29 2013
Return-Path: <lars@netapp.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A776B21F8C69 for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 09:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.413
X-Spam-Level: 
X-Spam-Status: No, score=-10.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L6rgInnXWaxC for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 09:15:29 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 114D321F8C71 for <tsvwg@ietf.org>; Wed, 13 Mar 2013 09:15:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.84,837,1355126400"; d="scan'208";a="14729516"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 13 Mar 2013 09:15:28 -0700
Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r2DGFSek025923; Wed, 13 Mar 2013 09:15:28 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0342.003; Wed, 13 Mar 2013 09:15:27 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Eliot Lear <lear@cisco.com>
Thread-Topic: [tsvwg] how much of a problem is buffer bloat today?
Thread-Index: AQHOH/Z8CYaPemGXTkuLw08HVgIeqpikQV0A
Date: Wed, 13 Mar 2013 16:15:26 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F7B2E12@SACEXCMBX01-PRD.hq.netapp.com>
References: <51408BF4.7090304@cisco.com>
In-Reply-To: <51408BF4.7090304@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.117]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <455C74480B9EFC42B9E1B6808CCA9E1A@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 16:15:29 -0000

Hi,

I recently did some very preliminary measurements using some lab equipment =
and Rick Jones' bloat.sh script. In their default configuration and with th=
e latest available firmware, here is what I saw:

Cisco Catalyst 2960: at 100Mb/s, 80ms under load
Cisco Catalyst 3750: at 1Gb/s, 8ms under load
Cisco Nexus 5010 & 5548: at 1Gb/s, 8ms under load

(I haven't measured the Nexus switches at 10Gb/s, because the single netper=
f instance used by Rick Jones' bloat.sh script can only pump out 5G/s on on=
e core. Once Toke's netperf-wrapper works on FreeBSD, I'll re-test using th=
at.)

Lars=

From lars@netapp.com  Wed Mar 13 09:34:18 2013
Return-Path: <lars@netapp.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7A4721F8DA8 for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 09:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.417
X-Spam-Level: 
X-Spam-Status: No, score=-10.417 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SmnegW+Nf-ZV for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 09:34:18 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 5A70221F8CE8 for <tsvwg@ietf.org>; Wed, 13 Mar 2013 09:34:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.84,838,1355126400"; d="scan'208";a="30489105"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 13 Mar 2013 09:34:18 -0700
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r2DGYISN019190; Wed, 13 Mar 2013 09:34:18 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0342.003; Wed, 13 Mar 2013 09:34:18 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Eliot Lear <lear@cisco.com>
Thread-Topic: [tsvwg] how much of a problem is buffer bloat today?
Thread-Index: AQHOH/Z8CYaPemGXTkuLw08HVgIeqpikQV0AgAAFQAA=
Date: Wed, 13 Mar 2013 16:34:16 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F7B3141@SACEXCMBX01-PRD.hq.netapp.com>
References: <51408BF4.7090304@cisco.com> <D4D47BCFFE5A004F95D707546AC0D7E91F7B2E12@SACEXCMBX01-PRD.hq.netapp.com>
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F7B2E12@SACEXCMBX01-PRD.hq.netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.117]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BE528011F4C8D843ADF0A932580AF53E@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 16:34:19 -0000

(And let me be clear that I'm not riffing on Cisco here. We like their gear=
, and that's why I had it lying around in the lab.)

On Mar 13, 2013, at 12:15, "Eggert, Lars" <lars@netapp.com> wrote:

> Hi,
>=20
> I recently did some very preliminary measurements using some lab equipmen=
t and Rick Jones' bloat.sh script. In their default configuration and with =
the latest available firmware, here is what I saw:
>=20
> Cisco Catalyst 2960: at 100Mb/s, 80ms under load
> Cisco Catalyst 3750: at 1Gb/s, 8ms under load
> Cisco Nexus 5010 & 5548: at 1Gb/s, 8ms under load
>=20
> (I haven't measured the Nexus switches at 10Gb/s, because the single netp=
erf instance used by Rick Jones' bloat.sh script can only pump out 5G/s on =
one core. Once Toke's netperf-wrapper works on FreeBSD, I'll re-test using =
that.)
>=20
> Lars


From g.white@CableLabs.com  Wed Mar 13 09:40:03 2013
Return-Path: <g.white@CableLabs.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA4F921F8CDB for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 09:40:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JA8YxTdCU-0G for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 09:40:02 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id A0CC421F8CAF for <tsvwg@ietf.org>; Wed, 13 Mar 2013 09:40:02 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id r2DGe0fp031817; Wed, 13 Mar 2013 10:40:00 -0600
Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Wed, 13 Mar 2013 10:40:00 -0600 (MDT)
X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com)
Received: from EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee]) by EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee%11]) with mapi id 14.02.0328.009; Wed, 13 Mar 2013 10:39:59 -0600
From: Greg White <g.white@CableLabs.com>
To: "Fred Baker (fred)" <fred@cisco.com>, Eliot Lear <lear@cisco.com>
Thread-Topic: [tsvwg] how much of a problem is buffer bloat today?
Thread-Index: AQHOH/Zy6Y2ujr6xyky0EcKlL8uw15ikI2qA///Q/gA=
Date: Wed, 13 Mar 2013 16:39:58 +0000
Message-ID: <C38E406F654CD249AB7D30B93B0207F517F54D92@EXCHANGE.cablelabs.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7D020F@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.1.130117
x-originating-ip: [10.5.0.27]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5312CDDFFB67AB48A83C102AF73A1A92@cablelabs.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 16:40:04 -0000

I would also suggest that in the conclusion of the paper:
=09
	=09
	=09
=09
=09
	=09
		=09
			=09
				=09
					=09

							However, the magnitude of the problem as manifest in live traffic
is modest. In particular, we find bloat bounded at (i) 100 msec for more
than half the samples and (ii) 250 msec for at least 94% of the samples.

					=09
				=09
			=09

Some may consider 100ms a big number.
		=09
	=09
=09


-Greg


On 3/13/13 11:28 AM, "Fred Baker (fred)" <fred@cisco.com> wrote:

>
>On Mar 13, 2013, at 10:23 AM, Eliot Lear <lear@cisco.com> wrote:
>
>> I don't have an answer to that question, but Mark Allman from ICIR did
>> attempt to characterize buffer bloat on the Internet through an
>> empirical study that appeared in the January edition of CCR.  You can
>> find a reference to that paper at the following URL:
>>=20
>> http://www.sigcomm.org/ccr/papers/2013/January/2427036.2427041
>>=20
>> Eliot
>
>Well, yes, he says that in his gigabit FTTH network he doesn't see
>megabit-scale problems.
>
>We know of data center cases; I can't go into listing customers, but
>think of well-known data center operators and ask them about it. That
>tends to be about the incast problem and what happens when you ask a
>whole lot of folks a question and they all answer.
>
>We know of broadband cases in DSL, Cable Modem, and so on. Ask yourself
>why Comcast wrote RFC 6057.


From fred@cisco.com  Wed Mar 13 09:50:53 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A429B21F8D19; Wed, 13 Mar 2013 09:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.317
X-Spam-Level: 
X-Spam-Status: No, score=-110.317 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f-1hq+vE2Skb; Wed, 13 Mar 2013 09:50:52 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id B2E8921F84B0; Wed, 13 Mar 2013 09:50:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1216; q=dns/txt; s=iport; t=1363193452; x=1364403052; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=5sTCTQA8ypALR6Z4f3lbKKvHpfMtlmar0hJjGd+yLuM=; b=bHdRJWLc7Vo6xbsRMkM1LnvwnhGpoib+DemDXlUfgKecDkQedNif+vM2 bVryacWONBE4a+HD06mXnCI92XfQBD5UYnu+n6ry0O4NHWRXdULbhQ4AH CPWYxGNNdX4Lci55YXcPFV8vtoy1es5F34QLMRMlFa6nYV7r8exUVzfxR 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFADysQFGtJXG9/2dsb2JhbABDxH+BWRZ0gioBAQEDATo9AhACAQgiFBAyJQIEDgUIAQuHegYMwkcXjUyBDgIxB4JfYQOXdY9XgwqBczU
X-IronPort-AV: E=Sophos;i="4.84,838,1355097600"; d="scan'208";a="187079100"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-6.cisco.com with ESMTP; 13 Mar 2013 16:50:52 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2DGoqqP015366 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Mar 2013 16:50:52 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Wed, 13 Mar 2013 11:50:52 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: tsvwg <tsvwg@ietf.org>
Thread-Topic: New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt
Thread-Index: AQHOIAqa1tJ18EAwSkCm0kPJ4goPbpikKZCA
Date: Wed, 13 Mar 2013 16:50:51 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com>
References: <20130313164833.27324.89314.idtracker@ietfa.amsl.com>
In-Reply-To: <20130313164833.27324.89314.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.236.166]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <023025B6AC7FCE40A4FB902A9216A212@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>
Subject: Re: [tsvwg] New Version Notification for	draft-baker-tsvwg-aqm-recommendation-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 16:50:53 -0000

Folks. I posted the email I sent yesterday as a draft, for discussion. I we=
lcome comments, and if substantive comments are made, suggested text.


On Mar 13, 2013, at 12:48 PM, <internet-drafts@ietf.org>
 wrote:

>=20
> A new version of I-D, draft-baker-tsvwg-aqm-recommendation-00.txt
> has been successfully submitted by Fred Baker and posted to the
> IETF repository.
>=20
> Filename:	 draft-baker-tsvwg-aqm-recommendation
> Revision:	 00
> Title:		 IETF Recommendations Regarding Active Queue Management
> Creation date:	 2013-03-13
> Group:		 Individual Submission
> Number of pages: 7
> URL:             http://www.ietf.org/internet-drafts/draft-baker-tsvwg-aq=
m-recommendation-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-baker-tsvwg-aqm-re=
commendation
> Htmlized:        http://tools.ietf.org/html/draft-baker-tsvwg-aqm-recomme=
ndation-00
>=20
>=20
> Abstract:
>   Fifteen years after the IAB issued its recommendations regarding
>   congestion control in RFC 2309, a major issue in the community is the
>   issue that RFC addresses: Buffer bloat.  It may be time to update the
>   recommendation.
>=20
>=20
>=20
>=20
> The IETF Secretariat
>=20


From swmike@swm.pp.se  Wed Mar 13 10:25:25 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A883F21F8510; Wed, 13 Mar 2013 10:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.409
X-Spam-Level: 
X-Spam-Status: No, score=-2.409 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qhG-bsqh15g8; Wed, 13 Mar 2013 10:25:25 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id E49FD21F8DDE; Wed, 13 Mar 2013 10:25:24 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 8D5039C; Wed, 13 Mar 2013 18:25:22 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 8392B9A; Wed, 13 Mar 2013 18:25:22 +0100 (CET)
Date: Wed, 13 Mar 2013 18:25:22 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Fred Baker (fred)" <fred@cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com>
Message-ID: <alpine.DEB.2.00.1303131810180.28820@uplift.swm.pp.se>
References: <20130313164833.27324.89314.idtracker@ietfa.amsl.com> <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 17:25:25 -0000

On Wed, 13 Mar 2013, Fred Baker (fred) wrote:

> Folks. I posted the email I sent yesterday as a draft, for discussion. I 
> welcome comments, and if substantive comments are made, suggested text.

I voiced my opinion on the tsv-area meeting via jabber that AQM especially 
on low/medium bw links (up to 10-20 megabits/s) is needed and bufferbloat 
is a serious problem. As an employee of an operator, I would like to see 
documents in the line of RFC6204, ie basic requirements, for (in this 
case) AQM that I can use in procurement documents. Preferrably these would 
be implemented by kernel vendors (linux kernel and others) so the actual 
device vendor only needs to turn it on and perhaps set a few parameters 
(like communicate the link speed to the queue handler).

Coming back to the document at hand, reading 
draft-baker-tsvwg-aqm-recommendation-00.txt, I notice a few things. Am I 
misinterpreting text such as:

"Hence, network communication to the host regarding the moderation of
    its traffic flow SHOULD include both ECN and loss, with ECN being
    triggered earlier than loss."

... that it recommendeds that ECN traffic will be marked before non-ECN 
traffic is dropped? I believe desired behaviour is that ECN traffic is 
marked and non-ECN traffic is dropped at the exact same queue depth (or 
whatever mechanism causes packets to be dropped/marked).

Also, the documents seem to handle both host stack implementations and 
device queue management. Am I correct? Perhaps it would be preferable to 
have one document handling queueing (including the queue on the host 
towards its network interface (wifi/fixed/cellular etc), and another 
document talking about "TCP congestion control mechanisms"? Or this the 
document at hand trying to be an umbrella document for other documents?

Anyhow, I feel this (AQM/congestion) area of discussion is extremely 
important and it solves a real life problem that impacts a lot of people 
on the Internet as it works today. Personally I have routers with quite 
advanced AQM on my home connection (100/100 megabit/s) because I feel that 
FIFO even with WRED isn't good enough. However I understand that 
"fair-queue" uses a lot of CPU at these speeds, so it might not be 
feasable to do too advanced stuff at those speeds. However, at ADSL type 
accesses, for the uplink interface there is definitely a huge upside to 
have AQM.

When evaluating AQM the test scenarios should be quite advanced (I liked 
what I heard in ICCRG meeting yesterday) including VoIP, hundreds of TCP 
sessions using bittorrent, gaming (could be over TCP) etc. The ideal 
solution would be something that automatically allow at least per-user 
fairness in the upstream and something that perhaps sent ACKs and other 
smaller packets ahead of the queue of larger data packets.

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

From swmike@swm.pp.se  Wed Mar 13 10:32:07 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D8BC21F8E0B for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 10:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[AWL=-0.541,  BAYES_00=-2.599, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZkDlUrDQNvUh for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 10:32:06 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id ABABC21F8E0A for <tsvwg@ietf.org>; Wed, 13 Mar 2013 10:32:06 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id AF2B89C; Wed, 13 Mar 2013 18:32:05 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A91D89A; Wed, 13 Mar 2013 18:32:05 +0100 (CET)
Date: Wed, 13 Mar 2013 18:32:05 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Greg White <g.white@CableLabs.com>
In-Reply-To: <C38E406F654CD249AB7D30B93B0207F517F54D92@EXCHANGE.cablelabs.com>
Message-ID: <alpine.DEB.2.00.1303131826130.28820@uplift.swm.pp.se>
References: <C38E406F654CD249AB7D30B93B0207F517F54D92@EXCHANGE.cablelabs.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 17:32:07 -0000

On Wed, 13 Mar 2013, Greg White wrote:

> Some may consider 100ms a big number.

My personal opinion that for sustained congestion, there is very little 
use to ever keep a packet more than ~50 ms in a buffer. There is use to 
have larger buffers for short term smoothing of flows, but if the buffer 
has been at higher depths than 50 ms for several seconds, just start 
dropping/marking aggressively until the buffer is substantially lower than 
this. This example if more in a general WRED scenario. If it's a per-flow 
queueing scenario with fair-queue or alike, then of course there is little 
reason to drop the traffic early.

I liked the numbers presented at ICCRG yesterday which had substantially 
lower numbers than this, because even 10-30ms is felt for interactive 
applications (or badly written ones that request data, waits for the data 
to come back, and then makes new requests based on that data). Speed of 
light in fiber is something we can't do much about, but buffer depths we 
definitely can.

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

From gorry@erg.abdn.ac.uk  Wed Mar 13 11:28:20 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2A721F8E71; Wed, 13 Mar 2013 11:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.421
X-Spam-Level: 
X-Spam-Status: No, score=-106.421 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YD6orn3eovTW; Wed, 13 Mar 2013 11:28:19 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id F3B6C21F8DD4; Wed, 13 Mar 2013 11:28:15 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id F265C2B4400; Wed, 13 Mar 2013 18:28:12 +0000 (GMT)
Received: from 2001:df8:0:16:5ab0:35ff:fe7b:b828 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Wed, 13 Mar 2013 18:28:13 -0000
Message-ID: <b6d8c6a56b1e4f066019c81da8a202a0.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com>
References: <20130313164833.27324.89314.idtracker@ietfa.amsl.com> <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com>
Date: Wed, 13 Mar 2013 18:28:13 -0000
From: gorry@erg.abdn.ac.uk
To: "Fred Baker (fred)" <fred@cisco.com>
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for	draft-baker-tsvwg-aqm-recommendation-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 18:28:20 -0000

Fred,

Comments below:

Section 2, pt 2
"Deployed AQM SHOULD use ECN as well as loss, and set thresholds
 to mark traffic earlier than it is lost."
- This is not clear, I agree SHOULD use ECN for ECT traffic, of course.
- I'm not sure about threshold question that sets ECN drop before ECN loss
 - I like the idea for various reasons (I'm not expanding that here), but
this isn't what I understand as the current recommended TCP ECN reaction -
which reacts to CE in the same way as loss?

We need to be careful that we don't suggest not using ECN can gain advantage.

Section 2 pt 3
- Again I agree, but not sure we can say this as a BCP requirement? I
think we should think about how best to present this.

Section 2 pt 4
- Agree and we also now have tunnel technologies considering ECN support,
so also these?

Section 2 pt 5
- Nice, but not not possible - so TCP without ECN  *IS* going to cause
loss and delay if it shares the same congested queue. The idea of defining
guidance on what to expect here is also good, and maybe a significant step
to getting a better understanding.

I note that RFC 2309 does recommend RED but importantly it did not
motivate it in the way that now makes AQM an imperative. It also largely
pre-dated ECN and certainly the experience in ECN implementation.

Gorry

> Folks. I posted the email I sent yesterday as a draft, for discussion. I
> welcome comments, and if substantive comments are made, suggested text.
>
>
> On Mar 13, 2013, at 12:48 PM, <internet-drafts@ietf.org>
>  wrote:
>
>>
>> A new version of I-D, draft-baker-tsvwg-aqm-recommendation-00.txt
>> has been successfully submitted by Fred Baker and posted to the
>> IETF repository.
>>
>> Filename:	 draft-baker-tsvwg-aqm-recommendation
>> Revision:	 00
>> Title:		 IETF Recommendations Regarding Active Queue Management
>> Creation date:	 2013-03-13
>> Group:		 Individual Submission
>> Number of pages: 7
>> URL:
>> http://www.ietf.org/internet-drafts/draft-baker-tsvwg-aqm-recommendation-00.txt
>> Status:
>> http://datatracker.ietf.org/doc/draft-baker-tsvwg-aqm-recommendation
>> Htmlized:
>> http://tools.ietf.org/html/draft-baker-tsvwg-aqm-recommendation-00
>>
>>
>> Abstract:
>>   Fifteen years after the IAB issued its recommendations regarding
>>   congestion control in RFC 2309, a major issue in the community is the
>>   issue that RFC addresses: Buffer bloat.  It may be time to update the
>>   recommendation.
>>
>>
>>
>>
>> The IETF Secretariat
>>
>



From roland.bless@kit.edu  Wed Mar 13 12:27:15 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59E6111E8126 for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 12:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tc1SkNgYYZZP for <tsvwg@ietfa.amsl.com>; Wed, 13 Mar 2013 12:27:14 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE1411E80E1 for <tsvwg@ietf.org>; Wed, 13 Mar 2013 12:27:14 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  id 1UFrKM-0004Qz-Fk; Wed, 13 Mar 2013 20:27:13 +0100
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id F1574A807AE; Wed, 13 Mar 2013 20:27:05 +0100 (CET)
Message-ID: <5140D308.5010903@kit.edu>
Date: Wed, 13 Mar 2013 20:27:04 +0100
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <51408BF4.7090304@cisco.com>
In-Reply-To: <51408BF4.7090304@cisco.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1363202833.116138000
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 19:27:15 -0000

Hi,

On 13.03.2013 15:23, Eliot Lear wrote:
> I don't have an answer to that question, but Mark Allman from ICIR did
> attempt to characterize buffer bloat on the Internet through an
> empirical study that appeared in the January edition of CCR.  You can
> find a reference to that paper at the following URL:
> 
> http://www.sigcomm.org/ccr/papers/2013/January/2427036.2427041

I know the paper, but here are my 2 cents:
- more systematic analysis is good
- "bufferbloat" exists at least in many residential broadband access
scenarios and is _reproducible_ there. The effects are pretty annoying
for interactive communications. IMHO this is enough motivation
to change the current braindead tail drop behavior and replace it
by some AQM mechanism.

Regards,
 Roland


From roland.bless@kit.edu  Wed Mar 13 13:34:33 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B37721F8994; Wed, 13 Mar 2013 13:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.136
X-Spam-Level: 
X-Spam-Status: No, score=-6.136 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HnzQWd3ObEpn; Wed, 13 Mar 2013 13:34:32 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id C436C21F8976; Wed, 13 Mar 2013 13:34:32 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  id 1UFsNW-0000xO-IU; Wed, 13 Mar 2013 21:34:31 +0100
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 10348A807AE; Wed, 13 Mar 2013 21:34:25 +0100 (CET)
Message-ID: <5140E2D1.4050309@kit.edu>
Date: Wed, 13 Mar 2013 21:34:25 +0100
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: tsv-area@ietf.org, tsvwg <tsvwg@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1363206871.870406000
Subject: [tsvwg] AQM work
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 20:34:33 -0000

Hi,

two things (not sure whether tsv-area or tsvwg is appropriate)
following today's AQM discussion in the tsvarea meeting:

- IMHO AQM work is strongly related to the transport area
  as transport protocols are affected (as Lars already mentioned)
  and we also have ECN which is not working without AQM underneath.

- it may be the case that it makes no difference which AQM algorithms
  (codel, PIE, whatever) are actually deployed (as Matt Mathis pointed
  out) - and I agree with Fred that it would be good to have the
  flexibility to use different AQMs.
  However, to me it's not quite obvious how consistent a system with
  different heterogeneous deployed AQMs works. For instance, codel is
  (somewhat) tuned to TCP's CC behavior by employing a sqrt() related
  drop intensity, while other's are maybe not tuned to specific
  transport protocols.
  It may be interesting to study how a combination of different AQMs
  along a path influences the transport protocol's behavior in
  comparison to a more homogeneous AQM setting (maybe it doesn't
  matter so much as long as the bottleneck location isn't moving)...

Regards,
 Roland

From fred@cisco.com  Wed Mar 13 14:36:29 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C90F11E80A3; Wed, 13 Mar 2013 14:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.444
X-Spam-Level: 
X-Spam-Status: No, score=-110.444 tagged_above=-999 required=5 tests=[AWL=-0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2vfEMmsSisJ; Wed, 13 Mar 2013 14:36:28 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 5311411E80ED; Wed, 13 Mar 2013 14:36:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4028; q=dns/txt; s=iport; t=1363210588; x=1364420188; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=lo1UH6yMI6vclgbj88xgfoMu+uQF14C+IQl1CHO3kY4=; b=HvsRjqOz3SbiV+66p5cM9j2MQapsR301vUDzjAyWerX/cNEsZHyNMLzk 483ktgq5yFFl9njdmJkuLjJZSoxrR+HTdR4K+IlWBpeNQGPs9Ko05u+7I gGrlmBg+AGXxMJjdXYIFZ5pLqz+DzoHY7VK/7RFnZnGOVpu/f6UxQOC2x g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAA7wQFGtJV2c/2dsb2JhbABDxFaBWRZ0gioBAQEDATo2BwIFCwIBCA4KChQQMiUCBA4FCBECh3MGwxAXjU+BDgIxB4JfYQOnWoFUgTaBczU
X-IronPort-AV: E=Sophos;i="4.84,840,1355097600"; d="scan'208";a="186968258"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP; 13 Mar 2013 21:36:27 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r2DLaRAI005060 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Mar 2013 21:36:27 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Wed, 13 Mar 2013 16:36:27 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Thread-Topic: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt
Thread-Index: AQHOIDLRd3GHxkUedkmr9NY+bCaqUA==
Date: Wed, 13 Mar 2013 21:36:27 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7D0B1C@xmb-rcd-x09.cisco.com>
References: <20130313164833.27324.89314.idtracker@ietfa.amsl.com> <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com> <alpine.DEB.2.00.1303131810180.28820@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1303131810180.28820@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.236.238]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9A6A13669E485244838017466293B35B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 21:36:29 -0000

On Mar 13, 2013, at 1:25 PM, Mikael Abrahamsson <swmike@swm.pp.se>
 wrote:

> On Wed, 13 Mar 2013, Fred Baker (fred) wrote:
>=20
>> Folks. I posted the email I sent yesterday as a draft, for discussion. I=
 welcome comments, and if substantive comments are made, suggested text.
>=20
> I voiced my opinion on the tsv-area meeting via jabber that AQM especiall=
y on low/medium bw links (up to 10-20 megabits/s) is needed and bufferbloat=
 is a serious problem. As an employee of an operator, I would like to see d=
ocuments in the line of RFC6204, ie basic requirements, for (in this case) =
AQM that I can use in procurement documents. Preferrably these would be imp=
lemented by kernel vendors (linux kernel and others) so the actual device v=
endor only needs to turn it on and perhaps set a few parameters (like commu=
nicate the link speed to the queue handler).

> Coming back to the document at hand, reading draft-baker-tsvwg-aqm-recomm=
endation-00.txt, I notice a few things. Am I misinterpreting text such as:
>=20
> "Hence, network communication to the host regarding the moderation of
>   its traffic flow SHOULD include both ECN and loss, with ECN being
>   triggered earlier than loss."
>=20
> ... that it recommendeds that ECN traffic will be marked before non-ECN t=
raffic is dropped? I believe desired behaviour is that ECN traffic is marke=
d and non-ECN traffic is dropped at the exact same queue depth (or whatever=
 mechanism causes packets to be dropped/marked).

Hmm. I probably didn't word that all that well.

My point is that at some level of congestion stress, we should mark ECN-cap=
able traffic and drop non-ECN-capable traffic. At some higher level of stre=
ss, we should drop from all streams, ECN-capable or not. In general, I'd li=
ke to believe that ECN is effective in managing end-to-end throughput.

> Also, the documents seem to handle both host stack implementations and de=
vice queue management. Am I correct? Perhaps it would be preferable to have=
 one document handling queueing (including the queue on the host towards it=
s network interface (wifi/fixed/cellular etc), and another document talking=
 about "TCP congestion control mechanisms"? Or this the document at hand tr=
ying to be an umbrella document for other documents?

One could argue for the separation. To my mind, though, they are firmly lin=
ked. Besides self-defense, the reason the network marks/drops traffic is to=
 signal to TCP/SCTP. if that's the case, it seems like it's useful to say w=
hat that signal means to TCP/SCTP, and how we hope it might work.

> Anyhow, I feel this (AQM/congestion) area of discussion is extremely impo=
rtant and it solves a real life problem that impacts a lot of people on the=
 Internet as it works today. Personally I have routers with quite advanced =
AQM on my home connection (100/100 megabit/s) because I feel that FIFO even=
 with WRED isn't good enough. However I understand that "fair-queue" uses a=
 lot of CPU at these speeds, so it might not be feasable to do too advanced=
 stuff at those speeds. However, at ADSL type accesses, for the uplink inte=
rface there is definitely a huge upside to have AQM.

That depends on how FQ is implemented. The implementation I did in 1994 pro=
bably would have been high overhead. It has been minted by others, and I be=
lieve rewritten to be a calendar queue implementation. For that, I would no=
t expect it was that much higher. I'll go take a look, though.

> When evaluating AQM the test scenarios should be quite advanced (I liked =
what I heard in ICCRG meeting yesterday) including VoIP, hundreds of TCP se=
ssions using bittorrent, gaming (could be over TCP) etc. The ideal solution=
 would be something that automatically allow at least per-user fairness in =
the upstream and something that perhaps sent ACKs and other smaller packets=
 ahead of the queue of larger data packets.
>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se


From andrewmcgr@gmail.com  Wed Mar 13 14:54:27 2013
Return-Path: <andrewmcgr@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E72D311E80A6; Wed, 13 Mar 2013 14:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.235
X-Spam-Level: 
X-Spam-Status: No, score=-3.235 tagged_above=-999 required=5 tests=[AWL=0.136,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QryJLjDEDQsD; Wed, 13 Mar 2013 14:54:27 -0700 (PDT)
Received: from mail-lb0-f179.google.com (mail-lb0-f179.google.com [209.85.217.179]) by ietfa.amsl.com (Postfix) with ESMTP id 8785D11E80A3; Wed, 13 Mar 2013 14:54:26 -0700 (PDT)
Received: by mail-lb0-f179.google.com with SMTP id j14so1363661lbo.38 for <multiple recipients>; Wed, 13 Mar 2013 14:54:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=yELg8lWn/8omat1JOvtjwBm4yuEAY1qBw9HF8dU8aB4=; b=nsApFsD9U97l0VmTU7VbzcObb2epTrjvw6hJbAEvKAgJilQxPQEujcTm3EVfqfs2OQ UGCM8HPWv/Mew1ec20H33FexvGK4K65UQq0zaJw7Gpi9z4bUd6gzIAZ1kSCaEoGDLsIC J2jHvCIfAd1Hy+lojrAHwNIlIMJGB/tN8KB28UtVnVd35Nyh9o7OpMHz/wzjTfKGv4kS aCHdx4M0fFIk2n0vlbbjYoeCd//mB7xLRteey5ZCc3Mf2rU+qbhTlcHY1sLxgL1kEKZG 2WYfNmaN3cmw4+SjA/4w/SOYLwlvAAlxrgwCyPALSE4HEMu0VmPEsIDj4W3QRzmNiZpI cQjA==
MIME-Version: 1.0
X-Received: by 10.152.46.17 with SMTP id r17mr19185744lam.47.1363211665324; Wed, 13 Mar 2013 14:54:25 -0700 (PDT)
Received: by 10.112.21.7 with HTTP; Wed, 13 Mar 2013 14:54:25 -0700 (PDT)
In-Reply-To: <5140E2D1.4050309@kit.edu>
References: <5140E2D1.4050309@kit.edu>
Date: Wed, 13 Mar 2013 17:54:25 -0400
Message-ID: <CAA_e5Z4H+mcLqwhHc5JPmPy4AypDrYB1iJzbX-tySmR5AFj0kA@mail.gmail.com>
From: Andrew McGregor <andrewmcgr@gmail.com>
To: Roland Bless <roland.bless@kit.edu>
Content-Type: multipart/alternative; boundary=bcaec552410612913d04d7d573bf
Cc: tsv-area@ietf.org, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] AQM work
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 21:54:28 -0000

--bcaec552410612913d04d7d573bf
Content-Type: text/plain; charset=ISO-8859-1

The sqrt() in CoDel is *not* tuning it to TCP, it's scaling the drops to
the right proportionality for controlling the queue.  It's an artefact of
happening to measure the square of what you really want.  Nevertheless,
CoDel's general behaviour is actually tuned to TCP, allowing a new flow to
build queue for a while is only appropriate for TCP-like controllers.

I believe we need to standardise the signals from the network to the
transport, so AQM designers at least know what signals and signal density
they need to deliver (there's at least six signal paths... drops, ECN and
arrival time, and their respective statistical distributions).  Given that,
we can then make sure that all the transport control systems deal with
those signals sanely (and ignore those that are not helpful).

That's quite a bit of work, and I expect it to need its own working group.
 It will also have a research dimension, so ICCRG will need to be involved.
 That WG should be in the transport area, of course.

Andrew


On Wed, Mar 13, 2013 at 4:34 PM, Roland Bless <roland.bless@kit.edu> wrote:

> Hi,
>
> two things (not sure whether tsv-area or tsvwg is appropriate)
> following today's AQM discussion in the tsvarea meeting:
>
> - IMHO AQM work is strongly related to the transport area
>   as transport protocols are affected (as Lars already mentioned)
>   and we also have ECN which is not working without AQM underneath.
>
> - it may be the case that it makes no difference which AQM algorithms
>   (codel, PIE, whatever) are actually deployed (as Matt Mathis pointed
>   out) - and I agree with Fred that it would be good to have the
>   flexibility to use different AQMs.
>   However, to me it's not quite obvious how consistent a system with
>   different heterogeneous deployed AQMs works. For instance, codel is
>   (somewhat) tuned to TCP's CC behavior by employing a sqrt() related
>   drop intensity, while other's are maybe not tuned to specific
>   transport protocols.
>   It may be interesting to study how a combination of different AQMs
>   along a path influences the transport protocol's behavior in
>   comparison to a more homogeneous AQM setting (maybe it doesn't
>   matter so much as long as the bottleneck location isn't moving)...
>
> Regards,
>  Roland
>

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

<div dir=3D"ltr">The sqrt() in CoDel is *not* tuning it to TCP, it&#39;s sc=
aling the drops to the right proportionality for controlling the queue. =A0=
It&#39;s an artefact of happening to measure the square of what you really =
want. =A0Nevertheless, CoDel&#39;s general behaviour is actually tuned to T=
CP, allowing a new flow to build queue for a while is only appropriate for =
TCP-like controllers.<div>
<br></div><div style>I believe we need to standardise the signals from the =
network to the transport, so AQM designers at least know what signals and s=
ignal density they need to deliver (there&#39;s at least six signal paths..=
. drops, ECN and arrival time, and their respective statistical distributio=
ns). =A0Given that, we can then make sure that all the transport control sy=
stems deal with those signals sanely (and ignore those that are not helpful=
).</div>
<div style><br></div><div style>That&#39;s quite a bit of work, and I expec=
t it to need its own working group. =A0It will also have a research dimensi=
on, so ICCRG will need to be involved. =A0That WG should be in the transpor=
t area, of course.</div>
<div style><br></div><div style>Andrew</div></div><div class=3D"gmail_extra=
"><br><br><div class=3D"gmail_quote">On Wed, Mar 13, 2013 at 4:34 PM, Rolan=
d Bless <span dir=3D"ltr">&lt;<a href=3D"mailto:roland.bless@kit.edu" targe=
t=3D"_blank">roland.bless@kit.edu</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi,<br>
<br>
two things (not sure whether tsv-area or tsvwg is appropriate)<br>
following today&#39;s AQM discussion in the tsvarea meeting:<br>
<br>
- IMHO AQM work is strongly related to the transport area<br>
=A0 as transport protocols are affected (as Lars already mentioned)<br>
=A0 and we also have ECN which is not working without AQM underneath.<br>
<br>
- it may be the case that it makes no difference which AQM algorithms<br>
=A0 (codel, PIE, whatever) are actually deployed (as Matt Mathis pointed<br=
>
=A0 out) - and I agree with Fred that it would be good to have the<br>
=A0 flexibility to use different AQMs.<br>
=A0 However, to me it&#39;s not quite obvious how consistent a system with<=
br>
=A0 different heterogeneous deployed AQMs works. For instance, codel is<br>
=A0 (somewhat) tuned to TCP&#39;s CC behavior by employing a sqrt() related=
<br>
=A0 drop intensity, while other&#39;s are maybe not tuned to specific<br>
=A0 transport protocols.<br>
=A0 It may be interesting to study how a combination of different AQMs<br>
=A0 along a path influences the transport protocol&#39;s behavior in<br>
=A0 comparison to a more homogeneous AQM setting (maybe it doesn&#39;t<br>
=A0 matter so much as long as the bottleneck location isn&#39;t moving)...<=
br>
<br>
Regards,<br>
=A0Roland<br>
</blockquote></div><br></div>

--bcaec552410612913d04d7d573bf--

From fred@cisco.com  Wed Mar 13 15:10:12 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43F8321F8A11; Wed, 13 Mar 2013 15:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.438
X-Spam-Level: 
X-Spam-Status: No, score=-110.438 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jwI27xAuV+gH; Wed, 13 Mar 2013 15:10:11 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id A65D121F8A14; Wed, 13 Mar 2013 15:10:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5228; q=dns/txt; s=iport; t=1363212610; x=1364422210; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+fYRLC04GRAWekv/QSHX4OzvNZMi33KFtRL7RY+cXTg=; b=P7DepqYjLlt9npwS3wZJHUxROtVxtex8przP9v7PmTLgvekKVUMVsD7k 2BVMbA+SwswmpknJpUalaJebYjh6fvajZ531P2p/6zmgWvL7ZkfmPjLMS nSxbAbOg0PUbcskCK/u7cLKMzZ9UKLqv7rnLDg8a7LRwPyclIgQOrz/Xd g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAIP4QFGtJV2c/2dsb2JhbABDDrM9kQuBVxZ0gioBAQEDAWwKAQIFCwIBCBgKJDIlAgQOBQgBC4d6BgzCcBeNTxB+AjEHgl9hA4g+jzmPY4FUdz+BczU
X-IronPort-AV: E=Sophos;i="4.84,840,1355097600"; d="scan'208";a="187234577"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-4.cisco.com with ESMTP; 13 Mar 2013 22:10:10 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r2DMAAsM032666 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Mar 2013 22:10:10 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Wed, 13 Mar 2013 17:10:09 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "<gorry@erg.abdn.ac.uk>" <gorry@erg.abdn.ac.uk>
Thread-Topic: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt
Thread-Index: AQHOIAqa1tJ18EAwSkCm0kPJ4goPbg==
Date: Wed, 13 Mar 2013 22:10:09 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7D0BD6@xmb-rcd-x09.cisco.com>
References: <20130313164833.27324.89314.idtracker@ietfa.amsl.com> <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com> <b6d8c6a56b1e4f066019c81da8a202a0.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <b6d8c6a56b1e4f066019c81da8a202a0.squirrel@www.erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.236.238]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <0F1F6694A3DB1347B34C181AB4CDBC24@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for	draft-baker-tsvwg-aqm-recommendation-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2013 22:10:12 -0000

On Mar 13, 2013, at 2:28 PM, <gorry@erg.abdn.ac.uk>
 wrote:

> Fred,
>=20
> Comments below:
>=20
> Section 2, pt 2
> "Deployed AQM SHOULD use ECN as well as loss, and set thresholds
> to mark traffic earlier than it is lost."
> - This is not clear, I agree SHOULD use ECN for ECT traffic, of course.
> - I'm not sure about threshold question that sets ECN drop before ECN los=
s

As I just said to Mikael, I don't think I worded that one well. I'm envisag=
ing two thresholds, testing two stress levels. It a lower one, one marks EC=
N-capable traffic and drops non-ECN-capable traffic; at the higher one, one=
 drops from all traffic. What "threshold" means in a given algorithm is alg=
orithm-dependent, however.

> - I like the idea for various reasons (I'm not expanding that here), but
> this isn't what I understand as the current recommended TCP ECN reaction =
-
> which reacts to CE in the same way as loss?

Well, 3168 says that TCP should respond in the same way it responds to loss=
. By that, what they mean is that it reduces cwnd, and if in slow-start, ex=
it slow-start. The other thing it does to respond to loss is to retransmit =
a message. There is obviously no need to retransmit, but it should indeed p=
lay with cwnd in some way.

How it responds will be specific to the congestion control algorithm, thoug=
h. With newreno, it might set cwnd to 1 or to the initial value, or perhaps=
 halve it. With CUBIC, IIRC, it reduces it by a smaller fraction. With CalT=
ech FAST, which is a delay-based model and tunes toward the knee, I could i=
magine that instead of literally reducing cwnd (if you're at the knee, why =
would you do that?) you might recalculate the current mean RTT.=20

> We need to be careful that we don't suggest not using ECN can gain advant=
age.

Did I say that?

> Section 2 pt 3
> - Again I agree, but not sure we can say this as a BCP requirement? I
> think we should think about how best to present this.

2.3.  AQM algorithms deployed SHOULD NOT require operational tuning=20

There are algorithms that don't require tuning. I'm suggesting we use one.

> Section 2 pt 4
> - Agree and we also now have tunnel technologies considering ECN support,
> so also these?

2.4.  AQM algorithms deployed SHOULD be effective on all common
      Internet traffic=20

We want to follow the rules for remarking traffic; I believe that's RFC 298=
3.

> Section 2 pt 5
> - Nice, but not not possible - so TCP without ECN  *IS* going to cause
> loss and delay if it shares the same congested queue. The idea of definin=
g
> guidance on what to expect here is also good, and maybe a significant ste=
p
> to getting a better understanding.

     2.5.  TCP and SCTP congestion control algorithms SHOULD
           maximize their use of available bandwidth without
           incurring loss or undue round trip delay=20

I'm not quite as pessimistic about the possibility here. We actually do hav=
e congestion control algorithms that tune to a point approximating the knee=
, and at least one that will co-exist with a loss-based model effectively (=
CAIA CDG). Note that I'm not dying to get to the knee, although that would =
be nice; the point is to not hit the cliff. Once the window advances to/bey=
ond the knee, we are using the available bandwidth in its entirety; increas=
ing cwnd after that point merely increases delay and the probability of los=
s, not throughput rate.

> I note that RFC 2309 does recommend RED but importantly it did not
> motivate it in the way that now makes AQM an imperative. It also largely
> pre-dated ECN and certainly the experience in ECN implementation.

Hmm. OK, then maybe we do need to re-do 2309. That was my first instinct wh=
en Wesley and I first chatted about this in mail, and I thought I would try=
 simply building on it. I'll take a gander at that.

> Gorry
>=20
>> Folks. I posted the email I sent yesterday as a draft, for discussion. I
>> welcome comments, and if substantive comments are made, suggested text.
>>=20
>>=20
>> On Mar 13, 2013, at 12:48 PM, <internet-drafts@ietf.org>
>> wrote:
>>=20
>>>=20
>>> A new version of I-D, draft-baker-tsvwg-aqm-recommendation-00.txt
>>> has been successfully submitted by Fred Baker and posted to the
>>> IETF repository.
>>>=20
>>> Filename:	 draft-baker-tsvwg-aqm-recommendation
>>> Revision:	 00
>>> Title:		 IETF Recommendations Regarding Active Queue Management
>>> Creation date:	 2013-03-13
>>> Group:		 Individual Submission
>>> Number of pages: 7
>>> URL:
>>> http://www.ietf.org/internet-drafts/draft-baker-tsvwg-aqm-recommendatio=
n-00.txt
>>> Status:
>>> http://datatracker.ietf.org/doc/draft-baker-tsvwg-aqm-recommendation
>>> Htmlized:
>>> http://tools.ietf.org/html/draft-baker-tsvwg-aqm-recommendation-00
>>>=20
>>>=20
>>> Abstract:
>>>  Fifteen years after the IAB issued its recommendations regarding
>>>  congestion control in RFC 2309, a major issue in the community is the
>>>  issue that RFC addresses: Buffer bloat.  It may be time to update the
>>>  recommendation.
>>>=20
>>>=20
>>>=20
>>>=20
>>> The IETF Secretariat
>>>=20
>>=20
>=20
>=20


From swmike@swm.pp.se  Wed Mar 13 20:09:50 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41ED221F85C0; Wed, 13 Mar 2013 20:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e1rU2jNHhmiu; Wed, 13 Mar 2013 20:09:49 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id A721C21F856D; Wed, 13 Mar 2013 20:09:49 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 45EF69C; Thu, 14 Mar 2013 04:09:48 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 3C9479A; Thu, 14 Mar 2013 04:09:48 +0100 (CET)
Date: Thu, 14 Mar 2013 04:09:48 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Fred Baker (fred)" <fred@cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7D0B1C@xmb-rcd-x09.cisco.com>
Message-ID: <alpine.DEB.2.00.1303140402490.28820@uplift.swm.pp.se>
References: <20130313164833.27324.89314.idtracker@ietfa.amsl.com> <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com> <alpine.DEB.2.00.1303131810180.28820@uplift.swm.pp.se> <8C48B86A895913448548E6D15DA7553B7D0B1C@xmb-rcd-x09.cisco.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 03:09:50 -0000

On Wed, 13 Mar 2013, Fred Baker (fred) wrote:

> That depends on how FQ is implemented. The implementation I did in 1994 
> probably would have been high overhead. It has been minted by others, 
> and I believe rewritten to be a calendar queue implementation. For that, 
> I would not expect it was that much higher. I'll go take a look, though.

To be concrete, turning on fair-queue (and some other stuff to assure bw 
for certain tcp/port combinations) on a Cisco 7200 style device seems to 
give 2-3x CPU usage for the same traffic. This is with just 30-100 flows. 
This is in latest code available (15.2).

So since in my market we have gig speeds (we have low cost residential 
CPEs capable of moving ~600 megabits/s in a single tcp session), CPU 
impact of these queueing mechanisms is important.

And yes, I feel doing AQM at 100/100 speeds is still important, but here 
the limiting factor for speed might actually be the CPU of the CPE, so the 
queueing mechanism should preferrably be able to prioritize and gracefully 
handle the case where the links are not full but instead the CPE CPU is 
insufficient and that's what causing congestion/drops.

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

From andrewmcgr@gmail.com  Wed Mar 13 20:59:48 2013
Return-Path: <andrewmcgr@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5582F11E809C; Wed, 13 Mar 2013 20:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Mn2jp5URqzL; Wed, 13 Mar 2013 20:59:47 -0700 (PDT)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id ED5FD21F8CD2; Wed, 13 Mar 2013 20:59:46 -0700 (PDT)
Received: by mail-la0-f53.google.com with SMTP id fr10so1974207lab.12 for <multiple recipients>; Wed, 13 Mar 2013 20:59:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=2Qjc55L01bGHdCGSJ79HltqX3woTdc6ENsKF/wm9aTI=; b=ulvAB7gvG2c8Omfft1BZnAzfHWeoT6jyDy842vdGvJsL9X/Nd9Tf1FtOq41rpMEjH1 S87NO8I7bsWFrV4JO4GvcixjdOq/AWxVQBCdjf8KXBsz8c0DF9jb7rzeJXXLaXL21NCP kYReRcxprkmkhsP7J52MP686+jkffOxb+RPzTDel22vK/2hAXwDSU9o3AIkwknJKHtRq 6cor/IC445itHNYgeJlnf7g1uwBtH641WTApnLKtfaHOwSN6UkEt1K20eSA3b2TW+OYj 3y94OYA3dea7QywtQ/NedTvOeMuKY/OZzbc+fxP31W2lCxlFiaepsStsMFWoYXTOAgov cX6Q==
MIME-Version: 1.0
X-Received: by 10.112.85.37 with SMTP id e5mr521512lbz.43.1363233585895; Wed, 13 Mar 2013 20:59:45 -0700 (PDT)
Received: by 10.112.21.7 with HTTP; Wed, 13 Mar 2013 20:59:45 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.00.1303140402490.28820@uplift.swm.pp.se>
References: <20130313164833.27324.89314.idtracker@ietfa.amsl.com> <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com> <alpine.DEB.2.00.1303131810180.28820@uplift.swm.pp.se> <8C48B86A895913448548E6D15DA7553B7D0B1C@xmb-rcd-x09.cisco.com> <alpine.DEB.2.00.1303140402490.28820@uplift.swm.pp.se>
Date: Wed, 13 Mar 2013 23:59:45 -0400
Message-ID: <CAA_e5Z58nOzgsfCj=4O36P51NrK6jR8HCC0Zjvfz5jrCYpi46Q@mail.gmail.com>
From: Andrew McGregor <andrewmcgr@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary=bcaec55553bca2239404d7da8dbf
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 03:59:48 -0000

--bcaec55553bca2239404d7da8dbf
Content-Type: text/plain; charset=ISO-8859-1

A Netgear WNDR3800 (680MHz MIPS) can handle fq_codel on two flat out
802.11n interfaces at the same time and still be very lightly loaded.  CPU
is not a problem because fq_codel is a tiny fraction of the usage of the
firewall, connection tracking and 802.11 AP code, all of which are
necessary (in IPv4 the NAT also uses more CPU than fq_codel).



On Wed, Mar 13, 2013 at 11:09 PM, Mikael Abrahamsson <swmike@swm.pp.se>wrote:

> On Wed, 13 Mar 2013, Fred Baker (fred) wrote:
>
>  That depends on how FQ is implemented. The implementation I did in 1994
>> probably would have been high overhead. It has been minted by others, and I
>> believe rewritten to be a calendar queue implementation. For that, I would
>> not expect it was that much higher. I'll go take a look, though.
>>
>
> To be concrete, turning on fair-queue (and some other stuff to assure bw
> for certain tcp/port combinations) on a Cisco 7200 style device seems to
> give 2-3x CPU usage for the same traffic. This is with just 30-100 flows.
> This is in latest code available (15.2).
>
> So since in my market we have gig speeds (we have low cost residential
> CPEs capable of moving ~600 megabits/s in a single tcp session), CPU impact
> of these queueing mechanisms is important.
>
> And yes, I feel doing AQM at 100/100 speeds is still important, but here
> the limiting factor for speed might actually be the CPU of the CPE, so the
> queueing mechanism should preferrably be able to prioritize and gracefully
> handle the case where the links are not full but instead the CPE CPU is
> insufficient and that's what causing congestion/drops.
>
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>

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

<div dir=3D"ltr">A Netgear WNDR3800 (680MHz MIPS) can handle fq_codel on tw=
o flat out 802.11n interfaces at the same time and still be very lightly lo=
aded. =A0CPU is not a problem because fq_codel is a tiny fraction of the us=
age of the firewall, connection tracking and 802.11 AP code, all of which a=
re necessary (in IPv4 the NAT also uses more CPU than fq_codel).<div>
<br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quot=
e">On Wed, Mar 13, 2013 at 11:09 PM, Mikael Abrahamsson <span dir=3D"ltr">&=
lt;<a href=3D"mailto:swmike@swm.pp.se" target=3D"_blank">swmike@swm.pp.se</=
a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Wed, 13 Mar 2013, Fred =
Baker (fred) wrote:<br>
<br>
</div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
That depends on how FQ is implemented. The implementation I did in 1994 pro=
bably would have been high overhead. It has been minted by others, and I be=
lieve rewritten to be a calendar queue implementation. For that, I would no=
t expect it was that much higher. I&#39;ll go take a look, though.<br>

</blockquote>
<br></div>
To be concrete, turning on fair-queue (and some other stuff to assure bw fo=
r certain tcp/port combinations) on a Cisco 7200 style device seems to give=
 2-3x CPU usage for the same traffic. This is with just 30-100 flows. This =
is in latest code available (15.2).<br>

<br>
So since in my market we have gig speeds (we have low cost residential CPEs=
 capable of moving ~600 megabits/s in a single tcp session), CPU impact of =
these queueing mechanisms is important.<br>
<br>
And yes, I feel doing AQM at 100/100 speeds is still important, but here th=
e limiting factor for speed might actually be the CPU of the CPE, so the qu=
eueing mechanism should preferrably be able to prioritize and gracefully ha=
ndle the case where the links are not full but instead the CPE CPU is insuf=
ficient and that&#39;s what causing congestion/drops.<div class=3D"HOEnZb">
<div class=3D"h5"><br>
<br>
-- <br>
Mikael Abrahamsson =A0 =A0email: <a href=3D"mailto:swmike@swm.pp.se" target=
=3D"_blank">swmike@swm.pp.se</a><br>
</div></div></blockquote></div><br></div>

--bcaec55553bca2239404d7da8dbf--

From swmike@swm.pp.se  Wed Mar 13 22:07:39 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E3B21F8E74; Wed, 13 Mar 2013 22:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.378
X-Spam-Level: 
X-Spam-Status: No, score=-2.378 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HdBCGraRjgx2; Wed, 13 Mar 2013 22:07:38 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 90C8421F8E73; Wed, 13 Mar 2013 22:07:38 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 52B0F9C; Thu, 14 Mar 2013 06:07:37 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 4A46C9A; Thu, 14 Mar 2013 06:07:37 +0100 (CET)
Date: Thu, 14 Mar 2013 06:07:37 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Andrew McGregor <andrewmcgr@gmail.com>
In-Reply-To: <CAA_e5Z58nOzgsfCj=4O36P51NrK6jR8HCC0Zjvfz5jrCYpi46Q@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1303140540370.17716@uplift.swm.pp.se>
References: <20130313164833.27324.89314.idtracker@ietfa.amsl.com> <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com> <alpine.DEB.2.00.1303131810180.28820@uplift.swm.pp.se> <8C48B86A895913448548E6D15DA7553B7D0B1C@xmb-rcd-x09.cisco.com> <alpine.DEB.2.00.1303140402490.28820@uplift.swm.pp.se> <CAA_e5Z58nOzgsfCj=4O36P51NrK6jR8HCC0Zjvfz5jrCYpi46Q@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 05:07:39 -0000

On Wed, 13 Mar 2013, Andrew McGregor wrote:

> A Netgear WNDR3800 (680MHz MIPS) can handle fq_codel on two flat out 
> 802.11n interfaces at the same time and still be very lightly loaded. 
> CPU is not a problem because fq_codel is a tiny fraction of the usage of 
> the firewall, connection tracking and 802.11 AP code, all of which are 
> necessary (in IPv4 the NAT also uses more CPU than fq_codel).

I'll have to look into what devices we're using and what CPUs they're 
using. The WNDR3800 seems to be a fairly high end device when I look at 
the price point.

However, the other part of your reply sounds hopeful. I read 
draft-nichols-tsvwg-codel-01 and I now realise that yes, it shouldn't be 
too cpu intensive as the hashing into bins sounds efficient on a 
per-packet level.

Would having multiple bin "trees" increase CPU usage a lot? I'm thinking 
of the use case where there are 10 computers in the home, of which one is 
doing 100 upload TCP sessions (bittorrent). If there was some mechanism 
that could identify a source IP address that caused most of the congestion 
and put them in a separate bin "tree" (basically each source IP would get 
its own set of bins, up to a maximum of perhaps 16 trees) and then these 
sets of bins would be emptied in a round-robin fashion (MDRR perhaps?). Or 
perhaps there would just be a "high volume speaker" tree and a "low volume 
speaker" tree, and it would be enough to just MDRR between these two 
trees. I realise we're now into "flow" territory which is exactly what 
Codel doesn't need to bother with currently, but just checking...

I saw in ICCRG that some testing was done with LEDBAT which I would 
imagine would help for the bittorrent case, but what about trying to 
achieve some of that without needing LEDBAT by using the above technique?

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

From internet-drafts@ietf.org  Thu Mar 14 05:14:36 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F21221F8F39; Thu, 14 Mar 2013 05:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level: 
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wmtxzYxA5tEO; Thu, 14 Mar 2013 05:14:35 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B526D21F8AD8; Thu, 14 Mar 2013 05:14:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.43
Message-ID: <20130314121435.26898.65449.idtracker@ietfa.amsl.com>
Date: Thu, 14 Mar 2013 05:14:35 -0700
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-udp-encaps-13.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 12:14:36 -0000

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

	Title           : UDP Encapsulation of SCTP Packets for End-Host to End-Ho=
st Communication
	Author(s)       : Michael Tuexen
                          Randall R. Stewart
	Filename        : draft-ietf-tsvwg-sctp-udp-encaps-13.txt
	Pages           : 12
	Date            : 2013-03-14

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

   Please note that this document only describes the functionality
   required within an SCTP stack to add on UDP encapsulation, providing
   only those mechanisms for two end-hosts to communicate with each
   other over UDP ports.  In particular, it does not provide mechanisms
   to determine whether UDP encapsulation is being used by the peer, nor
   the mechanisms for determining which remote UDP port number can be
   used.  These functions are are out of scope for this document.

   This document covers only end-hosts and not tunneling (egress or
   ingress) end-points.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-udp-encaps-13


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


From andrewmcgr@gmail.com  Thu Mar 14 06:38:12 2013
Return-Path: <andrewmcgr@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98FBA1F0D0B; Thu, 14 Mar 2013 06:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id deYhrULpkY2q; Thu, 14 Mar 2013 06:38:11 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 34AEA1F0D09; Thu, 14 Mar 2013 06:38:11 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id er20so2431006lab.4 for <multiple recipients>; Thu, 14 Mar 2013 06:38:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=wiXSmf5kU3abzlAbl2XIiSGQQDSiiVdMBqs3YRh3L4o=; b=ar2ixIyBZIESgZ1pkZnQdxlEC9AsrmDDKuvwDGsbS/KtbTpH3/xm0xbzssEsrmLcZk 5mJQ+N1qI5X85stadlcD9WmMq+KCzxfce5bP93ZjwyXI5rpICKfFxSQ1qtZ/sm3le4JT nrgSxanNTFPQN6ZTGkaNsUY+ulurdGDXTBn384yhV7DPUmrhBthAJ4OSbZ2er1PyRZnO x2iBsX+VPjVLEjewlK+vdPcaapqjxV6gBYfnIHvCTmJs4IZGWNUXuEXPNvZ9Z6MT+4oV u2cnAEqYa2ERCwg5PWx1Eyt7bDglsXRCo5Z8qxwkVEhN8sVJLLSnX+PcBkpQObJ630va zVOw==
MIME-Version: 1.0
X-Received: by 10.152.112.231 with SMTP id it7mr2242761lab.10.1363268290138; Thu, 14 Mar 2013 06:38:10 -0700 (PDT)
Received: by 10.112.21.7 with HTTP; Thu, 14 Mar 2013 06:38:09 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.00.1303140540370.17716@uplift.swm.pp.se>
References: <20130313164833.27324.89314.idtracker@ietfa.amsl.com> <8C48B86A895913448548E6D15DA7553B7D045F@xmb-rcd-x09.cisco.com> <alpine.DEB.2.00.1303131810180.28820@uplift.swm.pp.se> <8C48B86A895913448548E6D15DA7553B7D0B1C@xmb-rcd-x09.cisco.com> <alpine.DEB.2.00.1303140402490.28820@uplift.swm.pp.se> <CAA_e5Z58nOzgsfCj=4O36P51NrK6jR8HCC0Zjvfz5jrCYpi46Q@mail.gmail.com> <alpine.DEB.2.00.1303140540370.17716@uplift.swm.pp.se>
Date: Thu, 14 Mar 2013 09:38:09 -0400
Message-ID: <CAA_e5Z6hXZ+9v+3vWBL1Qxh+i=wm_3WGwtefg+_cc=dT8VXfwA@mail.gmail.com>
From: Andrew McGregor <andrewmcgr@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary=f46d040715332ad92904d7e2a279
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for draft-baker-tsvwg-aqm-recommendation-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 13:38:12 -0000

--f46d040715332ad92904d7e2a279
Content-Type: text/plain; charset=ISO-8859-1

fq_codel achieves nearly all of what you're suggesting already, except that
it works on a flow basis rather than on a host basis.  You could add a DRR
layer hashing on IP address only to get host-level balancing.  An efficient
implementation of that would again add only a very little overhead.

fq_codel actually has a 'high volume' and 'low volume' flow rotation, which
are called 'old' and 'new' in the code, and commonly 'thick' and 'thin'
flows in mailing list discussions.  Flows arrive in the thin flow list, get
demoted to the thick flow list when they build queue, and are removed from
either list when they drain completely.  When a flow reappears it will be
introduced back in to the thin flow list, but it will keep its codel state.
 Flows are served from the thin list until it is empty, and then from the
thick list, in round-robin order, so it is very much like DRR.


On Thu, Mar 14, 2013 at 1:07 AM, Mikael Abrahamsson <swmike@swm.pp.se>wrote:

> On Wed, 13 Mar 2013, Andrew McGregor wrote:
>
>  A Netgear WNDR3800 (680MHz MIPS) can handle fq_codel on two flat out
>> 802.11n interfaces at the same time and still be very lightly loaded. CPU
>> is not a problem because fq_codel is a tiny fraction of the usage of the
>> firewall, connection tracking and 802.11 AP code, all of which are
>> necessary (in IPv4 the NAT also uses more CPU than fq_codel).
>>
>
> I'll have to look into what devices we're using and what CPUs they're
> using. The WNDR3800 seems to be a fairly high end device when I look at the
> price point.
>
> However, the other part of your reply sounds hopeful. I read
> draft-nichols-tsvwg-codel-01 and I now realise that yes, it shouldn't be
> too cpu intensive as the hashing into bins sounds efficient on a per-packet
> level.
>
> Would having multiple bin "trees" increase CPU usage a lot? I'm thinking
> of the use case where there are 10 computers in the home, of which one is
> doing 100 upload TCP sessions (bittorrent). If there was some mechanism
> that could identify a source IP address that caused most of the congestion
> and put them in a separate bin "tree" (basically each source IP would get
> its own set of bins, up to a maximum of perhaps 16 trees) and then these
> sets of bins would be emptied in a round-robin fashion (MDRR perhaps?). Or
> perhaps there would just be a "high volume speaker" tree and a "low volume
> speaker" tree, and it would be enough to just MDRR between these two trees.
> I realise we're now into "flow" territory which is exactly what Codel
> doesn't need to bother with currently, but just checking...
>
> I saw in ICCRG that some testing was done with LEDBAT which I would
> imagine would help for the bittorrent case, but what about trying to
> achieve some of that without needing LEDBAT by using the above technique?
>
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>

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

<div dir=3D"ltr">fq_codel achieves nearly all of what you&#39;re suggesting=
 already, except that it works on a flow basis rather than on a host basis.=
 =A0You could add a DRR layer hashing on IP address only to get host-level =
balancing. =A0An efficient implementation of that would again add only a ve=
ry little overhead.<div>
<br></div><div style>fq_codel actually has a &#39;high volume&#39; and &#39=
;low volume&#39; flow rotation, which are called &#39;old&#39; and &#39;new=
&#39; in the code, and commonly &#39;thick&#39; and &#39;thin&#39; flows in=
 mailing list discussions. =A0Flows arrive in the thin flow list, get demot=
ed to the thick flow list when they build queue, and are removed from eithe=
r list when they drain completely. =A0When a flow reappears it will be intr=
oduced back in to the thin flow list, but it will keep its codel state. =A0=
Flows are served from the thin list until it is empty, and then from the th=
ick list, in round-robin order, so it is very much like DRR.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,=
 Mar 14, 2013 at 1:07 AM, Mikael Abrahamsson <span dir=3D"ltr">&lt;<a href=
=3D"mailto:swmike@swm.pp.se" target=3D"_blank">swmike@swm.pp.se</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Wed, 13 Mar 2013, Andre=
w McGregor wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
A Netgear WNDR3800 (680MHz MIPS) can handle fq_codel on two flat out 802.11=
n interfaces at the same time and still be very lightly loaded. CPU is not =
a problem because fq_codel is a tiny fraction of the usage of the firewall,=
 connection tracking and 802.11 AP code, all of which are necessary (in IPv=
4 the NAT also uses more CPU than fq_codel).<br>

</blockquote>
<br></div>
I&#39;ll have to look into what devices we&#39;re using and what CPUs they&=
#39;re using. The WNDR3800 seems to be a fairly high end device when I look=
 at the price point.<br>
<br>
However, the other part of your reply sounds hopeful. I read draft-nichols-=
tsvwg-codel-01 and I now realise that yes, it shouldn&#39;t be too cpu inte=
nsive as the hashing into bins sounds efficient on a per-packet level.<br>

<br>
Would having multiple bin &quot;trees&quot; increase CPU usage a lot? I&#39=
;m thinking of the use case where there are 10 computers in the home, of wh=
ich one is doing 100 upload TCP sessions (bittorrent). If there was some me=
chanism that could identify a source IP address that caused most of the con=
gestion and put them in a separate bin &quot;tree&quot; (basically each sou=
rce IP would get its own set of bins, up to a maximum of perhaps 16 trees) =
and then these sets of bins would be emptied in a round-robin fashion (MDRR=
 perhaps?). Or perhaps there would just be a &quot;high volume speaker&quot=
; tree and a &quot;low volume speaker&quot; tree, and it would be enough to=
 just MDRR between these two trees. I realise we&#39;re now into &quot;flow=
&quot; territory which is exactly what Codel doesn&#39;t need to bother wit=
h currently, but just checking...<br>

<br>
I saw in ICCRG that some testing was done with LEDBAT which I would imagine=
 would help for the bittorrent case, but what about trying to achieve some =
of that without needing LEDBAT by using the above technique?<div class=3D"H=
OEnZb">
<div class=3D"h5"><br>
<br>
-- <br>
Mikael Abrahamsson =A0 =A0email: <a href=3D"mailto:swmike@swm.pp.se" target=
=3D"_blank">swmike@swm.pp.se</a><br>
</div></div></blockquote></div><br></div>

--f46d040715332ad92904d7e2a279--

From Michael.Tuexen@lurchi.franken.de  Thu Mar 14 10:09:46 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB23A11E8162 for <tsvwg@ietfa.amsl.com>; Thu, 14 Mar 2013 10:09:46 -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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mW8wGZscqpEa for <tsvwg@ietfa.amsl.com>; Thu, 14 Mar 2013 10:09:46 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id DA91E11E815B for <tsvwg@ietf.org>; Thu, 14 Mar 2013 10:09:45 -0700 (PDT)
Received: from [IPv6:2001:df8::8:e80a:256d:1d51:5a63] (unknown [IPv6:2001:df8:0:8:e80a:256d:1d51:5a63]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 60F151C0C0692; Thu, 14 Mar 2013 18:09:43 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <513E4053.3090409@erg.abdn.ac.uk>
Date: Thu, 14 Mar 2013 13:09:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE6839DE-14DC-4CAC-83BF-53E2E196BB8E@lurchi.franken.de>
References: <513E4053.3090409@erg.abdn.ac.uk>
To: gorry@erg.abdn.ac.uk
X-Mailer: Apple Mail (2.1283)
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Comment on security considerations of draft-ietf-tsvwg-sctp-sack-immediately
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 17:09:46 -0000

On Mar 11, 2013, at 4:36 PM, Gorry Fairhurst wrote:

> Michael,
>=20
> Is there  potential extra remote processing/capacity of sending =
segments with the I-bit or not?
>=20
> (Am I correct in thinking that there is actually little extra work =
that can be forced on a receiver using this bit?)
>=20
> It may be worth explaining why this is an issue or non-issue in the =
security considerations. If we do this it may be worth noting this, this =
may be better than assuming reviewers are familiar with sctp.
Hi Gorry,

what about adding:
It should be noted that an malicious sender can force its peer to send
packets containing SACK chunks for each received packet containing DATA =
chunks instead
of every other. However, every receiver has to be able to do this =
anyway.
It might be configured to do so or has to do this because of packet loss =
or reordering in the network.

Best regards
Michael
>=20
> Gorry
>=20


From Michael.Tuexen@lurchi.franken.de  Thu Mar 14 12:36:12 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6084F11E81D6 for <tsvwg@ietfa.amsl.com>; Thu, 14 Mar 2013 12:36:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ScP01zkoXam for <tsvwg@ietfa.amsl.com>; Thu, 14 Mar 2013 12:36:11 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id D36EE11E8166 for <tsvwg@ietf.org>; Thu, 14 Mar 2013 12:36:10 -0700 (PDT)
Received: from dhcp-9228.meeting.ietf.org (dhcp-9228.meeting.ietf.org [130.129.10.40]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 9835A1C0C0692; Thu, 14 Mar 2013 20:36:03 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <51409D02.3080301@erg.abdn.ac.uk>
Date: Thu, 14 Mar 2013 15:36:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F67163E-C91C-4037-AC09-428BB69B840F@lurchi.franken.de>
References: <51409D02.3080301@erg.abdn.ac.uk>
To: gorry@erg.abdn.ac.uk
X-Mailer: Apple Mail (2.1283)
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP SACK-I detailed comments
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 19:36:12 -0000

On Mar 13, 2013, at 11:36 AM, Gorry Fairhurst wrote:

> I've done a fairly detailed read of the above draft, and have some =
specific comments that I'd like to submit as an individual as we head =
towards WGLC.
Hi Gorry,

thank you vert much for the detailed comments. I hope they are addressed =
by the next revision.
See my comments in-line. Please let me know if they address your =
comments. They have been include
in rev-01.

Best regards
Michael
>=20
> Gorry
> (as an individual)
>=20
> ---
>=20
> Abstract
> - The abstract will be read by people who do not read any other part =
of the document. I think the current abstract is terse. It doesn't say =
some things which I think it should. Missing is a statement that says =
this defines a new chunk flag, called the I-bit, that can be set by the =
SCTP stack or by an application.
OK, the new abstract reads:

<t>This document defines a method for the sender of a DATA chunk
to indicate that the corresponding SACK chunk should be sent
back immediately and not be delayed.
It is done by specifying a bit in the DATA chunk header, called the =
I-bit,
which can get set either by the SCTP implementation or by the =
application
using an SCTP stack.</t>
>=20
> Section 1
>  "According to [RFC4960] the receiver of a DATA chunk should use
>   delayed SACKs."
> - I think it is important to say why this is normally the right thing =
to do - e.g. this remains the normal case.
The text will read:
<t>According to <xref target=3D'RFC4960'/> the receiver of a DATA
chunk should use delayed SACKs. This delaying is completely controlled =
by
the receiver of the DATA chunk and remains the to be the default =
behavior.</t>
>=20
>  "In specific situations the delaying of SACKs results in reduced
>   performance of the protocol"
> - A separate subsection on examples of usage, would be really useful =
(see note on section 4.1), You could then (forward) refer to this here.
OK, I moved it to a separate section.
>=20
> Section 4.1
>  "Reasons for setting the I-bit include but are not limited to the
>   following:"
> - Insert commas around /but not limited/?
I inserted commas around /but not limited to/
>=20
> I think the set of examples provided in 4.1 are really important to =
publishing the spec. However, the current examples are really terse. =
Although they seem good examples, the motivation for using the I-but is =
not clear.
>=20
>  "o  The application requests to set the I-bit of the last DATA chunk
>      of a user message when providing the user message to the SCTP
>      implementation (see Section 6)."
> - What is the benefit?
>=20
>  "o  The sender is in the SHUTDOWN-PENDING state."
> - Is this that the immediate SACK can then expedite the shutdown of a =
stream?
>=20
>  "o  The sending of a DATA chunk fills the congestion or receiver
>      window."
> - An immediate SACK can then allow the sender to transmit the missing =
chunk that will release the congestion/receiver window to send new data?
>=20
> - I think this it is confusing that we have two lists, one in the =
second part of the introduction, and one in section 4.1. I'd suggest it =
may be useful to have one subsection in the introduction to do this.
OK. I have a section which describes the use-cases and refer in the list =
to this section for the benefits.
>=20
> - To me, the important aspect that should have been evident in 4.1 was =
that there are two use-cases, one when the I-bit is set by the stack as =
an internal transport function, and one as an application-triggered =
function via the API in section 6.
You are right. I split the new use cases section into two subsections: =
application level triggered
and stack level triggered.
>=20
> Section 4.2
>  "On reception of an SCTP packet containing a DATA chunk with the =
I-bit
>   set, the receiver SHOULD NOT delay the sending of the corresponding
>   SACK chunk and SHOULD send it back immediately."
>=20
> - This contains two RFC 2119 requirements. I think the two are the =
same, and suggest it is better to have only one. One way to resolve this =
would be to make the second /SHOULD/ read /should/.
Why not use

<t>On reception of an SCTP packet containing a DATA chunk with the I-bit =
set,
the receiver SHOULD NOT delay the sending of the corresponding SACK =
chunk
and send it back immediately.</t>

>=20
> Section 6
> - It would perhaps avoid ambiguity to say at the very start that the =
API allows the I-bit to be set for any specific data chunk.
Not for any specific data chunk via the API, because the upper layer has =
no control on the
data chunks. It only provides user messages.

So what about starting with:

<t>A socket API implementation based on <xref target=3D'RFC6458'/>
is extended to allow the application to set the I-bit of the last DATA
chunk for each provided user message.
>=20
>  "or the
>   sinfo_flags field of the struct sctp_sndrcvinfo structure, which is
>   deprecated."
> - I think the "or" is confusing, since the second part is deprecated. =
Could we make this a separate statement, by replacing the "or" by a stop =
and starting a new sentence with /The/.
And continuing with:
This can be done by by setting a flag called SCTP_SACK_IMMEDIATELY
in the snd_flags field of the struct sctp_sndinfo structure when using
sctp_sendv() or sendmsg().
If the deprecated struct sctp_sndrcvinfo structure is used instead
when calling sctp_send(), sctp_sendx(), or sendmsg(), the =
SCTP_SACK_IMMEDIATELY
flags can be set in the sinfo_flags field. When using the deprecated =
function
sctp_sendmsg() the SCTP_SACK_IMMEDIATELY flag can be in the flags =
parameter.</t>
>=20
> Section 8 (recently noted)
> - Section 4.1 implies this need to discuss cost of processing the =
I-bit when in 4.1 it says: "Please note that it is
>   irrelevant to the receiver why the sender has set the I-bit."
I added (as indicated in your other e-mail):
It should be noted that an malicious sender can force its peer to send =
packets
containing SACK chunks for each received packet containing DATA chunks =
instead
of every other. However, every receiver has to be able to do this =
anyway.
It might be configured to do so or has to do this because of packet loss =
or
reordering in the network.</t>

>=20
> [RFC6525]
> - This seems like an informative reference?
Done.
>=20
>=20


From internet-drafts@ietf.org  Thu Mar 14 12:36:14 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE7A11E81E3; Thu, 14 Mar 2013 12:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pcx05A40k4pO; Thu, 14 Mar 2013 12:36:13 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D862411E81D7; Thu, 14 Mar 2013 12:36:13 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.43
Message-ID: <20130314193613.22582.43311.idtracker@ietfa.amsl.com>
Date: Thu, 14 Mar 2013 12:36:13 -0700
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-sack-immediately-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 19:36:14 -0000

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

	Title           : SACK-IMMEDIATELY Extension for the Stream Control Transm=
ission Protocol
	Author(s)       : Michael Tuexen
                          Irene Ruengeler
                          Randall R. Stewart
	Filename        : draft-ietf-tsvwg-sctp-sack-immediately-01.txt
	Pages           : 7
	Date            : 2013-03-14

Abstract:
   This document defines a method for the sender of a DATA chunk to
   indicate that the corresponding SACK chunk should be sent back
   immediately and not be delayed.  It is done by specifying a bit in
   the DATA chunk header, called the I-bit, which can get set either by
   the SCTP implementation or by the application using an SCTP stack.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-sack-immediately-01


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


From touch@isi.edu  Thu Mar 14 13:12:15 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78B0611E820E for <tsvwg@ietfa.amsl.com>; Thu, 14 Mar 2013 13:12:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u1aHDKwFEYnN for <tsvwg@ietfa.amsl.com>; Thu, 14 Mar 2013 13:12:15 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id F170011E8133 for <tsvwg@ietf.org>; Thu, 14 Mar 2013 13:12:14 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r2EKC91u012678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 14 Mar 2013 13:12:09 -0700 (PDT)
Message-ID: <51422F18.7000100@isi.edu>
Date: Thu, 14 Mar 2013 13:12:08 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
References: <51408BF4.7090304@cisco.com> <D4D47BCFFE5A004F95D707546AC0D7E91F7B2E12@SACEXCMBX01-PRD.hq.netapp.com>
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F7B2E12@SACEXCMBX01-PRD.hq.netapp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 20:12:15 -0000

FWIW, not all bufferbloat happens in the routers.

The original example that JimG discussed with me at the start of this 
crusade ended up being poor scheduling and socket configuration inside a 
single OS. These aren't addressed by AQM AFAICT.
Joe

On 3/13/2013 9:15 AM, Eggert, Lars wrote:
> Hi,
>
> I recently did some very preliminary measurements using some lab equipment and Rick Jones' bloat.sh script. In their default configuration and with the latest available firmware, here is what I saw:
>
> Cisco Catalyst 2960: at 100Mb/s, 80ms under load
> Cisco Catalyst 3750: at 1Gb/s, 8ms under load
> Cisco Nexus 5010 & 5548: at 1Gb/s, 8ms under load
>
> (I haven't measured the Nexus switches at 10Gb/s, because the single netperf instance used by Rick Jones' bloat.sh script can only pump out 5G/s on one core. Once Toke's netperf-wrapper works on FreeBSD, I'll re-test using that.)
>
> Lars
>

From swmike@swm.pp.se  Thu Mar 14 20:40:35 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3071B11E81F4 for <tsvwg@ietfa.amsl.com>; Thu, 14 Mar 2013 20:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gF6o+pqCL6UV for <tsvwg@ietfa.amsl.com>; Thu, 14 Mar 2013 20:40:34 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 9520711E80DC for <tsvwg@ietf.org>; Thu, 14 Mar 2013 20:40:32 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id DD8BF9C; Fri, 15 Mar 2013 04:40:31 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D5F999A; Fri, 15 Mar 2013 04:40:31 +0100 (CET)
Date: Fri, 15 Mar 2013 04:40:31 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <51422F18.7000100@isi.edu>
Message-ID: <alpine.DEB.2.00.1303150438030.1887@uplift.swm.pp.se>
References: <51408BF4.7090304@cisco.com> <D4D47BCFFE5A004F95D707546AC0D7E91F7B2E12@SACEXCMBX01-PRD.hq.netapp.com> <51422F18.7000100@isi.edu>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2013 03:40:35 -0000

On Thu, 14 Mar 2013, Joe Touch wrote:

> The original example that JimG discussed with me at the start of this crusade 
> ended up being poor scheduling and socket configuration inside a single OS. 
> These aren't addressed by AQM AFAICT.

I was under the impression that for instance Linux, would use the same AQM 
code when putting packets from a local TCP socket onto a local ethernet 
interface, as if this packet came in from another interface and was being 
routed out the same interface as the TCP packet. AQM should be used 
regardless whether the packet was locally sourced or not.

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

From david.black@emc.com  Fri Mar 15 05:35:58 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB5C21F8F40 for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 05:35:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0PeBKBRu+xY1 for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 05:35:57 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id C2CE321F8F18 for <tsvwg@ietf.org>; Fri, 15 Mar 2013 05:35:57 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2FCZt2m029745 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Fri, 15 Mar 2013 08:35:55 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Fri, 15 Mar 2013 08:35:42 -0400
Received: from mxhub29.corp.emc.com (mxhub29.corp.emc.com [128.222.70.169]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2FCZgJB026144 for <tsvwg@ietf.org>; Fri, 15 Mar 2013 08:35:42 -0400
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub29.corp.emc.com ([128.222.70.169]) with mapi; Fri, 15 Mar 2013 08:35:41 -0400
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Date: Fri, 15 Mar 2013 08:35:40 -0400
Thread-Topic: RFC 4594 update: Audio class - consensus check
Thread-Index: Ac4heZqhCV4U8t4nS1CkxiPdzdLCfA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2013 12:35:58 -0000

The discussion of the Audio service class in the RFC 4594 update
draft in the tsvwg meeting yesterday reached a couple of initial
conclusions that need to be checked on the list:

(1) The class is being renamed from "Telephony" to "Audio", in part
because "Telephony" is interpreted to include video in some contexts
and that's not intended here.  There have also been some slight
changes/generalizations to the description.

(2) The newly-standardized Voice-Admit PHB is being added to the
Audio class.

In the absence of objection on the list, these directions will be
confirmed as the rough consensus of the tsvwg WG - please comment.

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 flefauch@cisco.com  Fri Mar 15 07:16:21 2013
Return-Path: <flefauch@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4BFE21F8738 for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 07:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SuLRBD+u50mL for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 07:16:21 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 2687521F8735 for <tsvwg@ietf.org>; Fri, 15 Mar 2013 07:16:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=117; q=dns/txt; s=iport; t=1363356981; x=1364566581; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=N/+GvKkc6bWEE2FvOtR+OMD4lWopsqbh3j8Sie/3Rrs=; b=a0paJmCiyPhISgP9x+VhUI6HWN4n4mFdIgDFuCWEv4XNMaPXA3by1m6R 5XIHl+fMFVW9QIjWkoUvbDIc+gGyah3gdhPPj0/eqoQMeP8G/KYiRAAxU 0zO7zL6Zzq8ntLruBJT3l67iFxvw+wNeHU1EDylQIUfL7D8VcrAQP36HS 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAFssQ1GtJXHB/2dsb2JhbABDxRaBZRZ0gisBAQR5EAIBCCIkMiUBAQQODYgMwxSOZDEHgl9hA4g/nx6DCoIo
X-IronPort-AV: E=Sophos;i="4.84,850,1355097600"; d="scan'208";a="184896101"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-9.cisco.com with ESMTP; 15 Mar 2013 14:16:20 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r2FEGKSp020567 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 15 Mar 2013 14:16:20 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Fri, 15 Mar 2013 09:16:20 -0500
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Black, David" <david.black@emc.com>
Thread-Topic: [tsvwg] RFC 4594 update: Audio class - consensus check
Thread-Index: Ac4heZqhCV4U8t4nS1CkxiPdzdLCfAAN/fOA
Date: Fri, 15 Mar 2013 14:16:20 +0000
Message-ID: <FC236DA6F2DA77449EF2D02DF4471A8D3A6748@xmb-rcd-x10.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.239.53]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <096C19A523711949833F890A26C56571@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2013 14:16:21 -0000

> (2) The newly-standardized Voice-Admit PHB is being added to the
> Audio class.

I support that.

Francois

From jgunn6@csc.com  Fri Mar 15 07:29:10 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2863921F859C; Fri, 15 Mar 2013 07:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.541
X-Spam-Level: 
X-Spam-Status: No, score=-6.541 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y+Y4fCUPCX9u; Fri, 15 Mar 2013 07:29:09 -0700 (PDT)
Received: from mail86.messagelabs.com (mail86.messagelabs.com [216.82.242.179]) by ietfa.amsl.com (Postfix) with ESMTP id B6F9D21F853A; Fri, 15 Mar 2013 07:29:06 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-5.tower-86.messagelabs.com!1363357573!33733683!1
X-Originating-IP: [20.137.2.87]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24484 invoked from network); 15 Mar 2013 14:26:14 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-5.tower-86.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Mar 2013 14:26:14 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta101.csc.com (8.13.8/8.13.8) with ESMTP id r2FEPFc7010668; Fri, 15 Mar 2013 10:25:15 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
MIME-Version: 1.0
X-KeepSent: A883E592:AC23E1EE-85257B2F:004F39A7; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OFA883E592.AC23E1EE-ON85257B2F.004F39A7-85257B2F.004F4FD0@csc.com>
Date: Fri, 15 Mar 2013 10:26:10 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 03/15/2013 10:20:46 AM, Serialize complete at 03/15/2013 10:20:46 AM
Content-Type: multipart/alternative; boundary="=_alternative 004F4F4B85257B2F_="
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, tsvwg-bounces@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2013 14:29:10 -0000

This is a multipart message in MIME format.
--=_alternative 004F4F4B85257B2F_=
Content-Type: text/plain; charset="US-ASCII"

I support it. (and I was in the room)

Janet

This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.



From:   "Black, David" <david.black@emc.com>
To:     "tsvwg@ietf.org" <tsvwg@ietf.org>
Date:   03/15/2013 08:36 AM
Subject:        [tsvwg] RFC 4594 update: Audio class - consensus check
Sent by:        tsvwg-bounces@ietf.org



The discussion of the Audio service class in the RFC 4594 update
draft in the tsvwg meeting yesterday reached a couple of initial
conclusions that need to be checked on the list:

(1) The class is being renamed from "Telephony" to "Audio", in part
because "Telephony" is interpreted to include video in some contexts
and that's not intended here.  There have also been some slight
changes/generalizations to the description.

(2) The newly-standardized Voice-Admit PHB is being added to the
Audio class.

In the absence of objection on the list, these directions will be
confirmed as the rough consensus of the tsvwg WG - please comment.

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




--=_alternative 004F4F4B85257B2F_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">I support it. (and I was in the room)</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
<br>
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">&quot;Black, David&quot;
&lt;david.black@emc.com&gt;</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">&quot;tsvwg@ietf.org&quot;
&lt;tsvwg@ietf.org&gt;</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">03/15/2013 08:36 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject: &nbsp; &nbsp;
&nbsp; &nbsp;</font><font size=1 face="sans-serif">[tsvwg] RFC
4594 update: Audio class - consensus check</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by: &nbsp; &nbsp;
&nbsp; &nbsp;</font><font size=1 face="sans-serif">tsvwg-bounces@ietf.org</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>The discussion of the Audio service class in the RFC
4594 update<br>
draft in the tsvwg meeting yesterday reached a couple of initial<br>
conclusions that need to be checked on the list:<br>
<br>
(1) The class is being renamed from &quot;Telephony&quot; to &quot;Audio&quot;,
in part<br>
because &quot;Telephony&quot; is interpreted to include video in some contexts<br>
and that's not intended here. &nbsp;There have also been some slight<br>
changes/generalizations to the description.<br>
<br>
(2) The newly-standardized Voice-Admit PHB is being added to the<br>
Audio class.<br>
<br>
In the absence of objection on the list, these directions will be<br>
confirmed as the rough consensus of the tsvwg WG - please comment.<br>
<br>
Thanks,<br>
--David<br>
----------------------------------------------------<br>
David L. Black, Distinguished Engineer<br>
EMC Corporation, 176 South St., Hopkinton, MA&nbsp; 01748<br>
+1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
FAX: +1 (508) 293-7786<br>
david.black@emc.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile: +1
(978) 394-7754<br>
----------------------------------------------------<br>
<br>
<br>
</font></tt>
<br>
--=_alternative 004F4F4B85257B2F_=--

From gorry@erg.abdn.ac.uk  Fri Mar 15 09:45:10 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6773B21F8887 for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 09:45:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PE9vzlTvlmsi for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 09:45:09 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id CCA1C21F8881 for <tsvwg@ietf.org>; Fri, 15 Mar 2013 09:45:08 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id A59242B4438 for <tsvwg@ietf.org>; Fri, 15 Mar 2013 16:45:07 +0000 (GMT)
Received: from 2001:df8:0:16:5ab0:35ff:fe7b:b828 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Fri, 15 Mar 2013 16:45:07 -0000
Message-ID: <0d3beac39a624d66a6ee6cbd708493b5.squirrel@www.erg.abdn.ac.uk>
Date: Fri, 15 Mar 2013 16:45:07 -0000
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: [tsvwg] Some comments on draft-ietf-tsvwg-sctp-sack-immediately-01.txt (Implementation requirements)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2013 16:45:10 -0000

This could look like a protocol update to RFC 4960.
- It seems to change a field in the receiver behaviour, I'm not sure
whether this should be seen as an update to the base spec or not, have you
thought about this?
- If it does, maybe you could add: updates="RFC 4960 (if published)".

There is  also one detail I think should be clear:
- I understand that it says this is backwards compatible.
- I therefore read this as the receiver side of this logic is optional, if
so, saying this is a backwards-compatible optional extension in the
abstract is good (no RFC 2119 language in the abstract).

Best wishes,

Gorry


From david.black@emc.com  Fri Mar 15 11:29:21 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB23721F84E8 for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 11:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xvPJ9-GFPq6O for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 11:29:21 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id CAA2921F84CE for <tsvwg@ietf.org>; Fri, 15 Mar 2013 11:29:20 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2FITEPP005102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Fri, 15 Mar 2013 14:29:18 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Fri, 15 Mar 2013 14:29:02 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2FIT1fG013500 for <tsvwg@ietf.org>; Fri, 15 Mar 2013 14:29:01 -0400
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Fri, 15 Mar 2013 14:29:01 -0400
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Date: Fri, 15 Mar 2013 14:29:00 -0400
Thread-Topic: RFC 4594 update: Hi-Res video class - open issue
Thread-Index: Ac4hmGOfPp6rctsMRaiGwuexfYqzKA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71290FA94A0@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [tsvwg] RFC 4594 update: Hi-Res video class - open issue
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2013 18:29:21 -0000

This is about the other RFC 4594 update topic discussed yesterday
in Orlando.

The RFC 4594 update draft proposes to introduce a new diffserv
class for (high-resolution) telepresence video.  That new class
would be split out of the Multimedia Conferencing class.  FWIW,
that Multimedia Conferencing is also the source out off which the
new Video (Conferencing) class for interactive video will be split
(the WG already has rough consensus on the need for this new
Video class).

Here's the relevant slide content from Orlando (slide 1 from the
slide deck on Diffserv Service Class Questions):

	"Hi-Res" NEW=20
		- For video and audio/video conferencing
		- Created for policy-based treatment different than "Video"

	Question #1: Is this new class needed?

The sense of the room was not clearly "Yes" - for that reason,
questions #2 and #3 in the slides were not asked in Orlando.
I heard considerably more of a hum for "No" than "Yes" and a
similar level of hum for "Not sure" as for "Yes".

Please comment on the need (or lack thereof) for this new class -
this decision starts from a default to not add the new class:

- The new Hi-Res class will only be added if there is good WG
	rough consensus that it is needed.
- Otherwise the class will not be added, even if the WG does not
	reach rough consensus that the new class is not needed.

Please limit discussion to the need or lack thereof for this new
Hi-Res class, and in particular please do not include the proposed
changes to CS4 and CS5 usage at this time - if the new class is to
be added, then whether to do that via changes to usage of CS4 and
CS5 will be opened up as a separate topic.

Thanks,
--David (tsvwg WG co-chair)
----------------------------------------------------
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 Michael.Tuexen@lurchi.franken.de  Fri Mar 15 12:50:43 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB2C21F88F1 for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 12:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0itBFCOHAqPt for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 12:50:40 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 1457A21F86AF for <tsvwg@ietf.org>; Fri, 15 Mar 2013 12:50:38 -0700 (PDT)
Received: from [130.129.135.39] (unknown [130.129.135.39]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id A993F1C0C0BCC; Fri, 15 Mar 2013 20:50:36 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
X-Priority: 3 (Normal)
In-Reply-To: <0d3beac39a624d66a6ee6cbd708493b5.squirrel@www.erg.abdn.ac.uk>
Date: Fri, 15 Mar 2013 15:50:35 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <3B3A4001-D28F-4CCB-B712-F64D892735C9@lurchi.franken.de>
References: <0d3beac39a624d66a6ee6cbd708493b5.squirrel@www.erg.abdn.ac.uk>
To: gorry@erg.abdn.ac.uk
X-Mailer: Apple Mail (2.1283)
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Some comments on draft-ietf-tsvwg-sctp-sack-immediately-01.txt (Implementation requirements)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2013 19:50:43 -0000

On Mar 15, 2013, at 12:45 PM, gorry@erg.abdn.ac.uk wrote:

> This could look like a protocol update to RFC 4960.
> - It seems to change a field in the receiver behaviour, I'm not sure
> whether this should be seen as an update to the base spec or not, have you
> thought about this?
> - If it does, maybe you could add: updates="RFC 4960 (if published)".
Yes, you are right. We change the behavior of the receiver. So the next
revision will contain the "RFC 4960 (if published)" text.
> 
> 
> There is  also one detail I think should be clear:
> - I understand that it says this is backwards compatible.
Correct.
> - I therefore read this as the receiver side of this logic is optional, if
> so, saying this is a backwards-compatible optional extension in the
> abstract is good (no RFC 2119 language in the abstract).
OK, I added
Since unknown flags in chunk headers are ignored by SCTP implementations,
this extension does not introduce any interoperability problems.
Does that cover it?

Thanks a lot for your comments.

Best regards
Michael
> 
> Best wishes,
> 
> Gorry
> 
> 


From touch@isi.edu  Fri Mar 15 15:44:59 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3597C21F86C1 for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 15:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YoWkKkqIIG7h for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 15:44:58 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id D2EDB1F0D05 for <tsvwg@ietf.org>; Fri, 15 Mar 2013 15:44:47 -0700 (PDT)
Received: from [204.140.155.215] ([204.140.155.215]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r2FMiCUv014038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Mar 2013 15:44:21 -0700 (PDT)
Message-ID: <5143A43E.3030901@isi.edu>
Date: Fri, 15 Mar 2013 15:44:14 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <51408BF4.7090304@cisco.com> <D4D47BCFFE5A004F95D707546AC0D7E91F7B2E12@SACEXCMBX01-PRD.hq.netapp.com> <51422F18.7000100@isi.edu> <alpine.DEB.2.00.1303150438030.1887@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1303150438030.1887@uplift.swm.pp.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2013 22:44:59 -0000

Hi, Mikael,

On 3/14/2013 8:40 PM, Mikael Abrahamsson wrote:
> On Thu, 14 Mar 2013, Joe Touch wrote:
>
>> The original example that JimG discussed with me at the start of this
>> crusade ended up being poor scheduling and socket configuration inside
>> a single OS. These aren't addressed by AQM AFAICT.
>
> I was under the impression that for instance Linux, would use the same
> AQM code when putting packets from a local TCP socket onto a local
> ethernet interface, as if this packet came in from another interface and
> was being routed out the same interface as the TCP packet. AQM should be
> used regardless whether the packet was locally sourced or not.

Sockets are between the app and the OS. If they're configured too large, 
they act like queues and add delay, except there's no AQM in a socket 
buffer - they don't have drops.

I don't know where Linux implements AQM; it might be just on the ingress 
side of the interfaces. I don't know if there are similar queues or not 
on the egress side.

Joe

From touch@isi.edu  Fri Mar 15 16:05:46 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB5611E80E3 for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 16:05:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mB-1Q6miV8Up for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2013 16:05:45 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id C23CA11E80F6 for <tsvwg@ietf.org>; Fri, 15 Mar 2013 16:05:45 -0700 (PDT)
Received: from [204.140.155.215] ([204.140.155.215]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r2FN5QLe023427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Mar 2013 16:05:34 -0700 (PDT)
Message-ID: <5143A937.3080301@isi.edu>
Date: Fri, 15 Mar 2013 16:05:27 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA94A0@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290FA94A0@MX15A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Hi-Res video class - open issue
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2013 23:05:46 -0000

Hi, David,

One general assumption I have for diffsrv classes is that they should 
describe a service, not an application.

How does this service differ from that for conferencing (i.e., roughly 
constant bitrate, lossy allowed, low latency)?

Joe

On 3/15/2013 11:29 AM, Black, David wrote:
> This is about the other RFC 4594 update topic discussed yesterday
> in Orlando.
>
> The RFC 4594 update draft proposes to introduce a new diffserv
> class for (high-resolution) telepresence video.  That new class
> would be split out of the Multimedia Conferencing class.  FWIW,
> that Multimedia Conferencing is also the source out off which the
> new Video (Conferencing) class for interactive video will be split
> (the WG already has rough consensus on the need for this new
> Video class).
>
> Here's the relevant slide content from Orlando (slide 1 from the
> slide deck on Diffserv Service Class Questions):
>
> 	"Hi-Res" NEW
> 		- For video and audio/video conferencing
> 		- Created for policy-based treatment different than "Video"
>
> 	Question #1: Is this new class needed?
>
> The sense of the room was not clearly "Yes" - for that reason,
> questions #2 and #3 in the slides were not asked in Orlando.
> I heard considerably more of a hum for "No" than "Yes" and a
> similar level of hum for "Not sure" as for "Yes".
>
> Please comment on the need (or lack thereof) for this new class -
> this decision starts from a default to not add the new class:
>
> - The new Hi-Res class will only be added if there is good WG
> 	rough consensus that it is needed.
> - Otherwise the class will not be added, even if the WG does not
> 	reach rough consensus that the new class is not needed.
>
> Please limit discussion to the need or lack thereof for this new
> Hi-Res class, and in particular please do not include the proposed
> changes to CS4 and CS5 usage at this time - if the new class is to
> be added, then whether to do that via changes to usage of CS4 and
> CS5 will be opened up as a separate topic.
>
> Thanks,
> --David (tsvwg WG co-chair)
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>

From brian.e.carpenter@gmail.com  Sat Mar 16 00:51:11 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2BBA21F8CC5 for <tsvwg@ietfa.amsl.com>; Sat, 16 Mar 2013 00:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.057
X-Spam-Level: 
X-Spam-Status: No, score=-99.057 tagged_above=-999 required=5 tests=[AWL=-0.136, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EGvBI73ZzOKB for <tsvwg@ietfa.amsl.com>; Sat, 16 Mar 2013 00:51:10 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 33D2321F8788 for <tsvwg@ietf.org>; Sat, 16 Mar 2013 00:51:09 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id hm11so1315386wib.5 for <tsvwg@ietf.org>; Sat, 16 Mar 2013 00:51:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7/O3Jhpvr7mS+8bqxdoLBuWzWvL4tIvHewvUHp6wtuc=; b=UTD1uGELs2cTW9+1Y8X24K8nsrleHBLBfWXNDnFKAlGcD0vKquwjupgbeeboJsiG6J czK2CV3dS/zo6GrSjQ6oMEo088EsjV14/UlI4wOl++SIxVK9XYEFB8wa6w2p3kVswfMr ZZWOH3BMX6htCptdJi+eRcT9eM9dcvKyj7G5CGEvjeiXCuNIGmrWfC9LjJzHrJS/IKcY TRUxtbW4+A1S3CtH+6u3nYakmVlizA53ppMHnckreL6g3IjzQv4vmBF6Ivb5vCrEf18T xjFJiGC4pgnvQAR9gvYVUXEQ2j8kR/HwN3Kk9ynL7ch3iCKQpjZGk1vzUcFLTYJlrGXB kK/w==
X-Received: by 10.194.178.9 with SMTP id cu9mr15261370wjc.39.1363420269307; Sat, 16 Mar 2013 00:51:09 -0700 (PDT)
Received: from [192.168.1.65] (host-2-101-188-149.as13285.net. [2.101.188.149]) by mx.google.com with ESMTPS id fb8sm2286261wid.1.2013.03.16.00.51.07 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 16 Mar 2013 00:51:08 -0700 (PDT)
Message-ID: <51442478.1080000@gmail.com>
Date: Sat, 16 Mar 2013 07:51:20 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA94A0@MX15A.corp.emc.com> <5143A937.3080301@isi.edu>
In-Reply-To: <5143A937.3080301@isi.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Hi-Res video class - open issue
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Mar 2013 07:51:11 -0000

On 15/03/2013 23:05, Joe Touch wrote:
> Hi, David,
> 
> One general assumption I have for diffsrv classes is that they should
> describe a service, not an application.

Not only that; they need to correspond 1:1 to a well defined PHB.

> How does this service differ from that for conferencing (i.e., roughly
> constant bitrate, lossy allowed, low latency)?

And why does it need a new PHB, or a separate set of parameters
for an existing PHB?

   Brian

> 
> Joe
> 
> On 3/15/2013 11:29 AM, Black, David wrote:
>> This is about the other RFC 4594 update topic discussed yesterday
>> in Orlando.
>>
>> The RFC 4594 update draft proposes to introduce a new diffserv
>> class for (high-resolution) telepresence video.  That new class
>> would be split out of the Multimedia Conferencing class.  FWIW,
>> that Multimedia Conferencing is also the source out off which the
>> new Video (Conferencing) class for interactive video will be split
>> (the WG already has rough consensus on the need for this new
>> Video class).
>>
>> Here's the relevant slide content from Orlando (slide 1 from the
>> slide deck on Diffserv Service Class Questions):
>>
>>     "Hi-Res" NEW
>>         - For video and audio/video conferencing
>>         - Created for policy-based treatment different than "Video"
>>
>>     Question #1: Is this new class needed?
>>
>> The sense of the room was not clearly "Yes" - for that reason,
>> questions #2 and #3 in the slides were not asked in Orlando.
>> I heard considerably more of a hum for "No" than "Yes" and a
>> similar level of hum for "Not sure" as for "Yes".
>>
>> Please comment on the need (or lack thereof) for this new class -
>> this decision starts from a default to not add the new class:
>>
>> - The new Hi-Res class will only be added if there is good WG
>>     rough consensus that it is needed.
>> - Otherwise the class will not be added, even if the WG does not
>>     reach rough consensus that the new class is not needed.
>>
>> Please limit discussion to the need or lack thereof for this new
>> Hi-Res class, and in particular please do not include the proposed
>> changes to CS4 and CS5 usage at this time - if the new class is to
>> be added, then whether to do that via changes to usage of CS4 and
>> CS5 will be opened up as a separate topic.
>>
>> Thanks,
>> --David (tsvwg WG co-chair)
>> ----------------------------------------------------
>> David L. Black, Distinguished Engineer
>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> david.black@emc.com        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>>
> 

From gorry@erg.abdn.ac.uk  Sat Mar 16 06:56:04 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2FBB21F8B85 for <tsvwg@ietfa.amsl.com>; Sat, 16 Mar 2013 06:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TL+TJsdsTiIT for <tsvwg@ietfa.amsl.com>; Sat, 16 Mar 2013 06:56:03 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 564BC21F8AD8 for <tsvwg@ietf.org>; Sat, 16 Mar 2013 06:56:03 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 276702B4360; Sat, 16 Mar 2013 13:56:02 +0000 (GMT)
Received: from 2001:df8:0:128:5ab0:35ff:fe7b:b828 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Sat, 16 Mar 2013 13:56:02 -0000
Message-ID: <d152e608e1ffd0e02547cc136a3daecd.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <3B3A4001-D28F-4CCB-B712-F64D892735C9@lurchi.franken.de>
References: <0d3beac39a624d66a6ee6cbd708493b5.squirrel@www.erg.abdn.ac.uk> <3B3A4001-D28F-4CCB-B712-F64D892735C9@lurchi.franken.de>
Date: Sat, 16 Mar 2013 13:56:02 -0000
From: gorry@erg.abdn.ac.uk
To: "Michael Tuexen" <Michael.Tuexen@lurchi.franken.de>
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: gorry@erg.abdn.ac.uk, tsvwg@ietf.org
Subject: Re: [tsvwg] Some comments on draft-ietf-tsvwg-sctp-sack-immediately-01.txt (Implementation requirements)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Mar 2013 13:56:04 -0000

Seems good to me.

Please publish a revised ID that includes this and any minor edits that
have been suggested to the authors.

I think this may then be ready for a WGLC to see if the WG has further
comments.

Gorry
(TSVWG Co-Chair)

> On Mar 15, 2013, at 12:45 PM, gorry@erg.abdn.ac.uk wrote:
>
>> This could look like a protocol update to RFC 4960.
>> - It seems to change a field in the receiver behaviour, I'm not sure
>> whether this should be seen as an update to the base spec or not, have
>> you
>> thought about this?
>> - If it does, maybe you could add: updates="RFC 4960 (if published)".
> Yes, you are right. We change the behavior of the receiver. So the next
> revision will contain the "RFC 4960 (if published)" text.
>>
>>
>> There is  also one detail I think should be clear:
>> - I understand that it says this is backwards compatible.
> Correct.
>> - I therefore read this as the receiver side of this logic is optional,
>> if
>> so, saying this is a backwards-compatible optional extension in the
>> abstract is good (no RFC 2119 language in the abstract).
> OK, I added
> Since unknown flags in chunk headers are ignored by SCTP implementations,
> this extension does not introduce any interoperability problems.
> Does that cover it?
>
> Thanks a lot for your comments.
>
> Best regards
> Michael
>>
>> Best wishes,
>>
>> Gorry
>>
>>
>



From andrewmcgr@gmail.com  Sat Mar 16 09:12:11 2013
Return-Path: <andrewmcgr@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EBC221F8865 for <tsvwg@ietfa.amsl.com>; Sat, 16 Mar 2013 09:12:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sdABuTV2Xqst for <tsvwg@ietfa.amsl.com>; Sat, 16 Mar 2013 09:12:10 -0700 (PDT)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 010E521F84E6 for <tsvwg@ietf.org>; Sat, 16 Mar 2013 09:12:09 -0700 (PDT)
Received: by mail-la0-f52.google.com with SMTP id fs12so4665960lab.25 for <tsvwg@ietf.org>; Sat, 16 Mar 2013 09:12:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=X9MOG8zFpXWnZgnzY9kvec004bFaFmZIaWB0p+hIkU0=; b=A4UDWFu4+3IMAWLQufl0UgkhH4LeqlHDVfoC+X4jgr2YIiWZwQcdzWvHOlqdFevshN AKLCcbZQOJISbeaAuWBGmHrTi8/a7NZGiioxEKiiNhXBnqPFrSSokILhW1bgqFKX3A2l MQhn74OnCNhTjLvxai8Al/8hL892PYMnGpqSMdpDYvGpPuLT87HlzrfzRzptHVXJ0gY0 J3fOYP38WYgiJ6xSlkIOYFPScbNVpuAM15F79OjE6Q0q6KZBd22imRuQdvo8b8SNfkf4 H/0JeCCF1bzZf7HuJK6VmNCn9linrV2o9wlkDvkt4sJtLjDjUoa/3YLBiEZBvUSJfBq/ ZmaQ==
MIME-Version: 1.0
X-Received: by 10.152.47.242 with SMTP id g18mr9112595lan.42.1363450328774; Sat, 16 Mar 2013 09:12:08 -0700 (PDT)
Received: by 10.112.21.7 with HTTP; Sat, 16 Mar 2013 09:12:08 -0700 (PDT)
Received: by 10.112.21.7 with HTTP; Sat, 16 Mar 2013 09:12:08 -0700 (PDT)
In-Reply-To: <5143A43E.3030901@isi.edu>
References: <51408BF4.7090304@cisco.com> <D4D47BCFFE5A004F95D707546AC0D7E91F7B2E12@SACEXCMBX01-PRD.hq.netapp.com> <51422F18.7000100@isi.edu> <alpine.DEB.2.00.1303150438030.1887@uplift.swm.pp.se> <5143A43E.3030901@isi.edu>
Date: Sat, 16 Mar 2013 12:12:08 -0400
Message-ID: <CAA_e5Z4_UXBqBAS=zMpUwNfcAvxrXjRsxkctJaTAA1RUCwofrQ@mail.gmail.com>
From: Andrew McGregor <andrewmcgr@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=bcaec554042284413204d80d049d
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Mar 2013 16:12:11 -0000

--bcaec554042284413204d80d049d
Content-Type: text/plain; charset=ISO-8859-1

Linux has very comprehensive AQM on most possible paths though the system.
Certain device drivers are problematic, as is the WiFi stack. AQM is
available on egress as well as ingress and on the forwarding path. As yet,
AQM is not the default behaviour, but there are people working on that.
On 15 Mar 2013 18:45, "Joe Touch" <touch@isi.edu> wrote:

> Hi, Mikael,
>
> On 3/14/2013 8:40 PM, Mikael Abrahamsson wrote:
>
>> On Thu, 14 Mar 2013, Joe Touch wrote:
>>
>>  The original example that JimG discussed with me at the start of this
>>> crusade ended up being poor scheduling and socket configuration inside
>>> a single OS. These aren't addressed by AQM AFAICT.
>>>
>>
>> I was under the impression that for instance Linux, would use the same
>> AQM code when putting packets from a local TCP socket onto a local
>> ethernet interface, as if this packet came in from another interface and
>> was being routed out the same interface as the TCP packet. AQM should be
>> used regardless whether the packet was locally sourced or not.
>>
>
> Sockets are between the app and the OS. If they're configured too large,
> they act like queues and add delay, except there's no AQM in a socket
> buffer - they don't have drops.
>
> I don't know where Linux implements AQM; it might be just on the ingress
> side of the interfaces. I don't know if there are similar queues or not on
> the egress side.
>
> Joe
>

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

<p dir=3D"ltr">Linux has very comprehensive AQM on most possible paths thou=
gh the system. Certain device drivers are problematic, as is the WiFi stack=
. AQM is available on egress as well as ingress and on the forwarding path.=
 As yet, AQM is not the default behaviour, but there are people working on =
that. </p>

<div class=3D"gmail_quote">On 15 Mar 2013 18:45, &quot;Joe Touch&quot; &lt;=
<a href=3D"mailto:touch@isi.edu">touch@isi.edu</a>&gt; wrote:<br type=3D"at=
tribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">
Hi, Mikael,<br>
<br>
On 3/14/2013 8:40 PM, Mikael Abrahamsson wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Thu, 14 Mar 2013, Joe Touch wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The original example that JimG discussed with me at the start of this<br>
crusade ended up being poor scheduling and socket configuration inside<br>
a single OS. These aren&#39;t addressed by AQM AFAICT.<br>
</blockquote>
<br>
I was under the impression that for instance Linux, would use the same<br>
AQM code when putting packets from a local TCP socket onto a local<br>
ethernet interface, as if this packet came in from another interface and<br=
>
was being routed out the same interface as the TCP packet. AQM should be<br=
>
used regardless whether the packet was locally sourced or not.<br>
</blockquote>
<br>
Sockets are between the app and the OS. If they&#39;re configured too large=
, they act like queues and add delay, except there&#39;s no AQM in a socket=
 buffer - they don&#39;t have drops.<br>
<br>
I don&#39;t know where Linux implements AQM; it might be just on the ingres=
s side of the interfaces. I don&#39;t know if there are similar queues or n=
ot on the egress side.<br>
<br>
Joe<br>
</blockquote></div>

--bcaec554042284413204d80d049d--

From internet-drafts@ietf.org  Sat Mar 16 12:13:03 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 756F521F8861; Sat, 16 Mar 2013 12:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.453
X-Spam-Level: 
X-Spam-Status: No, score=-102.453 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Boyf9nj6DdSw; Sat, 16 Mar 2013 12:13:02 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0676A21F897A; Sat, 16 Mar 2013 12:13:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.43
Message-ID: <20130316191302.20583.37948.idtracker@ietfa.amsl.com>
Date: Sat, 16 Mar 2013 12:13:02 -0700
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-sack-immediately-02.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Mar 2013 19:13:03 -0000

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

	Title           : SACK-IMMEDIATELY Extension for the Stream Control Transm=
ission Protocol
	Author(s)       : Michael Tuexen
                          Irene Ruengeler
                          Randall R. Stewart
	Filename        : draft-ietf-tsvwg-sctp-sack-immediately-02.txt
	Pages           : 7
	Date            : 2013-03-16

Abstract:
   This document updates RFC 4960 by defining a method for the sender of
   a DATA chunk to indicate that the corresponding SACK chunk should be
   sent back immediately and not be delayed.  It is done by specifying a
   bit in the DATA chunk header, called the I-bit, which can get set
   either by the SCTP implementation or by the application using an SCTP
   stack.  Since unknown flags in chunk headers are ignored by SCTP
   implementations, this extension does not introduce any
   interoperability problems.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-sack-immediately-02


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


From Michael.Tuexen@lurchi.franken.de  Sat Mar 16 12:19:22 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A591121F887F for <tsvwg@ietfa.amsl.com>; Sat, 16 Mar 2013 12:19:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QPTGSxN92gD for <tsvwg@ietfa.amsl.com>; Sat, 16 Mar 2013 12:19:22 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id D419321F888E for <tsvwg@ietf.org>; Sat, 16 Mar 2013 12:19:21 -0700 (PDT)
Received: from [192.168.1.101] (p508F91D4.dip.t-dialin.net [80.143.145.212]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 6490E1C0C0BD6; Sat, 16 Mar 2013 20:19:19 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
X-Priority: 3 (Normal)
In-Reply-To: <d152e608e1ffd0e02547cc136a3daecd.squirrel@www.erg.abdn.ac.uk>
Date: Sat, 16 Mar 2013 20:19:18 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <CB7FA722-86AC-4FCB-B6E6-6719CB07D92B@lurchi.franken.de>
References: <0d3beac39a624d66a6ee6cbd708493b5.squirrel@www.erg.abdn.ac.uk> <3B3A4001-D28F-4CCB-B712-F64D892735C9@lurchi.franken.de> <d152e608e1ffd0e02547cc136a3daecd.squirrel@www.erg.abdn.ac.uk>
To: gorry@erg.abdn.ac.uk
X-Mailer: Apple Mail (2.1283)
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Some comments on draft-ietf-tsvwg-sctp-sack-immediately-01.txt (Implementation requirements)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Mar 2013 19:19:22 -0000

On Mar 16, 2013, at 2:56 PM, gorry@erg.abdn.ac.uk wrote:

> Seems good to me.
> 
> Please publish a revised ID that includes this and any minor edits that
> have been suggested to the authors.
Done.
> 
> I think this may then be ready for a WGLC to see if the WG has further
> comments.
Yes, I think this is ready for WG LC.

Best regards
Michael
> 
> Gorry
> (TSVWG Co-Chair)
> 
>> On Mar 15, 2013, at 12:45 PM, gorry@erg.abdn.ac.uk wrote:
>> 
>>> This could look like a protocol update to RFC 4960.
>>> - It seems to change a field in the receiver behaviour, I'm not sure
>>> whether this should be seen as an update to the base spec or not, have
>>> you
>>> thought about this?
>>> - If it does, maybe you could add: updates="RFC 4960 (if published)".
>> Yes, you are right. We change the behavior of the receiver. So the next
>> revision will contain the "RFC 4960 (if published)" text.
>>> 
>>> 
>>> There is  also one detail I think should be clear:
>>> - I understand that it says this is backwards compatible.
>> Correct.
>>> - I therefore read this as the receiver side of this logic is optional,
>>> if
>>> so, saying this is a backwards-compatible optional extension in the
>>> abstract is good (no RFC 2119 language in the abstract).
>> OK, I added
>> Since unknown flags in chunk headers are ignored by SCTP implementations,
>> this extension does not introduce any interoperability problems.
>> Does that cover it?
>> 
>> Thanks a lot for your comments.
>> 
>> Best regards
>> Michael
>>> 
>>> Best wishes,
>>> 
>>> Gorry
>>> 
>>> 
>> 
> 
> 
> 


From touch@isi.edu  Sun Mar 17 09:44:18 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5C421F8BBC for <tsvwg@ietfa.amsl.com>; Sun, 17 Mar 2013 09:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g1u7ukEL-kJO for <tsvwg@ietfa.amsl.com>; Sun, 17 Mar 2013 09:44:17 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 7446021F8AD5 for <tsvwg@ietf.org>; Sun, 17 Mar 2013 09:44:17 -0700 (PDT)
Received: from [75.209.73.109] (109.sub-75-209-73.myvzw.com [75.209.73.109]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r2HGh7h9000637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 17 Mar 2013 09:43:22 -0700 (PDT)
Message-ID: <5145F29D.8090408@isi.edu>
Date: Sun, 17 Mar 2013 09:43:09 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Andrew McGregor <andrewmcgr@gmail.com>
References: <51408BF4.7090304@cisco.com> <D4D47BCFFE5A004F95D707546AC0D7E91F7B2E12@SACEXCMBX01-PRD.hq.netapp.com> <51422F18.7000100@isi.edu> <alpine.DEB.2.00.1303150438030.1887@uplift.swm.pp.se> <5143A43E.3030901@isi.edu> <CAA_e5Z4_UXBqBAS=zMpUwNfcAvxrXjRsxkctJaTAA1RUCwofrQ@mail.gmail.com>
In-Reply-To: <CAA_e5Z4_UXBqBAS=zMpUwNfcAvxrXjRsxkctJaTAA1RUCwofrQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Mar 2013 16:44:18 -0000

Hi, Mikael,

On 3/16/2013 9:12 AM, Andrew McGregor wrote:
> Linux has very comprehensive AQM on most possible paths though the
> system. Certain device drivers are problematic, as is the WiFi stack.
> AQM is available on egress as well as ingress and on the forwarding
> path. As yet, AQM is not the default behaviour, but there are people
> working on that.

Sockets are neither ingress packets nor egress packets. If the socket 
buffer is very large and/or the scheduling granularity to refill the 
socket is very large, then apps can experience the same high latency.

AQM isn't relevant for OS sockets. You can't drop stuff in a 
SOCK_STREAM, and you can't send "ECN" up to the app.

Even if you use backpressure to flow-control the app (and you do), a 
large socket buffer to a small egress pipe just creates a lot of app 
delay unless the app reacts to it, and most apps don't.

Joe


>
> On 15 Mar 2013 18:45, "Joe Touch" <touch@isi.edu <mailto:touch@isi.edu>>
> wrote:
>
>     Hi, Mikael,
>
>     On 3/14/2013 8:40 PM, Mikael Abrahamsson wrote:
>
>         On Thu, 14 Mar 2013, Joe Touch wrote:
>
>             The original example that JimG discussed with me at the
>             start of this
>             crusade ended up being poor scheduling and socket
>             configuration inside
>             a single OS. These aren't addressed by AQM AFAICT.
>
>
>         I was under the impression that for instance Linux, would use
>         the same
>         AQM code when putting packets from a local TCP socket onto a local
>         ethernet interface, as if this packet came in from another
>         interface and
>         was being routed out the same interface as the TCP packet. AQM
>         should be
>         used regardless whether the packet was locally sourced or not.
>
>
>     Sockets are between the app and the OS. If they're configured too
>     large, they act like queues and add delay, except there's no AQM in
>     a socket buffer - they don't have drops.
>
>     I don't know where Linux implements AQM; it might be just on the
>     ingress side of the interfaces. I don't know if there are similar
>     queues or not on the egress side.
>
>     Joe
>

From Ruediger.Geib@telekom.de  Mon Mar 18 04:56:54 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39BC621F8CF9 for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 04:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1lSNbUXNgjOr for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 04:56:53 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id 5476421F8CEC for <tsvwg@ietf.org>; Mon, 18 Mar 2013 04:56:52 -0700 (PDT)
Received: from he113443.emea1.cds.t-internal.com ([10.134.93.103]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 18 Mar 2013 12:56:18 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113443.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 18 Mar 2013 12:56:04 +0100
From: <Ruediger.Geib@telekom.de>
To: <brian.e.carpenter@gmail.com>, <touch@isi.edu>
Date: Mon, 18 Mar 2013 12:56:03 +0100
Thread-Topic: [tsvwg] RFC 4594 update: Hi-Res video class - open issue
Thread-Index: Ac4iGxROMBx8FwT9SGqeafMQzpkwzgBtEvWA
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A67EDD1@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA94A0@MX15A.corp.emc.com> <5143A937.3080301@isi.edu> <51442478.1080000@gmail.com>
In-Reply-To: <51442478.1080000@gmail.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Hi-Res video class - open issue
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2013 11:56:54 -0000

Joe, Brian,

thanks, your questions are the ones I have too.

Regards,

R=FCdiger


-----Original Message-----
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of B=
rian E Carpenter
Sent: Saturday, March 16, 2013 8:51 AM
To: Joe Touch
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Hi-Res video class - open issue

On 15/03/2013 23:05, Joe Touch wrote:
> Hi, David,
>
> One general assumption I have for diffsrv classes is that they should
> describe a service, not an application.

Not only that; they need to correspond 1:1 to a well defined PHB.

> How does this service differ from that for conferencing (i.e., roughly
> constant bitrate, lossy allowed, low latency)?

And why does it need a new PHB, or a separate set of parameters
for an existing PHB?

   Brian

>
> Joe
>
> On 3/15/2013 11:29 AM, Black, David wrote:
>> This is about the other RFC 4594 update topic discussed yesterday
>> in Orlando.
>>
>> The RFC 4594 update draft proposes to introduce a new diffserv
>> class for (high-resolution) telepresence video.  That new class
>> would be split out of the Multimedia Conferencing class.  FWIW,
>> that Multimedia Conferencing is also the source out off which the
>> new Video (Conferencing) class for interactive video will be split
>> (the WG already has rough consensus on the need for this new
>> Video class).
>>
>> Here's the relevant slide content from Orlando (slide 1 from the
>> slide deck on Diffserv Service Class Questions):
>>
>>     "Hi-Res" NEW
>>         - For video and audio/video conferencing
>>         - Created for policy-based treatment different than "Video"
>>
>>     Question #1: Is this new class needed?
>>
>> The sense of the room was not clearly "Yes" - for that reason,
>> questions #2 and #3 in the slides were not asked in Orlando.
>> I heard considerably more of a hum for "No" than "Yes" and a
>> similar level of hum for "Not sure" as for "Yes".
>>
>> Please comment on the need (or lack thereof) for this new class -
>> this decision starts from a default to not add the new class:
>>
>> - The new Hi-Res class will only be added if there is good WG
>>     rough consensus that it is needed.
>> - Otherwise the class will not be added, even if the WG does not
>>     reach rough consensus that the new class is not needed.
>>
>> Please limit discussion to the need or lack thereof for this new
>> Hi-Res class, and in particular please do not include the proposed
>> changes to CS4 and CS5 usage at this time - if the new class is to
>> be added, then whether to do that via changes to usage of CS4 and
>> CS5 will be opened up as a separate topic.
>>
>> Thanks,
>> --David (tsvwg WG co-chair)
>> ----------------------------------------------------
>> David L. Black, Distinguished Engineer
>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> david.black@emc.com        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>>
>

From Ruediger.Geib@telekom.de  Mon Mar 18 08:45:26 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCA3A21F8A56 for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 08:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WrvN8Uzd+Zrs for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 08:45:25 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id 423C521F899E for <tsvwg@ietf.org>; Mon, 18 Mar 2013 08:45:25 -0700 (PDT)
Received: from he110889.emea1.cds.t-internal.com ([10.134.92.130]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 18 Mar 2013 16:45:24 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE110889.emea1.cds.t-internal.com ([fe80::841f:f92c:15ca:8526%16]) with mapi; Mon, 18 Mar 2013 16:45:23 +0100
From: <Ruediger.Geib@telekom.de>
To: <david.black@emc.com>
Date: Mon, 18 Mar 2013 16:45:22 +0100
Thread-Topic: RFC 4594 update: Audio class - consensus check
Thread-Index: Ac4heZqhCV4U8t4nS1CkxiPdzdLCfACdN8BA
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2013 15:45:26 -0000

I don't object to broadening the name of a service class. As mentioned earl=
ier,
I don't like transport QoS classes being named close to applications. So
weak objections against (1).

Brian Carpenter didn't seem to favor (2) prior to the meeting. I personally=
 think,
classes Priority (here: audio) and Bulk Inelastic require admission control
in access networks or some kind of TE in backbone sections. So to me EF
already requires admission control and I don't think another PHB with
otherwise identical properties adds a lot of value. But well, that's my vie=
w.
Could an argument be given why Voice-Admit is required? I hope that has bee=
n
discussed during the meeting.

Regards,

R=FCdiger


-----Original Message-----
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of B=
lack, David
Sent: Friday, March 15, 2013 1:36 PM
To: tsvwg@ietf.org
Subject: [tsvwg] RFC 4594 update: Audio class - consensus check

The discussion of the Audio service class in the RFC 4594 update
draft in the tsvwg meeting yesterday reached a couple of initial
conclusions that need to be checked on the list:

(1) The class is being renamed from "Telephony" to "Audio", in part
because "Telephony" is interpreted to include video in some contexts
and that's not intended here.  There have also been some slight
changes/generalizations to the description.

(2) The newly-standardized Voice-Admit PHB is being added to the
Audio class.

In the absence of objection on the list, these directions will be
confirmed as the rough consensus of the tsvwg WG - please comment.

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



From david.black@emc.com  Mon Mar 18 09:58:18 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 048E321F8FF4 for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 09:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uVHchET1DMZq for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 09:58:10 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id E516F21F8FF9 for <tsvwg@ietf.org>; Mon, 18 Mar 2013 09:56:51 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2IGuk7f001102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Mar 2013 12:56:50 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Mon, 18 Mar 2013 12:56:25 -0400
Received: from mxhub35.corp.emc.com (mxhub35.corp.emc.com [10.254.93.83]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2IGuNZP022803; Mon, 18 Mar 2013 12:56:24 -0400
Received: from mxhub38.corp.emc.com (128.222.70.105) by mxhub35.corp.emc.com (10.254.93.83) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 18 Mar 2013 12:56:23 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub38.corp.emc.com ([128.222.70.105]) with mapi; Mon, 18 Mar 2013 12:56:24 -0400
From: "Black, David" <david.black@emc.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
Date: Mon, 18 Mar 2013 12:56:20 -0400
Thread-Topic: RFC 4594 update: Audio class - consensus check
Thread-Index: Ac4heZqhCV4U8t4nS1CkxiPdzdLCfACdN8BAAAK4xrA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293AEE04C@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2013 16:58:18 -0000

> Could an argument be given why Voice-Admit is required? I hope that has b=
een
> discussed during the meeting.

See RFC 5865, starting with its Section 1.2 .

Thanks,
--David

> -----Original Message-----
> From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]
> Sent: Monday, March 18, 2013 11:45 AM
> To: Black, David
> Cc: tsvwg@ietf.org
> Subject: RE: RFC 4594 update: Audio class - consensus check
>=20
> I don't object to broadening the name of a service class. As mentioned
> earlier,
> I don't like transport QoS classes being named close to applications. So
> weak objections against (1).
>=20
> Brian Carpenter didn't seem to favor (2) prior to the meeting. I personal=
ly
> think,
> classes Priority (here: audio) and Bulk Inelastic require admission contr=
ol
> in access networks or some kind of TE in backbone sections. So to me EF
> already requires admission control and I don't think another PHB with
> otherwise identical properties adds a lot of value. But well, that's my v=
iew.
> Could an argument be given why Voice-Admit is required? I hope that has b=
een
> discussed during the meeting.
>=20
> Regards,
>=20
> R=FCdiger
>=20
>=20
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Black, David
> Sent: Friday, March 15, 2013 1:36 PM
> To: tsvwg@ietf.org
> Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>=20
> The discussion of the Audio service class in the RFC 4594 update
> draft in the tsvwg meeting yesterday reached a couple of initial
> conclusions that need to be checked on the list:
>=20
> (1) The class is being renamed from "Telephony" to "Audio", in part
> because "Telephony" is interpreted to include video in some contexts
> and that's not intended here.  There have also been some slight
> changes/generalizations to the description.
>=20
> (2) The newly-standardized Voice-Admit PHB is being added to the
> Audio class.
>=20
> In the absence of objection on the list, these directions will be
> confirmed as the rough consensus of the tsvwg WG - please comment.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20
>=20


From rick.jones2@hp.com  Mon Mar 18 10:05:50 2013
Return-Path: <rick.jones2@hp.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7D6A21F901B for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 10:05:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BwU+OSEbBCfX for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 10:05:42 -0700 (PDT)
Received: from g4t0017.houston.hp.com (g4t0017.houston.hp.com [15.201.24.20]) by ietfa.amsl.com (Postfix) with ESMTP id A8E9D21F8F8A for <tsvwg@ietf.org>; Mon, 18 Mar 2013 10:05:07 -0700 (PDT)
Received: from g4t0009.houston.hp.com (g4t0009.houston.hp.com [16.234.32.26]) by g4t0017.houston.hp.com (Postfix) with ESMTP id 104FB3820F; Mon, 18 Mar 2013 17:05:07 +0000 (UTC)
Received: from [16.103.148.51] (tardy.usa.hp.com [16.103.148.51]) by g4t0009.houston.hp.com (Postfix) with ESMTP id A5DAFC0A7; Mon, 18 Mar 2013 17:05:06 +0000 (UTC)
Message-ID: <51474942.7050501@hp.com>
Date: Mon, 18 Mar 2013 10:05:06 -0700
From: Rick Jones <rick.jones2@hp.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
References: <51408BF4.7090304@cisco.com> <D4D47BCFFE5A004F95D707546AC0D7E91F7B2E12@SACEXCMBX01-PRD.hq.netapp.com> <51422F18.7000100@isi.edu> <alpine.DEB.2.00.1303150438030.1887@uplift.swm.pp.se> <5143A43E.3030901@isi.edu> <CAA_e5Z4_UXBqBAS=zMpUwNfcAvxrXjRsxkctJaTAA1RUCwofrQ@mail.gmail.com> <5145F29D.8090408@isi.edu>
In-Reply-To: <5145F29D.8090408@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2013 17:05:50 -0000

On 03/17/2013 09:43 AM, Joe Touch wrote:
> Hi, Mikael,
>
> On 3/16/2013 9:12 AM, Andrew McGregor wrote:
>> Linux has very comprehensive AQM on most possible paths though the
>> system. Certain device drivers are problematic, as is the WiFi stack.
>> AQM is available on egress as well as ingress and on the forwarding
>> path. As yet, AQM is not the default behaviour, but there are people
>> working on that.
>
> Sockets are neither ingress packets nor egress packets. If the socket
> buffer is very large and/or the scheduling granularity to refill the
> socket is very large, then apps can experience the same high latency.
>
> AQM isn't relevant for OS sockets. You can't drop stuff in a
> SOCK_STREAM, and you can't send "ECN" up to the app.
>
> Even if you use backpressure to flow-control the app (and you do), a
> large socket buffer to a small egress pipe just creates a lot of app
> delay unless the app reacts to it, and most apps don't.

In that case though at least, it is the application giving latency to 
itself and its large socket buffer backlog is not adding latency to 
unrelated applications.  In other words as it is the application messing 
with itself, the application is in a position to deal with it.

And Linux is not trying to hit anything SOCK_STREAM with AQM.  The AQM 
is at the handoff from IP to the drivers

rick jones

>
> Joe
>
>
>>
>> On 15 Mar 2013 18:45, "Joe Touch" <touch@isi.edu <mailto:touch@isi.edu>>
>> wrote:
>>
>>     Hi, Mikael,
>>
>>     On 3/14/2013 8:40 PM, Mikael Abrahamsson wrote:
>>
>>         On Thu, 14 Mar 2013, Joe Touch wrote:
>>
>>             The original example that JimG discussed with me at the
>>             start of this
>>             crusade ended up being poor scheduling and socket
>>             configuration inside
>>             a single OS. These aren't addressed by AQM AFAICT.
>>
>>
>>         I was under the impression that for instance Linux, would use
>>         the same
>>         AQM code when putting packets from a local TCP socket onto a
>> local
>>         ethernet interface, as if this packet came in from another
>>         interface and
>>         was being routed out the same interface as the TCP packet. AQM
>>         should be
>>         used regardless whether the packet was locally sourced or not.
>>
>>
>>     Sockets are between the app and the OS. If they're configured too
>>     large, they act like queues and add delay, except there's no AQM in
>>     a socket buffer - they don't have drops.
>>
>>     I don't know where Linux implements AQM; it might be just on the
>>     ingress side of the interfaces. I don't know if there are similar
>>     queues or not on the egress side.
>>
>>     Joe
>>


From dwing@cisco.com  Mon Mar 18 12:44:46 2013
Return-Path: <dwing@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC4EF11E80D9 for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 12:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.349
X-Spam-Level: 
X-Spam-Status: No, score=-110.349 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bLEuF7mwjuNn for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 12:44:30 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id D18D611E80AE for <tsvwg@ietf.org>; Mon, 18 Mar 2013 12:44:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2845; q=dns/txt; s=iport; t=1363635852; x=1364845452; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=EKdKYC8fnlixuwjIsKwxTANnt9vYJ1gQovmF2tS6ToY=; b=fnZVXJvsPN8xszHD4vOl7sj82qbx9Po3NIx6IV+zDc2mD5u9Xh+JiYUF bKJMfBbT5+2P5GLi/7dS2YbJGcTcWlB+FJceSxgEFgtTEsLJZS9Qqhwuz 2Bg5r/b/3uJ3idyywPeMk+GTKyqgOumX05tQ/jeaPnjpQW3vWyZJGJ2hD U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFADJtR1GrRDoI/2dsb2JhbABAAw6EecAZgVYWdIIkAQEBAwF5BQsLGC5XBhOIDgXCKI1ggQIjEAcRgk5hA4h1jWmFfYsFgktfHIEv
X-IronPort-AV: E=Sophos;i="4.84,865,1355097600"; d="scan'208";a="72837629"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 18 Mar 2013 19:44:11 +0000
Received: from [10.156.17.48] ([10.156.17.48]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2IJiBnM022233; Mon, 18 Mar 2013 19:44:11 GMT
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <5143A937.3080301@isi.edu>
Date: Mon, 18 Mar 2013 12:44:10 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <65C867E8-B8C5-4DD7-9602-FB0C2CC6A33A@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA94A0@MX15A.corp.emc.com> <5143A937.3080301@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1499)
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Hi-Res video class - open issue
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2013 19:44:47 -0000

On Mar 15, 2013, at 4:05 PM, Joe Touch <touch@isi.edu> wrote:

> Hi, David,
>=20
> One general assumption I have for diffsrv classes is that they should =
describe a service, not an application.

Agreed.

> How does this service differ from that for conferencing (i.e., roughly =
constant bitrate, lossy allowed, low latency)?

And, how will today's "high resolution" (1080i) compare with tomorrow's =
"high resolution" (4K, 8K), and more importantly, with the needs of the =
codecs used in the future and their tolerance to delay, loss, and =
jitter.

-d


> Joe
>=20
> On 3/15/2013 11:29 AM, Black, David wrote:
>> This is about the other RFC 4594 update topic discussed yesterday
>> in Orlando.
>>=20
>> The RFC 4594 update draft proposes to introduce a new diffserv
>> class for (high-resolution) telepresence video.  That new class
>> would be split out of the Multimedia Conferencing class.  FWIW,
>> that Multimedia Conferencing is also the source out off which the
>> new Video (Conferencing) class for interactive video will be split
>> (the WG already has rough consensus on the need for this new
>> Video class).
>>=20
>> Here's the relevant slide content from Orlando (slide 1 from the
>> slide deck on Diffserv Service Class Questions):
>>=20
>> 	"Hi-Res" NEW
>> 		- For video and audio/video conferencing
>> 		- Created for policy-based treatment different than =
"Video"
>>=20
>> 	Question #1: Is this new class needed?
>>=20
>> The sense of the room was not clearly "Yes" - for that reason,
>> questions #2 and #3 in the slides were not asked in Orlando.
>> I heard considerably more of a hum for "No" than "Yes" and a
>> similar level of hum for "Not sure" as for "Yes".
>>=20
>> Please comment on the need (or lack thereof) for this new class -
>> this decision starts from a default to not add the new class:
>>=20
>> - The new Hi-Res class will only be added if there is good WG
>> 	rough consensus that it is needed.
>> - Otherwise the class will not be added, even if the WG does not
>> 	reach rough consensus that the new class is not needed.
>>=20
>> Please limit discussion to the need or lack thereof for this new
>> Hi-Res class, and in particular please do not include the proposed
>> changes to CS4 and CS5 usage at this time - if the new class is to
>> be added, then whether to do that via changes to usage of CS4 and
>> CS5 will be opened up as a separate topic.
>>=20
>> Thanks,
>> --David (tsvwg WG co-chair)
>> ----------------------------------------------------
>> David L. Black, Distinguished Engineer
>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> david.black@emc.com        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>>=20


From touch@isi.edu  Mon Mar 18 13:54:48 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64D5521F9150 for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 13:54:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.832
X-Spam-Level: 
X-Spam-Status: No, score=-105.832 tagged_above=-999 required=5 tests=[AWL=0.767, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 37Zw6XXJ5eOg for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 13:54:46 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5454B21F9127 for <tsvwg@ietf.org>; Mon, 18 Mar 2013 13:54:44 -0700 (PDT)
Received: from [75.209.55.18] (18.sub-75-209-55.myvzw.com [75.209.55.18]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r2IKs9Qr029912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 18 Mar 2013 13:54:19 -0700 (PDT)
Message-ID: <51477EF4.6080201@isi.edu>
Date: Mon, 18 Mar 2013 13:54:12 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Rick Jones <rick.jones2@hp.com>
References: <51408BF4.7090304@cisco.com> <D4D47BCFFE5A004F95D707546AC0D7E91F7B2E12@SACEXCMBX01-PRD.hq.netapp.com> <51422F18.7000100@isi.edu> <alpine.DEB.2.00.1303150438030.1887@uplift.swm.pp.se> <5143A43E.3030901@isi.edu> <CAA_e5Z4_UXBqBAS=zMpUwNfcAvxrXjRsxkctJaTAA1RUCwofrQ@mail.gmail.com> <5145F29D.8090408@isi.edu> <51474942.7050501@hp.com>
In-Reply-To: <51474942.7050501@hp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2013 20:54:48 -0000

On 3/18/2013 10:05 AM, Rick Jones wrote:
> On 03/17/2013 09:43 AM, Joe Touch wrote:
>> Hi, Mikael,
>>
>> On 3/16/2013 9:12 AM, Andrew McGregor wrote:
>>> Linux has very comprehensive AQM on most possible paths though the
>>> system. Certain device drivers are problematic, as is the WiFi stack.
>>> AQM is available on egress as well as ingress and on the forwarding
>>> path. As yet, AQM is not the default behaviour, but there are people
>>> working on that.
>>
>> Sockets are neither ingress packets nor egress packets. If the socket
>> buffer is very large and/or the scheduling granularity to refill the
>> socket is very large, then apps can experience the same high latency.
>>
>> AQM isn't relevant for OS sockets. You can't drop stuff in a
>> SOCK_STREAM, and you can't send "ECN" up to the app.
>>
>> Even if you use backpressure to flow-control the app (and you do), a
>> large socket buffer to a small egress pipe just creates a lot of app
>> delay unless the app reacts to it, and most apps don't.
>
> In that case though at least, it is the application giving latency to
> itself and its large socket buffer backlog is not adding latency to
> unrelated applications.  In other words as it is the application messing
> with itself, the application is in a position to deal with it.

Depending on the scheduler, the OS, the packet sizes, and whether there 
is pre-emptive packet scheduling, a large socket buffer for one app can 
starve out another.

> And Linux is not trying to hit anything SOCK_STREAM with AQM.  The AQM
> is at the handoff from IP to the drivers

Sure, but the first example that I was told was a bad switch 
implementation turned out to be inside a single OS. An OS with a 10ms 
scheduler can't have latency that is consistently lower than 10ms when 
under load.

Joe

From touch@isi.edu  Mon Mar 18 16:56:07 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C70E21F8A71 for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 16:56:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.166
X-Spam-Level: 
X-Spam-Status: No, score=-103.166 tagged_above=-999 required=5 tests=[AWL=-0.567, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iRf4FXh0hEzI for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2013 16:56:06 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id AB3CF21F8A6F for <tsvwg@ietf.org>; Mon, 18 Mar 2013 16:56:06 -0700 (PDT)
Received: from [66.104.71.46] (206.111.226.201.ptr.us.xo.net [206.111.226.201]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r2INtS2w008960 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 18 Mar 2013 16:55:32 -0700 (PDT)
Message-ID: <5147A974.4030100@isi.edu>
Date: Mon, 18 Mar 2013 16:55:32 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Ruediger.Geib@telekom.de
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2013 23:56:07 -0000

Audio is a horrible name; the requirements for Pandora are completely 
different from Skype.

Maybe "audio interactive" (vs. audio streaming)?

Joe

On 3/18/2013 8:45 AM, Ruediger.Geib@telekom.de wrote:
> I don't object to broadening the name of a service class. As mentioned earlier,
> I don't like transport QoS classes being named close to applications. So
> weak objections against (1).
>
> Brian Carpenter didn't seem to favor (2) prior to the meeting. I personally think,
> classes Priority (here: audio) and Bulk Inelastic require admission control
> in access networks or some kind of TE in backbone sections. So to me EF
> already requires admission control and I don't think another PHB with
> otherwise identical properties adds a lot of value. But well, that's my view.
> Could an argument be given why Voice-Admit is required? I hope that has been
> discussed during the meeting.
>
> Regards,
>
> Rüdiger
>
>
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of Black, David
> Sent: Friday, March 15, 2013 1:36 PM
> To: tsvwg@ietf.org
> Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>
> The discussion of the Audio service class in the RFC 4594 update
> draft in the tsvwg meeting yesterday reached a couple of initial
> conclusions that need to be checked on the list:
>
> (1) The class is being renamed from "Telephony" to "Audio", in part
> because "Telephony" is interpreted to include video in some contexts
> and that's not intended here.  There have also been some slight
> changes/generalizations to the description.
>
> (2) The newly-standardized Voice-Admit PHB is being added to the
> Audio class.
>
> In the absence of objection on the list, these directions will be
> confirmed as the rough consensus of the tsvwg WG - please comment.
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>
>

From Ruediger.Geib@telekom.de  Tue Mar 19 00:50:16 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E39C21F85C2 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 00:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4qdh3TQ96JGd for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 00:50:15 -0700 (PDT)
Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) by ietfa.amsl.com (Postfix) with ESMTP id 83E7121F85C0 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 00:50:14 -0700 (PDT)
Received: from he113675.emea1.cds.t-internal.com ([10.134.99.28]) by tcmail91.telekom.de with ESMTP/TLS/AES128-SHA; 19 Mar 2013 08:50:12 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113675.emea1.cds.t-internal.com ([::1]) with mapi; Tue, 19 Mar 2013 08:50:12 +0100
From: <Ruediger.Geib@telekom.de>
To: <touch@isi.edu>
Date: Tue, 19 Mar 2013 08:50:11 +0100
Thread-Topic: [tsvwg] RFC 4594 update: Audio class - consensus check
Thread-Index: Ac4kNCpBFBijJQDKRmKyF582PuXsXAAQR2Ew
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F13B@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5147A974.4030100@isi.edu>
In-Reply-To: <5147A974.4030100@isi.edu>
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
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 07:50:16 -0000

There's still a possibility of decoupling class names from applications.

pro: we don't run into problems like the one described by Joe.
con: nobody can imagine what that class would be good for by just
     reading the name. Readers must be educated.

The application decoupled class name I've suggested is "Priority".

Regards,

R=FCdiger



-----Original Message-----
From: Joe Touch [mailto:touch@isi.edu]
Sent: Tuesday, March 19, 2013 12:56 AM
To: Geib, R=FCdiger
Cc: david.black@emc.com; tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check

Audio is a horrible name; the requirements for Pandora are completely
different from Skype.

Maybe "audio interactive" (vs. audio streaming)?

Joe

On 3/18/2013 8:45 AM, Ruediger.Geib@telekom.de wrote:
> I don't object to broadening the name of a service class. As mentioned ea=
rlier,
> I don't like transport QoS classes being named close to applications. So
> weak objections against (1).
>
> Brian Carpenter didn't seem to favor (2) prior to the meeting. I personal=
ly think,
> classes Priority (here: audio) and Bulk Inelastic require admission contr=
ol
> in access networks or some kind of TE in backbone sections. So to me EF
> already requires admission control and I don't think another PHB with
> otherwise identical properties adds a lot of value. But well, that's my v=
iew.
> Could an argument be given why Voice-Admit is required? I hope that has b=
een
> discussed during the meeting.
>
> Regards,
>
> R=FCdiger
>
>
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of=
 Black, David
> Sent: Friday, March 15, 2013 1:36 PM
> To: tsvwg@ietf.org
> Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>
> The discussion of the Audio service class in the RFC 4594 update
> draft in the tsvwg meeting yesterday reached a couple of initial
> conclusions that need to be checked on the list:
>
> (1) The class is being renamed from "Telephony" to "Audio", in part
> because "Telephony" is interpreted to include video in some contexts
> and that's not intended here.  There have also been some slight
> changes/generalizations to the description.
>
> (2) The newly-standardized Voice-Admit PHB is being added to the
> Audio class.
>
> In the absence of objection on the list, these directions will be
> confirmed as the rough consensus of the tsvwg WG - please comment.
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>
>

From gorry@erg.abdn.ac.uk  Tue Mar 19 02:07:29 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4794521F887F for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 02:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iRXdQ9nqy2lz for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 02:07:27 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id D398821F88F7 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 02:07:26 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 46B0A2B4265 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 09:07:25 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Tue, 19 Mar 2013 09:07:25 -0000
Message-ID: <2d70e630cca04dbbb6bfa8a2af52da77.squirrel@www.erg.abdn.ac.uk>
Date: Tue, 19 Mar 2013 09:07:25 -0000
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: [tsvwg] Draft TSVWG notes for IETF-86, Orlando.
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 09:07:29 -0000

The draft notes for the WG's meetings in Orlando have been posted to the
proceedings site:
http://www.ietf.org/proceedings/86/minutes/minutes-86-tsvwg

Thanks to this meeting's TSVWG Note-Takers:
   Enrico Marocco - Monday
   John Leslie - Additional notetaker, Monday.
   Scott Brim - Thursday

Please send any comments/corrections to the list or to me directly,

Best wishes,

Gorry
(TSVWG Co-Chair)


From touch@isi.edu  Tue Mar 19 07:07:28 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89E1221F8B75 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 07:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jX3udK0ZVlPj for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 07:07:28 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id E98E321F8A38 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 07:07:27 -0700 (PDT)
Received: from [192.168.1.96] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r2JE6MQq011706 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 19 Mar 2013 07:06:38 -0700 (PDT)
Message-ID: <514870E1.9050703@isi.edu>
Date: Tue, 19 Mar 2013 07:06:25 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Ruediger.Geib@telekom.de
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5147A974.4030100@isi.edu> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F13B@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F13B@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 14:07:29 -0000

IMO, QOS classes ought to describe differential service _to_ the user, 
whereas PHB ought to describe differential capabilities available _from_ 
the network.

Yes, a (slowly evolving and updated) mapping between typical 
applications and QOS classes is useful, as advice to users as to what to 
"ask" for from the network.

As is a much more static mapping that explains how PHBs can be utilized 
to provide the various QOS classes.

It seems odd to explain this, however - I thought this was 
well-understood in the QOS community.

Joe

On 3/19/2013 12:50 AM, Ruediger.Geib@telekom.de wrote:
> There's still a possibility of decoupling class names from applications.
>
> pro: we don't run into problems like the one described by Joe.
> con: nobody can imagine what that class would be good for by just
>       reading the name. Readers must be educated.
>
> The application decoupled class name I've suggested is "Priority".
>
> Regards,
>
> Rüdiger
>
>
>
> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, March 19, 2013 12:56 AM
> To: Geib, Rüdiger
> Cc: david.black@emc.com; tsvwg@ietf.org
> Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
>
> Audio is a horrible name; the requirements for Pandora are completely
> different from Skype.
>
> Maybe "audio interactive" (vs. audio streaming)?
>
> Joe
>
> On 3/18/2013 8:45 AM, Ruediger.Geib@telekom.de wrote:
>> I don't object to broadening the name of a service class. As mentioned earlier,
>> I don't like transport QoS classes being named close to applications. So
>> weak objections against (1).
>>
>> Brian Carpenter didn't seem to favor (2) prior to the meeting. I personally think,
>> classes Priority (here: audio) and Bulk Inelastic require admission control
>> in access networks or some kind of TE in backbone sections. So to me EF
>> already requires admission control and I don't think another PHB with
>> otherwise identical properties adds a lot of value. But well, that's my view.
>> Could an argument be given why Voice-Admit is required? I hope that has been
>> discussed during the meeting.
>>
>> Regards,
>>
>> Rüdiger
>>
>>
>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of Black, David
>> Sent: Friday, March 15, 2013 1:36 PM
>> To: tsvwg@ietf.org
>> Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>>
>> The discussion of the Audio service class in the RFC 4594 update
>> draft in the tsvwg meeting yesterday reached a couple of initial
>> conclusions that need to be checked on the list:
>>
>> (1) The class is being renamed from "Telephony" to "Audio", in part
>> because "Telephony" is interpreted to include video in some contexts
>> and that's not intended here.  There have also been some slight
>> changes/generalizations to the description.
>>
>> (2) The newly-standardized Voice-Admit PHB is being added to the
>> Audio class.
>>
>> In the absence of objection on the list, these directions will be
>> confirmed as the rough consensus of the tsvwg WG - please comment.
>>
>> Thanks,
>> --David
>> ----------------------------------------------------
>> David L. Black, Distinguished Engineer
>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> david.black@emc.com        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>>
>>

From lars@netapp.com  Tue Mar 19 07:25:20 2013
Return-Path: <lars@netapp.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 146B321F8AD8 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 07:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.532
X-Spam-Level: 
X-Spam-Status: No, score=-10.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pdFt3FGiavqw for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 07:25:19 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 87CF521F89E9 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 07:25:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.84,872,1355126400"; d="scan'208";a="31959600"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 19 Mar 2013 07:25:19 -0700
Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r2JEPJTW003879; Tue, 19 Mar 2013 07:25:19 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.218]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0342.003; Tue, 19 Mar 2013 07:25:17 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "Black, David" <david.black@emc.com>
Thread-Topic: [tsvwg] RFC 4594 update: Hi-Res video class - open issue
Thread-Index: Ac4hmGOfPp6rctsMRaiGwuexfYqzKADT9wQA
Date: Tue, 19 Mar 2013 14:25:17 +0000
Message-ID: <368AF79B-6725-4793-956E-1CFD575896DE@netapp.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA94A0@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290FA94A0@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <56C45A93DC3085449D5EDB767B2325E3@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Hi-Res video class - open issue
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 14:25:20 -0000

On Mar 15, 2013, at 11:29, "Black, David" <david.black@emc.com> wrote:
> 	Question #1: Is this new class needed?

As I said in the room in Orlando, I think it's a slippery slope if we start=
 assigning codepoints to classes that are distinguished from others only by=
 policy or preference and not intrinsically. So no, I don't think we want t=
o do this.

(And you can already prioritize these video flows over other video flows by=
 five-tuple, if you have to.)

Lars=

From internet-drafts@ietf.org  Tue Mar 19 10:18:04 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7674121F8FD9; Tue, 19 Mar 2013 10:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.368
X-Spam-Level: 
X-Spam-Status: No, score=-102.368 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WpwspRNpMSwd; Tue, 19 Mar 2013 10:18:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 006E021F8F4A; Tue, 19 Mar 2013 10:18:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.43
Message-ID: <20130319171803.5446.43772.idtracker@ietfa.amsl.com>
Date: Tue, 19 Mar 2013 10:18:03 -0700
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-udp-encaps-14.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 17:18:04 -0000

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

	Title           : UDP Encapsulation of SCTP Packets for End-Host to End-Ho=
st Communication
	Author(s)       : Michael Tuexen
                          Randall R. Stewart
	Filename        : draft-ietf-tsvwg-sctp-udp-encaps-14.txt
	Pages           : 12
	Date            : 2013-03-19

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

   Please note that this document only describes the functionality
   required within an SCTP stack to add on UDP encapsulation, providing
   only those mechanisms for two end-hosts to communicate with each
   other over UDP ports.  In particular, it does not provide mechanisms
   to determine whether UDP encapsulation is being used by the peer, nor
   the mechanisms for determining which remote UDP port number can be
   used.  These functions are are out of scope for this document.

   This document covers only end-hosts and not tunneling (egress or
   ingress) end-points.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-udp-encaps-14


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


From gorry@erg.abdn.ac.uk  Tue Mar 19 11:49:23 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F02E21F8514 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 11:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TETe1EYm7OpA for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 11:49:22 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 1F79121F84F7 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 11:49:22 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 558A92B44B3; Tue, 19 Mar 2013 18:49:21 +0000 (GMT)
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 459362B4265 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 18:49:20 +0000 (GMT)
Message-ID: <5148B330.3000304@erg.abdn.ac.uk>
Date: Tue, 19 Mar 2013 18:49:20 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: tsvwg WG <tsvwg@ietf.org>
References: <4F605902.40009@erg.abdn.ac.uk>
In-Reply-To: <4F605902.40009@erg.abdn.ac.uk>
X-Forwarded-Message-Id: <4F605902.40009@erg.abdn.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 18:49:23 -0000

This email announces the start of a working group last call for
draft-ietf-tsvwg-sctp-sack-immediately-02.txt, "SACK-IMMEDIATELY 
Extension for the Stream Control Transmission Protocol". This document 
is now thought to be ready to proceed to be published as a PS. Please 
send any comments to the TSVWG list.

The draft is available at:
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-sack-immediately/

The last call will run for TWO weeks, ending Friday 5th April 2013.

Emails saying "I support" or "I don't support" publication are also most 
  helpful in judging the WG consensus. Please let us know if this draft 
is useful and seems to provide the correct advice.

James, David and Gorry
(TSVWG Chairs)
tsvwg-chairs@ietf.org








From jmpolk@cisco.com  Tue Mar 19 13:16:36 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D232221F8BF4 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:16:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.901
X-Spam-Level: 
X-Spam-Status: No, score=-109.901 tagged_above=-999 required=5 tests=[AWL=0.698, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1NBbNB8XsFqe for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:16:36 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 3752C21F8B65 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 13:16:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2924; q=dns/txt; s=iport; t=1363724196; x=1364933796; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version:content-transfer-encoding; bh=blCXVeU8xpIoB4vmCHd2F4To/hV8/yRWKuQnX9hTeOI=; b=CNqoxvzPrhlmeadKnMPZKbD7XTMY4Q5AfXNYGu8JriWVP4AM2fQeEEQ5 tdPIFgn7FSCu+GeaMjpRluvkXip6sfv25fYdrj5RFk+P+CcSNhePjUHT4 ouEOIZRHrDJdljYlP8tQEOZPsEIgi1EE1vTC9pJPqSnEXmmeu+ocUg3bN Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAJ3GSFGtJXG8/2dsb2JhbABAA8UdgVwWdIIkAQEBBDg4CQwEBwQRBAEBAQkeBw8KLQkIBhOIFLF0kAiOWyMFCwcGCwWDKgOIPzaebIMoHg
X-IronPort-AV: E=Sophos;i="4.84,873,1355097600"; d="scan'208";a="189279606"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-4.cisco.com with ESMTP; 19 Mar 2013 20:16:35 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r2JKGZop008123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2013 20:16:35 GMT
Message-Id: <201303192016.r2JKGZop008123@rcdn-core2-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 19 Mar 2013 15:16:11 -0500
To: <Ruediger.Geib@telekom.de>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1. CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Authenticated-User: jmpolk
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 20:16:37 -0000

At 10:45 AM 3/18/2013, Ruediger.Geib@telekom.de wrote:
>I don't object to broadening the name of a=20
>service class. As mentioned earlier,
>I don't like transport QoS classes being named close to applications. So
>weak objections against (1).
>
>Brian Carpenter didn't seem to favor (2) prior=20
>to the meeting. I personally think,
>classes Priority (here: audio) and Bulk Inelastic require admission control
>in access networks or some kind of TE in backbone sections. So to me EF
>already requires admission control and I don't think another PHB with
>otherwise identical properties adds a lot of value.

Having EF marked traffic requiring admission=20
controls in the core is very different than=20
having EF marked traffic require admission=20
controls everywhere. In fact, this is exactly the=20
opposite view in all (if not 100%, only 1 or 2%=20
off 100%) enterprise, Small/Medium Businesses=20
(SMB) and residential environments.

The expedited forwarding codepoint that has=20
admission control as part of its specification is=20
"Voice-Admit" (101100), per RFC 5865 - thus, as=20
someone stated before, having two codepoints with=20
identical PHBs is redundant and should be avoided.

>But well, that's my view.
>Could an argument be given why Voice-Admit is required? I hope that has=
 been
>discussed during the meeting.

It has. It is an RFC from this WG. Please review=20
RFC 5865. It's the singular purpose topic of that=20
RFC. Given that DSCP and PHB already exist, where=20
do they go in the service classes, in a new=20
service class, or the one shared with Audio?

James


>Regards,
>
>R=FCdiger
>
>
>-----Original Message-----
>From: tsvwg-bounces@ietf.org=20
>[mailto:tsvwg-bounces@ietf.org] On Behalf Of Black, David
>Sent: Friday, March 15, 2013 1:36 PM
>To: tsvwg@ietf.org
>Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>
>The discussion of the Audio service class in the RFC 4594 update
>draft in the tsvwg meeting yesterday reached a couple of initial
>conclusions that need to be checked on the list:
>
>(1) The class is being renamed from "Telephony" to "Audio", in part
>because "Telephony" is interpreted to include video in some contexts
>and that's not intended here.  There have also been some slight
>changes/generalizations to the description.
>
>(2) The newly-standardized Voice-Admit PHB is being added to the
>Audio class.
>
>In the absence of objection on the list, these directions will be
>confirmed as the rough consensus of the tsvwg WG - please comment.
>
>Thanks,
>--David
>----------------------------------------------------
>David L. Black, Distinguished Engineer
>EMC Corporation, 176 South St., Hopkinton, MA  01748
>+1 (508) 293-7953             FAX: +1 (508) 293-7786
>david.black@emc.com        Mobile: +1 (978) 394-7754
>----------------------------------------------------


From jmpolk@cisco.com  Tue Mar 19 13:31:13 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6029C21F8D62 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:31:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.25
X-Spam-Level: 
X-Spam-Status: No, score=-110.25 tagged_above=-999 required=5 tests=[AWL=0.349, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nMiacJGQMF7k for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:31:12 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 8F19F21F8E0E for <tsvwg@ietf.org>; Tue, 19 Mar 2013 13:31:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2988; q=dns/txt; s=iport; t=1363725072; x=1364934672; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version:content-transfer-encoding; bh=S7hMuACBQqttMzk1SQOSYos4lbzCNNT2fN48gpMADCU=; b=Rh8F6mqJTxTNZXvBteGZxGMPfOM5qQspqZHpgbMvW+5rHVb4ahyk3WuM HQWtcwxxzeyVj3ykjdfw7Gc6OAFJ18oz5EIW1m/QBpDRyNH0LZVNxnxYl sZqykSEOsApIhEv+zgzDKMcfJ4+x2gdhbFq1jIl9Lyp/g41V4fThpBd+o I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAPDJSFGtJV2b/2dsb2JhbABAAw7FD4FcFnSCJAEBAQQ4QQwEBwQRBAEBAQkeBw8KLQkIBhOIFLF5kAmOWyMQBwYLgy8DiD82nmyCS10e
X-IronPort-AV: E=Sophos;i="4.84,873,1355097600"; d="scan'208";a="186248931"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP; 19 Mar 2013 20:31:10 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2JKV9Ko015659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2013 20:31:09 GMT
Message-Id: <201303192031.r2JKV9Ko015659@rcdn-core-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 19 Mar 2013 15:30:45 -0500
To: Joe Touch <touch@isi.edu>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <5147A974.4030100@isi.edu>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5147A974.4030100@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Authenticated-User: jmpolk
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 20:31:13 -0000

At 06:55 PM 3/18/2013, Joe Touch wrote:
>Audio is a horrible name; the requirements for=20
>Pandora are completely different from Skype.

Pandora... as in the music service?

If so, then I agree with you - the requirements=20
of a (bufferable) music service are clearly=20
different than a two way realtime interactive service.


>Maybe "audio interactive" (vs. audio streaming)?

Audio is already in an interactive group. The=20
draft calls the group "conversational", and includes the

         Realtime-Interactive service class,
         Video service class
         Hi-Res (I've admitted this is a bad name) service class

Audio streaming is covered within

         Broadcast service class, for non-buffered streams, and
         Multimedia-Streaming, for buffered streams

The "streaming" service classes are in RFC 4594.

James


>Joe
>
>On 3/18/2013 8:45 AM, Ruediger.Geib@telekom.de wrote:
>>I don't object to broadening the name of a=20
>>service class. As mentioned earlier,
>>I don't like transport QoS classes being named close to applications. So
>>weak objections against (1).
>>
>>Brian Carpenter didn't seem to favor (2) prior=20
>>to the meeting. I personally think,
>>classes Priority (here: audio) and Bulk Inelastic require admission=
 control
>>in access networks or some kind of TE in backbone sections. So to me EF
>>already requires admission control and I don't think another PHB with
>>otherwise identical properties adds a lot of value. But well, that's my=
 view.
>>Could an argument be given why Voice-Admit is required? I hope that has=
 been
>>discussed during the meeting.
>>
>>Regards,
>>
>>R=FCdiger
>>
>>
>>-----Original Message-----
>>From: tsvwg-bounces@ietf.org=20
>>[mailto:tsvwg-bounces@ietf.org] On Behalf Of Black, David
>>Sent: Friday, March 15, 2013 1:36 PM
>>To: tsvwg@ietf.org
>>Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>>
>>The discussion of the Audio service class in the RFC 4594 update
>>draft in the tsvwg meeting yesterday reached a couple of initial
>>conclusions that need to be checked on the list:
>>
>>(1) The class is being renamed from "Telephony" to "Audio", in part
>>because "Telephony" is interpreted to include video in some contexts
>>and that's not intended here.  There have also been some slight
>>changes/generalizations to the description.
>>
>>(2) The newly-standardized Voice-Admit PHB is being added to the
>>Audio class.
>>
>>In the absence of objection on the list, these directions will be
>>confirmed as the rough consensus of the tsvwg WG - please comment.
>>
>>Thanks,
>>--David
>>----------------------------------------------------
>>David L. Black, Distinguished Engineer
>>EMC Corporation, 176 South St., Hopkinton, MA  01748
>>+1 (508) 293-7953             FAX: +1 (508) 293-7786
>>david.black@emc.com        Mobile: +1 (978) 394-7754
>>----------------------------------------------------
>>


From fred@cisco.com  Tue Mar 19 13:35:58 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C174621F8DDB for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:35:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.264
X-Spam-Level: 
X-Spam-Status: No, score=-110.264 tagged_above=-999 required=5 tests=[AWL=0.335, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L0REbuFVZliq for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:35:58 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 398E321F8CC5 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 13:35:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1140; q=dns/txt; s=iport; t=1363725358; x=1364934958; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=zaVvurV1OmTw8OytpsBS1PZjVCbpCAJ8KRAuhQPyZNc=; b=kNgkFNNff5feEb03KlcUNT/481LhGHjuwlxZkI9bGEI1O/rM69EfqJMd R6MOTV78ejXMYuL8a83VBKt8Fu3gnuH8A9wgfx9tD3iM9o6C22asMYrsu OF+MkfXz9xNxUZdP4po5nPKzV7e+H+L3XEm+Ki1wwT7VKuGkuK4Y8sl0Y o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAMHKSFGtJV2d/2dsb2JhbABAA8UdgVwWdIIkAQEBAwF5BQsCAQgiJDIlAgQOBQiIBgaxepAKjl0hEAcRgk5hA4g/nyKDCoIo
X-IronPort-AV: E=Sophos;i="4.84,873,1355097600"; d="scan'208";a="189275194"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 19 Mar 2013 20:35:57 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r2JKZvw2017081 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Mar 2013 20:35:57 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Tue, 19 Mar 2013 15:35:57 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "Black, David" <david.black@emc.com>
Thread-Topic: [tsvwg] RFC 4594 update: Audio class - consensus check
Thread-Index: AQHOJOFbn4GW+chZ40eBszpqtGDzWA==
Date: Tue, 19 Mar 2013 20:35:57 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7DC264@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.100.174]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B1F73AE7F2B14A40871D609BD5F5F7C5@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 20:35:58 -0000

works for me

On Mar 15, 2013, at 5:35 AM, "Black, David" <david.black@emc.com> wrote:

> The discussion of the Audio service class in the RFC 4594 update
> draft in the tsvwg meeting yesterday reached a couple of initial
> conclusions that need to be checked on the list:
>=20
> (1) The class is being renamed from "Telephony" to "Audio", in part
> because "Telephony" is interpreted to include video in some contexts
> and that's not intended here.  There have also been some slight
> changes/generalizations to the description.
>=20
> (2) The newly-standardized Voice-Admit PHB is being added to the
> Audio class.
>=20
> In the absence of objection on the list, these directions will be
> confirmed as the rough consensus of the tsvwg WG - please comment.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20
>=20


From md3135@att.com  Tue Mar 19 13:37:23 2013
Return-Path: <md3135@att.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E98AF21F8DD5 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VqY-UKNOyyBS for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:37:17 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id D8C0D21F8DED for <tsvwg@ietf.org>; Tue, 19 Mar 2013 13:37:16 -0700 (PDT)
Received: from unknown [144.160.20.146] (EHLO nbfkord-smmo07.seg.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.15.0-1) with ESMTP id c7cc8415.2aaabd0b9940.305469.00-561.861783.nbfkord-smmo07.seg.att.com (envelope-from <md3135@att.com>);  Tue, 19 Mar 2013 20:37:16 +0000 (UTC)
X-MXL-Hash: 5148cc7c12de8cd0-58bdc13b3cc51c1b1fd7b9315c41357816e6cbb8
Received: from unknown [144.160.20.146] (EHLO mlpd194.enaf.sfdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id c7cc8415.0.305460.00-277.861752.nbfkord-smmo07.seg.att.com (envelope-from <md3135@att.com>);  Tue, 19 Mar 2013 20:37:16 +0000 (UTC)
X-MXL-Hash: 5148cc7c020eebe6-e64eab793970a4acf783b41325a8b2a835e16d7e
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r2JKbFkK025170; Tue, 19 Mar 2013 16:37:15 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r2JKb6Xh024984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2013 16:37:12 -0400
Received: from MISOUT7MSGHUB9D.ITServices.sbc.com (misout7msghub9d.itservices.sbc.com [144.151.223.93]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Tue, 19 Mar 2013 20:37:02 GMT
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by MISOUT7MSGHUB9D.ITServices.sbc.com ([144.151.223.93]) with mapi id 14.02.0342.003; Tue, 19 Mar 2013 16:37:02 -0400
From: "DOLLY, MARTIN C" <md3135@att.com>
To: "Fred Baker (fred)" <fred@cisco.com>, "Black, David" <david.black@emc.com>
Thread-Topic: [tsvwg] RFC 4594 update: Audio class - consensus check
Thread-Index: AQHOJOFbn4GW+chZ40eBszpqtGDzWJiteS1g
Date: Tue, 19 Mar 2013 20:37:01 +0000
Message-ID: <E42CCDDA6722744CB241677169E8365602068AB3@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC264@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7DC264@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.179.172.224]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <md3135@att.com>
X-SOURCE-IP: [144.160.20.146]
X-AnalysisOut: [v=2.0 cv=PI+4D4WC c=1 sm=0 a=Qs8R1XBwmid1qBFB/a8mmA==:17 a]
X-AnalysisOut: [=YRAYh2FRAh4A:10 a=ABrLo6XDwTIA:10 a=ofMgfj31e3cA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=XIqpo32R]
X-AnalysisOut: [AAAA:8 a=MQIF8QsfeGoA:10 a=48vgC7mUAAAA:8 a=G0_B3m8xAAAA:8]
X-AnalysisOut: [ a=fDNXzfH0M8yD_3fHA7IA:9 a=CjuIK1q_8ugA:10 a=x32YNh-eXBMA]
X-AnalysisOut: [:10 a=sXX8f2-lqQ8A:10 a=MuCzCmE08hAA:10 a=GMbka86qx8EA:10 ]
X-AnalysisOut: [a=jJ7F3QIqxRAA:10 a=2_NgnSQ5-uYA:10 a=lZB815dzVvQA:10 a=lW]
X-AnalysisOut: [_bInUQU2sA:10]
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 20:37:24 -0000

+1

-----Original Message-----
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of F=
red Baker (fred)
Sent: Tuesday, March 19, 2013 4:36 PM
To: Black, David
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check

works for me

On Mar 15, 2013, at 5:35 AM, "Black, David" <david.black@emc.com> wrote:

> The discussion of the Audio service class in the RFC 4594 update
> draft in the tsvwg meeting yesterday reached a couple of initial
> conclusions that need to be checked on the list:
>=20
> (1) The class is being renamed from "Telephony" to "Audio", in part
> because "Telephony" is interpreted to include video in some contexts
> and that's not intended here.  There have also been some slight
> changes/generalizations to the description.
>=20
> (2) The newly-standardized Voice-Admit PHB is being added to the
> Audio class.
>=20
> In the absence of objection on the list, these directions will be
> confirmed as the rough consensus of the tsvwg WG - please comment.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20
>=20


From jmpolk@cisco.com  Tue Mar 19 13:39:07 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F7521F86E8 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.366
X-Spam-Level: 
X-Spam-Status: No, score=-110.366 tagged_above=-999 required=5 tests=[AWL=0.233, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7hrSNzzv3TNP for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:39:02 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 9D25F21F86B2 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 13:39:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3220; q=dns/txt; s=iport; t=1363725542; x=1364935142; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version:content-transfer-encoding; bh=kVQKxKTFL/5WLhBpHk7IUKhs2T8KVCwQidFIafgl23M=; b=G2KAY63wTJNeRgG87xQGRVjbA0UogcangUtMSAfgpip+fCvBg87xgYJU Wl++lls4tYRtS4rOz/pa2OoG5s4tCF2el7H5i8vGbFZjj5lF44ikLRRKB Eab1VYbF2+v6nQzL3avZsvd9Y0zJWmYMdweJmE1F6D+uZMP29BAtoJr9w c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAC7MSFGtJXHB/2dsb2JhbABAAw7FD4FcFnSCJAEBAQMBOEEFBwQHBBEEAQEBCR4HDwotCQgGARKIDgaxfZALjlsjEAcGC4JOYQOIPzaebIJLXR4
X-IronPort-AV: E=Sophos;i="4.84,873,1355097600"; d="scan'208";a="189246566"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-8.cisco.com with ESMTP; 19 Mar 2013 20:38:58 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r2JKcwaA011488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2013 20:38:58 GMT
Message-Id: <201303192038.r2JKcwaA011488@rcdn-core2-6.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 19 Mar 2013 15:38:34 -0500
To: <Ruediger.Geib@telekom.de>, <touch@isi.edu>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F13B@HE111643.EMEA1. CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5147A974.4030100@isi.edu> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F13B@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Authenticated-User: jmpolk
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 20:39:07 -0000

At 02:50 AM 3/19/2013, Ruediger.Geib@telekom.de wrote:
>There's still a possibility of decoupling class names from applications.
>
>pro: we don't run into problems like the one described by Joe.
>con: nobody can imagine what that class would be good for by just
>      reading the name. Readers must be educated.
>
>The application decoupled class name I've suggested is "Priority".

Nitpicking - that sends the wrong message, as=20
DiffServ is *not* a priority service, it is a=20
differentiated service. Brian C. is quick to point this out...

James


>Regards,
>
>R=FCdiger
>
>
>
>-----Original Message-----
>From: Joe Touch [mailto:touch@isi.edu]
>Sent: Tuesday, March 19, 2013 12:56 AM
>To: Geib, R=FCdiger
>Cc: david.black@emc.com; tsvwg@ietf.org
>Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
>
>Audio is a horrible name; the requirements for Pandora are completely
>different from Skype.
>
>Maybe "audio interactive" (vs. audio streaming)?
>
>Joe
>
>On 3/18/2013 8:45 AM, Ruediger.Geib@telekom.de wrote:
> > I don't object to broadening the name of a=20
> service class. As mentioned earlier,
> > I don't like transport QoS classes being named close to applications. So
> > weak objections against (1).
> >
> > Brian Carpenter didn't seem to favor (2)=20
> prior to the meeting. I personally think,
> > classes Priority (here: audio) and Bulk Inelastic require admission=
 control
> > in access networks or some kind of TE in backbone sections. So to me EF
> > already requires admission control and I don't think another PHB with
> > otherwise identical properties adds a lot of=20
> value. But well, that's my view.
> > Could an argument be given why Voice-Admit is=20
> required? I hope that has been
> > discussed during the meeting.
> >
> > Regards,
> >
> > R=FCdiger
> >
> >
> > -----Original Message-----
> > From: tsvwg-bounces@ietf.org=20
> [mailto:tsvwg-bounces@ietf.org] On Behalf Of Black, David
> > Sent: Friday, March 15, 2013 1:36 PM
> > To: tsvwg@ietf.org
> > Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
> >
> > The discussion of the Audio service class in the RFC 4594 update
> > draft in the tsvwg meeting yesterday reached a couple of initial
> > conclusions that need to be checked on the list:
> >
> > (1) The class is being renamed from "Telephony" to "Audio", in part
> > because "Telephony" is interpreted to include video in some contexts
> > and that's not intended here.  There have also been some slight
> > changes/generalizations to the description.
> >
> > (2) The newly-standardized Voice-Admit PHB is being added to the
> > Audio class.
> >
> > In the absence of objection on the list, these directions will be
> > confirmed as the rough consensus of the tsvwg WG - please comment.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > david.black@emc.com        Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >
> >


From touch@isi.edu  Tue Mar 19 13:43:38 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D98421F8F35 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.413
X-Spam-Level: 
X-Spam-Status: No, score=-105.413 tagged_above=-999 required=5 tests=[AWL=1.186, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qipRiflY3p-n for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:43:37 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 383D921F8F40 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 13:43:37 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r2JKfjmH029013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 19 Mar 2013 13:41:47 -0700 (PDT)
Message-ID: <5148CD8A.4050408@isi.edu>
Date: Tue, 19 Mar 2013 13:41:46 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: James Polk <jmpolk@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5147A974.4030100@isi.edu> <201303192031.r2JKV9Ko015659@rcdn-core-4.cisco.com>
In-Reply-To: <201303192031.r2JKV9Ko015659@rcdn-core-4.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 20:43:38 -0000

On 3/19/2013 1:30 PM, James Polk wrote:
> At 06:55 PM 3/18/2013, Joe Touch wrote:
>> Audio is a horrible name; the requirements for Pandora are completely
>> different from Skype.
>
> Pandora... as in the music service?

Yeah - I was picking an example out of a hat...

> If so, then I agree with you - the requirements of a (bufferable) music
> service are clearly different than a two way realtime interactive service.
>
>> Maybe "audio interactive" (vs. audio streaming)?
>
> Audio is already in an interactive group. The draft calls the group
> "conversational", and includes the
>
>          Realtime-Interactive service class,
>          Video service class
>          Hi-Res (I've admitted this is a bad name) service class
>
> Audio streaming is covered within
>
>          Broadcast service class, for non-buffered streams, and
>          Multimedia-Streaming, for buffered streams
>
> The "streaming" service classes are in RFC 4594.

In that case a new class for audio isn't needed.

Though "realtime interactive" sounds like it could include voice, voice 
& video, and gaming - which aren't quite the same service class, IMO.

Joe

>> Joe
>>
>> On 3/18/2013 8:45 AM, Ruediger.Geib@telekom.de wrote:
>>> I don't object to broadening the name of a service class. As
>>> mentioned earlier,
>>> I don't like transport QoS classes being named close to applications. So
>>> weak objections against (1).
>>>
>>> Brian Carpenter didn't seem to favor (2) prior to the meeting. I
>>> personally think,
>>> classes Priority (here: audio) and Bulk Inelastic require admission
>>> control
>>> in access networks or some kind of TE in backbone sections. So to me EF
>>> already requires admission control and I don't think another PHB with
>>> otherwise identical properties adds a lot of value. But well, that's
>>> my view.
>>> Could an argument be given why Voice-Admit is required? I hope that
>>> has been
>>> discussed during the meeting.
>>>
>>> Regards,
>>>
>>> Rüdiger
>>>
>>>
>>> -----Original Message-----
>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On
>>> Behalf Of Black, David
>>> Sent: Friday, March 15, 2013 1:36 PM
>>> To: tsvwg@ietf.org
>>> Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>>>
>>> The discussion of the Audio service class in the RFC 4594 update
>>> draft in the tsvwg meeting yesterday reached a couple of initial
>>> conclusions that need to be checked on the list:
>>>
>>> (1) The class is being renamed from "Telephony" to "Audio", in part
>>> because "Telephony" is interpreted to include video in some contexts
>>> and that's not intended here.  There have also been some slight
>>> changes/generalizations to the description.
>>>
>>> (2) The newly-standardized Voice-Admit PHB is being added to the
>>> Audio class.
>>>
>>> In the absence of objection on the list, these directions will be
>>> confirmed as the rough consensus of the tsvwg WG - please comment.
>>>
>>> Thanks,
>>> --David
>>> ----------------------------------------------------
>>> David L. Black, Distinguished Engineer
>>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>>> david.black@emc.com        Mobile: +1 (978) 394-7754
>>> ----------------------------------------------------
>>>
>

From fred@cisco.com  Tue Mar 19 13:53:29 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72A0021F8F85 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.436
X-Spam-Level: 
X-Spam-Status: No, score=-110.436 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id krkmCbaa7MVi for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:53:28 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id AA55821F8F83 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 13:53:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2939; q=dns/txt; s=iport; t=1363726408; x=1364936008; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=defOWDmJ1RFCP6UZESq5XJ7vDIHg+TyacbuiQ4sB2Ic=; b=L3P4zf7IS08VKsDJYW94AUHD0WQVm3J2R/aMoAKCbibzbZS4UVAx8InT MyQmanoL9MmeYiP7NFdGAq5vuhXMGGIQd1DB0lEJcCpkx0vFC4TgEBvmn wkbVRzqli55anNu2MbCiyARCz6xRRShVxRD8yyDWiB6tVKmR+J5DXizUg k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAMfPSFGtJV2b/2dsb2JhbABDxR2BXBZtB4IlAQEEgQkCASokMiUCBBMIiAyyBpALjVmBBDiCX2EDiD+fIoMKgWs9
X-IronPort-AV: E=Sophos;i="4.84,873,1355097600"; d="scan'208";a="189248054"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-6.cisco.com with ESMTP; 19 Mar 2013 20:53:23 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2JKrN9m031030 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Tue, 19 Mar 2013 20:53:23 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.004; Tue, 19 Mar 2013 15:53:22 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: RFC 4594 update: Routing class
Thread-Index: AQHOJOPLO7HQcY3BYEe9wayWVpOf6Q==
Date: Tue, 19 Mar 2013 20:53:22 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.100.174]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8AD89BEB4DEADE45896BCC823B05F7B8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 20:53:29 -0000

I was unable to attend twvwg at IETF 86 as it competed with a meeting I pre=
sented in. I am told that there was a presentation in which folks argued ag=
ainst having a class of traffic for routing traffic. I'd like to comment on=
 that.

The origin of a class of traffic for routing traffic was a bug. The Cisco 7=
000 had an issue with its offloaded forwarding cards, of which it had two. =
When there was a route flap, it blew away the route cache and then rebuilt =
it in response to traffic it needed to forward. In that implementation, tha=
t meant that the Route Processor (the CPU) suddenly had all traffic from al=
l sources flooded into it. The impact of that was to make it very difficult=
 for the RP to actually re-populate the Route Cache. Doubleplus ungood. The=
 work-around was to rate-limit traffic from the line cards to the RP. Howev=
er, rate limiting the routing traffic worked against getting routing to sta=
bilize, so we marked routing traffic, and did not rate limit *it* from goin=
g to the RP.

Fast forward nearly 20 years. We don't have that bug anymore, if anything b=
ecause nobody equipped with a right mind uses the Cisco 7000 any more.

However...

If we're going to discuss quality of service for any application, we are ma=
king some fundamental assumptions. These include the concept of having enou=
gh bandwidth and so on; we're managing traffic at points in time when peak =
traffic loads on a millisecond scale create issues. One of those fundamenta=
l issues is that routing must be current; if we're sending traffic on a rou=
te that loops because the other guy updated his route table but we didn't, =
or vice versa, or for which interface or next hop router is no longer there=
, we can discuss jitter, rate, and loss to our heart's content - the applic=
ation's traffic isn't going to get there. At. All. And won't until routing =
stabilizes.

The fundamental argument for a class of traffic for routing in 2013 is not =
that routing requires certain jitter, rate, or etc characteristics; it is t=
hat routing traffic (apart from AQM issues, see separate discussion on aqm@=
ietf.org) should simply *not*be*dropped* in the normal course of business. =
Routing is fundamental to all other services the network delivers, includin=
g QoS, and including every networks's SLAs.=20

Now, one can say that routing is between neighboring nodes, and a router is=
 able to do special things with traffic it itself originates. It is true th=
at a router can do special things with its own traffic, and they do. But BG=
P Routing frequently goes from Route Arbiter to Route Arbiter instead of Ro=
uter to Router, which is to say through other routers between routing engin=
es. Traffic through other routers is traffic through other routers, not a r=
outer's own traffic. It requires some form of end to end marking to protect=
 it. Something like a DSCP.=

From jmpolk@cisco.com  Tue Mar 19 14:21:51 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0775C21F9018 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 14:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.425
X-Spam-Level: 
X-Spam-Status: No, score=-110.425 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1i86yaa2pXq5 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 14:21:50 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0CA5421F9030 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 14:21:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4052; q=dns/txt; s=iport; t=1363728110; x=1364937710; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version:content-transfer-encoding; bh=/q+L4fYq4IBNQWUMnk6ORAlhm10A7UDidQET2qdoMEc=; b=N/plB65rlQIajLEK4njzF0dDOlyGFQ7ze5JPkeNfsh1sYqwjbMsh5S7e meAxQ1rYlSl8S19GPaPgHeZFJwYm4IR6Dw0aBzJEd97Y63/VBxRcNd50M qZ1ghIamwigI/c9wRikRllyegrnMQI4oL4IM+xr+x02zexWX4Sg6BCqXr c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAGTVSFGtJXHB/2dsb2JhbABAAw7FD4FcFnSCJAEBAQQ4QQwEBwQRBAEBAQkeBw8KLQkIBhOIFLIJkA6OfhAHBguDLwOIPzaebIJLXR4
X-IronPort-AV: E=Sophos;i="4.84,874,1355097600"; d="scan'208";a="189043342"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-1.cisco.com with ESMTP; 19 Mar 2013 21:21:49 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r2JLLnjf009800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2013 21:21:49 GMT
Message-Id: <201303192121.r2JLLnjf009800@rcdn-core2-6.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 19 Mar 2013 16:21:25 -0500
To: Joe Touch <touch@isi.edu>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <5148CD8A.4050408@isi.edu>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5147A974.4030100@isi.edu> <201303192031.r2JKV9Ko015659@rcdn-core-4.cisco.com> <5148CD8A.4050408@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Authenticated-User: jmpolk
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 21:21:51 -0000

At 03:41 PM 3/19/2013, Joe Touch wrote:


>On 3/19/2013 1:30 PM, James Polk wrote:
>>At 06:55 PM 3/18/2013, Joe Touch wrote:
>>>Audio is a horrible name; the requirements for Pandora are completely
>>>different from Skype.
>>
>>Pandora... as in the music service?
>
>Yeah - I was picking an example out of a hat...
>
>>If so, then I agree with you - the requirements of a (bufferable) music
>>service are clearly different than a two way realtime interactive service.
>>
>>>Maybe "audio interactive" (vs. audio streaming)?
>>
>>Audio is already in an interactive group. The draft calls the group
>>"conversational", and includes the
>>
>>          Realtime-Interactive service class,
>>          Video service class
>>          Hi-Res (I've admitted this is a bad name) service class
>>
>>Audio streaming is covered within
>>
>>          Broadcast service class, for non-buffered streams, and
>>          Multimedia-Streaming, for buffered streams
>>
>>The "streaming" service classes are in RFC 4594.
>
>In that case a new class for audio isn't needed.

Joe

Audio is *not* a new service class, we're just=20
proposing a name change of the existing Telephony=20
service class, and removing the recommendation=20
that video traffic be marked the same as audio=20
traffic - which few networks currently do, even=20
in the core/interconnect (unless of course both are marked as best effort).


>Though "realtime interactive" sounds like it=20
>could include voice, voice & video, and gaming -=20
>which aren't quite the same service class, IMO.

It's not, as gaming (still recommended in=20
"realtime interactive" service class) is mostly=20
TCP based, and we don't want to place TCP based=20
anything in the same service class or queue with realtime UDP traffic.

James


>Joe
>
>>>Joe
>>>
>>>On 3/18/2013 8:45 AM, Ruediger.Geib@telekom.de wrote:
>>>>I don't object to broadening the name of a service class. As
>>>>mentioned earlier,
>>>>I don't like transport QoS classes being named close to applications. So
>>>>weak objections against (1).
>>>>
>>>>Brian Carpenter didn't seem to favor (2) prior to the meeting. I
>>>>personally think,
>>>>classes Priority (here: audio) and Bulk Inelastic require admission
>>>>control
>>>>in access networks or some kind of TE in backbone sections. So to me EF
>>>>already requires admission control and I don't think another PHB with
>>>>otherwise identical properties adds a lot of value. But well, that's
>>>>my view.
>>>>Could an argument be given why Voice-Admit is required? I hope that
>>>>has been
>>>>discussed during the meeting.
>>>>
>>>>Regards,
>>>>
>>>>R=FCdiger
>>>>
>>>>
>>>>-----Original Message-----
>>>>From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On
>>>>Behalf Of Black, David
>>>>Sent: Friday, March 15, 2013 1:36 PM
>>>>To: tsvwg@ietf.org
>>>>Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>>>>
>>>>The discussion of the Audio service class in the RFC 4594 update
>>>>draft in the tsvwg meeting yesterday reached a couple of initial
>>>>conclusions that need to be checked on the list:
>>>>
>>>>(1) The class is being renamed from "Telephony" to "Audio", in part
>>>>because "Telephony" is interpreted to include video in some contexts
>>>>and that's not intended here.  There have also been some slight
>>>>changes/generalizations to the description.
>>>>
>>>>(2) The newly-standardized Voice-Admit PHB is being added to the
>>>>Audio class.
>>>>
>>>>In the absence of objection on the list, these directions will be
>>>>confirmed as the rough consensus of the tsvwg WG - please comment.
>>>>
>>>>Thanks,
>>>>--David
>>>>----------------------------------------------------
>>>>David L. Black, Distinguished Engineer
>>>>EMC Corporation, 176 South St., Hopkinton, MA  01748
>>>>+1 (508) 293-7953             FAX: +1 (508) 293-7786
>>>>david.black@emc.com        Mobile: +1 (978) 394-7754
>>>>----------------------------------------------------


From touch@isi.edu  Tue Mar 19 14:28:42 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B023F21F8B0B for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 14:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.739
X-Spam-Level: 
X-Spam-Status: No, score=-103.739 tagged_above=-999 required=5 tests=[AWL=-1.140, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDM8xrx6r+qk for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 14:28:42 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id F195A21F8B96 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 14:28:41 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r2JLRbo5019508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 19 Mar 2013 14:27:37 -0700 (PDT)
Message-ID: <5148D843.6030309@isi.edu>
Date: Tue, 19 Mar 2013 14:27:31 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: James Polk <jmpolk@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5147A974.4030100@isi.edu> <201303192031.r2JKV9Ko015659@rcdn-core-4.cisco.com> <5148CD8A.4050408@isi.edu> <201303192121.r2JLLnjf009800@rcdn-core2-6.cisco.com>
In-Reply-To: <201303192121.r2JLLnjf009800@rcdn-core2-6.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 21:28:42 -0000

On 3/19/2013 2:21 PM, James Polk wrote:
> At 03:41 PM 3/19/2013, Joe Touch wrote:
...
>> Though "realtime interactive" sounds like it could include voice,
>> voice & video, and gaming - which aren't quite the same service class,
>> IMO.
>
> It's not, as gaming (still recommended in "realtime interactive" service
> class) is mostly TCP based, and we don't want to place TCP based
> anything in the same service class or queue with realtime UDP traffic.

Gaming widely uses UDP. See a good example here:

https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711

http://www.practicallynetworked.com/sharing/app_port_list.htm

Note how many games use *only* UDP.

Joe



From jmpolk@cisco.com  Tue Mar 19 14:42:55 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87A7F21F84B6 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 14:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.459
X-Spam-Level: 
X-Spam-Status: No, score=-110.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uj1WoiommHFR for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 14:42:54 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 0F97621F842B for <tsvwg@ietf.org>; Tue, 19 Mar 2013 14:42:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1054; q=dns/txt; s=iport; t=1363729374; x=1364938974; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=JaCUzepu88/8ec8qMCkxRngPow4Hj/FCbGq4oLDoMx8=; b=C4GCYdUhV41fAfS74tdc3yiDFthJaY1J3OP+6JSZGc6lXvRXPA57l+m8 6Dg2qNaQGyu/NCe6jC3vZBmLBJhEwBomcKtUT4Aiz1us1tWh4QSaQcul8 QQU4lsdZltOrWgx6fy8Yws3iRvjJRLKEz0tOFEHZReHTYVwM97KFF7FWH E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAKTaSFGtJV2a/2dsb2JhbAApGg7FD4FcFnSCJAEBAQQ4Aj8QBwQYCRUQDwo+BognDC6xUpAMjw4Hg0ADiHWebIJLXR4
X-IronPort-AV: E=Sophos;i="4.84,874,1355097600"; d="scan'208";a="189295343"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-3.cisco.com with ESMTP; 19 Mar 2013 21:42:53 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2JLgrgg015865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2013 21:42:53 GMT
Message-Id: <201303192142.r2JLgrgg015865@rcdn-core-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 19 Mar 2013 16:42:29 -0500
To: Joe Touch <touch@isi.edu>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <5148D843.6030309@isi.edu>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5147A974.4030100@isi.edu> <201303192031.r2JKV9Ko015659@rcdn-core-4.cisco.com> <5148CD8A.4050408@isi.edu> <201303192121.r2JLLnjf009800@rcdn-core2-6.cisco.com> <5148D843.6030309@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 21:42:55 -0000

At 04:27 PM 3/19/2013, Joe Touch wrote:


>On 3/19/2013 2:21 PM, James Polk wrote:
>>At 03:41 PM 3/19/2013, Joe Touch wrote:
>...
>>>Though "realtime interactive" sounds like it could include voice,
>>>voice & video, and gaming - which aren't quite the same service class,
>>>IMO.
>>
>>It's not, as gaming (still recommended in "realtime interactive" service
>>class) is mostly TCP based, and we don't want to place TCP based
>>anything in the same service class or queue with realtime UDP traffic.
>
>Gaming widely uses UDP. See a good example here:
>
>https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711
>
>http://www.practicallynetworked.com/sharing/app_port_list.htm
>
>Note how many games use *only* UDP.

Fair point. I wasn't claiming gaming only uses TCP, but that there 
were a fair amount of gaming apps that use TCP, and I was making the 
comment from the perspective of "let's not stuff audio and video into 
that service class as well if we don't have to, and we don't have to".

James


>Joe
>


From fred@cisco.com  Tue Mar 19 16:01:27 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64F5821F8D8F for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 16:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.294
X-Spam-Level: 
X-Spam-Status: No, score=-110.294 tagged_above=-999 required=5 tests=[AWL=0.304, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8tAsjSUqHep3 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 16:01:26 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 80FBB21F8D8C for <tsvwg@ietf.org>; Tue, 19 Mar 2013 16:01:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4135; q=dns/txt; s=iport; t=1363734086; x=1364943686; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+fcuTg23WlrPmkjgTelFp0aSvhfmkiRv/SGMCzEFOc0=; b=LnB91/TA8fZYhbi1KpKgNQRK0/1+sWatCPT9YS1Ej8B0V0/1IuMcqtRu 1GJNfyRu6CA3AD3Cf+i/Kn9XA/zNngZJG7l8gVTmScW4vAbK5zPXw5a1k ToTpDAYHSWx275QulRDjdykprZQr7beEutfOXzDyFcJqevYYpXnb4s1GP E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAE7tSFGtJXG9/2dsb2JhbAA5BwPFCYFFFnSCJAEBAQMBeQUHBAIBCBEEAQEBCh0HMhQJCAIEDgUIiAYGsgaQB41UBIEDAiEQBwYLgk5hA4g/nyKDCoFqPg
X-IronPort-AV: E=Sophos;i="4.84,874,1355097600"; d="scan'208";a="189068660"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-1.cisco.com with ESMTP; 19 Mar 2013 23:01:17 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2JN1HuF000509 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Mar 2013 23:01:17 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Tue, 19 Mar 2013 18:01:17 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "James Polk (jmpolk)" <jmpolk@cisco.com>
Thread-Topic: [tsvwg] RFC 4594 update: Audio class - consensus check
Thread-Index: AQHOJPWpaOrj+X+sQ0SpFjfdVcwBUw==
Date: Tue, 19 Mar 2013 23:01:16 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7DC5BB@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5147A974.4030100@isi.edu> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F13B@HE111643.EMEA1.CDS.T-INTERNAL.COM> <201303192038.r2JKcwaA011488@rcdn-core2-6.cisco.com>
In-Reply-To: <201303192038.r2JKcwaA011488@rcdn-core2-6.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.100.174]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4E18FCE1CD0B5C41938D25977CB1E026@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<tsvwg@ietf.org>" <tsvwg@ietf.org>, "<touch@isi.edu>" <touch@isi.edu>
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 23:01:27 -0000

On Mar 19, 2013, at 1:38 PM, James Polk <jmpolk@cisco.com> wrote:

> At 02:50 AM 3/19/2013, Ruediger.Geib@telekom.de wrote:
>> There's still a possibility of decoupling class names from applications.
>>=20
>> pro: we don't run into problems like the one described by Joe.
>> con: nobody can imagine what that class would be good for by just
>>     reading the name. Readers must be educated.
>>=20
>> The application decoupled class name I've suggested is "Priority".
>=20
> Nitpicking - that sends the wrong message, as DiffServ is *not* a priorit=
y service, it is a differentiated service. Brian C. is quick to point this =
out...

More than a nitpick. This is actually important.

Priority is the name of a scheduler, not a service. I'm will enough to have=
 the service decoupled from audio, but if we do, it would be better to iden=
tify the characteristics of the service in the name, not one of them in the=
 absence of the others. The characteristics are that it limits jitter (the =
effect of a priority scheduler) for a limited amount of data (if you exceed=
 the amount of data, it discards the excess).

I suspect that calling it "priority" will have every idiot on the planet tr=
ying to use it for his or her pet application without regard to the service=
 it offers or what their application's specific needs are.

> James
>=20
>=20
>> Regards,
>>=20
>> R=FCdiger
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@isi.edu]
>> Sent: Tuesday, March 19, 2013 12:56 AM
>> To: Geib, R=FCdiger
>> Cc: david.black@emc.com; tsvwg@ietf.org
>> Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
>>=20
>> Audio is a horrible name; the requirements for Pandora are completely
>> different from Skype.
>>=20
>> Maybe "audio interactive" (vs. audio streaming)?
>>=20
>> Joe
>>=20
>> On 3/18/2013 8:45 AM, Ruediger.Geib@telekom.de wrote:
>> > I don't object to broadening the name of a service class. As mentioned=
 earlier,
>> > I don't like transport QoS classes being named close to applications. =
So
>> > weak objections against (1).
>> >
>> > Brian Carpenter didn't seem to favor (2) prior to the meeting. I perso=
nally think,
>> > classes Priority (here: audio) and Bulk Inelastic require admission co=
ntrol
>> > in access networks or some kind of TE in backbone sections. So to me E=
F
>> > already requires admission control and I don't think another PHB with
>> > otherwise identical properties adds a lot of value. But well, that's m=
y view.
>> > Could an argument be given why Voice-Admit is required? I hope that ha=
s been
>> > discussed during the meeting.
>> >
>> > Regards,
>> >
>> > R=FCdiger
>> >
>> >
>> > -----Original Message-----
>> > From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf=
 Of Black, David
>> > Sent: Friday, March 15, 2013 1:36 PM
>> > To: tsvwg@ietf.org
>> > Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>> >
>> > The discussion of the Audio service class in the RFC 4594 update
>> > draft in the tsvwg meeting yesterday reached a couple of initial
>> > conclusions that need to be checked on the list:
>> >
>> > (1) The class is being renamed from "Telephony" to "Audio", in part
>> > because "Telephony" is interpreted to include video in some contexts
>> > and that's not intended here.  There have also been some slight
>> > changes/generalizations to the description.
>> >
>> > (2) The newly-standardized Voice-Admit PHB is being added to the
>> > Audio class.
>> >
>> > In the absence of objection on the list, these directions will be
>> > confirmed as the rough consensus of the tsvwg WG - please comment.
>> >
>> > Thanks,
>> > --David
>> > ----------------------------------------------------
>> > David L. Black, Distinguished Engineer
>> > EMC Corporation, 176 South St., Hopkinton, MA  01748
>> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> > david.black@emc.com        Mobile: +1 (978) 394-7754
>> > ----------------------------------------------------
>> >
>> >
>=20


From david.black@emc.com  Tue Mar 19 19:40:27 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5CE421F8F0F for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 19:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.49
X-Spam-Level: 
X-Spam-Status: No, score=-102.49 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RqflqFqkrhER for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 19:40:27 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1D21C21F8F03 for <tsvwg@ietf.org>; Tue, 19 Mar 2013 19:40:25 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2K2eNtc031634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2013 22:40:24 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 19 Mar 2013 22:40:07 -0400
Received: from mxhub25.corp.emc.com (mxhub25.corp.emc.com [10.254.110.181]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2K2e5lq028631; Tue, 19 Mar 2013 22:40:05 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub25.corp.emc.com ([10.254.110.181]) with mapi; Tue, 19 Mar 2013 22:40:04 -0400
From: "Black, David" <david.black@emc.com>
To: "Fred Baker (fred)" <fred@cisco.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Date: Tue, 19 Mar 2013 22:40:03 -0400
Thread-Topic: RFC 4594 update: Routing class
Thread-Index: AQHOJOPLO7HQcY3BYEe9wayWVpOf6Zit3Wjg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 02:40:28 -0000

Hi Fred,

> I was unable to attend tsvwg at IETF 86 as it competed with a meeting I
> presented in. I am told that there was a presentation in which folks argu=
ed
> against having a class of traffic for routing traffic. I'd like to commen=
t on
> that.

The argument in particular is about whether a class of traffic is needed fo=
r
Routing traffic across an interconnection of two carrier networks.

The argument was teed up for discussion in this slide presented in connecti=
on
with draft-geib-tsvwg-diffserv-intercon-02:

http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx

Thank you for the comments,
--David

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of=
 Fred
> Baker (fred)
> Sent: Tuesday, March 19, 2013 4:53 PM
> To: tsvwg@ietf.org
> Subject: [tsvwg] RFC 4594 update: Routing class
>=20
> I was unable to attend twvwg at IETF 86 as it competed with a meeting I
> presented in. I am told that there was a presentation in which folks argu=
ed
> against having a class of traffic for routing traffic. I'd like to commen=
t on
> that.
>=20
> The origin of a class of traffic for routing traffic was a bug. The Cisco=
 7000
> had an issue with its offloaded forwarding cards, of which it had two. Wh=
en
> there was a route flap, it blew away the route cache and then rebuilt it =
in
> response to traffic it needed to forward. In that implementation, that me=
ant
> that the Route Processor (the CPU) suddenly had all traffic from all sour=
ces
> flooded into it. The impact of that was to make it very difficult for the=
 RP
> to actually re-populate the Route Cache. Doubleplus ungood. The work-arou=
nd
> was to rate-limit traffic from the line cards to the RP. However, rate
> limiting the routing traffic worked against getting routing to stabilize,=
 so
> we marked routing traffic, and did not rate limit *it* from going to the =
RP.
>=20
> Fast forward nearly 20 years. We don't have that bug anymore, if anything
> because nobody equipped with a right mind uses the Cisco 7000 any more.
>=20
> However...
>=20
> If we're going to discuss quality of service for any application, we are
> making some fundamental assumptions. These include the concept of having
> enough bandwidth and so on; we're managing traffic at points in time when=
 peak
> traffic loads on a millisecond scale create issues. One of those fundamen=
tal
> issues is that routing must be current; if we're sending traffic on a rou=
te
> that loops because the other guy updated his route table but we didn't, o=
r
> vice versa, or for which interface or next hop router is no longer there,=
 we
> can discuss jitter, rate, and loss to our heart's content - the applicati=
on's
> traffic isn't going to get there. At. All. And won't until routing stabil=
izes.
>=20
> The fundamental argument for a class of traffic for routing in 2013 is no=
t
> that routing requires certain jitter, rate, or etc characteristics; it is=
 that
> routing traffic (apart from AQM issues, see separate discussion on
> aqm@ietf.org) should simply *not*be*dropped* in the normal course of busi=
ness.
> Routing is fundamental to all other services the network delivers, includ=
ing
> QoS, and including every networks's SLAs.
>=20
> Now, one can say that routing is between neighboring nodes, and a router =
is
> able to do special things with traffic it itself originates. It is true t=
hat a
> router can do special things with its own traffic, and they do. But BGP
> Routing frequently goes from Route Arbiter to Route Arbiter instead of Ro=
uter
> to Router, which is to say through other routers between routing engines.
> Traffic through other routers is traffic through other routers, not a rou=
ter's
> own traffic. It requires some form of end to end marking to protect it.
> Something like a DSCP.

From david.black@emc.com  Tue Mar 19 19:57:46 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A11821F85DB for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 19:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sUV+7Qpz4H-B for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 19:57:45 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1E8A021F86CB for <tsvwg@ietf.org>; Tue, 19 Mar 2013 19:57:37 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2K2vZs8020943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2013 22:57:35 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 19 Mar 2013 22:57:23 -0400
Received: from mxhub09.corp.emc.com (mxhub09.corp.emc.com [10.254.92.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2K2vNr4016397; Tue, 19 Mar 2013 22:57:23 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub09.corp.emc.com ([10.254.92.104]) with mapi; Tue, 19 Mar 2013 22:57:23 -0400
From: "Black, David" <david.black@emc.com>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, tsvwg WG <tsvwg@ietf.org>
Date: Tue, 19 Mar 2013 22:57:21 -0400
Thread-Topic: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013
Thread-Index: Ac4k01sCfQXBSLIgT6iW7UnrYRiiRQAQS/8w
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293AEE3FE@MX15A.corp.emc.com>
References: <4F605902.40009@erg.abdn.ac.uk> <5148B330.3000304@erg.abdn.ac.uk>
In-Reply-To: <5148B330.3000304@erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 02:57:46 -0000

Comments as an individual - <WG co-chair hat OFF>

The draft generally looks good - I have a bunch of minor comments.

End of Section 3 - I suggest adding a sentence about the new I-bit:

	This bit was Reserved in RFC 4960 - RFC 4960 specified
	that this bit should be set to 0 by the sender and ignored
	by the receiver.

Section 4.1 - The paragraph in this section describes an example of a
situation in which it is appropriate to set the I-bit.  It needs an
introductory sentence to say that it is an example, e.g.:

	One example of a situation in which it may be desirable for
	an application to trigger setting of the I-bit involves the
	SCTP_SENDER_DRY_EVENT in the SCTP socket API [RFC6458].

Section 4.2 - Suggest "should" -> "SHOULD" in the following paragraph:

   If the association is in the SHUTDOWN-PENDING state, the I-bit should
   be set.  This reduces the number of simultaneous associations in case
   of a busy server handling short living associations.

Also an editorial nit in the above - "in case of" -> "for"

Another editorial nit in the following:

   If an SCTP association supports the SCTP Stream Reconfiguration
   extension defined in [RFC6525], the performance can be improved by
   setting the I-bit when there are pending reconfiguration requests
   requiring no outstanding DATA chunks.

"requiring" -> "that require that there be"

Section 5.2:

   On reception of an SCTP packet containing a DATA chunk with the I-bit
   set, the receiver SHOULD NOT delay the sending of the corresponding
   SACK chunk and send it back immediately.

"SACK chunk and send it back immediately" -> "SACK chunk, i.e., the
receiver SHOULD immediately respond with the corresponding SACK chunk"

Section 8: Please tell IANA which registry to use by including the
name of the registry.

Section 9: Change start of paragraph to acknowledge new security
consideration:

OLD
   This document does not add any additional security considerations in
   addition to the ones given in [RFC4960].  It should be noted that a
   malicious sender can force its peer to send packets containing a SACK
NEW
   See [RFC4960] for general security considerations for SCTP.  In addition=
,
   a malicious sender can force its peer to send packets containing a SACK
END

Thanks,
--David


> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Gorry Fairhurst
> Sent: Tuesday, March 19, 2013 2:49 PM
> To: tsvwg WG
> Subject: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immedia=
tely-
> 02: 19th March 2013
>=20
>=20
> This email announces the start of a working group last call for
> draft-ietf-tsvwg-sctp-sack-immediately-02.txt, "SACK-IMMEDIATELY
> Extension for the Stream Control Transmission Protocol". This document
> is now thought to be ready to proceed to be published as a PS. Please
> send any comments to the TSVWG list.
>=20
> The draft is available at:
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-sack-immediately/
>=20
> The last call will run for TWO weeks, ending Friday 5th April 2013.
>=20
> Emails saying "I support" or "I don't support" publication are also most
>   helpful in judging the WG consensus. Please let us know if this draft
> is useful and seems to provide the correct advice.
>=20
> James, David and Gorry
> (TSVWG Chairs)
> tsvwg-chairs@ietf.org
>=20
>=20
>=20
>=20
>=20
>=20
>=20


From brian.e.carpenter@gmail.com  Wed Mar 20 01:10:47 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA2D921F8B80 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 01:10:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.306
X-Spam-Level: 
X-Spam-Status: No, score=-100.306 tagged_above=-999 required=5 tests=[AWL=-1.385, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y7h+pdb4wa6O for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 01:10:47 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id DA6B221F8B58 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 01:10:46 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id hm11so5344019wib.1 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 01:10:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=aSAq9hurqxQFj5wGIWE6J63eVnd7L5b6UIKnyavsJVw=; b=OSJ7Y+lCpdj3xseZVEEqOy2W5jlOWCTWba9BSgJdkZaphTuigFEZWj8zxd7qQ7Lifn 1r+1XfK44Py0pI+SHV70YMz8byuw5Vh9yU9MY3CGAF6UkVTCOyQV/ANq3LYxJpKQREQX zr4gPxN3+P+0qf1AWeDAhebebqUu0aaXQYE9FlOfNkD+9HkjydqsNKUsMcpR39jDsOYL x84/s8xQWWePb4jumLzyOM7YakM7q3Bs/EccJLTXJh2/2ZLOKbqzOPise2HO7JZ8Vsy7 ESdl8BqrKcrs5WpK/RMIf42NCuoQUXKYyR7U1Ar2zT4/icoQKTad7iQHIFpXSoLPLKRJ KSgA==
X-Received: by 10.194.157.42 with SMTP id wj10mr8694012wjb.12.1363767046060; Wed, 20 Mar 2013 01:10:46 -0700 (PDT)
Received: from [192.168.1.64] (host-2-102-218-109.as13285.net. [2.102.218.109]) by mx.google.com with ESMTPS id du2sm5359358wib.0.2013.03.20.01.10.44 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 Mar 2013 01:10:45 -0700 (PDT)
Message-ID: <51496F0C.7060806@gmail.com>
Date: Wed, 20 Mar 2013 08:10:52 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: James Polk <jmpolk@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>	<CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM>	<5147A974.4030100@isi.edu>	<CA7A7C64CC4ADB458B74477EA99DF6F5016A67F13B@HE111643.EMEA1.CDS.T-INTERNAL.COM> <201303192038.r2JKcwaA011488@rcdn-core2-6.cisco.com>
In-Reply-To: <201303192038.r2JKcwaA011488@rcdn-core2-6.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: tsvwg@ietf.org, touch@isi.edu
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 08:10:48 -0000

On 19/03/2013 20:38, James Polk wrote:
> At 02:50 AM 3/19/2013, Ruediger.Geib@telekom.de wrote:
>> There's still a possibility of decoupling class names from application=
s.
>>
>> pro: we don't run into problems like the one described by Joe.
>> con: nobody can imagine what that class would be good for by just
>>      reading the name. Readers must be educated.
>>
>> The application decoupled class name I've suggested is "Priority".
>=20
> Nitpicking - that sends the wrong message, as DiffServ is *not* a
> priority service, it is a differentiated service. Brian C. is quick to
> point this out...

Now I don't need to ;-)

   Brian

> James
>=20
>=20
>> Regards,
>>
>> R=C3=BCdiger
>>
>>
>>
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@isi.edu]
>> Sent: Tuesday, March 19, 2013 12:56 AM
>> To: Geib, R=C3=BCdiger
>> Cc: david.black@emc.com; tsvwg@ietf.org
>> Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
>>
>> Audio is a horrible name; the requirements for Pandora are completely
>> different from Skype.
>>
>> Maybe "audio interactive" (vs. audio streaming)?
>>
>> Joe
>>
>> On 3/18/2013 8:45 AM, Ruediger.Geib@telekom.de wrote:
>> > I don't object to broadening the name of a service class. As
>> mentioned earlier,
>> > I don't like transport QoS classes being named close to
>> applications. So
>> > weak objections against (1).
>> >
>> > Brian Carpenter didn't seem to favor (2) prior to the meeting. I
>> personally think,
>> > classes Priority (here: audio) and Bulk Inelastic require admission
>> control
>> > in access networks or some kind of TE in backbone sections. So to me=
 EF
>> > already requires admission control and I don't think another PHB wit=
h
>> > otherwise identical properties adds a lot of value. But well, that's=

>> my view.
>> > Could an argument be given why Voice-Admit is required? I hope that
>> has been
>> > discussed during the meeting.
>> >
>> > Regards,
>> >
>> > R=C3=BCdiger
>> >
>> >
>> > -----Original Message-----
>> > From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On
>> Behalf Of Black, David
>> > Sent: Friday, March 15, 2013 1:36 PM
>> > To: tsvwg@ietf.org
>> > Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>> >
>> > The discussion of the Audio service class in the RFC 4594 update
>> > draft in the tsvwg meeting yesterday reached a couple of initial
>> > conclusions that need to be checked on the list:
>> >
>> > (1) The class is being renamed from "Telephony" to "Audio", in part
>> > because "Telephony" is interpreted to include video in some contexts=

>> > and that's not intended here.  There have also been some slight
>> > changes/generalizations to the description.
>> >
>> > (2) The newly-standardized Voice-Admit PHB is being added to the
>> > Audio class.
>> >
>> > In the absence of objection on the list, these directions will be
>> > confirmed as the rough consensus of the tsvwg WG - please comment.
>> >
>> > Thanks,
>> > --David
>> > ----------------------------------------------------
>> > David L. Black, Distinguished Engineer
>> > EMC Corporation, 176 South St., Hopkinton, MA  01748
>> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> > david.black@emc.com        Mobile: +1 (978) 394-7754
>> > ----------------------------------------------------
>> >
>> >
>=20
> .
>=20


From brian.e.carpenter@gmail.com  Wed Mar 20 01:18:19 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1777A21F8BC5 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 01:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.614
X-Spam-Level: 
X-Spam-Status: No, score=-99.614 tagged_above=-999 required=5 tests=[AWL=-0.693, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yxPkXepznn7x for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 01:18:18 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 9A92321F8BB3 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 01:18:16 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id r5so1050103wey.6 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 01:18:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=t7jvWauchZtN6nx4MR6qG6xVt53JzPGaCcv02SXhrVs=; b=qnCYp/ujYJlZhVB2auc426y1gfFw7uIKnYhu5oErY/uaDxsAUXI1dd4GhGyl1tWwbO 40y6di9fktYFtNcZbvDiFpwl/YXbQdUSH1tD+zoh6JWfav8W/eK3UEvMKVLyYmUJ8k9z XgGR1OriHq/1W6IazCHfPyNGt0qJ2ZyhV/76dAwV+I5AH+JIcWFGJYfxYogp+g/auV/2 g2M62Zdh0g3D2j1YqBG8khNRg7YkV18BHx8J33CBTGmt8BWdC9P63tJBu7bb6LA4oSTR Mii44Cill7qpYYHgcnoo7PjlwEcZv6zLUZslnpIycXjs7l+1Vo3e/RgzA7fPtiCcqIhP T56w==
X-Received: by 10.194.7.131 with SMTP id j3mr8628586wja.23.1363767495613; Wed, 20 Mar 2013 01:18:15 -0700 (PDT)
Received: from [192.168.1.64] (host-2-102-218-109.as13285.net. [2.102.218.109]) by mx.google.com with ESMTPS id dp5sm5384996wib.1.2013.03.20.01.18.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 Mar 2013 01:18:14 -0700 (PDT)
Message-ID: <514970AB.20606@gmail.com>
Date: Wed, 20 Mar 2013 08:17:47 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>	<8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "Fred Baker \(fred\)" <fred@cisco.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 08:18:19 -0000

On 20/03/2013 02:40, Black, David wrote:
> Hi Fred,
> 
>> I was unable to attend tsvwg at IETF 86 as it competed with a meeting I
>> presented in. I am told that there was a presentation in which folks argued
>> against having a class of traffic for routing traffic. I'd like to comment on
>> that.
> 
> The argument in particular is about whether a class of traffic is needed for
> Routing traffic across an interconnection of two carrier networks.

What am I missing? It seems blindingly obvious that the answer is yes
and that this is what CS6 and CS7 were intended for. Quoting RFC2474,
"  In addition, PHBs selected
   by codepoints '11x000' MUST give packets a preferential forwarding
   treatment by comparison to the PHB selected by codepoint '000000' to
   preserve the common usage of IP Precedence values '110' and '111' for
   routing traffic."

      Brian


> 
> The argument was teed up for discussion in this slide presented in connection
> with draft-geib-tsvwg-diffserv-intercon-02:
> 
> http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx
> 
> Thank you for the comments,
> --David
> 
>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of Fred
>> Baker (fred)
>> Sent: Tuesday, March 19, 2013 4:53 PM
>> To: tsvwg@ietf.org
>> Subject: [tsvwg] RFC 4594 update: Routing class
>>
>> I was unable to attend twvwg at IETF 86 as it competed with a meeting I
>> presented in. I am told that there was a presentation in which folks argued
>> against having a class of traffic for routing traffic. I'd like to comment on
>> that.
>>
>> The origin of a class of traffic for routing traffic was a bug. The Cisco 7000
>> had an issue with its offloaded forwarding cards, of which it had two. When
>> there was a route flap, it blew away the route cache and then rebuilt it in
>> response to traffic it needed to forward. In that implementation, that meant
>> that the Route Processor (the CPU) suddenly had all traffic from all sources
>> flooded into it. The impact of that was to make it very difficult for the RP
>> to actually re-populate the Route Cache. Doubleplus ungood. The work-around
>> was to rate-limit traffic from the line cards to the RP. However, rate
>> limiting the routing traffic worked against getting routing to stabilize, so
>> we marked routing traffic, and did not rate limit *it* from going to the RP.
>>
>> Fast forward nearly 20 years. We don't have that bug anymore, if anything
>> because nobody equipped with a right mind uses the Cisco 7000 any more.
>>
>> However...
>>
>> If we're going to discuss quality of service for any application, we are
>> making some fundamental assumptions. These include the concept of having
>> enough bandwidth and so on; we're managing traffic at points in time when peak
>> traffic loads on a millisecond scale create issues. One of those fundamental
>> issues is that routing must be current; if we're sending traffic on a route
>> that loops because the other guy updated his route table but we didn't, or
>> vice versa, or for which interface or next hop router is no longer there, we
>> can discuss jitter, rate, and loss to our heart's content - the application's
>> traffic isn't going to get there. At. All. And won't until routing stabilizes.
>>
>> The fundamental argument for a class of traffic for routing in 2013 is not
>> that routing requires certain jitter, rate, or etc characteristics; it is that
>> routing traffic (apart from AQM issues, see separate discussion on
>> aqm@ietf.org) should simply *not*be*dropped* in the normal course of business.
>> Routing is fundamental to all other services the network delivers, including
>> QoS, and including every networks's SLAs.
>>
>> Now, one can say that routing is between neighboring nodes, and a router is
>> able to do special things with traffic it itself originates. It is true that a
>> router can do special things with its own traffic, and they do. But BGP
>> Routing frequently goes from Route Arbiter to Route Arbiter instead of Router
>> to Router, which is to say through other routers between routing engines.
>> Traffic through other routers is traffic through other routers, not a router's
>> own traffic. It requires some form of end to end marking to protect it.
>> Something like a DSCP.
> 

From prvs=784114126=ankit.mahawar@tcs.com  Wed Mar 20 02:47:27 2013
Return-Path: <prvs=784114126=ankit.mahawar@tcs.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07FA421F88BC for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 02:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nxRthXn36n2d for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 02:47:26 -0700 (PDT)
Received: from inmumg02.tcs.com (Inmumg02.tcs.com [219.64.33.222]) by ietfa.amsl.com (Postfix) with ESMTP id C43F621F85B0 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 02:47:24 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.84,876,1355077800"; d="scan'208";a="131394360"
Received: from cdctdlpprotect3 (unknown [127.0.0.1]) by cdctdlpprotect3.localdomain (Service) with ESMTP id C43DCABE02 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 15:15:34 +0530 (IST)
Received: from inmumm13.tcs.com (unknown [172.17.9.193]) by cdctdlpprotect3.localdomain (Service) with ESMTP id 7F6CDABE15 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 15:15:34 +0530 (IST)
From: Ankit Mahawar <ankit.mahawar@tcs.com>
X-KeepSent: 2FAE4932:D8FCB5F8-65257B34:0035654D; type=4; name=$KeepSent
To: tsvwg@ietf.org
X-Mailer: Lotus Notes Release 8.5.2FP1 November 30, 2010
Message-ID: <OF2FAE4932.D8FCB5F8-ON65257B34.0035654D-65257B34.0035BC57@tcs.com>
Sender: Ankit Mahawar <ankit.mahawar@tcs.com>
Date: Wed, 20 Mar 2013 15:16:56 +0530
X-MIMETrack: Serialize by Router on InMumM13/TCS(Release 8.5.2FP4HF188 | September 13, 2012) at 03/20/2013 15:17:00
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Subject: [tsvwg] Query regarding heartbeat re-transmission pattern
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 09:49:47 -0000

Hi All ,

I have a basic query regarding SCTP heartbeat re-transmission pattern .

As per the RFC 4960 :

Furthermore, when its peer is multi-homed, an endpoint SHOULD try to
retransmit a chunk that timed out to an active destination transport
address that is different from the last destination address to which the
DATA chunk was sent.

Also,
When retransmitting data that timed out, if the endpoint is multi-homed, it
should consider each source-destination address pair in its retransmission
selection policy.  When retransmitting timed-out data, the endpoint should
attempt to pick the most divergent source-destination pair from the
original source-destination pair to which the packet was transmitted.

Suppose if we have multihomed SCTP endpoints A and B .

A                      B

a.a.a.p               b.b.b.p
a.a.a.s               b.b.b.s

If we transmit heartbeat from a.a.a.s to b.b.b.s and it is not acknowledged
so does it re-transmit it using the same src and destination or with
a.a.a.p to b.b.b.s.

Please help to understand .

Thanks

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you




From jsaldana@unizar.es  Wed Mar 20 03:34:31 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A37C521F8488 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 03:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lEMd3MqO4yXp for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 03:34:30 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 5D67E21F8481 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 03:34:30 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r2KAYKnO026513; Wed, 20 Mar 2013 11:34:21 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'James Polk'" <jmpolk@cisco.com>, "'Joe Touch'" <touch@isi.edu>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>	<CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM>	<5147A974.4030100@isi.edu>	<201303192031.r2JKV9Ko015659@rcdn-core-4.cisco.com>	<5148CD8A.4050408@isi.edu>	<201303192121.r2JLLnjf009800@rcdn-core2-6.cisco.com>	<5148D843.6030309@isi.edu> <201303192142.r2JLgrgg015865@rcdn-core-3.cisco.com>
In-Reply-To: <201303192142.r2JLgrgg015865@rcdn-core-3.cisco.com>
Date: Wed, 20 Mar 2013 11:34:31 +0100
Organization: Universidad de Zaragoza
Message-ID: <004201ce2556$8260cc00$87226400$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHAVz7zqB1kDcIbViyAoVNgS3e5YQI5GWb5AROxG6MBJVsD9QIU1iTKAe2bmQwCaomX5AKtTQdKmF2YfBA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 20 Mar 2013 10:34:31 -0000

James, Joe,

My two cents about online games traffic.

We have two things here:

- Game genres: First Person Shooters, MMORPGs, Real-time Strategy, Racing
- TCP or UDP usage

A short summary:

- First Person Shooters always use UDP (as far as I know). You have to shoot
and move really fast, so TCP is not an option. They implement loss
concealment algorithms. For example, Quake III can work with 35% packet
loss. FPS players will be angry with delays over 50ms.

- MMORPG almost always use TCP: For example, World of Warcraft uses TCP, and
it had 12 million players. However, some of them use UDP. MMORPG players can
tolerate 150 or 200 ms.

- Real-time strategy (RTS) can use either TCP or UDP. Since they don't have
really tight interactivity requirements, TCP could be suitable, but some of
them use UDP (e.g. 0 Anno Domini). RTS can tolerate up to 1 second.

- Racing games: The only one I have studied uses UDP (Auto Club Revolution)

My conclusions:
- The game genre determines the delay requirements. 
- Perhaps we cannot put together all the game genres
- The genre and the protocol (TCP/UDP) should be considered "orthogonal".
Otherwise things will get very complicated

Best regards,

Jose



> -----Mensaje original-----
> De: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] En nombre de
> James Polk
> Enviado el: martes, 19 de marzo de 2013 22:42
> Para: Joe Touch
> CC: tsvwg@ietf.org
> Asunto: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
> 
> At 04:27 PM 3/19/2013, Joe Touch wrote:
> 
> 
> >On 3/19/2013 2:21 PM, James Polk wrote:
> >>At 03:41 PM 3/19/2013, Joe Touch wrote:
> >...
> >>>Though "realtime interactive" sounds like it could include voice,
> >>>voice & video, and gaming - which aren't quite the same service
> >>>class, IMO.
> >>
> >>It's not, as gaming (still recommended in "realtime interactive"
> >>service
> >>class) is mostly TCP based, and we don't want to place TCP based
> >>anything in the same service class or queue with realtime UDP traffic.
> >
> >Gaming widely uses UDP. See a good example here:
> >
> >https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711
> >
> >http://www.practicallynetworked.com/sharing/app_port_list.htm
> >
> >Note how many games use *only* UDP.
> 
> Fair point. I wasn't claiming gaming only uses TCP, but that there were a
fair
> amount of gaming apps that use TCP, and I was making the comment from
> the perspective of "let's not stuff audio and video into that service
class as
> well if we don't have to, and we don't have to".
> 
> James
> 
> 
> >Joe
> >


From magnus.westerlund@ericsson.com  Wed Mar 20 05:57:01 2013
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C0CC21F8825 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 05:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.978
X-Spam-Level: 
X-Spam-Status: No, score=-105.978 tagged_above=-999 required=5 tests=[AWL=0.271, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDsvLQThBePD for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 05:57:00 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3A84B21F8539 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 05:56:59 -0700 (PDT)
X-AuditID: c1b4fb30-b7f0d6d000007e61-f2-5149b21a1653
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id B1.81.32353.A12B9415; Wed, 20 Mar 2013 13:56:58 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Wed, 20 Mar 2013 13:56:57 +0100
Message-ID: <5149B215.6050608@ericsson.com>
Date: Wed, 20 Mar 2013 13:56:53 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>, draft-ietf-tsvwg-sctp-dtls-encaps@tools.ietf.org
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLJMWRmVeSWpSXmKPExsUyM+Jvja7UJs9Ag/eXzSy23tjBaHHszV02 ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugStj14aXrAU3xSseTHrP1MA4TbiLkZNDQsBE 4uq9z4wQtpjEhXvr2boYuTiEBE4ySnTsO8QO4SxnlJi2rZ8FpIpXQFvi29eVTCA2i4CqxOnO r2wgNpuAhcTNH41gtqhAsMTPV2eg6gUlTs58AmaLCPhLLF/+nxnEFhYwl7j27h0TxGZJiS0v 2tlBbGYBPYkpV1sYIWx5ieats8HqhYD2NjR1sE5g5J+FZOwsJC2zkLQsYGRexciem5iZk15u vokRGGQHt/w22MG46b7YIUZpDhYlcd5w1wsBQgLpiSWp2ampBalF8UWlOanFhxiZODilGhh3 rfyt9tL5fuaUxt83DLMLz5d6blaJCAlzLJK7eXyCmmj9+QWmutfWbkj/wurYeCNybur2nzfc ThZEie0579GeJG1k6GIR8Orf2XjrLwqnU8WS5sVf/WCxKlhi5at7CoIPSliWcooWM2lu2iDc u2E+K2fOw+TH7YF3drFufP58fd1+VqUl4XuUWIozEg21mIuKEwHv9bhAAAIAAA==
Subject: [tsvwg] review of draft-ietf-tsvwg-sctp-dtls-encaps-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 12:57:01 -0000

Hi,

I have reviewed the SCTP in DTLS encapsulation draft and have some
comments.

1. Abstract:
SCTP
   over DTLS is used by the RTCWeb protocol suite for transporting non-
   media data between browsers.

I think if one likes to include something like this in the abstract one
should word it like "An initial usage of ..."

2. Section 5.5:
   The SCTP implementation MUST support the extension defined in
   [RFC3758].

I wonder why this is required in a protocol encapsulation declaration?
This specification is from my perspective a common tool that anyone that
has similar requirements as WebRTC can choose to use. CLUE WG is clearly
one with high probability to have need for UDP/DTLS/SCTP. However, I
don't yet know if CLUE for example has any requirements that requires
partial reliability.

So please explain why mandating the partial reliability is necessary for
a DTLS encapsulation of SCTP. I think it is fine for the RTCWEB data
channel document to mandate the support of the PR-SCTP extension in the
context of WebRTC. But, please try to have the correct specifications in
the appropriate places.

3. Section 5.6:
The same as 2) appears to be true also here. Are there reasons why one
needs this extension when one uses the DTLS encapsulation?

4. Section 5.7:
To my understanding this is a pure performance enchancement. Thus I
wonder over the SHOULD level of an extension that yet not exist. I think
it is fine to indicate the issue. And if you actually have a draft ready
do an informative reference. But I do question the need for a normative
reference here. Isn't it better to let this specification be published
in a timely fashion?

5. Section 5.8:
Yet another case of a potential issue when running in common context
with real-time applications. This encapsulation does not in any way is
solely for real-time applications. Thus I think both using MAY is
unwarranted and I question how necessary this whole discussion are.

I think this document is suffering from an issue of not getting the
correct separation between the documents. This needs to specify the DTLS
encapsualtion of SCTP and what is needed. But I think is the wrong place
to have requirements on SCTP extensions that are specific in the context
of particular applications or class of applications. So please ensure
that you have the basics of the encapsulation in place, then ensure that
the extensions can be negotiated and allow the applications to make the
choices it needs on what features of SCTP it requires.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
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 fred@cisco.com  Wed Mar 20 09:28:05 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50D5B21F8F09 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 09:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.32
X-Spam-Level: 
X-Spam-Status: No, score=-110.32 tagged_above=-999 required=5 tests=[AWL=0.279, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rvnQzMRwM8tK for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 09:28:03 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 7D67121F8F06 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 09:28:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4334; q=dns/txt; s=iport; t=1363796882; x=1365006482; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=wsiZpHRZf7yRayRYXT4HnNRwBIVkBYdkd8xyzEpyy7s=; b=QXqh+n2eIgHpv9U1pVth/wTO6qeynjqHbs3Cr4TvJHtvkVrICs+Yn2TL HtAXNRdqLruXgxX8TE3ZP3kZtbkDLv/0GlcoYUt1Ao47B7lTQUYsZmwUW OcnP6I82tg+SarEDXhRPFkzAjCL8MCGOde2eM/WnEuEJ/PXOqtXZkiQEs 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFALnhSVGtJV2a/2dsb2JhbABDxRuBTxZ0giQBAQEDATotEgUHBAIBCBEEAQELFAkHMhQJCAIEDgUIAYgFBgzCWI1agQICJgsHBoJZYQOnYoMKgWs9
X-IronPort-AV: E=Sophos;i="4.84,879,1355097600"; d="scan'208";a="189632392"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP; 20 Mar 2013 16:28:00 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2KGS0nL004746 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 20 Mar 2013 16:28:00 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Wed, 20 Mar 2013 11:27:59 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "Black, David" <david.black@emc.com>
Thread-Topic: RFC 4594 update: Routing class
Thread-Index: AQHOJYfijVsJ14jO/06S/pwXWNapwQ==
Date: Wed, 20 Mar 2013 16:27:59 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.125.235]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <00E835988AF0474A88686F92C4016647@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 16:28:07 -0000

On Mar 19, 2013, at 7:40 PM, "Black, David" <david.black@emc.com> wrote:

> Hi Fred,
>=20
>> I was unable to attend tsvwg at IETF 86 as it competed with a meeting I
>> presented in. I am told that there was a presentation in which folks arg=
ued
>> against having a class of traffic for routing traffic. I'd like to comme=
nt on
>> that.
>=20
> The argument in particular is about whether a class of traffic is needed =
for
> Routing traffic across an interconnection of two carrier networks.
>=20
> The argument was teed up for discussion in this slide presented in connec=
tion
> with draft-geib-tsvwg-diffserv-intercon-02:
>=20
> http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx

My only comment on that slide is that the story I told in my previous note =
happened on inter-provider links. The slide is correct that there is not a =
defined class in 5127 for admitted video traffic.

> Thank you for the comments,
> --David
>=20
>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf O=
f Fred
>> Baker (fred)
>> Sent: Tuesday, March 19, 2013 4:53 PM
>> To: tsvwg@ietf.org
>> Subject: [tsvwg] RFC 4594 update: Routing class
>>=20
>> I was unable to attend twvwg at IETF 86 as it competed with a meeting I
>> presented in. I am told that there was a presentation in which folks arg=
ued
>> against having a class of traffic for routing traffic. I'd like to comme=
nt on
>> that.
>>=20
>> The origin of a class of traffic for routing traffic was a bug. The Cisc=
o 7000
>> had an issue with its offloaded forwarding cards, of which it had two. W=
hen
>> there was a route flap, it blew away the route cache and then rebuilt it=
 in
>> response to traffic it needed to forward. In that implementation, that m=
eant
>> that the Route Processor (the CPU) suddenly had all traffic from all sou=
rces
>> flooded into it. The impact of that was to make it very difficult for th=
e RP
>> to actually re-populate the Route Cache. Doubleplus ungood. The work-aro=
und
>> was to rate-limit traffic from the line cards to the RP. However, rate
>> limiting the routing traffic worked against getting routing to stabilize=
, so
>> we marked routing traffic, and did not rate limit *it* from going to the=
 RP.
>>=20
>> Fast forward nearly 20 years. We don't have that bug anymore, if anythin=
g
>> because nobody equipped with a right mind uses the Cisco 7000 any more.
>>=20
>> However...
>>=20
>> If we're going to discuss quality of service for any application, we are
>> making some fundamental assumptions. These include the concept of having
>> enough bandwidth and so on; we're managing traffic at points in time whe=
n peak
>> traffic loads on a millisecond scale create issues. One of those fundame=
ntal
>> issues is that routing must be current; if we're sending traffic on a ro=
ute
>> that loops because the other guy updated his route table but we didn't, =
or
>> vice versa, or for which interface or next hop router is no longer there=
, we
>> can discuss jitter, rate, and loss to our heart's content - the applicat=
ion's
>> traffic isn't going to get there. At. All. And won't until routing stabi=
lizes.
>>=20
>> The fundamental argument for a class of traffic for routing in 2013 is n=
ot
>> that routing requires certain jitter, rate, or etc characteristics; it i=
s that
>> routing traffic (apart from AQM issues, see separate discussion on
>> aqm@ietf.org) should simply *not*be*dropped* in the normal course of bus=
iness.
>> Routing is fundamental to all other services the network delivers, inclu=
ding
>> QoS, and including every networks's SLAs.
>>=20
>> Now, one can say that routing is between neighboring nodes, and a router=
 is
>> able to do special things with traffic it itself originates. It is true =
that a
>> router can do special things with its own traffic, and they do. But BGP
>> Routing frequently goes from Route Arbiter to Route Arbiter instead of R=
outer
>> to Router, which is to say through other routers between routing engines=
.
>> Traffic through other routers is traffic through other routers, not a ro=
uter's
>> own traffic. It requires some form of end to end marking to protect it.
>> Something like a DSCP.


From Ruediger.Geib@telekom.de  Wed Mar 20 11:47:58 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BED3711E80D9 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 11:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U17MKVORf4o1 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 11:47:58 -0700 (PDT)
Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) by ietfa.amsl.com (Postfix) with ESMTP id 6D42011E80D5 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 11:47:57 -0700 (PDT)
Received: from he113470.emea1.cds.t-internal.com ([10.134.93.128]) by tcmail91.telekom.de with ESMTP/TLS/AES128-SHA; 20 Mar 2013 19:47:40 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113470.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 20 Mar 2013 19:47:40 +0100
From: <Ruediger.Geib@telekom.de>
To: <fred@cisco.com>, <david.black@emc.com>
Date: Wed, 20 Mar 2013 19:47:39 +0100
Thread-Topic: RFC 4594 update: Routing class
Thread-Index: AQHOJYfijVsJ14jO/06S/pwXWNapwZiu53Aw
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 18:47:58 -0000

David, Fred,

an appropriate class for routing is envisaged by Y.1566
and my draft is based on Y.1566. In fact, marking routing
traffic by CS6 was easy to agree.

The question is, how to treat traffic marked by CS6 at
interconnection links. David originally objected to having
such a routing class at interconnecton. I think we need
some discussion.

Routing information should be transmitted free of loss.
That could mean an own class marked by CS6, that could be
any other class resulting in low loss for TCP based
traffic. One could map this traffic from CS6 to
another fitting class and PHB, like Assured AF31.

There's also an issue with VPN treatment. Providers may
prefer not to transport customer routing traffic together
with their own routing traffic.

It may be good to add some text in -03 of my draft.
Objections?

Regards,

R=FCdiger


-----Original Message-----
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of F=
red Baker (fred)
Sent: Wednesday, March 20, 2013 5:28 PM
To: Black, David
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Routing class


On Mar 19, 2013, at 7:40 PM, "Black, David" <david.black@emc.com> wrote:

> Hi Fred,
>
>> I was unable to attend tsvwg at IETF 86 as it competed with a meeting I
>> presented in. I am told that there was a presentation in which folks arg=
ued
>> against having a class of traffic for routing traffic. I'd like to comme=
nt on
>> that.
>
> The argument in particular is about whether a class of traffic is needed =
for
> Routing traffic across an interconnection of two carrier networks.
>
> The argument was teed up for discussion in this slide presented in connec=
tion
> with draft-geib-tsvwg-diffserv-intercon-02:
>
> http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx

My only comment on that slide is that the story I told in my previous note =
happened on inter-provider links. The slide is correct that there is not a =
defined class in 5127 for admitted video traffic.

> Thank you for the comments,
> --David
>
>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf O=
f Fred
>> Baker (fred)
>> Sent: Tuesday, March 19, 2013 4:53 PM
>> To: tsvwg@ietf.org
>> Subject: [tsvwg] RFC 4594 update: Routing class
>>
>> I was unable to attend twvwg at IETF 86 as it competed with a meeting I
>> presented in. I am told that there was a presentation in which folks arg=
ued
>> against having a class of traffic for routing traffic. I'd like to comme=
nt on
>> that.
>>
>> The origin of a class of traffic for routing traffic was a bug. The Cisc=
o 7000
>> had an issue with its offloaded forwarding cards, of which it had two. W=
hen
>> there was a route flap, it blew away the route cache and then rebuilt it=
 in
>> response to traffic it needed to forward. In that implementation, that m=
eant
>> that the Route Processor (the CPU) suddenly had all traffic from all sou=
rces
>> flooded into it. The impact of that was to make it very difficult for th=
e RP
>> to actually re-populate the Route Cache. Doubleplus ungood. The work-aro=
und
>> was to rate-limit traffic from the line cards to the RP. However, rate
>> limiting the routing traffic worked against getting routing to stabilize=
, so
>> we marked routing traffic, and did not rate limit *it* from going to the=
 RP.
>>
>> Fast forward nearly 20 years. We don't have that bug anymore, if anythin=
g
>> because nobody equipped with a right mind uses the Cisco 7000 any more.
>>
>> However...
>>
>> If we're going to discuss quality of service for any application, we are
>> making some fundamental assumptions. These include the concept of having
>> enough bandwidth and so on; we're managing traffic at points in time whe=
n peak
>> traffic loads on a millisecond scale create issues. One of those fundame=
ntal
>> issues is that routing must be current; if we're sending traffic on a ro=
ute
>> that loops because the other guy updated his route table but we didn't, =
or
>> vice versa, or for which interface or next hop router is no longer there=
, we
>> can discuss jitter, rate, and loss to our heart's content - the applicat=
ion's
>> traffic isn't going to get there. At. All. And won't until routing stabi=
lizes.
>>
>> The fundamental argument for a class of traffic for routing in 2013 is n=
ot
>> that routing requires certain jitter, rate, or etc characteristics; it i=
s that
>> routing traffic (apart from AQM issues, see separate discussion on
>> aqm@ietf.org) should simply *not*be*dropped* in the normal course of bus=
iness.
>> Routing is fundamental to all other services the network delivers, inclu=
ding
>> QoS, and including every networks's SLAs.
>>
>> Now, one can say that routing is between neighboring nodes, and a router=
 is
>> able to do special things with traffic it itself originates. It is true =
that a
>> router can do special things with its own traffic, and they do. But BGP
>> Routing frequently goes from Route Arbiter to Route Arbiter instead of R=
outer
>> to Router, which is to say through other routers between routing engines=
.
>> Traffic through other routers is traffic through other routers, not a ro=
uter's
>> own traffic. It requires some form of end to end marking to protect it.
>> Something like a DSCP.


From jmpolk@cisco.com  Wed Mar 20 11:54:04 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11BAF21F856D for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 11:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.09
X-Spam-Level: 
X-Spam-Status: No, score=-111.09 tagged_above=-999 required=5 tests=[AWL=0.723, BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_HI=-8, SARE_OBFU_PART_INA=0.786, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qpFay5FVB2Sx for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 11:54:00 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 626BD21F8615 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 11:54:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6515; q=dns/txt; s=iport; t=1363805640; x=1365015240; h=message-id:date:to:from:subject:mime-version: content-transfer-encoding; bh=4Fzh2Cog4tYjfGVvtbGDGYPK2+9st+liEkK/RDueTx8=; b=Hf0KKe/5c8vqrhg7dEFooaREj3v5CazGb1JKCC+BrUreR3fdFen1PhMj HoPNAg+g13UJywSXAdWxVj2sKLelUwDMAZkeS6hzj67H8PCGLQRxzAUXo w5IWYNiz7hOPCyd+ASMyWtKbmCi2oPqzAGCRrYAx4Cfp99lOLzhgndFc0 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAEkESlGtJV2Z/2dsb2JhbABExSKBUhZ0giQBAQEFAQEJLDYEFQkVAwECCh4WCgIMHwcCIYgUDKEyoR4EBI1bgSWDUgOIPzaebYMoHoE3
X-IronPort-AV: E=Sophos;i="4.84,880,1355097600"; d="scan'208";a="189629829"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 20 Mar 2013 18:53:57 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2KIrvQk029906 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 20 Mar 2013 18:53:57 GMT
Message-Id: <201303201853.r2KIrvQk029906@rcdn-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 20 Mar 2013 13:53:27 -0500
To: tsvwg@ietf.org
From: James Polk <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Authenticated-User: jmpolk
Subject: [tsvwg] Fwd: [MMUSIC] Review of draft-ietf-mmusic-sctp-sdp-03
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 18:54:04 -0000

<chair hat on>

this review by Magnus might be of interest to some in this WG.

please comment on the MMUSIC list though, for=20
those WG chair's to be aware of your support/comments, concerns, or=
 whatever...

James

>Date: Wed, 20 Mar 2013 16:11:38 +0100
>From: Magnus Westerlund <magnus.westerlund@ericsson.com>
>To: "mmusic (E-mail)" <mmusic@ietf.org>,
>         <draft-ietf-mmusic-sctp-sdp@tools.ietf.org>
>Subject: [MMUSIC] Review of draft-ietf-mmusic-sctp-sdp-03
>
>
>Hi,
>
>I have reviewed the SDP description of SCTP and have some comments and
>suggestions.
>
>1. My first comments is a very general one and concerns the relationship
>between the proposed SCTP related proto identifiers and ICE for the
>DTLS/SCTP encapsulation.
>
>When ICE was defined it was natural to include ICE by reftorfitting it
>to existing proto identifiers. However, given that this specification
>intorduce a number of new identifiers I do woner if we should be more
>explicit about the ICE usage in the proto field. I think have both pro
>and cons for this.
>
>So my considerations is basically to include specification of
>ICE/DTLS/SCTP, where the lower layer transport is defined by what ICE
>agrees on. This makes a lot of sense given that ICE can in fact arrive
>on the usage of TCP/framing/DTLS/SCTP, TCP/TURN/DTLS/SCTP in addition to
>more expected choices as UDP/DTLS/SCTP. This makes it clears that you do
>require ICE to negotiate this transport flow. At the same time it is a
>significant downside if ones negotiation needs are to chose between
>using ICE or a specific lower layer transport.
>
>These comments doesn't apply when one runs SCTP on top of IP.
>
>2. Section 1:
>RFC4145 [RFC4145] specifies a general mechanism for
>    describing and establishing TCP (Transmission Control Protocol)
>    streams.
>
>I do dislike that usage of the RFC number as the explanation of what the
>referenced document is. The previous sentence is how I prefer it to be
>done:
>    SDP (Session Description Protocol) [RFC4566] provides a general-
>    purpose format for describing multimedia sessions in announcements or
>    invitations.
>
>Use the document title or an abbreviated explanation for what the
>referenced document specifies and one gets much better flow in the
>reading as one don't have stop look up the reference to find out what is
>referred to.
>
>3. Section 1:
>I think having first a paragraph for SCTP and then having "Additionaly
>.." with the other two protos are bit strange. Why not simpley say. This
>document defines three proto identifiers: list of them with explnation.
>
>4. Section 1:
>    DTLS/SCTP :  to allow the usage of SCTP on top of the Datagram
>       Transport Layer Security (DTLS) protocol, as defined in
>       [I-D.tuexen-tsvwg-sctp-dtls-encaps], using SDP.  SCTP over DTLS is
>       used by the RTCWeb protocol suite for transporting non- media data
>       between browsers.
>
>This definitions says nothing of the lower transport layer for DTLS/SCTP
>even if UDP is referred to in a later section. I think this needs to be
>clarified and discussed in the context of which lower layers do we
>expect to be supported? From my perspective I think two makes sense.
>ICE/DTLS/SCTP that allows ICE to negoiate what ever and then
>UDP/DTSL/SCTP that only uses UDP as lower layer. Lets other add other
>variants in the future if needed.
>
>5. Section 3:
>    The 'DTLS/SCTP' protocol identifier indicates that the media
>    described will use SCTP on top of the Datagram Transport Layer
>    Security (DTLS) protocol as specified in
>    [I-D.tuexen-tsvwg-sctp-dtls-encaps].
>
>I would like to point out that the referenced document does not at all
>indicate what lower layer is being used under DTLS.
>
>6. Section 4.1:
>
>This section discuss the usage of the "data channels" within the SCTP
>association. My personal position is that for the moment this appears to
>be unnecessary. The most important part is the SCTP association
>establishment. Then one can discuss the general application using the
>SCTP association as whole. Examples of such are WebRTC data channel.
>
>If anyone want stream level information in SDP then I propose that this
>is handled as a extension to this signaling, not an from the start
>included functionality as we don't appear to have clear requirement for
>that.
>
>7. Section 4.2:
>
>What are the requirements behind being able to establish multiple SCTP
>association over the same DTLS connection? I am very unclear why this
>would be required, and if not really needed I would suggest keeping
>things simple.
>
>8. Section 4.3: I guess this can for the moment be removed as it appears
>to be taken care in other places, such as the RTCWEB WG data channel
>protocol proposal.
>
>9. If you are removing the multiple association and the "data channel"
>parameters then most of the issues in section 5 vanish. If not I have
>additional feedback on this section.
>
>10. Section 8.
>
>    Current NATs do not typically support SCTP.  As an alternative to
>    design SCTP specific NATs, Encapsulating SCTP into UDP
>    [I-D.tuexen-sctp-udp-encaps] makes it possible to use SCTP in
>    networks with legacy NAT and firewalls not supporting SCTP.
>
>First of all, there is a WG version for this document:
>draft-ietf-tsvwg-sctp-udp-encaps-14. Which is in IESG evaluation. Thus I
>wonder why signalling for this is not included when all the other
>options are included, even less mature ones then this?
>
>To me it looks like this document need to have some high level decisions
>on what to include and not and then try to finish it up within the
>agreed constraints. From my perspective I think it should focus on a
>single SCTP association per m=3D line and the actual SCTP association.
>
>Cheers
>
>Magnus Westerlund
>
>----------------------------------------------------------------------
>Multimedia Technologies, Ericsson Research EAB/TVM
>----------------------------------------------------------------------
>Ericsson AB                | Phone  +46 10 7148287
>F=E4r=F6gatan 6                | Mobile +46 73 0949079
>SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
>----------------------------------------------------------------------
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www.ietf.org/mailman/listinfo/mmusic


From Ruediger.Geib@telekom.de  Wed Mar 20 11:56:12 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B7C221F8A27 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 11:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.749
X-Spam-Level: 
X-Spam-Status: No, score=-2.749 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C1aZCjmQNOkG for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 11:56:11 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [80.149.113.247]) by ietfa.amsl.com (Postfix) with ESMTP id 722B521F8A0D for <tsvwg@ietf.org>; Wed, 20 Mar 2013 11:56:11 -0700 (PDT)
Received: from he113675.emea1.cds.t-internal.com ([10.134.99.28]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 20 Mar 2013 19:56:10 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113675.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 20 Mar 2013 19:56:09 +0100
From: <Ruediger.Geib@telekom.de>
To: <fred@cisco.com>, <jmpolk@cisco.com>
Date: Wed, 20 Mar 2013 19:56:08 +0100
Thread-Topic: [tsvwg] RFC 4594 update: Audio class - consensus check
Thread-Index: AQHOJPWpaOrj+X+sQ0SpFjfdVcwBU5iu7acw
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE22@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5147A974.4030100@isi.edu> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F13B@HE111643.EMEA1.CDS.T-INTERNAL.COM> <201303192038.r2JKcwaA011488@rcdn-core2-6.cisco.com> <8C48B86A895913448548E6D15DA7553B7DC5BB@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7DC5BB@xmb-rcd-x09.cisco.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg@ietf.org, touch@isi.edu
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 18:56:12 -0000

Fred, James

RG>> The application decoupled class name I've suggested is "Priority".
>
JP> Nitpicking - that sends the wrong message, as DiffServ is *not* a prior=
ity service, it is a differentiated service. Brian C. is quick to point thi=
s out...

FB: More than a nitpick. This is actually important.

RG: Propose any name not linking this class to an application
    or application aggregate. That's difficult, at least for me.

FB: I suspect that calling it "priority" will have every idiot
    on the planet trying to use it for his or her pet application
    without regard to the service it offers or what their
    application's specific needs are.

RG: You clearly underestimate the bunch. They can read SLA numbers
    by now. It doesn't matter how you call the class.

Regards,

R=FCdiger

From Ruediger.Geib@telekom.de  Wed Mar 20 12:12:28 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5685A11E80EE for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 12:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.149
X-Spam-Level: 
X-Spam-Status: No, score=-3.149 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qFtsZwdY1BdJ for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 12:12:25 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id F0C6521F89E9 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 12:12:24 -0700 (PDT)
Received: from he113656.emea1.cds.t-internal.com ([10.134.99.16]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 20 Mar 2013 20:12:22 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113656.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 20 Mar 2013 20:12:22 +0100
From: <Ruediger.Geib@telekom.de>
To: <jmpolk@cisco.com>, <david.black@emc.com>
Date: Wed, 20 Mar 2013 20:12:21 +0100
Thread-Topic: [tsvwg] RFC 4594 update: Audio class - consensus check
Thread-Index: Ac4k3qno2ahQmI8fTWOA0E8qVp0yfQAvhOPA
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE28@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <201303192016.r2JKGZop008123@rcdn-core2-1.cisco.com>
In-Reply-To: <201303192016.r2JKGZop008123@rcdn-core2-1.cisco.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 19:12:28 -0000

James, David

I'm going to read 5865, once time allows. Just another
remark on EF and about definitions of network
sections:

- Backbone: no interface below Gbit/s.
- Access & Aggregation: Mbit/s to customer, but also
  lower Gbit/s, controlled by a network provider.
- in home network and LAN: customer domain.

I expect EF to be admission controlled in the network
provider domain (access, aggregation and backbone).

EF and voice-admit are identical in the network
provider domain and James would say rather similar,
but not identical from an overall perspective.
Am I completely wrong?

Regards,

R=FCdiger

>But well, that's my view.
>Could an argument be given why Voice-Admit is required? I hope that has be=
en
>discussed during the meeting.

It has. It is an RFC from this WG. Please review
RFC 5865. It's the singular purpose topic of that
RFC. Given that DSCP and PHB already exist, where
do they go in the service classes, in a new
service class, or the one shared with Audio?

James


>Regards,
>
>R=FCdiger
>
>
>-----Original Message-----
>From: tsvwg-bounces@ietf.org
>[mailto:tsvwg-bounces@ietf.org] On Behalf Of Black, David
>Sent: Friday, March 15, 2013 1:36 PM
>To: tsvwg@ietf.org
>Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>
>The discussion of the Audio service class in the RFC 4594 update
>draft in the tsvwg meeting yesterday reached a couple of initial
>conclusions that need to be checked on the list:
>
>(1) The class is being renamed from "Telephony" to "Audio", in part
>because "Telephony" is interpreted to include video in some contexts
>and that's not intended here.  There have also been some slight
>changes/generalizations to the description.
>
>(2) The newly-standardized Voice-Admit PHB is being added to the
>Audio class.
>
>In the absence of objection on the list, these directions will be
>confirmed as the rough consensus of the tsvwg WG - please comment.
>
>Thanks,
>--David
>----------------------------------------------------
>David L. Black, Distinguished Engineer
>EMC Corporation, 176 South St., Hopkinton, MA  01748
>+1 (508) 293-7953             FAX: +1 (508) 293-7786
>david.black@emc.com        Mobile: +1 (978) 394-7754
>----------------------------------------------------


From rs@netapp.com  Wed Mar 20 12:19:19 2013
Return-Path: <rs@netapp.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEF4111E80F4 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 12:19:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.351
X-Spam-Level: 
X-Spam-Status: No, score=-10.351 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XiY854ooYWio for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 12:19:19 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 426BC11E80F6 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 12:19:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.84,880,1355126400"; d="scan'208";a="32428254"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 20 Mar 2013 12:19:19 -0700
Received: from vmwexceht05-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r2KJJIBl000737; Wed, 20 Mar 2013 12:19:19 -0700 (PDT)
Received: from SACEXCMBX02-PRD.hq.netapp.com ([169.254.1.222]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0342.003; Wed, 20 Mar 2013 12:19:18 -0700
From: "Scheffenegger, Richard" <rs@netapp.com>
To: Ankit Mahawar <ankit.mahawar@tcs.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] Query regarding heartbeat re-transmission pattern
Thread-Index: AQHOJVBFWnTl+OQskEW70ry2X+WMjZiu9Gzw
Date: Wed, 20 Mar 2013 19:19:17 +0000
Message-ID: <012C3117EDDB3C4781FD802A8C27DD4F24AC0CB5@SACEXCMBX02-PRD.hq.netapp.com>
References: <OF2FAE4932.D8FCB5F8-ON65257B34.0035654D-65257B34.0035BC57@tcs.com>
In-Reply-To: <OF2FAE4932.D8FCB5F8-ON65257B34.0035654D-65257B34.0035BC57@tcs.com>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.115]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [tsvwg] Query regarding heartbeat re-transmission pattern
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 19:19:20 -0000

Hi Ankit,

is it only the heartbeat that failed (are there other packets flowing betwe=
en A.p to B.p), in your scenario?

I would read the 2nd fragment of text, that if A.s to B.s failed, a retrans=
mission (of data) should be checked between A.p to B.p first; other (possib=
le) combinations, like A.p -> B.s, or A.s -> B.p later...

Regards,

Richard Scheffenegger

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Ankit Mahawar
> Sent: Mittwoch, 20. M=E4rz 2013 10:47
> To: tsvwg@ietf.org
> Subject: [tsvwg] Query regarding heartbeat re-transmission pattern
>=20
>=20
> Hi All ,
>=20
> I have a basic query regarding SCTP heartbeat re-transmission pattern .
>=20
> As per the RFC 4960 :
>=20
> Furthermore, when its peer is multi-homed, an endpoint SHOULD try to
> retransmit a chunk that timed out to an active destination transport
> address that is different from the last destination address to which the
> DATA chunk was sent.
>=20
> Also,
> When retransmitting data that timed out, if the endpoint is multi-homed,
> it
> should consider each source-destination address pair in its retransmissio=
n
> selection policy.  When retransmitting timed-out data, the endpoint shoul=
d
> attempt to pick the most divergent source-destination pair from the
> original source-destination pair to which the packet was transmitted.
>=20
> Suppose if we have multihomed SCTP endpoints A and B .
>=20
> A                      B
>=20
> a.a.a.p               b.b.b.p
> a.a.a.s               b.b.b.s
>=20
> If we transmit heartbeat from a.a.a.s to b.b.b.s and it is not
> acknowledged
> so does it re-transmit it using the same src and destination or with
> a.a.a.p to b.b.b.s.
>=20
> Please help to understand .
>=20
> Thanks
>=20
> =3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>=20
>=20


From Ruediger.Geib@telekom.de  Wed Mar 20 12:28:45 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 119F121F8493 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 12:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.166
X-Spam-Level: 
X-Spam-Status: No, score=-3.166 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pCqaMB3+sZQj for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 12:28:44 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF3611E80FD for <tsvwg@ietf.org>; Wed, 20 Mar 2013 12:28:43 -0700 (PDT)
Received: from he113443.emea1.cds.t-internal.com ([10.134.93.103]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 20 Mar 2013 20:28:42 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113443.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 20 Mar 2013 20:28:42 +0100
From: <Ruediger.Geib@telekom.de>
To: <jsaldana@unizar.es>
Date: Wed, 20 Mar 2013 20:28:42 +0100
Thread-Topic: [tsvwg] RFC 4594 update: Audio class - consensus check
Thread-Index: AQHAVz7zqB1kDcIbViyAoVNgS3e5YQI5GWb5AROxG6MBJVsD9QIU1iTKAe2bmQwCaomX5AKtTQdKmF2YfBCAAJR2cA==
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE2F@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67F02E@HE111643.EMEA1.CDS.T-INTERNAL.COM> <5147A974.4030100@isi.edu> <201303192031.r2JKV9Ko015659@rcdn-core-4.cisco.com> <5148CD8A.4050408@isi.edu> <201303192121.r2JLLnjf009800@rcdn-core2-6.cisco.com> <5148D843.6030309@isi.edu> <201303192142.r2JLgrgg015865@rcdn-core-3.cisco.com> <004201ce2556$8260cc00$87226400$@unizar.es>
In-Reply-To: <004201ce2556$8260cc00$87226400$@unizar.es>
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
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 19:28:45 -0000

Jose,

thanks for your information. I'd prefer classes to be
described in terms of designed for traffic with /
without retransmits. But there's admission control too,
and I never heard of a game signling SIP or RSVP.
I think QoS for games requires more discussion.

Classes with properties suiting the requirements you
describe are specified.

Regards,

R=FCdiger

From fred@cisco.com  Wed Mar 20 12:53:20 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 903E311E80F9 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 12:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.341
X-Spam-Level: 
X-Spam-Status: No, score=-110.341 tagged_above=-999 required=5 tests=[AWL=0.258, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id avUgKJmUNJMs for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 12:53:19 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0827E11E80CC for <tsvwg@ietf.org>; Wed, 20 Mar 2013 12:53:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6227; q=dns/txt; s=iport; t=1363809198; x=1365018798; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=1d5R5NRn0I0CHin37vThOHKCk9VJsYvA2kjRd+Aasfs=; b=fatmx6PFwgwaFHFrqgzeA5F6MKYTTbvElAIl8bSAjAkh+7WfK/Pc0nOu OzH0sNxXfVuqJj8i36xWoudRtAG7Kb97qYPshyhRqZb/Lz7Y4kPGqJiTI jzhbJQ+UyESRcZ6RQVvT6TQmjgKlPTbAgOjmlJXLA/FV93xcBVvsysMEs o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAAgSSlGtJXG9/2dsb2JhbABExSGBUhZtB4IkAQEBAwFnEgUHBAIBCBEEAQEBCh0HMhQJCAIEDgUIAYgFBgzCSo1agQICJgsHBoJZYQOIP58jgwqBaz0
X-IronPort-AV: E=Sophos;i="4.84,880,1355097600"; d="scan'208";a="189462345"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-1.cisco.com with ESMTP; 20 Mar 2013 19:53:15 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2KJrFe7007656 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 20 Mar 2013 19:53:15 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Wed, 20 Mar 2013 14:53:15 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
Thread-Topic: RFC 4594 update: Routing class
Thread-Index: AQHOJaSPuoFMSa3/5E2yQicrO5Fcwg==
Date: Wed, 20 Mar 2013 19:53:15 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7DD927@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@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.21.146.87]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <68EEC7E183CA004A991AABC38B804FAB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 19:53:20 -0000

On Mar 20, 2013, at 11:47 AM, Ruediger.Geib@telekom.de wrote:

> David, Fred,
>=20
> an appropriate class for routing is envisaged by Y.1566
> and my draft is based on Y.1566. In fact, marking routing
> traffic by CS6 was easy to agree.
>=20
> The question is, how to treat traffic marked by CS6 at
> interconnection links. David originally objected to having
> such a routing class at interconnecton. I think we need
> some discussion.
>=20
> Routing information should be transmitted free of loss.
> That could mean an own class marked by CS6, that could be
> any other class resulting in low loss for TCP based
> traffic. One could map this traffic from CS6 to
> another fitting class and PHB, like Assured AF31.
>=20
> There's also an issue with VPN treatment. Providers may
> prefer not to transport customer routing traffic together
> with their own routing traffic.

That, I should think, would be between the provider of the VPN and the clie=
nt. If the client objects, the client can mop the whole VPN into some servi=
ce class of his interest.

> It may be good to add some text in -03 of my draft.
> Objections?

No objection to adding text to your draft. I would object to removing the s=
ervice class, as you report David to be proposing and your draft would appe=
ar to be proposing. I think there could be a lot in AF3 that could sustain =
an isolated loss while one wanted to preserve inter-provider routing traffi=
c.

> Regards,
>=20
> R=FCdiger
>=20
>=20
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of=
 Fred Baker (fred)
> Sent: Wednesday, March 20, 2013 5:28 PM
> To: Black, David
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] RFC 4594 update: Routing class
>=20
>=20
> On Mar 19, 2013, at 7:40 PM, "Black, David" <david.black@emc.com> wrote:
>=20
>> Hi Fred,
>>=20
>>> I was unable to attend tsvwg at IETF 86 as it competed with a meeting I
>>> presented in. I am told that there was a presentation in which folks ar=
gued
>>> against having a class of traffic for routing traffic. I'd like to comm=
ent on
>>> that.
>>=20
>> The argument in particular is about whether a class of traffic is needed=
 for
>> Routing traffic across an interconnection of two carrier networks.
>>=20
>> The argument was teed up for discussion in this slide presented in conne=
ction
>> with draft-geib-tsvwg-diffserv-intercon-02:
>>=20
>> http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx
>=20
> My only comment on that slide is that the story I told in my previous not=
e happened on inter-provider links. The slide is correct that there is not =
a defined class in 5127 for admitted video traffic.
>=20
>> Thank you for the comments,
>> --David
>>=20
>>> -----Original Message-----
>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf =
Of Fred
>>> Baker (fred)
>>> Sent: Tuesday, March 19, 2013 4:53 PM
>>> To: tsvwg@ietf.org
>>> Subject: [tsvwg] RFC 4594 update: Routing class
>>>=20
>>> I was unable to attend twvwg at IETF 86 as it competed with a meeting I
>>> presented in. I am told that there was a presentation in which folks ar=
gued
>>> against having a class of traffic for routing traffic. I'd like to comm=
ent on
>>> that.
>>>=20
>>> The origin of a class of traffic for routing traffic was a bug. The Cis=
co 7000
>>> had an issue with its offloaded forwarding cards, of which it had two. =
When
>>> there was a route flap, it blew away the route cache and then rebuilt i=
t in
>>> response to traffic it needed to forward. In that implementation, that =
meant
>>> that the Route Processor (the CPU) suddenly had all traffic from all so=
urces
>>> flooded into it. The impact of that was to make it very difficult for t=
he RP
>>> to actually re-populate the Route Cache. Doubleplus ungood. The work-ar=
ound
>>> was to rate-limit traffic from the line cards to the RP. However, rate
>>> limiting the routing traffic worked against getting routing to stabiliz=
e, so
>>> we marked routing traffic, and did not rate limit *it* from going to th=
e RP.
>>>=20
>>> Fast forward nearly 20 years. We don't have that bug anymore, if anythi=
ng
>>> because nobody equipped with a right mind uses the Cisco 7000 any more.
>>>=20
>>> However...
>>>=20
>>> If we're going to discuss quality of service for any application, we ar=
e
>>> making some fundamental assumptions. These include the concept of havin=
g
>>> enough bandwidth and so on; we're managing traffic at points in time wh=
en peak
>>> traffic loads on a millisecond scale create issues. One of those fundam=
ental
>>> issues is that routing must be current; if we're sending traffic on a r=
oute
>>> that loops because the other guy updated his route table but we didn't,=
 or
>>> vice versa, or for which interface or next hop router is no longer ther=
e, we
>>> can discuss jitter, rate, and loss to our heart's content - the applica=
tion's
>>> traffic isn't going to get there. At. All. And won't until routing stab=
ilizes.
>>>=20
>>> The fundamental argument for a class of traffic for routing in 2013 is =
not
>>> that routing requires certain jitter, rate, or etc characteristics; it =
is that
>>> routing traffic (apart from AQM issues, see separate discussion on
>>> aqm@ietf.org) should simply *not*be*dropped* in the normal course of bu=
siness.
>>> Routing is fundamental to all other services the network delivers, incl=
uding
>>> QoS, and including every networks's SLAs.
>>>=20
>>> Now, one can say that routing is between neighboring nodes, and a route=
r is
>>> able to do special things with traffic it itself originates. It is true=
 that a
>>> router can do special things with its own traffic, and they do. But BGP
>>> Routing frequently goes from Route Arbiter to Route Arbiter instead of =
Router
>>> to Router, which is to say through other routers between routing engine=
s.
>>> Traffic through other routers is traffic through other routers, not a r=
outer's
>>> own traffic. It requires some form of end to end marking to protect it.
>>> Something like a DSCP.
>=20


From Ruediger.Geib@telekom.de  Wed Mar 20 14:25:08 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5069A21F88EF for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 14:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.178
X-Spam-Level: 
X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKaJHYkViYZK for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 14:25:07 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id C859121F88DB for <tsvwg@ietf.org>; Wed, 20 Mar 2013 14:25:06 -0700 (PDT)
Received: from he113675.emea1.cds.t-internal.com ([10.134.99.28]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 20 Mar 2013 22:25:05 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113675.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 20 Mar 2013 22:25:05 +0100
From: <Ruediger.Geib@telekom.de>
To: <fred@cisco.com>
Date: Wed, 20 Mar 2013 22:25:02 +0100
Thread-Topic: RFC 4594 update: Routing class
Thread-Index: AQHOJaSPuoFMSa3/5E2yQicrO5FcwpivE7Rw
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE35@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DD927@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7DD927@xmb-rcd-x09.cisco.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 21:25:08 -0000

My draft says there may be a provider internal class
for routing and network management. It does not exclude
a situation where traffic of such a class and codepoint
is sent to a network provider. That's an aspect I'd be
happy to settle.

I've been suggesting AF31 as a potential CS6 match at
interconnection. The idea is, that AF32 and AF33 may
carry traffic of applications able to deal with an
isolated loss. I'd expect the Assured (AF3) class to
be produced almost free of loss within a
provider network not differentiating the 3 PHBs.
Differentiation of AF3 PHBs may be useful to the sending
party at interconnection. These are rough thoughts by now.

Regards,

R=FCdiger

-----Original Message-----
From: Fred Baker (fred) [mailto:fred@cisco.com]
Sent: Wednesday, March 20, 2013 8:53 PM
To: Geib, R=FCdiger
Cc: david.black@emc.com; tsvwg@ietf.org
Subject: Re: RFC 4594 update: Routing class


On Mar 20, 2013, at 11:47 AM, Ruediger.Geib@telekom.de wrote:

> David, Fred,
>
> an appropriate class for routing is envisaged by Y.1566
> and my draft is based on Y.1566. In fact, marking routing
> traffic by CS6 was easy to agree.
>
> The question is, how to treat traffic marked by CS6 at
> interconnection links. David originally objected to having
> such a routing class at interconnecton. I think we need
> some discussion.
>
> Routing information should be transmitted free of loss.
> That could mean an own class marked by CS6, that could be
> any other class resulting in low loss for TCP based
> traffic. One could map this traffic from CS6 to
> another fitting class and PHB, like Assured AF31.
>
> There's also an issue with VPN treatment. Providers may
> prefer not to transport customer routing traffic together
> with their own routing traffic.

That, I should think, would be between the provider of the VPN and the clie=
nt. If the client objects, the client can mop the whole VPN into some servi=
ce class of his interest.

> It may be good to add some text in -03 of my draft.
> Objections?

No objection to adding text to your draft. I would object to removing the s=
ervice class, as you report David to be proposing and your draft would appe=
ar to be proposing. I think there could be a lot in AF3 that could sustain =
an isolated loss while one wanted to preserve inter-provider routing traffi=
c.

> Regards,
>
> R=FCdiger
>
>
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of=
 Fred Baker (fred)
> Sent: Wednesday, March 20, 2013 5:28 PM
> To: Black, David
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] RFC 4594 update: Routing class
>
>
> On Mar 19, 2013, at 7:40 PM, "Black, David" <david.black@emc.com> wrote:
>
>> Hi Fred,
>>
>>> I was unable to attend tsvwg at IETF 86 as it competed with a meeting I
>>> presented in. I am told that there was a presentation in which folks ar=
gued
>>> against having a class of traffic for routing traffic. I'd like to comm=
ent on
>>> that.
>>
>> The argument in particular is about whether a class of traffic is needed=
 for
>> Routing traffic across an interconnection of two carrier networks.
>>
>> The argument was teed up for discussion in this slide presented in conne=
ction
>> with draft-geib-tsvwg-diffserv-intercon-02:
>>
>> http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx
>
> My only comment on that slide is that the story I told in my previous not=
e happened on inter-provider links. The slide is correct that there is not =
a defined class in 5127 for admitted video traffic.
>
>> Thank you for the comments,
>> --David
>>
>>> -----Original Message-----
>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf =
Of Fred
>>> Baker (fred)
>>> Sent: Tuesday, March 19, 2013 4:53 PM
>>> To: tsvwg@ietf.org
>>> Subject: [tsvwg] RFC 4594 update: Routing class
>>>
>>> I was unable to attend twvwg at IETF 86 as it competed with a meeting I
>>> presented in. I am told that there was a presentation in which folks ar=
gued
>>> against having a class of traffic for routing traffic. I'd like to comm=
ent on
>>> that.
>>>
>>> The origin of a class of traffic for routing traffic was a bug. The Cis=
co 7000
>>> had an issue with its offloaded forwarding cards, of which it had two. =
When
>>> there was a route flap, it blew away the route cache and then rebuilt i=
t in
>>> response to traffic it needed to forward. In that implementation, that =
meant
>>> that the Route Processor (the CPU) suddenly had all traffic from all so=
urces
>>> flooded into it. The impact of that was to make it very difficult for t=
he RP
>>> to actually re-populate the Route Cache. Doubleplus ungood. The work-ar=
ound
>>> was to rate-limit traffic from the line cards to the RP. However, rate
>>> limiting the routing traffic worked against getting routing to stabiliz=
e, so
>>> we marked routing traffic, and did not rate limit *it* from going to th=
e RP.
>>>
>>> Fast forward nearly 20 years. We don't have that bug anymore, if anythi=
ng
>>> because nobody equipped with a right mind uses the Cisco 7000 any more.
>>>
>>> However...
>>>
>>> If we're going to discuss quality of service for any application, we ar=
e
>>> making some fundamental assumptions. These include the concept of havin=
g
>>> enough bandwidth and so on; we're managing traffic at points in time wh=
en peak
>>> traffic loads on a millisecond scale create issues. One of those fundam=
ental
>>> issues is that routing must be current; if we're sending traffic on a r=
oute
>>> that loops because the other guy updated his route table but we didn't,=
 or
>>> vice versa, or for which interface or next hop router is no longer ther=
e, we
>>> can discuss jitter, rate, and loss to our heart's content - the applica=
tion's
>>> traffic isn't going to get there. At. All. And won't until routing stab=
ilizes.
>>>
>>> The fundamental argument for a class of traffic for routing in 2013 is =
not
>>> that routing requires certain jitter, rate, or etc characteristics; it =
is that
>>> routing traffic (apart from AQM issues, see separate discussion on
>>> aqm@ietf.org) should simply *not*be*dropped* in the normal course of bu=
siness.
>>> Routing is fundamental to all other services the network delivers, incl=
uding
>>> QoS, and including every networks's SLAs.
>>>
>>> Now, one can say that routing is between neighboring nodes, and a route=
r is
>>> able to do special things with traffic it itself originates. It is true=
 that a
>>> router can do special things with its own traffic, and they do. But BGP
>>> Routing frequently goes from Route Arbiter to Route Arbiter instead of =
Router
>>> to Router, which is to say through other routers between routing engine=
s.
>>> Traffic through other routers is traffic through other routers, not a r=
outer's
>>> own traffic. It requires some form of end to end marking to protect it.
>>> Something like a DSCP.
>


From fred@cisco.com  Wed Mar 20 14:30:51 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4226B1F0D15 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 14:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.36
X-Spam-Level: 
X-Spam-Status: No, score=-110.36 tagged_above=-999 required=5 tests=[AWL=0.239, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9oeF4jPQPg-7 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 14:30:50 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id C14F11F0D14 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 14:30:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7813; q=dns/txt; s=iport; t=1363815049; x=1365024649; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=aqh38rP/9fYAVqzPSZlFx3hekQERPv9s0BJSDLV4pfQ=; b=EptkZ0d17spaZqAAhaZpl2u0i0ghpMeM4dVb5s1nxMzyfKz2QlL00RKY TFYod269+A8JoeVMmHk13QFa2LuyeIEymnwEaQRzbQ6LA6t226KN8Voag DVwJuPBaSdySmLF0qHKYzT35C3Uh2aKVlsfCu+XBvwYiMXmsAZHnZDpsB Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAFQpSlGtJXG9/2dsb2JhbABEs36RLYFSFnSCJAEBAQMBZxIFBwQCAQgRBAEBAQodBzIUCQgCBA4FCAGIBQYMwlSNWoECAgYgCwcCBIJZYQOIP58jgwqBaz0
X-IronPort-AV: E=Sophos;i="4.84,880,1355097600"; d="scan'208";a="189741498"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-3.cisco.com with ESMTP; 20 Mar 2013 21:30:49 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2KLUmcx019034 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 20 Mar 2013 21:30:48 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Wed, 20 Mar 2013 16:30:48 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "<Ruediger.Geib@telekom.de> " <Ruediger.Geib@telekom.de>
Thread-Topic: RFC 4594 update: Routing class
Thread-Index: AQHOJbIw3aMJNosqg0u6rabNg/ovmw==
Date: Wed, 20 Mar 2013 21:30:48 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7DDCA6@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DD927@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE35@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE35@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.21.146.87]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <467A93FEE73FE84F84B2BCA2B0C224DA@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 21:30:51 -0000

On Mar 20, 2013, at 2:25 PM, <Ruediger.Geib@telekom.de>
 wrote:

> My draft says there may be a provider internal class
> for routing and network management. It does not exclude
> a situation where traffic of such a class and codepoint
> is sent to a network provider. That's an aspect I'd be
> happy to settle.
>=20
> I've been suggesting AF31 as a potential CS6 match at
> interconnection. The idea is, that AF32 and AF33 may
> carry traffic of applications able to deal with an
> isolated loss. I'd expect the Assured (AF3) class to
> be produced almost free of loss within a
> provider network not differentiating the 3 PHBs.
> Differentiation of AF3 PHBs may be useful to the sending
> party at interconnection. These are rough thoughts by now.

The same is true of CS6.

The reason we picked the number 110 000, by the way, was current use. If yo=
u want to change the number, it will take more than a stroke of the pen; it=
 will take changing at least configuration if not software. What you wind u=
p with is a class that carries both numbers until the old class goes away.

I'm not sure I see the point.

> Regards,
>=20
> R=FCdiger
>=20
> -----Original Message-----
> From: Fred Baker (fred) [mailto:fred@cisco.com]
> Sent: Wednesday, March 20, 2013 8:53 PM
> To: Geib, R=FCdiger
> Cc: david.black@emc.com; tsvwg@ietf.org
> Subject: Re: RFC 4594 update: Routing class
>=20
>=20
> On Mar 20, 2013, at 11:47 AM, Ruediger.Geib@telekom.de wrote:
>=20
>> David, Fred,
>>=20
>> an appropriate class for routing is envisaged by Y.1566
>> and my draft is based on Y.1566. In fact, marking routing
>> traffic by CS6 was easy to agree.
>>=20
>> The question is, how to treat traffic marked by CS6 at
>> interconnection links. David originally objected to having
>> such a routing class at interconnecton. I think we need
>> some discussion.
>>=20
>> Routing information should be transmitted free of loss.
>> That could mean an own class marked by CS6, that could be
>> any other class resulting in low loss for TCP based
>> traffic. One could map this traffic from CS6 to
>> another fitting class and PHB, like Assured AF31.
>>=20
>> There's also an issue with VPN treatment. Providers may
>> prefer not to transport customer routing traffic together
>> with their own routing traffic.
>=20
> That, I should think, would be between the provider of the VPN and the cl=
ient. If the client objects, the client can mop the whole VPN into some ser=
vice class of his interest.
>=20
>> It may be good to add some text in -03 of my draft.
>> Objections?
>=20
> No objection to adding text to your draft. I would object to removing the=
 service class, as you report David to be proposing and your draft would ap=
pear to be proposing. I think there could be a lot in AF3 that could sustai=
n an isolated loss while one wanted to preserve inter-provider routing traf=
fic.
>=20
>> Regards,
>>=20
>> R=FCdiger
>>=20
>>=20
>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf O=
f Fred Baker (fred)
>> Sent: Wednesday, March 20, 2013 5:28 PM
>> To: Black, David
>> Cc: tsvwg@ietf.org
>> Subject: Re: [tsvwg] RFC 4594 update: Routing class
>>=20
>>=20
>> On Mar 19, 2013, at 7:40 PM, "Black, David" <david.black@emc.com> wrote:
>>=20
>>> Hi Fred,
>>>=20
>>>> I was unable to attend tsvwg at IETF 86 as it competed with a meeting =
I
>>>> presented in. I am told that there was a presentation in which folks a=
rgued
>>>> against having a class of traffic for routing traffic. I'd like to com=
ment on
>>>> that.
>>>=20
>>> The argument in particular is about whether a class of traffic is neede=
d for
>>> Routing traffic across an interconnection of two carrier networks.
>>>=20
>>> The argument was teed up for discussion in this slide presented in conn=
ection
>>> with draft-geib-tsvwg-diffserv-intercon-02:
>>>=20
>>> http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx
>>=20
>> My only comment on that slide is that the story I told in my previous no=
te happened on inter-provider links. The slide is correct that there is not=
 a defined class in 5127 for admitted video traffic.
>>=20
>>> Thank you for the comments,
>>> --David
>>>=20
>>>> -----Original Message-----
>>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf=
 Of Fred
>>>> Baker (fred)
>>>> Sent: Tuesday, March 19, 2013 4:53 PM
>>>> To: tsvwg@ietf.org
>>>> Subject: [tsvwg] RFC 4594 update: Routing class
>>>>=20
>>>> I was unable to attend twvwg at IETF 86 as it competed with a meeting =
I
>>>> presented in. I am told that there was a presentation in which folks a=
rgued
>>>> against having a class of traffic for routing traffic. I'd like to com=
ment on
>>>> that.
>>>>=20
>>>> The origin of a class of traffic for routing traffic was a bug. The Ci=
sco 7000
>>>> had an issue with its offloaded forwarding cards, of which it had two.=
 When
>>>> there was a route flap, it blew away the route cache and then rebuilt =
it in
>>>> response to traffic it needed to forward. In that implementation, that=
 meant
>>>> that the Route Processor (the CPU) suddenly had all traffic from all s=
ources
>>>> flooded into it. The impact of that was to make it very difficult for =
the RP
>>>> to actually re-populate the Route Cache. Doubleplus ungood. The work-a=
round
>>>> was to rate-limit traffic from the line cards to the RP. However, rate
>>>> limiting the routing traffic worked against getting routing to stabili=
ze, so
>>>> we marked routing traffic, and did not rate limit *it* from going to t=
he RP.
>>>>=20
>>>> Fast forward nearly 20 years. We don't have that bug anymore, if anyth=
ing
>>>> because nobody equipped with a right mind uses the Cisco 7000 any more=
.
>>>>=20
>>>> However...
>>>>=20
>>>> If we're going to discuss quality of service for any application, we a=
re
>>>> making some fundamental assumptions. These include the concept of havi=
ng
>>>> enough bandwidth and so on; we're managing traffic at points in time w=
hen peak
>>>> traffic loads on a millisecond scale create issues. One of those funda=
mental
>>>> issues is that routing must be current; if we're sending traffic on a =
route
>>>> that loops because the other guy updated his route table but we didn't=
, or
>>>> vice versa, or for which interface or next hop router is no longer the=
re, we
>>>> can discuss jitter, rate, and loss to our heart's content - the applic=
ation's
>>>> traffic isn't going to get there. At. All. And won't until routing sta=
bilizes.
>>>>=20
>>>> The fundamental argument for a class of traffic for routing in 2013 is=
 not
>>>> that routing requires certain jitter, rate, or etc characteristics; it=
 is that
>>>> routing traffic (apart from AQM issues, see separate discussion on
>>>> aqm@ietf.org) should simply *not*be*dropped* in the normal course of b=
usiness.
>>>> Routing is fundamental to all other services the network delivers, inc=
luding
>>>> QoS, and including every networks's SLAs.
>>>>=20
>>>> Now, one can say that routing is between neighboring nodes, and a rout=
er is
>>>> able to do special things with traffic it itself originates. It is tru=
e that a
>>>> router can do special things with its own traffic, and they do. But BG=
P
>>>> Routing frequently goes from Route Arbiter to Route Arbiter instead of=
 Router
>>>> to Router, which is to say through other routers between routing engin=
es.
>>>> Traffic through other routers is traffic through other routers, not a =
router's
>>>> own traffic. It requires some form of end to end marking to protect it=
.
>>>> Something like a DSCP.
>>=20
>=20


From Ruediger.Geib@telekom.de  Wed Mar 20 15:12:47 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 577C011E80E8 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 15:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level: 
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zok5r0uHOXeK for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 15:12:46 -0700 (PDT)
Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) by ietfa.amsl.com (Postfix) with ESMTP id 450961F0D16 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 15:12:44 -0700 (PDT)
Received: from he113472.emea1.cds.t-internal.com ([10.134.93.130]) by tcmail41.telekom.de with ESMTP/TLS/AES128-SHA; 20 Mar 2013 23:12:41 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113472.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 20 Mar 2013 23:12:41 +0100
From: <Ruediger.Geib@telekom.de>
To: <fred@cisco.com>
Date: Wed, 20 Mar 2013 23:12:40 +0100
Thread-Topic: RFC 4594 update: Routing class
Thread-Index: AQHOJbIw3aMJNosqg0u6rabNg/ovm5ivIA0w
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE37@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DD927@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE35@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DDCA6@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7DDCA6@xmb-rcd-x09.cisco.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 22:12:47 -0000

I don't exclude CS6 from being sent.
I know of the router limitations if it's about
setting DSCPs for internally created traffic.
That's not limited to BGP or IGP Protocols.

CS6 was easy to agree within ITU as those
providers I talked to use it. And they agreed
that they wouldn't be happy to carry customer
traffic in that class.

I never said I'd like to change the codepoint in
general. I'm discussing how to treat the
PHB/codepoint if received at interconnetion. I
recall that one of the starting points of our
current acitivities was Brians remark, that
changing DSCPs is the default DiffServ behaviour
at interconnecton interfaces.

I think we agree, here's an issue. We don't seem
to agree about the solution.

Regards,

R=FCdiger

-----Original Message-----
From: Fred Baker (fred) [mailto:fred@cisco.com]
Sent: Wednesday, March 20, 2013 10:31 PM
To: Geib, R=FCdiger
Cc: tsvwg@ietf.org
Subject: Re: RFC 4594 update: Routing class


On Mar 20, 2013, at 2:25 PM, <Ruediger.Geib@telekom.de>
 wrote:

> My draft says there may be a provider internal class
> for routing and network management. It does not exclude
> a situation where traffic of such a class and codepoint
> is sent to a network provider. That's an aspect I'd be
> happy to settle.
>
> I've been suggesting AF31 as a potential CS6 match at
> interconnection. The idea is, that AF32 and AF33 may
> carry traffic of applications able to deal with an
> isolated loss. I'd expect the Assured (AF3) class to
> be produced almost free of loss within a
> provider network not differentiating the 3 PHBs.
> Differentiation of AF3 PHBs may be useful to the sending
> party at interconnection. These are rough thoughts by now.

The same is true of CS6.

The reason we picked the number 110 000, by the way, was current use. If yo=
u want to change the number, it will take more than a stroke of the pen; it=
 will take changing at least configuration if not software. What you wind u=
p with is a class that carries both numbers until the old class goes away.

I'm not sure I see the point.

> Regards,
>
> R=FCdiger
>
> -----Original Message-----
> From: Fred Baker (fred) [mailto:fred@cisco.com]
> Sent: Wednesday, March 20, 2013 8:53 PM
> To: Geib, R=FCdiger
> Cc: david.black@emc.com; tsvwg@ietf.org
> Subject: Re: RFC 4594 update: Routing class
>
>
> On Mar 20, 2013, at 11:47 AM, Ruediger.Geib@telekom.de wrote:
>
>> David, Fred,
>>
>> an appropriate class for routing is envisaged by Y.1566
>> and my draft is based on Y.1566. In fact, marking routing
>> traffic by CS6 was easy to agree.
>>
>> The question is, how to treat traffic marked by CS6 at
>> interconnection links. David originally objected to having
>> such a routing class at interconnecton. I think we need
>> some discussion.
>>
>> Routing information should be transmitted free of loss.
>> That could mean an own class marked by CS6, that could be
>> any other class resulting in low loss for TCP based
>> traffic. One could map this traffic from CS6 to
>> another fitting class and PHB, like Assured AF31.
>>
>> There's also an issue with VPN treatment. Providers may
>> prefer not to transport customer routing traffic together
>> with their own routing traffic.
>
> That, I should think, would be between the provider of the VPN and the cl=
ient. If the client objects, the client can mop the whole VPN into some ser=
vice class of his interest.
>
>> It may be good to add some text in -03 of my draft.
>> Objections?
>
> No objection to adding text to your draft. I would object to removing the=
 service class, as you report David to be proposing and your draft would ap=
pear to be proposing. I think there could be a lot in AF3 that could sustai=
n an isolated loss while one wanted to preserve inter-provider routing traf=
fic.
>
>> Regards,
>>
>> R=FCdiger
>>
>>
>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf O=
f Fred Baker (fred)
>> Sent: Wednesday, March 20, 2013 5:28 PM
>> To: Black, David
>> Cc: tsvwg@ietf.org
>> Subject: Re: [tsvwg] RFC 4594 update: Routing class
>>
>>
>> On Mar 19, 2013, at 7:40 PM, "Black, David" <david.black@emc.com> wrote:
>>
>>> Hi Fred,
>>>
>>>> I was unable to attend tsvwg at IETF 86 as it competed with a meeting =
I
>>>> presented in. I am told that there was a presentation in which folks a=
rgued
>>>> against having a class of traffic for routing traffic. I'd like to com=
ment on
>>>> that.
>>>
>>> The argument in particular is about whether a class of traffic is neede=
d for
>>> Routing traffic across an interconnection of two carrier networks.
>>>
>>> The argument was teed up for discussion in this slide presented in conn=
ection
>>> with draft-geib-tsvwg-diffserv-intercon-02:
>>>
>>> http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx
>>
>> My only comment on that slide is that the story I told in my previous no=
te happened on inter-provider links. The slide is correct that there is not=
 a defined class in 5127 for admitted video traffic.
>>
>>> Thank you for the comments,
>>> --David
>>>
>>>> -----Original Message-----
>>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf=
 Of Fred
>>>> Baker (fred)
>>>> Sent: Tuesday, March 19, 2013 4:53 PM
>>>> To: tsvwg@ietf.org
>>>> Subject: [tsvwg] RFC 4594 update: Routing class
>>>>
>>>> I was unable to attend twvwg at IETF 86 as it competed with a meeting =
I
>>>> presented in. I am told that there was a presentation in which folks a=
rgued
>>>> against having a class of traffic for routing traffic. I'd like to com=
ment on
>>>> that.
>>>>
>>>> The origin of a class of traffic for routing traffic was a bug. The Ci=
sco 7000
>>>> had an issue with its offloaded forwarding cards, of which it had two.=
 When
>>>> there was a route flap, it blew away the route cache and then rebuilt =
it in
>>>> response to traffic it needed to forward. In that implementation, that=
 meant
>>>> that the Route Processor (the CPU) suddenly had all traffic from all s=
ources
>>>> flooded into it. The impact of that was to make it very difficult for =
the RP
>>>> to actually re-populate the Route Cache. Doubleplus ungood. The work-a=
round
>>>> was to rate-limit traffic from the line cards to the RP. However, rate
>>>> limiting the routing traffic worked against getting routing to stabili=
ze, so
>>>> we marked routing traffic, and did not rate limit *it* from going to t=
he RP.
>>>>
>>>> Fast forward nearly 20 years. We don't have that bug anymore, if anyth=
ing
>>>> because nobody equipped with a right mind uses the Cisco 7000 any more=
.
>>>>
>>>> However...
>>>>
>>>> If we're going to discuss quality of service for any application, we a=
re
>>>> making some fundamental assumptions. These include the concept of havi=
ng
>>>> enough bandwidth and so on; we're managing traffic at points in time w=
hen peak
>>>> traffic loads on a millisecond scale create issues. One of those funda=
mental
>>>> issues is that routing must be current; if we're sending traffic on a =
route
>>>> that loops because the other guy updated his route table but we didn't=
, or
>>>> vice versa, or for which interface or next hop router is no longer the=
re, we
>>>> can discuss jitter, rate, and loss to our heart's content - the applic=
ation's
>>>> traffic isn't going to get there. At. All. And won't until routing sta=
bilizes.
>>>>
>>>> The fundamental argument for a class of traffic for routing in 2013 is=
 not
>>>> that routing requires certain jitter, rate, or etc characteristics; it=
 is that
>>>> routing traffic (apart from AQM issues, see separate discussion on
>>>> aqm@ietf.org) should simply *not*be*dropped* in the normal course of b=
usiness.
>>>> Routing is fundamental to all other services the network delivers, inc=
luding
>>>> QoS, and including every networks's SLAs.
>>>>
>>>> Now, one can say that routing is between neighboring nodes, and a rout=
er is
>>>> able to do special things with traffic it itself originates. It is tru=
e that a
>>>> router can do special things with its own traffic, and they do. But BG=
P
>>>> Routing frequently goes from Route Arbiter to Route Arbiter instead of=
 Router
>>>> to Router, which is to say through other routers between routing engin=
es.
>>>> Traffic through other routers is traffic through other routers, not a =
router's
>>>> own traffic. It requires some form of end to end marking to protect it=
.
>>>> Something like a DSCP.
>>
>


From fred@cisco.com  Wed Mar 20 16:05:34 2013
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0209721F8BD9 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 16:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.482
X-Spam-Level: 
X-Spam-Status: No, score=-110.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KE8QQhFDIX-r for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 16:05:33 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 4964D21F8BC5 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 16:05:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=316; q=dns/txt; s=iport; t=1363820733; x=1365030333; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=xtEdMB4hhRWrEoWiBZxTdo4+0bi+4ytPgxDwdNePQFI=; b=bF/WMrsMo9qbGWTjmdinzCAce4L13KKWVRQrxexvkj+cGClLPiT8eBnB g6YVIRuxs6kZ4VD0eQS5HEmYMtF/hDTAahsNlOr33tQEzLFIDGmS6Ea+7 1KT2jgAO+0YPz2idB80GxA9RZNGLEd/dmZiSxDyDJ4isN9ZniA2iz4/K3 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwFAFY/SlGtJXG+/2dsb2JhbABDh1G9YIFSFm0HgiQBAQEDAXkFCwIBCCIkMiUCBA4FCBOHcwbCWY5dAjEHgl9hA4g/nyODCoIo
X-IronPort-AV: E=Sophos;i="4.84,880,1355097600"; d="scan'208";a="189735676"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-8.cisco.com with ESMTP; 20 Mar 2013 23:05:32 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2KN5WIf006576 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 20 Mar 2013 23:05:32 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Wed, 20 Mar 2013 18:05:22 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
Thread-Topic: RFC 4594 update: Routing class
Thread-Index: AQHOJb9l8e854Z4LKkWJpxEOJw7eQQ==
Date: Wed, 20 Mar 2013 23:05:21 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7DDEA9@xmb-rcd-x09.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DD927@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE35@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DDCA6@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE37@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE37@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.21.146.87]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <2B78A037DEE5484790B5F771C6738E2B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2013 23:05:34 -0000

On Mar 20, 2013, at 3:12 PM, Ruediger.Geib@telekom.de wrote:

> I think we agree, here's an issue.=20

I think we agree that there is a conversation to be had. I'm not sure what =
actual problem you're trying to solve. I mostly see a proposed solution, di=
splayed in the slide you have in the proceedings.



From david.black@emc.com  Wed Mar 20 21:03:02 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1976C21F8B35 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 21:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zfd56BzacPuM for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 21:03:01 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 4588621F8AE2 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 21:03:01 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2L42vOs025873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Mar 2013 00:02:59 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 21 Mar 2013 00:02:41 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2L42fGt032421; Thu, 21 Mar 2013 00:02:41 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Thu, 21 Mar 2013 00:02:41 -0400
From: "Black, David" <david.black@emc.com>
To: "Fred Baker (fred)" <fred@cisco.com>, "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
Date: Thu, 21 Mar 2013 00:02:37 -0400
Thread-Topic: RFC 4594 update: Routing class
Thread-Index: AQHOJb9l8e854Z4LKkWJpxEOJw7eQZivgfWQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293AEE61D@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DD927@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE35@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DDCA6@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE37@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DDEA9@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7DDEA9@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 04:03:02 -0000

To be clear, that slide was based on ITU-T Y.1566 and draft-geib-diffserv-i=
ntercon.
The unstated purpose of that slide was to stimulate discussion - which is n=
ow underway.
Slide URL: http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx

The slides on draft-geib-diffserv-intercon are here:
	http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-2.ppt

Thanks,
--David

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of=
 Fred
> Baker (fred)
> Sent: Wednesday, March 20, 2013 7:05 PM
> To: Ruediger.Geib@telekom.de
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] RFC 4594 update: Routing class
>=20
>=20
> On Mar 20, 2013, at 3:12 PM, Ruediger.Geib@telekom.de wrote:
>=20
> > I think we agree, here's an issue.
>=20
> I think we agree that there is a conversation to be had. I'm not sure wha=
t
> actual problem you're trying to solve. I mostly see a proposed solution,
> displayed in the slide you have in the proceedings.
>=20
>=20


From prvs=785051959=ankit.mahawar@tcs.com  Wed Mar 20 23:29:21 2013
Return-Path: <prvs=785051959=ankit.mahawar@tcs.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 603AA21F8F3E for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 23:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.433
X-Spam-Level: 
X-Spam-Status: No, score=-6.433 tagged_above=-999 required=5 tests=[AWL=0.166,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wS5+L4CfJ-Xp for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 23:29:20 -0700 (PDT)
Received: from inmumg02.tcs.com (Inmumg02.tcs.com [219.64.33.222]) by ietfa.amsl.com (Postfix) with ESMTP id 099D121F8F2D for <tsvwg@ietf.org>; Wed, 20 Mar 2013 23:29:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.84,884,1355077800"; d="scan'208";a="131540050"
X-DISCLAIMER: FALSE
Received: from cdctdlpprotect3 (unknown [127.0.0.1]) by cdctdlpprotect3.localdomain (Service) with ESMTP id D8E66ABE16; Thu, 21 Mar 2013 11:57:47 +0530 (IST)
Received: from inmumm13.tcs.com (unknown [172.17.9.193]) by cdctdlpprotect3.localdomain (Service) with ESMTP id 523F1ABE14; Thu, 21 Mar 2013 11:57:47 +0530 (IST)
In-Reply-To: <012C3117EDDB3C4781FD802A8C27DD4F24AC0CB5@SACEXCMBX02-PRD.hq.netapp.com>
References: <OF2FAE4932.D8FCB5F8-ON65257B34.0035654D-65257B34.0035BC57@tcs.com> <012C3117EDDB3C4781FD802A8C27DD4F24AC0CB5@SACEXCMBX02-PRD.hq.netapp.com>
From: Ankit Mahawar <ankit.mahawar@tcs.com>
X-KeepSent: 42569AB5:7C738A52-65257B35:0023204B; type=4; name=$KeepSent
To: "Scheffenegger, Richard" <rs@netapp.com>
X-Mailer: Lotus Notes Release 8.5.2FP1 November 30, 2010
Message-ID: <OF42569AB5.7C738A52-ON65257B35.0023204B-65257B35.0023968B@tcs.com>
Sender: Ankit Mahawar <ankit.mahawar@tcs.com>
Date: Thu, 21 Mar 2013 11:58:42 +0530
X-MIMETrack: Serialize by Router on InMumM13/TCS(Release 8.5.2FP4HF188 | September 13, 2012) at 03/21/2013 11:59:16
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] Query regarding heartbeat re-transmission pattern
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 06:29:21 -0000

Hi Richard,

I wanted to know the scenario how SCTP behave when the heartbeat is not=

acknowledged  and the timer expires  waiting for the acknowledgement.

Thanks


                                                                       =
                                                                  
  From:       "Scheffenegger, Richard" <rs@netapp.com>                 =
                                                                  
                                                                       =
                                                                  
  To:         Ankit Mahawar <ankit.mahawar@tcs.com>, "tsvwg@ietf.org" <=
tsvwg@ietf.org>                                                   
                                                                       =
                                                                  
  Date:       03/21/2013 12:49 AM                                      =
                                                                  
                                                                       =
                                                                  
  Subject:    RE: [tsvwg] Query regarding heartbeat re-transmission pat=
tern                                                              
                                                                       =
                                                                  





Hi Ankit,

is it only the heartbeat that failed (are there other packets flowing
between A.p to B.p), in your scenario?

I would read the 2nd fragment of text, that if A.s to B.s failed, a
retransmission (of data) should be checked between A.p to B.p first; ot=
her
(possible) combinations, like A.p -> B.s, or A.s -> B.p later...

Regards,

Richard Scheffenegger

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behal=
f Of
> Ankit Mahawar
> Sent: Mittwoch, 20. M=E4rz 2013 10:47
> To: tsvwg@ietf.org
> Subject: [tsvwg] Query regarding heartbeat re-transmission pattern
>
>
> Hi All ,
>
> I have a basic query regarding SCTP heartbeat re-transmission pattern=
 .
>
> As per the RFC 4960 :
>
> Furthermore, when its peer is multi-homed, an endpoint SHOULD try to
> retransmit a chunk that timed out to an active destination transport
> address that is different from the last destination address to which =
the
> DATA chunk was sent.
>
> Also,
> When retransmitting data that timed out, if the endpoint is multi-hom=
ed,
> it
> should consider each source-destination address pair in its
retransmission
> selection policy.  When retransmitting timed-out data, the endpoint
should
> attempt to pick the most divergent source-destination pair from the
> original source-destination pair to which the packet was transmitted.=

>
> Suppose if we have multihomed SCTP endpoints A and B .
>
> A                      B
>
> a.a.a.p               b.b.b.p
> a.a.a.s               b.b.b.s
>
> If we transmit heartbeat from a.a.a.s to b.b.b.s and it is not
> acknowledged
> so does it re-transmit it using the same src and destination or with
> a.a.a.p to b.b.b.s.
>
> Please help to understand .
>
> Thanks
>
> =3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>


=



From padman.m@gmail.com  Wed Mar 20 23:39:36 2013
Return-Path: <padman.m@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D60F21F8F81 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 23:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxfOkDZTXFjl for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2013 23:39:35 -0700 (PDT)
Received: from mail-bk0-x229.google.com (mail-bk0-x229.google.com [IPv6:2a00:1450:4008:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2E7E221F8E1A for <tsvwg@ietf.org>; Wed, 20 Mar 2013 23:39:35 -0700 (PDT)
Received: by mail-bk0-f41.google.com with SMTP id q16so1266006bkw.0 for <tsvwg@ietf.org>; Wed, 20 Mar 2013 23:39:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=GR1COf+GGEVlyIVFzD4aqFzvB2SY+IS8ioSBya/MhHU=; b=mh4PPfhIwlJRlrGTSli8hrX/VieTJFVfyNbDdN/Nlm0KEY+dLSJtqGUvYSZwLz9uvB +6/20JEnQPfpPA6Iwjqc6UtcxVgWaRzxiBYph+578PzPuFLwb5qvkFOm2S3PluE2Ea9Q M5S7dS+h2tp5clUsrJLXtOLUm/zOxudOp1wI26WcchgkDSfj0vD5/X3HWhSxiVXXHl// hkmz+OFNJo9e1TNaeEkpZJYFM4jm6xhdrw59cM+v8lsLoRw2AM29FhSJURLdZ0IzYO/o wXF2JgfkqNd6ffcLVKRwlOFXgU1T+3D0ce+KLPi0vQVb7d9ZQJ4xutD1ySFZ1DbFi6hP ggag==
MIME-Version: 1.0
X-Received: by 10.204.175.193 with SMTP id bb1mr12186313bkb.72.1363847974290;  Wed, 20 Mar 2013 23:39:34 -0700 (PDT)
Received: by 10.204.173.205 with HTTP; Wed, 20 Mar 2013 23:39:34 -0700 (PDT)
In-Reply-To: <OF42569AB5.7C738A52-ON65257B35.0023204B-65257B35.0023968B@tcs.com>
References: <OF2FAE4932.D8FCB5F8-ON65257B34.0035654D-65257B34.0035BC57@tcs.com> <012C3117EDDB3C4781FD802A8C27DD4F24AC0CB5@SACEXCMBX02-PRD.hq.netapp.com> <OF42569AB5.7C738A52-ON65257B35.0023204B-65257B35.0023968B@tcs.com>
Date: Thu, 21 Mar 2013 12:09:34 +0530
Message-ID: <CADEup3fS4+hnfp4zZkuBFwPCZWK1CXcLXLrPrYSQ9sF70mDmsg@mail.gmail.com>
From: Padmalochan Moharana <padman.m@gmail.com>
To: Ankit Mahawar <ankit.mahawar@tcs.com>
Content-Type: multipart/alternative; boundary=bcaec51b1e5109345604d8699a7e
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] Query regarding heartbeat re-transmission pattern
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 06:39:36 -0000

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

Hi Ankit,

Please go through the below section in rfc4960.

8.3 <http://tools.ietf.org/html/rfc4960#section-8.3>.  Path Heartbeat



Thanks,
Padmalochan

On Thu, Mar 21, 2013 at 11:58 AM, Ankit Mahawar <ankit.mahawar@tcs.com>wrot=
e:

> Hi Richard,
>
> I wanted to know the scenario how SCTP behave when the heartbeat is not
> acknowledged  and the timer expires  waiting for the acknowledgement.
>
> Thanks
>
>
>
>   From:       "Scheffenegger, Richard" <rs@netapp.com>
>
>   To:         Ankit Mahawar <ankit.mahawar@tcs.com>, "tsvwg@ietf.org" <
> tsvwg@ietf.org>
>
>   Date:       03/21/2013 12:49 AM
>
>   Subject:    RE: [tsvwg] Query regarding heartbeat re-transmission patte=
rn
>
>
>
>
>
>
> Hi Ankit,
>
> is it only the heartbeat that failed (are there other packets flowing
> between A.p to B.p), in your scenario?
>
> I would read the 2nd fragment of text, that if A.s to B.s failed, a
> retransmission (of data) should be checked between A.p to B.p first; othe=
r
> (possible) combinations, like A.p -> B.s, or A.s -> B.p later...
>
> Regards,
>
> Richard Scheffenegger
>
> > -----Original Message-----
> > From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf
> Of
> > Ankit Mahawar
> > Sent: Mittwoch, 20. M=E4rz 2013 10:47
> > To: tsvwg@ietf.org
> > Subject: [tsvwg] Query regarding heartbeat re-transmission pattern
> >
> >
> > Hi All ,
> >
> > I have a basic query regarding SCTP heartbeat re-transmission pattern .
> >
> > As per the RFC 4960 :
> >
> > Furthermore, when its peer is multi-homed, an endpoint SHOULD try to
> > retransmit a chunk that timed out to an active destination transport
> > address that is different from the last destination address to which th=
e
> > DATA chunk was sent.
> >
> > Also,
> > When retransmitting data that timed out, if the endpoint is multi-homed=
,
> > it
> > should consider each source-destination address pair in its
> retransmission
> > selection policy.  When retransmitting timed-out data, the endpoint
> should
> > attempt to pick the most divergent source-destination pair from the
> > original source-destination pair to which the packet was transmitted.
> >
> > Suppose if we have multihomed SCTP endpoints A and B .
> >
> > A                      B
> >
> > a.a.a.p               b.b.b.p
> > a.a.a.s               b.b.b.s
> >
> > If we transmit heartbeat from a.a.a.s to b.b.b.s and it is not
> > acknowledged
> > so does it re-transmit it using the same src and destination or with
> > a.a.a.p to b.b.b.s.
> >
> > Please help to understand .
> >
> > Thanks
> >
> > =3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D
> > Notice: The information contained in this e-mail
> > message and/or attachments to it may contain
> > confidential or privileged information. If you are
> > not the intended recipient, any dissemination, use,
> > review, distribution, printing or copying of the
> > information contained in this e-mail message
> > and/or attachments to it are strictly prohibited. If
> > you have received this communication in error,
> > please notify us by reply e-mail or telephone and
> > immediately and permanently delete the message
> > and any attachments. Thank you
> >
> >
>
>
>
>
>

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

Hi Ankit,<div><br></div><div>Please go through the below section in rfc4960=
.</div><div><br></div><div><pre class=3D"newpage" style=3D"font-size:1em;ma=
rgin-top:0px;margin-bottom:0px"><span class=3D"h3" style=3D"line-height:0pt=
;display:inline;font-size:1em;font-weight:bold"><h3 style=3D"line-height:0p=
t;display:inline;font-size:1em">
<a class=3D"selflink" name=3D"section-8.3" href=3D"http://tools.ietf.org/ht=
ml/rfc4960#section-8.3" style=3D"color:black;text-decoration:none">8.3</a>.=
  Path Heartbeat</h3></span></pre><pre class=3D"newpage" style=3D"font-size=
:1em;margin-top:0px;margin-bottom:0px">
<span class=3D"h3" style=3D"line-height:0pt;display:inline;font-size:1em;fo=
nt-weight:bold"><h3 style=3D"line-height:0pt;display:inline;font-size:1em">=
<br></h3></span></pre></div><div><br></div><div>Thanks,</div><div>Padmaloch=
an<br>
<br><div class=3D"gmail_quote">On Thu, Mar 21, 2013 at 11:58 AM, Ankit Maha=
war <span dir=3D"ltr">&lt;<a href=3D"mailto:ankit.mahawar@tcs.com" target=
=3D"_blank">ankit.mahawar@tcs.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
Hi Richard,<br>
<br>
I wanted to know the scenario how SCTP behave when the heartbeat is not<br>
acknowledged =A0and the timer expires =A0waiting for the acknowledgement.<b=
r>
<br>
Thanks<br>
<br>
<br>
<br>
=A0 From: =A0 =A0 =A0 &quot;Scheffenegger, Richard&quot; &lt;<a href=3D"mai=
lto:rs@netapp.com">rs@netapp.com</a>&gt;<br>
<br>
=A0 To: =A0 =A0 =A0 =A0 Ankit Mahawar &lt;<a href=3D"mailto:ankit.mahawar@t=
cs.com">ankit.mahawar@tcs.com</a>&gt;, &quot;<a href=3D"mailto:tsvwg@ietf.o=
rg">tsvwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:tsvwg@ietf.org">tsvwg@ie=
tf.org</a>&gt;<br>

<br>
=A0 Date: =A0 =A0 =A0 03/21/2013 12:49 AM<br>
<br>
=A0 Subject: =A0 =A0RE: [tsvwg] Query regarding heartbeat re-transmission p=
attern<br>
<br>
<br>
<br>
<br>
<br>
<br>
Hi Ankit,<br>
<br>
is it only the heartbeat that failed (are there other packets flowing<br>
between A.p to B.p), in your scenario?<br>
<br>
I would read the 2nd fragment of text, that if A.s to B.s failed, a<br>
retransmission (of data) should be checked between A.p to B.p first; other<=
br>
(possible) combinations, like A.p -&gt; B.s, or A.s -&gt; B.p later...<br>
<br>
Regards,<br>
<br>
Richard Scheffenegger<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:tsvwg-bounces@ietf.org">tsvwg-bounces@ietf.org=
</a> [mailto:<a href=3D"mailto:tsvwg-bounces@ietf.org">tsvwg-bounces@ietf.o=
rg</a>] On Behalf Of<br>
&gt; Ankit Mahawar<br>
&gt; Sent: Mittwoch, 20. M=E4rz 2013 10:47<br>
&gt; To: <a href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a><br>
&gt; Subject: [tsvwg] Query regarding heartbeat re-transmission pattern<br>
&gt;<br>
&gt;<br>
&gt; Hi All ,<br>
&gt;<br>
&gt; I have a basic query regarding SCTP heartbeat re-transmission pattern =
.<br>
&gt;<br>
&gt; As per the RFC 4960 :<br>
&gt;<br>
&gt; Furthermore, when its peer is multi-homed, an endpoint SHOULD try to<b=
r>
&gt; retransmit a chunk that timed out to an active destination transport<b=
r>
&gt; address that is different from the last destination address to which t=
he<br>
&gt; DATA chunk was sent.<br>
&gt;<br>
&gt; Also,<br>
&gt; When retransmitting data that timed out, if the endpoint is multi-home=
d,<br>
&gt; it<br>
&gt; should consider each source-destination address pair in its<br>
retransmission<br>
&gt; selection policy. =A0When retransmitting timed-out data, the endpoint<=
br>
should<br>
&gt; attempt to pick the most divergent source-destination pair from the<br=
>
&gt; original source-destination pair to which the packet was transmitted.<=
br>
&gt;<br>
&gt; Suppose if we have multihomed SCTP endpoints A and B .<br>
&gt;<br>
&gt; A =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0B<br>
&gt;<br>
&gt; a.a.a.p =A0 =A0 =A0 =A0 =A0 =A0 =A0 b.b.b.p<br>
&gt; a.a.a.s =A0 =A0 =A0 =A0 =A0 =A0 =A0 b.b.b.s<br>
&gt;<br>
&gt; If we transmit heartbeat from a.a.a.s to b.b.b.s and it is not<br>
&gt; acknowledged<br>
&gt; so does it re-transmit it using the same src and destination or with<b=
r>
&gt; a.a.a.p to b.b.b.s.<br>
&gt;<br>
&gt; Please help to understand .<br>
&gt;<br>
&gt; Thanks<br>
&gt;<br>
&gt; =3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D<br>
&gt; Notice: The information contained in this e-mail<br>
&gt; message and/or attachments to it may contain<br>
&gt; confidential or privileged information. If you are<br>
&gt; not the intended recipient, any dissemination, use,<br>
&gt; review, distribution, printing or copying of the<br>
&gt; information contained in this e-mail message<br>
&gt; and/or attachments to it are strictly prohibited. If<br>
&gt; you have received this communication in error,<br>
&gt; please notify us by reply e-mail or telephone and<br>
&gt; immediately and permanently delete the message<br>
&gt; and any attachments. Thank you<br>
&gt;<br>
&gt;<br>
<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--bcaec51b1e5109345604d8699a7e--

From prvs=785051959=ankit.mahawar@tcs.com  Thu Mar 21 00:06:33 2013
Return-Path: <prvs=785051959=ankit.mahawar@tcs.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 002A921F9013 for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.188
X-Spam-Level: 
X-Spam-Status: No, score=-6.188 tagged_above=-999 required=5 tests=[AWL=-0.189, BAYES_00=-2.599, J_CHICKENPOX_28=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f7UJSthDGfGl for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:06:32 -0700 (PDT)
Received: from inmumg02.tcs.com (Inmumg02.tcs.com [219.64.33.222]) by ietfa.amsl.com (Postfix) with ESMTP id 8F6F821F9009 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 00:06:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.84,884,1355077800"; d="scan'208";a="131550409"
X-DISCLAIMER: FALSE
Received: from cdctdlpprotect3 (unknown [127.0.0.1]) by cdctdlpprotect3.localdomain (Service) with ESMTP id 03888ABE16; Thu, 21 Mar 2013 12:35:00 +0530 (IST)
Received: from inmumm13.tcs.com (unknown [172.17.9.193]) by cdctdlpprotect3.localdomain (Service) with ESMTP id 7089AABE02; Thu, 21 Mar 2013 12:34:59 +0530 (IST)
In-Reply-To: <CADEup3fS4+hnfp4zZkuBFwPCZWK1CXcLXLrPrYSQ9sF70mDmsg@mail.gmail.com>
References: <OF2FAE4932.D8FCB5F8-ON65257B34.0035654D-65257B34.0035BC57@tcs.com>	<012C3117EDDB3C4781FD802A8C27DD4F24AC0CB5@SACEXCMBX02-PRD.hq.netapp.com> <OF42569AB5.7C738A52-ON65257B35.0023204B-65257B35.0023968B@tcs.com> <CADEup3fS4+hnfp4zZkuBFwPCZWK1CXcLXLrPrYSQ9sF70mDmsg@mail.gmail.com>
From: Ankit Mahawar <ankit.mahawar@tcs.com>
X-KeepSent: 3A70C667:B43B3444-65257B35:0026BD11; type=4; name=$KeepSent
To: Padmalochan Moharana <padman.m@gmail.com>
X-Mailer: Lotus Notes Release 8.5.2FP1 November 30, 2010
Message-ID: <OF3A70C667.B43B3444-ON65257B35.0026BD11-65257B35.002709EB@tcs.com>
Sender: Ankit Mahawar <ankit.mahawar@tcs.com>
Date: Thu, 21 Mar 2013 12:36:24 +0530
X-MIMETrack: Serialize by Router on InMumM13/TCS(Release 8.5.2FP4HF188 | September 13, 2012) at 03/21/2013 12:36:28
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] Query regarding heartbeat re-transmission pattern
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 07:06:33 -0000

Hi All,

Thanks for your replies.

Actually I am a little confused as to whether heartbeats are re-transmi=
tted
when the timer expire or it will be transmitted as per the HB.interval =
even
when the last heartbeat was not acknowledged.

Thanks

                                                                       =
                                                                  
  From:       Padmalochan Moharana <padman.m@gmail.com>                =
                                                                  
                                                                       =
                                                                  
  To:         Ankit Mahawar <ankit.mahawar@tcs.com>                    =
                                                                  
                                                                       =
                                                                  
  Cc:         "Scheffenegger, Richard" <rs@netapp.com>, "tsvwg@ietf.org=
" <tsvwg@ietf.org>                                                
                                                                       =
                                                                  
  Date:       03/21/2013 12:10 PM                                      =
                                                                  
                                                                       =
                                                                  
  Subject:    Re: [tsvwg] Query regarding heartbeat re-transmission pat=
tern                                                              
                                                                       =
                                                                  





Hi Ankit,

Please go through the below section in rfc4960.


8.3.  Path Heartbeat




Thanks,
Padmalochan

On Thu, Mar 21, 2013 at 11:58 AM, Ankit Mahawar <ankit.mahawar@tcs.com>=

wrote:
  Hi Richard,

  I wanted to know the scenario how SCTP behave when the heartbeat is n=
ot
  acknowledged =A0and the timer expires =A0waiting for the acknowledgem=
ent.

  Thanks



  =A0 From: =A0 =A0 =A0 "Scheffenegger, Richard" <rs@netapp.com>

  =A0 To: =A0 =A0 =A0 =A0 Ankit Mahawar <ankit.mahawar@tcs.com>, "tsvwg=
@ietf.org" <
  tsvwg@ietf.org>

  =A0 Date: =A0 =A0 =A0 03/21/2013 12:49 AM

  =A0 Subject: =A0 =A0RE: [tsvwg] Query regarding heartbeat re-transmis=
sion
  pattern






  Hi Ankit,

  is it only the heartbeat that failed (are there other packets flowing=

  between A.p to B.p), in your scenario?

  I would read the 2nd fragment of text, that if A.s to B.s failed, a
  retransmission (of data) should be checked between A.p to B.p first;
  other
  (possible) combinations, like A.p -> B.s, or A.s -> B.p later...

  Regards,

  Richard Scheffenegger

  > -----Original Message-----
  > From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Beh=
alf
  Of
  > Ankit Mahawar
  > Sent: Mittwoch, 20. M=E4rz 2013 10:47
  > To: tsvwg@ietf.org
  > Subject: [tsvwg] Query regarding heartbeat re-transmission pattern
  >
  >
  > Hi All ,
  >
  > I have a basic query regarding SCTP heartbeat re-transmission patte=
rn .
  >
  > As per the RFC 4960 :
  >
  > Furthermore, when its peer is multi-homed, an endpoint SHOULD try t=
o
  > retransmit a chunk that timed out to an active destination transpor=
t
  > address that is different from the last destination address to whic=
h
  the
  > DATA chunk was sent.
  >
  > Also,
  > When retransmitting data that timed out, if the endpoint is
  multi-homed,
  > it
  > should consider each source-destination address pair in its
  retransmission
  > selection policy. =A0When retransmitting timed-out data, the endpoi=
nt
  should
  > attempt to pick the most divergent source-destination pair from the=

  > original source-destination pair to which the packet was transmitte=
d.
  >
  > Suppose if we have multihomed SCTP endpoints A and B .
  >
  > A =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0B
  >
  > a.a.a.p =A0 =A0 =A0 =A0 =A0 =A0 =A0 b.b.b.p
  > a.a.a.s =A0 =A0 =A0 =A0 =A0 =A0 =A0 b.b.b.s
  >
  > If we transmit heartbeat from a.a.a.s to b.b.b.s and it is not
  > acknowledged
  > so does it re-transmit it using the same src and destination or wit=
h
  > a.a.a.p to b.b.b.s.
  >
  > Please help to understand .
  >
  > Thanks
  >
  > =3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D
  > Notice: The information contained in this e-mail
  > message and/or attachments to it may contain
  > confidential or privileged information. If you are
  > not the intended recipient, any dissemination, use,
  > review, distribution, printing or copying of the
  > information contained in this e-mail message
  > and/or attachments to it are strictly prohibited. If
  > you have received this communication in error,
  > please notify us by reply e-mail or telephone and
  > immediately and permanently delete the message
  > and any attachments. Thank you
  >
  >





=



From adrian@olddog.co.uk  Thu Mar 21 00:45:36 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01DAD21F84E8 for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BYGLHaS4k0Tu for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:45:32 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id BBB5421F84AB for <tsvwg@ietf.org>; Thu, 21 Mar 2013 00:45:31 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r2L7jQoG028295;  Thu, 21 Mar 2013 07:45:26 GMT
Received: from 950129200 ([88.128.80.2]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r2L7jNff028239 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 21 Mar 2013 07:45:25 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Black, David'" <david.black@emc.com>, "'Fred Baker \(fred\)'" <fred@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>	<8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com>	<8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com>	<8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com>	<CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@HE111643.EMEA1.CDS.T-INTERNAL.COM>	<8C48B86A895913448548E6D15DA7553B7DD927@xmb-rcd-x09.cisco.com>	<CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE35@HE111643.EMEA1.CDS.T-INTERNAL.COM>	<8C48B86A895913448548E6D15DA7553B7DDCA6@xmb-rcd-x09.cisco.com>	<CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE37@HE111643.EMEA1.CDS.T-INTERNAL.COM>	<8C48B86A895913448548E6D15DA7553B7DDEA9@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE61D@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293AEE61D@MX15A.corp.emc.com>
Date: Thu, 21 Mar 2013 07:45:25 -0000
Message-ID: <02be01ce2608$0ea68130$2bf38390$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHAVz7zqB1kDcIbViyAoVNgS3e5YQGhv6S2AmvUWtABuO95agH8ngzGAbwzB9oB2JXxWAJWhcOdAQurqWsB1rW8WAIjW5UImDW9emA=
Content-Language: en-gb
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 07:45:36 -0000

David, All,

Thanks for this thread, and thanks to Fred for picking up the baton.

Are there any specific questions you would like to ask to the Routing Area wrt
routing traffic, MPLS, or pseudowires?

Thanks,
Adrian

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Black, David
> Sent: 21 March 2013 04:03
> To: Fred Baker (fred); Ruediger.Geib@telekom.de
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] RFC 4594 update: Routing class
> 
> To be clear, that slide was based on ITU-T Y.1566 and
draft-geib-diffserv-intercon.
> The unstated purpose of that slide was to stimulate discussion - which is now
> underway.
> Slide URL: http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx
> 
> The slides on draft-geib-diffserv-intercon are here:
> 	http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-2.ppt
> 
> Thanks,
> --David
> 
> > -----Original Message-----
> > From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Fred
> > Baker (fred)
> > Sent: Wednesday, March 20, 2013 7:05 PM
> > To: Ruediger.Geib@telekom.de
> > Cc: tsvwg@ietf.org
> > Subject: Re: [tsvwg] RFC 4594 update: Routing class
> >
> >
> > On Mar 20, 2013, at 3:12 PM, Ruediger.Geib@telekom.de wrote:
> >
> > > I think we agree, here's an issue.
> >
> > I think we agree that there is a conversation to be had. I'm not sure what
> > actual problem you're trying to solve. I mostly see a proposed solution,
> > displayed in the slide you have in the proceedings.
> >
> >


From brian.e.carpenter@gmail.com  Thu Mar 21 01:19:58 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7B6A21F8F35 for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 01:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.547
X-Spam-Level: 
X-Spam-Status: No, score=-100.547 tagged_above=-999 required=5 tests=[AWL=1.144, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16ad60AMT8VQ for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 01:19:54 -0700 (PDT)
Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) by ietfa.amsl.com (Postfix) with ESMTP id 18A8321F8F2E for <tsvwg@ietf.org>; Thu, 21 Mar 2013 01:19:51 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id gg9so1593798wgb.4 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 01:19:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=YXFZePFxHeP1XATFU1/X6ux4M3b1tb5dQ2ZHLzdvO4o=; b=UlRuKxBJnmfAtocDDWf5ZKreAsJ3cZ3K26YMcBKzx7v75Apjyxd8y2ICJyf8tdAryf v7/ERGw+QqL1Tm7MBWzghLbWXmWSd/g3DMIHgz7YIg/p/J5Ce2EG3miBomxPy183OxkK SlAspnFW9/7sV8E3hOEY2RoLmmNxf8v/AB9Uk7UrCmTRWq6U8F/qn3QAAPEUdpnSAQRS QdNZwgmWYK58tLD0tm41r3HqeDDlkjAiMWzC9SVQM76GTKxqFkYgvm9t16D4/wGXlqc0 o3zkZfTBv59FTw5L146sM5GFvBdtymyBafE842GLpDfRmCGtfG2dbznpDRimUssx2WJs iPLg==
X-Received: by 10.180.189.17 with SMTP id ge17mr3169388wic.17.1363853991209; Thu, 21 Mar 2013 01:19:51 -0700 (PDT)
Received: from [192.168.1.65] (host-2-101-189-49.as13285.net. [2.101.189.49]) by mx.google.com with ESMTPS id dp5sm3188872wib.1.2013.03.21.01.19.48 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Mar 2013 01:19:50 -0700 (PDT)
Message-ID: <514AC2B0.40805@gmail.com>
Date: Thu, 21 Mar 2013 08:20:00 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ruediger.Geib@telekom.de
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>	<8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com>	<8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com>	<8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com>	<CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@HE111643.EMEA1.CDS.T-INTERNAL.COM>	<8C48B86A895913448548E6D15DA7553B7DD927@xmb-rcd-x09.cisco.com>	<CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE35@HE111643.EMEA1.CDS.T-INTERNAL.COM>	<8C48B86A895913448548E6D15DA7553B7DDCA6@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE37@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE37@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: fred@cisco.com, tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 08:19:58 -0000

On 20/03/2013 22:12, Ruediger.Geib@telekom.de wrote:
> I don't exclude CS6 from being sent.
> I know of the router limitations if it's about
> setting DSCPs for internally created traffic.
> That's not limited to BGP or IGP Protocols.
>=20
> CS6 was easy to agree within ITU as those
> providers I talked to use it. And they agreed
> that they wouldn't be happy to carry customer
> traffic in that class.
>=20
> I never said I'd like to change the codepoint in
> general. I'm discussing how to treat the
> PHB/codepoint if received at interconnetion. I
> recall that one of the starting points of our
> current acitivities was Brians remark, that
> changing DSCPs is the default DiffServ behaviour
> at interconnecton interfaces.

That is the architectural model, but of course there
is no issue if peering ISPs choose to agree that
CS6 maps to CS6 and that all routing traffic is labelled
with CS6. Since I understand that to be the essentially
universal current practice, naming it "Routing Class"
doesn't seem to be a big step. Attempting to change it
seems to be a major undertaking (with no obvious benefit).

    Brian

> I think we agree, here's an issue. We don't seem
> to agree about the solution.
>=20
> Regards,
>=20
> R=C3=BCdiger
>=20
> -----Original Message-----
> From: Fred Baker (fred) [mailto:fred@cisco.com]
> Sent: Wednesday, March 20, 2013 10:31 PM
> To: Geib, R=C3=BCdiger
> Cc: tsvwg@ietf.org
> Subject: Re: RFC 4594 update: Routing class
>=20
>=20
> On Mar 20, 2013, at 2:25 PM, <Ruediger.Geib@telekom.de>
>  wrote:
>=20
>> My draft says there may be a provider internal class
>> for routing and network management. It does not exclude
>> a situation where traffic of such a class and codepoint
>> is sent to a network provider. That's an aspect I'd be
>> happy to settle.
>>
>> I've been suggesting AF31 as a potential CS6 match at
>> interconnection. The idea is, that AF32 and AF33 may
>> carry traffic of applications able to deal with an
>> isolated loss. I'd expect the Assured (AF3) class to
>> be produced almost free of loss within a
>> provider network not differentiating the 3 PHBs.
>> Differentiation of AF3 PHBs may be useful to the sending
>> party at interconnection. These are rough thoughts by now.
>=20
> The same is true of CS6.
>=20
> The reason we picked the number 110 000, by the way, was current use. I=
f you want to change the number, it will take more than a stroke of the p=
en; it will take changing at least configuration if not software. What yo=
u wind up with is a class that carries both numbers until the old class g=
oes away.
>=20
> I'm not sure I see the point.
>=20
>> Regards,
>>
>> R=C3=BCdiger
>>
>> -----Original Message-----
>> From: Fred Baker (fred) [mailto:fred@cisco.com]
>> Sent: Wednesday, March 20, 2013 8:53 PM
>> To: Geib, R=C3=BCdiger
>> Cc: david.black@emc.com; tsvwg@ietf.org
>> Subject: Re: RFC 4594 update: Routing class
>>
>>
>> On Mar 20, 2013, at 11:47 AM, Ruediger.Geib@telekom.de wrote:
>>
>>> David, Fred,
>>>
>>> an appropriate class for routing is envisaged by Y.1566
>>> and my draft is based on Y.1566. In fact, marking routing
>>> traffic by CS6 was easy to agree.
>>>
>>> The question is, how to treat traffic marked by CS6 at
>>> interconnection links. David originally objected to having
>>> such a routing class at interconnecton. I think we need
>>> some discussion.
>>>
>>> Routing information should be transmitted free of loss.
>>> That could mean an own class marked by CS6, that could be
>>> any other class resulting in low loss for TCP based
>>> traffic. One could map this traffic from CS6 to
>>> another fitting class and PHB, like Assured AF31.
>>>
>>> There's also an issue with VPN treatment. Providers may
>>> prefer not to transport customer routing traffic together
>>> with their own routing traffic.
>> That, I should think, would be between the provider of the VPN and the=
 client. If the client objects, the client can mop the whole VPN into som=
e service class of his interest.
>>
>>> It may be good to add some text in -03 of my draft.
>>> Objections?
>> No objection to adding text to your draft. I would object to removing =
the service class, as you report David to be proposing and your draft wou=
ld appear to be proposing. I think there could be a lot in AF3 that could=
 sustain an isolated loss while one wanted to preserve inter-provider rou=
ting traffic.
>>
>>> Regards,
>>>
>>> R=C3=BCdiger
>>>
>>>
>>> -----Original Message-----
>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behal=
f Of Fred Baker (fred)
>>> Sent: Wednesday, March 20, 2013 5:28 PM
>>> To: Black, David
>>> Cc: tsvwg@ietf.org
>>> Subject: Re: [tsvwg] RFC 4594 update: Routing class
>>>
>>>
>>> On Mar 19, 2013, at 7:40 PM, "Black, David" <david.black@emc.com> wro=
te:
>>>
>>>> Hi Fred,
>>>>
>>>>> I was unable to attend tsvwg at IETF 86 as it competed with a meeti=
ng I
>>>>> presented in. I am told that there was a presentation in which folk=
s argued
>>>>> against having a class of traffic for routing traffic. I'd like to =
comment on
>>>>> that.
>>>> The argument in particular is about whether a class of traffic is ne=
eded for
>>>> Routing traffic across an interconnection of two carrier networks.
>>>>
>>>> The argument was teed up for discussion in this slide presented in c=
onnection
>>>> with draft-geib-tsvwg-diffserv-intercon-02:
>>>>
>>>> http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx
>>> My only comment on that slide is that the story I told in my previous=
 note happened on inter-provider links. The slide is correct that there i=
s not a defined class in 5127 for admitted video traffic.
>>>
>>>> Thank you for the comments,
>>>> --David
>>>>
>>>>> -----Original Message-----
>>>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Beh=
alf Of Fred
>>>>> Baker (fred)
>>>>> Sent: Tuesday, March 19, 2013 4:53 PM
>>>>> To: tsvwg@ietf.org
>>>>> Subject: [tsvwg] RFC 4594 update: Routing class
>>>>>
>>>>> I was unable to attend twvwg at IETF 86 as it competed with a meeti=
ng I
>>>>> presented in. I am told that there was a presentation in which folk=
s argued
>>>>> against having a class of traffic for routing traffic. I'd like to =
comment on
>>>>> that.
>>>>>
>>>>> The origin of a class of traffic for routing traffic was a bug. The=
 Cisco 7000
>>>>> had an issue with its offloaded forwarding cards, of which it had t=
wo. When
>>>>> there was a route flap, it blew away the route cache and then rebui=
lt it in
>>>>> response to traffic it needed to forward. In that implementation, t=
hat meant
>>>>> that the Route Processor (the CPU) suddenly had all traffic from al=
l sources
>>>>> flooded into it. The impact of that was to make it very difficult f=
or the RP
>>>>> to actually re-populate the Route Cache. Doubleplus ungood. The wor=
k-around
>>>>> was to rate-limit traffic from the line cards to the RP. However, r=
ate
>>>>> limiting the routing traffic worked against getting routing to stab=
ilize, so
>>>>> we marked routing traffic, and did not rate limit *it* from going t=
o the RP.
>>>>>
>>>>> Fast forward nearly 20 years. We don't have that bug anymore, if an=
ything
>>>>> because nobody equipped with a right mind uses the Cisco 7000 any m=
ore.
>>>>>
>>>>> However...
>>>>>
>>>>> If we're going to discuss quality of service for any application, w=
e are
>>>>> making some fundamental assumptions. These include the concept of h=
aving
>>>>> enough bandwidth and so on; we're managing traffic at points in tim=
e when peak
>>>>> traffic loads on a millisecond scale create issues. One of those fu=
ndamental
>>>>> issues is that routing must be current; if we're sending traffic on=
 a route
>>>>> that loops because the other guy updated his route table but we did=
n't, or
>>>>> vice versa, or for which interface or next hop router is no longer =
there, we
>>>>> can discuss jitter, rate, and loss to our heart's content - the app=
lication's
>>>>> traffic isn't going to get there. At. All. And won't until routing =
stabilizes.
>>>>>
>>>>> The fundamental argument for a class of traffic for routing in 2013=
 is not
>>>>> that routing requires certain jitter, rate, or etc characteristics;=
 it is that
>>>>> routing traffic (apart from AQM issues, see separate discussion on
>>>>> aqm@ietf.org) should simply *not*be*dropped* in the normal course o=
f business.
>>>>> Routing is fundamental to all other services the network delivers, =
including
>>>>> QoS, and including every networks's SLAs.
>>>>>
>>>>> Now, one can say that routing is between neighboring nodes, and a r=
outer is
>>>>> able to do special things with traffic it itself originates. It is =
true that a
>>>>> router can do special things with its own traffic, and they do. But=
 BGP
>>>>> Routing frequently goes from Route Arbiter to Route Arbiter instead=
 of Router
>>>>> to Router, which is to say through other routers between routing en=
gines.
>>>>> Traffic through other routers is traffic through other routers, not=
 a router's
>>>>> own traffic. It requires some form of end to end marking to protect=
 it.
>>>>> Something like a DSCP.
>=20
>=20


From Ruediger.Geib@telekom.de  Thu Mar 21 01:34:35 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D11321F8F2D for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 01:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.193
X-Spam-Level: 
X-Spam-Status: No, score=-3.193 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRoNYtdS4-bd for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 01:34:34 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id 69B7521F8F35 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 01:34:34 -0700 (PDT)
Received: from he111631.emea1.cds.t-internal.com ([10.134.93.23]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 21 Mar 2013 09:34:33 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE111631.emea1.cds.t-internal.com ([::1]) with mapi; Thu, 21 Mar 2013 09:34:33 +0100
From: <Ruediger.Geib@telekom.de>
To: <fred@cisco.com>
Date: Thu, 21 Mar 2013 09:34:32 +0100
Thread-Topic: RFC 4594 update: Routing class
Thread-Index: AQHOJb9l8e854Z4LKkWJpxEOJw7eQZivzWaQ
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EF43@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DD927@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE35@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DDCA6@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE37@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DDEA9@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7DDEA9@xmb-rcd-x09.cisco.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 08:34:35 -0000

Fred,

its not simple to figure out what you ask for.

Today EBGP largely is marked as BE (as far as I
know, but I will check that). In many
domains internal routing or management traffic
is marked by CS6 and at least the network
provider representatives I talked to don't
want to transport customer traffic in that
class within their network.

Many routers today don't provide marking
options, if it is about marking internally
created traffic. Mostly that means these
routers set CS6 for this traffic.

I've suggested to standardise a limited set
of classes at interconnection. Traffic marked
by CS6 may occur at interconnections. The draft
I authored should offer some options how to
deal with this.

You
- think that todays practice of classifying EBGP by
  BE and leave router limitation on classification
  of internally created traffic by CS76 as it is.
- do not think anything else should be standardised?
- think standardisation as described above is useful?
- ???

Sorry if I'm thick on that. I'd like to understand your
position and currently I don't. Note that I'm not a
native speaker.

Regards,

R=FCdiger

-----Original Message-----
From: Fred Baker (fred) [mailto:fred@cisco.com]
Sent: Thursday, March 21, 2013 12:05 AM
To: Geib, R=FCdiger
Cc: tsvwg@ietf.org
Subject: Re: RFC 4594 update: Routing class


On Mar 20, 2013, at 3:12 PM, Ruediger.Geib@telekom.de wrote:

> I think we agree, here's an issue.

I think we agree that there is a conversation to be had. I'm not sure what =
actual problem you're trying to solve. I mostly see a proposed solution, di=
splayed in the slide you have in the proceedings.



From Ruediger.Geib@telekom.de  Thu Mar 21 01:48:29 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED51121F8E1C for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 01:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.199
X-Spam-Level: 
X-Spam-Status: No, score=-3.199 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ijjMEtambV3z for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 01:48:25 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id EF81F21F8BB3 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 01:48:24 -0700 (PDT)
Received: from he113445.emea1.cds.t-internal.com ([10.134.93.105]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 21 Mar 2013 09:48:23 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113445.emea1.cds.t-internal.com ([::1]) with mapi; Thu, 21 Mar 2013 09:48:23 +0100
From: <Ruediger.Geib@telekom.de>
To: <brian.e.carpenter@gmail.com>
Date: Thu, 21 Mar 2013 09:48:22 +0100
Thread-Topic: [tsvwg] RFC 4594 update: Routing class
Thread-Index: Ac4mDN0pfG8lzuFtQSyhezOAOUbMQQAAg47Q
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EF6B@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FA@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DD39D@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE21@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DD927@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE35@HE111643.EMEA1.CDS.T-INTERNAL.COM> <8C48B86A895913448548E6D15DA7553B7DDCA6@xmb-rcd-x09.cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74EE37@HE111643.EMEA1.CDS.T-INTERNAL.COM> <514AC2B0.40805@gmail.com>
In-Reply-To: <514AC2B0.40805@gmail.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 08:48:30 -0000

Hi Brian,

we agree that this traffic may appear at interconnection.
And yes, not changing CS6 is one option, which is
desireable in some cases and possibly generally agreed
in others.

As I mentioned, the network providers I talked to don't
want to share their internal routing PHB with customer
traffic. The number is limited but I so far had no
objection. That means, mapping of the CS6 routing PHB at
interconnection is a valid option too.

Now having said that it means, that the company I work
for would not be surprised, if traffic we send to an
interconnection partner is mapped to another PHB - it
should be a suitable one however.

Then I think, as this traffic is pretty important,
offering some standard proposals are useful.

Am I completely wrong with that?

Then you suggest to have an own class for this traffic...
yes I probably am pretty alone if I say, what about
just an own PHB? To me, the Assured Class properties
match the requirements. The class can at least be
engineered to do that.

Regards,

R=FCdiger

-----Original Message-----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
Sent: Thursday, March 21, 2013 9:20 AM
To: Geib, R=FCdiger
Cc: fred@cisco.com; tsvwg@ietf.org
Subject: Re: [tsvwg] RFC 4594 update: Routing class

On 20/03/2013 22:12, Ruediger.Geib@telekom.de wrote:
> I don't exclude CS6 from being sent.
> I know of the router limitations if it's about
> setting DSCPs for internally created traffic.
> That's not limited to BGP or IGP Protocols.
>
> CS6 was easy to agree within ITU as those
> providers I talked to use it. And they agreed
> that they wouldn't be happy to carry customer
> traffic in that class.
>
> I never said I'd like to change the codepoint in
> general. I'm discussing how to treat the
> PHB/codepoint if received at interconnetion. I
> recall that one of the starting points of our
> current acitivities was Brians remark, that
> changing DSCPs is the default DiffServ behaviour
> at interconnecton interfaces.

That is the architectural model, but of course there
is no issue if peering ISPs choose to agree that
CS6 maps to CS6 and that all routing traffic is labelled
with CS6. Since I understand that to be the essentially
universal current practice, naming it "Routing Class"
doesn't seem to be a big step. Attempting to change it
seems to be a major undertaking (with no obvious benefit).

    Brian

> I think we agree, here's an issue. We don't seem
> to agree about the solution.
>
> Regards,
>
> R=FCdiger
>
> -----Original Message-----
> From: Fred Baker (fred) [mailto:fred@cisco.com]
> Sent: Wednesday, March 20, 2013 10:31 PM
> To: Geib, R=FCdiger
> Cc: tsvwg@ietf.org
> Subject: Re: RFC 4594 update: Routing class
>
>
> On Mar 20, 2013, at 2:25 PM, <Ruediger.Geib@telekom.de>
>  wrote:
>
>> My draft says there may be a provider internal class
>> for routing and network management. It does not exclude
>> a situation where traffic of such a class and codepoint
>> is sent to a network provider. That's an aspect I'd be
>> happy to settle.
>>
>> I've been suggesting AF31 as a potential CS6 match at
>> interconnection. The idea is, that AF32 and AF33 may
>> carry traffic of applications able to deal with an
>> isolated loss. I'd expect the Assured (AF3) class to
>> be produced almost free of loss within a
>> provider network not differentiating the 3 PHBs.
>> Differentiation of AF3 PHBs may be useful to the sending
>> party at interconnection. These are rough thoughts by now.
>
> The same is true of CS6.
>
> The reason we picked the number 110 000, by the way, was current use. If =
you want to change the number, it will take more than a stroke of the pen; =
it will take changing at least configuration if not software. What you wind=
 up with is a class that carries both numbers until the old class goes away=
.
>
> I'm not sure I see the point.
>
>> Regards,
>>
>> R=FCdiger
>>
>> -----Original Message-----
>> From: Fred Baker (fred) [mailto:fred@cisco.com]
>> Sent: Wednesday, March 20, 2013 8:53 PM
>> To: Geib, R=FCdiger
>> Cc: david.black@emc.com; tsvwg@ietf.org
>> Subject: Re: RFC 4594 update: Routing class
>>
>>
>> On Mar 20, 2013, at 11:47 AM, Ruediger.Geib@telekom.de wrote:
>>
>>> David, Fred,
>>>
>>> an appropriate class for routing is envisaged by Y.1566
>>> and my draft is based on Y.1566. In fact, marking routing
>>> traffic by CS6 was easy to agree.
>>>
>>> The question is, how to treat traffic marked by CS6 at
>>> interconnection links. David originally objected to having
>>> such a routing class at interconnecton. I think we need
>>> some discussion.
>>>
>>> Routing information should be transmitted free of loss.
>>> That could mean an own class marked by CS6, that could be
>>> any other class resulting in low loss for TCP based
>>> traffic. One could map this traffic from CS6 to
>>> another fitting class and PHB, like Assured AF31.
>>>
>>> There's also an issue with VPN treatment. Providers may
>>> prefer not to transport customer routing traffic together
>>> with their own routing traffic.
>> That, I should think, would be between the provider of the VPN and the c=
lient. If the client objects, the client can mop the whole VPN into some se=
rvice class of his interest.
>>
>>> It may be good to add some text in -03 of my draft.
>>> Objections?
>> No objection to adding text to your draft. I would object to removing th=
e service class, as you report David to be proposing and your draft would a=
ppear to be proposing. I think there could be a lot in AF3 that could susta=
in an isolated loss while one wanted to preserve inter-provider routing tra=
ffic.
>>
>>> Regards,
>>>
>>> R=FCdiger
>>>
>>>
>>> -----Original Message-----
>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf =
Of Fred Baker (fred)
>>> Sent: Wednesday, March 20, 2013 5:28 PM
>>> To: Black, David
>>> Cc: tsvwg@ietf.org
>>> Subject: Re: [tsvwg] RFC 4594 update: Routing class
>>>
>>>
>>> On Mar 19, 2013, at 7:40 PM, "Black, David" <david.black@emc.com> wrote=
:
>>>
>>>> Hi Fred,
>>>>
>>>>> I was unable to attend tsvwg at IETF 86 as it competed with a meeting=
 I
>>>>> presented in. I am told that there was a presentation in which folks =
argued
>>>>> against having a class of traffic for routing traffic. I'd like to co=
mment on
>>>>> that.
>>>> The argument in particular is about whether a class of traffic is need=
ed for
>>>> Routing traffic across an interconnection of two carrier networks.
>>>>
>>>> The argument was teed up for discussion in this slide presented in con=
nection
>>>> with draft-geib-tsvwg-diffserv-intercon-02:
>>>>
>>>> http://www.ietf.org/proceedings/86/slides/slides-86-tsvwg-5.pptx
>>> My only comment on that slide is that the story I told in my previous n=
ote happened on inter-provider links. The slide is correct that there is no=
t a defined class in 5127 for admitted video traffic.
>>>
>>>> Thank you for the comments,
>>>> --David
>>>>
>>>>> -----Original Message-----
>>>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behal=
f Of Fred
>>>>> Baker (fred)
>>>>> Sent: Tuesday, March 19, 2013 4:53 PM
>>>>> To: tsvwg@ietf.org
>>>>> Subject: [tsvwg] RFC 4594 update: Routing class
>>>>>
>>>>> I was unable to attend twvwg at IETF 86 as it competed with a meeting=
 I
>>>>> presented in. I am told that there was a presentation in which folks =
argued
>>>>> against having a class of traffic for routing traffic. I'd like to co=
mment on
>>>>> that.
>>>>>
>>>>> The origin of a class of traffic for routing traffic was a bug. The C=
isco 7000
>>>>> had an issue with its offloaded forwarding cards, of which it had two=
. When
>>>>> there was a route flap, it blew away the route cache and then rebuilt=
 it in
>>>>> response to traffic it needed to forward. In that implementation, tha=
t meant
>>>>> that the Route Processor (the CPU) suddenly had all traffic from all =
sources
>>>>> flooded into it. The impact of that was to make it very difficult for=
 the RP
>>>>> to actually re-populate the Route Cache. Doubleplus ungood. The work-=
around
>>>>> was to rate-limit traffic from the line cards to the RP. However, rat=
e
>>>>> limiting the routing traffic worked against getting routing to stabil=
ize, so
>>>>> we marked routing traffic, and did not rate limit *it* from going to =
the RP.
>>>>>
>>>>> Fast forward nearly 20 years. We don't have that bug anymore, if anyt=
hing
>>>>> because nobody equipped with a right mind uses the Cisco 7000 any mor=
e.
>>>>>
>>>>> However...
>>>>>
>>>>> If we're going to discuss quality of service for any application, we =
are
>>>>> making some fundamental assumptions. These include the concept of hav=
ing
>>>>> enough bandwidth and so on; we're managing traffic at points in time =
when peak
>>>>> traffic loads on a millisecond scale create issues. One of those fund=
amental
>>>>> issues is that routing must be current; if we're sending traffic on a=
 route
>>>>> that loops because the other guy updated his route table but we didn'=
t, or
>>>>> vice versa, or for which interface or next hop router is no longer th=
ere, we
>>>>> can discuss jitter, rate, and loss to our heart's content - the appli=
cation's
>>>>> traffic isn't going to get there. At. All. And won't until routing st=
abilizes.
>>>>>
>>>>> The fundamental argument for a class of traffic for routing in 2013 i=
s not
>>>>> that routing requires certain jitter, rate, or etc characteristics; i=
t is that
>>>>> routing traffic (apart from AQM issues, see separate discussion on
>>>>> aqm@ietf.org) should simply *not*be*dropped* in the normal course of =
business.
>>>>> Routing is fundamental to all other services the network delivers, in=
cluding
>>>>> QoS, and including every networks's SLAs.
>>>>>
>>>>> Now, one can say that routing is between neighboring nodes, and a rou=
ter is
>>>>> able to do special things with traffic it itself originates. It is tr=
ue that a
>>>>> router can do special things with its own traffic, and they do. But B=
GP
>>>>> Routing frequently goes from Route Arbiter to Route Arbiter instead o=
f Router
>>>>> to Router, which is to say through other routers between routing engi=
nes.
>>>>> Traffic through other routers is traffic through other routers, not a=
 router's
>>>>> own traffic. It requires some form of end to end marking to protect i=
t.
>>>>> Something like a DSCP.
>
>


From Ruediger.Geib@telekom.de  Thu Mar 21 06:13:29 2013
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8972B21F8A8F for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 06:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.204
X-Spam-Level: 
X-Spam-Status: No, score=-3.204 tagged_above=-999 required=5 tests=[AWL=0.045,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cTqoNMazNeqL for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 06:13:29 -0700 (PDT)
Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) by ietfa.amsl.com (Postfix) with ESMTP id A114921F8AB7 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 06:13:28 -0700 (PDT)
Received: from he113656.emea1.cds.t-internal.com ([10.134.99.16]) by tcmail91.telekom.de with ESMTP/TLS/AES128-SHA; 21 Mar 2013 14:13:26 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113656.emea1.cds.t-internal.com ([::1]) with mapi; Thu, 21 Mar 2013 14:13:26 +0100
From: <Ruediger.Geib@telekom.de>
To: <gorry@erg.abdn.ac.uk>, <david.black@emc.com>, <jmpolk@cisco.com>
Date: Thu, 21 Mar 2013 14:13:24 +0100
Thread-Topic: Diffserv interconnect issues - Scavenger / lessthan Best effort class
Thread-Index: Ac4jwId4AYOBsSMQT/2U4ik2yR3o4gCczkfg
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74F1FF@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA94A2@MX15A.corp.emc.com> <CA7A7C64CC4ADB458B74477EA99DF6F5016A67EC97@HE111643.EMEA1.CDS.T-INTERNAL.COM> <12a7c296ca70fe33ba66a86371b22dd5.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <12a7c296ca70fe33ba66a86371b22dd5.squirrel@www.erg.abdn.ac.uk>
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
Cc: tsvwg@ietf.org
Subject: [tsvwg] Diffserv interconnect issues - Scavenger / lessthan Best effort class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 13:13:29 -0000

Dear chairs,

during the last IETF meeting, one question
was whether and if so how a Less than Best
Effort / Scavenger class is or should be
supported at Interconnection points.

I can't give a clear answer. I hope my
statements and questions below help to
achieve progress on the topic.

Definition:
The Default Class could be engineered to
consist of two PHBs, differentiated by a
drop policy similar to those of AF. The
default class is however not engineered
to meet any specific QoS. Correct?

IETF Standardisation
Only the Default PHB is specified by IETF.
Internet2 specified a Scavenger PHB. MEF has
a better than Best Effort PHB.
Should IETF specify a second PHB in the
Default class?
Note that I don't think this specification
should be part of the DiffServ Interconnection
draft.

Is there another IETF Less than Best Effort
standard being desired if the idea of having
two PHBs in the Default class is wrong?

If there is interst in standardising a Less
than Best Effort class, should it be supported
at interconnection points?

Please add questions or ask, if I missed
something or if I'm not clear above.

Regards,

R=FCdiger

From brian.e.carpenter@gmail.com  Thu Mar 21 06:58:12 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 946E021F84C9 for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 06:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.252
X-Spam-Level: 
X-Spam-Status: No, score=-99.252 tagged_above=-999 required=5 tests=[AWL=-0.331, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id souK6YVIe5hA for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 06:58:10 -0700 (PDT)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id AEAB221F8A4E for <tsvwg@ietf.org>; Thu, 21 Mar 2013 06:58:09 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id x51so2334877wey.18 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 06:58:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZLsV6G4o94TwfkKzgyER9eTtRNBa5oipQ4X47/z+ImI=; b=X2ICiG3PgEiQM8QkXX+AmlBcdqHFd8KvDDYDqHqc5VI2HB5fh0i9bOaXsmQsTbdtuU BRXUItx4u4xcvrz57B/ay2VU1xR7/jZUVzVij5y7P6F6cw+vVvVRzDJiVOftmg3RsAgX OcB0w6F1e3rnYUJOKwJaJgB2MDfa0WN5bJLf7u7WpDJKScRIy0wD3ZEHpchHSDMSllgJ F7dgPog6qqR6VweuX1MWrcvsNZY0owPhv/5ZUsnDmqyprudsaxita994uw3yo8KGHPwx uY3Ze1jQ8EpcBJbQXgm+QGMTlkGe1De86sP4YOsVdcdTBu2x4NTq06EvxOt5gifisL5v rCYw==
X-Received: by 10.180.189.17 with SMTP id ge17mr5150508wic.17.1363874287686; Thu, 21 Mar 2013 06:58:07 -0700 (PDT)
Received: from [192.168.1.65] (host-2-101-189-49.as13285.net. [2.101.189.49]) by mx.google.com with ESMTPS id fg6sm5421987wib.10.2013.03.21.06.58.05 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Mar 2013 06:58:06 -0700 (PDT)
Message-ID: <514B11F9.4020709@gmail.com>
Date: Thu, 21 Mar 2013 13:58:17 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ruediger.Geib@telekom.de
References: <8D3D17ACE214DC429325B2B98F3AE71290FA94A2@MX15A.corp.emc.com>	<CA7A7C64CC4ADB458B74477EA99DF6F5016A67EC97@HE111643.EMEA1.CDS.T-INTERNAL.COM>	<12a7c296ca70fe33ba66a86371b22dd5.squirrel@www.erg.abdn.ac.uk> <CA7A7C64CC4ADB458B74477EA99DF6F5016A74F1FF@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5016A74F1FF@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: gorry@erg.abdn.ac.uk, jmpolk@cisco.com, tsvwg@ietf.org
Subject: Re: [tsvwg] Diffserv interconnect issues - Scavenger / lessthan Best effort class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 13:58:12 -0000

I can understand why an inter-ISP SLA might include an LBE class.

The IETF failed to advance draft-bless-diffserv-lbe-phb.
As far as a PHB goes, I haven't changed my opinion since I wrote this:

-------- Original Message --------
Subject: LBE using RFC 2474
Date: Wed, 10 Nov 1999 13:00:27 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
To: Diff Serv <diffserv@ietf.org>

Kathie and I discussed the less than best effort requirement expressed
by some people, and concluded that this can be done using RFC 2474
with no change:

In the DSCP to PHB mapping table, map the DSCP value 0 (default)
to the PHB Class Selector 2. Then classify the "LBE" tarffic
into a BA that receives PHB Class Selector 1.

This usage overrides the SHOULD in RFC 2474, section 4.2.2.2,
but that is why we use SHOULD instead of MUST.

Regards
   Brian Carpenter




On 21/03/2013 13:13, Ruediger.Geib@telekom.de wrote:
> Dear chairs,
>=20
> during the last IETF meeting, one question
> was whether and if so how a Less than Best
> Effort / Scavenger class is or should be
> supported at Interconnection points.
>=20
> I can't give a clear answer. I hope my
> statements and questions below help to
> achieve progress on the topic.
>=20
> Definition:
> The Default Class could be engineered to
> consist of two PHBs, differentiated by a
> drop policy similar to those of AF. The
> default class is however not engineered
> to meet any specific QoS. Correct?
>=20
> IETF Standardisation
> Only the Default PHB is specified by IETF.
> Internet2 specified a Scavenger PHB. MEF has
> a better than Best Effort PHB.
> Should IETF specify a second PHB in the
> Default class?
> Note that I don't think this specification
> should be part of the DiffServ Interconnection
> draft.
>=20
> Is there another IETF Less than Best Effort
> standard being desired if the idea of having
> two PHBs in the Default class is wrong?
>=20
> If there is interst in standardising a Less
> than Best Effort class, should it be supported
> at interconnection points?
>=20
> Please add questions or ask, if I missed
> something or if I'm not clear above.
>=20
> Regards,
>=20
> R=C3=BCdiger
>=20


From graham@apolix.co.za  Thu Mar 21 09:06:47 2013
Return-Path: <graham@apolix.co.za>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF0721F911F for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 09:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.36
X-Spam-Level: 
X-Spam-Status: No, score=-1.36 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVGiaCKlpzVC for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 09:06:47 -0700 (PDT)
Received: from oryx.apolix.co.za (oryx.apolix.co.za [IPv6:2001:43e8:400::11]) by ietfa.amsl.com (Postfix) with ESMTP id 5B15021F910E for <tsvwg@ietf.org>; Thu, 21 Mar 2013 09:06:42 -0700 (PDT)
Received: from mirage.apolix.co.za ([2001:43e8:8:200::50]:60287) by oryx.apolix.co.za with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <graham@apolix.co.za>) id 1UIi0j-000585-L6 for tsvwg@ietf.org; Thu, 21 Mar 2013 18:06:38 +0200
Message-ID: <514B2FE9.90101@apolix.co.za>
Date: Thu, 21 Mar 2013 18:06:01 +0200
From: Graham Beneke <graham@apolix.co.za>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <C38E406F654CD249AB7D30B93B0207F517F54D92@EXCHANGE.cablelabs.com> <alpine.DEB.2.00.1303131826130.28820@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1303131826130.28820@uplift.swm.pp.se>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-AuthenticatedID: graham@apolix.co.za
X-Report-Abuse-To: abuse@apolix.co.za
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - oryx.apolix.co.za
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - apolix.co.za
X-Get-Message-Sender-Via: oryx.apolix.co.za: authenticated_id: graham@apolix.co.za
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 16:06:47 -0000

On 13/03/2013 19:32, Mikael Abrahamsson wrote:
> On Wed, 13 Mar 2013, Greg White wrote:
> 
>> Some may consider 100ms a big number.

I've heard the 100ms figure thrown about quite a bit. In the VoIP world
its considered to be the pain threshold for a reasonable call experience
and for "general Internet" (aka http browsing) it doesn't normally
impact the user experience notably.

> My personal opinion that for sustained congestion, there is very little
> use to ever keep a packet more than ~50 ms in a buffer. There is use to
> have larger buffers for short term smoothing of flows, but if the buffer
> has been at higher depths than 50 ms for several seconds, just start
> dropping/marking aggressively until the buffer is substantially lower
> than this. This example if more in a general WRED scenario. If it's a
> per-flow queueing scenario with fair-queue or alike, then of course
> there is little reason to drop the traffic early.

I agree. I've been playing around with building RED queues that buffer
only 10-50ms and the user experience seems to be quite good. Anything
more than that and user experience suffers.

The other issue that this research probably missed is the problem of
"dark buffers" - those buffers that only start filling up and causing
latency when some other part of the network fails and the network
experiences unplanned congestion.

I have observed numerous incidents on peer and upstream networks where
latency through a single buffer suddenly goes from ~0 ms to as much as
250 ms during a congestion incident. Most of this will not be solved by
a single test and needs ongoing monitoring and trends analysis to detect
and resolve.

-- 
Graham Beneke

From g.white@CableLabs.com  Thu Mar 21 09:59:19 2013
Return-Path: <g.white@CableLabs.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1A9E21F9178; Thu, 21 Mar 2013 09:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VrBmo6mdY6Lf; Thu, 21 Mar 2013 09:59:19 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id E6C9721F8F44; Thu, 21 Mar 2013 09:59:15 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id r2LGx4bn003862; Thu, 21 Mar 2013 10:59:04 -0600
Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Thu, 21 Mar 2013 10:59:04 -0600 (MDT)
X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com)
Received: from EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee]) by EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee%11]) with mapi id 14.02.0328.009; Thu, 21 Mar 2013 10:59:03 -0600
From: Greg White <g.white@CableLabs.com>
To: Graham Beneke <graham@apolix.co.za>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] how much of a problem is buffer bloat today?
Thread-Index: AQHOH/Zy6Y2ujr6xyky0EcKlL8uw15ikI2qA///Q/gCAAFGcgIAMepqA//+qP4A=
Date: Thu, 21 Mar 2013 16:59:03 +0000
Message-ID: <C38E406F654CD249AB7D30B93B0207F517F5E4AE@EXCHANGE.cablelabs.com>
In-Reply-To: <514B2FE9.90101@apolix.co.za>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.1.130117
x-originating-ip: [10.4.1.127]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <88FA79DEB375EF42B2E096171593333A@cablelabs.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 16:59:19 -0000

....cross posting to aqm.

On 3/21/13 10:06 AM, "Graham Beneke" <graham@apolix.co.za> wrote:

>On 13/03/2013 19:32, Mikael Abrahamsson wrote:
>> On Wed, 13 Mar 2013, Greg White wrote:
>>=20
>>> Some may consider 100ms a big number.
>
>I've heard the 100ms figure thrown about quite a bit. In the VoIP world
>its considered to be the pain threshold for a reasonable call experience
>and for "general Internet" (aka http browsing) it doesn't normally
>impact the user experience notably.

Web browsing *is* sensitive to RTT (though maybe less so than VoIP or
gaming).  Page load time increases linearly with RTT (at approximately
10x-20x).  So adding 100ms of *unnecessary* buffering latency adds ~1-2
seconds of *unnecessary* delay to page loads.=20


From oliver@net.t-labs.tu-berlin.de  Thu Mar 21 10:50:44 2013
Return-Path: <oliver@net.t-labs.tu-berlin.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8806621F9158 for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 10:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.284
X-Spam-Level: 
X-Spam-Status: No, score=-0.284 tagged_above=-999 required=5 tests=[AWL=2.317,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qdkjaA15sJ8R for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 10:50:38 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:4:130:149:220:252]) by ietfa.amsl.com (Postfix) with ESMTP id BBF6B21F9170 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 10:50:26 -0700 (PDT)
Received: from [IPv6:2001:470:96b9:1:14cb:af2e:2e24:2838] (ibis.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:1:14cb:af2e:2e24:2838]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 84B434C4C25;  Thu, 21 Mar 2013 18:50:25 +0100 (CET)
Message-ID: <514B484F.2070902@net.t-labs.tu-berlin.de>
Date: Thu, 21 Mar 2013 18:50:07 +0100
From: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: tsvwg@ietf.org, bloat@lists.bufferbloat.net
References: <51408BF4.7090304@cisco.com> <8C48B86A895913448548E6D15DA7553B7D020F@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7D020F@xmb-rcd-x09.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 17:50:44 -0000

(cross posting to bloat)

On 03/13/2013 04:28 PM, Fred Baker (fred) wrote:
> On Mar 13, 2013, at 10:23 AM, Eliot Lear <lear@cisco.com> wrote:
> 
>> I don't have an answer to that question, but Mark Allman from ICIR did
>> attempt to characterize buffer bloat on the Internet through an
>> empirical study that appeared in the January edition of CCR.  You can
>> find a reference to that paper at the following URL:
>>
>> http://www.sigcomm.org/ccr/papers/2013/January/2427036.2427041
>>
>> Eliot
> 
> Well, yes, he says that in his gigabit FTTH network he doesn't see megabit-scale problems.

Marks paper is /not/ about measuring buffer bloat in an FTTH network.
While he uses the FTTH network as /vantage point/, the paper actually
measures buffer bloat in various remote networks.

Marks paper is not the only study suggesting the extend of the problem
to be modest. The presented results are in line with recent findings by
Chirichella and Rossi [1]. Based on unpublished work, I can confirm the
low magnitude of the problem. I analyzed passive measurements of
residential users traffic from multiple continents (~60 million IPs
originating from 50\% of all ASes) and rarely find excessive RTTs that,
among other problems, can indicate the presence of buffer bloat.

In summary, bloated buffers exist and buffer bloat can be demonstrated,
but current findings suggest that it rarely occurs in practice. One
potential reason being that users do not often sustainably utilize
their uplink capacity and fill-up their potentially large queues.

Oliver

[1] To the Moon and back: are Internet bufferbloat delays really that large?
http://perso.telecom-paristech.fr/~drossi/paper/rossi13tma-a.pdf

From oliver@net.t-labs.tu-berlin.de  Thu Mar 21 11:14:05 2013
Return-Path: <oliver@net.t-labs.tu-berlin.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9934521F907E for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.442
X-Spam-Level: 
X-Spam-Status: No, score=-1.442 tagged_above=-999 required=5 tests=[AWL=1.158,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vpos4rSt6p+8 for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:14:05 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:4:130:149:220:252]) by ietfa.amsl.com (Postfix) with ESMTP id D3AC321F9072 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 11:14:04 -0700 (PDT)
Received: from [IPv6:2001:470:96b9:1:14cb:af2e:2e24:2838] (ibis.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:1:14cb:af2e:2e24:2838]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 1ED9B4C4C25;  Thu, 21 Mar 2013 19:14:04 +0100 (CET)
Message-ID: <514B4DEB.3020402@net.t-labs.tu-berlin.de>
Date: Thu, 21 Mar 2013 19:14:03 +0100
From: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: "tsvwg@ietf.org" <tsvwg@ietf.org>,  bloat <bloat@lists.bufferbloat.net>
References: <51408BF4.7090304@cisco.com> <8C48B86A895913448548E6D15DA7553B7D020F@xmb-rcd-x09.cisco.com> <514B484F.2070902@net.t-labs.tu-berlin.de> <CAGhGL2Cu6m-s_6SyZPMGm0ebXjn4_wbftNcY519v11Lk3CvaJg@mail.gmail.com>
In-Reply-To: <CAGhGL2Cu6m-s_6SyZPMGm0ebXjn4_wbftNcY519v11Lk3CvaJg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [tsvwg] [Bloat]  how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 18:14:05 -0000

> I believe you are actually measuring the *fraction of the time* your
> measurements show bad latency

Yes.

> The best data I've seen on how widespread the problem is is the ICSI
> Netalyzr scatter plots results

One has to be extremely careful on what to conclude from this data.
The Netalyzr data shows that bloated buffers _exist_, not that they
are _used_ in practice. Or as Mark has put it: "[it] shows that large
delays due to buffering can happen, not that they do happen."
Empirical evidence cited in my previous mail suggests that buffer
bloat does not happen often.

> I encourage everyone to run netalyzr and/or the mlabs tests for
> bufferbloat on your own broadband connections, or do simple copy and
> ping tests inside your own house over wifi to your local file servers....

While this will identify bloated buffers, it does not help in answering
what fraction of Internet users actually experience the problem.

Oliver

From touch@isi.edu  Thu Mar 21 11:21:16 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C4E321F9109 for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.769
X-Spam-Level: 
X-Spam-Status: No, score=-105.769 tagged_above=-999 required=5 tests=[AWL=0.830, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cutc3eUuA8HJ for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:21:15 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id AC2BC21F90DA for <tsvwg@ietf.org>; Thu, 21 Mar 2013 11:21:15 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r2LIJTdh020582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 21 Mar 2013 11:19:29 -0700 (PDT)
Message-ID: <514B4F2A.3030902@isi.edu>
Date: Thu, 21 Mar 2013 11:19:22 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 18:21:16 -0000

Again, I don't like classes named for applications - or protocols, or 
groups of protocols. This ought to be something you can describe in 
terms of the service provided, not how the service is used.

Joe

On 3/19/2013 1:53 PM, Fred Baker (fred) wrote:
> I was unable to attend twvwg at IETF 86 as it competed with a meeting I presented in. I am told that there was a presentation in which folks argued against having a class of traffic for routing traffic. I'd like to comment on that.
>
> The origin of a class of traffic for routing traffic was a bug. The Cisco 7000 had an issue with its offloaded forwarding cards, of which it had two. When there was a route flap, it blew away the route cache and then rebuilt it in response to traffic it needed to forward. In that implementation, that meant that the Route Processor (the CPU) suddenly had all traffic from all sources flooded into it. The impact of that was to make it very difficult for the RP to actually re-populate the Route Cache. Doubleplus ungood. The work-around was to rate-limit traffic from the line cards to the RP. However, rate limiting the routing traffic worked against getting routing to stabilize, so we marked routing traffic, and did not rate limit *it* from going to the RP.
>
> Fast forward nearly 20 years. We don't have that bug anymore, if anything because nobody equipped with a right mind uses the Cisco 7000 any more.
>
> However...
>
> If we're going to discuss quality of service for any application, we are making some fundamental assumptions. These include the concept of having enough bandwidth and so on; we're managing traffic at points in time when peak traffic loads on a millisecond scale create issues. One of those fundamental issues is that routing must be current; if we're sending traffic on a route that loops because the other guy updated his route table but we didn't, or vice versa, or for which interface or next hop router is no longer there, we can discuss jitter, rate, and loss to our heart's content - the application's traffic isn't going to get there. At. All. And won't until routing stabilizes.
>
> The fundamental argument for a class of traffic for routing in 2013 is not that routing requires certain jitter, rate, or etc characteristics; it is that routing traffic (apart from AQM issues, see separate discussion on aqm@ietf.org) should simply *not*be*dropped* in the normal course of business. Routing is fundamental to all other services the network delivers, including QoS, and including every networks's SLAs.
>
> Now, one can say that routing is between neighboring nodes, and a router is able to do special things with traffic it itself originates. It is true that a router can do special things with its own traffic, and they do. But BGP Routing frequently goes from Route Arbiter to Route Arbiter instead of Router to Router, which is to say through other routers between routing engines. Traffic through other routers is traffic through other routers, not a router's own traffic. It requires some form of end to end marking to protect it. Something like a DSCP.
>

From bidulock@openss7.org  Thu Mar 21 11:35:00 2013
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF7B221F906F for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_28=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m6su3wplqd9s for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:35:00 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) by ietfa.amsl.com (Postfix) with ESMTP id EE1BB21F9080 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 11:34:53 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r2LIYobq002214; Thu, 21 Mar 2013 12:34:50 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r2LIYo8k015759; Thu, 21 Mar 2013 12:34:50 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id r2LIYn36015751; Thu, 21 Mar 2013 12:34:49 -0600
Date: Thu, 21 Mar 2013 12:34:49 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Ankit Mahawar <ankit.mahawar@tcs.com>
Message-ID: <20130321183449.GA12988@openss7.org>
Mail-Followup-To: Ankit Mahawar <ankit.mahawar@tcs.com>, Padmalochan Moharana <padman.m@gmail.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <OF2FAE4932.D8FCB5F8-ON65257B34.0035654D-65257B34.0035BC57@tcs.com> <012C3117EDDB3C4781FD802A8C27DD4F24AC0CB5@SACEXCMBX02-PRD.hq.netapp.com> <OF42569AB5.7C738A52-ON65257B35.0023204B-65257B35.0023968B@tcs.com> <CADEup3fS4+hnfp4zZkuBFwPCZWK1CXcLXLrPrYSQ9sF70mDmsg@mail.gmail.com> <OF3A70C667.B43B3444-ON65257B35.0026BD11-65257B35.002709EB@tcs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF3A70C667.B43B3444-ON65257B35.0026BD11-65257B35.002709EB@tcs.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] Query regarding heartbeat re-transmission pattern
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 18:35:01 -0000

Ankit,

Transmitted on HB.interval, retransmitted on RTO.

--brian

Ankit Mahawar wrote:                (Thu, 21 Mar 2013 12:36:24)
> Hi All,
> 
> Thanks for your replies.
> 
> Actually I am a little confused as to whether heartbeats are re-transmitted
> when the timer expire or it will be transmitted as per the HB.interval even
> when the last heartbeat was not acknowledged.
> 
> Thanks
> 

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

From oliver@net.t-labs.tu-berlin.de  Thu Mar 21 12:09:02 2013
Return-Path: <oliver@net.t-labs.tu-berlin.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87ECA21F8FAC for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 12:09:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.828
X-Spam-Level: 
X-Spam-Status: No, score=-1.828 tagged_above=-999 required=5 tests=[AWL=0.772,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QW9+X9LNp3y9 for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 12:09:01 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:4:130:149:220:252]) by ietfa.amsl.com (Postfix) with ESMTP id 3FBA821F8FAA for <tsvwg@ietf.org>; Thu, 21 Mar 2013 12:09:01 -0700 (PDT)
Received: from [IPv6:2001:470:96b9:1:14cb:af2e:2e24:2838] (ibis.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:1:14cb:af2e:2e24:2838]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 074004C4DF1;  Thu, 21 Mar 2013 20:08:57 +0100 (CET)
Message-ID: <514B5AC8.8000502@net.t-labs.tu-berlin.de>
Date: Thu, 21 Mar 2013 20:08:56 +0100
From: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: tsvwg@ietf.org, bloat <bloat@lists.bufferbloat.net>
References: <51408BF4.7090304@cisco.com>
In-Reply-To: <51408BF4.7090304@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 19:09:02 -0000

On 03/13/2013 03:23 PM, Eliot Lear wrote:
> I don't have an answer to that question, but Mark Allman from ICIR did
> attempt to characterize buffer bloat on the Internet through an
> empirical study that appeared in the January edition of CCR.  You can
> find a reference to that paper at the following URL:
> 
> http://www.sigcomm.org/ccr/papers/2013/January/2427036.2427041

The full extend of the answer is still unclear to me. We have recently
attempt to complement the rather technical and QoS centric view on the
buffer bloat problem by estimating the user experience impact:

BufferBloat: How Relevant? A QoE Perspective on Buffer Sizing.
Oliver Hohlfeld, Enric Pujol, Florin Ciucu, Anja Feldmann, Paul Barford
http://downloads.ohohlfeld.com/paper/bufferbloat-qoe-tr.pdf

The paper studies the impact of buffer sizes on VoIP, IPTV, and web
browsing Quality of Experience (QoE). We find that:

- oversized buffers indeed degrade QoE when they are sustainable filled.
- however, large buffers do not always degrade user experience.
- the level of congestion significantly degrades QoE, oftentimes more
  than buffer sizes.

One example discussed in the paper is web browsing. When the level of
congestion is low, HTTP transactions benefit from "large" buffers as
they reduce losses by absorbing transient bursts. When the level of
congestion is high, transfer times become RTT dominated and the queuing
delays start to kick in.

Note that objective QoE metrics used in our paper also do not provide
the full picture:
(i) objective QoE metrics and subjective user experience are not
    always correlated.
(ii) the influence memory effects is still unclear (e.g., for how
     long will a user be influenced by a single degradation and how
     does it alter his behavior?). Psychological insights are only
     available for short-time scales.
(ii) even if service degradations exist that would degrade the user
     experience, the user might not always notice them.

In summary, the question on how much of a problem buffer bloat currently
is cannot be fully answered and still requires further research.

Oliver

From swmike@swm.pp.se  Thu Mar 21 12:25:37 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDA6D21F905B for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 12:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.355
X-Spam-Level: 
X-Spam-Status: No, score=-2.355 tagged_above=-999 required=5 tests=[AWL=0.244,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5pPHzHRrVL4J for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 12:25:37 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 3B26F21F9057 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 12:25:37 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 6ACCD9C; Thu, 21 Mar 2013 20:25:35 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 5DA8C9A; Thu, 21 Mar 2013 20:25:35 +0100 (CET)
Date: Thu, 21 Mar 2013 20:25:35 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
In-Reply-To: <514B5AC8.8000502@net.t-labs.tu-berlin.de>
Message-ID: <alpine.DEB.2.00.1303212019520.2309@uplift.swm.pp.se>
References: <51408BF4.7090304@cisco.com> <514B5AC8.8000502@net.t-labs.tu-berlin.de>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: tsvwg@ietf.org, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [tsvwg] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 19:25:37 -0000

On Thu, 21 Mar 2013, Oliver Hohlfeld wrote:

> In summary, the question on how much of a problem buffer bloat currently 
> is cannot be fully answered and still requires further research.

Buffer bloat is a problem on basically all access forms apart from ETTH. 
Usually ETTH is produced using L2 or L3 switches with very small buffers 
(5 ms or so), and policing is used instead of buffering for limiting 
service rate. This means high speed TCP flows will sawtooth their 
performance over time because of large amount of consecutive drops, 
meaning low bw interactive flows are less impacted.

So it's my belief that your measurements means most people don't actually 
put congestion pressure on their accesses, thus the large buffers are 
seldom used and you're not seeing buffering.

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

From oliver@net.t-labs.tu-berlin.de  Thu Mar 21 13:47:55 2013
Return-Path: <oliver@net.t-labs.tu-berlin.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D77F021F8A54 for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 13:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[AWL=0.579,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tU-XTWIxLg5M for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 13:47:55 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:4:130:149:220:252]) by ietfa.amsl.com (Postfix) with ESMTP id 2F87721F8A04 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 13:47:55 -0700 (PDT)
Received: from net.t-labs.tu-berlin.de (ibis.net.t-labs.tu-berlin.de [IPv6:2001:470:96b9:1:14cb:af2e:2e24:2838]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 3278E4C3028;  Thu, 21 Mar 2013 21:47:54 +0100 (CET)
Date: Thu, 21 Mar 2013 21:47:53 +0100
From: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
To: tsvwg@ietf.org, bloat@lists.bufferbloat.net
Message-ID: <20130321204752.GA18256@net.t-labs.tu-berlin.de>
Mail-Followup-To: tsvwg@ietf.org, bloat@lists.bufferbloat.net
References: <51408BF4.7090304@cisco.com> <514B5AC8.8000502@net.t-labs.tu-berlin.de> <alpine.DEB.2.02.1303211254420.17535@nftneq.ynat.uz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1303211254420.17535@nftneq.ynat.uz>
X-Operating-System: Linux ibis 2.6.32-33-generic 
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [tsvwg] [Bloat]  how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 20:47:56 -0000

On Thu, Mar 21, 2013 at 01:04:21PM -0700, David Lang wrote:
> Also, if you measure the impact of bufferbloat in terms of how many
> seconds a day the line is impacted, you get a horribly skewed view of
> the impact.

I agree that such a temporal view will skew the results. The approach
taken in Mark Allman's paper is to measure the magnitude by measuring
the number of affected packets relative to the total number of packets.
This implies the amount of time a user can potentially suffer from
buffer bloat when actively using the line. It's not relative to when
the user is idle.

Oliver

From swmike@swm.pp.se  Thu Mar 21 21:27:39 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D37921F899E; Thu, 21 Mar 2013 21:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.378
X-Spam-Level: 
X-Spam-Status: No, score=-2.378 tagged_above=-999 required=5 tests=[AWL=0.221,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wk7OC8bSSeIK; Thu, 21 Mar 2013 21:27:39 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id D29B621F8733; Thu, 21 Mar 2013 21:27:31 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 28ACA9C; Fri, 22 Mar 2013 05:27:31 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 21CB19A; Fri, 22 Mar 2013 05:27:31 +0100 (CET)
Date: Fri, 22 Mar 2013 05:27:31 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Jim Gettys <jg@freedesktop.org>
In-Reply-To: <CAGhGL2DHrNUEnVF-Qn6OeeD9LvST06c0QaTxSJ+zbKdpQq2Y7g@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1303220521370.2309@uplift.swm.pp.se>
References: <51408BF4.7090304@cisco.com> <514B5AC8.8000502@net.t-labs.tu-berlin.de> <alpine.DEB.2.00.1303212019520.2309@uplift.swm.pp.se> <CAGhGL2DHrNUEnVF-Qn6OeeD9LvST06c0QaTxSJ+zbKdpQq2Y7g@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: aqm@ietf.org, "tsvwg@ietf.org" <tsvwg@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [tsvwg] [Bloat]  how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2013 04:27:39 -0000

On Thu, 21 Mar 2013, Jim Gettys wrote:

> Every more modern TCP can easily fill any sized buffer given time with a 
> single TCP connection.

I agree with this, I made this discovery myself back in 2004 or so, and 
had to implement Fairqueue and WRED on my home connection to make it 
bearable to use any interactive application while transferring files.

In IETF75 in Stockholm in 2009, I made proposals in both TCP and at open 
mic in one of the sessions, that I would like to see statistics and 
performance numbers on packet loss, delay variation etc from actual 
traffic. The IP stack has great insight in what the network conditions are 
(especially with TCP Timestamping), but as far as I know it's not really 
exported in any usable format to the user. My idea was to have some kind 
of dashboard for the user to show if currently the network was the 
limiting factor, if the tcp window was maxed out etc. Would also be nice 
if there was output that could be cut/pasted and attached to a fault 
report in case the customer talks to customer support. It would be good if 
this was actually a standard so all OSes did the same.

I am not aware of any such work going on, so I'd like to know if anyone 
else is aware of work in this area?

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

From david.black@emc.com  Fri Mar 22 00:07:22 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD8211E80A6 for <tsvwg@ietfa.amsl.com>; Fri, 22 Mar 2013 00:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OwzLTyK2eVGd for <tsvwg@ietfa.amsl.com>; Fri, 22 Mar 2013 00:07:22 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D5E9D21F844C for <tsvwg@ietf.org>; Fri, 22 Mar 2013 00:07:21 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2M77KoH017243 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Mar 2013 03:07:20 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 22 Mar 2013 03:07:03 -0400
Received: from mxhub35.corp.emc.com (mxhub35.corp.emc.com [10.254.93.83]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2M7721x030555; Fri, 22 Mar 2013 03:07:02 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub35.corp.emc.com ([::1]) with mapi; Fri, 22 Mar 2013 03:07:02 -0400
From: "Black, David" <david.black@emc.com>
To: Joe Touch <touch@isi.edu>
Date: Fri, 22 Mar 2013 03:07:00 -0400
Thread-Topic: [tsvwg] RFC 4594 update: Routing class
Thread-Index: Ac4mYT81fmUT1HZUTme83LI9mCigpAAakz3A
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293AEE844@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <514B4F2A.3030902@isi.edu>
In-Reply-To: <514B4F2A.3030902@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2013 07:07:22 -0000

Joe,

This is already a solved problem.  This traffic class is called "Network Co=
ntrol"
in RFC 4594 (which recommends CS6 for that class of traffic).  The use of "=
Routing"
as a class name here name is effectively shorthand for that "Network Contro=
l" class.

Thanks,
--David

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of=
 Joe
> Touch
> Sent: Thursday, March 21, 2013 2:19 PM
> To: Fred Baker (fred)
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] RFC 4594 update: Routing class
>=20
> Again, I don't like classes named for applications - or protocols, or
> groups of protocols. This ought to be something you can describe in
> terms of the service provided, not how the service is used.
>=20
> Joe
>=20
> On 3/19/2013 1:53 PM, Fred Baker (fred) wrote:
> > I was unable to attend twvwg at IETF 86 as it competed with a meeting I
> presented in. I am told that there was a presentation in which folks argu=
ed
> against having a class of traffic for routing traffic. I'd like to commen=
t on
> that.
> >
> > The origin of a class of traffic for routing traffic was a bug. The Cis=
co
> 7000 had an issue with its offloaded forwarding cards, of which it had tw=
o.
> When there was a route flap, it blew away the route cache and then rebuil=
t it
> in response to traffic it needed to forward. In that implementation, that
> meant that the Route Processor (the CPU) suddenly had all traffic from al=
l
> sources flooded into it. The impact of that was to make it very difficult=
 for
> the RP to actually re-populate the Route Cache. Doubleplus ungood. The wo=
rk-
> around was to rate-limit traffic from the line cards to the RP. However, =
rate
> limiting the routing traffic worked against getting routing to stabilize,=
 so
> we marked routing traffic, and did not rate limit *it* from going to the =
RP.
> >
> > Fast forward nearly 20 years. We don't have that bug anymore, if anythi=
ng
> because nobody equipped with a right mind uses the Cisco 7000 any more.
> >
> > However...
> >
> > If we're going to discuss quality of service for any application, we ar=
e
> making some fundamental assumptions. These include the concept of having
> enough bandwidth and so on; we're managing traffic at points in time when=
 peak
> traffic loads on a millisecond scale create issues. One of those fundamen=
tal
> issues is that routing must be current; if we're sending traffic on a rou=
te
> that loops because the other guy updated his route table but we didn't, o=
r
> vice versa, or for which interface or next hop router is no longer there,=
 we
> can discuss jitter, rate, and loss to our heart's content - the applicati=
on's
> traffic isn't going to get there. At. All. And won't until routing stabil=
izes.
> >
> > The fundamental argument for a class of traffic for routing in 2013 is =
not
> that routing requires certain jitter, rate, or etc characteristics; it is=
 that
> routing traffic (apart from AQM issues, see separate discussion on
> aqm@ietf.org) should simply *not*be*dropped* in the normal course of busi=
ness.
> Routing is fundamental to all other services the network delivers, includ=
ing
> QoS, and including every networks's SLAs.
> >
> > Now, one can say that routing is between neighboring nodes, and a route=
r is
> able to do special things with traffic it itself originates. It is true t=
hat a
> router can do special things with its own traffic, and they do. But BGP
> Routing frequently goes from Route Arbiter to Route Arbiter instead of Ro=
uter
> to Router, which is to say through other routers between routing engines.
> Traffic through other routers is traffic through other routers, not a rou=
ter's
> own traffic. It requires some form of end to end marking to protect it.
> Something like a DSCP.
> >


From gettysjim@gmail.com  Thu Mar 21 10:20:22 2013
Return-Path: <gettysjim@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4350121F9180; Thu, 21 Mar 2013 10:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.54
X-Spam-Level: 
X-Spam-Status: No, score=-1.54 tagged_above=-999 required=5 tests=[AWL=1.209,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DI-mCHL8UQsc; Thu, 21 Mar 2013 10:20:21 -0700 (PDT)
Received: from mail-oa0-f50.google.com (mail-oa0-f50.google.com [209.85.219.50]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD2E21F90DD; Thu, 21 Mar 2013 10:20:21 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id n1so562957oag.9 for <multiple recipients>; Thu, 21 Mar 2013 10:20:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UwJEIfs/TZlZs6Qfiok8UOccboC4kGhAyF0WB+kR4iE=; b=FbQ+ssP/RZW6jbLphQcJ16uVB3NuP62JyXGbLzsQkC7DIZCAMlmxk0/6BVaqWmqVQV yKV6SksQX0jVV65wtlRFqi5VC9Rt9tiY1NIIBbKMoTv27CTvotNGXnl2wI/XJixVn1oO FUXduYPw75jCUGBSLjlWLgcu5U59zkcIId+aI/vtNt+B7MBm1faWq/TjDgrqtlSM7dy+ zgd9/5JzHwh99XdXwrjxd7vMhv3/ugD8wXSxRc2t9QhUzv8HK0wl/kchA7/v5ttEOIJL j4NJXvV4v5H6BaHWiixzrvKD533YA62JhUPkE/dLiRM6myYlVK/mZW6vMpcq6lesBDmu 3Mhg==
MIME-Version: 1.0
X-Received: by 10.60.10.138 with SMTP id i10mr7495696oeb.95.1363886420730; Thu, 21 Mar 2013 10:20:20 -0700 (PDT)
Sender: gettysjim@gmail.com
Received: by 10.76.22.193 with HTTP; Thu, 21 Mar 2013 10:20:20 -0700 (PDT)
In-Reply-To: <C38E406F654CD249AB7D30B93B0207F517F5E4AE@EXCHANGE.cablelabs.com>
References: <514B2FE9.90101@apolix.co.za> <C38E406F654CD249AB7D30B93B0207F517F5E4AE@EXCHANGE.cablelabs.com>
Date: Thu, 21 Mar 2013 13:20:20 -0400
X-Google-Sender-Auth: fGLBIzDMN2uNCb2X_0wOjtY3WLU
Message-ID: <CAGhGL2Bzpmrq6wQ2iodtYjd-_S3zMBKaf0qGRo=eYs-Bj+Vfag@mail.gmail.com>
From: Jim Gettys <jg@freedesktop.org>
To: Greg White <g.white@cablelabs.com>
Content-Type: multipart/alternative; boundary=e89a8f5036fc9f2b7004d8728d59
X-Mailman-Approved-At: Fri, 22 Mar 2013 02:23:43 -0700
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [tsvwg] [aqm]  how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 17:20:22 -0000
X-List-Received-Date: Thu, 21 Mar 2013 17:20:22 -0000

--e89a8f5036fc9f2b7004d8728d59
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Mar 21, 2013 at 12:59 PM, Greg White <g.white@cablelabs.com> wrote:

> ....cross posting to aqm.
>
> On 3/21/13 10:06 AM, "Graham Beneke" <graham@apolix.co.za> wrote:
>
> >On 13/03/2013 19:32, Mikael Abrahamsson wrote:
> >> On Wed, 13 Mar 2013, Greg White wrote:
> >>
> >>> Some may consider 100ms a big number.
> >
> >I've heard the 100ms figure thrown about quite a bit. In the VoIP world
> >its considered to be the pain threshold for a reasonable call experience
> >and for "general Internet" (aka http browsing) it doesn't normally
> >impact the user experience notably.
>
> Web browsing *is* sensitive to RTT (though maybe less so than VoIP or
> gaming).  Page load time increases linearly with RTT (at approximately
> 10x-20x).  So adding 100ms of *unnecessary* buffering latency adds ~1-2
> seconds of *unnecessary* delay to page loads.
>

This is one very visible result; but far from the most important, as we
work on trying to make applications like WebRTC viable.

One way I think about latency is that it sets the "diameter" in which
particular applications are viable, as well as causing performance problems
in general.  These are set by human factors and the speed of our neurology.

Variance of latency is just about as bad as the latency itself; you have to
add that to jitter buffers and it increases the latency the system can be
used at.

And you have to think of latency in terms of a budget: it takes of order
75ms to get across the United States by a good unloaded Internet connection
(the same as it did in the 1990's; Einstein + the index of refraction of
glass  makes this hard to change).  So you really have much, much, less
than 100ms you can afford to burn in the edge of the network even by this
metric.

For example, human perception to make interactive "rubber
banding" imperceptible is in the 20-30ms range.  As the latency budget
includes screen refresh time, this one is doable, but you have to work
hard, as we did with the X Window System in the 1980's.  I find it
personally very sad that while X11 used to be usable between continents,
it's not typically usable today (though mistakes we made in the X11
protocol made this worse than it should have been).

If you want to play music with a friend, professional musicians might
tolerate up to 100ms total; but duffers can't tolerate even half of that
latency well.  So if you want to play music in Boston with a friend in NYC,
you've lost 20ms before you spend time in any queuing.

Gamers (and day traders) care about latency down to the single millisecond
range as it changes the *probability* of bad outcomes.

So unpredictable 100ms latency not only hurt web performance in easily
measurable ways as Greg and I have shown, but, more insidiously,  kill a
large set of applications, or reduces the geographic network "diameter"
over which they are practical.

Courtesy of the speed of light, therefore, any unnecessary latency *and*
jitter hurts what the Internet can be used for.
                                                  - Jim

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Ma=
r 21, 2013 at 12:59 PM, Greg White <span dir=3D"ltr">&lt;<a href=3D"mailto:=
g.white@cablelabs.com" target=3D"_blank">g.white@cablelabs.com</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">....cross posting to aqm.<br>
<br>
On 3/21/13 10:06 AM, &quot;Graham Beneke&quot; &lt;<a href=3D"mailto:graham=
@apolix.co.za">graham@apolix.co.za</a>&gt; wrote:<br>
<br>
&gt;On 13/03/2013 19:32, Mikael Abrahamsson wrote:<br>
&gt;&gt; On Wed, 13 Mar 2013, Greg White wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; Some may consider 100ms a big number.<br>
&gt;<br>
&gt;I&#39;ve heard the 100ms figure thrown about quite a bit. In the VoIP w=
orld<br>
&gt;its considered to be the pain threshold for a reasonable call experienc=
e<br>
&gt;and for &quot;general Internet&quot; (aka http browsing) it doesn&#39;t=
 normally<br>
&gt;impact the user experience notably.<br>
<br>
Web browsing *is* sensitive to RTT (though maybe less so than VoIP or<br>
gaming). =A0Page load time increases linearly with RTT (at approximately<br=
>
10x-20x). =A0So adding 100ms of *unnecessary* buffering latency adds ~1-2<b=
r>
seconds of *unnecessary* delay to page loads.<br></blockquote><div><br></di=
v><div style=3D"font-size:small" class=3D"gmail_default">This is one very v=
isible result; but far from the most important, as we work on trying to mak=
e applications like WebRTC viable.</div>
<div><br></div><div class=3D"gmail_default">One way I think about latency i=
s that it sets the &quot;diameter&quot; in which particular applications ar=
e viable, as well as causing performance problems in general. =A0These are =
set by human factors and the speed of our neurology.</div>
<div class=3D"gmail_default"><br></div><div class=3D"gmail_default"><div cl=
ass=3D"gmail_default">Variance of latency is just about as bad as the laten=
cy itself; you have to add that to jitter buffers and it increases the late=
ncy the system can be used at.</div>
<div><br></div></div><div class=3D"gmail_default" style>And you have to thi=
nk of latency in terms of a budget: it takes of order 75ms to get across th=
e United States by a good unloaded Internet connection (the same as it did =
in the 1990&#39;s; Einstein + the index of refraction of glass =A0makes thi=
s hard to change). =A0So you really have much, much, less than 100ms you ca=
n afford to burn in the edge of the network even by this metric.</div>
<div class=3D"gmail_default"><br></div><div class=3D"gmail_default" style>F=
or example, human perception to make interactive &quot;rubber banding&quot;=
=A0imperceptible is in the 20-30ms range. =A0As the latency budget includes=
 screen refresh time, this one is doable, but you have to work hard, as we =
did with the X Window System in the 1980&#39;s. =A0I find it personally ver=
y sad that while X11 used to be usable between continents, it&#39;s not typ=
ically usable today (though mistakes we made in the X11 protocol made this =
worse than it should have been).</div>
<div class=3D"gmail_default" style><br></div><div class=3D"gmail_default" s=
tyle>If you want to play music with a friend, professional musicians might =
tolerate up to 100ms total; but duffers can&#39;t tolerate even half of tha=
t latency well. =A0So if you want to play music in Boston with a friend in =
NYC, you&#39;ve lost 20ms before you spend time in any queuing.</div>
<div class=3D"gmail_default" style><br></div><div class=3D"gmail_default" s=
tyle>Gamers (and day traders) care about latency down to the single millise=
cond range as it changes the *probability* of bad outcomes.</div><div class=
=3D"gmail_default" style>
<br></div><div class=3D"gmail_default" style>So unpredictable 100ms latency=
 not only hurt web performance in easily measurable ways as Greg and I have=
 shown, but, more=A0insidiously,=A0 kill a large set of applications, or re=
duces the geographic network &quot;diameter&quot; over which they are pract=
ical.</div>
<div class=3D"gmail_default" style><br></div><div class=3D"gmail_default" s=
tyle>Courtesy of the speed of light, therefore, any unnecessary latency *an=
d* jitter hurts what the Internet can be used for.</div><div class=3D"gmail=
_default" style>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 - Jim</div><div class=3D"gmail_default" style><br>=
</div><div class=3D"gmail_default" style><br></div><div style=3D"font-size:=
small" class=3D"gmail_default"><br></div></div></div></div>

--e89a8f5036fc9f2b7004d8728d59--

From gettysjim@gmail.com  Thu Mar 21 11:01:43 2013
Return-Path: <gettysjim@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 382A321F90CA for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:01:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.253
X-Spam-Level: 
X-Spam-Status: No, score=-0.253 tagged_above=-999 required=5 tests=[AWL=1.724,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YswqMS50QxHz for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:01:42 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 07C1421F90A1 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 11:01:37 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id tb18so3187953obb.31 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 11:01:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=KKrbD/yeGlRbVgDATGzD6sYgtZDq6Ng1ieElEubglno=; b=gjlmaztO7gUewlZE1YiflpdKpNd6ypeXmzOIYoW0rJ42HtmMt6za9H1V5vrbE/FIRm at87pQyW3XnRD7eaHhPI26ETVoZcTT9xSFH+O2fHF4BN89T8UKj89VGU9JK9s+X7YDHA nYV7l1xN19QAjB5vXM//qd666XHtRleypUL4qBwjE273dcj/5zQ1WlWEJT+OwYo+xOjG +14LpL9/3CmyKVZDOAnNZtOmxAFBf7dpMM7MAOOjGbzzw2lscSm/v6dvHJsvUXSmNb4m jZU7p6bYJcM5hq0+v6ei14oj9d/3fB48yoVP4KsrtITomj9eTrIPAxMh6dYAVPCa3PuY gEzg==
MIME-Version: 1.0
X-Received: by 10.182.192.3 with SMTP id hc3mr7323049obc.41.1363888897515; Thu, 21 Mar 2013 11:01:37 -0700 (PDT)
Sender: gettysjim@gmail.com
Received: by 10.76.22.193 with HTTP; Thu, 21 Mar 2013 11:01:37 -0700 (PDT)
In-Reply-To: <514B484F.2070902@net.t-labs.tu-berlin.de>
References: <51408BF4.7090304@cisco.com> <8C48B86A895913448548E6D15DA7553B7D020F@xmb-rcd-x09.cisco.com> <514B484F.2070902@net.t-labs.tu-berlin.de>
Date: Thu, 21 Mar 2013 14:01:37 -0400
X-Google-Sender-Auth: 6dykhrSvdCTxRRww4B-_11wcCR4
Message-ID: <CAGhGL2Cu6m-s_6SyZPMGm0ebXjn4_wbftNcY519v11Lk3CvaJg@mail.gmail.com>
From: Jim Gettys <jg@freedesktop.org>
To: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
Content-Type: multipart/alternative; boundary=f46d041fa0c53fe5a304d87321ea
X-Mailman-Approved-At: Fri, 22 Mar 2013 02:23:43 -0700
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [tsvwg] [Bloat]  how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 18:01:43 -0000

--f46d041fa0c53fe5a304d87321ea
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Mar 21, 2013 at 1:50 PM, Oliver Hohlfeld <
oliver@net.t-labs.tu-berlin.de> wrote:

> (cross posting to bloat)
>
> On 03/13/2013 04:28 PM, Fred Baker (fred) wrote:
> > On Mar 13, 2013, at 10:23 AM, Eliot Lear <lear@cisco.com> wrote:
> >
> >> I don't have an answer to that question, but Mark Allman from ICIR did
> >> attempt to characterize buffer bloat on the Internet through an
> >> empirical study that appeared in the January edition of CCR.  You can
> >> find a reference to that paper at the following URL:
> >>
> >> http://www.sigcomm.org/ccr/papers/2013/January/2427036.2427041
> >>
> >> Eliot
> >
> > Well, yes, he says that in his gigabit FTTH network he doesn't see
> megabit-scale problems.
>
> Marks paper is /not/ about measuring buffer bloat in an FTTH network.
> While he uses the FTTH network as /vantage point/, the paper actually
> measures buffer bloat in various remote networks.
>
> Marks paper is not the only study suggesting the extend of the problem
> to be modest. The presented results are in line with recent findings by
> Chirichella and Rossi [1]. Based on unpublished work, I can confirm the
> low magnitude of the problem. I analyzed passive measurements of
> residential users traffic from multiple continents (~60 million IPs
> originating from 50\% of all ASes) and rarely find excessive RTTs that,
> among other problems, can indicate the presence of buffer bloat.
>

I believe you are actually measuring the *fraction of the time* your
measurements show bad latency, rather than the fraction of paths that may
suffer from significant bufferbloat at various times due to excessive
buffering.

Buffers only fill when they are being used and that only happens when
saturation occurs.

The best data I've seen on how widespread the problem is is the ICSI
Netalyzr scatter plots results, which (in color) are in my blog.
http://gettys.wordpress.com/2010/12/06/whose-house-is-of-glasse-must-not-throw-stones-at-another/
These must be flavored by understanding that those tests top out at about
20Mbps, and that (to keep the time that netalzyr takes to run sane) stops
at about 5 seconds of buffering.

I encourage everyone to run netalyzr and/or the mlabs tests for bufferbloat
on your own broadband connections, or do simple copy and ping tests inside
your own house over wifi to your local file servers....
                                                               - Jim


> In summary, bloated buffers exist and buffer bloat can be demonstrated,
> but current findings suggest that it rarely occurs in practice. One
> potential reason being that users do not often sustainably utilize
> their uplink capacity and fill-up their potentially large queues.
>
> Oliver
>
> [1] To the Moon and back: are Internet bufferbloat delays really that
> large?
> http://perso.telecom-paristech.fr/~drossi/paper/rossi13tma-a.pdf
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><di=
v class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D=
"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, Mar 21, 2013 at 1:50 PM, Oliver =
Hohlfeld <span dir=3D"ltr">&lt;<a href=3D"mailto:oliver@net.t-labs.tu-berli=
n.de" target=3D"_blank">oliver@net.t-labs.tu-berlin.de</a>&gt;</span> wrote=
:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">(cross posting to bloat)<br>
<br>
On 03/13/2013 04:28 PM, Fred Baker (fred) wrote:<br>
&gt; On Mar 13, 2013, at 10:23 AM, Eliot Lear &lt;<a href=3D"mailto:lear@ci=
sco.com">lear@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; I don&#39;t have an answer to that question, but Mark Allman from =
ICIR did<br>
&gt;&gt; attempt to characterize buffer bloat on the Internet through an<br=
>
&gt;&gt; empirical study that appeared in the January edition of CCR. =A0Yo=
u can<br>
&gt;&gt; find a reference to that paper at the following URL:<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"http://www.sigcomm.org/ccr/papers/2013/January/2427036.=
2427041" target=3D"_blank">http://www.sigcomm.org/ccr/papers/2013/January/2=
427036.2427041</a><br>
&gt;&gt;<br>
&gt;&gt; Eliot<br>
&gt;<br>
&gt; Well, yes, he says that in his gigabit FTTH network he doesn&#39;t see=
 megabit-scale problems.<br>
<br>
Marks paper is /not/ about measuring buffer bloat in an FTTH network.<br>
While he uses the FTTH network as /vantage point/, the paper actually<br>
measures buffer bloat in various remote networks.<br>
<br>
Marks paper is not the only study suggesting the extend of the problem<br>
to be modest. The presented results are in line with recent findings by<br>
Chirichella and Rossi [1]. Based on unpublished work, I can confirm the<br>
low magnitude of the problem. I analyzed passive measurements of<br>
residential users traffic from multiple continents (~60 million IPs<br>
originating from 50\% of all ASes) and rarely find excessive RTTs that,<br>
among other problems, can indicate the presence of buffer bloat.<br></block=
quote><div><br></div><div class=3D"gmail_default">I believe you are actuall=
y measuring the *fraction of the time* your measurements show bad latency, =
rather than the fraction of paths that may suffer from significant bufferbl=
oat at various times due to excessive buffering.=A0</div>
<div class=3D"gmail_default"><br></div><div class=3D"gmail_default">Buffers=
 only fill when they are being used and that only happens when saturation o=
ccurs.</div><div class=3D"gmail_default"><br></div><div class=3D"gmail_defa=
ult">
The best data I&#39;ve seen on how widespread the problem is is the ICSI Ne=
talyzr scatter plots results, which (in color) are in my blog. =A0<a href=
=3D"http://gettys.wordpress.com/2010/12/06/whose-house-is-of-glasse-must-no=
t-throw-stones-at-another/">http://gettys.wordpress.com/2010/12/06/whose-ho=
use-is-of-glasse-must-not-throw-stones-at-another/</a>=A0 These must be fla=
vored by understanding that those tests top out at about 20Mbps, and that (=
to keep the time that netalzyr takes to run sane) stops at about 5 seconds =
of buffering.</div>
<div class=3D"gmail_default"><br></div><div class=3D"gmail_default" style>I=
 encourage everyone to run netalyzr and/or the mlabs tests for bufferbloat =
on your own broadband connections, or do simple copy and ping tests inside =
your own house over wifi to your local file servers....</div>
<div class=3D"gmail_default" style>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0- Jim</div><div class=3D"gmail_default" style><br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-wi=
dth:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-=
left:1ex">

<br>
In summary, bloated buffers exist and buffer bloat can be demonstrated,<br>
but current findings suggest that it rarely occurs in practice. One<br>
potential reason being that users do not often sustainably utilize<br>
their uplink capacity and fill-up their potentially large queues.<br>
<br>
Oliver<br>
<br>
[1] To the Moon and back: are Internet bufferbloat delays really that large=
?<br>
<a href=3D"http://perso.telecom-paristech.fr/~drossi/paper/rossi13tma-a.pdf=
" target=3D"_blank">http://perso.telecom-paristech.fr/~drossi/paper/rossi13=
tma-a.pdf</a><br>
_______________________________________________<br>
Bloat mailing list<br>
<a href=3D"mailto:Bloat@lists.bufferbloat.net">Bloat@lists.bufferbloat.net<=
/a><br>
<a href=3D"https://lists.bufferbloat.net/listinfo/bloat" target=3D"_blank">=
https://lists.bufferbloat.net/listinfo/bloat</a><br>
</blockquote></div><br></div></div>

--f46d041fa0c53fe5a304d87321ea--

From gettysjim@gmail.com  Thu Mar 21 13:05:59 2013
Return-Path: <gettysjim@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F32EE21F8CCF for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 13:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.235
X-Spam-Level: 
X-Spam-Status: No, score=0.235 tagged_above=-999 required=5 tests=[AWL=0.546,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dAaMen51MllD for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 13:05:58 -0700 (PDT)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 5555221F8CCB for <tsvwg@ietf.org>; Thu, 21 Mar 2013 13:05:58 -0700 (PDT)
Received: by mail-ob0-f177.google.com with SMTP id eh20so3241210obb.22 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 13:05:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=jGmoyfkI3MbOGods205iQk3YI8u/jEZsd+uYAK0PuF8=; b=wXCwxFVslxSTjy1Y0lhw1n3TiJZbVGqSL5CxG5DK46aLqdEZeQZ+cgMsWVJFyRiMIf LBSg+2XoNkIS2RpBLApAqmhXvheX5lXx2sJAU3Wad9KXTpvYWrOrXzd7kuOKIVpJNp6s eJSGeKVG/gj47ff8C/H2j91OEtpFfLgoq+xFJujPn1U7gr4pqRng1+7Vul0o1owhBdwA Mdd7zD3E9x5zCbh+xnKC8bmzbmBB0JDKhP7dfJ7UAN1O+R9h8HhVFrHCJGP5ZyF2kn0Z ek9YekGZvNV7z1Rzzs4dMW8kNf9PAxbwqTCX5lSwi4rRA4X381TMy3hzrAs0eeud1HD9 vG3Q==
MIME-Version: 1.0
X-Received: by 10.60.8.197 with SMTP id t5mr8042836oea.4.1363896357820; Thu, 21 Mar 2013 13:05:57 -0700 (PDT)
Sender: gettysjim@gmail.com
Received: by 10.76.22.193 with HTTP; Thu, 21 Mar 2013 13:05:57 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.00.1303212019520.2309@uplift.swm.pp.se>
References: <51408BF4.7090304@cisco.com> <514B5AC8.8000502@net.t-labs.tu-berlin.de> <alpine.DEB.2.00.1303212019520.2309@uplift.swm.pp.se>
Date: Thu, 21 Mar 2013 16:05:57 -0400
X-Google-Sender-Auth: 0GxwoNfDeDAObHFLinCVUe_nOVk
Message-ID: <CAGhGL2DHrNUEnVF-Qn6OeeD9LvST06c0QaTxSJ+zbKdpQq2Y7g@mail.gmail.com>
From: Jim Gettys <jg@freedesktop.org>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary=e89a8fb1ef42eb2bc604d874ddf7
X-Mailman-Approved-At: Fri, 22 Mar 2013 02:23:43 -0700
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [tsvwg] [Bloat]  how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 20:05:59 -0000

--e89a8fb1ef42eb2bc604d874ddf7
Content-Type: text/plain; charset=ISO-8859-1

Also, Windows XP is still significantly in use in the Internet
(unfortunately).



On Thu, Mar 21, 2013 at 3:25 PM, Mikael Abrahamsson <swmike@swm.pp.se>wrote:

> On Thu, 21 Mar 2013, Oliver Hohlfeld wrote:
>
>  In summary, the question on how much of a problem buffer bloat currently
>> is cannot be fully answered and still requires further research.
>>
>
> Buffer bloat is a problem on basically all access forms apart from ETTH.
> Usually ETTH is produced using L2 or L3 switches with very small buffers (5
> ms or so), and policing is used instead of buffering for limiting service
> rate. This means high speed TCP flows will sawtooth their performance over
> time because of large amount of consecutive drops, meaning low bw
> interactive flows are less impacted.
>
> So it's my belief that your measurements means most people don't actually
> put congestion pressure on their accesses, thus the large buffers are
> seldom used and you're not seeing buffering.



Due to the fact TCP window scaling is off by default in Windows XP, the
most a single TCP connection will have in flight on Windows XP is 64K bytes.

This both limits the ability of a Windows XP system to saturate a link in
the first place (thereby sometimes avoiding filling buffers at the
bottleneck at all), and limits the amount of latency a single TCP
connection will inflict.

Every more modern TCP can easily fill any sized buffer given time with a
single TCP connection.
                                   - Jim

>
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
> ______________________________**_________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/**listinfo/bloat<https://lists.bufferbloat.net/listinfo/bloat>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">Als=
o, Windows XP is still significantly in use in the Internet (unfortunately)=
.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><di=
v class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, Mar 21, 2013 at 3:25 PM, Mikael =
Abrahamsson <span dir=3D"ltr">&lt;<a href=3D"mailto:swmike@swm.pp.se" targe=
t=3D"_blank">swmike@swm.pp.se</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;borde=
r-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=3D"im">On Thu, 21 Mar 2013, Oliver Hohlfeld wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
In summary, the question on how much of a problem buffer bloat currently is=
 cannot be fully answered and still requires further research.<br>
</blockquote>
<br></div>
Buffer bloat is a problem on basically all access forms apart from ETTH. Us=
ually ETTH is produced using L2 or L3 switches with very small buffers (5 m=
s or so), and policing is used instead of buffering for limiting service ra=
te. This means high speed TCP flows will sawtooth their performance over ti=
me because of large amount of consecutive drops, meaning low bw interactive=
 flows are less impacted.<br>

<br>
So it&#39;s my belief that your measurements means most people don&#39;t ac=
tually put congestion pressure on their accesses, thus the large buffers ar=
e seldom used and you&#39;re not seeing buffering.</blockquote><div><br>
</div><div class=3D"gmail_default"><br class=3D"">Due to the fact TCP windo=
w scaling is off by default in Windows XP, the most a single TCP connection=
 will have in flight on Windows XP is 64K bytes.</div><div class=3D"gmail_d=
efault">
<br></div><div class=3D"gmail_default">This both limits the ability of a Wi=
ndows XP system to saturate a link in the first place (thereby sometimes av=
oiding filling buffers at the bottleneck at all), and limits the amount of =
latency a single TCP connection will inflict.</div>
<div class=3D"gmail_default"><br></div><div class=3D"gmail_default">Every m=
ore modern TCP can easily fill any sized buffer given time with a single TC=
P connection.</div><div style=3D"font-size:small" class=3D"gmail_default">=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0- Ji=
m</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><span class=3D""><font color=3D"#888888"><br>
<br>
-- <br>
Mikael Abrahamsson =A0 =A0email: <a href=3D"mailto:swmike@swm.pp.se" target=
=3D"_blank">swmike@swm.pp.se</a></font></span><div class=3D""><div class=3D=
"h5"><br>
______________________________<u></u>_________________<br>
Bloat mailing list<br>
<a href=3D"mailto:Bloat@lists.bufferbloat.net" target=3D"_blank">Bloat@list=
s.bufferbloat.net</a><br>
<a href=3D"https://lists.bufferbloat.net/listinfo/bloat" target=3D"_blank">=
https://lists.bufferbloat.net/<u></u>listinfo/bloat</a><br>
</div></div></blockquote></div><br></div></div>

--e89a8fb1ef42eb2bc604d874ddf7--

From gettysjim@gmail.com  Thu Mar 21 11:28:21 2013
Return-Path: <gettysjim@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD0AF21F89D8 for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.826
X-Spam-Level: 
X-Spam-Status: No, score=-1.826 tagged_above=-999 required=5 tests=[AWL=1.150,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id STkOQI7Q+xmn for <tsvwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:28:20 -0700 (PDT)
Received: from mail-oa0-f51.google.com (mail-oa0-f51.google.com [209.85.219.51]) by ietfa.amsl.com (Postfix) with ESMTP id 714B221F874B for <tsvwg@ietf.org>; Thu, 21 Mar 2013 11:28:20 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id g12so109998oah.38 for <tsvwg@ietf.org>; Thu, 21 Mar 2013 11:28:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=y+AY1Z4ZyLUWLDyQHRYTCQJWyyYCue2ocLsQnuySEOI=; b=mZLrGZpElScNbgzCYIjxxgQVCbcSxJZbOUBTf0q1boozrage1UKw3HE4ZXDqZBYTSs 77tLSzPLg7Xdjc2caqqwlxX4ypRpv4CeCwORKLdev7FyuBQrE5W3eKsC1BLM+9bDsshZ NcjrC2WPOjGMPlftp9lWaIiC3puzY2C7/9Kz2Ll6mHbF0LfSC2sQ3ElmoL9+0IU0MEpt ouPxWKTaakCPr1WDHNWgxAIZDrAqdKSf5GmW7JT1lcYWFi45qCEL4fF1OcEOBmLA7Qjd wOPq31+OK+sq4Ln674gGY85MPtWerxnif4emrEOipK6G/v9+ZAtjyx/Y9g9/3Hsi8Du8 8nKA==
MIME-Version: 1.0
X-Received: by 10.182.2.132 with SMTP id 4mr7637045obu.42.1363890499974; Thu, 21 Mar 2013 11:28:19 -0700 (PDT)
Sender: gettysjim@gmail.com
Received: by 10.76.22.193 with HTTP; Thu, 21 Mar 2013 11:28:19 -0700 (PDT)
In-Reply-To: <514B4DEB.3020402@net.t-labs.tu-berlin.de>
References: <51408BF4.7090304@cisco.com> <8C48B86A895913448548E6D15DA7553B7D020F@xmb-rcd-x09.cisco.com> <514B484F.2070902@net.t-labs.tu-berlin.de> <CAGhGL2Cu6m-s_6SyZPMGm0ebXjn4_wbftNcY519v11Lk3CvaJg@mail.gmail.com> <514B4DEB.3020402@net.t-labs.tu-berlin.de>
Date: Thu, 21 Mar 2013 14:28:19 -0400
X-Google-Sender-Auth: kBAY8P1-QQyFhHUyOH2xcUgs7eM
Message-ID: <CAGhGL2DWvC-2auKQdOMAP9KqnPGKsN+Uxu7kpVDB=J+3HMr-vg@mail.gmail.com>
From: Jim Gettys <jg@freedesktop.org>
To: Oliver Hohlfeld <oliver@net.t-labs.tu-berlin.de>
Content-Type: multipart/alternative; boundary=f46d044519d9c37e3d04d87380f7
X-Mailman-Approved-At: Fri, 22 Mar 2013 02:23:43 -0700
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [tsvwg] [Bloat]  how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 18:28:21 -0000

--f46d044519d9c37e3d04d87380f7
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Mar 21, 2013 at 2:14 PM, Oliver Hohlfeld <
oliver@net.t-labs.tu-berlin.de> wrote:

> > I believe you are actually measuring the *fraction of the time* your
> > measurements show bad latency
>
> Yes.
>
> > The best data I've seen on how widespread the problem is is the ICSI
> > Netalyzr scatter plots results
>
> One has to be extremely careful on what to conclude from this data.
> The Netalyzr data shows that bloated buffers _exist_, not that they
> are _used_ in practice. Or as Mark has put it: "[it] shows that large
> delays due to buffering can happen, not that they do happen."
> Empirical evidence cited in my previous mail suggests that buffer
> bloat does not happen often.
>

Heh.

6% of the time isn't "often"?  The measurements is much more a measurement
of how much of the time your competing with someone else (or yourself in
background) for the bottleneck than anything else.

Start up any long lived TCP connection (using a modern TCP; that leaves out
Windows XP).

Stand back a few seconds.

Measure latency.

Think uploading/downloading files/videos, or sending email with images
attached, etc.


More insidious is what visiting a web page with lots of embedded images can
do.

The cross product of:
   1) current web browsers using many more than 2 TCP connections.
   2) web site "sharding".
   3) the initial window of data in those TCP connections.

This causes transients of what is up to hundreds of milliseconds of head of
line blocking even
on very high speed broadband/wifi connections.  Again, I encourage you to
do this measurement on your own broadband connection, by visiting any image
heavy web site and running ping....



>
> > I encourage everyone to run netalyzr and/or the mlabs tests for
> > bufferbloat on your own broadband connections, or do simple copy and
> > ping tests inside your own house over wifi to your local file servers....
>
> While this will identify bloated buffers, it does not help in answering
> what fraction of Internet users actually experience the problem.
>

We've not come across any broadband equipment buffered "correctly".  If
thought is given at all to buffering, it's been sized to the maximum
buffering the device might ever need for a single TCP flow at its maximum
bandwidth.  Example, plug a current DOCSIS 3 modem (capable up to 300Mbps
these days) and use it at 20Mbps; unless the buffersizing amendment has
been turned on (no ISP I am aware of yet does so), you'll be overbuffered
by a factor of 15.

And all the operating systems have problems, to one degree or another (and
as they are all adjacent to wireless links these days, they also contribute
to the problem.

Bufferbloat just waits in hiding to get you when you try to use the network.
                                        - Jim


> Oliver

_______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu=
, Mar 21, 2013 at 2:14 PM, Oliver Hohlfeld <span dir=3D"ltr">&lt;<a href=3D=
"mailto:oliver@net.t-labs.tu-berlin.de" target=3D"_blank">oliver@net.t-labs=
.tu-berlin.de</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt; I believe you are act=
ually measuring the *fraction of the time* your<br>
&gt; measurements show bad latency<br>
<br>
</div>Yes.<br>
<div class=3D"im"><br>
&gt; The best data I&#39;ve seen on how widespread the problem is is the IC=
SI<br>
&gt; Netalyzr scatter plots results<br>
<br>
</div>One has to be extremely careful on what to conclude from this data.<b=
r>
The Netalyzr data shows that bloated buffers _exist_, not that they<br>
are _used_ in practice. Or as Mark has put it: &quot;[it] shows that large<=
br>
delays due to buffering can happen, not that they do happen.&quot;<br>
Empirical evidence cited in my previous mail suggests that buffer<br>
bloat does not happen often.<br></blockquote><div><br></div><div style=3D"f=
ont-size:small" class=3D"gmail_default">Heh. =A0</div><div style=3D"font-si=
ze:small" class=3D"gmail_default"><br></div><div style=3D"font-size:small" =
class=3D"gmail_default">
6% of the time isn&#39;t &quot;often&quot;? =A0The measurements is much mor=
e a measurement of how much of the time your competing with someone else (o=
r yourself in background) for the bottleneck than anything else.</div><div =
style=3D"font-size:small" class=3D"gmail_default">
<br></div><div style=3D"font-size:small" class=3D"gmail_default">Start up a=
ny long lived TCP connection (using a modern TCP; that leaves out Windows X=
P).</div><div style=3D"font-size:small" class=3D"gmail_default"><br></div><=
div style=3D"font-size:small" class=3D"gmail_default">
Stand back a few seconds.</div><div style=3D"font-size:small" class=3D"gmai=
l_default"><br></div><div style=3D"font-size:small" class=3D"gmail_default"=
>Measure latency.</div><div style=3D"font-size:small" class=3D"gmail_defaul=
t"><br></div>
<div style=3D"font-size:small" class=3D"gmail_default">Think uploading/down=
loading files/videos, or sending email with images attached, etc.</div><div=
 style=3D"font-size:small" class=3D"gmail_default"><br></div><div style=3D"=
font-size:small" class=3D"gmail_default">
<br></div><div style=3D"font-size:small" class=3D"gmail_default">More insid=
ious is what visiting a web page with lots of embedded images can do.</div>=
<div style=3D"font-size:small" class=3D"gmail_default"><br></div><div style=
=3D"font-size:small" class=3D"gmail_default">
The cross product of:</div><div style=3D"font-size:small" class=3D"gmail_de=
fault">=A0 =A01) current web browsers using many more than 2 TCP connection=
s.</div><div style=3D"font-size:small" class=3D"gmail_default">=A0 =A02) we=
b site &quot;sharding&quot;.</div>
<div style=3D"font-size:small" class=3D"gmail_default">=A0 =A03) the initia=
l window of data in those TCP connections.</div><div style=3D"font-size:sma=
ll" class=3D"gmail_default"><br></div><div style=3D"font-size:small" class=
=3D"gmail_default">
This causes transients of what is up to hundreds of milliseconds of head of=
 line blocking even</div><div style=3D"font-size:small" class=3D"gmail_defa=
ult">on very high speed broadband/wifi connections. =A0Again, I encourage y=
ou to do this measurement on your own broadband connection, by visiting any=
 image heavy web site and running ping....</div>
<div style=3D"font-size:small" class=3D"gmail_default"><br></div><div style=
=3D"font-size:small" class=3D"gmail_default"></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">

<div class=3D"im"><br>
&gt; I encourage everyone to run netalyzr and/or the mlabs tests for<br>
&gt; bufferbloat on your own broadband connections, or do simple copy and<b=
r>
&gt; ping tests inside your own house over wifi to your local file servers.=
...<br>
<br>
</div>While this will identify bloated buffers, it does not help in answeri=
ng<br>
what fraction of Internet users actually experience the problem.<br></block=
quote><div><br></div><div style=3D"font-size:small" class=3D"gmail_default"=
>We&#39;ve not come across any broadband equipment buffered &quot;correctly=
&quot;. =A0If thought is given at all to buffering, it&#39;s been sized to =
the maximum buffering the device might ever need for a single TCP flow at i=
ts maximum bandwidth. =A0Example, plug a current DOCSIS 3 modem (capable up=
 to 300Mbps these days) and use it at 20Mbps; unless the buffersizing amend=
ment has been turned on (no ISP I am aware of yet does so), you&#39;ll be o=
verbuffered by a factor of 15.</div>
<div style=3D"font-size:small" class=3D"gmail_default"><br></div><div style=
=3D"font-size:small" class=3D"gmail_default">And all the operating systems =
have problems, to one degree or another (and as they are all adjacent to wi=
reless links these days, they also contribute to the problem.</div>
<div style=3D"font-size:small" class=3D"gmail_default"><br></div><div style=
=3D"font-size:small" class=3D"gmail_default">Bufferbloat just waits in hidi=
ng to get you when you try to use the network.</div><div style=3D"font-size=
:small" class=3D"gmail_default">
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 - Jim</div><div style=3D"font-size:small" class=3D"gmail_default"><br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Oliver</font></span>=A0</blockquote><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span cl=
ass=3D"HOEnZb"><font color=3D"#888888">
</font></span><div class=3D"HOEnZb"><div class=3D"h5">_____________________=
__________________________<br>
Bloat mailing list<br>
<a href=3D"mailto:Bloat@lists.bufferbloat.net">Bloat@lists.bufferbloat.net<=
/a><br>
<a href=3D"https://lists.bufferbloat.net/listinfo/bloat" target=3D"_blank">=
https://lists.bufferbloat.net/listinfo/bloat</a><br>
</div></div></blockquote></div><br></div></div>

--f46d044519d9c37e3d04d87380f7--

From gorry@erg.abdn.ac.uk  Fri Mar 22 05:19:43 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4C5D21F8839 for <tsvwg@ietfa.amsl.com>; Fri, 22 Mar 2013 05:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlFdc8YHE6vL for <tsvwg@ietfa.amsl.com>; Fri, 22 Mar 2013 05:19:43 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 09D4D21F8837 for <tsvwg@ietf.org>; Fri, 22 Mar 2013 05:19:43 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 324032B44B4; Fri, 22 Mar 2013 12:19:42 +0000 (GMT)
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 3873D2B4275 for <tsvwg@ietf.org>; Fri, 22 Mar 2013 12:19:41 +0000 (GMT)
Message-ID: <514C4C5C.9090706@erg.abdn.ac.uk>
Date: Fri, 22 Mar 2013 12:19:40 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: tsvwg WG <tsvwg@ietf.org>
References: <4F605902.40009@erg.abdn.ac.uk>
In-Reply-To: <4F605902.40009@erg.abdn.ac.uk>
X-Forwarded-Message-Id: <4F605902.40009@erg.abdn.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-udp-encaps-14 to confirm changes - 5th April 2013
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2013 12:19:44 -0000

This email announces the start of a working group last call for
draft-ietf-tsvwg-sctp-udp-encaps-14, "UDP Encapsulation of SCTP Packets 
for End-Host to End-Host Communication".  This document has completed an 
IETF LC and was updated after IESG review. This is now thought to be 
ready to proceed to be published as a PS by RFC-Ed. Please send any 
comments to the TSVWG list.

The draft is available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-udp-encaps-14

Summary of main changes:

* Clarification that the focus is on encapsulation between SCTP endpoints.

* UNSAF considerations added.

* Change from UDP checksum MUST be computed for SCTP/UDP/IPv6 to UDP 
checksum SHOULD be computed for SCTP/UDP/IPv6 to reflect recently 
changed UDP/IPv6 checksum handling, with rationale provided.

A diff between the version submitted to the IESG and the current version 
can be viewed using:
http://tools.ietf.org/rfcdiff?url1=draft-ietf-tsvwg-sctp-udp-encaps-07.txt&url2=draft-ietf-tsvwg-sctp-udp-encaps-14.txt

This shortened last call will end on Friday 5th April 2013.

Emails saying "I support" or "I don't support" publication with these 
changes are also most  helpful in judging the WG consensus.

Please note another running SCTP WGLC also below.

James and Gorry
(TSVWG Chairs)
tsvwg-chairs@ietf.org



-------- Forwarded Message --------

This email announces the start of a working group last call for
draft-ietf-tsvwg-sctp-sack-immediately-02.txt, "SACK-IMMEDIATELY 
Extension for the Stream Control Transmission Protocol". This document 
is now thought to be ready to proceed to be published as a PS. Please 
send any comments to the TSVWG list.

The draft is available at:
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-sack-immediately/

The last call will run for TWO weeks, ending Friday 5th April 2013.

Emails saying "I support" or "I don't support" publication are also most 
  helpful in judging the WG consensus. Please let us know if this draft 
is useful and seems to provide the correct advice.

James, David and Gorry
(TSVWG Chairs)
tsvwg-chairs@ietf.org








From swmike@swm.pp.se  Fri Mar 22 06:23:58 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E72D321F8A8F; Fri, 22 Mar 2013 06:23:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level: 
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1xRtr33oB97l; Fri, 22 Mar 2013 06:23:58 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA8521F8A85; Fri, 22 Mar 2013 06:23:58 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9E3A99C; Fri, 22 Mar 2013 14:23:56 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 92D019A; Fri, 22 Mar 2013 14:23:56 +0100 (CET)
Date: Fri, 22 Mar 2013 14:23:56 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: grenville armitage <garmitage@swin.edu.au>
In-Reply-To: <514BF37D.2080000@swin.edu.au>
Message-ID: <alpine.DEB.2.00.1303221421180.2309@uplift.swm.pp.se>
References: <51408BF4.7090304@cisco.com> <514B5AC8.8000502@net.t-labs.tu-berlin.de> <alpine.DEB.2.00.1303212019520.2309@uplift.swm.pp.se> <CAGhGL2DHrNUEnVF-Qn6OeeD9LvST06c0QaTxSJ+zbKdpQq2Y7g@mail.gmail.com> <alpine.DEB.2.00.1303220521370.2309@uplift.swm.pp.se> <514BF37D.2080000@swin.edu.au>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, aqm@ietf.org, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [tsvwg] [aqm] [Bloat] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2013 13:23:59 -0000

On Fri, 22 Mar 2013, grenville armitage wrote:

>
>
> On 03/22/2013 15:27, Mikael Abrahamsson wrote:
> 	[..]
>> I am not aware of any such work going on, so I'd like to know if
>> anyone else is aware of work in this area?
>
> Of possible relevance, recent FreeBSDs have SIFTR -- a kernel resident
> module for collecting TCP state-machine stats (like cwnd, rtt estimator,
> etc) as packets arrive and depart.
>
> http://www.freebsd.org/cgi/man.cgi?query=siftr

This seems exactly like what I'm after.

On another note, is there software that can get mirrored traffic from 
another host and do TCP analysis of flows when it comes to buffer bloat, 
packet loss etc. If there was, I am in the position of running this 
against a large number of customers over time and can present the results.

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

From touch@isi.edu  Fri Mar 22 08:14:42 2013
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACA121F8E7D for <tsvwg@ietfa.amsl.com>; Fri, 22 Mar 2013 08:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.247
X-Spam-Level: 
X-Spam-Status: No, score=-103.247 tagged_above=-999 required=5 tests=[AWL=-0.648, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wSs8kc80To4d for <tsvwg@ietfa.amsl.com>; Fri, 22 Mar 2013 08:14:41 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 1D86121F8D1A for <tsvwg@ietf.org>; Fri, 22 Mar 2013 08:14:41 -0700 (PDT)
Received: from [192.168.1.89] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r2MFDhjD018845 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 22 Mar 2013 08:13:46 -0700 (PDT)
Message-ID: <514C7528.3060203@isi.edu>
Date: Fri, 22 Mar 2013 08:13:44 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com> <8C48B86A895913448548E6D15DA7553B7DC2E7@xmb-rcd-x09.cisco.com> <514B4F2A.3030902@isi.edu> <8D3D17ACE214DC429325B2B98F3AE71293AEE844@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293AEE844@MX15A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] RFC 4594 update: Routing class
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2013 15:14:42 -0000

Hi, David,

Routing != network control.

It's a subset thereof; I don't want the name to imply that we need 
another class for other sorts of network control traffic.

(and even network control is a bit "application"-oriented, but I'll 
accept that it's the more effective way to say "critical internal traffic")

Joe

On 3/22/2013 12:07 AM, Black, David wrote:
> Joe,
>
> This is already a solved problem.  This traffic class is called "Network Control"
> in RFC 4594 (which recommends CS6 for that class of traffic).  The use of "Routing"
> as a class name here name is effectively shorthand for that "Network Control" class.
>
> Thanks,
> --David
>
>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of Joe
>> Touch
>> Sent: Thursday, March 21, 2013 2:19 PM
>> To: Fred Baker (fred)
>> Cc: tsvwg@ietf.org
>> Subject: Re: [tsvwg] RFC 4594 update: Routing class
>>
>> Again, I don't like classes named for applications - or protocols, or
>> groups of protocols. This ought to be something you can describe in
>> terms of the service provided, not how the service is used.
>>
>> Joe
>>
>> On 3/19/2013 1:53 PM, Fred Baker (fred) wrote:
>>> I was unable to attend twvwg at IETF 86 as it competed with a meeting I
>> presented in. I am told that there was a presentation in which folks argued
>> against having a class of traffic for routing traffic. I'd like to comment on
>> that.
>>>
>>> The origin of a class of traffic for routing traffic was a bug. The Cisco
>> 7000 had an issue with its offloaded forwarding cards, of which it had two.
>> When there was a route flap, it blew away the route cache and then rebuilt it
>> in response to traffic it needed to forward. In that implementation, that
>> meant that the Route Processor (the CPU) suddenly had all traffic from all
>> sources flooded into it. The impact of that was to make it very difficult for
>> the RP to actually re-populate the Route Cache. Doubleplus ungood. The work-
>> around was to rate-limit traffic from the line cards to the RP. However, rate
>> limiting the routing traffic worked against getting routing to stabilize, so
>> we marked routing traffic, and did not rate limit *it* from going to the RP.
>>>
>>> Fast forward nearly 20 years. We don't have that bug anymore, if anything
>> because nobody equipped with a right mind uses the Cisco 7000 any more.
>>>
>>> However...
>>>
>>> If we're going to discuss quality of service for any application, we are
>> making some fundamental assumptions. These include the concept of having
>> enough bandwidth and so on; we're managing traffic at points in time when peak
>> traffic loads on a millisecond scale create issues. One of those fundamental
>> issues is that routing must be current; if we're sending traffic on a route
>> that loops because the other guy updated his route table but we didn't, or
>> vice versa, or for which interface or next hop router is no longer there, we
>> can discuss jitter, rate, and loss to our heart's content - the application's
>> traffic isn't going to get there. At. All. And won't until routing stabilizes.
>>>
>>> The fundamental argument for a class of traffic for routing in 2013 is not
>> that routing requires certain jitter, rate, or etc characteristics; it is that
>> routing traffic (apart from AQM issues, see separate discussion on
>> aqm@ietf.org) should simply *not*be*dropped* in the normal course of business.
>> Routing is fundamental to all other services the network delivers, including
>> QoS, and including every networks's SLAs.
>>>
>>> Now, one can say that routing is between neighboring nodes, and a router is
>> able to do special things with traffic it itself originates. It is true that a
>> router can do special things with its own traffic, and they do. But BGP
>> Routing frequently goes from Route Arbiter to Route Arbiter instead of Router
>> to Router, which is to say through other routers between routing engines.
>> Traffic through other routers is traffic through other routers, not a router's
>> own traffic. It requires some form of end to end marking to protect it.
>> Something like a DSCP.
>>>
>

From Michael.Tuexen@lurchi.franken.de  Sat Mar 23 06:19:16 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75BBA21F89C7 for <tsvwg@ietfa.amsl.com>; Sat, 23 Mar 2013 06:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6d0zUtDLVEv for <tsvwg@ietfa.amsl.com>; Sat, 23 Mar 2013 06:19:15 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id F0D5221F88C1 for <tsvwg@ietf.org>; Sat, 23 Mar 2013 06:19:14 -0700 (PDT)
Received: from [192.168.1.101] (p508FACBB.dip.t-dialin.net [80.143.172.187]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 09B951C0C069B; Sat, 23 Mar 2013 14:19:11 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293AEE3FE@MX15A.corp.emc.com>
Date: Sat, 23 Mar 2013 14:19:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DC8AE4B-298D-46AB-BF17-0E11F3165926@lurchi.franken.de>
References: <4F605902.40009@erg.abdn.ac.uk> <5148B330.3000304@erg.abdn.ac.uk> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FE@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1283)
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, tsvwg WG <tsvwg@ietf.org>
Subject: Re: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Mar 2013 13:19:16 -0000

Hi David,

thank you very much for your comments. I'll incorporate them
in the next revision as stated in detail below.

Best regards
Michael
On Mar 20, 2013, at 3:57 AM, Black, David wrote:

> Comments as an individual - <WG co-chair hat OFF>
>=20
> The draft generally looks good - I have a bunch of minor comments.
>=20
> End of Section 3 - I suggest adding a sentence about the new I-bit:
>=20
> 	This bit was Reserved in RFC 4960 - RFC 4960 specified
> 	that this bit should be set to 0 by the sender and ignored
> 	by the receiver.
Done in CVS. Will be in the next revision.
>=20
> Section 4.1 - The paragraph in this section describes an example of a
> situation in which it is appropriate to set the I-bit.  It needs an
> introductory sentence to say that it is an example, e.g.:
>=20
> 	One example of a situation in which it may be desirable for
> 	an application to trigger setting of the I-bit involves the
> 	SCTP_SENDER_DRY_EVENT in the SCTP socket API [RFC6458].
>=20
> Section 4.2 - Suggest "should" -> "SHOULD" in the following paragraph:
We don't use the normative text in the other use cases of this section.
So being consistent might be good. What about:
<t>If the association is in the SHUTDOWN-PENDING state, setting the =
I-bit
reduces the number of simultaneous associations for a busy server =
handling
short living associations.</t>
>=20
>   If the association is in the SHUTDOWN-PENDING state, the I-bit =
should
>   be set.  This reduces the number of simultaneous associations in =
case
>   of a busy server handling short living associations.
>=20
> Also an editorial nit in the above - "in case of" -> "for"
Done in CVS. Will be in the next revision.
>=20
> Another editorial nit in the following:
>=20
>   If an SCTP association supports the SCTP Stream Reconfiguration
>   extension defined in [RFC6525], the performance can be improved by
>   setting the I-bit when there are pending reconfiguration requests
>   requiring no outstanding DATA chunks.
>=20
> "requiring" -> "that require that there be"
Done in CVS. Will be in the next rev.
Quick question: Instead of

... that require that there be no outstanding DATA chunks.

should it be

... that require that there are no outstanding DATA chunks.


>=20
> Section 5.2:
>=20
>   On reception of an SCTP packet containing a DATA chunk with the =
I-bit
>   set, the receiver SHOULD NOT delay the sending of the corresponding
>   SACK chunk and send it back immediately.
>=20
> "SACK chunk and send it back immediately" -> "SACK chunk, i.e., the
> receiver SHOULD immediately respond with the corresponding SACK chunk"
Done in CVS. Will be in the next rev.
>=20
>=20
> Section 8: Please tell IANA which registry to use by including the
> name of the registry.
I agree, making is clearer is a good thing. So how about:

<t>Following the chunk flag registration procedure defined in
<xref target=3D'RFC6096'/>, IANA should register a new bit, the I-bit, =
for
the DATA chunk. The suggested value is 0x08 and the reference should be
RFCXXXX.</t>
<t>This requires an update of the "DATA Chunk Flags" registry for =
SCTP:</t>
<texttable>
<preamble>DATA Chunk Flags</preamble>
<ttcol align=3D'left'>Chunk Flag Value</ttcol>
<ttcol align=3D'left'>Chunk Flag Name</ttcol>
<ttcol align=3D'left'>Reference</ttcol>
<c>0x01</c> <c>E bit     </c> <c>[RFC4960]</c>
<c>0x02</c> <c>B bit     </c> <c>[RFC4960]</c>
<c>0x04</c> <c>U bit     </c> <c>[RFC4960]</c>
<c>0x08</c> <c>I Bit     </c> <c>[RFCXXXX]</c>
<c>0x10</c> <c>Unassigned</c> <c>         </c>
<c>0x20</c> <c>Unassigned</c> <c>         </c>
<c>0x40</c> <c>Unassigned</c> <c>         </c>
<c>0x80</c> <c>Unassigned</c> <c>         </c>
</texttable>

>=20
> Section 9: Change start of paragraph to acknowledge new security
> consideration:
>=20
> OLD
>   This document does not add any additional security considerations in
>   addition to the ones given in [RFC4960].  It should be noted that a
>   malicious sender can force its peer to send packets containing a =
SACK
> NEW
>   See [RFC4960] for general security considerations for SCTP.  In =
addition,
>   a malicious sender can force its peer to send packets containing a =
SACK
> END
Done in CVS. Will be in the next rev.
>=20
> Thanks,
> --David
>=20
>=20
>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On =
Behalf Of
>> Gorry Fairhurst
>> Sent: Tuesday, March 19, 2013 2:49 PM
>> To: tsvwg WG
>> Subject: [tsvwg] WGLC Announcement for =
draft-ietf-tsvwg-sctp-sack-immediately-
>> 02: 19th March 2013
>>=20
>>=20
>> This email announces the start of a working group last call for
>> draft-ietf-tsvwg-sctp-sack-immediately-02.txt, "SACK-IMMEDIATELY
>> Extension for the Stream Control Transmission Protocol". This =
document
>> is now thought to be ready to proceed to be published as a PS. Please
>> send any comments to the TSVWG list.
>>=20
>> The draft is available at:
>> =
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-sack-immediately/
>>=20
>> The last call will run for TWO weeks, ending Friday 5th April 2013.
>>=20
>> Emails saying "I support" or "I don't support" publication are also =
most
>>  helpful in judging the WG consensus. Please let us know if this =
draft
>> is useful and seems to provide the correct advice.
>>=20
>> James, David and Gorry
>> (TSVWG Chairs)
>> tsvwg-chairs@ietf.org
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>=20
>=20


From Michael.Tuexen@lurchi.franken.de  Sat Mar 23 12:03:42 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63E8B21F8A4A for <tsvwg@ietfa.amsl.com>; Sat, 23 Mar 2013 12:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pguswBnKKznj for <tsvwg@ietfa.amsl.com>; Sat, 23 Mar 2013 12:03:41 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE2321F89DA for <tsvwg@ietf.org>; Sat, 23 Mar 2013 12:03:41 -0700 (PDT)
Received: from [192.168.1.101] (p508F9C22.dip.t-dialin.net [80.143.156.34]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id D07CC1C0C069B; Sat, 23 Mar 2013 20:03:39 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <5149B215.6050608@ericsson.com>
Date: Sat, 23 Mar 2013 20:03:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B27210F-40D5-437B-A743-CAFB3A899E66@lurchi.franken.de>
References: <5149B215.6050608@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.1283)
Cc: draft-ietf-tsvwg-sctp-dtls-encaps@tools.ietf.org, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] review of draft-ietf-tsvwg-sctp-dtls-encaps-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Mar 2013 19:03:42 -0000

On Mar 20, 2013, at 1:56 PM, Magnus Westerlund wrote:

> Hi,
>=20
> I have reviewed the SCTP in DTLS encapsulation draft and have some
> comments.
>=20
> 1. Abstract:
> SCTP
>   over DTLS is used by the RTCWeb protocol suite for transporting non-
>   media data between browsers.
>=20
> I think if one likes to include something like this in the abstract =
one
> should word it like "An initial usage of ..."
>=20
> 2. Section 5.5:
>   The SCTP implementation MUST support the extension defined in
>   [RFC3758].
>=20
> I wonder why this is required in a protocol encapsulation declaration?
> This specification is from my perspective a common tool that anyone =
that
> has similar requirements as WebRTC can choose to use. CLUE WG is =
clearly
> one with high probability to have need for UDP/DTLS/SCTP. However, I
> don't yet know if CLUE for example has any requirements that requires
> partial reliability.
>=20
> So please explain why mandating the partial reliability is necessary =
for
> a DTLS encapsulation of SCTP. I think it is fine for the RTCWEB data
> channel document to mandate the support of the PR-SCTP extension in =
the
> context of WebRTC. But, please try to have the correct specifications =
in
> the appropriate places.
>=20
> 3. Section 5.6:
> The same as 2) appears to be true also here. Are there reasons why one
> needs this extension when one uses the DTLS encapsulation?
>=20
> 4. Section 5.7:
> To my understanding this is a pure performance enchancement. Thus I
> wonder over the SHOULD level of an extension that yet not exist. I =
think
> it is fine to indicate the issue. And if you actually have a draft =
ready
> do an informative reference. But I do question the need for a =
normative
> reference here. Isn't it better to let this specification be published
> in a timely fashion?
I think this extension is really needed. In the meantime there is an
ID for it:
http://tools.ietf.org/html/draft-stewart-tsvwg-sctp-ndata-01
The document is not complete yet, but we plan to have it completed
and implemented by the IETF in Berlin...
>=20
> 5. Section 5.8:
> Yet another case of a potential issue when running in common context
> with real-time applications. This encapsulation does not in any way is
> solely for real-time applications. Thus I think both using MAY is
> unwarranted and I question how necessary this whole discussion are.
>=20
> I think this document is suffering from an issue of not getting the
> correct separation between the documents. This needs to specify the =
DTLS
> encapsualtion of SCTP and what is needed. But I think is the wrong =
place
> to have requirements on SCTP extensions that are specific in the =
context
> of particular applications or class of applications. So please ensure
> that you have the basics of the encapsulation in place, then ensure =
that
> the extensions can be negotiated and allow the applications to make =
the
> choices it needs on what features of SCTP it requires.
You are right. The document contains stuff which deals with
(a) generic SCTP over DTLS encapsulation and
(b) SCTP usage for RTCWeb.

I'm not sure if using SCTP over DTLS makes sense outside the RTCWeb =
scope.
For general usage, I would suggest to use SCTP over UDP...

So I guess you are you suggesting to move (b) into a different document.
Would make
http://wiki.tools.ietf.org/html/draft-ietf-rtcweb-data-channel-04
more sense for you?

Best regards
Michael
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
>=20


From Michael.Tuexen@lurchi.franken.de  Sun Mar 24 11:27:35 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD4F21F88BE for <tsvwg@ietfa.amsl.com>; Sun, 24 Mar 2013 11:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BKens9ES9CG1 for <tsvwg@ietfa.amsl.com>; Sun, 24 Mar 2013 11:27:34 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 08EED21F8938 for <tsvwg@ietf.org>; Sun, 24 Mar 2013 11:27:33 -0700 (PDT)
Received: from [192.168.1.101] (p508FBA33.dip.t-dialin.net [80.143.186.51]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 49A7E1C0B4047; Sun, 24 Mar 2013 19:27:31 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <6B27210F-40D5-437B-A743-CAFB3A899E66@lurchi.franken.de>
Date: Sun, 24 Mar 2013 19:27:30 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E1C22747-680A-4FD7-9C19-BEF35AF2D641@lurchi.franken.de>
References: <5149B215.6050608@ericsson.com> <6B27210F-40D5-437B-A743-CAFB3A899E66@lurchi.franken.de>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.1283)
Cc: draft-ietf-tsvwg-sctp-dtls-encaps@tools.ietf.org, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] review of draft-ietf-tsvwg-sctp-dtls-encaps-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Mar 2013 18:27:35 -0000

On Mar 23, 2013, at 8:03 PM, Michael Tuexen wrote:

> On Mar 20, 2013, at 1:56 PM, Magnus Westerlund wrote:
>=20
>> Hi,
>>=20
>> I have reviewed the SCTP in DTLS encapsulation draft and have some
>> comments.
>>=20
>> 1. Abstract:
>> SCTP
>>  over DTLS is used by the RTCWeb protocol suite for transporting non-
>>  media data between browsers.
>>=20
>> I think if one likes to include something like this in the abstract =
one
>> should word it like "An initial usage of ..."
>>=20
>> 2. Section 5.5:
>>  The SCTP implementation MUST support the extension defined in
>>  [RFC3758].
>>=20
>> I wonder why this is required in a protocol encapsulation =
declaration?
>> This specification is from my perspective a common tool that anyone =
that
>> has similar requirements as WebRTC can choose to use. CLUE WG is =
clearly
>> one with high probability to have need for UDP/DTLS/SCTP. However, I
>> don't yet know if CLUE for example has any requirements that requires
>> partial reliability.
>>=20
>> So please explain why mandating the partial reliability is necessary =
for
>> a DTLS encapsulation of SCTP. I think it is fine for the RTCWEB data
>> channel document to mandate the support of the PR-SCTP extension in =
the
>> context of WebRTC. But, please try to have the correct specifications =
in
>> the appropriate places.
>>=20
>> 3. Section 5.6:
>> The same as 2) appears to be true also here. Are there reasons why =
one
>> needs this extension when one uses the DTLS encapsulation?
>>=20
>> 4. Section 5.7:
>> To my understanding this is a pure performance enchancement. Thus I
>> wonder over the SHOULD level of an extension that yet not exist. I =
think
>> it is fine to indicate the issue. And if you actually have a draft =
ready
>> do an informative reference. But I do question the need for a =
normative
>> reference here. Isn't it better to let this specification be =
published
>> in a timely fashion?
> I think this extension is really needed. In the meantime there is an
> ID for it:
> http://tools.ietf.org/html/draft-stewart-tsvwg-sctp-ndata-01
> The document is not complete yet, but we plan to have it completed
> and implemented by the IETF in Berlin...
>>=20
>> 5. Section 5.8:
>> Yet another case of a potential issue when running in common context
>> with real-time applications. This encapsulation does not in any way =
is
>> solely for real-time applications. Thus I think both using MAY is
>> unwarranted and I question how necessary this whole discussion are.
>>=20
>> I think this document is suffering from an issue of not getting the
>> correct separation between the documents. This needs to specify the =
DTLS
>> encapsualtion of SCTP and what is needed. But I think is the wrong =
place
>> to have requirements on SCTP extensions that are specific in the =
context
>> of particular applications or class of applications. So please ensure
>> that you have the basics of the encapsulation in place, then ensure =
that
>> the extensions can be negotiated and allow the applications to make =
the
>> choices it needs on what features of SCTP it requires.
> You are right. The document contains stuff which deals with
> (a) generic SCTP over DTLS encapsulation and
> (b) SCTP usage for RTCWeb.
>=20
> I'm not sure if using SCTP over DTLS makes sense outside the RTCWeb =
scope.
> For general usage, I would suggest to use SCTP over UDP...
>=20
> So I guess you are you suggesting to move (b) into a different =
document.
> Would make
> http://wiki.tools.ietf.org/html/draft-ietf-rtcweb-data-channel-04
> more sense for you?
What I missed... One possibility to make things clearer would be to
move all RTCWeb specific stuff into a separate section within the encaps
document. This would also make things clear. Would that be OK for you?

Best regards
Michael
>=20
> Best regards
> Michael
>>=20
>> Cheers
>>=20
>> Magnus Westerlund
>>=20
>> =
----------------------------------------------------------------------
>> Multimedia Technologies, Ericsson Research EAB/TVM
>> =
----------------------------------------------------------------------
>> Ericsson AB                | Phone  +46 10 7148287
>> F=E4r=F6gatan 6                | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
>> =
----------------------------------------------------------------------
>>=20
>>=20
>=20
>=20


From david.black@emc.com  Mon Mar 25 15:27:59 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3769E21F8623 for <tsvwg@ietfa.amsl.com>; Mon, 25 Mar 2013 15:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i56vnHU8OIgn for <tsvwg@ietfa.amsl.com>; Mon, 25 Mar 2013 15:27:58 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0970221F8618 for <tsvwg@ietf.org>; Mon, 25 Mar 2013 15:27:57 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2PMRmu0006004 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Mar 2013 18:27:52 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 25 Mar 2013 18:27:40 -0400
Received: from mxhub25.corp.emc.com (mxhub25.corp.emc.com [10.254.110.181]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2PMRd85011907; Mon, 25 Mar 2013 18:27:39 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub25.corp.emc.com ([10.254.110.181]) with mapi; Mon, 25 Mar 2013 18:27:39 -0400
From: "Black, David" <david.black@emc.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Mon, 25 Mar 2013 18:27:38 -0400
Thread-Topic: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013
Thread-Index: Ac4nyS6+PdN6+PAUR5yZIaaeVksWXwB3m/Kw
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293AEED90@MX15A.corp.emc.com>
References: <4F605902.40009@erg.abdn.ac.uk> <5148B330.3000304@erg.abdn.ac.uk> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FE@MX15A.corp.emc.com> <5DC8AE4B-298D-46AB-BF17-0E11F3165926@lurchi.franken.de>
In-Reply-To: <5DC8AE4B-298D-46AB-BF17-0E11F3165926@lurchi.franken.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, tsvwg WG <tsvwg@ietf.org>
Subject: Re: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2013 22:27:59 -0000

Hi Michael,

All of your proposed changes look fine to me, including not using "SHOULD" =
in 4.2.

Are you also going to pick up the new sentence in 4.1 below?

I'll trust you to get the IANA registry contents correct.

Thanks,
--David

> -----Original Message-----
> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
> Sent: Saturday, March 23, 2013 9:19 AM
> To: Black, David
> Cc: gorry@erg.abdn.ac.uk; tsvwg WG
> Subject: Re: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-
> immediately-02: 19th March 2013
>=20
> Hi David,
>=20
> thank you very much for your comments. I'll incorporate them
> in the next revision as stated in detail below.
>=20
> Best regards
> Michael
> On Mar 20, 2013, at 3:57 AM, Black, David wrote:
>=20
> > Comments as an individual - <WG co-chair hat OFF>
> >
> > The draft generally looks good - I have a bunch of minor comments.
> >
> > End of Section 3 - I suggest adding a sentence about the new I-bit:
> >
> > 	This bit was Reserved in RFC 4960 - RFC 4960 specified
> > 	that this bit should be set to 0 by the sender and ignored
> > 	by the receiver.
> Done in CVS. Will be in the next revision.
> >
> > Section 4.1 - The paragraph in this section describes an example of a
> > situation in which it is appropriate to set the I-bit.  It needs an
> > introductory sentence to say that it is an example, e.g.:
> >
> > 	One example of a situation in which it may be desirable for
> > 	an application to trigger setting of the I-bit involves the
> > 	SCTP_SENDER_DRY_EVENT in the SCTP socket API [RFC6458].
> >
> > Section 4.2 - Suggest "should" -> "SHOULD" in the following paragraph:
> We don't use the normative text in the other use cases of this section.
> So being consistent might be good. What about:
> <t>If the association is in the SHUTDOWN-PENDING state, setting the I-bit
> reduces the number of simultaneous associations for a busy server handlin=
g
> short living associations.</t>
> >
> >   If the association is in the SHUTDOWN-PENDING state, the I-bit should
> >   be set.  This reduces the number of simultaneous associations in case
> >   of a busy server handling short living associations.
> >
> > Also an editorial nit in the above - "in case of" -> "for"
> Done in CVS. Will be in the next revision.
> >
> > Another editorial nit in the following:
> >
> >   If an SCTP association supports the SCTP Stream Reconfiguration
> >   extension defined in [RFC6525], the performance can be improved by
> >   setting the I-bit when there are pending reconfiguration requests
> >   requiring no outstanding DATA chunks.
> >
> > "requiring" -> "that require that there be"
> Done in CVS. Will be in the next rev.
> Quick question: Instead of
>=20
> ... that require that there be no outstanding DATA chunks.
>=20
> should it be
>=20
> ... that require that there are no outstanding DATA chunks.
>=20
>=20
> >
> > Section 5.2:
> >
> >   On reception of an SCTP packet containing a DATA chunk with the I-bit
> >   set, the receiver SHOULD NOT delay the sending of the corresponding
> >   SACK chunk and send it back immediately.
> >
> > "SACK chunk and send it back immediately" -> "SACK chunk, i.e., the
> > receiver SHOULD immediately respond with the corresponding SACK chunk"
> Done in CVS. Will be in the next rev.
> >
> >
> > Section 8: Please tell IANA which registry to use by including the
> > name of the registry.
> I agree, making is clearer is a good thing. So how about:
>=20
> <t>Following the chunk flag registration procedure defined in
> <xref target=3D'RFC6096'/>, IANA should register a new bit, the I-bit, fo=
r
> the DATA chunk. The suggested value is 0x08 and the reference should be
> RFCXXXX.</t>
> <t>This requires an update of the "DATA Chunk Flags" registry for SCTP:</=
t>
> <texttable>
> <preamble>DATA Chunk Flags</preamble>
> <ttcol align=3D'left'>Chunk Flag Value</ttcol>
> <ttcol align=3D'left'>Chunk Flag Name</ttcol>
> <ttcol align=3D'left'>Reference</ttcol>
> <c>0x01</c> <c>E bit     </c> <c>[RFC4960]</c>
> <c>0x02</c> <c>B bit     </c> <c>[RFC4960]</c>
> <c>0x04</c> <c>U bit     </c> <c>[RFC4960]</c>
> <c>0x08</c> <c>I Bit     </c> <c>[RFCXXXX]</c>
> <c>0x10</c> <c>Unassigned</c> <c>         </c>
> <c>0x20</c> <c>Unassigned</c> <c>         </c>
> <c>0x40</c> <c>Unassigned</c> <c>         </c>
> <c>0x80</c> <c>Unassigned</c> <c>         </c>
> </texttable>
>=20
> >
> > Section 9: Change start of paragraph to acknowledge new security
> > consideration:
> >
> > OLD
> >   This document does not add any additional security considerations in
> >   addition to the ones given in [RFC4960].  It should be noted that a
> >   malicious sender can force its peer to send packets containing a SACK
> > NEW
> >   See [RFC4960] for general security considerations for SCTP.  In addit=
ion,
> >   a malicious sender can force its peer to send packets containing a SA=
CK
> > END
> Done in CVS. Will be in the next rev.
> >
> > Thanks,
> > --David
> >
> >
> >> -----Original Message-----
> >> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf=
 Of
> >> Gorry Fairhurst
> >> Sent: Tuesday, March 19, 2013 2:49 PM
> >> To: tsvwg WG
> >> Subject: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-
> immediately-
> >> 02: 19th March 2013
> >>
> >>
> >> This email announces the start of a working group last call for
> >> draft-ietf-tsvwg-sctp-sack-immediately-02.txt, "SACK-IMMEDIATELY
> >> Extension for the Stream Control Transmission Protocol". This document
> >> is now thought to be ready to proceed to be published as a PS. Please
> >> send any comments to the TSVWG list.
> >>
> >> The draft is available at:
> >> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-sack-immediately=
/
> >>
> >> The last call will run for TWO weeks, ending Friday 5th April 2013.
> >>
> >> Emails saying "I support" or "I don't support" publication are also mo=
st
> >>  helpful in judging the WG consensus. Please let us know if this draft
> >> is useful and seems to provide the correct advice.
> >>
> >> James, David and Gorry
> >> (TSVWG Chairs)
> >> tsvwg-chairs@ietf.org
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
>=20


From Michael.Tuexen@lurchi.franken.de  Tue Mar 26 01:32:31 2013
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09CC721F88A2 for <tsvwg@ietfa.amsl.com>; Tue, 26 Mar 2013 01:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24179bDWSKoV for <tsvwg@ietfa.amsl.com>; Tue, 26 Mar 2013 01:32:30 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 7E26821F8820 for <tsvwg@ietf.org>; Tue, 26 Mar 2013 01:32:29 -0700 (PDT)
Received: from [192.168.1.101] (p508F9EC4.dip.t-dialin.net [80.143.158.196]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 8E7C01C0C0BD6; Tue, 26 Mar 2013 09:32:26 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293AEED90@MX15A.corp.emc.com>
Date: Tue, 26 Mar 2013 09:32:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <532CE581-056D-471B-8821-11BC5A645A9A@lurchi.franken.de>
References: <4F605902.40009@erg.abdn.ac.uk> <5148B330.3000304@erg.abdn.ac.uk> <8D3D17ACE214DC429325B2B98F3AE71293AEE3FE@MX15A.corp.emc.com> <5DC8AE4B-298D-46AB-BF17-0E11F3165926@lurchi.franken.de> <8D3D17ACE214DC429325B2B98F3AE71293AEED90@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1283)
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, tsvwg WG <tsvwg@ietf.org>
Subject: Re: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2013 08:32:31 -0000

On Mar 25, 2013, at 11:27 PM, Black, David wrote:

> Hi Michael,
>=20
> All of your proposed changes look fine to me, including not using =
"SHOULD" in 4.2.
>=20
> Are you also going to pick up the new sentence in 4.1 below?
Sure. Sorry I missed that. Thank for drawing my attention to it.

Best regards
Michael
>=20
> I'll trust you to get the IANA registry contents correct.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
>> Sent: Saturday, March 23, 2013 9:19 AM
>> To: Black, David
>> Cc: gorry@erg.abdn.ac.uk; tsvwg WG
>> Subject: Re: [tsvwg] WGLC Announcement for =
draft-ietf-tsvwg-sctp-sack-
>> immediately-02: 19th March 2013
>>=20
>> Hi David,
>>=20
>> thank you very much for your comments. I'll incorporate them
>> in the next revision as stated in detail below.
>>=20
>> Best regards
>> Michael
>> On Mar 20, 2013, at 3:57 AM, Black, David wrote:
>>=20
>>> Comments as an individual - <WG co-chair hat OFF>
>>>=20
>>> The draft generally looks good - I have a bunch of minor comments.
>>>=20
>>> End of Section 3 - I suggest adding a sentence about the new I-bit:
>>>=20
>>> 	This bit was Reserved in RFC 4960 - RFC 4960 specified
>>> 	that this bit should be set to 0 by the sender and ignored
>>> 	by the receiver.
>> Done in CVS. Will be in the next revision.
>>>=20
>>> Section 4.1 - The paragraph in this section describes an example of =
a
>>> situation in which it is appropriate to set the I-bit.  It needs an
>>> introductory sentence to say that it is an example, e.g.:
>>>=20
>>> 	One example of a situation in which it may be desirable for
>>> 	an application to trigger setting of the I-bit involves the
>>> 	SCTP_SENDER_DRY_EVENT in the SCTP socket API [RFC6458].
>>>=20
>>> Section 4.2 - Suggest "should" -> "SHOULD" in the following =
paragraph:
>> We don't use the normative text in the other use cases of this =
section.
>> So being consistent might be good. What about:
>> <t>If the association is in the SHUTDOWN-PENDING state, setting the =
I-bit
>> reduces the number of simultaneous associations for a busy server =
handling
>> short living associations.</t>
>>>=20
>>>  If the association is in the SHUTDOWN-PENDING state, the I-bit =
should
>>>  be set.  This reduces the number of simultaneous associations in =
case
>>>  of a busy server handling short living associations.
>>>=20
>>> Also an editorial nit in the above - "in case of" -> "for"
>> Done in CVS. Will be in the next revision.
>>>=20
>>> Another editorial nit in the following:
>>>=20
>>>  If an SCTP association supports the SCTP Stream Reconfiguration
>>>  extension defined in [RFC6525], the performance can be improved by
>>>  setting the I-bit when there are pending reconfiguration requests
>>>  requiring no outstanding DATA chunks.
>>>=20
>>> "requiring" -> "that require that there be"
>> Done in CVS. Will be in the next rev.
>> Quick question: Instead of
>>=20
>> ... that require that there be no outstanding DATA chunks.
>>=20
>> should it be
>>=20
>> ... that require that there are no outstanding DATA chunks.
>>=20
>>=20
>>>=20
>>> Section 5.2:
>>>=20
>>>  On reception of an SCTP packet containing a DATA chunk with the =
I-bit
>>>  set, the receiver SHOULD NOT delay the sending of the corresponding
>>>  SACK chunk and send it back immediately.
>>>=20
>>> "SACK chunk and send it back immediately" -> "SACK chunk, i.e., the
>>> receiver SHOULD immediately respond with the corresponding SACK =
chunk"
>> Done in CVS. Will be in the next rev.
>>>=20
>>>=20
>>> Section 8: Please tell IANA which registry to use by including the
>>> name of the registry.
>> I agree, making is clearer is a good thing. So how about:
>>=20
>> <t>Following the chunk flag registration procedure defined in
>> <xref target=3D'RFC6096'/>, IANA should register a new bit, the =
I-bit, for
>> the DATA chunk. The suggested value is 0x08 and the reference should =
be
>> RFCXXXX.</t>
>> <t>This requires an update of the "DATA Chunk Flags" registry for =
SCTP:</t>
>> <texttable>
>> <preamble>DATA Chunk Flags</preamble>
>> <ttcol align=3D'left'>Chunk Flag Value</ttcol>
>> <ttcol align=3D'left'>Chunk Flag Name</ttcol>
>> <ttcol align=3D'left'>Reference</ttcol>
>> <c>0x01</c> <c>E bit     </c> <c>[RFC4960]</c>
>> <c>0x02</c> <c>B bit     </c> <c>[RFC4960]</c>
>> <c>0x04</c> <c>U bit     </c> <c>[RFC4960]</c>
>> <c>0x08</c> <c>I Bit     </c> <c>[RFCXXXX]</c>
>> <c>0x10</c> <c>Unassigned</c> <c>         </c>
>> <c>0x20</c> <c>Unassigned</c> <c>         </c>
>> <c>0x40</c> <c>Unassigned</c> <c>         </c>
>> <c>0x80</c> <c>Unassigned</c> <c>         </c>
>> </texttable>
>>=20
>>>=20
>>> Section 9: Change start of paragraph to acknowledge new security
>>> consideration:
>>>=20
>>> OLD
>>>  This document does not add any additional security considerations =
in
>>>  addition to the ones given in [RFC4960].  It should be noted that a
>>>  malicious sender can force its peer to send packets containing a =
SACK
>>> NEW
>>>  See [RFC4960] for general security considerations for SCTP.  In =
addition,
>>>  a malicious sender can force its peer to send packets containing a =
SACK
>>> END
>> Done in CVS. Will be in the next rev.
>>>=20
>>> Thanks,
>>> --David
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On =
Behalf Of
>>>> Gorry Fairhurst
>>>> Sent: Tuesday, March 19, 2013 2:49 PM
>>>> To: tsvwg WG
>>>> Subject: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-
>> immediately-
>>>> 02: 19th March 2013
>>>>=20
>>>>=20
>>>> This email announces the start of a working group last call for
>>>> draft-ietf-tsvwg-sctp-sack-immediately-02.txt, "SACK-IMMEDIATELY
>>>> Extension for the Stream Control Transmission Protocol". This =
document
>>>> is now thought to be ready to proceed to be published as a PS. =
Please
>>>> send any comments to the TSVWG list.
>>>>=20
>>>> The draft is available at:
>>>> =
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-sack-immediately/
>>>>=20
>>>> The last call will run for TWO weeks, ending Friday 5th April 2013.
>>>>=20
>>>> Emails saying "I support" or "I don't support" publication are also =
most
>>>> helpful in judging the WG consensus. Please let us know if this =
draft
>>>> is useful and seems to provide the correct advice.
>>>>=20
>>>> James, David and Gorry
>>>> (TSVWG Chairs)
>>>> tsvwg-chairs@ietf.org
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>=20
>>>=20
>>=20
>=20
>=20


From mirja.kuehlewind@ikr.uni-stuttgart.de  Tue Mar 26 10:25:50 2013
Return-Path: <mirja.kuehlewind@ikr.uni-stuttgart.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 086F921F8B45; Tue, 26 Mar 2013 10:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.762
X-Spam-Level: 
X-Spam-Status: No, score=-1.762 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, HELO_EQ_DE=0.35, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zx+qpugt7QSG; Tue, 26 Mar 2013 10:25:49 -0700 (PDT)
Received: from mailsrv.ikr.uni-stuttgart.de (mailsrv.ikr.uni-stuttgart.de [129.69.170.2]) by ietfa.amsl.com (Postfix) with ESMTP id 2ECB221F8A3F; Tue, 26 Mar 2013 10:25:48 -0700 (PDT)
Received: from netsrv1.ikr.uni-stuttgart.de (netsrv1-c [10.11.12.12]) by mailsrv.ikr.uni-stuttgart.de (Postfix) with ESMTP id 00A5660277; Tue, 26 Mar 2013 18:25:48 +0100 (CET)
Received: from vpn-2-cl195 (vpn-2-cl195 [10.41.21.195]) by netsrv1.ikr.uni-stuttgart.de (Postfix) with ESMTP id BA47360276; Tue, 26 Mar 2013 18:25:47 +0100 (CET)
From: Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
Organization: University of Stuttgart (Germany), IKR
To: aqm@ietf.org
Date: Tue, 26 Mar 2013 18:25:47 +0100
User-Agent: KMail/1.9.10 (enterprise35 0.20101217.1207316)
References: <51408BF4.7090304@cisco.com> <CAGhGL2DHrNUEnVF-Qn6OeeD9LvST06c0QaTxSJ+zbKdpQq2Y7g@mail.gmail.com> <alpine.DEB.2.00.1303220521370.2309@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1303220521370.2309@uplift.swm.pp.se>
X-KMail-QuotePrefix: > 
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <201303261825.47601.mirja.kuehlewind@ikr.uni-stuttgart.de>
Cc: bloat <bloat@lists.bufferbloat.net>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] [aqm] [Bloat] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2013 17:25:50 -0000

Hi,

+1. Would be nice to have such statictics available for the user in every O=
S!

Mirja


On Friday 22 March 2013 05:27:31 Mikael Abrahamsson wrote:
> On Thu, 21 Mar 2013, Jim Gettys wrote:
> > Every more modern TCP can easily fill any sized buffer given time with a
> > single TCP connection.
>
> I agree with this, I made this discovery myself back in 2004 or so, and
> had to implement Fairqueue and WRED on my home connection to make it
> bearable to use any interactive application while transferring files.
>
> In IETF75 in Stockholm in 2009, I made proposals in both TCP and at open
> mic in one of the sessions, that I would like to see statistics and
> performance numbers on packet loss, delay variation etc from actual
> traffic. The IP stack has great insight in what the network conditions are
> (especially with TCP Timestamping), but as far as I know it's not really
> exported in any usable format to the user. My idea was to have some kind
> of dashboard for the user to show if currently the network was the
> limiting factor, if the tcp window was maxed out etc. Would also be nice
> if there was output that could be cut/pasted and attached to a fault
> report in case the customer talks to customer support. It would be good if
> this was actually a standard so all OSes did the same.
>
> I am not aware of any such work going on, so I'd like to know if anyone
> else is aware of work in this area?



=2D-=20
=2D------------------------------------------------------------------
Dipl.-Ing. Mirja K=FChlewind
Institute of Communication Networks and Computer Engineering (IKR)
University of Stuttgart, Germany
Pfaffenwaldring 47, D-70569 Stuttgart

tel: +49(0)711/685-67973
email: mirja.kuehlewind@ikr.uni-stuttgart.de
web: www.ikr.uni-stuttgart.de
=2D------------------------------------------------------------------

From rs@netapp.com  Tue Mar 26 10:49:54 2013
Return-Path: <rs@netapp.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB74621F85A4; Tue, 26 Mar 2013 10:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[AWL=0.324, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K0dOHS7A+lIK; Tue, 26 Mar 2013 10:49:50 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id D881421F85A1; Tue, 26 Mar 2013 10:49:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.84,913,1355126400"; d="scan'208";a="34224530"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 26 Mar 2013 10:49:50 -0700
Received: from vmwexceht03-prd.hq.netapp.com (vmwexceht03-prd.hq.netapp.com [10.106.76.241]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r2QHnoef006408; Tue, 26 Mar 2013 10:49:50 -0700 (PDT)
Received: from VMWEXCEHT06-PRD.hq.netapp.com (10.106.77.104) by vmwexceht03-prd.hq.netapp.com (10.106.76.241) with Microsoft SMTP Server (TLS) id 14.2.342.3; Tue, 26 Mar 2013 10:49:50 -0700
Received: from SACEXCMBX02-PRD.hq.netapp.com ([169.254.1.222]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.02.0342.003; Tue, 26 Mar 2013 10:49:49 -0700
From: "Scheffenegger, Richard" <rs@netapp.com>
To: Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>, "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [tsvwg] [aqm] [Bloat] how much of a problem is buffer bloat today?
Thread-Index: AQHOKkb4bz1RAbJaNkyIcjxYVOA1Q5i4PtEA
Date: Tue, 26 Mar 2013 17:49:49 +0000
Message-ID: <012C3117EDDB3C4781FD802A8C27DD4F24ACFA86@SACEXCMBX02-PRD.hq.netapp.com>
References: <51408BF4.7090304@cisco.com> <CAGhGL2DHrNUEnVF-Qn6OeeD9LvST06c0QaTxSJ+zbKdpQq2Y7g@mail.gmail.com> <alpine.DEB.2.00.1303220521370.2309@uplift.swm.pp.se> <201303261825.47601.mirja.kuehlewind@ikr.uni-stuttgart.de>
In-Reply-To: <201303261825.47601.mirja.kuehlewind@ikr.uni-stuttgart.de>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.53]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [tsvwg] [aqm] [Bloat] how much of a problem is buffer bloat	today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2013 17:49:54 -0000

Hmm...


TCP measures RTT;=20

one could create a global histogram of all measured RTTs by TCP (whenever a=
 valid measurement is taken), and export that with "netstat -sp tcp"... Of =
course, vastly different paths would be gobbled up together, but when inves=
tigating specific paths, that should be good enough as a high level startin=
g point.




Richard Scheffenegger


> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Mirja Kuehlewind
> Sent: Dienstag, 26. M=E4rz 2013 18:26
> To: aqm@ietf.org
> Cc: bloat; tsvwg@ietf.org
> Subject: Re: [tsvwg] [aqm] [Bloat] how much of a problem is buffer bloat
> today?
>=20
> Hi,
>=20
> +1. Would be nice to have such statictics available for the user in every
> OS!
>=20
> Mirja
>=20
>=20
> On Friday 22 March 2013 05:27:31 Mikael Abrahamsson wrote:
> > On Thu, 21 Mar 2013, Jim Gettys wrote:
> > > Every more modern TCP can easily fill any sized buffer given time
> > > with a single TCP connection.
> >
> > I agree with this, I made this discovery myself back in 2004 or so,
> > and had to implement Fairqueue and WRED on my home connection to make
> > it bearable to use any interactive application while transferring files=
.
> >
> > In IETF75 in Stockholm in 2009, I made proposals in both TCP and at
> > open mic in one of the sessions, that I would like to see statistics
> > and performance numbers on packet loss, delay variation etc from
> > actual traffic. The IP stack has great insight in what the network
> > conditions are (especially with TCP Timestamping), but as far as I
> > know it's not really exported in any usable format to the user. My
> > idea was to have some kind of dashboard for the user to show if
> > currently the network was the limiting factor, if the tcp window was
> > maxed out etc. Would also be nice if there was output that could be
> > cut/pasted and attached to a fault report in case the customer talks
> > to customer support. It would be good if this was actually a standard s=
o
> all OSes did the same.
> >
> > I am not aware of any such work going on, so I'd like to know if
> > anyone else is aware of work in this area?
>=20
>=20
>=20
> --
> -------------------------------------------------------------------
> Dipl.-Ing. Mirja K=FChlewind
> Institute of Communication Networks and Computer Engineering (IKR)
> University of Stuttgart, Germany Pfaffenwaldring 47, D-70569 Stuttgart
>=20
> tel: +49(0)711/685-67973
> email: mirja.kuehlewind@ikr.uni-stuttgart.de
> web: www.ikr.uni-stuttgart.de
> -------------------------------------------------------------------

From hagen@jauu.net  Tue Mar 26 13:02:24 2013
Return-Path: <hagen@jauu.net>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B866521F8D34; Tue, 26 Mar 2013 13:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.373
X-Spam-Level: 
X-Spam-Status: No, score=-2.373 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3OA5wmIyEskR; Tue, 26 Mar 2013 13:02:24 -0700 (PDT)
Received: from Chamillionaire.breakpoint.cc (Chamillionaire.breakpoint.cc [IPv6:2001:4d88:1ffa:82:880:aa0:9009:64ae]) by ietfa.amsl.com (Postfix) with ESMTP id CF69421F8D06; Tue, 26 Mar 2013 13:02:23 -0700 (PDT)
Received: from pfeifer by Chamillionaire.breakpoint.cc with local (Exim 4.72) (envelope-from <hagen@jauu.net>) id 1UKa4X-000555-E8; Tue, 26 Mar 2013 21:02:17 +0100
Date: Tue, 26 Mar 2013 21:02:16 +0100
From: Hagen Paul Pfeifer <hagen@jauu.net>
To: "Scheffenegger, Richard" <rs@netapp.com>
Message-ID: <20130326200216.GB9410@virgo.local>
References: <51408BF4.7090304@cisco.com> <CAGhGL2DHrNUEnVF-Qn6OeeD9LvST06c0QaTxSJ+zbKdpQq2Y7g@mail.gmail.com> <alpine.DEB.2.00.1303220521370.2309@uplift.swm.pp.se> <201303261825.47601.mirja.kuehlewind@ikr.uni-stuttgart.de> <012C3117EDDB3C4781FD802A8C27DD4F24ACFA86@SACEXCMBX02-PRD.hq.netapp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <012C3117EDDB3C4781FD802A8C27DD4F24ACFA86@SACEXCMBX02-PRD.hq.netapp.com>
X-Key-Id: 98350C22
X-Key-Fingerprint: 490F 557B 6C48 6D7E 5706 2EA2 4A22 8D45 9835 0C22
X-GPG-Key: gpg --recv-keys --keyserver wwwkeys.eu.pgp.net 98350C22
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: bloat <bloat@lists.bufferbloat.net>, "aqm@ietf.org" <aqm@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] [Bloat] [aqm] how much of a problem is buffer bloat today?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2013 20:02:25 -0000

* Scheffenegger, Richard | 2013-03-26 17:49:49 [+0000]:

>TCP measures RTT; 
>
>one could create a global histogram of all measured RTTs by TCP (whenever a
>valid measurement is taken), and export that with "netstat -sp tcp"... Of
>course, vastly different paths would be gobbled up together, but when
>investigating specific paths, that should be good enough as a high level
>starting point.

For Linux tcp-probe[1] is your friend. The last colum is the smoothed round trip
time. The port filter is optional and can be 0 to disable filtering. Not sure
if Linux Distribution ship this module by default. But via tcp-probe you get
accurate per-path rtt statistics without any effort (just a few CPU cycles).


Hagen

[1] http://www.linuxfoundation.org/collaborate/workgroups/networking/tcpprobe


From david.black@emc.com  Fri Mar 29 15:40:06 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FC6721F9002 for <tsvwg@ietfa.amsl.com>; Fri, 29 Mar 2013 15:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qVkpKZWxoCXr for <tsvwg@ietfa.amsl.com>; Fri, 29 Mar 2013 15:40:05 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id B071221F866F for <tsvwg@ietf.org>; Fri, 29 Mar 2013 15:40:05 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2TMe5X6022056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Fri, 29 Mar 2013 18:40:05 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Fri, 29 Mar 2013 18:39:45 -0400
Received: from mxhub29.corp.emc.com (mxhub29.corp.emc.com [128.222.70.169]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2TMdj7L005410 for <tsvwg@ietf.org>; Fri, 29 Mar 2013 18:39:45 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub29.corp.emc.com ([128.222.70.169]) with mapi; Fri, 29 Mar 2013 18:39:44 -0400
From: "Black, David" <david.black@emc.com>
To: "Black, David" <david.black@emc.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Date: Fri, 29 Mar 2013 18:39:44 -0400
Thread-Topic: RFC 4594 update: Audio class - consensus check result
Thread-Index: Ac4heZqhCV4U8t4nS1CkxiPdzdLCfALVDazA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293D36C57@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290FA93C1@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [tsvwg] RFC 4594 update: Audio class - consensus check result
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Mar 2013 22:40:06 -0000

Having reviewed all the messages, I believe that the WG has rough
consensus for (2):

> (2) The newly-standardized Voice-Admit PHB is being added to the
> Audio class.

See RFC 5865 for details of that Voice-Admit PHB.  I noticed an objection
from Ruediger Geib, but no others.

OTOH, I don't believe that the WG has rough consensus for the new name:

> (1) The class is being renamed from "Telephony" to "Audio", in part
> because "Telephony" is interpreted to include video in some contexts
> and that's not intended here.  There have also been some slight
> changes/generalizations to the description.

Suggestions for new names that better characterize the traffic that should
use the class named "Telephony" in RFC 4594, but that do not imply inclusio=
n
of video traffic in that class are encouraged.

Thanks,
--David (tsvwg co-chair)


> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Black, David
> Sent: Friday, March 15, 2013 8:36 AM
> To: tsvwg@ietf.org
> Subject: [tsvwg] RFC 4594 update: Audio class - consensus check
>=20
> The discussion of the Audio service class in the RFC 4594 update
> draft in the tsvwg meeting yesterday reached a couple of initial
> conclusions that need to be checked on the list:
>=20
> (1) The class is being renamed from "Telephony" to "Audio", in part
> because "Telephony" is interpreted to include video in some contexts
> and that's not intended here.  There have also been some slight
> changes/generalizations to the description.
>=20
> (2) The newly-standardized Voice-Admit PHB is being added to the
> Audio class.
>=20
> In the absence of objection on the list, these directions will be
> confirmed as the rough consensus of the tsvwg WG - please comment.
>=20
> 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-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20
>=20


From david.black@emc.com  Fri Mar 29 15:50:10 2013
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DF1321F8596 for <tsvwg@ietfa.amsl.com>; Fri, 29 Mar 2013 15:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9y98azljtdG for <tsvwg@ietfa.amsl.com>; Fri, 29 Mar 2013 15:50:09 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2479D21F8203 for <tsvwg@ietf.org>; Fri, 29 Mar 2013 15:50:08 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2TMo5es020404 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Fri, 29 Mar 2013 18:50:07 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Fri, 29 Mar 2013 18:49:53 -0400
Received: from mxhub30.corp.emc.com (mxhub30.corp.emc.com [128.222.70.170]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2TMnqGp016131 for <tsvwg@ietf.org>; Fri, 29 Mar 2013 18:49:53 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub30.corp.emc.com ([128.222.70.170]) with mapi; Fri, 29 Mar 2013 18:49:52 -0400
From: "Black, David" <david.black@emc.com>
To: "Black, David" <david.black@emc.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Date: Fri, 29 Mar 2013 18:49:51 -0400
Thread-Topic: RFC 4594 update: Hi-Res video class - open issue result
Thread-Index: Ac4hmGOfPp6rctsMRaiGwuexfYqzKALNhCFQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293D36C59@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71290FA94A0@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290FA94A0@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [tsvwg] RFC 4594 update: Hi-Res video class - open issue result
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Mar 2013 22:50:10 -0000

Between discussion in the room and on the list, it is clear
that the WG does not have rough consensus that the new "Hi-Res"
class is needed.  I believe that the WG has actually reached
rough consensus that the this new class is not needed.

The decision criteria were:

> this decision starts from a default to not add the new class:
>=20
> - The new Hi-Res class will only be added if there is good WG
> 	rough consensus that it is needed.
> - Otherwise the class will not be added, even if the WG does not
> 	reach rough consensus that the new class is not needed.

Therefore, the new Hi-Res class should be removed from the next
version of the RFC 4594 update draft.

Moving on, I also wrote:

> in particular please do not include the proposed
> changes to CS4 and CS5 usage at this time - if the new class is to
> be added, then whether to do that via changes to usage of CS4 and
> CS5 will be opened up as a separate topic.

The decision to not add the new "Hi-Res" class suggests that the RFC
4594 update draft should be revised to restore the recommended uses
of CS4 and CS5 to those in RFC 4594, but I am interested in hearing
further input and comments on this topic.

Thanks,
--David (tsvwg WG chair)

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> Black, David
> Sent: Friday, March 15, 2013 2:29 PM
> To: tsvwg@ietf.org
> Subject: [tsvwg] RFC 4594 update: Hi-Res video class - open issue
>=20
> This is about the other RFC 4594 update topic discussed yesterday
> in Orlando.
>=20
> The RFC 4594 update draft proposes to introduce a new diffserv
> class for (high-resolution) telepresence video.  That new class
> would be split out of the Multimedia Conferencing class.  FWIW,
> that Multimedia Conferencing is also the source out off which the
> new Video (Conferencing) class for interactive video will be split
> (the WG already has rough consensus on the need for this new
> Video class).
>=20
> Here's the relevant slide content from Orlando (slide 1 from the
> slide deck on Diffserv Service Class Questions):
>=20
> 	"Hi-Res" NEW
> 		- For video and audio/video conferencing
> 		- Created for policy-based treatment different than "Video"
>=20
> 	Question #1: Is this new class needed?
>=20
> The sense of the room was not clearly "Yes" - for that reason,
> questions #2 and #3 in the slides were not asked in Orlando.
> I heard considerably more of a hum for "No" than "Yes" and a
> similar level of hum for "Not sure" as for "Yes".
>=20
> Please comment on the need (or lack thereof) for this new class -
> this decision starts from a default to not add the new class:
>=20
> - The new Hi-Res class will only be added if there is good WG
> 	rough consensus that it is needed.
> - Otherwise the class will not be added, even if the WG does not
> 	reach rough consensus that the new class is not needed.
>=20
> Please limit discussion to the need or lack thereof for this new
> Hi-Res class, and in particular please do not include the proposed
> changes to CS4 and CS5 usage at this time - if the new class is to
> be added, then whether to do that via changes to usage of CS4 and
> CS5 will be opened up as a separate topic.
>=20
> Thanks,
> --David (tsvwg WG co-chair)
> ----------------------------------------------------
> 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-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20

