Re: [Sip-implementors] P-Access-Network-Info Header

2016-02-10 Thread Basu Chikkalli
Thanks a lot. Even I feel anchoring node should validate the "access-type"/"access-class". and check the length of the "access-info". Thanks Basu On Wed, Feb 10, 2016 at 12:57 PM, Amardeep wrote: > Hi Basu, > > Yes, PVNI header must needed to be validated by Anchoring node. > For LTE., eNode o

Re: [Sip-implementors] P-Access-Network-Info Header

2016-02-09 Thread Amardeep
Hi Basu, Yes, PVNI header must needed to be validated by Anchoring node. For LTE., eNode or for WIFI AP/elec must validate PVNI header if it same which is assigned to user during boot process. Thanks, Amar Sent from my iPhone > On 10-Feb-2016, at 10:47 am, ankur bansal wrote: > > Hi Basu >

Re: [Sip-implementors] P-Access-Network-Info Header

2016-02-09 Thread ankur bansal
Hi Basu PANI header coming from UA will be having all information in this header from the access network where UA has latched to during bootup and got IP connectivity .So PANI header is most specific to UA rather than any proxy or AS. Now whether AS should consider PANI or not depends upon if AS