Re: [Dime] Regarding 'P' bit setting in Diameter Header

On Thu, 2012-08-02 at 09:08 +0200, Arud Selvan Sundaramurthy wrote:
> Hi,
> 
> I  have a doubt in diameter proxy behaviour when routing  a request.
> 
>  
> 
> When diameter proxy receives a request with ‘P’ bit **NOT SET ** in
> header   , and having valid routing entry to route the request to next
> hop, will it route the request to next hop by setting the ‘P’ bit or
> will it reply will “DIAMETER_UNABLE_TO_DELIVER” as the ‘P’ bit is not
> set.  Will the proxy is allowed to modify the header in this case?

No; the value of the 'P' bit is part of the command definition and isn't
modifiable at run time.

> 
>  
> 
>  
> 
> 
> 
> As per bis draft-ietf-dime-rfc3588bis-34.txt in section 6.1.9 , it
> states
> 
> “Relay and proxy agents are not required to perform full inspection of
>    incoming messages.  At a minimum, validation of the message header
>    and relevant routing AVPs has to be done when relaying messages.”.
> 
> Does the “minimum header validation” includes checking the ‘P’ in
> header by Proxy agent also?

It actually says "At a minimum," which means 'At the very least'.

> Kindly provide your suggestion on this.
> 
>  
> 
> Thanks,
> 
> Arud selvan.S.
> 
>  
> 
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime