Re: [sidr] draft-ietf-sidr-repos-struct to Standards Track

[Terry Manderson <[e-mail]>]

On 19/07/11 2:23 PM, "Randy Bush" <[e-mail]> wrote:

>> And I'm happy to see it written as a hint. A validated mapping should
>> come, in my opinion from something more robust which also transcends
>> the technology used in the repository.
> 
> easy.  throw away the entire structure and code to date and do it as a
> collection of tlvs.

I think there is an easier way, as already suggested. Add the object type to
the manifest in FileandHash.

1) the rescert points to the publication point and manifest
2) the manifest is mandatory
3) the manifest is signed
4) the manifest is nicely(?) readable ASN.1

Really its a much nicer and more robust solution than either throwing the
entire structure out or using filename extensions to 'mandate' file/object
content.

Then if hints, for human readable reasons, are still required then maintain
the extensions as they are as a BCP.

> 
> i suspect no one else wants to go there, at least no one with code in
> the game.

Really... that is a shame. I always thought that coders wanted to make their
code less susceptible to adverse external influence.

T.