----- Original Message ----- From: "Stephen Kent" <k...@bbn.com> To: "t.petch" <ie...@btconnect.com> Cc: "Terry Manderson" <terry.mander...@icann.org>; "Rob Austein" <s...@isc.org>; <draft-ietf-sidr-repos-str...@tools.ietf.org>; <sidr-cha...@tools.ietf.org>; <sidr@ietf.org> Sent: Saturday, July 23, 2011 3:37 PM > >... > >Given the distributed nature of the dynamic database that is RPKI, I > >would have > >thought a self identifying first line would be essential. > > > >Tom Petch > > Repository objects are not text files. They are binary (CMS). Each > object DOES begin with its context type (and OID). So, in the binary > space, we do just what you suggested. But, it is still very helpful > to make use of filename extensions, e.g., to allow different types of > RPs to filter what they retrieve.
Yes, I am well familiar with OIDs and their encoding and assume that Terry is as well, so I was endorsing what I take to be his disquiet about only using file extensions before assuming that there is an OID there and presenting it to the validation regime on the assumption that there is one to decode. Tom Petch > > Steve _______________________________________________ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr
