Metalinks / Code / Commit [r676]

Commit [r676] Maximize Restore History

Thus, a publisher can choose weak or strong cryptography, and a

Metalink Processor SHOULD normally accept that. There are potential
applications where the Metalink Processor chooses to reject weak
cryptography, but that is not envisioned as the common use case.

Authored by: antbryan 2010-05-09

Browse code at this revision

Parent: [r675]

Child: [r677]

changed	/internetdraft/rfc5854.html
changed	/internetdraft/rfc5854.txt
changed	/internetdraft/rfc5854.xml

Metalinks Code

Commit [r676] Maximize Restore History

/internetdraft/rfc5854.html Diff Switch to side-by-side view

/internetdraft/rfc5854.txt Diff Switch to side-by-side view

/internetdraft/rfc5854.xml Diff Switch to side-by-side view