[RAI] draft-ietf-sipping-media-policy-dataset: zero children of an element

"Worley, Dale R (Dale)" <dworley@avaya.com> Wed, 08 December 2010 18:56 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: rai@core3.amsl.com
Delivered-To: rai@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4285C3A6869; Wed, 8 Dec 2010 10:56:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.509
X-Spam-Level:
X-Spam-Status: No, score=-102.509 tagged_above=-999 required=5 tests=[AWL=0.090, 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 dnWriVqh0LiF; Wed, 8 Dec 2010 10:56:54 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 03A943A6823; Wed, 8 Dec 2010 10:56:53 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AigFAExk/0zGmAcF/2dsb2JhbACieWl4pn0CmTGFSQSEYok9
X-IronPort-AV: E=Sophos;i="4.59,316,1288584000"; d="scan'208";a="222267531"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 08 Dec 2010 13:58:20 -0500
X-IronPort-AV: E=Sophos;i="4.59,316,1288584000"; d="scan'208";a="552474227"
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; 08 Dec 2010 13:58:19 -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; Wed, 8 Dec 2010 13:58:19 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "rai@ietf.org" <rai@ietf.org>, "sipping@ietf.org" <sipping@ietf.org>
Date: Wed, 08 Dec 2010 13:58:18 -0500
Thread-Topic: draft-ietf-sipping-media-policy-dataset: zero children of an element
Thread-Index: AQHLlwng9SNwSqbq+U6w3K49mGt2Sg==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288AB2@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: [RAI] draft-ietf-sipping-media-policy-dataset: zero children of an element
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2010 18:56:55 -0000

In a number of places, draft-ietf-sipping-media-policy-dataset-10 specifies that one element must have one or more children of a particular type.  In many of these cases, having zero children would have a well-defined meaning.  And in various situations, it is difficult to define appropriate processing without allowing zero children.  I am proposing that we modify the draft to admit zero children whenever this has a well-defined meaning.

The two cases I've identified so far are:

A <streams> element with zero <stream> children, indicating a session with no media streams.  This is needed to be able to encode SDP descriptions that contain zero m= lines (which is permitted by RFC 4566).

In various situations where a policy is specified, we need a way to specify that no value of a particular attribute is allowed.  This describes a policy that accepts no media streams, which can happen if two policies are merged that have no overlap.  Without this change, one would not be able to express the conjunction of two incompatible policies at all.

Comments?

Dale