FW: RFC 5241 on Naming Rights in IETF Protocols

"Richard Shockey" <richard@shockey.us> Tue, 01 April 2008 18:54 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC3CB28C53D; Tue, 1 Apr 2008 11:54:18 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6DD728C520 for <ietf@core3.amsl.com>; Tue, 1 Apr 2008 11:54:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.524
X-Spam-Level:
X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yfr9K5VRJbUC for <ietf@core3.amsl.com>; Tue, 1 Apr 2008 11:54:16 -0700 (PDT)
Received: from mail.songbird.com (mail.songbird.com [208.184.79.10]) by core3.amsl.com (Postfix) with ESMTP id B936028C50F for <ietf@ietf.org>; Tue, 1 Apr 2008 11:54:16 -0700 (PDT)
Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id m31IqxTU021446 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 1 Apr 2008 10:53:00 -0800
From: Richard Shockey <richard@shockey.us>
To: 'IETF Discussion' <ietf@ietf.org>
Subject: FW: RFC 5241 on Naming Rights in IETF Protocols
Date: Tue, 01 Apr 2008 14:53:47 -0400
Message-ID: <132f01c89429$b8a748c0$29f5da40$@us>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AciUGYsqKQcpsOOxS7WcM8UI/qfLzQAEBkpg
Content-Language: en-us
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Clean
X-Songbird-From: richard@shockey.us
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Can this be extended to WG naming rights as well. :-) 

-----Original Message-----
From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org]
On Behalf Of rfc-editor@rfc-editor.org
Sent: Tuesday, April 01, 2008 12:58 PM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: rfc-editor@rfc-editor.org
Subject: RFC 5241 on Naming Rights in IETF Protocols


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5241

        Title:      Naming Rights in IETF Protocols 
        Author:     A. Falk, S. Bradner
        Status:     Informational
        Date:       1 April 2008
        Mailbox:    falk@bbn.com, 
                    sob@harvard.edu
        Pages:      12
        Characters: 25304
        Updates/Obsoletes/SeeAlso:   None

        URL:        http://www.rfc-editor.org/rfc/rfc5241.txt

This document proposes a new revenue source for the IETF to support
standardization activities: protocol field naming rights, i.e., the 
association of commercial brands with protocol fields.  This memo 
describes a process for assignment of rights and explores some of the 
issues associated with the process.  Individuals or organizations that 
wish to purchase naming rights for one or more protocol fields are 
expected to follow this process.  This memo provides information for the 
Internet community.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf