Re: [Dots] WGLC on draft-ietf-dots-architecture-08

["Konda, Tirumaleswar Reddy" <[e-mail]>]

> -----Original Message-----
> From: Dots <[e-mail]> On Behalf Of
> [e-mail]
> Sent: Thursday, November 29, 2018 2:01 PM
> To: Roman Danyliw <[e-mail]>; [e-mail]
> Subject: Re: [Dots] WGLC on draft-ietf-dots-architecture-08
> 
> 
> 
> Hi Roman, all,
> 
> I support this draft to be sent to the IESG for publication.
> 
> Some easy-to-fix comment, though:
> 
> (1) The document cites [I-D.ietf-dots-requirements] in may occurrences. I
> suggest these citations to be more specific, that is to point the specific REQ# or
> the section. Doing so would help readers not familiar with DOTS documents to
> easily link the various pieces.
> 
> (2) I used to point people to the DOTS architecture I-D when I receive
> comments/questions about the notion of "DOTS session" and to the
> Requirements I-D for clarification about DOTS channels. It seems that some
> clarifications are needed in the architecture I-D to explain for readers not
> familiar with all DOTS documents, for example:
> - the link with the underlying transport sessions/connections and security
> associations.
> - mitigations are not bound to a DOTS session but to a DOTS client/domain.
> 
> (3) The signal channel I-D uses "DOTS signal channel session", "DOTS signal
> channel sessions" and "DOTS data channel session" to refer to specific DOTS
> sessions. I'd like to have these terms introduced also in the arch I-D.
> 
> BTW, the signal channel uses in few occurrences "DOTS session"; those can be
> changed to "DOTS signal channel session". There is no occurrence of "DOTS
> session" in the data channel I-D.

I don't see a need to modify the "DOTS session" discussed in the signal channel draft, https://tools.ietf.org/html/draft-ietf-dots-architecture-07#section-3.1 defines the term "DOTS session". However, I agree with your comments to update the section 3.1 to add the following lines:
Mitigation requests created using a DOTS session are not bound to the DOTS session. Mitigation requests are associated with a DOTS client and can be managed using different DOTS sessions. A DOTS session is associated with a single transport connection (e.g. TCP or UDP session) and an ephemeral security association (e.g. a TLS or DTLS session). 

The DOTS signal data channel session is a mutually authenticated DOTS session between DOTS agents.

DOTS data channel draft is not using the term "DOTS data channel session", we can fix the signal channel draft to use "DOTS data channel" instead of "DOTS data channel session".

Cheers,
-Tiru

> 
> Thank you.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Dots [mailto:[e-mail]] De la part de Roman Danyliw
> > Envoyé : mardi 27 novembre 2018 23:15 À : [e-mail] Objet : [Dots]
> > WGLC on draft-ietf-dots-architecture-08
> >
> > Hello!
> >
> > Consistent with our discussion at the Bangkok meeting, we are starting
> > a working group last call (WGLC) for the DOTS architecture draft:
> >
> > DOTS Architecture
> > draft-ietf-dots-architecture-08
> > https://tools.ietf.org/html/draft-ietf-dots-architecture-08
> >
> > Please send comments to the DOTS mailing list -- feedback on remaining
> > issues or needed changes; as well as endorsements that this draft is ready.
> >
> > This WGLC will end on December 12, 2018.
> >
> > Thanks,
> > Roman and Frank
> >
> > _______________________________________________
> > Dots mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/dots
> 
> _______________________________________________
> Dots mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dots