Re: IPCP option for SIP server

James Carlson <[email protected]>
Newsgroups gmane.ietf.pppext
Message-ID <[email protected]>
Ashutosh Dutta writes:
>        Just to reiterate, there are cases where each PDSN may have a
>        different outbound proxy associated with it. Thus as the mobile
>        mobile moves between PDSNs within the same DNS domain or AAA
>        domain , it may end up getting a new outbound proxy or P-CSCF
>        (in IMS language) during each transition.

I agree that overconstrained problems are difficult to solve.

That doesn't mean that adding options to PPP is really the right
answer.

> The point I was
>        trying to make was that timing associated with outbound proxy
>        configuration should not be neglected and should be considered
>        during any handover optimization. Of course there are many ways
>        it can be done, such as make-before-break as you have
>        indicated. I was hoping if it can as well be done during the
>        PPP negotiation phase itself, but DHCP appears to be cleaner
>        solution at the moment, albeit an extra pair of message
>        exchange. 

I agree that performance is important, but I wouldn't suggest a micro-
optimization such as this (moving an option from one protocol to
another) unless we've got hard data showing that this is an important
consideration (compared to all the other issues; there's no need to
optimize away 1% of the problem) and that there aren't more global
optimizations possible.

Such as, for instance, fixing the deployment so that these SIP servers
are accessible from adjacent cells.

-- 
James Carlson, KISS Network                    <[email protected]>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

_______________________________________________
Pppext mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/pppext
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.