Re: CAP - BEEP Profile

Doug Royer <[email protected]>
Newsgroups gmane.ietf.calendar
Organization http://INET-Consulting.com
Message-ID <[email protected]>


Marshall Rose wrote:

>doug - let's focus on the core issue:
>
>  
>
>>>the bug here is that to do the "or more" part of "one or more", you must
>>>use a multipart, because each BEEP message contains either zero or one
>>>MIME objects. 
>>>      
>>>
>>   
>>Not all CUA's support multipart. So no that will not work.
>>    
>>
>    
>sorry, those are BEEP's rules. so, either you make support of multipart
>mandatory, or you do not allow requests that would require a multipart
>response if multipart isn't available.
>  
>
Not sure how that differs from what was said.

If the capability of the endpoint does not include multipart, then you can
not send multipart to that recipient. I think we agree.

I can add text that says if you get a multipart and you said "no 
multipart", then
you get a BEEP error...  Is that what you were saying, add a BEEP error?

-- 

 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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.