Document: draft-bryan-metalink-24.txt
Reviewer: Brian Carpenter
Review Date: 2009-12-21
IETF LC End Date: 2010-01-08
IESG Telechat date: 

Summary: Technically ready, but one copyright issue
--------

Major issues:
-------------

Note that the inclusion of the pre-5378 disclosure makes it unclear
whether the RelaxNG code can be licensed by the Trust in the normal way
(simplified BSD) under the current rules. It would be worth checking on this,
and maybe including some clarification beyond the standard boilerplate. If
the RelaxNG code is in fact submitted under RFC5378 conditions, i.e. is
not derived from older work, stating that fact would probably be enough.
If the code is in fact subject to RFC3978 conditions, stating that fact would
be helpful. 

Minor issues:
-------------

This is a bit picky, but section 4.1.2 contains a series of rules like
this one:

   o  metalink:file elements MAY contain exactly one metalink:copyright
      element.

Note that (if parsed rigorously according to RFC2119) this does not forbid an
element that contains more than one metalink:copyright element. To be rigorous,
you'd have to add "and MUST NOT contain more than one such element". I'm not sure
if you want to go there...

Comment:
--------

I have not checked any of the RelaxNG code from a technical viewpoint.