Re: [paws] Ted Lemon's Discuss on draft-ietf-paws-protocol-14: (with DISCUSS and COMMENT)

Vincent Chen <vchen@google.com> Fri, 22 August 2014 07:04 UTC

Return-Path: <vchen@google.com>
X-Original-To: paws@ietfa.amsl.com
Delivered-To: paws@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2F271A00ED for <paws@ietfa.amsl.com>; Fri, 22 Aug 2014 00:04:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level:
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] 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 Zqr7l-zyvZow for <paws@ietfa.amsl.com>; Fri, 22 Aug 2014 00:04:00 -0700 (PDT)
Received: from mail-vc0-x229.google.com (mail-vc0-x229.google.com [IPv6:2607:f8b0:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F8DA1A00EC for <paws@ietf.org>; Fri, 22 Aug 2014 00:03:59 -0700 (PDT)
Received: by mail-vc0-f169.google.com with SMTP id le20so11985550vcb.14 for <paws@ietf.org>; Fri, 22 Aug 2014 00:03:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SCRY1LEK3YgsQ5JTVPnyttKzbxvyU6TIxnLEMCiPmfc=; b=bmL8Qf7FwUQiQ7p06tetYA74gjy73Q3wX3O+csvRiWDz28T8MQhDt+3YNAZcKHrcFb Q0B2Ke8jqQ+uw5D+3t6j+wpOue8kFC0XW+jgUAG3Q9Lqe14sE1SihaPyMiBABT3UNBOR WtAMPqQnV4VlOeevzU3TUpvcTrqucZ3AJshyNSm3we4IV2zTlCDaW+tnG7NgQscpCq22 t4rPZ7ALVN64Tay0lpilwjvBj0Gg0Qd5tZhH94ZtAI8Jc6ja3agUs9C4ZBVk7awLB96R XfQkg16s7Tpu52GCk54GmrA5M0gEWh9Yi4hH2chWp5a+e2p1SPr2BhTgftJKINqelXiy yfTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=SCRY1LEK3YgsQ5JTVPnyttKzbxvyU6TIxnLEMCiPmfc=; b=imSdAlSsgvh8eF2AeHwqwSqgy6DU6wZQGunbJPIREXse8EIGh+59h2kAphV4iWw1xo 3cI3azEigSyCbOpfZEgieVkdBT9F4EtiG2SkcZM8dcRGFK5/LB18dCd9kMPckwshSASQ 0o/zdiHrdrMKYYczz/dWxE26AwWpZW9yeuNR3PNU+c2RAgC4LKXsuCxJ1o1T9RorEfsJ OtEQd3HoVlTjPtf/Q/RJVJajyicvdalYgNq6QKN8bPl4AParjHAYrHPtGpijIGB8e3uK 4DhVLbW5kFfdFFqeGwAwN+IQAfD+Rlxb8RjizpFoVixA3sspC1Y4GNBNQC4QA3WlzwBB hWNw==
X-Gm-Message-State: ALoCoQlvL3hvzbdd5jf787xWMGAoK3nESErgkXFun5SxaD8aaX81JzRrppA9aJpb1Ll4w/1Cb2UH
MIME-Version: 1.0
X-Received: by 10.52.69.172 with SMTP id f12mr469131vdu.9.1408691038412; Fri, 22 Aug 2014 00:03:58 -0700 (PDT)
Received: by 10.52.177.226 with HTTP; Fri, 22 Aug 2014 00:03:58 -0700 (PDT)
In-Reply-To: <8E8E5E78-4755-4889-8B8A-B804D30155C9@nominum.com>
References: <20140821133025.17118.4987.idtracker@ietfa.amsl.com> <CABEV9RMX6DPBCmao5owW3ajrNchnWCzRPR2=PCVU=1WYSMdxYg@mail.gmail.com> <8E8E5E78-4755-4889-8B8A-B804D30155C9@nominum.com>
Date: Fri, 22 Aug 2014 00:03:58 -0700
Message-ID: <CABEV9ROXdJnhY1M-NcAJeHyRQx+N08ZDXFKFRzTPcGuCN3gF0Q@mail.gmail.com>
From: Vincent Chen <vchen@google.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=20cf307cffd6f1887b05013270f8
Archived-At: http://mailarchive.ietf.org/arch/msg/paws/m_y67iyHXOFwsggSXKHi_I_sLg0
Cc: "paws@ietf.org" <paws@ietf.org>, "paws-chairs@tools.ietf.org" <paws-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-paws-protocol@tools.ietf.org
Subject: Re: [paws] Ted Lemon's Discuss on draft-ietf-paws-protocol-14: (with DISCUSS and COMMENT)
X-BeenThere: paws@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Protocol to Access White Space database \(PAWS\)" <paws.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/paws>, <mailto:paws-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/paws/>
List-Post: <mailto:paws@ietf.org>
List-Help: <mailto:paws-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/paws>, <mailto:paws-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Aug 2014 07:04:04 -0000

On Thu, Aug 21, 2014 at 6:06 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Aug 21, 2014, at 8:30 PM, Vincent Chen <vchen@google.com> wrote:
> >> 4.1 says "Some regulatory domains may have specific rules regarding how
> >> long the spectrum data remains valid in these cases."   It might be
> worth
> >> adding that in such cases the initialization procedure is required.
> >> This is addressed to some extent in section 4.3, but I'm not sure it's
> >> completely addressed.   The potential problem I see is that a device
> >> might be used in a regulatory regime where this is required, but might
> >> have pre-configured values for some other regulatory regime.   If these
> >> values are not valid in the regime that applies for its current
> location,
> >> it might have a too-long refresh interval configured, fail to detect
> that
> >> this is the case, and as a result accidentally break the law.   Can a
> >> scenario like this occur in practice?
> >
> > It should not occur in practice for well-behaved devices.
> >
> > When it is preconfigured, there must be a preconfigured value for each
> ruleset.
> > Of course, a device may choose to use preconfigured values for only a
> subset
> > of the rulesets it supports.
> >
> > Note that, in practice, a device needs to be certified for each
> "ruleset" by
> > whatever process is defined by each applicable regulatory body, so that
> > any preconfigured values will be certified to be compliant.
>
> If this is how it works, shouldn't the document say so?   Or was that in
> the requirements document?   I admit it's been a while since I read it. :)
>

I'll clarify the text some. Note, however, that INIT_RESP return these
values
as part of a RulesetInfo structure, so that it is implied that
preconfiguration also
must be on a per-ruleset basis.


>
> > In 4.4.2, I think that if none of the rulesets are accepted, the intent
> > is that the database should return a REGISTRATION_RESP with the error
> > element, and will not return a rulesetInfos list.   However, the
> > specification does not make an exception for this case when it says "A
> > RulesetInfo list MUST be included" and  "The list MUST contain at least
> > one entry".   I can't think of another valid interpretation, but you've
> > stated a MUST, so you need to say that it doesn't apply in the case of
> > the error.
> >
> > Ah, right. There is language from INIT_RESP that needs to be repeated
> here.
> >
> >        If the Database does not support the device or any of the rulesets
> >       specified in the DeviceDescriptor, it MUST instead return an error
> >       with the UNSUPPORTED (Table 1) code in the error response.
>
> That doesn't fix it, though—you need to fix the other MUST to say "unless
> there's an error" or words to that effect.
>

Actually, REGISTRATION_RESP is returned only when there is not error,
so if it is returned, it must have one or more entries.

The "it MUST instead return an error" should suffice to clarify this?


>
> > In 4.5:
> >
> >        If some
> >        locations within a batch request are outside the regulatory
> >        domain supported by the Database, the Database MAY return an OK
> >        response with available spectrum for only the valid locations;
> >        otherwise, if all locations within a batch request are outside
> >        the regulatory domain, the Database MUST respond with an
> >        OUTSIDE_COVERAGE error.
> >
> > What should the database do if it doesn't follow the MAY?   Should it
> > return an OUTSIDE_COVERAGE error?   It seems to me that this MAY is going
> > to require some unclear heuristics on the side of the master device.
> > Why isn't this a MUST?   I think if this were a MUST, it would be clear
> > how implementations should behave; by making it a MAY, there's a big gap
> > that I think will lead to interoperability problems as different
> > implementors make different choices about how to treat this situation.
> >
> > If it does not follow MAY, the assumption is that it would return
> OUTSIDE_COVERAGE error.
> > I take your point about it being harder to use for the device.
> >
> > I don't think there would be objections to changing this to a MUST.
>
> That would certainly satisfy my concern!   :)
>
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > Section 3 describes spectrum-usage messages as purely informational.
> > Section 4.5 says that the database can require that such messages be
> > sent.   Which is it: is it sometimes required, or always purely
> > informational?   Or does "purely informational" just mean that the
> > protocol provides no mechanism for tracking such notifications?  It would
> > be helpful if this were clearer.
> >
> > "purely informational" means that the it's just notifying the Database
> what
> > spectrum it intends to use and is not a request to the Database to get
> permission
> > to use that spectrum. Some regulators require this notification.
> >
> > I'll try to clarify the text.
>
> Ah, that explains it.   Thanks.   Adding some text pretty much like what
> you just wrote would address this comment nicely.
>

Will do.


>
> > I have to confess that the use of "master" and "slave" throughout this
> > document makes me quite uncomfortable in reading it.   It would really be
> > preferable to use terms that have less painful history associated with
> > them, like "core" and "leaf" or "coordinator" and "supplicant."   I
> > realize this is a matter of taste, and I do not at all mean to suggest
> > that there's anything wrong with the use of these terms, which are
> > certainly common in the computing industry.   This is just a comment, and
> > whether you address it is entirely up to you.
> >
> > This results from the terminology established in RFC6953.
>
> I guess I should have complained sooner... :}
>
> > In 4.6.1, it would help to have text that explains what it means to
> > validate a device.   It's certainly not required for interoperability,
> > but might be helpful for implementors of database servers.
> >
> > This is explained in the first paragraph of 4.6, I think.
> >
> >    A Slave Device needs a Master Device to ask the Database on its
> >    behalf for available spectrum.  Depending on the ruleset, the Master
> >    Device also must validate with the Database that the Slave Device is
> >    permitted to operate. ...
>
> Ah, okay.   The problem is that "validate the device" isn't obviously
> connected to "validate with the database that the ..."   I see the
> connection now, but it would help to make it clearer.
>

Will do.


>
> > In 5.3, it's a little puzzling that antenna direction, radiation pattern,
> > gain and polarization aren't defined, because they seem like properties
> > that should have universal applicability, even if they are not required
> > in all cases.   Is this being left as future work, or is there some more
> > subtle reason why these haven't been defined explicitly?
> >
> > This is for future extension, rather than defining a whole set of things
> that
> > won't get used. Note that for mobile devices,
> direction/pattern/polarization
> > changes all the time and would be "crazy" to define rules based on these
> > characteristics.
>
> Right, just checking.
>
> > In 5.11, power is expressed in dbm, which leads me to wonder if this is
> > the product of the antenna gain and the input power to the output
> > amplifier, or whether it's just the input power to the amplifier, or
> > whether it's being left intentionally ambiguous.
> >
> > Great question.
> >
> > I believe this was left intentionally ambiguous, since each regulator
> may choose to define
> > the power in a different way. Typically, it's the radiated power at the
> > antenna, over some bandwidth, averaged over some period of time (defined
> by the regulator).
> >
> > Perhaps I should add the "Typically" statement to Section 5.11 that
> describes Spectrum.
>
> The problem with this is that if the meaning of the unit is different
> depending on the regulatory regime, it might make life really difficult for
> the maker of a device that has to operate in different regimes.   I suppose
> makers of devices like this are used to this problem, so maybe it's not
> really a problem in practice, but it would certainly be nice to talk a bit
> about this in the document.
>

I'll add it to the doc.


>
> Thanks for the quick response!
>
>


-- 
-vince