Re: [Idr] New Draft Notification draft-knoll-idr-qos-attribute-00.txt

"Thomas M. Knoll" <knoll@etit.tu-chemnitz.de> Mon, 09 June 2008 19:45 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8028E3A69E6; Mon, 9 Jun 2008 12:45:18 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23E3D3A68EA for <idr@core3.amsl.com>; Mon, 9 Jun 2008 12:45:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.382
X-Spam-Level:
X-Spam-Status: No, score=-1.382 tagged_above=-999 required=5 tests=[AWL=0.867, BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lHHCudcEUJf8 for <idr@core3.amsl.com>; Mon, 9 Jun 2008 12:45:07 -0700 (PDT)
Received: from john.hrz.tu-chemnitz.de (john.hrz.tu-chemnitz.de [134.109.132.2]) by core3.amsl.com (Postfix) with ESMTP id CA4053A6944 for <idr@ietf.org>; Mon, 9 Jun 2008 12:45:06 -0700 (PDT)
Received: from galba.hrz.tu-chemnitz.de ([134.109.133.156] helo=mailbox.hrz.tu-chemnitz.de) by john.hrz.tu-chemnitz.de with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <knoll@etit.tu-chemnitz.de>) id 1K5nIz-0000T8-6w; Mon, 09 Jun 2008 21:45:25 +0200
Received: from tor.hrz.tu-chemnitz.de ([134.109.133.13]) by mailbox.hrz.tu-chemnitz.de with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <knoll@etit.tu-chemnitz.de>) id 1K5nIz-0002cj-43; Mon, 09 Jun 2008 21:45:25 +0200
Received: from tor.hrz.tu-chemnitz.de (localhost.localdomain [127.0.0.1]) by tor.hrz.tu-chemnitz.de (8.13.8/8.12.10) with ESMTP id m59JjPUZ021466; Mon, 9 Jun 2008 21:45:25 +0200
Received: from localhost (tkn@localhost) by tor.hrz.tu-chemnitz.de (8.13.8/8.12.10/Submit) with ESMTP id m59JjOQ3021463; Mon, 9 Jun 2008 21:45:24 +0200
X-Authentication-Warning: tor.hrz.tu-chemnitz.de: tkn owned process doing -bs
Date: Mon, 9 Jun 2008 21:45:24 +0200 (MEST)
From: "Thomas M. Knoll" <knoll@etit.tu-chemnitz.de>
X-X-Sender: tkn@tor.hrz.tu-chemnitz.de
To: Robert Raszuk <raszuk@juniper.net>
In-Reply-To: <484D7A99.4060009@juniper.net>
Message-ID: <alpine.LRH.1.10.0806092142350.2343@tor.hrz.tu-chemnitz.de>
References: <alpine.LRH.1.10.0806091642180.32755@tor.hrz.tu-chemnitz.de> <484D7A99.4060009@juniper.net>
User-Agent: Alpine 1.10 (LRH 962 2008-03-14)
MIME-Version: 1.0
X-Scan-Signature: 7a7caa0833baa437e5d8530a557da03a
Cc: idr@ietf.org
Subject: Re: [Idr] New Draft Notification draft-knoll-idr-qos-attribute-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Thank you, Robert, for this fast reply.

The point of this draft is not to signal single QoS markings for /32 
prefixes but rather to make the class set and class encodings on different 
layers seen to all ASes (not only neighbouring ones).
Those QoS Marking Attribute (one per class and layer) would now been 
associated with the possibly long list of NLRI IP prefixes of different 
sizes.

If a traffic source now wants to send ftp traffic and voice traffic to one 
of these prefixes, the sending AS could now see which class set will be 
supported by the targeted AS and which encoding the next hop neighbour AS 
will be using for this class.
So, the assumption of having all traffic now beeing marked as voice is not 
true. The sending AS is free to choose its marking as it is today. But it 
can now make an informed decision on how to possibly remark its own DSCP 
at the egress to fit best the available class set along the forwarding 
chain.
If neighbouring ASes support equal class encodings (which they are now 
informed about by means of the attribute), the neighbour's incress layer 4 
or higher layer classification can even become redundant with this new 
approach.

As far as previous QoS attribute contributions are concerned, I have found 
some drafts, which specified certain delay, bandwidth etc. parameters 
within the attributes, but I did not find a draft, which mentioned to 
convey the QoS marking for different technologies.
So I take your advice, that I should have mentioned those drafts in order 
to make clear, that my approach is not about QoS parameter signalling but 
rather about QoS marking signalling.

I hope this resolves some concerns and I thank you again for your fast 
feedback.

Regards,
Thomas


On Mon, 9 Jun 2008, Robert Raszuk wrote:

> Hi Thomas,
>
> I would like to clarify one point this draft is suggesting ...
>
> If I understand it correctly it proposes to propagate QoS marking within BGP 
> across domain boundaries. The least granularity I could see this used with is 
> /32 (mostly unroutable in the internet). But even that .. even if this is to 
> work only across two peering ASes which allow to send to each other number of 
> /32s it assumes that this entire destination uses the same QoS marking. So if 
> this is a server with voice, video and httpd running everything to it would 
> use voice qos marking. IMHO this is already non starter.
>
> Now section 3.3 goes even further ... if we are sending an aggregate in BGP 
> (/24 /20 /16 etc ...) and if even a single member of an aggregate uses qos 
> marking (for example for voice) all packets going this entire aggregate 
> should be marked as voice ? I think this would be a mistake.
>
> Marking is usually done on packet content inspection on ingress (up to 
> application layer) and not on it's destination.
>
> IMHO BGP is too course to carry qos marking in the single SAFI. Note that 
> some time back there was an attempt to make context address family to allow 
> to achieve very similar goal to yours but at more controllable and granular 
> fashion. That included the ability to send those separate classes of traffic 
> via different next hops and map them to different forwarding paradigms in 
> peering ASes (one could use TE-LSPs, one MTR etc.). Your proposal does not 
> have any reference to it.
>
> Thx,
> R.
>
>
>> Dear WG members,
>> 
>> a new draft has been uploaded, which suggests the definition of a new 
>> extended community attribute for QoS marking.
>> It is available at 
>> http://tools.ietf.org/html/draft-knoll-idr-qos-attribute-00 and I would 
>> kindly ask you for comments to it.
>> I would like the IDR to consider the proposed mechanism for further study 
>> within the WG.
>> 
>> Regards,
>> Thomas M. Knoll
>> 
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>> 
>
>
>
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr