Re: [siprec] Adoption of material fromdraft-ram-siprec-metadata-format-02
"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Mon, 20 June 2011 15:40 UTC
Return-Path: <eckelcu@cisco.com>
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 492C19E801A for <siprec@ietfa.amsl.com>; Mon, 20 Jun 2011 08:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.509
X-Spam-Level:
X-Spam-Status: No, score=-10.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 FpO+B3i83aor for <siprec@ietfa.amsl.com>; Mon, 20 Jun 2011 08:40:44 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 9C70D9E8018 for <siprec@ietf.org>; Mon, 20 Jun 2011 08:40:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=1804; q=dns/txt; s=iport; t=1308584444; x=1309794044; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=soI/kp47LpOMSooDBWRoBSZLFHPzNlSGjCCX7D/48Qc=; b=l4dWAb03lP7PVUMBLmmn7OByk35+6uPiC3+W3g8GjSaLT3xkZLNa2oc5 WZTSMxOhZsVQ5mrNRO0YIc76HAArBTTaDP7yi4jz951HwQETaODzN/ixg 1wLGsAiBsfvPO3vr/EU8MheFRJzqbQo8IIn4CkWvFiaO2jELsKcP3LN/7 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEAADJp/02rRDoJ/2dsb2JhbABTl1WPC3eqR51rhioEhyCPJ4s4
X-IronPort-AV: E=Sophos;i="4.65,394,1304294400"; d="scan'208";a="341672110"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-3.cisco.com with ESMTP; 20 Jun 2011 15:40:44 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p5KFeiMr000967; Mon, 20 Jun 2011 15:40:44 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 20 Jun 2011 08:40:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 20 Jun 2011 08:40:42 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C0497E061@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA08C663758C@MCHP058A.global-ad.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [siprec] Adoption of material fromdraft-ram-siprec-metadata-format-02
Thread-Index: AcwvOXaZg+4+wDzBQu2PC/LOxWkIwAAJgwgw
References: <A444A0F8084434499206E78C106220CA08C663758C@MCHP058A.global-ad.net>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, siprec@ietf.org
X-OriginalArrivalTime: 20 Jun 2011 15:40:43.0808 (UTC) FILETIME=[6A8FDA00:01CC2F60]
Subject: Re: [siprec] Adoption of material fromdraft-ram-siprec-metadata-format-02
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: Mon, 20 Jun 2011 15:40:48 -0000
Hi John, One general comment/question I have received from web application savvy coworkers with whom I have discussed the contents of this draft is that the metadata is essentially a document and HTTP already has well defined mechanisms for document sharing and updating, so why not exchange an HTTP address for the document and leverage those mechanisms instead of sending all the metadata within SIP messages. My assumption is that the requirement is to have a SIP based solutions that does not require an HTTP server. Is that accurate? Thanks, Charles > -----Original Message----- > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John > Sent: Monday, June 20, 2011 4:02 AM > To: siprec@ietf.org > Subject: [siprec] Adoption of material fromdraft-ram-siprec-metadata-format-02 > > Although there are some open issues, to be discussed during Thursday's call, I would like the WG to > consider whether material in draft-ram-siprec-metadata-format-02 is ready for adoption into draft- > ietf-siprec-metadata, i.e., bring it under WG control. In particular, between now and the call, please > consider whether: > - the material is heading roughly in an acceptable direction; > - there are any issues that really should be closed before adoption; > - there are any aspects of the draft that should not be adopted at this time. > > If, on the call or shortly afterwards, we can agree on adoption, the authors of the two drafts would > be asked to perform a merger and publish a new version of draft-ietf-siprec-metadata before the cut- > off for IETF#81 (2011-07-11). > > John > _______________________________________________ > siprec mailing list > siprec@ietf.org > https://www.ietf.org/mailman/listinfo/siprec
- [siprec] Adoption of material from draft-ram-sipr… Elwell, John
- Re: [siprec] Adoption of material fromdraft-ram-s… Charles Eckel (eckelcu)
- Re: [siprec] Adoption of material fromdraft-ram-s… Paul Kyzivat
- Re: [siprec] Adoption of material fromdraft-ram-s… Elwell, John
- Re: [siprec] Adoption of material fromdraft-ram-s… Leon Portman
- Re: [siprec] Adoptionof material fromdraft-ram-si… Parthasarathi R (partr)
- Re: [siprec] Adoption of material from draft-ram-… Parthasarathi R (partr)
- Re: [siprec] Adoption of material from draft-ram-… Elwell, John