[Sipping] draft-ietf-sipping-media-policy-dataset: media-intermediaries

"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 20 May 2011 20:25 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: sipping@ietfa.amsl.com
Delivered-To: sipping@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C09DE0746 for <sipping@ietfa.amsl.com>; Fri, 20 May 2011 13:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.499
X-Spam-Level:
X-Spam-Status: No, score=-103.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 S2FYfJXEbQ+0 for <sipping@ietfa.amsl.com>; Fri, 20 May 2011 13:25:08 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id E549DE0710 for <sipping@ietf.org>; Fri, 20 May 2011 13:25:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAK3K1k2HCzI1/2dsb2JhbACmH3inJQKbN4YZBJRdikU
X-IronPort-AV: E=Sophos;i="4.65,243,1304308800"; d="scan'208";a="281032606"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 20 May 2011 16:25:06 -0400
X-IronPort-AV: E=Sophos;i="4.65,243,1304308800"; d="scan'208";a="654508119"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 20 May 2011 16:25:07 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 20 May 2011 16:25:06 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Volker Hilt <volkerh@bell-labs.com>
Date: Fri, 20 May 2011 16:25:06 -0400
Thread-Topic: draft-ietf-sipping-media-policy-dataset: media-intermediaries
Thread-Index: AQHMFywBs6ZChCcVq0GF1axnfX0S6g==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22246BD4C7@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
Cc: "sipping@ietf.org" <sipping@ietf.org>
Subject: [Sipping] draft-ietf-sipping-media-policy-dataset: media-intermediaries
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 20 May 2011 20:25:08 -0000

The media policy dataset defines an XML element <media-intermediaries> for specifying intermediary
relays that should be used for sending media.  The current draft has some odd features with regard
to this element:

- It can be specified for a session-info but not a session-policy.  Whereas it seems to me that it should
be possible to put a media intermediary specification into a policy.

- <media-intermediaries> is specified as a child of <session-info>, with various complexities to allow
particular intermediaries to be specified for particular streams.  But it seems simpler to me to demote
<media-intermediaries> to a child of <stream>, so that the intermediaries for each stream can be
specified directly.

- The handling of media streams that use multiple ports is not specified clearly.  My impression is that the
only such protocol is RTP, which uses one port for the media (RTP proper) and one port for control information
(RTCP).  Are there any other protocols that use multiple ports?

Dale