[Emailcore] Ticket #76: G.22. IANA Registration Model for Registries Other, Than Service Extensions

[Alexey Melnikov <[e-mail]>]

Dear EMAILCORE participants,

Based on discussions at the EMAILCORE 115 session, I propose the 
following changes to address this ticket. (John, feel free to wordsmith)

8.1.2. Address Literal Tags

Replace the last sentence:

OLD:

   Additional literal types require standardization before being used;

   none are anticipated at this time.

NEW:

   Additional literal types MUST be specified in a Standards-Track RFC

   before being used; none are anticipated at this time.

8.1.3.  Mail Transmission Types

Replace the 2nd sentence of the 1st paragraph:

OLD:

    Link and protocol identifiers in addition to those specified in this
    document may be registered only by standardization or by way of an
    RFC-documented, IESG-approved, Experimental protocol extension.

NEW:
    Link and protocol identifiers in addition to those specified in this
    document may be registered using the IETF Review IANA registration procedure.

The 2nd paragraph:
    An additional subregistry has been added to the "VIA link types" and
    "WITH protocol types" subregistries of this registry to contain
    registrations of "Additional-registered-clauses" as described above
    and in the subsection that follows.

Should it be moved to section 8.1.4.  Additional Registered Clauses?

8.1.4.  Additional Registered Clauses

Replace the 1st sentence of the 1st paragraph
OLD:
    As mentioned in Section 4.4.1 above, additional clauses for the
    "Received:" header field may be added by future standards track
    specifications.

NEW:
    As mentioned in Section 4.4.5 above, additional clauses for the
    "Received:" header field may be added by future IETF stream specifications.

(Section 4.4.1 doesn't say anything about additional registered clauses. Section 4.4.5 contains ABNF for it, but only contains the reference to 8.1.4 in the comment. So maybe just drop "As mentioned in Section 4.4.1 above"?)

Replace the 2nd sentence of the 2nd paragraph

OLD:
    As with link and
    protocol identifiers, additional clauses may be registered only by
    standardization or by way of an RFC-documented, IESG-approved,
    Experimental protocol extension.

NEW:
    As with link and
    protocol identifiers, additional clauses may be registered
    using the IETF Review IANA registration procedure.

Best Regards,
Alexey