[tsvwg] DSCP and 802.1Q prioirty
"Pat (Patricia) Thaler" <pthaler@broadcom.com> Fri, 06 November 2015 02:15 UTC
Return-Path: <pthaler@broadcom.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 3631E1A8766
for <tsvwg@ietfa.amsl.com>; Thu, 5 Nov 2015 18:15:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3,
T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id VkZKbXBKSN15 for <tsvwg@ietfa.amsl.com>;
Thu, 5 Nov 2015 18:15:47 -0800 (PST)
Received: from mail-gw1-out.broadcom.com (mail-gw1-out.broadcom.com
[216.31.210.62])
by ietfa.amsl.com (Postfix) with ESMTP id 43FB11A8749
for <tsvwg@ietf.org>; Thu, 5 Nov 2015 18:15:47 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,250,1444719600"; d="scan'208,217";
a="79907364"
Received: from irvexchcas08.broadcom.com (HELO
IRVEXCHCAS08.corp.ad.broadcom.com) ([10.9.208.57])
by mail-gw1-out.broadcom.com with ESMTP; 05 Nov 2015 20:20:00 -0800
Received: from SJEXCHCAS05.corp.ad.broadcom.com (10.16.203.12) by
IRVEXCHCAS08.corp.ad.broadcom.com (10.9.208.57) with Microsoft SMTP Server
(TLS) id 14.3.235.1; Thu, 5 Nov 2015 18:15:46 -0800
Received: from SJEXCHMB09.corp.ad.broadcom.com ([fe80::3da7:665e:cc78:181f])
by SJEXCHCAS05.corp.ad.broadcom.com ([::1]) with mapi id 14.03.0235.001; Thu,
5 Nov 2015 18:15:46 -0800
From: "Pat (Patricia) Thaler" <pthaler@broadcom.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: DSCP and 802.1Q prioirty
Thread-Index: AdEYNah/MZAMNBr+TyipiPLqSNnIBw==
Date: Fri, 6 Nov 2015 02:15:45 +0000
Message-ID: <EB9B93801780FD4CA165E0FBCB3C3E672B42BED9@SJEXCHMB09.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.16.203.100]
Content-Type: multipart/alternative;
boundary="_000_EB9B93801780FD4CA165E0FBCB3C3E672B42BED9SJEXCHMB09corpa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/w1H3Q-hpU96G6RfpNXjVoGzmVCQ>
Subject: [tsvwg] DSCP and 802.1Q prioirty
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>,
<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>,
<mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2015 02:15:49 -0000
After the discussion on DSCP mapping to IEEE 802.1Q priority yesterday, I realized that there is something that I should have mentioned. In IEEE 802.1Qcd, we added the ability to use the Application Priority TLV (an LLDP TLV defined originally in IEEE 802.1Qaz for Data Center Networking Configuration Exchange, DCBX) to indicate mapping from DSCP to 802.1Q Priority. DCBX was created partly because bridges/switches are often configured by network administration but end nodes often aren't so this gives a way for the end node to get the information on how the priorities are used when it attaches to the network. This TLV would be something to mention if there is an RFC developed on relationship between DSCP and 802.1Q prioiries. Regards, Pat
- [tsvwg] DSCP and 802.1Q prioirty Pat (Patricia) Thaler