Re: [Nea] IESG query re Expert Review
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nea] IESG query re Expert Review



Stephen Hanna wrote:

Alexey Melnikov (APP AD) has provided many useful comments
on PA-TNC and PB-TNC. One issue that he has raised is
whether Expert Review should be required for IANA registration
of vendor-specific values in the NEA registries and, if so,
what the expert guidelines should be. Alexey has asked the
NEA WG to reconsider and discuss this matter. Therefore,
I'm raising this topic on the NEA list and cc'ing Alexey.
I am actually don't have a strong opinion on this, but I want to make sure that the WG has considered consequences of the choice.

The text in draft-ietf-nea-pb-tnc-05.txt on this matter
is in section 7.1:
For all of the IANA registries defined by this specification, new values are added to the registry by Expert Review with Specification Required, using the Designated Expert process defined in RFC 5226 [3]. This section provides guidance to designated experts so that they may make decisions using a philosophy appropriate for these registries.

[snip]

All values in these IANA registries MUST be documented in a specification that is clear, permanently and publicly available, and likely to ensure interoperability. IETF standard values MUST be useful and not harmful to the Internet. Designated experts should encourage vendors to avoid defining similar but incompatible values and instead agree on a single IETF standard value. However, it is beneficial to document existing practice.
I will let Alexey make the full case for removing the requirement
for expert review of vendor-specific values. I think that the main
thrust of the argument is that we should encourage vendors to
document the values that they use.
Indeed.

The situation I have in mind is as follows: Assume a vendor A implements some vendor specific attributes. The implementation becomes widespread and other implementations would like to implement it as well. Then somebody not working for vendor A convinces an A's representative to register the attributes as a favor to the community. The A's representative tries to do that, but either the documentation is not quite clear on some details, or it is not always interoperable. At this point the registration procedure says that the expert should reject the registration. The A's representative doesn't feel obligated to fix documentation, because the registration was submitted as a service to the community. So, would rejecting the registration in such a case be worse than registering something which is not perfect?

If the WG group agrees that this might be a problem, then there are 2 ways to fix this: a). you update the text to relax instructions for the designated Expert Reviewer
or
b). the WG can select an Expert Reviewer who is quite relaxed about the rules and would be flexible about allowing not-fully-compliant vendor specific registrations. In this case you don't need to change the document, but there is a small risk that the designated expert wouldn't be as flexible.

Best Regards,
Alexey


Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.