[EMAIL PROTECTED] wrote:
>
> Hi,
> THe newer version of the draft which you are referring to is
> draft-ietf-sip-nat-01.txt. This addresses only issues with NAT.
> I think the issues with firewall will be addressed in a different
> draft.
The stuff in draft-ietf-sip-nat-01 will work for firewalls which
implement the policy that allows outgoing tcp or udp, with responses
back in. If a firewall blocks anything but HTTP and SMTP, then this is
for a reason and it is not the role of IETF to define specifications for
bypassing enterprise security policy. As such, there will be no specific
documents on bypassing firewalls.
> There is also a draft available, which discusses about the various
> solutions for NAT tarversal,and also gives call flows.It should be
> available at
> http://www.jdrosen.net/papers/draft-rosenberg-sipping-nat-scenarios-00.t
> xt
Also, note that the RTP traversal is the more complex problem, and is
covered in our stun and turn proposals:
http://www.ietf.org/internet-drafts/draft-rosenberg-midcom-stun-00.txt
http://www.ietf.org/internet-drafts/draft-rosenberg-midcom-turn-00.txt
> What is the current state of draft-rosenberg-sip-entfw-02.txt? How
> likely is it that persistent TCP/TLS connections will be rolled into
> 2543-bis?
They are already there, and have been for some time (since -03, I think).
-Jonathan R.
--
Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Avenue
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PH: (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
