[Sip] Re: A Hitchhikers Guide to SIP

Jonathan Rosenberg <jdrosen@cisco.com> Sat, 22 April 2006 04:59 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FXADS-00053k-M4; Sat, 22 Apr 2006 00:59:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FXADQ-00053a-Ra for sip@ietf.org; Sat, 22 Apr 2006 00:59:28 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FXADP-0007D5-Iv for sip@ietf.org; Sat, 22 Apr 2006 00:59:28 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 21 Apr 2006 21:59:27 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.04,146,1144047600"; d="scan'208"; a="26443074:sNHT23748946"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k3M4xRvF025347; Sat, 22 Apr 2006 00:59:27 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 22 Apr 2006 00:59:26 -0400
Received: from [192.168.1.104] ([10.86.242.87]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 22 Apr 2006 00:59:26 -0400
Message-ID: <4449B82E.3030107@cisco.com>
Date: Sat, 22 Apr 2006 00:59:26 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: henry@pulver.com
References: <4uco4o$ffcqn@test-inbound-a.cisco.com>
In-Reply-To: <4uco4o$ffcqn@test-inbound-a.cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Apr 2006 04:59:26.0520 (UTC) FILETIME=[87A4E380:01C665C9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: sip@ietf.org
Subject: [Sip] Re: A Hitchhikers Guide to SIP
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

One of the challenges in this document was figuring out what is covered 
under the umbrella of SIP, and what is used by SIP but not SIP itself. 
This draft, at least, said that things in here had to be extensions to 
be considered part of SIP. ICE isn't actually a SIP extension, its an 
SDP extension.

My recollcetion is that, during the meeting, we did agree that it made 
sense to include things which were directly normatively dependent as 
well, which certainly includes SDP. ICE is questionable based on this 
criteria, but I personally would be happy to include it. Main open issue 
is really what is the criteria for inclusion in this document.

Thanks,
Jonathan R.

Henry Sinnreich wrote:

> This is an excellent document, though I wonder why ICE has been omitted in
> the list of key documents. ICE is only mentioned in a reference associated
> with RFC 2327 for SDP. See:
> 
> http://www.ietf.org/internet-drafts/draft-rosenberg-sip-hitchhikers-guide-00
> .txt
> 
> TURN is not mentioned at all.
> 
> Maybe a section on NAT traversal would be appropriate for the next version
> of the I-D.
> 
> Thanks, Henry
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.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