[rfc-dist] BCP 79, RFC 8179 on Intellectual Property Rights in IETF Technology
rfc-editor@rfc-editor.org Wed, 31 May 2017 23:01 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B95A128B8E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 31 May 2017 16:01:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 HVKhtUkNE2fw for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 31 May 2017 16:01:01 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68FD3124D37 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 31 May 2017 16:01:01 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A8A4EB80DD7; Wed, 31 May 2017 16:00:38 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id C8DAFB80DD6; Wed, 31 May 2017 16:00:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170531230037.C8DAFB80DD6@rfc-editor.org>
Date: Wed, 31 May 2017 16:00:37 -0700
Subject: [rfc-dist] BCP 79, RFC 8179 on Intellectual Property Rights in IETF Technology
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
BCP 79
RFC 8179
Title: Intellectual Property Rights in IETF Technology
Author: S. Bradner,
J. Contreras
Status: Best Current Practice
Stream: IETF
Date: May 2017
Mailbox: sob@sobco.com,
cntreras@gmail.com
Pages: 26
Characters: 65486
Obsoletes: RFC 3979, RFC 4879
Updates: RFC 2026
See Also: BCP 79
I-D Tag: draft-bradner-rfc3979bis-13.txt
URL: https://www.rfc-editor.org/info/rfc8179
DOI: 10.17487/RFC8179
The IETF policies about Intellectual Property Rights (IPR), such as
patent rights, relative to technologies developed in the IETF are
designed to ensure that IETF working groups and participants have as
much information as possible about any IPR constraints on a technical
proposal as early as possible in the development process. The
policies are intended to benefit the Internet community and the
public at large, while respecting the legitimate rights of IPR
holders. This document sets out the IETF policies concerning IPR
related to technology worked on within the IETF. It also
describes the objectives that the policies are designed to meet.
This document updates RFC 2026 and, with RFC 5378, replaces Section 10
of RFC 2026. This document also obsoletes RFCs 3979 and 4879.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org