Re: [Rats] Question about WG Procedure -- Re: 答复: Use case -> architecture document

[Henk Birkholz <[e-mail]>]

Hi all,

I 2nd this for the first YANG module, too. +1 to Nancy's summary.

We explicitly illustrated during chartering that the architecture should 
grow and be inclusive to be able to represent the evolution of other WG 
items and be able to map solutions outside the IETF.

 From my subjective point of view today, EAT might actually have the 
least dependencies as it is intended to be quite versatile by design.

Viele Grüße,

Henk

On 16.10.19 19:21, Kathleen Moriarty wrote:
> 
> 
> On Wed, Oct 16, 2019 at 12:01 PM Nancy Cam-Winget (ncamwing) 
> <[e-mail] <mailto:[e-mail]>> wrote:
> 
>     Hi,____
> 
>     Comments below:____
> 
>     __ __
> 
>     *From: *RATS <[e-mail] <mailto:[e-mail]>>
>     on behalf of Laurence Lundblade <[e-mail]
>     <mailto:[e-mail]>>
>     *Date: *Wednesday, October 16, 2019 at 08:50
>     *To: *"Smith, Ned" <[e-mail] <mailto:[e-mail]>>
>     *Cc: *"[e-mail] <mailto:[e-mail]>" <[e-mail]
>     <mailto:[e-mail]>>, Thomas Hardjono <[e-mail]
>     <mailto:[e-mail]>>
>     *Subject: *Re: [Rats] Question about WG Procedure -- Re: 答复: Use
>     case -> architecture document____
> 
>     __ __
> 
>     __ __
> 
>         On Oct 16, 2019, at 8:13 AM, Smith, Ned <[e-mail]
>         <mailto:[e-mail]>> wrote:____
> 
>         ...____
> 
>         The original milestones suggested that the timing could lag that
>         of other drafts (that seem to address more immediate needs.)
>         Maybe that is no longer the case because of a need to agree on
>         terminology, attestation workflows or connection endpoint
>         semantics?____
> 
>     ...____
> 
>     EAT is not being held up by lack of a completed architecture
>     document. The same might be true of the yang draft. ____
> 
>     [NCW] Fully agree….and  we did state (perhaps it was during the
>     BoFs) that the architecture could be done in parallel as on several
>     occasions the architecture gets “tweaked” based on the adoption of
>     the actual schemas, protocols and interfaces adopted.____
> 
>     __ __
> 
>     i think it is still true that architecture can lag the other
>     documents.____
> 
>     __ __
> 
>     Lots of use cases already know what to do about end-end flows and
>     architecture. FIDO and Android attestation already have their flows.
>     They could use EAT without any IETF architecture document.____
> 
>     __ __
> 
>     Seems like the architecture effort is attempting a unified field
>     theory of attestation across all use cases. I think this is of
>     value, but hard to do.____
> 
>     [NCW] Abstractly, I think there is general agreement on most of the
>     roles despite the naming of the roles and how they potentially
>     fllow.  That, to me, can be the basis for the architecture, the
>     models that Dave describes are more of the interactions that define
>     the interfaces or communications between the roles.  I’m not
>     convinced yet on the hardship other  than the discussions on the
>     terminology
> 
> 
> +1 - I agree with Nancy's responses.
> 
> Best regards,
> Kathleen
> 
>     ____
> 
>     __ __
> 
>     LL____
> 
>     __ __
> 
>     _______________________________________________
>     RATS mailing list
>     [e-mail] <mailto:[e-mail]>
>     https://www.ietf.org/mailman/listinfo/rats
> 
> 
> 
> -- 
> 
> Best regards,
> Kathleen
> 
> _______________________________________________
> RATS mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rats
>