=?utf-8?B?UkU6IHF1ZXN0aW9uIGFib3V0IENsaWVudC10eXBlIE9QTiBNc2cg?=

[=?utf-8?B?RHVyaGFtLCBEYXZpZA==?= <david.durham@intel.com>]

> -----Original Message-----
> From: sunjian [mailto:jians@huawei.com]
> 
> In the COPS protocol RFC2748
> ======================================================
> 3.6 Client-Open (OPN)  PEP -> PDP
> 
>    The Client-Open message can be used by the PEP to specify 
> to the PDP
>    the client-types the PEP can support, the last PDP to which the PEP
>    connected for the given client-type, and/or client specific feature
>    negotiation. A Client-Open message can be sent to the PDP 
> at any time
>    and multiple Client-Open messages for the same client-type are
>    allowed (in case of global state changes).
>         <Client-Open>  ::= <Common Header>
>                                         <PEPID>
>                                         [<ClientSI>]
>                                         [<LastPDPAddr>]
>                                         [<Integrity>]
> =====================================================
> 
> It is said that:
>  "A Client-Open message can be sent to the PDP at any time
>    and multiple Client-Open messages for the same client-type are
>    allowed (in case of global state changes)."
> 
> The question is :
> 1. What's the mean of "in case of global state changes"
>     Does there some examples of "case"?

[Dave] There is a ClientSI object in the COPS OPN Message, this object was
intended to carry global state information, if any. As it turns out, no such
global state has ever been defined for any standard Client Types to date.
The statement above simply says *if* you had sent such global state
information in a OPN message, you can update it by simply repeating the OPN
message again with the new data.

>     Does the "state" refer to the established request handle?
[Dave] No see above.
> 
> 2.If it emphasize the word " global " then what's the 
> following process will be?
> 
> 1>
> PEP                                                     PDP
> OPN( ClientTypeA)->
>          <-CAT(ClientTypeA )
> OPN( ClientTypeA)-> ---------------------------At this point, 
> what should the
> PDP COPS do?

[Dave]  <- CAT(ClientTypeA)    (assuming the PDP still accepts the
ClientType and any global data that might be part of the updated OPN
message)

> 
> 2>
> PEP                                                     PDP
> OPN( ClientTypeA)->
>          <-CAT(ClientTypeA )
> REQ( ClientTypeA handle 1)->
>           <-DEC( ClientTypeA handle 1)
> RPT( ClientTypeA handle 1)->
> 
> REQ( ClientTypeA handle 2)->
>           <-DEC( ClientTypeA handle 1)
> RPT( ClientTypeA handle 2)->
> 
> OPN( ClientTypeA)-> ---------------------------At this point, 
> what should the
> PDP COPS do?

[Dave] <- CAT(ClientTypeA)   ... And everything else would continue as
normal. Really, there is no point in sending a repeated OPN message just for
the hellofit, but it is not an error either.
> 
> 
> Thanks
> 
> Sunjian
> 
> 
>