[Ietf-calsify] additional IANA considerations

Eliot Lear lear at ofcourseimright.com
Mon Jun 18 00:25:10 PDT 2007


Hi,

Apologies for this being in XML, but it is intended for insertion.  I 
propose the following be inserted at the top of the IANA Considerations 
section.


<t>
    This section contains initial registrations for various protocol
    elements specified in this memo, as well as a table that explains
    what is required to add a new element.  Changing or removing an
    existing element requires a standards action.  In order to add
    a new element, where marked "RFC", that specification MUST
    make use of the following template:
</t>
<figure>
<artwork>
<![CDATA[

    Protocol Element Type:
    (e.g., Component, Property, Property Parameter, etc)
    Protocol element name:
    (MUST NOT begin with "X-")
    Short Description:
    (What it is)
    Long Description:
    In what contexts are the element valid?
    (Specify, for instance, where a property would be valid)
    Does this protocol element modify other existing elements?
    If so, describe:
    (For example, if a property parameter, how does it modify the
    property?)

]]></artwork>
</figure>
<t>
    Each answer MAY contain a normative reference.  No default values
    are allowed for properties or parameters.  Implementations that
    make use of a new protocol element MUST assume that they will
    interact with implementations that do not understand it.
</t>



More information about the Ietf-calsify mailing list