Re: [Sip] Conclusion of WGLC, Call for IETF Last Call on sip-dhcpv6
Jonathan Rosenberg <jdrosen@dynamicsoft.com> Tue, 28 May 2002 17:04 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25022 for <sip-archive@odin.ietf.org>; Tue, 28 May 2002 13:04:50 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA29716 for sip-archive@odin.ietf.org; Tue, 28 May 2002 13:05:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA28056; Tue, 28 May 2002 12:44:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA28030 for <sip@optimus.ietf.org>; Tue, 28 May 2002 12:44:34 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24283 for <sip@ietf.org>; Tue, 28 May 2002 12:44:09 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.70]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g4SGj2YH025130; Tue, 28 May 2002 12:45:02 -0400 (EDT)
Message-ID: <3CF3B3AC.48C27A59@dynamicsoft.com>
Date: Tue, 28 May 2002 12:43:24 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
CC: sip@ietf.org, rohan@cisco.com, brian.rosen@marconi.com, jo@ipdialog.com, hgs@cs.columbia.edu
Subject: Re: [Sip] Conclusion of WGLC, Call for IETF Last Call on sip-dhcpv6
References: <004801c201b8$8b4f1060$1d036e3f@TXDWILLIS2>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>
X-BeenThere: sip@ietf.org
Content-Transfer-Encoding: 7bit
One comment. One of the things we need to be striving for is to move everything consistently towards the usage of loose routing for sending requests through intermediate hops. This has countless benefits, primarily derived from the ability to associate parameters and other information with the loose route URI. A local outbound proxy is most definitely a hop that can be specified with a loose route. So, while bis does allow a UAC to simply send requests to a configured IP/FQDN rather than use loose routing, it recommends loose routing. So, my question is this: why don't we specify that the DHCP option provides you a URI that is used as a loose route, and not a domain name/IP address? Wouldn't that handle v6,v4 domain names and everything else? Also, I suspect that in many cases, local outbound proxies will be doing compression. How does the client know whether it can send compressed sip messages to its proxy? Well, we have a URI parameter for this purpose: http://search.ietf.org/internet-drafts/draft-camarillo-sip-sigcomp-00.txt Thus, if the client learns about the local outbound proxy through a URI, it will be able to learn whether it supports compression. If only the address/domain name are provided, separate means are needed to learn about support for compression. Thanks, Jonathan R. Dean Willis wrote: > > We started working group last call of the sip-dhcpv6 draft on May 2. > There has been no negative veedback that I'm aware of, so let's call > WGLC complete and request IETF Last Call. > > http://search.ietf.org/internet-drafts/draft-ietf-sip-dhcpv6-00.txt > > -- > Dean > > _______________________________________________ > Sip mailing list https://www1.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol > Use sip-implementors@cs.columbia.edu for questions on current sip > Use sipping@ietf.org for new developments on the application of sip -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Avenue Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PH: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] Conclusion of WGLC, Call for IETF Last Call… Dean Willis
- Re: [Sip] Conclusion of WGLC, Call for IETF Last … Jonathan Rosenberg
- Re: [Sip] Conclusion of WGLC, Call for IETF Last … Henning Schulzrinne
- Re: [Sip] Conclusion of WGLC, Call for IETF Last … Jonathan Rosenberg
- Re: [Sip] Conclusion of WGLC, Call for IETF Last … Henning Schulzrinne
- Re: [Sip] Conclusion of WGLC, Call for IETF Last … Jonathan Rosenberg