AW: Naive question on multiple TCP/IP channels and please dont start a uS NN debate here unless you really want to.

<> Mon, 09 February 2015 08:47 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 4071E1A00B8; Mon, 9 Feb 2015 00:47:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.16
X-Spam-Status: No, score=-1.16 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RifENA3N31GZ; Mon, 9 Feb 2015 00:47:32 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 92D9B1A00A9; Mon, 9 Feb 2015 00:47:31 -0800 (PST)
Received: from ([]) by with ESMTP; 09 Feb 2015 09:47:21 +0100
X-IronPort-AV: E=Sophos;i="5.09,542,1418079600"; d="scan'208";a="614908234"
Received: from ([]) by with ESMTP/TLS/AES128-SHA; 09 Feb 2015 09:47:22 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([]) by ([::1]) with mapi; Mon, 9 Feb 2015 09:47:21 +0100
From: <>
To: <>
Date: Mon, 9 Feb 2015 09:47:20 +0100
Subject: AW: Naive question on multiple TCP/IP channels and please dont start a uS NN debate here unless you really want to.
Thread-Topic: Naive question on multiple TCP/IP channels and please dont start a uS NN debate here unless you really want to.
Thread-Index: AdBDBVq1waQAspliTOScx0MentGvWwBNsZOQ
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5044572A520@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US, de-DE
Content-Language: de-DE
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Approved-At: Mon, 09 Feb 2015 08:16:01 -0800
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 09 Feb 2015 08:47:35 -0000

As Brian pointed out, proposes a method "how to get the labeling/queueing across the AS boundary". Input is welcome.

Commercial DiffServ interconnection products are available. They may however not be be widespread. 

If you however ask the question how to transit the complete QoS concept and codepoints of a sending domain to a customer connected to another domain - that hasn't been standardized yet.  
If your expectation is that a consumer (device) sets priorities of packets and carriers honour these markings, a technical and commercial model accepted by all parties is required. I'm not aware of one (I'm not interested in discussing how to get one on this list).
There's also no generally specified set of packet marks within the Best Effort class, which can transparently cross carrier boundaries on an end to end basis. That might offer a separation of WAN and LAN or application QoS marks (should this be useful).



-----Ursprüngliche Nachricht-----
Von: tsvwg [] Im Auftrag von Richard Shockey
Gesendet: Freitag, 6. Februar 2015 19:25
An: Piers O'Hanlon; Michael Richardson
Cc:; Phillip Hallam-Baker; Jim Gettys; IETF Discussion Mailing List
Betreff: Re: [tsvwg] Naive question on multiple TCP/IP channels and please dont start a uS NN debate here unless you really want to.

Fine now how do you get the labeling/queueing across the AS boundary?  I don’t know any ISP that accepts or recognizes the packet labeling of another AS.

On 2/6/15, 12:28 PM, "Piers O'Hanlon" <> wrote:

>On 6 Feb 2015, at 16:57, Michael Richardson wrote:
>> Jim Gettys <> wrote:
>>> ​What effect does this algorithm have in practice? Here are some
>>> o real time isochronous traffic​ (such as VOIP, skype, etc) won't 
>>>build  a queue, so will be scheduled in preference to your bulk data.
>>> o your DNS traffic will be prioritized.
>>> o your TCP open handshakes will be prioritized  o your DHCP & RA 
>>>handshakes will be prioritized  o your handshakes for TLS will be 
>>>prioritized  o any simple request/response protocol with small 
>>> o the first packet or so of a TCP transfer will be prioritized:
>>> that packet may have the size information needed for web page layout 
>>>in it.
>>> o There is a *positive* incentive for flows to pace their traffic (i.e.
>>> to be a good network citizen, rather than always transmitting at 
>>>line rate).
>>> *All without needing any explicit classification.  No identification 
>>>of  what application is running is being performed at all in this
>> This last part is I think the part that needs to be shouted at 
>>residential  ISPs on a regular basis.  I wish that the IETF and ISOC 
>>was better able to  do this... in particular to ISPs which do not tend 
>>to send the right people  to NANOG/RIPE/etc.
>Explicit class-based queueing is seeing fairly substantial deployment 
>in some places - such as the UK - where for a few years now the default 
>home routers (Thomson/Technicolor TG587/582 etc) for a number of the 
>big ISPs (Plusnet, O2/Sky, Talk-talk and others) have shipped 
>preconfigured with 5 queuing classes that classify traffic and provide 
>for differing treatment. They also have some ALGs that work with 
>SIP/H.323. I'm not aware of AQM enabled on the individual queues but at 
>least they separate the traffic into different queues - albeit based on 
>port number or ALG classifiers. Better than nothing anyway.
>Also the DOCSIS3.1 standard now mandates the use an AQM - namely PIE, 
>though others can be implemented. I'm not sure where that is in terms 
>of deployment though. There's a good report on it here:
>> --
>> ]               Never tell me the odds!                 | ipv6 mesh
>>networks [
>> ]   Michael Richardson, Sandelman Software Works        | network
>>architect  [
>> ]        |   ruby on
>>rails    [