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

["Tim Szigeti (szigeti)" <[e-mail]>]

Yes - RFC 4594 recommends DNS to be serviced with DF; our draft takes RFC 4594 recommendations as a given / starting point.

-tim

-----Original Message-----
From: Fred Baker (fred) 
Sent: Tuesday, March 29, 2016 10:07 AM
To: Agarwal, Anil
Cc: Tim Szigeti (szigeti); [e-mail]
Subject: Re: [tsvwg] New Version Notification for draft-szigeti-tsvwg-ieee-802-11-01.txt


> On Mar 29, 2016, at 9:53 AM, Agarwal, Anil <[e-mail]> 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:[e-mail]] On Behalf Of Tim Szigeti 
> (szigeti)
> Sent: Monday, March 28, 2016 6:38 PM
> To: [e-mail]
> 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_ht
> ml_draft-2Dszigeti-2Dtsvwg-2Dieee-2D802-2D11-2D00&d=BQIFAg&c=jcv3orpCs
> v7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=FyvaklKYrHaSCPjbBTdviWIW9uSbnxdNS
> heSGz1Jvq4&m=Clq-IzF9qeDd5yZLQyA8KmtL4psfk3_WDpx1oJbmVCE&s=9ZLvTSIJ7vV
> iNIjFwJVUcu_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: [e-mail] [mailto:[e-mail]]
> Sent: Wednesday, March 23, 2016 8:36 AM
> To: Fred Baker (fred)
> Cc: [e-mail]; 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)" <[e-mail]>
>>> 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: "[e-mail]" <[e-mail]>
>>> 
>>>> From: <[e-mail]>
>>>> 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 <[e-mail]>, Tim Szigeti <[e-mail]>
>>>> 
>>>> 
>>>> 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_i
>>>> nternet-2Ddrafts_draft-2Dszigeti-2Dtsvwg-2Dieee-2D802-2D11&d=BQIFAg
>>>> &c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=FyvaklKYrHaSCPjbBT
>>>> dviWIW9uSbnxdNSheSGz1Jvq4&m=Clq-IzF9qeDd5yZLQyA8KmtL4psfk3_WDpx1oJb
>>>> mVCE&s=yUc8E8p6BcX9BI1TLhtlw_6ayIYCvbL5dEcOz1wukdI&e=
>>>> -01.txt
>>>> Status:
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ie
>>>> tf.org_doc_draft-2Dszigeti-2Dtsvwg-2Dieee-2D802-2D11_&d=BQIFAg&c=jc
>>>> v3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=FyvaklKYrHaSCPjbBTdviWI
>>>> W9uSbnxdNSheSGz1Jvq4&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=jcv
>>>> 3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=FyvaklKYrHaSCPjbBTdviWIW
>>>> 9uSbnxdNSheSGz1Jvq4&m=Clq-IzF9qeDd5yZLQyA8KmtL4psfk3_WDpx1oJbmVCE&s
>>>> =hCedeeOVDF6-XVyszl1t24DJUhtReOAIS0boFU81WAY&e=
>>>> Diff:
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_r
>>>> fcdiff-3Furl2-3Ddraft-2Dszigeti-2Dtsvwg-2Dieee-2D802-2D11-2D01&d=BQ
>>>> IFAg&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=FyvaklKYrHaSCP
>>>> jbBTdviWIW9uSbnxdNSheSGz1Jvq4&m=Clq-IzF9qeDd5yZLQyA8KmtL4psfk3_WDpx
>>>> 1oJbmVCE&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
>>>> 
>>> 
>> 
>> 
>