Thanks for the review. I will fix the nits. You did understand that this is the mechanism by which an IoT device makes an emergency call when the device doesn’t have two way interactive media, right? Brian > On Mar 2, 2020, at 2:48 PM, Gonzalo Salgueiro via Datatracker <noreply@xxxxxxxx> wrote: > > Reviewer: Gonzalo Salgueiro > Review result: Ready with Nits > > Document: draft-ietf-ecrit-data-only-ea-21 > Review result: Ready with Nits > Review type: iotdir - Last Call review > Requested version for review: Current > Review Date: 2020-03-02 > Reviewer: Gonzalo Salgueiro > > I am the assigned IoT directorate reviewer for <draft-ietf-ecrit-data-only-ea>. > These comments were written primarily for the benefit of the Internet Area > Directors. Document editors and shepherd(s) should treat these comments just > like they would treat comments from any other IETF contributors and resolve > them along with any other Last Call comments that have been received. For more > details on the IoT Directorate, see > https://datatracker.ietf.org/group/iotdir/about/ > > This document describes (1) how method of including a CAP message in a SIP > transaction by defining it as a block of "additional data" as well as (2) > describes how a SIP MESSAGE transaction can be used to send a non-interactive > call. I have reviewed this document from the IoT perspective and the document > appears to be informative, clear and without obvious technical gaps. There are > just a few the authors might consider addressing. > > Nits: > ==== > > S: Abstract > > "type of interactions" -> "types of interactions" > > S:1 > > "alert specific" -> "alert-specific" > > S:9 > > "Location specific" -> "Location-specific" > > S:9 > > "Note that none of the security mechanism in this document" -> "Note that none > of the security mechanisms in this document" > > > -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
