--- 1/draft-ietf-tsvwg-ieee-802-11-10.txt	2017-12-18 10:13:24.702997259 -0800
+++ 2/draft-ietf-tsvwg-ieee-802-11-11.txt	2017-12-18 10:13:24.778999048 -0800
@@ -1,19 +1,19 @@
 
 Transport Working Group                                       T. Szigeti
 Internet-Draft                                                  J. Henry
 Intended status: Best Current Practice                     Cisco Systems
-Expires: June 18, 2018                                          F. Baker
-                                                       December 15, 2017
+Expires: June 21, 2018                                          F. Baker
+                                                       December 18, 2017
 
                     Diffserv to IEEE 802.11 Mapping
-                    draft-ietf-tsvwg-ieee-802-11-10
+                    draft-ietf-tsvwg-ieee-802-11-11
 
 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 document specifies a set of Differentiated
    Services Code Point (DSCP) to IEEE 802.11 User Priority (UP) mappings
    to reconcile the marking recommendations offered by the IETF and the
    IEEE so as to maintain consistent QoS treatment between wired and
@@ -27,21 +27,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on June 18, 2018.
+   This Internet-Draft will expire on June 21, 2018.
 
 Copyright Notice
 
    Copyright (c) 2017 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -899,22 +899,22 @@
 
    The Low-Priority Data service class serves applications that the user
    is willing to accept without service assurances.  This service class
    is specified in [RFC3662] and [I-D.ietf-tsvwg-le-phb].
 
    [RFC3662] and [RFC4594] both recommend Low-Priority Data be marked
    CS1 DSCP.
 
    Note: This marking recommendation may change in the future, as
    [I-D.ietf-tsvwg-le-phb] defines a Lower Effort (LE) per-hop behavior
-   (PHB) and states: "The RECOMMENDED codepoint for the LE PHB is
-   '000010'.
+   (PHB) for Low-Priority Data traffic and recommends an additional DSCP
+   for this traffic.
 
    The Low-Priority Data service class loosely corresponds to the
    [IEEE.802.11-2016] Background Access Category (AC_BK) and therefore
    it is RECOMMENDED to map Low-Priority Data traffic marked CS1 DSCP to
    UP 1, thereby admitting it to the Background Access Category (AC_BK).
    This happens to correspond to the default mapping (as described in
    Section 2.3).
 
 4.3.  DSCP-to-UP Mapping Recommendations Summary