Re: [Ecrit] Ivo's review of draft-ietf-ecrit-ecall-15 - Issue 7

[Christer Holmberg <[e-mail]>]

Hi,

>> >>  >  ISSUE 7

>> >>  >

>> >>  >  section 6 - "The IVS then attaches an updated MSD to a SIP

>> >>  >     INFO request and sends it within the dialog." - what is meant by

>> >>  > "attaching MSD to SIP INFO request"?

>> >>

>> >>  I think that's made abundantly clear in the multiple earlier

>> >> instances in the  same section that say "as a MIME body part".

>> >

>> >  I do not really know what "attach body to SIP request"  means.

>> > Likely, other readers will not know it either.

>> >

>> >  A reference to a section defining how to "attach body to SIP request"

>> > would help.

>>

>> It's the same section, just a little bit before.

>

>I assume you refer -19 text stating: "[RFC7852] establishes a general mechanism for attaching blocks of

>   data to a SIP emergency call."



I think we could say something like:

“[RFC7852] provides the general guidelines for including emergency call related data in SIP messages”

Then, wherever the text talks about “attaching” data to a SIP message, you use similar terminology:

E.g.,

   "encoding it per Annex A of EN 15722 [msd] and attaching it to a SIP
   message as a MIME body part per [RFC7852].”

…becomes:

   "encoding it per Annex A of EN 15722 [msd] and including it in a SIP
   message as a MIME body part per [RFC7852]. "

Regards,

Christer