DISCOVER: Supporting Multicast DNS Queries
draft-manning-opcode-discover-07

IANA has reviewed draft-manning-opcode-discover-06 and has the following comments:

IANA understands that, upon approval of this document, there are no IANA actions
that need to be completed. As the document is a description of an experiment in
the DNS and is intended for historical status, IANA also understands that there
are no protocol identifiers or parameters that need to be marked obsolete nor
are there any references that need to be updated.

[Note]: 'Proposing DNP note to the RFC editor because IETF standards action is required for DNS opcode allocation.  See ballot write-up for details.' added by Amy Vezza

DNP note:

    This document requires an IANA allocation of a DNS
    OpCode value for the DISCOVER message. However,
    according to RFC 2929 such allocations are via
    Standards Action only. As a result, the IESG thinks
    that this document violates IETF procedures for
    DNS OpCode allocations and should therefore not
    be published without IETF review and IESG approval
    (response 4 from RFC 3932).

[Note]: 'Proposing DNP note to the RFC editor because IETF standards action is required for DNS opcode allocation.  See ballot write-up for details.' added by Amy Vezza

[Ballot comment]
I agree with Margaret.

It might make sense to request the rfc editor to mention the exact reason for our DNP request to the author instead of the generic reponse.

[Ballot comment]
I concur with Margaret's assessment.

However, if the document were worded in such a way that the opcode assignment was described as "this is what would need to be done to make this work" (instead of "IANA, please do this") and the document were intended for Informational status, I would probably no-ob.

[Note]: 'Proposing DNP note to the RFC editor because IETF standards action is required for DNS opcode allocation.  See ballot write-up for details.' added by Margaret Wasserman

[Note]: 'Proposing DNP note to the RFC editor because IETF standards action is required for DNS opcode allocation.  See ballot write-up for details.' added by Margaret Wasserman

IANA Comments:
This document requests that the IANA assign a numeric value for the DISCOVER opcode. 
It is not clear as to which registry should this opcode be put in.  IANA needs clarification.

Original request:

From: Bill Manning
To: iesg-secretary@ietf.org, margaret@thingmagic.com, narten@us.ibm.com,
  rfc-ed@ISI.EDU
Cc: bmanning@ISI.EDU, paul@vix.com
Date: Tue, 6 Jul 2004 11:48:33 -0700 (PDT)
Subject: Request to Advance: draft-manning-opcode-discover-00.txt


Please advance this ID. It is expected to be an experimental RFC.


--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).

From: RFC Editor
To: Bill Manning
Cc: margaret@thingmagic.com, narten@us.ibm.com, paul@vix.com,
  RFC Editor
Date: Tue, 6 Jul 2004 14:37:25 -0700
Subject: Re: Request to Advance: draft-manning-opcode-discover-00.txt
User-Agent: Mutt/1.4.1i

Bill,

Thank you for your submission.  The RFC Editor has received your
proposed RFC, and will review the document.  Once the RFC Editor has
reviewed this draft, we will send it to the IESG for a 4 week timeout,
allowing the IESG time to review and comment on this effort.

You can track the progress of your document at:

  http://www.rfc-editor.org/queue.html

Please note that your document will be removed from our queue and
treated as a new submission if we send it back to you for revisions.

Thank you.

RFC Editor


On Tue, Jul 06, 2004 at 11:48:33AM -0700, Bill Manning wrote:
>
> Please advance this ID. It is expected to be an experimental RFC.
>
>
> --bill
> Opinions expressed may not even be mine by the time you read them, and
> certainly don't reflect those of any other entity (legal or otherwise).

From: RFC Editor
To: Bill Manning
Cc: margaret@thingmagic.com, narten@us.ibm.com, paul@vix.com,
  RFC Editor
Date: Tue, 6 Jul 2004 14:37:25 -0700
Subject: Re: Request to Advance: draft-manning-opcode-discover-00.txt
User-Agent: Mutt/1.4.1i

Bill,

Thank you for your submission.  The RFC Editor has received your
proposed RFC, and will review the document.  Once the RFC Editor has
reviewed this draft, we will send it to the IESG for a 4 week timeout,
allowing the IESG time to review and comment on this effort.

You can track the progress of your document at:

  http://www.rfc-editor.org/queue.html

Please note that your document will be removed from our queue and
treated as a new submission if we send it back to you for revisions.

Thank you.

RFC Editor


On Tue, Jul 06, 2004 at 11:48:33AM -0700, Bill Manning wrote:
>
> Please advance this ID. It is expected to be an experimental RFC.
>
>
> --bill
> Opinions expressed may not even be mine by the time you read them, and
> certainly don't reflect those of any other entity (legal or otherwise).