Subject: [Sipping] Comments on draft-marjou-sipping-b2bua-00.txt

From: [email-masked]
Date: Tue, 12 Jun 2007 09:59:01 +0530

Hi  Marjou,

Here is few enhancements required on this draft.

1) The behavior of the Transparent B2BUA is not defined when any dialog 
info carrying SIP header is received in a Request.
        What should be the behavior of this B2BUA when an INVITE with 
Replaces(3891) is received? what about 
        Traget-Dialog?
        Currently this draft just tells that "The UAC SHOULD copy other 
header fields and body from
        the upstream request into this downstream request before sending 
it"

2) Is it correct to copy the Route headers from upstream to downstream?
        a) What about if the B2BUA has a configured pre-loaded route set?
        c) It is acting as a pure UA (B2BUA) w.r.t Record-Route header.
        b) From section 3 of this draft :  Hide topology information, for 
example in the Call-ID,
        Via, Route, Record-Route, Contact header fields.
        So copying Route headers is not so correct w.r.t Topology hiding.

Thanks & Regards,

Prince Arimboor
Senior Technical Leader
 
A R I C E N T
 
#7, 4th Floor, Sigma Softtech Park
Whitefield main Road,
Bangalore 560066, India
Main     +91 80.4106.9010
Fax      +91 80.4106.9500

***********************  Aricent- Confidential   ***********************

***********************  Aricent- Confidential   ***********************
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of 
the individual to whom it is addressed. It may contain privileged or confidential information and should not be 
circulated or used for any purpose other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for 
loss or damage arising from the use of the information transmitted by this email including damage from virus."
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP