Re: [tsvwg] AD Evaluation comments for draft-ietf-tsvwg-ieee-802-11-07

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 13 September 2017 16:42 UTC

Return-Path: <spencerdawkins.ietf@gmail.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 A84351326FE; Wed, 13 Sep 2017 09:42:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_WP_DIRINDEX=1] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 8onHstD_VArN; Wed, 13 Sep 2017 09:42:45 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B487313305E; Wed, 13 Sep 2017 09:42:45 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id v72so1793198ywa.3; Wed, 13 Sep 2017 09:42:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vNGZugPvMnf/rqcRhJLpdJRerOLjoyz53wqtOgGWLwU=; b=Ni3bcXWwcl6/mPW/B8VwrbqZPw2nOs4g0HBaA/tYB10kZU4PpXxn5bGoIYpja17dsO 4mSzUWF3JoD8RW7bovi+NOYGHsWZjNdvvFELMp9KaBle33P+RXMTcQKrLy+4zUuIUbMA fFVdQjZ2+fIm5mb9BZXFUgRL44Qq/pAyK3SKQ1xSViaaKPCF0Hk48g8IJWAPR6+2d2zR 0nYlZWYRCPaMZLNo7nZLCs63MuScilZD2/k0lRVZf+UtpEMTvNIlowyKQJk8zJK2r4u2 m7usQXRxQ7F+9qHW2l6jlTeAhJ7VbtXgme1bhbbV0kke+Q+BeDZkOP4aFu0Wu65kEtv6 x2VA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vNGZugPvMnf/rqcRhJLpdJRerOLjoyz53wqtOgGWLwU=; b=pcc47g0nzRPocYP/CXWHBncdCnSogVr6zKpwuYzLLWTwWt0kVwNgBKodR0ahAMgZEN Mu0AIeyXyU6VM9BoZNKhUzcZTD9TmcVUI/5bP0k9/BzQEYoyVUvJzYwVoDsjgb2ctIvF um0NH3EE2aRTIkegQbJBGsVGxBB95d/7MloELVw9jj1Ek9xDN3fPRaYSPj5RxOR0nwDY uwc+XpZE7Q1TSOURPMGe5A3WI20bAAqUlrN6RWtU2fO0iKLIUI2NBqIb2oMImF/cBL2h pdmiJvTmroaCO0d4JjTlKJ0OBG4UKegsSXco5MbWztgVx/eYjh2u63jLKEjuH6E9j0ur 6jzA==
X-Gm-Message-State: AHPjjUjyrRbJ+5c0mqQd93AqtypFmQXbIyqpgvv4mztlUXSrshqft1/1 qqCEQMcewmzgJ9SKgzvxJ8eab1qgk1HuNKOaW6o=
X-Google-Smtp-Source: ADKCNb7Xx2pc7LKwzxoyir4jGv0u2VxN1T3Pca69dwZKkTtmKxZPep90J8P8bc7kw0h+i5jMlM/KjeFw0BSKZ/3dw08=
X-Received: by 10.129.167.67 with SMTP id e64mr9114563ywh.85.1505320964653; Wed, 13 Sep 2017 09:42:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.2.15 with HTTP; Wed, 13 Sep 2017 09:42:44 -0700 (PDT)
In-Reply-To: <D33894F3-8C87-4B3A-AC0C-6D1A48EED13D@gmail.com>
References: <CAKKJt-dnnYxO0C9ahXURu8aDjpRP=vtKn8z2JsiRm+YP+mLrVw@mail.gmail.com> <D33894F3-8C87-4B3A-AC0C-6D1A48EED13D@gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 13 Sep 2017 11:42:44 -0500
Message-ID: <CAKKJt-cq0GJGeeeJ7_YtMrgT8g2aVsWhTzwvSoFsEhwFDZ48pQ@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: David Black <david.black@dell.com>, "David L. Black" <david.black@emc.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, draft-ietf-tsvwg-ieee-802-11@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c146c7e5f0940055914d92c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/wHrweEcuNZyRJI_cbctOUjBMMus>
Subject: Re: [tsvwg] AD Evaluation comments for draft-ietf-tsvwg-ieee-802-11-07
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 13 Sep 2017 16:42:48 -0000

Hi, Fred,

On Tue, Sep 12, 2017 at 11:42 PM, Fred Baker <fredbaker.ietf@gmail.com>
wrote:

> On Sep 12, 2017, at 7:55 PM, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
> >
> > I'm looking at this text,
> >
> >    There is also a recommendation from the Global System for Mobile
> >    Communications Association (GSMA), specifically their Mapping Quality
> >    of Service (QoS) Procedures of Proxy Mobile IPv6 (PMIPv6) and WLAN
> >    [RFC7561] specification.  This GSMA specification was developed
> >    without reference to existing IETF specifications for various
> >    services, referenced in Section 1.1.
> >
> > and I'm not quite sure how an IETF-stream Informational RFC produced by
> a working group becomes "a recommendation from GSMA" and "a GSMA
> specification". I recognize the names of the RFC 7561 authors, and I see
> the connection, but I would have thought that the reference would have been
> to something more obviously tied to GSMA. Is there any reference that could
> be cited, to help people who didn't sit two desks away from one of the
> authors see the connection?
>
> You might take a look at RFC 7561 section 4.2 and reference [6]. It says
> that it mandates GSMA-specified DSCP mappings.


Thanks for the feedback. I'm actually asking a stupider question than you
think.

I saw the reference to [6] in RFC 7561, but I was scanning for "GSMA", and
the only occurrence to that string that I saw was in the Informative
References section.

   [6]  3GPP, "Guidelines for IPX Provider networks (Previously
        Inter-Service Provider IP Backbone Guidelines)", GSMA Official
        Document IR.34 v11.0, November 2014,
        <http://www.gsma.com/newsroom/wp-content/uploads/
        IR.34-v11.0.pdf>.

If a reader is persistent enough to click through the references in an RFC
that's listed as a reference, the reader can figure this out, but it isn't
obvious.

So I think I'm asking if you can add [6] as a reference in your draft,
perhaps pointing to

   There is also a recommendation from the Global System for Mobile
   Communications Association (GSMA),

You'll know best where to point it, of course, but I'd like to point to the
actual GSMA recommendation if we're going to say

   This GSMA specification was developed
    without reference to existing IETF specifications for various
    services, referenced in Section 1.1.

which seemed to refer back to *RFC 7561* as the GSMA recommendation, which
is what confused me in the first place :-)

Spencer, who is noting with bemusement that neither TSV AD balloted on RFC
7561 when it was approved ... how did we miss THAT one???