Internet Engineering Task Force (IETF) E. Juskevicius Request for Comments: 6174 TrekAhead Category: Informational March 2011 ISSN: 2070-1721
Definition of IETF Working Group Document States
Abstract
The IETF Datatracker tool needs to be enhanced to make it possible
for Working Group (WG) Chairs to provide IETF participants with more information about the status and progression of WG documents than is currently possible.
This document defines new states and status annotation tags that need to be added to the Datatracker to enable WG Chairs and their
Delegates to track the status of Internet-Drafts (I-Ds) that are
associated with their WGs. This document also describes the meaning of all previously implemented I-D states and substate annotation tags currently used by IETF Area Directors to indicate the status of I-Ds that have been sent to the IESG for evaluation and publication.
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
https://www.doczj.com/doc/7c6881660.html,/info/rfc6174.
Juskevicius Informational [Page 1]
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
(https://www.doczj.com/doc/7c6881660.html,/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.
Table of Contents
1. Introduction (4)
2. Conventions Used in This Document (4)
3. I-D States Already Implemented by the Datatracker (5)
3.1. I-D Availability States (5)
3.1.1. Expired (6)
3.1.2. Active (6)
3.1.3. Replaces and Replaced By (6)
3.2. IESG Document States (7)
3.2.1. Publication Requested (7)
3.2.2. AD Evaluation (8)
3.2.3. IESG Evaluation (8)
4. New States and Status Annotation Tags for WG I-Ds (9)
4.1. Working Group I-D State Diagram (9)
4.2. Working Group I-D States (11)
4.2.1. Call for Adoption by WG Issued (12)
4.2.2. Adopted by a WG (12)
4.2.3. Adopted for WG Info Only (13)
4.2.4. WG Document (13)
4.2.5. Parked WG Document (13)
4.2.6. Dead WG Document (14)
4.2.7. In WG Last Call (14)
4.2.8. Waiting for WG Chair Go-Ahead (15)
4.2.9. WG Consensus: Waiting for Writeup (15)
4.2.10. Submitted to IESG for Publication (15)
4.3. Working Group I-D Status Annotation Tags (16)
4.3.1. Awaiting Expert Review/Resolution of Issues Raised .16 4.3.2. Awaiting External Review/Resolution of
Issues Raised (16)
4.3.3. Awaiting Merge with Other Document (16)
4.3.4. Author or Editor Needed (17)
4.3.5. Waiting for Referenced Document (17)
Juskevicius Informational [Page 2]
4.3.6. Waiting for Referencing Document (17)
4.3.7. Revised I-D Needed - Issue raised by WGLC (18)
4.3.8. Revised I-D Needed - Issue raised by AD (18)
4.3.9. Revised I-D Needed - Issue raised by IESG (18)
4.3.10. Doc Shepherd Followup Underway (18)
4.3.11. Other - see Comment Log (19)
5. Intended Maturity Level of WG Drafts (19)
6. Security Considerations (19)
7. References (19)
7.1. Normative References (19)
7.2. Informative References (20)
8. Acknowledgments (20)
Appendix A: "IESG Document" States (21)
A.1. Definition of "IESG Document" States (21)
A.1.1. Publication Requested (21)
A.1.2. AD Evaluation (21)
A.1.3. Expert Review (21)
A.1.4. Last Call Requested (22)
A.1.5. In Last Call (22)
A.1.6. Waiting for Writeup (22)
A.1.7. Waiting for AD Go-Ahead (22)
A.1.8. IESG Evaluation (22)
A.1.9. IESG Evaluation - Defer (23)
A.1.10. Approved - Announcement to be sent (23)
A.1.11. Approved - Announcement sent (23)
A.1.12. RFC Ed Queue (23)
A.1.13. RFC Published (23)
A.1.14. DNP - Waiting for AD note (23)
A.1.15. DNP - Announcement to be sent (23)
A.1.16. AD is Watching (23)
A.1.17. Dead (24)
A.2. IESG Document Substates (24)
A.2.1. Point Raised - writeup needed (24)
A.2.2. AD Followup (24)
A.2.3. External Party (25)
A.2.4. Revised ID Needed (25)
Juskevicius Informational [Page 3]
1. Introduction
The IETF Datatracker is a web-based system for managing information
about Internet-Drafts (I-Ds) and RFCs, IPR disclosures, liaison
statements, and several other important aspects of the IETF process
[IDTRACKER].
The Datatracker is currently able to track and report on the status
of I-Ds that have been submitted to the IESG for evaluation and
publication. Appendix A of this document describes all of the
document states and substate annotation tags used by IETF Area
Directors (ADs) to indicate the status of I-Ds that have been sent to the IESG.
In contrast, the Datatracker has almost no ability to indicate the
status and progression of I-Ds before they are sent to the IESG. The Datatracker can only track the availability status of I-Ds today
(e.g., "Active", Expired", "Withdrawn", "Replaced by") and in some
cases indicate which IETF Working Group (WG) an I-D is associated
with (if any).
Section 3 of this document contains a summary of the Datatracker’s
current ability to track and report on the status of I-Ds in the IETF document stream. The IETF document stream is defined in Section
5.1.1 of RFC 4844 [RFC4844].
Section 4 of this document defines several new I-D states and I-D
status annotation tags that need to be added to the Datatracker to
enable status tracking and reporting for WG I-Ds.
2. Conventions Used in This Document
A "working group I-D" (WG I-D) is an Internet-Draft that has achieved consensus for adoption as a work item by a WG (compared to an
individual submission I-D that has not, or has not yet, achieved
consensus).
The terms "WG I-D", "WG document", and "WG draft" are used
synonymously throughout this document. The same is true for the
plural case of each term.
The terms "WG document" and "WG draft" are not intended to apply to
any other document that may be reviewed, discussed, or produced by an IETF working group. Working group meeting materials such as Blue
Sheets, agendas, jabber logs, scribe’s notes, minutes, and
presentation slides are not to be considered "WG documents" or "WG
drafts" in the context of this document.
Juskevicius Informational [Page 4]
The phrase "WG status of an I-D" is to be interpreted as referring to the state that an I-D is in, as defined in Section 4.2 of this
document. This phrase does not refer to an I-D’s availability status
(e.g., "Expired", "Active", "Replaced by") as described in Section
3.1, or to any of the IESG states used by Area Directors to describe the status of I-Ds they may be evaluating.
3. I-D States Already Implemented by the Datatracker
This section describes capabilities that are currently implemented in the Datatracker to track the status of I-Ds in the IETF document
stream.
The document availability states described in Section 3.1 are
applicable to every I-D submitted to the IETF.
The IESG document states and substate annotation tags described in
Section 3.2 and Appendix A are only applicable to I-Ds that have been submitted to the IESG for evaluation and publication.
The Datatracker currently has no I-D states or I-D status annotation tags to describe the WG status of any I-D.
3.1. I-D Availability States
The Datatracker currently maintains availability status information
for every I-D submitted to the IETF. The I-D availability states are as follows:
- Expired
- Active
- Replaces
- Replaced by
- Withdrawn by Submitter
- Withdrawn by IETF
- RFC
The first four I-D availability states are explained in the following subsections. The other states are self-explanatory.
Note that the Datatracker describes the status of some I-Ds with the phrase "I-D Exists". "I-D Exists" is the state that is manufactured by the Datatracker to describe I-Ds for which it has no other status information. For example, the tool currently uses "I-D Exists" to
describe I-Ds that are not expired and that have not been sent to the IESG.
Juskevicius Informational [Page 5]
3.1.1. Expired
An "Expired" I-D is a document that is more than six months old and
that has not been updated or replaced by a newer I-D or an RFC.
Every I-D has a normal lifespan of 185 days. An I-D will expire and be deleted from the I-D repository after six months unless it is
updated or replaced by a newer version. One exception is that an I-D undergoing official evaluation by the IESG will not be expired before its status is resolved (e.g., the I-D is published as an RFC). IESG states that do not relate to a formal request to publish a document
(e.g., "AD is Watching") do not prevent an I-D from expiring.
[AUTHGUIDE]
3.1.2. Active
An "Active" I-D is a document that is less than six months old and
has not been updated or replaced by a newer I-D or an RFC.
The "Active" availability state is applicable to individual I-Ds and WG I-Ds. The Datatracker may also use "Active" to describe the
status of I-Ds under formal evaluation by the IESG and I-Ds in the
RFC Editor Queue. As a result, the "Active" I-D availability state
cannot be used to determine if an I-D is actively being developed by
a WG. [WGDTSPEC]
3.1.3. Replaces and Replaced By
The Datatracker uses "Replaces" and "Replaced by" to describe I-Ds
that have been renamed and subsequently resubmitted to the I-D
repository for some reason.
Two common uses of "Replaced by" are as follows:
- The filename of an individual I-D that is being considered for
adoption by a WG typically includes the name of its author (e.g., ’draft-author-wgname-topic-nn’). If the individual I-D is adopted by a WG it will be "Replaced by" a newer draft having a filename
that includes the string ’ietf-’ (e.g., ’draft-ietf-wgname-
topic-00’); when the newer WG I-D is submitted to the I-D
repository, it "Replaces" the older individual submission I-D.
- The Datatracker also uses "Replaced by" to describe the final
state of an I-D that has been published as an RFC; the I-D was
"Replaced By" the RFC.
Note that getting correct "Replaces" and "Replaced by" data into the Datatracker currently requires an explicit request by a WG Chair. Juskevicius Informational [Page 6]
Without such a request, an individual submission I-D will co-exist
with the newer WG I-D that replaces it until the individual
submission I-D eventually expires.
The Datatracker’s ability to track "Replaces" and "Replaced by"
information may need to be extended in the future to handle more
complex cases such as the following:
- Two or more I-Ds are merged into (i.e., "Replaced by") a single
I-D; in such cases, the availability status of the (one) new I-D
should indicate that the draft "Replaces" two or more older and
previously separate I-Ds; and
- One I-D is split or divided into two or more new I-Ds; in this
case the availability status should indicate that one (older) I-D was "Replaced by" two or more newer I-Ds.
3.2. IESG Document States
In addition to tracking the availability status of every I-D, the
Datatracker also maintains detailed information about the status and progression of I-Ds that have been sent to the IESG for evaluation
and publication.
All of the states used by Area Directors to indicate the status of
I-Ds under evaluation by the IESG are defined in [IESGSTAT] and are
reproduced for convenience in Appendix A.
The following subsections describe some common interactions between
three of the IESG I-D states and normal IETF WG processes. These
interactions are relevant to several of the new WG I-D states defined in Section 4.
3.2.1. Publication Requested
When a WG has determined that at least rough consensus exists within the WG to advance an I-D, progressing the document is then the
responsibility of the IESG (unless the IESG returns the I-D to the WG for further development). [RFC2418]
The "Publication Requested" state describes an I-D for which a formal request has been sent to the IESG to advance/publish the I-D as an
RFC, following the procedures specified in Section 7.5 of RFC 2418
[RFC2418]. This state does not mean that an Area Director has
reviewed the I-D or that any official action has been taken on the
I-D other than to note that its publication has been requested. Juskevicius Informational [Page 7]
Many WG drafts enter the IESG state machine for the first time via
the "Publication Requested" state. When an I-D advances through the IESG process, its IESG state will change to reflect its progress.
This said, the WG status of the I-D should not change unless an AD or the IESG sends the I-D back to the WG for further development. The
WG state of an I-D that is being progressed by the IESG is "Submitted to IESG for Publication", as defined in Section 4.2.10.
3.2.2. AD Evaluation
The "AD Evaluation" state describes an I-D that the responsible Area Director has begun to review. The purpose of the AD’s review is to
verify that the I-D is ready for advancement before an IETF Last Call is started or before the document is progressed to the IESG as a
whole.
After evaluating an I-D, the responsible AD may decide that the
document needs to be revised before it can be progressed further.
The AD may send a working group I-D back to the WG that created it
for revision.
When an AD sends an I-D back to a WG for revision, the Datatracker
will report the IESG state and substate status of the document as "AD Evaluation: Revised I-D Needed". If the required revisions are
extensive, a WG Chair may decide to change the WG state of the I-D
from "Submitted to IESG for Publication" to another WG state (e.g.,
"Waiting for WG Chair Go-Ahead" or "WG Document") for as long as it
takes the revised I-D to be developed. The IESG status of the I-D
will continue to be "AD Evaluation: Revised I-D Needed" until the
revised I-D becomes available.
3.2.3. IESG Evaluation
The "IESG Evaluation" state describes an I-D that is being formally
evaluated by the entire IESG. Every AD is able to raise any content or process issues he/she may have with the document. Issues that are blocking approval of the document are called "DISCUSS" comments. A
"DISCUSS" with serious issues may cause a WG I-D to be returned to
the WG for revision.
If the IESG sends an I-D back to a WG for more development, the
Datatracker will report the IESG state and substate of the I-D as
"IESG Evaluation: Revised I-D Needed" until a revised version of the I-D becomes available. During the time that the I-D is being
revised, the WG Chair may decide to transition the I-D from the
"Submitted to IESG for Publication" state into one of the earlier WG states (e.g., "Waiting for WG Chair Go-Ahead" or "WG Document"). Juskevicius Informational [Page 8]
4. New States and Status Annotation Tags for WG I-Ds
The status-tracking states described in Section 3 are currently
implemented in the Datatracker; however, their scope is not broad
enough to provide good visibility into the WG status of any I-D.
This section describes new I-D states and I-D status annotation tags that need to be added to the Datatracker to make it possible for WG
Chairs and/or their Delegates (e.g., WG Secretaries) to indicate the status and progression of the I-Ds associated with their WGs.
The WG I-D states defined in this section are a superset of the I-D
states currently used across all IETF WGs. This is not to suggest or imply that all of the WG I-D states must be used by all WG Chairs to describe the status and progression of the I-Ds associated with their WGs. Chairs may use all or just some of the document states
illustrated in Figure 1 to describe the WG status of their I-Ds as
appropriate.
4.1. Working Group I-D State Diagram
Figure 1 is a state machine diagram that illustrates all of the WG
I-D states defined in Section 4.2 of this document. The names of the WG I-D states are capitalized for clarity, and common state
transitions are indicated via the solid, dashed, and dotted lines.
The WG I-D state machine illustrated in Figure 1 is intended to be a new front-end to the IESG I-D state machine [IESGIDSM] that is
currently implemented in Datatracker.
Note that Figure 1 does not show every possible state transition. WG Chairs may move an I-D from any WG state to any other WG state as
appropriate to describe the WG status of the document. The lack of
an explicit path between two states does not mean that such a state
transition is precluded.
The first WG I-D state is "Call for Adoption by WG Issued" and its
meaning and usage are defined in Section 4.2.1.
One of several possible last states for a WG I-D is "Submitted to
IESG for Publication". This state is defined in Section 4.2.10. Juskevicius Informational [Page 9]
"I-D EXISTS": ’draft-author-wgname-topic-nn’ < - - .
: .
+---------------------------------------------------------------------+ | WG I-D State Machine | . | | v (not adopted) | | . | | CALL FOR ADOPTION BY WG ISSUED . . . . . | | . : | | . v | | v | | ADOPTED FOR ADOPTED BY WG | | WG INFO ONLY . | | : | | : | | (individual I-D "Replaced by" ’draft-ietf-wgname-topic-00’) | | : | | v | | | | DEAD WG <--------> WG DOCUMENT <--------> PARKED WG | | DOCUMENT ("Replaces" individual I-D) DOCUMENT | | . | | . ^ \ | | . / \ | | . / \ | | . v \ | | . \ | | . IN WG ---+ v | | LAST CALL | | | ’ ^ +--> WG CONSENSUS: | | ^ : WAITING FOR | | ’ v +--> WRITEUP | | ’ | | | ^ WAITING FOR | | | | ’ WG CHAIR ---+ | | | ’ GO-AHEAD v | | . | | . SUBMITTED TO IESG | | ("Revised ID Needed") - - < - FOR PUBLICATION | | | | | +---------------------------------------------------------------------+ |
v
IESG Document States
(see Appendix A)
Figure 1: WG I-D States and Common State Transitions
Juskevicius Informational [Page 10]
The Datatracker will be enhanced to automatically generate the
following two state transitions for all WG drafts:
- A version-00 I-D that conforms to the ’draft-ietf-wgname-topic-00’ file naming convention will be moved into the "WG Document" state automatically by the Datatracker when the WG Chair approves the
posting of an I-D; and
- A WG draft that is moved into the IESG state called "Publication
Requested" will automatically be moved by the Datatracker into the WG state called "Submitted to IESG for Publication".
All other WG I-D state transitions will require the WG Chairs or
their Delegates to log in to the Datatracker to manually input the
appropriate WG state to describe the WG status of an I-D.
Note that Figure 1 includes an arc from the "Submitted to IESG for
Publication" state back to the "WG Document" state. This is one
example of what may happen after an AD or the IESG as a whole sends
an I-D back to a WG for revision. The WG chair may decide that the
I-D needs further development and that it needs to return to the "WG Document" state for a while.
4.2. Working Group I-D States
The WG I-D states defined in this section are a superset of the I-D
states currently used across all IETF WGs.
All of the states described herein need to be added to the front-end of IESG state machine [IESGIDSM] that has already been implemented in the IETF Datatracker.
WG Chairs and their Delegates will be given the flexibility to use
whichever of the WG I-D states they feel to be appropriate to
describe the WG status of the I-Ds associated with their WG.
It is not suggested or implied that Chairs must use all of the I-D
states defined herein to describe the status and progression of all
I-Ds associated with their WGs; Chairs may use all of the WG I-D
states, or just some of the states.
Note that an I-D that is not associated with a WG will be in a ’Null’ state with respect to the WG state machine in Figure 1.
Juskevicius Informational [Page 11]
4.2.1. Call for Adoption by WG Issued
The "Call for Adoption by WG Issued" state should be used to indicate when an I-D is being considered for adoption by an IETF WG. An I-D
that is in this state is actively being considered for adoption and
has not yet achieved consensus, preference, or selection in the WG.
This state may be used to describe an I-D that someone has asked a WG to consider for adoption, if the WG Chair has agreed with the
request. This state may also be used to identify an I-D that a WG
Chair asked an author to write specifically for consideration as a
candidate WG item [WGDTSPEC], and/or an I-D that is listed as a
’candidate draft’ in the WG’s charter.
Under normal conditions, it should not be possible for an I-D to be
in the "Call for Adoption by WG Issued" state in more than one
working group at the same time. This said, it is not uncommon for
authors to "shop" their I-Ds to more than one WG at a time, with the hope of getting their documents adopted somewhere.
After this state is implemented in the Datatracker, an I-D that is in the "Call for Adoption by WG Issued" state will not be able to be
"shopped" to any other WG without the consent of the WG Chairs and
the responsible ADs impacted by the shopping.
Note that Figure 1 includes an arc leading from this state to outside of the WG state machine. This illustrates that some I-Ds that are
considered do not get adopted as WG drafts. An I-D that is not
adopted as a WG draft will transition out of the WG state machine and revert back to having no stream-specific state; however, the status
change history log of the I-D will record that the I-D was previously in the "Call for Adoption by WG Issued" state.
4.2.2. Adopted by a WG
The "Adopted by a WG" state describes an individual submission I-D
that an IETF WG has agreed to adopt as one of its WG drafts.
WG Chairs who use this state will be able to clearly indicate when
their WGs adopt individual submission I-Ds. This will facilitate the Datatracker’s ability to correctly capture "Replaces" information for WG drafts and correct "Replaced by" information for individual
submission I-Ds that have been replaced by WG drafts.
This state is needed because the Datatracker uses the filename of an I-D as a key to search its database for status information about the I-D, and because the filename of a WG I-D is supposed to be different from the filename of an individual submission I-D.
Juskevicius Informational [Page 12]
The filename of an individual submission I-D will typically be
formatted as ’draft-author-wgname-topic-nn’.
The filename of a WG document is supposed to be formatted as ’draft- ietf-wgname-topic-nn’.
An individual I-D that is adopted by a WG may take weeks or months to be resubmitted by the author as a new (version-00) WG draft. If the "Adopted by a WG" state is not used, the Datatracker has no way to
determine that an I-D has been adopted until a new version of the I-D is submitted to the WG by the author and until the I-D is approved
for posting by a WG Chair.
4.2.3. Adopted for WG Info Only
The "Adopted for WG Info Only" state describes a document that
contains useful information for the WG that adopted it, but the
document is not intended to be published as an RFC. The WG will not actively develop the contents of the I-D or progress it for
publication as an RFC. The only purpose of the I-D is to provide
information for internal use by the WG.
4.2.4. WG Document
The "WG Document" state describes an I-D that has been adopted by an IETF WG and is being actively developed.
A WG Chair may transition an I-D into the "WG Document" state at any time as long as the I-D is not being considered or developed in any
other WG.
Alternatively, WG Chairs may rely upon new functionality to be added to the Datatracker to automatically move version-00 drafts into the
"WG Document" state as described in Section 4.1.
Under normal conditions, it should not be possible for an I-D to be
in the "WG Document" state in more than one WG at a time. This said, I-Ds may be transferred from one WG to another with the consent of
the WG Chairs and the responsible ADs.
4.2.
5. Parked WG Document
A "Parked WG Document" is an I-D that has lost its author or editor, is waiting for another document to be written or for a review to be
completed, or cannot be progressed by the working group for some
other reason.
Juskevicius Informational [Page 13]
Some of the annotation tags described in Section 4.3 may be used in
conjunction with this state to indicate why an I-D has been parked,
and/or what may need to happen for the I-D to be un-parked.
Parking a WG draft will not prevent it from expiring; however, this
state can be used to indicate why the I-D has stopped progressing in the WG.
A "Parked WG Document" that is not expired may be transferred from
one WG to another with the consent of the WG Chairs and the
responsible ADs.
4.2.6. Dead WG Document
A "Dead WG Document" is an I-D that has been abandoned. Note that
’Dead’ is not always a final state for a WG I-D. If consensus is
subsequently achieved, a "Dead WG Document" may be resurrected. A
"Dead WG Document" that is not resurrected will eventually expire.
Note that an I-D that is declared to be "Dead" in one WG and that is not expired may be transferred to a non-dead state in another WG with the consent of the WG Chairs and the responsible ADs.
4.2.7. In WG Last Call
A document "In WG Last Call" is an I-D for which a WG Last Call
(WGLC) has been issued and is in progress.
Note that conducting a WGLC is an optional part of the IETF WG
process, per Section 7.4 of RFC 2418 [RFC2418].
If a WG Chair decides to conduct a WGLC on an I-D, the "In WG Last
Call" state can be used to track the progress of the WGLC. The Chair may configure the Datatracker to send a WGLC message to one or more
mailing lists when the Chair moves the I-D into this state. The WG
Chair may also be able to select a different set of mailing lists for a different document undergoing a WGLC; some documents may deserve
coordination with other WGs.
A WG I-D in this state should remain "In WG Last Call" until the WG
Chair moves it to another state. The WG Chair may configure the
Datatracker to send an e-mail after a specified period of time to
remind or ’nudge’ the Chair to conclude the WGLC and to determine the next state for the document.
Juskevicius Informational [Page 14]
It is possible for one WGLC to lead into another WGLC for the same
document. For example, an I-D that completed a WGLC as an
"Informational" document may need another WGLC if a decision is taken to convert the I-D into a Standards Track document.
4.2.8. Waiting for WG Chair Go-Ahead
A WG Chair may wish to place an I-D that receives a lot of comments
during a WGLC into the "Waiting for WG Chair Go-Ahead" state. This
state describes an I-D that has undergone a WGLC; however, the Chair is not yet ready to call consensus on the document.
If comments from the WGLC need to be responded to, or a revision to
the I-D is needed, the Chair may place an I-D into this state until
all of the WGLC comments are adequately addressed and the (possibly
revised) document is in the I-D repository.
4.2.9. WG Consensus: Waiting for Writeup
A document in the "WG Consensus: Waiting for Writeup" state has
essentially completed its development within the working group, and
is nearly ready to be sent to the IESG for publication. The last
thing to be done is the preparation of a protocol writeup by a
Document Shepherd. The IESG requires that a document shepherd
writeup be completed before publication of the I-D is requested. The IETF document shepherding process and the role of a WG Document
Shepherd is described in RFC 4858 [RFC4858]
A WG Chair may call consensus on an I-D without a formal WGLC and
transition an I-D that was in the "WG Document" state directly into
this state.
The name of this state includes the words "Waiting for Writeup"
because a good document shepherd writeup takes time to prepare.
4.2.10. Submitted to IESG for Publication
This state describes a WG document that has been submitted to the
IESG for publication and that has not been sent back to the working
group for revision.
An I-D in this state may be under review by the IESG, it may have
been approved and be in the RFC Editor’s queue, or it may have been
published as an RFC. Other possibilities exist too. The document
may be "Dead" (in the IESG state machine) or in a "Do Not Publish"
state.
Juskevicius Informational [Page 15]
4.3. Working Group I-D Status Annotation Tags
In addition to indicating which state a working group draft is in,
the Datatracker will allow several substate conditions to be
identified and tracked. This section defines annotation tags that
may be used to describe a condition that is affecting a WG I-D (e.g., why a document is in the state it is in) or to indicate an action
needed to progress the document.
Annotation tags do not change the WG I-D state of WG drafts.
Each of the annotation tags defined herein may be used to provide
more information about the status of any WG draft in any state, if it makes sense to do so. Each annotation tag may be used by itself, or in combination with other tags.
4.3.1. Awaiting Expert Review/Resolution of Issues Raised
This tag means that someone (e.g., an author or editor of the WG
draft, or a WG Chair) has initiated an expert review of the document and the review has not yet been completed and/or the resolution of
issues raised by the review has not yet been completed. Examples of expert reviews include cross-area reviews, MIB Doctor reviews,
security expert reviews, and IANA reviews.
WG drafts tagged with this annotation should retain the tag until the review is complete and possibly until any issues raised in the review are addressed.
4.3.2. Awaiting External Review/Resolution of Issues Raised
This tag means that someone (e.g., an author or editor of the WG
draft, or a WG Chair) has initiated some other review of the document (e.g., sent it to another Standards Development Organization (SDO)
for comments via a formal or informal liaison process), and the
review has not yet been completed and/or the resolution of issues
raised by the review has not yet been completed.
WG drafts tagged with this annotation should retain the tag until the review is complete and possibly until any issues raised in the review are addressed.
4.3.3. Awaiting Merge with Other Document
This tag means a decision has been made by someone (e.g., the
document author, editor, or the WG Chair) to merge the I-D with one
or more other I-Ds from the same (or another) working group. Juskevicius Informational [Page 16]
If the result of the merge is a new I-D having a different title,
then the old I-D may be declared as being a "Dead WG Document". In
such a case, the annotation tag should be changed from "Awaiting
Merge with Other Document" to "Other - see Comment Log" and a
description of the merge should be entered into the log for
posterity.
The Datatracker’s regular ’Replaced by’ information should also be
set for the old I-Ds to make it easier to find the new merged
document from the old documents.
If the result of the merge operation is a revision to the old I-D,
this annotation tag should be cleared when the revised (merged) I-D
is submitted to the WG.
4.3.4. Author or Editor Needed
This tag means an I-D has lost a primary author or editor, and that
further work on the I-D cannot continue in an effective or efficient manner until a new author or editor is found.
This tag should be removed after a new primary author or editor is
found.
4.3.
5. Waiting for Referenced Document
This tag means that completion of the I-D is on-hold because the
draft has a dependency on one or more other documents. A typical
example is where an I-D depends on another IETF document that has not yet progressed to a point where it may be referenced; the dependency may be on one or more documents in other IETF Working Groups or on
work in progress documents in other SDOs.
This tag should be removed after the dependency is cleared.
4.3.6. Waiting for Referencing Document
This tag means that completion of the I-D is on-hold because one or
more other documents are dependent on it, and the WG Chair wants to
submit all of the documents to the IESG (for publication)
simultaneously. This tag is the inverse of 4.3.5.
This tag should be removed after the dependency is cleared.
Juskevicius Informational [Page 17]
4.3.7. Revised I-D Needed - Issue raised by WGLC
This annotation may be used to flag an I-D that needs to be revised
to address issues raised during a Working Group Last Call. This
annotation may also be used to indicate when the I-D is in the
process of being revised.
This tag should be removed after a revised version of the I-D is
submitted to the WG.
4.3.8. Revised I-D Needed - Issue raised by AD
This annotation means the responsible AD raised one or more issues
with the I-D during "AD Evaluation" and that the AD has sent the
document back to the working group for revision. This annotation may also be used to indicate when the I-D is in the process of being
revised.
This tag should be removed after the revised version of the I-D is
submitted to the WG.
4.3.9. Revised I-D Needed - Issue raised by IESG
This annotation means that one or more IESG members had issues with
the I-D during "IESG Evaluation" and the document has been sent back to the working group for revision. This annotation may also be used to indicate that the revision to the I-D is in process.
This tag should be removed after the revised version of the I-D is
submitted to the WG.
4.3.10. Doc Shepherd Followup Underway
This annotation tag may be used to indicate that the Document
Shepherd for the WG document has begun working on the writeup
required to submit the document (to the IESG) for publication.
It is possible that too many I-Ds may arrive in a shepherd’s queue in too short a time, and the shepherd cannot create satisfactory
writeups for all of the documents simultaneously.
When this annotation tag is set, it means the Document Shepherd has
started work on the writeup for the I-D. The absence or resetting of this annotation tag for an I-D in the "WG Consensus: Waiting for
Writeup" state indicates the writeup has not yet been started, or has been put on-hold for some reason.
Juskevicius Informational [Page 18]
4.3.11. Other - see Comment Log
This annotation tag is a catch-all to indicate that someone (e.g., an author or editor of the document, the WG Chair, the Document
Shepherd) has entered one or more comments about the current status
of the I-D into the IETF Datatracker.
5. Intended Maturity Level of WG Drafts
The IESG requires a WG I-D to have an "intended maturity level"
associated with it (e.g., Informational, Proposed Standard,
Experimental) before the I-D is submitted to the IESG for evaluation and publication. This information is also often requested by IETF
participants.
I-D maturity levels were first defined in Sections 4 and 5 of RFC
2026 [RFC2026]. The names of the maturity levels in use today are:
* "Experimental"
* "Informational"
* "Best Current Practice"
* "Proposed Standard"
* "Draft Standard"
* "Standard"
* "Historic"
The Datatracker may need to be enhanced to enable WG Chairs to input and/or change the intended maturity level of a WG draft before the
I-D is sent to the IESG.
6. Security Considerations
This document does not propose any new Internet mechanisms and has no security implications for the Internet.
7. References
7.1. Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2418] Bradner, S., "IETF Working Group Guidelines and
Procedures", BCP 25, RFC 2418, September 1998.
[RFC4844] Daigle, L., Ed., and Internet Architecture Board, "The
RFC Series and RFC Editor", RFC 4844, July 2007. Juskevicius Informational [Page 19]
7.2. Informative References
[AUTHGUIDE] Housley, R., Ed. (for the IESG), "Guidelines to Authors
of Internet-Drafts", December 7, 2010,
https://www.doczj.com/doc/7c6881660.html,/ietf/1id-guidelines.txt.
[IDTRACKER] "The IETF Datatracker tool", Web Application:
https://https://www.doczj.com/doc/7c6881660.html,/, Version 3.12, February 2, 2011.
[IESGIDSM] "Diagram of Main I-D States", Web Application:
https://https://www.doczj.com/doc/7c6881660.html,/images/state_diagram.gif,
October 21, 2002.
[IESGSTAT] "Main I-D States", Web Application:
https://https://www.doczj.com/doc/7c6881660.html,/idtracker/help/state/,
Version 3.12, February 2, 2011.
[PROTO] Levkowetz, H. and Mankin, A., "Requirements on I-D
Tracker Extensions for Working Group Chairs", Work in
Progress, February 2007.
[WGDTSPEC] Juskevicius, E., "Minutes of wgdtspec BOF", Proceedings
of IETF 77, March 26, 2010,
https://www.doczj.com/doc/7c6881660.html,/proceedings/10mar/minutes/wgdtspec
8. Acknowledgments
The author would like to thank Henrik Levkowetz and Allison Mankin
for developing the original I-D [PROTO] that served as the starting
point for this document, and Alfred Hoenes for his many comments and suggestions and for articulating the need for the "Adopted by a WG"
state.
The author would also like to thank Henrik Levkowetz, Russ Housley,
Paul Hoffman, John Klensin, Pasi Eronen, Robert Sparks, Spencer
Dawkins, Mary Barnes, Glenn Parsons, Marc Blanchet, Andy Malis, and
Joel Halpern for their comments and feedback along the way.
Finally, the author also wishes to thank the IETF WG Chairs, ADs and other people who contributed their insights and suggestions in real- time during the wgdtspec BOF at IETF 77, and Lars Eggert, Tim Polk,
Robert Sparks, Adrian Farrel and Alexey Melnikov for their comments, suggestions and DISCUSS points on the penultimate draft version of
this document.
This document was initially prepared using 2-Word-v2.0.template.dot. Juskevicius Informational [Page 20]
组织部简介及职能 Company number：【WTUT-WT88Y-W8BBGB-BWYTT-19998】
设计与艺术学院团总支学生会组织部简介及职能 简介：组织部是学院党团共建工作的助手，也是学院团总支学生会工作的重要组成部门，具体负责全院团支部的思想建设和组织建设，不断加强对各班团员青年的思想政治教育工作，及时解决各班团支部建设中存在的问题，从而有效组织和指导各团支部开展学校团委和学院团工委的各项活动。组织部在长期的工作过程中逐渐形成了严谨、高效、规范、创新的工作作风。 职能：日常工作和特色活动。 日常工作 1、做好团员发展工作，按时收缴团费，做好团员证的注册、补办以及团组织关系转入（出）。 2、召开团支书例会，及时下达学习文件及有关指示精神，引导和监督各年级团支部认真开展团组织活动。 3、了解团员的思想、工作情况，及时做好反馈工作并对团员进行思想教育和纪律教育，并编写学期初的思想动态。 4、负责对各班的团干部进行考察和培训，提高其素质和工作能力，做到权责分明，指导他们认真、切实地开展团支部活动，以及协助党代表开展本班团支部的党建工作。
5、优秀团员、团干部、团支部以及优秀党员、党代表的评选表彰:每学期都要对各团支部以及党代表的工作予以考核评比,对于表现突出的组织和个人给予表彰。 特色活动 1.优秀学生座谈会，旨在让各位同学在新学期伊始，大家就回家的所见，所闻，所感，所想进行交流。以促进同学之间的相互了解，和同学之间的友谊。为大家进行思想碰撞提供绝佳的机会。 2.团日活动，及时了解各位同学在生活，学习中遇到问题。以便尽快解决。我们还会就一些热点问题展开讨论。给大家交流提供机会。 除了以上几项基本工作以外，组织部始终坚持为广大同学服务，贡献的坚定信念，尽我所能与其他各部门鼎力合作，共同完成团总支学生会的工作。总之，组织部的行动中贯穿着哪个地方需要“组织”就去哪里的“方针”，颇有管家的风范。
组织部工作职责范文 干部工作岗位职责 第一条、负责贯彻执行和结合实际研究制定选拔任用干部的标准、程序，做好区管科级干部的推荐、考核、任免、调配等工作的准备、材料收集、材料归档； 第二条、负责科级后备干部的选拔、培养、管理工作，拟定选拔培养科级后备干部规划，建立后备 __和档案，做好科级后备干部的选拔、考核、调整、补充、审批、呈报工作，及时提出后备干部工作的建议和意见，切实抓好后备干部队伍建设； 第三条、负责处级后备干部信息的选拔、培养、管理工作，并做好有关工作；及时将后备干部登记表，考察材料、民主推荐情况、民主评议情况、考核情况、培养和奖惩情况等，按照干部管理权限，对后备干部材料实行统一管理。实现管理工作的规范化、科学化。 第四条、负责抓好领导班子和领导干部的思想作风建设，以加强和改进思想工作作风为重点，以增强各级领导班子的创造力、凝聚力、战斗力为目标，加强思想教育，推进制度建设，解决突出问题，营造良好环境，努力塑造领导班子和干部队伍新形象，总结推广加强领导班子建设的典型经验；
第五条、负责领导班子宏观管理工作，贯彻党的干部工作方针政策，并按要求研究制定干部工作方面的办法和规定； 第六条、负责领导班子民主生活会以及质量测评工作，认真做好准备，广泛征求基层干部群众和社会各界对领导班子及成员的意见和建议，对征求到的意见要进行认真梳理和反馈，确保区级领导班子民主生活会质量； 第七条、负责科级干部选拔任免向市委组织部备案工作，按照市部要求，保证上报表格和材料达到完整、准确、及时、全面的要求； 第八条、负责干部挂职锻炼工作，根据干部培养和工作的实际需要，拓宽干部挂职锻炼选派渠道，丰富挂职锻炼的形式和内容，积极探索干部挂职锻炼的长效机制，促进干部挂职锻炼选派管理工作的制度化、规范化； 第九条、负责抓好干部人事制度改革工作，干部工作的宣传报道以及干部信息、资料收集、综合、上报和反馈工作，承担部领导交办的文稿草拟和其他工作。 第十条、完成部领导交办的其他工作。
大学生组织部1分钟自我介绍 大学生组织部1分钟自我介绍篇一 尊敬的同学们： 大家好！能站在这里参加学生会的竞选，我很高兴也很激动，更要感谢大家对我的支持和信任，谢谢大家。我首先作一下自我介绍，我叫陈然，来自大一（1）班，是（1）班班长、体育委员及治安部大一负责人之一。 泰戈尔有句话：“天空中没有鸟的痕迹，但我已飞过。”而我想说：“天空中没有鸟的痕迹，但我正在飞翔”。我想成为学生会组织部的一员，希望在同学们的协助下，我相信我可以把学生会的工作做得更好、更出色。我是一个十分有上进心人的，任何事不做则已，做则一定做好。俗话说：“海阔凭鱼跃，天高任鸟飞”。 作为我自己，我需要一个更广阔的空间来展示自己的能力。“欲穷千里目，更上一层楼”，只有站得更高才会看得更远，我希望这次加入学生会组织部是我进步的台阶，我更希望贡献自己微薄的力量，协助学生会组织部搞好各项工作。 相信我，相信您的眼光。我愿意为学生会尽我所能。最重要的，我喜欢这里！ 谢谢！ 大学生组织部1分钟自我介绍篇二
尊敬的学院领导，你们好！ 我自愿申请加入学校学生会组织部，这对于我来说是一次鞭策与提高，也是对我的一次锻炼和考验，我申请加入这个组织，并力争为学校教学管理做出自己的一份贡献。 我认为学院纪检工作责任很大，它是学院的重要管理组织，不仅担任学院学生会其他工作的开展监督检查督促等职能，更能以自己的表率作用促进学校的管理工作上新台阶，更能激发学生的学习热情，使他们养成良好的习惯，使学生的精神面貌发生新的变化。 因此，它对于促进学院学生的管理工作有着重要的意义。可以说学院纪检工作是学院管理工作的重中之中，是管理之基，是服务之本，因此我申请加入这个组织。 如果我加入这个组织，我将感到无上光荣，我将严格要求自己，模范遵守学院各项纪律和规定，对照标准找差距，使自己的自身素质的提高，端正学习的态度，树立远大的理想，树立正确的人生观，价值观，珍惜时间，刻苦学习，做遵守纪律的榜样，做认真学习的榜样，为学院实现更大的发展，为学院创造新的辉煌做出自己的贡献，我将从现在起向这一目标奋进，请学院领导批准我的请求。
设计与艺术学院团总支学生会组织部简介及职能 简介：组织部是学院党团共建工作的助手，也是学院团总支学生会工作的重要组成部门，具体负责全院团支部的思想建设和组织建设，不断加强对各班团员青年的思想政治教育工作，及时解决各班团支部建设中存在的问题，从而有效组织和指导各团支部开展学校团委和学院团工委的各项活动。组织部在长期的工作过程中逐渐形成了严谨、高效、规范、创新的工作作风。 职能：日常工作和特色活动。 日常工作 1、做好团员发展工作，按时收缴团费，做好团员证的注册、补办以及团组织关系转入（出）。 2、召开团支书例会，及时下达学习文件及有关指示精神，引导和监督各年级团支部认真开展团组织活动。 3、了解团员的思想、工作情况，及时做好反馈工作并对团员进行思想教育和纪律教育，并编写学期初的思想动态。 4、负责对各班的团干部进行考察和培训，提高其素质和工作能力，做到权责分明，指导他们认真、切实地开展团支部活动，以及协助党代表开展本班团支部的党建工作。
5、优秀团员、团干部、团支部以及优秀党员、党代表的评选表彰:每学期都要对各团支部以及党代表的工作予以考核评比,对于表现突出的组织和个人给予表彰。 特色活动 1.优秀学生座谈会，旨在让各位同学在新学期伊始，大家就回家的所见，所闻，所感，所想进行交流。以促进同学之间的相互了解，和同学之间的友谊。为大家进行思想碰撞提供绝佳的机会。 2.团日活动，及时了解各位同学在生活，学习中遇到问题。以便尽快解决。我们还会就一些热点问题展开讨论。给大家交流提供机会。 除了以上几项基本工作以外，组织部始终坚持为广大同学服务，贡献的坚定信念，尽我所能与其他各部门鼎力合作，共同完成团总支学生会的工作。总之，组织部的行动中贯穿着哪个地方需要“组织”就去哪里的“方针”，颇有管家的风范。
（一）办公室（信访办公室） １、协助部领导综合协调、处理本部政务和日常事务，做好内部科室协调、对外联系和接待工作，负责部内的保卫、内务管理、后勤服务等工作； 2、负责会议组织、秘书事务、文电处理、文书档案管理和机要保密工作； 3、负责本部信访工作，负责财务的综合管理和协调工作，搞好本部办公用品的购买和固定资产的登记管理，以及协调车辆管理调度等工作； 4、负责印章的保管和使用； 5、负责修订部内管理的有关规章制度并组织实施； 6、承办本部机构编制、干部人事、老干部服务和党群工作，完成部领导交办的其他工作。 电话: 传真： （二）研究室 1、负责全县组织系统调研工作，负责有关干部管理和党建工作的理论探讨、政策研究工作，及时调查了解党的基层组织建设、干部工作和人才工作情况，为部领导决策提供建议和方案； 2、承担或参与综合性报告、总结、重要文件和领导讲话稿的起草工作；
3、负责全县组工信息的编发和上报工作； 4、制定研讨课题，指导各乡镇党委的调研工作。 电话: 传真： （三）组织科 1、负责全县基层组织建设的宏观指导和管理； 2、指导各镇党的组织的领导班子建设和换届选举； 3、指导乡镇（社区）和县直单位领导班子召开民主生活会； 4、负责党员教育、管理与发展工作的宏观指导； 5、承办党员组织的关系转移手续和党费的管理； 6、负责全县党组织、党员统计和分析工作； 7、负责全县党员教育和发展新党员工作的宏观管理的指导。 电话: 传真： （四）干部科（公务员管理科） 1、按照干部管理权限、负责对股级以上领导干部的考察、考核、任免、调配工作及办理退休、工资和职级待遇的审批手续，负责股级干部的备案审查和审批等工作； 2、负责全县各级后备干部的培养、考察工作； 3、指导全县各级领导班子的思想政治作风建设。 （五）干部监督科（举报中心） 1、负责县管干部的监督审查工作；
欧洲标准E N简介 WTD standardization office【WTD 5AB- WTDK 08- WTD 2C】
欧洲标准E N简介 1.欧洲标准化委员会CEN（European Committee for Stadardization）简介 为了适应欧洲共同市场采用统一标准的需要，1951年欧洲炼钢联盟ECSC（European Coal and Steel Community）成立，两年之后钢铁产品术语协调委员会COCOR （Coordinating Commission for the Nomenclature of Iron and Steel Products）产生。 在随后30年过程中COCOR率其工作组（其成员由ECSC成员国的标准委员代表组成，具体负责钢分类和产品工作）编制了涉及面很广的钢铁标准手册，它不但有术语标准，还有关于钢产品的尺寸、质量和试验方法的协调统一标准，称为欧洲煤钢联标准 ——EURONORM S ，然而ECSC成员国并没有义务一定要采用EURONORM S 。多数情况下，各 成员国在本国范围里仍采用各自的标准。60年代初由欧洲经济联盟EES（European Economic Community）和欧洲自由贸易联盟EFTA（European Free Trade Association）的成员国国家标准团体成立了欧洲标准化委员会CEN和欧洲电工标准化委员会CENLEC（European Committee for Electrotechnical Standardization）其分工恰似国际标准化组织ISO和国际电工标准化组织IEC，他们既要协调成员国之间的标准和制订区域性标准，又要在国际场合下维护本地区的利益。其与ECSC不同的是，它的成员国必须无条件采用这两个组织颁布的欧洲标准Ens(European Standards)作为本国标准。 二、CEN的组织机构
组织部简介 一．部室性质 组织部是一个严谨的部门，起纽带作用，是协调团委加强全院共青团思想建设、组织建设及共青团干部的培养和管理的重要职能部门。 组织个团支部开展活动，并负责做好团干部量化考核工作、鉴定工作，组织开展团员年度考评及团内评优评先等工作。 二．工作要求 认真负责，忠于职守，严谨高效，务实创新 三．部室风气 团结进取，积极热情 四．部室宗旨 知行合一，行胜于言 五．工作简介 1．熟练掌握全院各团支部的基本情况，了解基层团组织的活动，组织生活、团总支委员等情况。 2.组织并监督各团支部按时优质的开展团日活动（如团支部风采大赛、校风校纪建设月等）。 3．加强组织建设领导管理各团支组织部的相关工作。 4．负责团干部思想政治教育工作，定期了解团干部的思想状况。 5．制定落实团学干部培训计划，培训方式以培训教育工作积极开展。 6．负责做好团干部量化考核工作、鉴定工作，组织开展团员年度考评及团内评优评先工作。 7．做好团员证的注册和管理工作，做好团员登记、团费收缴、团员组织关系转接等工作。 8．负责各团支部“推优”（推荐优秀团员入党）并完成各团支部党员发展对象的申报、审核、确定等工作。 9．负责我院入党积极分子的培训教育以及积极分子党课考试工作。 10．配合各党支部、团支部做好党员、团员的档案建立和管理工作，做好组织工作中的各种数据统计和材料收集以及党费的收缴工作。 11. 协助党支部组织开展党员民主生活会以及党内评优评先工作，进行监督及时做好汇总和报告工作。 12. 协助党支部进行党员组织活动，组织生活工作.
13．负责新生团支部的建立，高年级班委换届及班委的调动等工作。 14．在需要时，及时协同配合其它部室开展工作。 15．完成团委交办的其它任务。 六．部室成员： 由1名部长，2名副部长，6名干事组成。
校团委组织部简介与工作职责 校团委组织部，是负责全校共青团员思想教育、各级团组织的建设及各级团干培养和考核的职能部门。主要工作为加强基层团组织建设和团员教育管理，完善各项规章制度，进行团籍管理；推进以团校培训暨各级团干培训为核心的基层团干部的培训管理及考核; 提高基层团干部及校级学生干部的政治、思想道德素质和工作能力；组织、协调、配合校团委内部各项活动；对院系团委各部门工作进行监督和考核，制定校团委部门评优制度以及组织全校团组织的先进集体和先进个人的评选；负责业余党校的工作和推荐优秀团员作为党的发展对象的工作（简称＂推优＂）． 组织部在长期的工作过程中积淀形成了“务实、规范、开拓、奉献、团结、创新、严谨、高效＂这样独具特色的组织文化，同时，注意科学管理方法的运用，积极推进目标化管理、项目化管理、规范化管理和人性化管理，是一支具有很强战斗力和凝聚力的团的骨干队伍。目前下设；秘书处、组织处和团务处。各处室间协调配合，共同推动组织部各项工作的开展。
院团委组织部为你创造一个交流的平台，关注你的成长；为你提供一个发展的机遇，期待你的成熟。今天，你与“组织＂有约，明天，成功将与你有约。 院团委组织部的工作职责为： 1、执行团委例会制度，定期召开组织部、分团委组织部门会议，传达学院党委和团的文件精神，布置落实组织工作。 2、制定学期团的组织生活计划，指导各级团组织过好团的组织生活，做好考核并及时组织交流总结。 3、负责对院团委委员、分团委主要团干的考核与管理，加强对全院各级团干部的培养、指导和考察，定期办好团干培训班（团校）。 4、抓好团内奖惩工作。及时掌握团员中的先进典型并做好评优表彰工作；对违纪团员及时进行批评教育及处理，受理团员申诉。 5、定期做好发展新团员工作，办理超龄团员离团手续。 6、搞好团员登记、团籍注册和统计工作，收缴团费，接转团组织关系，协助做好团籍档案管理工作。
市委组织部机构职能 机构职能 市委组织部是市委主管组织工作和干部工作的综合职能部门。 （一）研究和指导党组织特别是党的基层组织建设，探索和指导各类新的经济组织中党组织的设置和活动方式，研究和提出党内生活制度建设的意见，协调、规划和指导党员教育工作和党建理论研究，主管党员的管理和发展工作。 （二）提出各县（区）和市直各部门以及其他列入市委管理的领导班子调整、配备的意见和建议，负责市管干部的考察和办理任免、工资、待遇、退（离）休审批手续，指导领导班子的思想政治建设，负责各县（区）、乡镇和市直机关科级干部的备案审查和宏观管理工作，承办相关干部的调配、交流、挂职及安置事项。 （三）研究制订干部队伍建设的意见，组织落实培养选拔中、青年干部和后备干部、妇女干部及党外干部工作。 （四）从宏观上研究和指导党的组织制度和干部人事制度的改革，制订或参与制订组织、干部、人事工作的重要制度。 （五）综合指导党的机关，人大、政协机关，群众团体和民主党派机关参照执行（管理）国家公务员制度的工作。 （六）负责组织、干部工作的检查督促，了解反映犯有严重错误干部的审查和调查工作等。及时向市委反映重要情况，提出建议。 （七）主管干部教育工作。制订干部教育工作的规划，对各县（区）和市直单位的干部培训工作进行协调、指导、检查，组织市管干部和一定层次干部的培训。
（八）参与制订知识分子政策。负责知识分子工作的检查、指导、综合、协调。负责市管优秀专家和拔尖人才的选拔管理。 （九）负责全市计算机干部信息，多媒体干部音像资料收集、管理及报送工作。 （十）负责退（离）休干部工作的宏观管理。 （十一）承办市委和上级组织部门交办的其他事项。 科室职能 内设机构及职能： （一）秘书科 主管本部机要、秘书、信访、文印、文书，负责本部会务组织、文电处理、文件审核及归档、督办检查和机关保密工作，负责本部的人事、工资福利、劳动保险、医疗、计划生育及本部退休人员管理、慰问工作，负责本部的财务、物资、房产、车辆、卫生管理和接待等工作，办理部领导交办事宜。 （二）调研科 负责全市党的组织建设和干部工作有关方针、政策的综合研究，调查了解市管各级领导班子和干部队伍建设的情况，为部领导决策提供意见和方案，承担干部人事制度改革的综合研究和宏观指导，协调、指导全市组织部门的调研信息工作，主办部刊《惠州组工通讯》，负责组织、干部工作的宣传报道以及本部信息、资料收集、综合、上报和反馈工作，承担部领导交办的文稿草拟和其他工作。 （三）组织科 研究和指导农村党组织的建设，研究和提出农村党员队伍建设的意见，协
目次 1、ITU介绍 (2) 1.1 ITU的历史和组成 (2) 1.2 ITU的结构 (2) 1.3 ITU-R研究组结构 (2) 1.4 ITU-R SG5的组成 (3) 1.5 ITU-R WP 5D (3) 1.5.1 ITU-R WP 5D介绍 (3) 1.5.2 ITU-R WP5D在2008年7月会议后的最新组成 (3) 1.5.3 各组工作范围和职责 (4) 1.6 ITU与3GPP关系 (4) 2 3GPP组织介绍 (5) 2.1 3GPP介绍 (5) 2.2 3GPP工作范围和目标 (5) 2.3 合作伙伴及成员 (6) 2.4 与其他标准组织的关系 (7) 2.4.1 与3GPP2&Wimax的关系 (7) 2.4.2 与其他标准组织的关系 (7) 2.5 3GPP主要工作成果 (7) 2.6 内部组织结构 (7) 2.7 各组工作范围和职责 (9) 2.8 3GPP工作方法流程 (10) 3 3GPP2 (11) 3.1 3GPP2介绍 (11) 3.2 3GPP2组织结构 (11) 4 CCSA (12) 4.1 简介 (12) 4.2 组织结构 (13) 4.3 TC5介绍及组织结构 (13)
1、ITU介绍 1.1 ITU的历史和组成 ITU（International Telecommunication Union）是电信界最权威的标准制定机构，简称国际电联，成立于1865年5月，1947年10月成为联合国的一个专门机构，总部设在瑞士日内瓦。 经过100多年的变迁，1992年12月改革后的ITU下设电信标准部门（ITU-T）、无线电通信部门（ITU-R）、电信发展部门（ITU-D）。每个部门下设多个研究组（Study Group）。每个研究组下设多个工作组（Working Group或Working Party）。 ITU成员由各国电信主管部门组成，也接纳经主管部门批准的从事电信的企业和研究机构参与。 ITU现在由189个成员国,620个行业成员,100合作成员组成。 1.2 ITU的结构 ITU为了便于无线电管理和协调，人为把世界分为三个区域，包括： ◆Region1：由欧洲、俄罗斯、中亚、西亚和非洲组成，主要的区域组织为欧洲的 CEPT，标准制定由欧洲的ETSI完成； ◆Region2：由南北美洲组成，主要的区域组织为CITEL，但美国的FCC起较大作 用； ◆Region3：由东亚、东南亚、南亚、伊朗和大洋州组成，主要的区域组织例如中 国CCSA、日本ARIB。 1.3 ITU-R研究组结构 Study Group 1(SG 1)-Spectrum management ?Working Party 1A(WP 1A)-Spectrum engineering techniques ?Working Party 1B(WP 1B)-Spectrum management methodologies and economic strategies ?Working Party 1C(WP 1C)-Spectrum monitoring Study Group 3(SG 3)-Radiowave propagation ?Working Party 3J(WP 3J)-Propagation fundamentals ?Working Party 3K(WP 3K)-Point-to-area propagation ?Working Party 3L(WP 3L)-Ionospheric propagation and radio noise ?Working Party 3M(WP 3M)-Point-to-point and Earth-space propagation Study Group 4(SG 4)-Satellite services ?Working Party 4A(WP 4A)-Efficient orbit/spectrum utilization for FSS and BSS ?Working Party 4B(WP 4B)-Systems, air interfaces, performance and availability objectives for FSS,BSS and MSS, including IP-based applications and satellite news gathering ?Working Party 4C(WP 4C)-Efficient orbit/spectrum utilization for MSS and RDSS
组织部简介 一.部室性质 组织部是一个严谨的部门，起纽带作用，是协调团委加强全院共青团思想建设、组织建设及共青团干部的培养和管理的重要职能部门。 组织个团支部开展活动，并负责做好团干部量化考核工作、鉴定工作，组织开展团员年度考评及团内评优评先等工作。 二.工作要求 认真负责，忠于职守，严谨高效，务实创新 三.部室风气 团结进取，积极热情 四.部室宗旨 知行合一，行胜于言 五.工作简介 1. 熟练掌握全院各团支部的基本情况，了解基层团组织的活动，组织生活、团总支委员等情况。 2. 组织并监督各团支部按时优质的开展团日活动（如团支部风采大赛、校风校纪建设月等）。 3 .加强组织建设领导管理各团支组织部的相关工作。 4 .负责团干部思想政治教育工作，定期了解团干部的思想状况。 5 .制定落实团学干部培训计划，培训方式以培训教育工作积极开展。 6 .负责做好团干部量化考核工作、鉴定工作，组织开展团员年度考评及团内评优评先工作。 7 .做好团员证的注册和管理工作，做好团员登记、团费收缴、团员组织关系转接等工作。 8 .负责各团支部“推优”（推荐优秀团员入党）并完成各团支部党员发展对象的申报、审核、确定等工作。 9 .负责我院入党积极分子的培训教育以及积极分子党课考试工作。 10 .配合各党支部、团支部做好党员、团员的档案建立和管理工作，做好组织工作中的各种数据统计和材料收集以及党费的收缴工作。 11. 协助党支部组织开展党员民主生活会以及党内评优评先工作，进行监督及时做好汇总和报告工作。
13 .负责新生团支部的建立，高年级班委换届及班委的调动等工作。 14 .在需要时，及时协同配合其它部室开展工作 15 .完成团委交办的其它任务。 六?部室成员： 由1名部长，2名副部长，6名干事组成。
作者：未知文章来源：本站收集点击数：3250 UL：美国保险商实验所Underwriters Laboratories UL成立于1894年，它是美国最具权威的保险机构。UL标准有五分之三为美国国家标准(ANSI)采用。其前身是美国火灾保险商协会。 UL主要制定安全标准，下设电气、防盗、事故、防火和船舶工程部，以及消费者咨询委员会，负责UL标准的制定工作。UL在国内外从事对各种设备、系统和材料的安全试验与检查，以确定对生命财产是否存在危险，并将检查结果公之于各保险公司、政府机构及其他组织。经检查合格者，发给UL质量标志。UL标志已在许多国家通行。 在标准化工作方面，UL与许多组织都有协作关系，如：ANSI、ASTM等。 IS O国际标准化组织 International Organization for Standardization 国际标准化组织是世界上最大的非政府性标准化专门机构，它在国际标准化中占主导地位。ISO制定国际标准。IS O的主要活动是制定国际标准，协调世界范围内的标准化工作，组织各成员国和技术委员会进行情报交流，以及与其他国际性组织进行合作，共同研究有关标准化问题。 随着国际贸易的发展，对国际标准的要求日益提高，ISO的 作用也日趋扩大，世界上许多国家对ISO也越加重视。 ISO的目的和宗旨是：在世界范围内促进标准化工作的发展，以利于国际物资交流和互助，并扩大在知识、科学、技术和经济方面的合作。 IEC：国际电工委员会 International Electro technical Commission IEC是世界上成立最早的非政府性国际电工标准化机构，是联合国经社理事会(ECOSOC)的甲级咨询组织。目前IE C成员国包括了绝大多数的工业发达国家及一部分发展中国家。这些国家拥有世界人口的80%，其生产和消耗的电能占全世界的95%，制造和使用的电气、电子产品占全世界产量的90%。 IEC的宗旨：促进电工标准的国际统一，电气、电子工程领域中标准化及有关方面的国际合作，增进国际间的相互了解。 ANSI：美国国家标准学会American National Standards Institute 美国国家标准学会是非赢利性质的民间标准化团体，但它实际上已成为美国国家标准化中心，美国各界标准化活动都围绕它进行。通过它，使政府有关系统和民间系统相互配合，起到了政府和民间标准化系统之间的桥梁作用。 ANSI协调并指导美国全国的标准化活动，给标准制定、研究和使用单位以帮助，提供国内外标准化情报。同时，又起着行政管理机关的作用。 BSI：英国标准学会 British Standards Institution 英国标准学会(BSI)是世界上最早的全国性标准化机构，它不受政府控制但得到了政府的大力支持。 BSI制定和修订英国标准，并促进其贯彻执行。 BSI不断发展自己的工作队伍，完善自己的工作机构和体制，把标准化和质量管理以及对外贸易紧密结合起来开展工作。 BSI的宗旨： 1.为增产节约努力协调生产者和用户之间的关系，促进生产，达到标准化（包括简化）。 2.制定和修订英国标准，并促进其贯彻执行。 3.以学会名义，对各种标志进行登记，并颁发许可证。 4.必要时采取各种行动，保护学会利益。
校团委组织部简介 校团委组织部，是负责全校共青团员思想教育、各级团组织的建设及各级团干培养和考核的职能部门。主要工作为加强基层团组织建设和团员教育管理，完善各项规章制度，进行团籍管理；推进以团校培训暨各级团干培训为核心的基层团干部的培训管理及考核; 提高基层团干部及校级学生干部的政治、思想道德素质和工作能力；组织、协调、配合校团委内部各项活动；对院系团委各部门工作进行监督和考核，制定校团委部门评优制度以及组织全校团组织的先进集体和先进个人的评选；负责业余党校的工作和推荐优秀团员作为党的发展对象的工作（简称“推优”）． 组织部在长期的工作过程中积淀形成了“务实、规范、开拓、奉献、团结、创新、严谨、高效”这样独具特色的组织文化，同时，注意科学管理方法的运用，积极推进目标化管理、项目化管理、规范化管理和人性化管理，是一支具有很强战斗力和凝聚力的团的骨干队伍。 在这个队伍里，你能找到一种家的感觉。在这个大家庭里，不仅仅是工作是服务，在这里是历练是学习是为体现本身价值，是为追求理想丰富自己，是为让你接下来的大学生活中多出一次贡献的机会，是为在今后的人生旅途中更好地做自己做更好的自己积累经验...也许是为了也仅仅为了自己的选择赋予的最神圣的使命—责任！ 校团委组织部为你创造一个交流的平台，关注你的成长；为你提供一个发展的机遇，期待你的成熟。
校团委组织部的工作职责 1、执行团委例会制度，定期召开组织部、分团委组织部门会议，传达学院党委和团的文件精神，布置落实组织工作。 2、制定学期团的组织生活计划，指导各级团组织过好团的组织生活，做好考核并及时组织交流总结。 3、负责基层团干的考核与管理，加强对全院各级团干部的培养、指导和考察以及基层团组织的年度考核、信息统计工作。 4、抓好团内奖惩工作。及时掌握团员中的先进典型并做好评优表彰工作；对违纪团员及时进行批评教育及处理，受理团员申诉。 5、定期做好发展新团员工作，办理超龄团员离团手续。 6、搞好团员登记、团籍注册和统计工作，收缴团费，接转团组织关系，协助做好团籍档案管理工作。 7、负责团内推优工作，协助有关部门做好业余党校学员的推荐工作。 8、按有关规定和院党委要求，有计划地开展推荐优秀团员作为党的发展对象工作，同时做好入党积极分子的建档和管理工作。 9、负责起草、汇编、修订团内管理的有关规定、制度和办法。 10、完成书记交办的其它工作。
ISO ISO是（International Organization for Standardization）的简称，是目前世界上最大、最有权威性的国际标准化专门机构。其成员由来自世界上117个国家和地区的国家标准化团体组成,代表中国参加ISO的国家机构是中国国家技术监督局(CSBTS)。 ISO的宗旨是在世界范围内促进标准化及有关工作的发展，以利于国际物资交流和服务，并推动各国在科学、技术和经济活动中的相互合作。其主要活动是制定和出版ISO标准，协调世界范围的标准化工作，组织各成员国和技术委员会进行情报交流，以及与其他国际组织进行合作，共同研究有关标准化问题。 ISO制定的标准内容涉及广泛,从基础的紧固件、轴承各种原材料到半成品和成品,其技术领域涉及信息技术、交通运输、农业、保健和环境等。每个工作机构都有自己的工作计划，该计划列出需要制订的标准项目(试验方法、术语、规格、性能要求等)。 ISO与国际电工委员会(IEC)有密切的联系，中国参加IEC的国家机构也是国家技术监督局。 IEC IEC是国际电工委员会（International Electrotechnical Commission）的简称，成立于1906年，它是世界上成立最早的国际性电工标准化机构，负责有关电气工程和电子工程领域中的国际标准化工作。总部设在瑞士日内瓦。 IEC的宗旨是，促进电气、电子工程领域中标准化及有关问题的国际合作，增进国际间的相互了解。目前，IEC的工作领域已由单纯研究电气设备、电机的名词术语和功率等问题扩展到电子、电力、微电子及其应用、通讯、视听、机器人、信息技术、新型医疗器械和核仪表等电工技术的各个方面。IEC标准已涉及了世界市场中35%的产品。 IEC标准的权威性是世界公认的。IEC每年要在世界各地召开一百多次国际标准会议，世界各国的近10万名专家在参与IEC的标准制订、修订工作。IEC 现在有技术委员会(TC)89个；分技术委员会(SC)107个。IEC标准在迅速增加，1963年只有120个标准，截止到2000年12月底，IEC已制定了4885个国际标
附件1： 团学组织各部门职能简介 团委 一、组织部 1.负责新老生团组织关系的接收，转移工作，规范团员证、团徽管理，统一各基层团支部的团员证注册工作。进行全院基层团组织团员情况统计调查，作好团员资料的整理和保管工作。 2.负责团费的收缴工作。 3.负责开办团员培训班，对青年积极分子进行培养、教育，作好发展新团员工作，办理新团员的审批手续、考察工作。 4.协助作好年度评优工作，进行优秀团支部、优秀团干及优秀团员的评比工作。 5.协助党组织做好入党积极分子的培养、考察工作，推荐优秀团员作党的发展对象。 6.对团的组织生活提出计划和建议，指导和督促基层团组织开展活动，定期对基层团支部书记进行考核、检查，加强组织纪律性；进行团员教育评议和思想教育培训，安排布置团内理论学习和考核，定期进行检查、督促。 7.按照校团委指示开展各项活动。 二、宣传部 1.负责宣传党委及上级团委的主体思想,执行其思想传达任务。 2.负责学部团委内部的思想统一、思想推进。 3.负责学部内部各级团组织活动的设计、组织、安排和进行，完成各团学组织活动计划及新闻稿的改写工作。 4.通过学部主页和微博等形式对内、对外宣传学部的时政思想和工作方针。（备注：有一定网页管理基础者优先。）
学生会 一、秘书处 秘书处是一个以书面文字工作为主，负责学生会成员培训工作，在学生会起到枢纽作用的部门，其主要工作职能是： 1.负责部内协调和部校学生会联络工作； 2.负责起草学生会章程、总结及规章制度等文件； 3.负责财务管理； 4.负责公文流转与存档； 5.负责组织安排学生会例会、制作周工作历、做好会议记录； 6.负责接待和会务； 7.负责采购与管理办公设备、用品和纪念品，管理固定资产； 8.负责学生会办公室的日常管理以及防火、安全和卫生工作； 9.负责学生会的日常工作，如通知、资料收集等。 二、学研部 学研部主要以围绕“营造良好的学习风气，共建良好学习氛围”这一主题开展工作，其主要工作职能是： 1.负责组织部内各项科技竞赛活动，并做好参赛选手的选拔和培训工作； 2.负责组织、选拔学生作品参加部、校各级大学生科技创新类活动及竞赛； 3.负责组织开展学生科技成果展等宣传活动，营造热爱科研、投身创新和奋发学习的校园文化氛围； 4.负责部内学生科技赛事级别认定和获奖学生的表彰工作。 三、宣传部 宣传部的工作主要是围绕着“打造部会精品，宣传品牌活动”的主题展开的，其主要工作职能是： 1.负责活动前横幅、海报的制作。 2.负责对所举办活动进行宣传造势，对内鼓舞学生积极投入，对外充分展示本学部及学生蓬勃向上的精神风采。 3.组织并开展摄影培训、pop字培训等创新活动 四、生活部 生活部主要是协助学部有关部门做好学生宿舍、学习的管理工作，其主要工
标准化组织介绍 本文档为个人总结了国际上主要的标准化组织。 有助于全面了解标准化组织的组成，标准分类等。 希望能对读者有帮助。 分类： ?国际标准化组织 ?地区性的标准化组织 ?专业性的通信标准化组织 国际标准化组织IEC/ISO/ITU IEC 国际电工委员会（International Electrotechnical Commission） IEC的宗旨是促进电工、电子领域中标准化及有关方面问题的国际合作，增进相互了解。为实现这一目的，出版包括国际标准在内的各种出版物，并希望各国家委员会在其本国条件许可的情况下，使用这些国际标准。IEC的工作领域包括了电力、电子、电信和原子能方面的电工技术。现已制订国际电工标准3000多个。 IEC对于电磁兼容方面的国际标准化活动有着特殊重要的作用。承担研究工作的主要是电磁兼容咨询委员会(ACEC)、无线电干扰特别委员会(CISPR)和TC77。 IEC与通信有关的技术委员会主要有：
TC1 名词术语； TC3 信息结构、文件和图形符号； TC46 通信和信号传输用电缆、电线、波导、RF连接器和附件；TC48电子设备机电组成和机械结构； TC77 电器设备(包括网络)之间的电磁兼容性； TC81 雷击防护； TC100 音频、视频和多媒体系统与设备； TC103 无线电通信的发射设备； TC 108 视频、音频、信息技术和通信技术领域内的电子设备安全；CISPR 无线电干扰国际特别委员会； ISO/IEC JTC 1 ISO/IEC信息技术联合委员会； ISO/IEC JTC 1/SC 6 系统间电信和信息交换； ISO/IEC JTC 1/SC 25 信息技术设备互连； JTC 1/SC 27 IT安全技术； JTC 1/SC 29 视频、图象、多媒体和超媒体信息的译码； JTC 1/SC 36 学习、教育和培训用信息技术。
组织部简介及职能 Prepared on 24 November 2020
设计与艺术学院团总支学生会组织部简介及职能 简介：组织部是学院党团共建工作的助手，也是学院团总支学生会工作的重要组成部门，具体负责全院团支部的思想建设和组织建设，不断加强对各班团员青年的思想政治教育工作，及时解决各班团支部建设中存在的问题，从而有效组织和指导各团支部开展学校团委和学院团工委的各项活动。组织部在长期的工作过程中逐渐形成了严谨、高效、规范、创新的工作作风。 职能：日常工作和特色活动。 日常工作 1、做好团员发展工作，按时收缴团费，做好团员证的注册、补办以及团组织关系转入（出）。 2、召开团支书例会，及时下达学习文件及有关指示精神，引导和监督各年级团支部认真开展团组织活动。 3、了解团员的思想、工作情况，及时做好反馈工作并对团员进行思想教育和纪律教育，并编写学期初的思想动态。 4、负责对各班的团干部进行考察和培训，提高其素质和工作能力，做到权责分明，指导他们认真、切实地开展团支部活动，以及协助党代表开展本班团支部的党建工作。
5、优秀团员、团干部、团支部以及优秀党员、党代表的评选表彰:每学期都要对各团支部以及党代表的工作予以考核评比,对于表现突出的组织和个人给予表彰。 特色活动 1.优秀学生座谈会，旨在让各位同学在新学期伊始，大家就回家的所见，所闻，所感，所想进行交流。以促进同学之间的相互了解，和同学之间的友谊。为大家进行思想碰撞提供绝佳的机会。 2.团日活动，及时了解各位同学在生活，学习中遇到问题。以便尽快解决。我们还会就一些热点问题展开讨论。给大家交流提供机会。 除了以上几项基本工作以外，组织部始终坚持为广大同学服务，贡献的坚定信念，尽我所能与其他各部门鼎力合作，共同完成团总支学生会的工作。总之，组织部的行动中贯穿着哪个地方需要“组织”就去哪里的“方针”，颇有管家的风范。
UL：美国保险商实验所Underwriters Laboratories UL成立于1894年，它是美国最具权威的保险机构。UL标准有五分之三为美国国家标准(ANSI)采用。其前身是美国火灾保险商协会。UL主要制定安全标准，下设电气、防盗、事故、防火和船舶工程部，以及消费者咨询委员会，负责UL标准的制定工作。UL在国内外从事对各种设备、系统和材料的安全试验与检查，以确定对生命财产是否存在危险，并将检查结果公之于各保险公司、政府机构及其他组织。经检查合格者，发给UL质量标志。UL标志已在许多国家通行。在标准化工作方面，UL与许多组织都有协作关系，如：ANSI、ASTM等。IS国际标准化组织查询International Organization for Standardization 国际标准化组织是世界上最大的非政府性标准化专门机构，它在国际标准化中占主导地位。ISO制定国际标准。ISO的主要活动是制定国际标准，协调世界范围内的标准化工作，组织各成员国和技术委员会进行情报交流，以及与其他国际性组织进行合作，共同研究有关标准化问题。随着国际贸易的发展，对国际标准的要求日益提高，ISO的作用也日趋扩大，世界上许多国家对ISO也越加重视。ISO的目的和宗旨是：在世界范围内促进标准化工作的发展，以利于国际物资交流和互助，并扩大在知识、科学、技术和经济方面的合作。IEC：国际电工委员会查询International Electro technical Commission IEC是世界上成立最早的非政府性国际电工标准化机构，是联合国经社理事会(ECOSOC)的甲级咨询组织。目前IEC成员国包括了绝大多数的工业发达国家及一部分发展中国家。这些国家拥有世界人口的80%，其生产和消耗的电能占全世界的95%，制造和使用的电气、电子产品占全世界产量的90%。IEC的宗旨：促进电工标准的国际统一，电气、电子工程领域中标准化及有关方面的国际合作，增进国际间的相互了解。ANSI：美国国家标准学会American National Standards Institute 美国国家标准学会是非赢利性质的民间标准化团体，但它实际上已成为美国国家标准化中心，美国各界标准化活动都围绕它进行。通过它，使政府有关系统和民间系统相互配合，起到了政府和民间标准化系统之间的桥梁作用。ANSI协调并指导美国全国的标准化活动，给标准制定、研究和使用单位以帮助，提供国内外标准化情报。同时，又起着行政管理机关的作用。BSI：英国标准学会查询British Standards Institution 英国标准学会(BSI)是世界上最早的全国性标准化机构，它不受政府控制但得到了政府的大力支持。BSI制定和修订英国标准，并促进其贯彻执行。BSI不断发展自己的工作队伍，完善自己的工作机构和体制，把标准化和质量管理以及对外贸易紧密结合起来开展工作。BSI的宗旨：1.为增产节约努力协调生产者和用户之间的关系，促进生产，达到标准化（包括简化）。2.制定和修订英国标准，并促进其贯彻执行。3.以学会名义，对各种标志进行登记，并颁发许可证。4.必要时采取各种行动，保护学会利益。DIN：德国标准化学会查询Deutsches Institut fur Normung DIN是德国的标准化主管机关，作为全国性标准化机构参加国际和区域的非政府性标准化机构。DIN是一个经注册的私立协会，大约有6000个工业公司和组织为其会员。目前设有123个标准委员会和3655个工作委员会。DIN于1951年参加国际标准化组织。由DIN和德国电气工程师协会(VDE)联合组成的德国电工委员会(DKE)代表德国参加国际电工委员会。DIN还是欧洲标准化委员会、欧洲电工标准化委员会(CENELEC)和国际标准实践联合会(IFAN)的积极参加国。AFNOR:法国标准化协会法国标准化协会是一个公益性的民间团体，也是一个被政府承认，为国家服务的组织。它接受标准化专署领导，负责标准的制、修订等工作。JIS：日本工业标准调查会查询Japanese Industrial Standard 日本工业标准调查会成立于1946年2月，隶属于通产省工业技术院。它由总会、标准会议、部会和专门委员会组成。标准会议下设29个部会，负责审查部会的设置与废除，协调部会间工作，负责管理调查会的全部业务和制定综合计划。各部会负责最后审查在专门委员会会议上通过JIS标准草案。专门委员会负责审查JIS标准的实质内容。ASME：美国机械工程师协会查询American Society of Mechanical Engineers 美国机械工程师协会成立于1881年12月24日，会员约693000人。ASME主要从事发展机械工