Re: [sipcore] draft-barnes-sipcore-rfc4244bis

Cullen Jennings <fluffy@cisco.com> Tue, 21 June 2011 23:21 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9063511E80A6 for <sipcore@ietfa.amsl.com>; Tue, 21 Jun 2011 16:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.592
X-Spam-Level:
X-Spam-Status: No, score=-110.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 92kFspkiCDsb for <sipcore@ietfa.amsl.com>; Tue, 21 Jun 2011 16:21:32 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 31A6E11E8083 for <sipcore@ietf.org>; Tue, 21 Jun 2011 16:21:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1086; q=dns/txt; s=iport; t=1308698492; x=1309908092; h=mime-version:subject:from:in-reply-to:date: content-transfer-encoding:message-id:references:to; bh=UTRPCISvtV+10Vs/djuuDPVcWaxsDr/MInIaJxJPPtM=; b=L1zE6U9kCmyoN0PaF6Ww2+5Nt3V/AJrnV5Punwzs+GUwIynV0sNaOaMg 37DcGbwlWxJcnJefL3oFpLagVDIeRNY9UaGvBe9oWHQAvWpdIBcgL/TKZ TvBCFjJ8+gmgGXoiZGm0wIzxmZtD3mZutgP4hwD3gF5V/hdAO28jILb8L Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAPwmAU5Io8UR/2dsb2JhbABUpwZ3iHOhfJ4ghioEhyKKRJAm
X-IronPort-AV: E=Sophos;i="4.65,403,1304294400"; d="scan'208";a="95708867"
Received: from bgl-core-2.cisco.com ([72.163.197.17]) by ams-iport-1.cisco.com with ESMTP; 21 Jun 2011 23:21:30 +0000
Received: from dhcp-171-68-21-143.cisco.com (dhcp-171-68-21-143.cisco.com [171.68.21.143]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5LNLR0F026990 for <sipcore@ietf.org>; Tue, 21 Jun 2011 23:21:28 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <14FFF078-E5D1-45F2-8D9A-AD52DE677CEF@cisco.com>
Date: Tue, 21 Jun 2011 16:21:29 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F0155A5D-B8F4-4538-8B8B-DC8EC0AC0131@cisco.com>
References: <14FFF078-E5D1-45F2-8D9A-AD52DE677CEF@cisco.com>
To: "sipcore@ietf.org WG" <sipcore@ietf.org>
X-Mailer: Apple Mail (2.1084)
Subject: Re: [sipcore] draft-barnes-sipcore-rfc4244bis
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 23:21:36 -0000

I still feel the same as my email from last nov ...

On Nov 11, 2010, at 1:41 , Cullen Jennings wrote:

> 
> The draft has a lot well specified procedures about how to write tags to a message, and it discusses that the tags could be used in lots of ways. However, I would like to see some text added to section 8 that allowed implementers to use this specification to implemented some of the use cases it is designed to meet. Specifically I would like to see normative language on how a voicemail system can use the tags found in an incoming invite to determined which mailbox the call should be delivered too. 
> 
> People have suggested to me this information is in the call flows document. I like call flows, I think they help people, but this is an information document with no normative language describing how to do this. I'm not a huge fan of people implementing things off call flows. I rather have the procedures for this specified in 4244bis and then have example call flows that illustrated this in the call flow draft.