Re: [Sip] SIPit 20 survey summary

"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Sun, 29 April 2007 15:19 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HiBB2-00033U-WE; Sun, 29 Apr 2007 11:19:05 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HiBB1-00033K-25 for sip-confirm+ok@megatron.ietf.org; Sun, 29 Apr 2007 11:19:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HiBB0-00033C-Oq for sip@ietf.org; Sun, 29 Apr 2007 11:19:02 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HiBAz-0004Ne-CN for sip@ietf.org; Sun, 29 Apr 2007 11:19:02 -0400
Received: (qmail 29084 invoked by uid 0); 29 Apr 2007 15:19:00 -0000
Received: from 90.187.53.37 by www111.gmx.net with HTTP; Sun, 29 Apr 2007 17:19:00 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Date: Sun, 29 Apr 2007 17:19:00 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
In-Reply-To: <17972.45384.981257.4920@tutpro.com>
Message-ID: <20070429151900.77890@gmx.net>
MIME-Version: 1.0
References: <075001c788fc$9f6a2be0$640fa8c0@cis.neustar.com> <001401c78976$5f8dc020$0601a8c0@BEMBUSTER> <17971.5486.819002.96466@tutpro.com> <CCACA85C-15C7-49F2-968B-1F12060CB271@cisco.com> <1177802622.3020.8.camel@localhost.localdomain> <20070429074034.224850@gmx.net> <003201c78a63$74cff690$0601a8c0@BEMBUSTER> <20070429143555.77900@gmx.net> <17972.45384.981257.4920@tutpro.com>
Subject: Re: [Sip] SIPit 20 survey summary
To: jh@tutpro.com
X-Authenticated: #29516787
X-Flags: 0001
X-Mailer: WWW-Mail 6100 (Global Message Exchange)
X-Priority: 3
X-Provags-ID: V01U2FsdGVkX1/LVKx6k0HLjBY6jy8Blnu/FdPo83SNpuohRf/9Mo LYHF9TOtkIbhkj8XnrIg5S/X1pOB/Pq+bTlQ==
Content-Transfer-Encoding: 7bit
X-GMX-UID: AN5RBwNqfW47X8k5tWRov3JudmllcoU7
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: fluffy@cisco.com, discussion@sipforum.org, sip@ietf.org, rjsparks@estacado.net, sip-implementors@cs.columbia.edu, fwmiller@cornfed.com
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

Hi, 

I am not sure what drafts you counted but I noticed a couple of things that had an impact on the increase of pages in documents:

* Publication of documents for requirements, frameworks, document design considerations and design decisions
* More examples in the drafts 
* Security con
* Split documents to involve more people as draft authors 
  (=more documents, potentially smaller but each one of them with all the IETF document templates)

Hence, I am not so sure whether the number of papes actually indicate something about the amount of code you have to write. 

Ciao
Hannes

-------- Original-Nachricht --------
Datum: Sun, 29 Apr 2007 17:52:56 +0300
Von: jh@tutpro.com
An: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
CC: "Jeroen van Bemmel" <jbemmel@zonnet.nl>, fluffy@cisco.com, fwmiller@cornfed.com, rjsparks@estacado.net, sip-implementors@cs.columbia.edu, discussion@sipforum.org, sip@ietf.org
Betreff: Re: [Sip] SIPit 20 survey summary

> Hannes Tschofenig writes:
> 
>  > I would like to understand the complexity of the proposed mechanisms,
>  > if you see some. I am obviously in favor of simplifications.
> 
> number of lines in internet-draft:  2028
> number of lines in xmpp spec:        410
> 
> just adopt the latter.
> 
> -- juha


_______________________________________________
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