[iucg] IUser information
jefsey <jefsey@jefsey.com> Thu, 25 August 2011 01:11 UTC
Return-Path: <jefsey@jefsey.com>
X-Original-To: iucg@ietfa.amsl.com
Delivered-To: iucg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97C8E21F8BB6 for <iucg@ietfa.amsl.com>; Wed, 24 Aug 2011 18:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.076
X-Spam-Level:
X-Spam-Status: No, score=-102.076 tagged_above=-999 required=5 tests=[AWL=0.522, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h3uEbCXNM6pr for <iucg@ietfa.amsl.com>; Wed, 24 Aug 2011 18:11:31 -0700 (PDT)
Received: from montage2.altserver.com (montage2.altserver.com [72.34.52.22]) by ietfa.amsl.com (Postfix) with ESMTP id 4BAA021F8B03 for <iucg@ietf.org>; Wed, 24 Aug 2011 18:11:31 -0700 (PDT)
Received: from 123.154-227-89.dsl.completel.net ([89.227.154.123]:57197 helo=jfcmsc.jefsey.com) by montage2.altserver.com with esmtpa (Exim 4.69) (envelope-from <jefsey@jefsey.com>) id 1QwOUs-0000RS-4M for iucg@ietf.org; Wed, 24 Aug 2011 18:12:43 -0700
Message-Id: <7.0.1.0.2.20110825015847.06e32520@jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Thu, 25 Aug 2011 03:15:13 +0200
To: iucg@ietf.org
From: jefsey <jefsey@jefsey.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_690720853==.ALT"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage2.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: [iucg] IUser information
X-BeenThere: iucg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: internet users contributing group <iucg@ietf.org>
List-Id: internet users contributing group <iucg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iucg>, <mailto:iucg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iucg>
List-Post: <mailto:iucg@ietf.org>
List-Help: <mailto:iucg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 01:11:32 -0000
Dear IUsers, some clarification in terms of IUser documentation: 1. Unicode seems to deny IUsers the right to study and discuss the Unicode terminology. This seems preposterous and in conflict with WTO basic documetation rules. 2. After the intervention of Unicode VP, I have published a description of IUWW (IUser Working Wiki). http://iucg.org/wiki/IUWW 3. Russ Hosley (IETF, Chair) puts an official end to the FYI sub-series of RFC destined, by the IETF user area to inform the public If you have any comment you are welcome. RFC 6360 being short enough, I provide its text for direct perusal and possible debate: over the IUCG's scope. ------ Internet Engineering Task Force (IETF) R. Housley Request for Comments: 6360 Vigil Security Obsoletes: 1150 August 2011 Category: Informational ISSN: 2070-1721 Conclusion of FYI RFC Sub-Series Abstract This document concludes the For Your Information (FYI) sub-series of RFCs, established by RFC 1150 for use by the IETF User Services Area, which no longer exists. The IESG does not intend to make any further additions to this RFC sub-series, and this document provides a record of this decision. This document also obsoletes RFC 1150 and changes the status of RFC 1150 to Historic. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6360. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 1. Background The For Your Information (FYI) sub-series of RFCs was established by RFC 1150 [RFC1150] in 1990 for use by the IETF User Services Area, which has not met since IETF 53 held in March 2001. This RFC sub- series was designed to provide Internet users with a repository of information regarding the Internet that might be interesting to a wide range of people. The publication of RFC 1150 [RFC1150] introduced the FYI sub-series of RFCs. Since that time, a total of 38 FYI numbers have been assigned. Many other Informational RFCs have been published that are not part of the FYI sub-series. The list of documents in the FYI sub-series can be found on the RFC Editor web site [INDEX]. 2. Conclusion of the FYI Sub-Series The IESG does not intend to make any further additions to the FYI sub-series. The IESG intends to continue to produce Informational RFCs, but none of them will be assigned an FYI number. All published RFCs that are currently part of the FYI sub-series will retain their FYI numbers. The FYI numbers continue to provide reference points for these documents, and the FYI number can be used in citations to these documents. If a future RFC is published that obsoletes an existing member of the FYI sub-series, the new RFC will not be assigned an FYI number. 3. RFC 1150 Moved to Historic This document moves RFC 1150 [RFC1150] to Historic. The procedural information in RFC 1150 is no longer valid. If it becomes desirable to make additions to the FYI sub-series in the future, new procedures can be developed to replace this document. 4. Security Considerations No Internet security issues are anticipated by the actions described in this document. 5. References 5.1. Normative Reference [RFC1150] Malkin, G. and J. Reynolds, "FYI on FYI: Introduction to the FYI Notes", FYI 1, RFC 1150, March 1990. 5.2. Informative Reference [INDEX] "FYI Index", http://www.rfc-editor.org/fyi-index.html Author's Address Russell Housley Vigil Security, LLC 918 Spring Knoll Drive Herndon, VA 20170 USA EMail: housley@vigilsec.com ----- Best. jfc
- [iucg] IUser information jefsey
- Re: [iucg] IUser information Marie-France Berny
- Re: [iucg] IUser information JFC Morfin
- Re: [iucg] IUser information Marie-France Berny
- Re: [iucg] IUser information Mykyta Yevstifeyev
- Re: [iucg] IUser information JFC Morfin