Re: [Sidrops] HTTPS in TALs

[Rob Austein <[e-mail]>]

I think we should move from rsync to HTTPS for fetching TALs, yes, so
I think the WG should be doing something of this general nature.

How many stages...I think at this point I would be most comfortable
with making HTTPS mandatory and rsync optional.

My own RP implementation has supported both schemes for years (albeit
only on a development branch until about a year ago).  I don't know
the status of the other RP implementations, but the authors of those
can speak for themselves.

Regarding Job's request that we change format to JSON or XML or ...,
I must respectfully disagree.  The current format was deliberately
chosen to be as simple as possible, no presentation-layer-du-jour
parsing library required.  ASN.1 is enough fun for somebody who has to
implement an RP in an embedded environment, but that is required,
because all of the objects being validated are ASN.1.  Let's please
not add a requirement for another whole parser just for TALs when the
trivial line-oriented thing we have now will suffice.