Re: [siprec] Two questions on draft-ietf-siprec-metadata
"Parthasarathi R" <partha@parthasarathi.co.in> Wed, 24 October 2012 05:58 UTC
Return-Path: <partha@parthasarathi.co.in>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5126F21F8D32 for <siprec@ietfa.amsl.com>; Tue, 23 Oct 2012 22:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[AWL=0.598, BAYES_00=-2.599]
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 tP4+PBZtbzxg for <siprec@ietfa.amsl.com>; Tue, 23 Oct 2012 22:58:09 -0700 (PDT)
Received: from outbound-us3.mailhostbox.com (outbound-us3.mailhostbox.com [70.87.28.151]) by ietfa.amsl.com (Postfix) with ESMTP id 6524521F8D2F for <siprec@ietf.org>; Tue, 23 Oct 2012 22:58:09 -0700 (PDT)
Received: from userPC (unknown [122.179.43.209]) (Authenticated sender: partha@parthasarathi.co.in) by outbound-us3.mailhostbox.com (Postfix) with ESMTPA id D2D4F14D844B; Wed, 24 Oct 2012 05:58:06 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1351058288; bh=pQcE3TulwKUrsAng5tBx2nr3apTFdsmREAt9pPK3t4s=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=nikzbnt9t4B7SLLDQmgnjrO3NLxwm7FJyGo3cVzUnmc9ROzicHp9TRIBuL+NuMlGF Tec14yCFERZ9yANA1K4ACMR+46kjGzb+mOnUM5/lUvcJRdMwpjQJD1aEonKdw8OxnM SHsUEfqCCbcnvWjDsGtrVcqL07PoQKc5CghhyYDI=
From: Parthasarathi R <partha@parthasarathi.co.in>
To: "'Ram Mohan R (rmohanr)'" <rmohanr@cisco.com>, siprec@ietf.org
References: <E92E67B176B8B64D8D3A8F5E44E9D8F40DA8CC@xmb-aln-x05.cisco.com>
In-Reply-To: <E92E67B176B8B64D8D3A8F5E44E9D8F40DA8CC@xmb-aln-x05.cisco.com>
Date: Wed, 24 Oct 2012 11:28:01 +0530
Message-ID: <000f01cdb1ac$89ee00a0$9dca01e0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHNrQqU5qNQ89wCc06Y7ZJvLCpf9JfH+1iA
Content-Language: en-us
X-CTCH-Spam: Suspect
X-CTCH-VOD: Unknown
X-CTCH-RefID: str=0001.0A0B0209.50878370.014E, ss=2, re=0.000, recu=0.000, reip=0.000, cl=2, cld=1, fgs=64
Subject: Re: [siprec] Two questions on draft-ietf-siprec-metadata
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 05:58:10 -0000
Hi all, Object instance diagram was useful while forming Metadata XML format. As the metadata XML format is matured and few implementation already exists, I'm not seeing more advantages in having object instances. IMO, Object instance (Appendix A) shall be removed until otherwise somebody have trouble in review the metadata model relationship with current metadata XML schema. I agree with Ram that metadata example shall be removed from Appendix B as it is subset of SIPREC callflow document. Also, SIPREC callflow document shall include SIP & SDP message apart from metadata XML. Thanks Partha -----Original Message----- From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of Ram Mohan R (rmohanr) Sent: Thursday, October 18, 2012 1:59 PM To: siprec@ietf.org Subject: [siprec] Two questions on draft-ietf-siprec-metadata Hi All, I have two questions for which I need inputs on what we could do: 1) The object diagrams in the Appendix A have gone out of sync now due to changes in the model. It would take some time to re-draw. I wonder if they are really needed now ? I don't know if any one have paidsome attention to them ? Comments ? I feel the UML diagram is sufficient enough and we may not need the Appendix A. 2)What about Appendix B. Do we need that now given that we are having call flows in a separate draft ? My preference here to move the Appendix B to call flow ID and have both call flows + metadata in the same document (draft-ram-siprec-callflows). draft-ietf-siprec-metadata can just refer to call flows document for examples Let me know your comments on this. Regards, Ram _______________________________________________ siprec mailing list siprec@ietf.org https://www.ietf.org/mailman/listinfo/siprec
- [siprec] Two questions on draft-ietf-siprec-metad… Ram Mohan R (rmohanr)
- Re: [siprec] Two questions on draft-ietf-siprec-m… Parthasarathi R