Re: [sidr] draft-ietf-sidrops-signed-tal-00

Tim: Works for me. Thanks for considering my suggestion. Russ > On Mar 27, 2018, at 5:38 AM, Tim Bruijnzeels wrote: > > Hi Russ, all, > > How about: > > OLD: > A signed TAL is an RPKI signed object, as specified in [RFC6488]. > > NEW: > The signed TAL object uses the

Re: [sidr] draft-ietf-sidrops-signed-tal-00

Hi Russ, all, How about: OLD: A signed TAL is an RPKI signed object, as specified in [RFC6488]. NEW: The signed TAL object uses the standard template for specifying signed objects that can be validated using the RPKI [RFC6488], which is based on Cryptographic Message Syntax (CMS) [RFC5652] as a

Re: [sidr] draft-ietf-sidrops-signed-tal-00

Tim: I think that a statement in Section 3 that it uses CMS SignedData [RFC5652] would make this very clear. Russ > On Mar 22, 2018, at 1:07 PM, Tim Bruijnzeels wrote: > > Hi Russ, > > Yes, this is a CMS object. Section 3 describes this. It’s an extension of > RPKI Signed

Re: [sidr] draft-ietf-sidrops-signed-tal-00

Hi Russ, Yes, this is a CMS object. Section 3 describes this. It’s an extension of RPKI Signed Object - which is CMS.- and specifies the relevant content type (3.1) and eContent (3.2). Tim > On 22 Mar 2018, at 17:02, Russ Housley wrote: > > Is the intent to use CMS to