Re: [core] MULTIPART-CT: A few editorial comments

[Christer Holmberg <[e-mail]>]

Hi,

   >> We need to define how the generic terms above are mapped into CoAP.
   >>
   >> For example, if you transport a "message body" in CoAP, what is the
   >> part of the CoAP message where the "message body" is conveyed?
   >>
   >> Figure 7 of RFC 7252 defines the "Payload" part of a CoAP message. I
   >> assume that is the part used to convey a "message body" associated
   >> with a MIME media type.
   > 
   > Yes - barring Block which allows fragments of the same "MIME message
   >  body" to be spread across multiple "CoAP payloads".
   
   Sure.

    >> But, MULTIPART-CT does not talk about the Payload part. It talks about
    >> "body", which is nowhere defined for CoAP. I need to know what part of
    >> a CoAP message the "body" is.
    >
    > I'm not sure multipart-ct should necessarily talk about that, no more
    > than any other MIME types should.  The mapping of resource
    > representations into CoAP frames should be explained by RFC 7252.
    
    Exactly! That is my point :)

    RFC 7252 should define/reference the generic CoAP terminology, and we should then use that terminology in the CoAP extension document.

    Only MULTIPART-CT specific terminology should be defined in MULTIPART-CT.

Regards,

Christer