Re: [nvo3] I-D Action: draft-xia-nvo3-vxlan-qosmarking-01.txt

Behcet Sarikaya <sarikaya2012@gmail.com> Tue, 11 November 2014 03:47 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24BD01AD52A for <nvo3@ietfa.amsl.com>; Mon, 10 Nov 2014 19:47:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P6GVsuOWvbVh for <nvo3@ietfa.amsl.com>; Mon, 10 Nov 2014 19:47:34 -0800 (PST)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A321D1AD519 for <nvo3@ietf.org>; Mon, 10 Nov 2014 19:47:34 -0800 (PST)
Received: by mail-yh0-f53.google.com with SMTP id a41so2933653yho.12 for <nvo3@ietf.org>; Mon, 10 Nov 2014 19:47:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ie+Xn3XG3kSOhpd/zJcG3bmHgHuZqQKV9bosSle6/Xs=; b=h7dbOSwoiU0mJvw7oMX376I/pv0+RFCmAauUnou2hBhXoW1VeL2IMHxCOUXnMwOFw6 rRbcMcnTbyifj4eI/TgDLgeom5patTVeZSQjFaGtCgHlRyxTor1zN2tUfBF/xo2UnnAm udO4q0F0JXylr2FHb83CJXmvf8zRYEyQkeGMRJRT2opTbPW8huJy8MeS32+lJclw0VHp c/mGGFohypJGYwF5DOoxeeQMho4owya4NBFN8P5BaLpwwiTxf0QjkZEsetL4gHuLbdYn mWOD9xiCp06kdZQdPgMqdTHd4aIkjuHJeW7aoDewj2mvg9S3NAVUEsNbcbHfj3u4nkNY WcdA==
MIME-Version: 1.0
X-Received: by 10.236.229.165 with SMTP id h35mr33575149yhq.129.1415677653959; Mon, 10 Nov 2014 19:47:33 -0800 (PST)
Received: by 10.170.71.198 with HTTP; Mon, 10 Nov 2014 19:47:33 -0800 (PST)
In-Reply-To: <5461854F.3020305@gmail.com>
References: <20141110200919.27869.2915.idtracker@ietfa.amsl.com> <5461854F.3020305@gmail.com>
Date: Mon, 10 Nov 2014 21:47:33 -0600
Message-ID: <CAC8QAce9kWVp_3+MeMcNpFinhnTcCgk0k1eDtip2j47iCWAbpg@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/nvo3/31JsEDYz7HDSbQ_2Mti5gY-f05c
Cc: David Black <david.black@emc.com>, "nvo3@ietf.org" <nvo3@ietf.org>, draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org
Subject: Re: [nvo3] I-D Action: draft-xia-nvo3-vxlan-qosmarking-01.txt
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Nov 2014 03:47:36 -0000

On Mon, Nov 10, 2014 at 9:41 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> [resend with corrected address, sorry]
>
> Hi,
>
>>  The first three bits (bits 5-7) are precedence bits. They are
>>  assigned according to [RFC0791]. Precedence values '110' and '111'
>>  are selected for routing traffic.
>>
>>  The last three bits (bits 8-10) are class selector bits. Thet are
>>  assigned as follows:
>>
>> 001 - BK or background traffic
> ...
>> As can be seen the markings are the same as in IEEE 802.1p...
>
> This is not in any way compatible with RFC 2474, which also made the
> relevant part of RFC 791 obsolete.
>
> If you want to be compatible with RFC 2474 you should not specify the
> bits at all - just say that they are exactly as defined in RFC 2474
> and the various PHB definitions that have been published.

I think that diffserv is less relevant in the context of VXLAN.

>  If you
> want to be compatible with IEEE 802.1p that is a different matter,

Yes this is more relevant for VXLAN.

> but you cannot mix the two up in this way.

I now understand that we confused the two very different things.

Regards,

Behcet
>
>     Brian
>
>
>