Requirements for an IETF Draft Submission Toolset
RFC 4228
Document | Type |
RFC - Informational
(December 2005; No errata)
Was draft-ietf-tools-draft-submission (individual in gen area)
|
|
---|---|---|---|
Author | Alex Rousskov | ||
Last updated | 2013-03-02 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4228 (Informational) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Brian Carpenter | ||
Send notices to | (None) |
Network Working Group A. Rousskov Request for Comments: 4228 The Measurement Factory Category: Informational December 2005 Requirements for an IETF Draft Submission Toolset Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This document specifies requirements for an IETF toolset to facilitate Internet-Draft submission, validation, and posting. Table of Contents 1. Introduction ....................................................2 2. Scope ...........................................................2 3. Notation and Terminology ........................................3 4. Status Quo ......................................................4 5. Overall Toolset Operation .......................................6 6. Upload Page .....................................................9 7. Check Action ....................................................9 7.1. Preprocessing .............................................10 7.2. Processing ................................................11 7.3. Storage ...................................................11 7.4. Extraction ................................................12 7.5. Validation ................................................13 7.5.1. Absolute Requirements ..............................14 7.5.2. Desirable Features .................................15 7.5.3. DoS Thresholds .....................................17 7.5.4. WG Approval ........................................17 8. Check Page .....................................................18 8.1. External Meta-Data ........................................19 9. Post Now Action ................................................20 9.1. Receipt Page ..............................................20 10. Adjust Action .................................................21 11. Adjust Page ...................................................21 12. Post Manually Action ..........................................22 13. Receipt Page ..................................................22 Rousskov Informational [Page 1] RFC 4228 ID Submission Toolset: Requirements December 2005 14. Bypassing the Toolset .........................................22 15. Email Interface ...............................................23 16. Implementation Stages .........................................25 17. Testing .......................................................26 18. Security Considerations .......................................27 19. Compliance ....................................................27 Appendix A. Comparison with Current Procedures ....................28 Appendix B. Acknowledgements ......................................29 Normative References ..............................................30 Informative References ............................................30 1. Introduction Public Internet-Drafts are the primary means of structured communication within the IETF. Current Internet-Draft submission and posting mechanisms hinder efficient and timely communication while creating an unnecessary load on the IETF Secretariat. The IETF Tools team recommends formalization and automation of the current mechanisms. This document contains specific automation requirements. The IETF Secretariat and many IETF participants have long been proponents of automation. This document attempts to reflect their known needs and wishes, as interpreted by the Tools team. 2. Scope The Draft Submission Toolset discussed in this document is about getting a single new version of an Internet-Draft from an IETF participant to the IETF draft repository. A single draft version may include several formats, and dealing with those formats is in scope for the Toolset. Definition and sources of draft meta-information (to be used in Secretariat databases and elsewhere) are in scope. Submitter authentication and submission authorization are in scope. Draft posting may result in various notifications sent to interested parties. While this document recommends a subset of notification targets, details of notifications are out of scope. Creation of new drafts or new draft versions as well as manipulation, visualization, and interaction with the drafts already in the repository are out of scope. Draft expiration and archiving of old draft versions are out of scope. The set of requirements in this document is not meant to be comprehensive or final. Other IETF documents or procedures mayShow full document text