[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    RE: [Sip-implementors] NAT RFC and drafts
From:       "Senthilnmd" <senthilnmd () future ! futsoft ! com>
Date:       2004-10-21 7:22:48
Message-ID: 000001c4b73d$18360ce0$4f06020a () senthilnmd
[Download RAW message or body]

Hi suheel,
Kindly refer  "draft-ietf-sip-nat-01.txt ". It will give you some
information about NAT traversal in SIP.

To my understanding  in NAT travesal in SIP is

Normal senario:
" we don't have enough addresses in IPv4. here NAT comes in to the picture.
we have some(few) dummy IP(Universal) address and another(multiple)
internal(local) IP addresses with port addresses(unique). When ever a IP
packet goes out from my local IP (with port address) to out world the IP
header will be changed by manipulating my local IP and port address to
generate the IP address(universal) in such a way that when I get a return
packet the same inverse algorithm will be applied to find the local IP with
port address. This will be port translation"

ALG :: Application level gateway.

Consider if we have some IP address in payloads ALG`s will be applied to
change the IP`s present in the payload with the manipulated IP(universal)
address.
Eg:: DNS as payload in IP

Kindly share your ideas or info you have and correct me if I am wrong as I
am also new to this arena.

Best Regards,
Retbin and SenthilNathan

-----Original Message-----
From: sip-implementors-bounces@cs.columbia.edu
[mailto:sip-implementors-bounces@cs.columbia.edu]On Behalf Of
suheelh@nc.rr.com
Sent: Thursday, October 21, 2004 6:55 AM
To: sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] NAT RFC and drafts

My current project requires NAT functionality in the sip stack. I am new to
NAT in SIP. Can anyone point me to basic RFCs/drafts to get started?

thanks
-suheel

-----------------
Suheel Hussain



***************************************************************************
This message is proprietary to Future Software Limited (FSL)
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.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************


[prev in list] [next in list] [prev in thread] [next in thread]