[ieee-ietf-coord] FW: RFC 7545 on Protocol to Access White-Space (PAWS) Databases

["Romascanu, Dan (Dan)" <[e-mail]>]

This announcement is related to item #9 in the list of shared areas of interest between the IETF and IEEE 802. This concludes the last pending action item, and this item will be CLOSED at the next iteration of the list. 

Thanks and Regards,

Dan


> -----Original Message-----
> From: IETF-Announce [mailto:[e-mail]] On Behalf Of
> [e-mail]
> Sent: Wednesday, May 20, 2015 3:51 AM
> To: [e-mail]; [e-mail]
> Cc: [e-mail]; [e-mail]; [e-mail]
> Subject: RFC 7545 on Protocol to Access White-Space (PAWS) Databases
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 7545
> 
>         Title:      Protocol to Access White-Space (PAWS)
>                     Databases
>         Author:     V. Chen, Ed., S. Das, L. Zhu,
>                     J. Malyar, P. McCann
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       May 2015
>         Mailbox:    [e-mail],
>                     [e-mail],
>                     [e-mail],
>                     [e-mail],
>                     [e-mail]
>         Pages:      90
>         Characters: 188634
>         Updates/Obsoletes/SeeAlso:   None
> 
>         I-D Tag:    draft-ietf-paws-protocol-20.txt
> 
>         URL:        https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.rfc-
> 2Deditor.org_info_rfc7545&d=AwIBAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4d
> zGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=puCEOiBS78FvqasjC2l1E5
> -y-hWHXuBmYG-PMA8-
> r18&s=hRhHRmMOi0cIwISOEHgSiNIbASbLOr_z1PHm_HsChu8&e=
> 
>         DOI:        https://urldefense.proofpoint.com/v2/url?u=http-
> 3A__dx.doi.org_10.17487_RFC7545&d=AwIBAg&c=BFpWQw8bsuKpl1SgiZH6
> 4Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=puCEOiBS78Fv
> qasjC2l1E5-y-hWHXuBmYG-PMA8-
> r18&s=xzMrRDf3WRwSRJKvJR7x2HFXngj6OLl-Pezw4Eb34Q8&e=
> 
> Portions of the radio spectrum that are allocated to licensees are available for
> non-interfering use.  This available spectrum is called "white space".  Allowing
> secondary users access to available spectrum "unlocks" existing spectrum to
> maximize its utilization and to provide opportunities for innovation, resulting
> in greater overall spectrum utilization.
> 
> One approach to managing spectrum sharing uses databases to report
> spectrum availability to devices.  To achieve interoperability among multiple
> devices and databases, a standardized protocol must be defined and
> implemented.  This document defines such a protocol, the "Protocol to
> Access White-Space (PAWS) Databases".
> 
> This document is a product of the Protocol to Access WS database Working
> Group of the IETF.
> 
> This is now a Proposed Standard.
> 
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and
> suggestions for improvements.  Please refer to the current edition of the
> Official Internet Protocol Standards
> (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-
> 2Deditor.org_standards&d=AwIBAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzG
> xR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=puCEOiBS78FvqasjC2l1E5-y-
> hWHXuBmYG-PMA8-r18&s=tYzcx4qWOdQb_PI-mvr3DrL1-
> k_3cu9ahoGt7svJuSM&e= ) for the standardization state and status of this
> protocol.  Distribution of this memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_ietf-
> 2Dannounce&d=AwIBAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNX
> CJfQzvlsiLQfucBXRucPvdrphpBsFA&m=puCEOiBS78FvqasjC2l1E5-y-
> hWHXuBmYG-PMA8-r18&s=JVngvK20qC4nCXcKhHx53Ys-
> lbqpjqmkMIu2uTcs1Dc&e=
>   https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.rfc-
> 2Deditor.org_mailman_listinfo_rfc-
> 2Ddist&d=AwIBAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvl
> siLQfucBXRucPvdrphpBsFA&m=puCEOiBS78FvqasjC2l1E5-y-hWHXuBmYG-
> PMA8-r18&s=0E4fc0KMZ94Axfd0qiqGdCq94APlHFqws5Euu4autvY&e=
> 
> For searching the RFC series, see
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-
> 2Deditor.org_search&d=AwIBAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR
> 31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=puCEOiBS78FvqasjC2l1E5-y-
> hWHXuBmYG-PMA8-
> r18&s=Mqu4UFkWMBDuNPwHU4Csa9aygoqdiJguC3yHoS1th7w&e=
> For downloading RFCs, see
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-
> 2Deditor.org_rfc.html&d=AwIBAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGx
> R31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=puCEOiBS78FvqasjC2l1E5-y-
> hWHXuBmYG-PMA8-
> r18&s=d6RUzZ8rWa5_C_ciHRIJoktReMhJkmIV7LSph9xF664&e=
> 
> Requests for special distribution should be addressed to either the author of
> the RFC in question, or to [e-mail].  Unless specifically noted
> otherwise on the RFC itself, all RFCs are for unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
>