Re: per-data option processing for statusRequest option

hi. i'm confused because you answered both your questions...

/mtr


> Consider the following scenario's: 
> 
> A. per-data option "statusRequest" is specified with
> 'this' hop as target and the message is meant for 2 or
> more recipients:
> ---------------------------------------------------------------------------------------
> ------------------------------------
> 
> <data content='cid:[email protected]'>
>   <originator identity='[email protected]' />
>   <recipient identity='[email protected]' />
>   <recipient identity='[email protected]' />
>   <option internal='statusRequest' targetHop='this'
>          mustUnderstand='true' transID='86' />
> </data>
> 
> 
> What should the relay(example.com) do while processing
> per-data option?
> 
> Does relay(example.com) remove the per-data option
> when forwarding to relay(rubble.com) as specified in
> section 5 "APEX Options"
> ...
>    	   this: the option applies to this relay, and
> must be removed prior to transmitting the containing
> element.
> ...
> 
> 
> 
> B. if relay(rubble.com) does not support
> 'statusRequest' option and since 'mustUnderstand' is
> true 
> ---------------------------------------------------------------------------------------
> -----------
> 
> Should relay(rubble.com) move to step 4 of section
> "4.4.4.1" or return an error element to the orginator.
> 
> 
> 
> According to my understanding of the protocol, If
> relay does not supports any of the option
> (mustUnderstand as true) then it should return some 
> 
> error element. If relay supports all the option
> (mustUnderstand as true) specified than it should
> return 'ok' element and later when processing 
> 
> for each recipient, should process 'per-data' option
> for each recipient depending upon the response from
> the recipients.
> 
> Any help will be appreciated....
> 
> Regards-
> Mike
> 
> 
> __________________________________________________
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
> http://launch.yahoo.com
> _______________________________________________
> APEXwg mailing list
> [email protected]
> http://lists.beepcore.org/mailman/listinfo/apexwg