Re: submitting an ID

Edward Lewis <Ed.Lewis@neustar.biz> Tue, 23 January 2007 21:46 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9TTe-0003KM-1a; Tue, 23 Jan 2007 16:46:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9TTc-0003KG-OC for ietf@ietf.org; Tue, 23 Jan 2007 16:46:48 -0500
Received: from hlid.ogud.com ([66.92.146.160] helo=ogud.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9TTb-0002tN-CN for ietf@ietf.org; Tue, 23 Jan 2007 16:46:48 -0500
Received: from [192.168.1.101] (hlid.ogud.com [66.92.146.160]) by ogud.com (8.13.1/8.13.1) with ESMTP id l0NLbe4f053161; Tue, 23 Jan 2007 16:37:41 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Mime-Version: 1.0
Message-Id: <a06230910c1dc2de2f3cb@[192.168.1.101]>
In-Reply-To: <45B62D3A.20808@zurich.ibm.com>
References: <03E7D3E231BB7B4A915A6581D4296CC6035FAD4E@NSNOVPS00411.nacio.xythos.com> <p06240603c1d6eef6b9d6@[129.46.225.123]> <45B6119A.3030009@gmx.de> <a06230906c1dbcd874b6b@[192.168.1.101]> <45B62D3A.20808@zurich.ibm.com>
Date: Tue, 23 Jan 2007 16:46:50 -0500
To: ietf@ietf.org
From: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.57 on 66.92.146.160
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: submitting an ID
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

>Use XML2RFC and you simply don't have to worry about this anyway.

In the spirit of trying follow a specification and not an implementation:

Referencing this, linked from the IETF main page via http://ietf.org/ID.html:

http://www.ietf.org/ietf/1id-guidelines.html

In the section on IPR it says:

# 9.  Intellectual Property Rights
# If you think that you, your company, or anyone else owns a patent or other
# IPR on the work described in the draft, you should read carefully RFC 3979
# (Bradner, S., "Intellectual Property Rights in IETF Technology," March 2005.)
# [RFC3979]. The first notice required in Internet-Drafts, described in
# Section 3 (IPR-Related Notices Required in Internet-Drafts) of this document,
# obligates you to send an IPR disclosure under certain circumstances. Before
# submitting the draft, it would be a good advice to talk to the working group
# chair or area directors about it.

Where in there is there a requirement to include the text mentioned below?

   * The document seems to lack an RFC 3979 Section 5, para 1 IPR Disclosure
     Acknowledgement.

   * The document seems to lack an RFC 3979 Section 5, para 2 IPR Disclosure
     Acknowledgement.

   * The document seems to lack an RFC 3979 Section 5, para 3 IPR Disclosure
     Invitation.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                +1-571-434-5468
NeuStar

Dessert - aka Service Pack 1 for lunch.

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf