Last Call: draft-bryan-metalink (The Metalink Download Description Format) to Proposed Standard
Anthony Bryan
we've finally reached Last Call in the IETF for the Metalink Internet Draft!
this is one of the final stages to becoming an RFC. for the next 4
weeks, we have to defend our work.
there's lots left to be done, I'll keep everyone posted
----
Last Call: draft-bryan-metalink (The Metalink Download Description
Format) to Proposed Standard
* To: IETF-Announce <ietf-announce at ietf.org>
* Subject: Last Call: draft-bryan-metalink (The Metalink Download
Description Format) to Proposed Standard
* From: The IESG <iesg-secretary at ietf.org>
* Date: Fri, 11 Dec 2009 10:59:20 -0800 (PST)
The IESG has received a request from an individual submitter to consider
the following document:
- 'The Metalink Download Description Format '
<draft-bryan-metalink-24.txt> as a Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf at ietf.org mailing lists by 2010-01-08. Exceptionally,
comments may be sent to iesg at ietf.org instead. In either case, please
retain the beginning of the Subject line to allow automated sorting.
The file can be obtained via
http://www.ietf.org/internet-drafts/draft-bryan-metalink-24.txt
IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=17661&rfc_flag=0
--
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
)) Easier, More Reliable, Self Healing Downloads
Bram Neijt
I can help, I'll voice my opinion. If anybody thinks I can do something,
I'd be happy to look into it.
Go Anthony, go!
Bram
Anthony Bryan
for those that weren't around back then, Bram is one of the
co-discoverers of metalink.
I say discover, because both of us were separately exploring similar
ideas. before me, Bram had an XML format called metalinks which
focused on hashes & p2p.
I didn't find out about him until this project had been going a year.
he was gracious enough to join forces, & the rest is history :)
>
> You received this message because you are subscribed to the Google Groups "Metalink Discussion" group.
> To post to this group, send email to metalink-...@googlegroups.com.
> To unsubscribe from this group, send email to metalink-discus...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/metalink-discussion?hl=en.
Tatsuhiro
I'll keep an eye on the mailing list.
> > --
>
> > You received this message because you are subscribed to the Google Groups "Metalink Discussion" group.
> > To post to this group, send email to metalink-...@googlegroups.com.
> > To unsubscribe from this group, send email to metalink-discus...@googlegroups.com.
Anthony Bryan
sentences about white space, and references.
we can use this
http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#extract-artwork
to extract the schema & make sure the fragments inline match up w/ the
schema in the appendix.
these changes can be seen in svn.
Anthony Bryan
mailing list below with the reason(s) why you support it.
apps-d...@ietf.org / https://www.ietf.org/mailman/listinfo/apps-discuss
On Sat, Dec 12, 2009 at 12:23 PM, Anthony Bryan <anthon...@gmail.com> wrote:
Anthony Bryan
Julian Reschke's XML issues
General Area Review Team (Gen-ART) review nits.
TT's generator text w/ ABNF. generator examples
Remove license element.
use MIME type for digital signature.
Allow one or more language elements as discussed on list
Metalink Documents MAY contain one or multiples hashes of a complete file. ...
Metalink Documents MAY also contain hashes for individual pieces of a file.
ipr="trust200902"
remove dynamic element, make it an attribute of origin element
Brian Carpenter gen-art review:
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".
Ant Bryan
The IESG has a conference every 2 weeks and metalink will be discussed
on 1/21. The IESG then votes on it. Lisa Dusseault, the Applications
Area Director, has already voted Yes.
https://datatracker.ietf.org/idtracker/draft-bryan-metalink/
25 Ballot has been issued by Lisa Dusseault [more] Lisa
Dusseault 2010-01-11
25 Placed on agenda for telechat - 2010-01-21 by Lisa Dusseault
[more] Lisa Dusseault 2010-01-11
25 Ballot has been issued by Lisa Dusseault [more] Lisa Dusseault
2010-01-11
25 New version available [more] (System) 2010-01-11
On Dec 22 2009, 5:52 pm, Anthony Bryan <anthonybr...@gmail.com> wrote:
> recent changes, due to last call & IETF responses:
>
> http://metalinks.svn.sourceforge.net/viewvc/metalinks/internetdraft/d...
>
> Julian Reschke's XML issues
> General Area Review Team (Gen-ART) review nits.
> TT's generator text w/ ABNF. generator examples
> Remove license element.
> use MIME type for digital signature.
> Allow one or more language elements as discussed on list
> Metalink Documents MAY contain one or multiples hashes of a complete file. ...
> Metalink Documents MAY also contain hashes for individual pieces of a file.
> ipr="trust200902"
> remove dynamic element, make it an attribute of origin element
>
> Brian Carpenter gen-art review:
> 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".
>
>
>
> On Wed, Dec 16, 2009 at 9:59 PM, Anthony Bryan <anthonybr...@gmail.com> wrote:
> > hi, if you are in favor of Metalink you should post on the IETF
> > mailing list below with the reason(s) why you support it.
>
> > apps-disc...@ietf.org /https://www.ietf.org/mailman/listinfo/apps-discuss
> >>https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dT...
Tatsuhiro Tsujikawa
Hash: SHA1
Ant Bryan wrote:
> just pushed out a new version with all changes during last call.
>
> The IESG has a conference every 2 weeks and metalink will be discussed
> on 1/21. The IESG then votes on it. Lisa Dusseault, the Applications
> Area Director, has already voted Yes.
>
> https://datatracker.ietf.org/idtracker/draft-bryan-metalink/
>
>
> 25 Ballot has been issued by Lisa Dusseault [more] Lisa
> Dusseault 2010-01-11
> 25 Placed on agenda for telechat - 2010-01-21 by Lisa Dusseault
> [more] Lisa Dusseault 2010-01-11
> 25 Ballot has been issued by Lisa Dusseault [more] Lisa Dusseault
> 2010-01-11
> 25 New version available [more] (System) 2010-01-11
>
I hope they vote yes! How many vote is required?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAktN2LkACgkQfoQD1dZzw2a4gwCfRH6wdMi2Afx1mFYKogVvJOfF
HmAAoIve1g6VrpqXPGnGfAQRqh+stOG4
=FnuB
-----END PGP SIGNATURE-----
Anthony Bryan
<tatsu...@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ant Bryan wrote:
>> just pushed out a new version with all changes during last call.
>>
>> The IESG has a conference every 2 weeks and metalink will be discussed
>> on 1/21. The IESG then votes on it. Lisa Dusseault, the Applications
>> Area Director, has already voted Yes.
>>
>> https://datatracker.ietf.org/idtracker/draft-bryan-metalink/
>>
>>
>> 25 Ballot has been issued by Lisa Dusseault [more] Lisa
>> Dusseault 2010-01-11
>> 25 Placed on agenda for telechat - 2010-01-21 by Lisa Dusseault
>> [more] Lisa Dusseault 2010-01-11
>> 25 Ballot has been issued by Lisa Dusseault [more] Lisa Dusseault
>> 2010-01-11
>> 25 New version available [more] (System) 2010-01-11
>>
>
> I hope they vote yes! How many vote is required?
""Yes" or "No-Objection" positions from 2/3 of non-recused ADs,
with no "Discuss" positions, are needed for approval."
we need the other ADs to vote No-Objection. we'll probably get some
Discuss votes with things to change.
you can follow the ballot here
https://datatracker.ietf.org/idtracker/ballot/3271/
Ant Bryan
update) are on the IESG agenda for 1/21.
https://datatracker.ietf.org/iesg/agenda/
from what I understand, they discuss IDs on this telechat, & possibly
vote, altho voting has already started. for metalink (
https://datatracker.ietf.org/idtracker/draft-bryan-metalink/ ) we have
4 DISCUSS votes that we will be addressing.
all the suggestions/review during this phase have been very helpful, &
are tightening this spec way up. :)
https://datatracker.ietf.org/idtracker/ballot/3271/
I think we need 10 Yes/No-Obj votes to pass...
On Jan 13, 12:30 pm, Anthony Bryan <anthonybr...@gmail.com> wrote:
> On Wed, Jan 13, 2010 at 9:29 AM, Tatsuhiro Tsujikawa
>
>
>
> <tatsuhir...@gmail.com> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
>
> > Ant Bryan wrote:
> >> just pushed out a new version with all changes during last call.
>
> >> The IESG has a conference every 2 weeks and metalink will be discussed
> >> on 1/21. The IESG then votes on it. Lisa Dusseault, the Applications
> >> Area Director, has already voted Yes.
>
> >>https://datatracker.ietf.org/idtracker/draft-bryan-metalink/
>
> >> 25 Ballot has been issued by Lisa Dusseault [more] Lisa
> >> Dusseault 2010-01-11
> >> 25 Placed on agenda for telechat - 2010-01-21 by Lisa Dusseault
> >> [more] Lisa Dusseault 2010-01-11
> >> 25 Ballot has been issued by Lisa Dusseault [more] Lisa Dusseault
> >> 2010-01-11
> >> 25 New version available [more] (System) 2010-01-11
>
> > I hope they vote yes! How many vote is required?
>
> ""Yes" or "No-Objection" positions from 2/3 of non-recused ADs,
> with no "Discuss" positions, are needed for approval."
>
> we need the other ADs to vote No-Objection. we'll probably get some
> Discuss votes with things to change.
>
> you can follow the ballot herehttps://datatracker.ietf.org/idtracker/ballot/3271/
Ant Bryan
all but 2.5 issues or so :)
soon we'll put up a -26 revision, take comments, & work with that.
On Jan 20, 1:39 pm, Ant Bryan <anthonybr...@gmail.com> wrote:
> Metalink (& my other ID, draft-bryan-http-digest-algorithm-values-
> update) are on the IESG agenda for 1/21.
>
> https://datatracker.ietf.org/iesg/agenda/
>
> from what I understand, they discuss IDs on this telechat, & possibly
> vote, altho voting has already started. for metalink (https://datatracker.ietf.org/idtracker/draft-bryan-metalink/) we have
Ant Bryan
here's what's left:
Commented by: Alexey Melnikov
Comment: [IESG Evaluation COMMENT]
5.3. Processing Foreign Markup
Metalink Processors that encounter foreign markup in a location
that
is legal according to this specification MUST NOT stop processing
or
signal an error.
Are you saying that any foreign markup "MUST be ignored"?
When unknown foreign markup is encountered in a Text Construct,
software SHOULD ignore the markup and process any text content of
foreign elements as though the surrounding markup were not present.
Can you give me an example here?
Commented by: Pasi Eronen
Comment: [IESG Evaluation DISCUSS]
- Section 7 doesn't really contain sufficient information for
interoperable signing of metalink documents. RFC 4287 Section 5 has an
example what those details should look like.
Commented by: Tim Polk
Comment: [IESG Evaluation DISCUSS]
As noted in Pasi's Discuss, the document does not contain sufficient
information to result in interoperabie digital signatures. Without
specification of a mandatory to implement MIME media type in 4.2.13.1,
families
of non-interoperable generators and processors seem inevitable.
Even with a common media type, interoperability may fail due to the
selected
cryptographic algorithms. Specifying mandatory to implement
algorithms (e.g.,
RSA with SHA-256 for signatures, SHA-256 for hashes) and reasonable
key sizes
(e.g., MUST support 2048 RSA keys) would provide some basis for
selecting
algorithms where broad interoperability is desired.
[Specification of one more SHOULDs in each case (media type, hash, and
signature algorithms) would be advantageous imho, but is not strictly
necessary. I would list this as a comment, but it would be out of
context!]
Discussion of how metalink processors handle (1) unrecognized media
types or
cryptographic algorithms and (2) legacy/marginal algorithms or key
sizes (i.e.,
MD5 or 512 bit RSA) s needed as well.
Commented by: Ralph Droms
Comment: [IESG Evaluation DISCUSS]
This is a "meta-discuss' to ask a couple of clarifying questions.
What is the purpose of the "metalink:os" element? How would an entity
use the
"metalink:os" element?
The list at http://www.iana.org/assignments/operating-system-names was
"last
updated 2009-09-28". Not a criticism, just curiosity - the list seems
incomplete (Windows XP, Vista, 7; Linux 2.6 missing?), so I'm curious
about the
utility of the list utility.
A somewhat more philosophical question, triggered by "metalink:os":
what
constitutes the contents of a "file"? For UNIX and related
filesystems, we
customarily think of a "file" as an undifferentiated linera array of
bytes.
What about line terminators? Other filesystems (please don't ask me
to try to
recall my knowledge IBM OS filesystem details from 25 years ago) may
have
internal structure information that is included in the "file" but is
not really
part of the "data".
Commented by: Alexey Melnikov
Comment: [IESG Evaluation DISCUSS]
1) The request for media type review was sent out to the ietf-types@
mailing
list. After waiting for 2 weeks for review and confirming that there
are no
significant issues raised, I will clear this part of the DISCUSS.
Ant Bryan
please check out the latest version (-28) in svn
http://metalinks.svn.sourceforge.net/viewvc/metalinks/internetdraft/
then we'll submit it soon!
Tatsuhiro Tsujikawa
Hash: SHA1
Hi!!
Ant Bryan wrote:
> as far as I can tell, all issues have been addressed.
>
> please check out the latest version (-28) in svn
> http://metalinks.svn.sourceforge.net/viewvc/metalinks/internetdraft/
> then we'll submit it soon!
>
I did small modification in section 4.2.3. The "metalink:generator"
Element. I hope it makes document better:
"""
Since token is defined in ABNF, "token is of type text" is redundant, so
removed it.
agent-version is also defined as token, simplified sentence as "Although
any token character MAY appear ...
"""
Best regards,
Tatsuhiro Tsujikawa
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAktwOT8ACgkQfoQD1dZzw2a0EQCg0dIIjGulAfw/YckGsEdWZKxw
xYsAnjZEy6mzFkN3UD405CDayNiD3U01
=ych3
-----END PGP SIGNATURE-----
Ant Bryan
On Feb 8, 11:18 am, Tatsuhiro Tsujikawa <tatsuhir...@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Ant Bryan wrote:
> > as far as I can tell, all issues have been addressed.
>
> > please check out the latest version (-28) in svn
> >http://metalinks.svn.sourceforge.net/viewvc/metalinks/internetdraft/
> > then we'll submit it soon!
>
> I did small modification in section 4.2.3. The "metalink:generator"
> Element. I hope it makes document better:
>
> """
> Since token is defined in ABNF, "token is of type text" is redundant, so
> removed it.
> agent-version is also defined as token, simplified sentence as "Although
> any token character MAY appear ...
> """
thanks, as always!
version 28 is up, with diff:
Ant Bryan
I think the issue has been addressed, so it's a matter of time before
the last AD reviews it & changes his vote.
Ant Bryan
https://datatracker.ietf.org/idtracker/ballot/3271/
Yes No-Objection Discuss Abstain
Jari Arkko [ ] [ X ] [ ] [ ]
Ron Bonica [ ] [ X ] [ ] [ ]
Ross Callon [ ] [ X ] [ ] [ ]
Ralph Droms [ ] [ X ] [ . ] [ ]
Lisa Dusseault [ X ] [ ] [ ] [ ]
Lars Eggert [ ] [ X ] [ . ] [ ]
Pasi Eronen [ ] [ X ] [ . ] [ ]
Adrian Farrel [ ] [ X ] [ ] [ ]
Russ Housley [ ] [ X ] [ ] [ ]
Cullen Jennings [ ] [ ] [ ] [ ]
Alexey Melnikov [ X ] [ ] [ . ] [ ]
Tim Polk [ ] [ X ] [ . ] [ ]
Dan Romascanu [ ] [ X ] [ ] [ ]
Robert Sparks [ ] [ X ] [ . ] [ ]
Magnus Westerlund [ ] [ X ] [ ] [ ]
"Yes" or "No-Objection" positions from 2/3 of non-recused ADs,
with no "Discuss" positions, are needed for approval.
Tatsuhiro Tsujikawa
Hash: SHA1
Ant Bryan wrote:
> The final DISCUSS vote was just changed to No-Objection! :)
>
Great!!:) Congrats everyone involved!
Best regards,
Tatsuhiro Tsujikawa
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkuGn6sACgkQfoQD1dZzw2bkNwCeNOY0X/wBX2JcOe1Sqw7LMSJs
dF8Ani0OfKD8rnr4DYm+j/H7zYnW8ZNs
=Nl1M
-----END PGP SIGNATURE-----