I like how this is evolving ... few things
Few small things
If you use CMS, I think you need to deal with how the JSON in canonicalized
before being signed. I will suggest that the standards the IETF created for
signing JSON would be a better choice for signing JSON than CMS - that's
Hi Uri,
On 6/7/16 7:32 PM, Blumenthal, Uri - 0553 - MITLL wrote:
>
> * We now include a signature mechanism for the MUD files. It
> was always the plan to do this. There were two choices:
> CMS/PKCS#7 or JWS. Again for tooling's sake, so that people
> don't need
> * We now include a signature mechanism for the MUD files. It was always the
> plan to do this. There were two choices: CMS/PKCS#7 or JWS. Again for
> tooling's sake, so that people don't need to roll their own, especially for
> anything security related, we've gone with CMS and a detached
On Tue, Jun 7, 2016 at 9:38 AM, Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> On Tue, Jun 07, 2016 at 09:08:56AM -0700, Andy Bierman wrote:
> > On Tue, Jun 7, 2016 at 8:52 AM, Juergen Schoenwaelder <
> > j.schoenwael...@jacobs-university.de> wrote:
> >
> > > On Tue, Jun
On Tue, Jun 07, 2016 at 09:08:56AM -0700, Andy Bierman wrote:
> On Tue, Jun 7, 2016 at 8:52 AM, Juergen Schoenwaelder <
> j.schoenwael...@jacobs-university.de> wrote:
>
> > On Tue, Jun 07, 2016 at 11:26:03AM -0400, Dale R. Worley wrote:
> > > Ladislav Lhotka writes:
> > > > "Dale
Hi,
I prefer (B).
I do not think it is realistic that vendors will rewrite their IETF
modules and vendor modules and all the associated client/server
instrumentation.
This is expensive at many levels. Stability is important for an API.
So if we do (A), there will be some modules following the
On Tue, Jun 7, 2016 at 8:52 AM, Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> On Tue, Jun 07, 2016 at 11:26:03AM -0400, Dale R. Worley wrote:
> > Ladislav Lhotka writes:
> > > "Dale R. Worley" writes:
> > >> A difficulty I have with
> On 07 Jun 2016, at 17:26, Dale R. Worley wrote:
>
> Ladislav Lhotka writes:
>> "Dale R. Worley" writes:
>>> A difficulty I have with the current wording is that it doesn't point
>>> out the crucial fact about leafref that the XPath
Ladislav Lhotka writes:
> "Dale R. Worley" writes:
>> A difficulty I have with the current wording is that it doesn't point
>> out the crucial fact about leafref that the XPath expression can only
>> select elements that are instantiations of one particular
All,
We want to provide an update based on the off line discussions
related to OpState Solutions that we have been having and solicit
input from the WG.
All authors of current solution drafts [1,2,3] together with those
who helped conduct the solutions analysis* were invited to the these
On Tue, Jun 07, 2016 at 04:03:43PM +0200, Ladislav Lhotka wrote:
>
> But what if the canonical value isn't defined, e.g. when the list key is an
> identityref? It would be handy to be able to use the derived-from() function
> as a key predicate.
>
Lada,
we are at a stage where the document
> On 07 Jun 2016, at 14:47, Martin Bjorklund wrote:
>
> Ladislav Lhotka wrote:
>>
>>> On 06 Jun 2016, at 16:02, Juergen Schoenwaelder
>>> wrote:
>>>
>>> On Mon, Jun 06, 2016 at 03:43:23PM +0200, Ladislav Lhotka wrote:
Ladislav Lhotka wrote:
>
> > On 06 Jun 2016, at 16:02, Juergen Schoenwaelder
> > wrote:
> >
> > On Mon, Jun 06, 2016 at 03:43:23PM +0200, Ladislav Lhotka wrote:
> >>
> >>> On 06 Jun 2016, at 15:09, Juergen Schoenwaelder
> >>>
Juergen Schoenwaelder wrote:
> Martin, how close are we to have a final version addressing all the
> review comments we received during the journey through the IESG?
We're shrinking the list of open issues with every iteration of
emails. I will go through
"Dale R. Worley" writes:
> A difficulty I have with the current wording is that it doesn't point
> out the crucial fact about leafref that the XPath expression can only
> select elements that are instantiations of one particular data node. I
> don't know XPath, but it seems
Hi everyone,
There is a new version of draft-ietf-lear-netmod-mud out there. In
discussions with various WG chairs it seems like the best approach is to
(a) consolidate the drafts a bit and (b) proceed in opsawg with this
work. That is what this draft does. Both the PKIX constraint and the
16 matches
Mail list logo