Re: [Anima] draft-richardson-anima-ace-constrained-voucher

[Michael Richardson <[e-mail]>]

Jim Schaad <[e-mail]> wrote:
    > * In section 1 para #4 you appear to have a formatting error where a list
    > was supposed to exist.

Thanks, I fixed that in the markdown.

peter van der Stok <[e-mail]> wrote:
    >> * Section 5 - you have a return of multiple items with the same rt value.
    >> However I would not want to have to filter through the list of return
    >> values
    >> to figure out which is the "root" one.  Should this example have the
    >> rt=ace.est attribute on all of the links?

    > The example is an example and people can decide to do it differently.
    > Two alternatives:
    > - only return the root collection
    > - define additional rt values per resource
    >
    > You have a preference? I prefer the first approach

I'm not clueful about this part, and generally quite fearful about parsing
this stuff.  Sure, it's easy in Ruby, but it's the constrained C code that
I'm concerned about, so I don't understand the tradeoffs here.

    jim> * Suggest a strong recommendation on not use cmsVersion=1 to make your life
    jim> easier.

In other words: to not be PKCS7 compatible, but require CMS processing.

I think this is reasonable from a specification point of view, but there has
been pushback from people who have FIPS-140 libraries that they
have hard times getting updated.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [