> > The one thing I wanted to point out is that section 2.6 is going to end
> > up in the IANA registry in it's entirety, including the text about the example
> > parameter values. I think this is OK, but want to be sure nobody else thinks it
> > might confuse people into thinking all these names actually need to be
> > implemented.
> I don't think so (first sentence), and I can certainly make sure it
> doesn't when we get the IANA actions note. The intent is that the
> only thing in the registry is "addrbook" and the reference to section
> 2.6 of RFC xxxx as where the doc lives. The stuff in sec 2.6 is
> simply the documentation that has to exist, as required by the reg
> template.
> Section 4.3 says that the registry has "URN parameter name" and
> "Reference". Under "reference", it goes on to say what information
> MUST exist in the *reference*, but not in the *registry*.
OK, then is shouldn't be an issue.
Ned
_______________________________________________
sieve mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sieve
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.