My view is that any protocol parameter should be in a registry, so it is easy to go to ONE location and see what's up. Especially if the list of allowed parameters might be changed/updated in updates to the RFC you are writing.
paf
On Dec 18, 2004, at 20:58, Cullen Jennings wrote:
There is the beginning of yet another debate on the SIMPLE mailing list
about do we need an IANA registry from some fields in a specific draft.
There does not seem to be a clear opinion on when to create a registry or
not and past activities are not 100% consistent. I'm sure this has come up
many times before. Are there some things I should go read that help shed
light on this?
Could the IAB give any advice here? Is it good to use IANA just as a
convenient place to go find links to all the RFC you might need to know
about? Should we only have a registry only if there is a real possibility to
two values being allocated to two different things (when the value was
supposed to be unique). Who can is in a good position to help sort this out
IAB? IESG? Other?
Thanks, Cullen
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf
Attachment:
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf