Re: Comments: draft-ietf-msgtrk-mtqp-11.txt

[ned.freed@mrochek.com]

> Ned,

> Sorry for the late comments but I just noticed a lack
> of instructions in this document.

> In the IANA Considerations section below, it mentions that
> those options that do not start with vnd must be defined
> in a standards track doc, which is fine.  What are the
> requirements for the ones that do start with vnd?  FCFS?
> Expert or WG review?

FCFS will be fine. I don't think expert review is needed given that
registration of these is only a MAY.

				Ned

> Thanks for the clarification.

> Michelle



> 10.  IANA Considerations

>      System port number XXXX - TBD by IANA

>      The service name to be registered with the Internet Assigned Number
> Authority (IANA) is "MTQP".

>      The IANA is asked to register the URI registration template found
> in Appendix A in accordance with [BCP35].

>      This document requests that IANA maintain one new registry: MTQP
> options.  The registry's purpose is to register options to this proto-
> col.  Options whose names do not begin with "vnd." MUST be defined in a
> standards track or IESG approved experimental RFC.  New MTQP options
> MUST include the following information as part of their definition:

>      option identifier
>      option parameters
>      added commands
>      standard commands affected



> Hansen                                                         [Page 18]
> 
> Internet Draft      Message Tracking Query Protocol        July 16, 2003


>      specification reference
>      discussion

>      One MTQP option is defined in this document, with the following
> registration definition:

>      option identifier: STARTTLS
>      option parameters: none
>      added commands: STARTTLS
>      standard commands affected: none
>      specification reference: RFC TBD
>      discussion: see RFC TBD

>      Additional vendor-specific options for this protocol have names
> that begin with "vnd.".  After the "vnd." would appear the reversed
> domain name of the vendor, another dot ".", and a name for the option
> itself.  For example, "vnd.com.example.extinfo" might represent a
> vendor-specific extension providing extended information by the owner of
> the "example.com" domain.  These names MAY be registered with IANA.