[Sipping] draft-ietf-sipping-media-policy-dataset: Remove <property-set>?
"Worley, Dale R (Dale)" <dworley@avaya.com> Mon, 06 December 2010 20:15 UTC
Return-Path: <dworley@avaya.com>
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0114D3A6894; Mon, 6 Dec 2010 12:15:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level:
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uwgs89o4B1mt; Mon, 6 Dec 2010 12:15:20 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 038733A68BA; Mon, 6 Dec 2010 12:15:19 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAIvT/EzGmAcF/2dsb2JhbACjPHGlVgKZGYVJBIRfiTw
X-IronPort-AV: E=Sophos;i="4.59,306,1288584000"; d="scan'208";a="48751986"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 06 Dec 2010 15:16:43 -0500
X-IronPort-AV: E=Sophos;i="4.59,306,1288584000"; d="scan'208";a="551190410"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 Dec 2010 15:16:42 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Mon, 6 Dec 2010 15:16:42 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "rai@ietf.org" <rai@ietf.org>, "sipping@ietf.org" <sipping@ietf.org>
Date: Mon, 06 Dec 2010 15:11:59 -0500
Thread-Topic: draft-ietf-sipping-media-policy-dataset: Remove <property-set>?
Thread-Index: AQHLlYJ+mQ/V84qx1UC5HDgam/HT3g==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288A97@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Sipping] draft-ietf-sipping-media-policy-dataset: Remove <property-set>?
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Dec 2010 20:15:21 -0000
I have updated the text of draft-ietf-sipping-media-policy-dataset-11 to consistently use "property-set" rather than sometimes using "property_set". However, it seems to me that the <property-set> element serves no use (now that sipping-profile-datasets has been abandoned). The draft says that each <session-info> and <session-policy> appears in a <property-set>, and <property-set> can contain more than one of each. But there seems to be no practical use for this grouping; the semantics of <session-info> and <session-policy> is completely standalone. So I am proposing eliminating the <property-set> element entirely, making <session-info> and <session-policy> into top-level elements. Comments? Dale
- [Sipping] draft-ietf-sipping-media-policy-dataset… Worley, Dale R (Dale)