Re: [tsvwg] New Version Notification for draft-szigeti-tsvwg-ieee-802-11-01.txt

"Fred Baker (fred)" <fred@cisco.com> Tue, 29 March 2016 17:18 UTC

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 A75D412DAAD for <tsvwg@ietfa.amsl.com>; Tue, 29 Mar 2016 10:18:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.531
X-Spam-Level:
X-Spam-Status: No, score=-114.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 4_GH4yMUtIum for <tsvwg@ietfa.amsl.com>; Tue, 29 Mar 2016 10:18:50 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4592912DAA2 for <tsvwg@ietf.org>; Tue, 29 Mar 2016 10:06:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7681; q=dns/txt; s=iport; t=1459271217; x=1460480817; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=i4CFhyl8rfU3KsuDDLwSsMuqmZxpHBQ1uG2DrXphSvk=; b=ENTCAAgN42axN0tjg36/cQv+F/H75135EvVda12C554dUEb0AB0gIb7D LomFS29+Sdl+SS7V0AWy+ZaP+P0y1Omwn1cTHIeJUBx7qtViOmARrd8Pg gL0uG6da5WGiRQFwMeL4wNrEMuql2OxaLX/969OzzuWU4CQfez4CjdO2h Q=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DVAgDJtfpW/5FdJa1dgy5TfQa6eA6BcBmFdAKBNTgUAQEBAQEBAWQnhEEBAQEDASdQAgUHBAIBCBEDAQEBAScHMhQJCAIEDgUODYgECMBBAQEBAQEBAQEBAQEBAQEBAQEBAQEBDQiIEIJRhEMaHoJtgisFjUSKKAGDHoFmbYgVgWZOg3+DKIUyjw4BHgFDg2Vsh0F+AQEB
X-IronPort-AV: E=Sophos;i="5.24,411,1454976000"; d="asc'?scan'208";a="255038085"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Mar 2016 17:06:56 +0000
Received: from XCH-ALN-010.cisco.com (xch-aln-010.cisco.com [173.36.7.20]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u2TH6tlu020785 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 29 Mar 2016 17:06:55 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-ALN-010.cisco.com (173.36.7.20) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 29 Mar 2016 12:06:55 -0500
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Tue, 29 Mar 2016 12:06:55 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "Agarwal, Anil" <Anil.Agarwal@viasat.com>
Thread-Topic: [tsvwg] New Version Notification for draft-szigeti-tsvwg-ieee-802-11-01.txt
Thread-Index: AQHRid1l3fMYirOS2kKHw1Ly3WZTqA==
Date: Tue, 29 Mar 2016 17:06:55 +0000
Message-ID: <2DF38F7F-E818-4EC8-960B-228B1D0F8F02@cisco.com>
References: <3359B326-B826-4B18-9DAA-D0E44CE816B4@cisco.com> <A3F25E9C-3FB5-450F-9331-1CE93D4720B5@cisco.com> <feda8cc39fb0edc0f328f4b680370f49.squirrel@erg.abdn.ac.uk> <aa4e7d4f47c84a578fa790cd55c4930d@XCH-RCD-010.cisco.com> <7A2801D5E40DD64A85E38DF22117852CD0963F75@wdc1exchmbxp01.hq.corp.viasat.com>
In-Reply-To: <7A2801D5E40DD64A85E38DF22117852CD0963F75@wdc1exchmbxp01.hq.corp.viasat.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.64.123]
Content-Type: multipart/signed; boundary="Apple-Mail=_84FFCE1D-200F-46BC-90B5-B1284ABECE05"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/APbfvY_3eBstFr8MkTZzNLIyUYI>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for draft-szigeti-tsvwg-ieee-802-11-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 29 Mar 2016 17:18:56 -0000

> On Mar 29, 2016, at 9:53 AM, Agarwal, Anil <Anil.Agarwal@viasat.com> wrote:
> 
> I wonder why we have not found a reason to use a non-zero DSCP value for DNS packets.
> This draft does not mention DNS.
> RFC 4594 suggests using DSCP = DF = 0.
> 
> Anil

Have we demonstrated a requirement for DNS to use a non-default service? I'm unaware of one...

> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Tim Szigeti (szigeti)
> Sent: Monday, March 28, 2016 6:38 PM
> To: tsvwg@ietf.org
> Subject: [tsvwg] FW: Fwd: New Version Notification for draft-szigeti-tsvwg-ieee-802-11-01.txt
> 
> Hi TSVWG,
> 
> As the majority of clients connecting to IP networks are doing so via WLANs, and since IEEE recommendations for QoS do not align with IETF recommendations, it would be highly beneficial to have an IETF-endorsed reconciliation between IETF IP QoS and IEEE WMM QoS, which is the intent of draft-szigeti-tsvwg-ieee-802-11.
> 
> Apple, Cisco and other vendors are all planning on developing solutions in the coming months based on a consistent IETF-ratified set of QoS mappings. If you have stake/opinion/feedback in making sure that QoS is handled correctly at wired/wireless edges, then please read the draft and help us pass this through.
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dszigeti-2Dtsvwg-2Dieee-2D802-2D11-2D00&d=BQIFAg&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=FyvaklKYrHaSCPjbBTdviWIW9uSbnxdNSheSGz1Jvq4&m=Clq-IzF9qeDd5yZLQyA8KmtL4psfk3_WDpx1oJbmVCE&s=9ZLvTSIJ7vViNIjFwJVUcu_rkMgQAETtdd9_L7tyEeo&e=
> 
> [Otherwise, the only guidance in this area is based on non-IETF recommendations (e.g. GSMA <--> WMM)]
> 
> Thanks in advance.
> 
> -tim
> 
> 
> 
> -----Original Message-----
> From: gorry@erg.abdn.ac.uk [mailto:gorry@erg.abdn.ac.uk]
> Sent: Wednesday, March 23, 2016 8:36 AM
> To: Fred Baker (fred)
> Cc: tsvwg-chairs@tools.ietf.org; Tim Szigeti (szigeti)
> Subject: Re: Fwd: [tsvwg] New Version Notification for draft-szigeti-tsvwg-ieee-802-11-01.txt
> 
> 
> True. This will appear on the draft agenda. We will need to get some people sufficiently excited to allocate some cycles to read and continue to comment on the draft.
> 
> I'm assuming you'll ask for adoption (which seems reasonable). At which point I'll ask who has read or plans to read this? Let's hope the room is not deadly quiet. We'll move on from there.
> 
> gorry
> 
>> I haven't heard anything from  you...
>> 
>> Please consider this a request for an agenda slot.
>> 
>>> Begin forwarded message:
>>> 
>>> From: "Fred Baker (fred)" <fred@cisco.com>
>>> Subject: [tsvwg] Fwd: New Version Notification for
>>> draft-szigeti-tsvwg-ieee-802-11-01.txt
>>> Date: March 15, 2016 at 12:02:20 PM PDT
>>> To: "tsvwg@ietf.org" <tsvwg@ietf.org>
>>> 
>>>> From: <internet-drafts@ietf.org>
>>>> Subject: New Version Notification for
>>>> draft-szigeti-tsvwg-ieee-802-11-01.txt
>>>> Date: March 15, 2016 at 11:28:58 AM PDT
>>>> To: Fred Baker <fred@cisco.com>, Tim Szigeti <szigeti@cisco.com>
>>>> 
>>>> 
>>>> A new version of I-D, draft-szigeti-tsvwg-ieee-802-11-01.txt
>>>> has been successfully submitted by Fred Baker and posted to the IETF
>>>> repository.
>>>> 
>>>> Name:		draft-szigeti-tsvwg-ieee-802-11
>>>> Revision:	01
>>>> Title:		Guidelines for DiffServ to IEEE 802.11 Mapping
>>>> Document date:	2016-03-14
>>>> Group:		Individual Submission
>>>> Pages:		27
>>>> URL:
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_internet-2Ddrafts_draft-2Dszigeti-2Dtsvwg-2Dieee-2D802-2D11&d=BQIFAg&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=FyvaklKYrHaSCPjbBTdviWIW9uSbnxdNSheSGz1Jvq4&m=Clq-IzF9qeDd5yZLQyA8KmtL4psfk3_WDpx1oJbmVCE&s=yUc8E8p6BcX9BI1TLhtlw_6ayIYCvbL5dEcOz1wukdI&e=
>>>> -01.txt
>>>> Status:
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dszigeti-2Dtsvwg-2Dieee-2D802-2D11_&d=BQIFAg&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=FyvaklKYrHaSCPjbBTdviWIW9uSbnxdNSheSGz1Jvq4&m=Clq-IzF9qeDd5yZLQyA8KmtL4psfk3_WDpx1oJbmVCE&s=gPewTn7qnPI4-4fppKtA4ZS_Ofmx06hVJOtMl4-bp3o&e=
>>>> Htmlized:
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dszigeti-2Dtsvwg-2Dieee-2D802-2D11-2D01&d=BQIFAg&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=FyvaklKYrHaSCPjbBTdviWIW9uSbnxdNSheSGz1Jvq4&m=Clq-IzF9qeDd5yZLQyA8KmtL4psfk3_WDpx1oJbmVCE&s=hCedeeOVDF6-XVyszl1t24DJUhtReOAIS0boFU81WAY&e=
>>>> Diff:
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dszigeti-2Dtsvwg-2Dieee-2D802-2D11-2D01&d=BQIFAg&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=FyvaklKYrHaSCPjbBTdviWIW9uSbnxdNSheSGz1Jvq4&m=Clq-IzF9qeDd5yZLQyA8KmtL4psfk3_WDpx1oJbmVCE&s=4E_ZaOCzjpImcajsVRJ32Z82lJnJ0iO5NpRsBJMspLo&e=
>>>> 
>>>> Abstract:
>>>> As internet traffic is increasingly sourced-from and destined-to
>>>> wireless endpoints, it is crucial that Quality of Service be aligned
>>>> between wired and wireless networks; however, this is not always the
>>>> case by default.  This is due to the fact that two independent
>>>> standards bodies provide QoS guidance on wired and wireless networks:
>>>> specifically, the IETF specifies standards and design
>>>> recommendations  for wired IP networks, while a separate and
>>>> autonomous standards-  body, the IEEE, administers the standards for
>>>> wireless 802.11  networks.  The purpose of this document is to
>>>> propose a set  Differentiated Services Code Point (DSCP) to IEEE
>>>> 802.11 User  Priority (UP) mappings to reconcile the marking
>>>> recommendations  offered by these two standards bodies, and, as
>>>> such, to optimize  wired-and-wireless interconnect QoS.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> Please note that it may take a couple of minutes from the time of
>>>> submission until the htmlized version and diff are available at
>>>> tools.ietf.org.
>>>> 
>>>> The IETF Secretariat
>>>> 
>>> 
>> 
>> 
>