Re: CAP - BEEP Profile

John Berthels wrote:

>
>
>Is the following wording any help?
>
>-------------------------
>Multiple iCal objects may be sent in a single BEEP message by either
>representing them as separate MIME text/calendar parts contained within a
>MIME multipart/mixed part or by simple concatenation within a single
>text/calendar [**] part, separated by a single blank line.
>
>In either case, all iCal objects transmitted together must have the same
>TARGET property.
>
>The sending of multipart MIME entities over BEEP is not permitted for CAP
>unless the other endpoint has indicated its ability to accept them via the
>appropriate CAPABILITY[*].
>-------------------------
>
Thanks. Much clearer.

And the 'single blank line' is not in the ABNF of 2445, so no that is 
not valid.

  icalobject = 1*("BEGIN" ":" "VCALENDAR" CRLF
                      icalbody
                      "END" ":" "VCALENDAR" CRLF)

And both are valid for recipients that allow multipart. That is you 
could send
a multipart object where one or more of the parts contained one or more 
'icalobject's.

-- 

 Doug Royer                     |   http://INET-Consulting.com 
 -------------------------------|-----------------------------
 [email protected]                 | Office: (208)612-INET
 http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                |   Cell: (208)520-4044

                We Do Standards - You Need Standards