Return-Path: 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 9347B1A87EB for ; Tue, 26 Aug 2014 13:58:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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, 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 o4T39fGuDjVX for ; Tue, 26 Aug 2014 13:58:20 -0700 (PDT) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 175DC1A87DF for ; Tue, 26 Aug 2014 13:58:18 -0700 (PDT) Received: by mail-lb0-f179.google.com with SMTP id v6so2058006lbi.10 for ; Tue, 26 Aug 2014 13:58:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UgORPWpbf0KTRc44l0RFAruErnEzO2kEGriLfFCvk7I=; b=0ffTiDh4/4FVvXD6FilSzJ8ZVZDXsyxd5cNoFC4mDhmcyPjGrL/Z1EZwhMCV1xUGr0 uV0cZkoRIzC1eLdGcyPQ+MbtS0kzMiuaqkqZU7Rl88oD+38JsR4vn2iJHhzcFsP7S8l+ /LSZdrScGOYbbdy4HPq0udpcsF96xXcWj365hLzKg1M4xdrfCTl0ywRHCI9e2TFZUWG8 bcqKgtiHG8VbcyQwXYjg4d5JSW/Os2+hjNIcTbBvXoiIsWVbX9rWPp4cfhZ9ysBB/fuG eDfBRx6ArRvAqheUDsRj92EK5swLTAKP6px6jtgcVPx8kj31arKWcm9ZsQjhIgRT8Rcx NlXg== MIME-Version: 1.0 X-Received: by 10.112.28.8 with SMTP id x8mr4431724lbg.104.1409086697378; Tue, 26 Aug 2014 13:58:17 -0700 (PDT) Received: by 10.112.64.170 with HTTP; Tue, 26 Aug 2014 13:58:17 -0700 (PDT) In-Reply-To: References: <20140826075902.18942.88866.idtracker@ietfa.amsl.com> Date: Tue, 26 Aug 2014 16:58:17 -0400 Message-ID: From: Kathleen Moriarty To: Vincent Chen Content-Type: multipart/alternative; boundary=001a113404280e1b4805018e90d1 Archived-At: http://mailarchive.ietf.org/arch/msg/paws/mc_0CxZpF5uWftjD3VQSSazaKjQ Cc: "paws-chairs@tools.ietf.org" , Pete Resnick , "paws@ietf.org" , Ted Lemon , draft-ietf-paws-protocol@tools.ietf.org Subject: Re: [paws] New Version Notification - draft-ietf-paws-protocol-15.txt X-BeenThere: paws@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Protocol to Access White Space database \(PAWS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2014 20:58:22 -0000 --001a113404280e1b4805018e90d1 Content-Type: text/plain; charset=UTF-8 Thank you for the updates, my discuss will be cleared in a minute. I have a comment below to assist with one of the other points from Stephen. On Tue, Aug 26, 2014 at 4:07 AM, Vincent Chen wrote: > All, > > I've taken a stab at addressing all the DISCUSS points and comments. > Hopefully this moves us closer. > > Diff: http://www.ietf.org/rfcdiff?url2=draft-ietf-paws-protocol-15 > > > Summary of updates: > o Clarified why spectrum-notify is "informational" > > o Clarified that device registration is typically only required for > fixed devices > > o Global statement about timestamp format and must be UTC > > o Global statement about MISSING error returned, whether it's > required by PAWS or ruleset > > o Clarified UNSUPPORTED error > > o Mandate that Database-change must be included in all responses a > minimum of 2 weeks before change > > o Clarified that preconfigured values are ruleset specific > (INIT_RESP) > > o Added reference to FCC ruleset for registration of Fixed Devices > > o Make deviceOwner and serialNumber optional at PAWS level and > required on a per-ruleset basis > > o Update description for "location" to be where device intends to > operate, rather than "current location" > > o For REGISTRATION_RESP, add clarification that when it is returned, > it will have at least one RulesetInfo. Otherwise, it's an > UNSUPPORTED error. > > o Clarified that, when a Master Device asks for spectrum on behalf > of a Slave Device, there are 2 locations in the message and > changed masterDeviceLocation to be required > > o Indicate that power levels are typically EIRP (as opposed to > conducted power to the antenna) > > o Added description for a "schedule" > > o Add intro to DEVICE_VALID_REQ > > o TLS: Follow best practices to improve security and interop. > Reference draft-ietf-uta-tls-bcp > > o TLS: Use OCSP for better performance; RFC6960 > OCSP Stapling improves performance over just OCSP, but not for leaving out OCSP all together. Security is improved as well. If you keep the sentence in about OCSP, I think you need all 3 references: RFC6066, RFC6961, and RFC6960. If you just wanted to follow the guidance in draft-ietf-uta-tls-bcp, they already covered this. > > o TLS: When using client auth, Database determines acceptable root > CAs > > o Extensibility: Add statement that no extensions that return device > information will not be accepted > > o Clarify IANA instructions for the Ruleset ID Registry > > o Security: Acknowledge that unauthorized access to device > registration, other sensitive device info is a risk, and indicate > that privacy policies must be published and implement to control > access. > > Thanks! > > -vince > > > On Tue, Aug 26, 2014 at 12:59 AM, wrote: > >> >> A new version (-15) has been submitted for draft-ietf-paws-protocol: >> http://www.ietf.org/internet-drafts/draft-ietf-paws-protocol-15.txt >> >> Sub state has been changed to AD Followup from Revised ID Needed >> >> >> The IETF datatracker page for this Internet-Draft is: >> https://datatracker.ietf.org/doc/draft-ietf-paws-protocol/ >> >> Diff from previous version: >> http://www.ietf.org/rfcdiff?url2=draft-ietf-paws-protocol-15 >> >> 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. >> >> IETF Secretariat. >> >> > > > -- > -vince > -- Best regards, Kathleen --001a113404280e1b4805018e90d1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thank you for the updates, my discuss will be cleared in a= minute. =C2=A0I have a comment below to assist with one of the other point= s from Stephen.


On Tue, Aug 26, 2014 at 4:07 AM, Vincent Chen <<= a href=3D"mailto:vchen@google.com" target=3D"_blank">vchen@google.com&g= t; wrote:
All,

I&#= 39;ve taken a stab at addressing all the DISCUSS points and comments.
=
Hopefully this moves us closer.

Diff: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-paws-protocol-15


Summary of updates:
=C2= =A0 =C2=A0o =C2=A0Clarified why spectrum-notify is "informational"= ;

=C2=A0 =C2=A0o =C2=A0Clarified that device regis= tration is typically only required for
=C2=A0 =C2=A0 =C2=A0 fixed devices

=C2=A0 =C2= =A0o =C2=A0Global statement about timestamp format and must be UTC

=C2=A0 =C2=A0o =C2=A0Global statement about MISSING error = returned, whether it's
=C2=A0 =C2=A0 =C2=A0 required by PAWS = or ruleset

=C2=A0 =C2=A0o =C2=A0Clarified UNSUPPORTED error
<= div>
=C2=A0 =C2=A0o =C2=A0Mandate that Database-change must b= e included in all responses a
=C2=A0 =C2=A0 =C2=A0 minimum of 2 w= eeks before change

=C2=A0 =C2=A0o =C2=A0Clarified that preconfigured values are ruleset specif= ic
=C2=A0 =C2=A0 =C2=A0 (INIT_RESP)

=C2= =A0 =C2=A0o =C2=A0Added reference to FCC ruleset for registration of Fixed = Devices

=C2=A0 =C2=A0o =C2=A0Make deviceOwner and = serialNumber optional at PAWS level and
=C2=A0 =C2=A0 =C2=A0 required on a per-ruleset basis

=C2=A0 =C2=A0o =C2=A0Update description for "location" to= be where device intends to
=C2=A0 =C2=A0 =C2=A0 operate, rather = than "current location"

=C2=A0 =C2=A0o =C2=A0For REGISTRATION_RESP, add clarificatio= n that when it is returned,
=C2=A0 =C2=A0 =C2=A0 it will have at = least one RulesetInfo. =C2=A0Otherwise, it's an
=C2=A0 =C2=A0= =C2=A0 UNSUPPORTED error.

=C2=A0 =C2=A0o =C2=A0Clarified that, when a Master Device asks for spe= ctrum on behalf
=C2=A0 =C2=A0 =C2=A0 of a Slave Device, there are= 2 locations in the message and
=C2=A0 =C2=A0 =C2=A0 changed mast= erDeviceLocation to be required

=C2=A0 =C2=A0o =C2=A0Indicate that power levels are typicall= y EIRP (as opposed to
=C2=A0 =C2=A0 =C2=A0 conducted power to the= antenna)

=C2=A0 =C2=A0o =C2=A0Added description f= or a "schedule"

=C2=A0 =C2=A0o =C2=A0Add intro to DEVICE_VALID_REQ

=C2=A0 =C2=A0o =C2=A0TLS: Follow best practices to improve security a= nd interop.
=C2=A0 =C2=A0 =C2=A0 Reference draft-ietf-uta-tls-bcp=

=C2=A0 =C2=A0o =C2=A0TLS: Use OCSP for better per= formance; RFC6960
OCSP Stapling improves performance over just = OCSP, but not for leaving out OCSP all together. =C2=A0Security is improved= as well.=C2=A0
If you keep the sentence in about OCSP, I think y= ou need all 3 references: RFC6066, RFC6961, and RFC6960. =C2=A0If you just = wanted to follow the guidance in draft-ietf-uta-tls-bcp, they already cover= ed this.=C2=A0

=C2=A0 =C2=A0o =C2=A0TLS: When using client auth, Datab= ase determines acceptable root
=C2=A0 =C2=A0 =C2=A0 CAs

=C2=A0 =C2=A0o =C2=A0Extensibility: Add statement that no e= xtensions that return device
=C2=A0 =C2=A0 =C2=A0 information wil= l not be accepted

=C2=A0 =C2=A0o =C2=A0Clarify IANA instructions for the = Ruleset ID Registry

=C2=A0 =C2=A0o =C2=A0Security:= Acknowledge that unauthorized access to device
=C2=A0 =C2=A0 =C2= =A0 registration, other sensitive device info is a risk, and indicate
=C2=A0 =C2=A0 =C2=A0 that privacy policies must be published and imple= ment to control
=C2=A0 =C2=A0 =C2=A0 access.

=
Thanks!

-vince


On Tue, Aug 26, 2014 at 12:59 AM, <internet-drafts@ietf.org>= ; wrote:

A new version (-15) has been submitted for draft-ietf-paws-protocol:
http://www.ietf.org/internet-drafts/draft-ietf-paws-= protocol-15.txt

Sub state has been changed to AD Followup from Revised ID Needed


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-paws-protocol/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-paws-protoc= ol-15

Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.




--
-vince



--

Best regards,
Kathleen
--001a113404280e1b4805018e90d1--