Changes between Version 2 and Version 3 of WikiStart


Ignore:
Timestamp:
May 20, 2010, 1:41:30 PM (10 years ago)
Author:
mary.ietf.barnes@…
Comment:

Fixing formatting

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v2 v3  
    1515The process for reviewing Early documents:
    1616
    17 * The Secretary assigns a reviewer when a request comes in from an AD via the IETF chair. The assignments are typically done on Thursday evenings, along with any LC assignments.
    18 * We expect the reviewer to be done before the deadline (typically 2 weeks).
    19 * The reviewer sends the review to the Gen-ART list
    20 * The reviewer also sends the review to the AD, WG chairs & authors, and optionally to the WG mailing list.
     17 * The Secretary assigns a reviewer when a request comes in from an AD via the IETF chair. The assignments are typically done on Thursday evenings, along with any LC assignments.
     18 * We expect the reviewer to be done before the deadline (typically 2 weeks).
     19 * The reviewer sends the review to the Gen-ART list
     20 * The reviewer also sends the review to the AD, WG chairs & authors, and optionally to the WG mailing list.
    2121
    2222The process for reviewing documents at Last Call:
     
    8787The review should apply generally agreed IETF criteria, such as
    8888
    89 [RFC1958] The Architectural Principles of the Internet
    90 [RFC3426] General Architectural and Policy Considerations
    91 [RFC3439] Some Internet Architectural Guidelines and Philosophy
     89 [RFC1958] The Architectural Principles of the Internet
     90 [RFC3426] General Architectural and Policy Considerations
     91 [RFC3439] Some Internet Architectural Guidelines and Philosophy
    9292[NITS] The "I-D Nits" document maintained by the IESG
    9393[RFC2223] Instructions to RFC Authors
     
    9898
    9999Of special interest to the GEN area (because it's no area's special interest) is:
    100 * Clear description of why the document or protocol is useful to the Internet
    101 * Adherence to IETF formalities such as capitalized MUST/SHOULD (ID-Nits)
    102 * Useful and reasonable IANA considerations
    103 * Correct dependencies for normative references
    104 * That it's written in reasonably clear English
     100 * Clear description of why the document or protocol is useful to the Internet
     101 * Adherence to IETF formalities such as capitalized MUST/SHOULD (ID-Nits)
     102 * Useful and reasonable IANA considerations
     103 * Correct dependencies for normative references
     104 * That it's written in reasonably clear English
    105105
    106 Mailing List:   All reviews are posted on the IETF gen-art mailing list: https://www1.ietf.org/mailman/listinfo/gen-art
     106=== Mailing List ===
     107 All reviews are posted on the IETF gen-art mailing list: https://www1.ietf.org/mailman/listinfo/gen-art
    107108
    108 Archiving of reviews:   All reviews are also archived and publicly visible: http://www.softarmor.com/rai/temp-gen-art/
     109=== Archiving of reviews ===
     110 All reviews are also archived and publicly visible: http://www.softarmor.com/rai/temp-gen-art/
    109111