
From dworley@avaya.com  Mon May  9 12:01:48 2011
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 F22B3E080E for <sipping@ietfa.amsl.com>; Mon,  9 May 2011 12:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.404
X-Spam-Level: 
X-Spam-Status: No, score=-102.404 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_18=0.6, 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 FTxeK+JBBA6b for <sipping@ietfa.amsl.com>; Mon,  9 May 2011 12:01:44 -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 8B98DE0787 for <sipping@ietf.org>; Mon,  9 May 2011 12:01:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAOY3yE2HCzI1/2dsb2JhbACmAneIcaJXAptdhgwElCqKNA
X-IronPort-AV: E=Sophos;i="4.64,341,1301889600"; d="scan'208";a="278976028"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 09 May 2011 14:57:48 -0400
X-IronPort-AV: E=Sophos;i="4.64,341,1301889600"; d="scan'208";a="649370437"
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 09 May 2011 14:57:48 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Mon, 9 May 2011 14:57:47 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, "sipping@ietf.org" <sipping@ietf.org>
Date: Mon, 9 May 2011 14:57:47 -0400
Thread-Topic: [Sipping] draft-ietf-sipping-media-policy-dataset: Bandwidth directionality
Thread-Index: AQHL3RUNafBx19X2g0mVkymy0YZjuZSFOQPd
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22246BD46E@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B220B5C1555@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220B5C1555@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: Re: [Sipping] draft-ietf-sipping-media-policy-dataset: Bandwidth	directionality
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: Mon, 09 May 2011 19:01:48 -0000

> From: Worley, Dale R (Dale) [dworley@avaya.com]
>=20
> One problem I'm noticing is that the session-policy XML allows
> specifying the bandwidth in each direction, but SDP does not (as far
> as I can tell).  How should we resolve this?  Should we define
> directional bandwidth modifiers in SDP?  Or should we restrict
> bandwidth in a stream based on the directionality attributes of the
> stream?
>=20
> That is, if the sending bandwidth is limited to 10,000 and the
> receiving bandwidth is limited to 100,000, then an a=3Dsendrecv stream
> would be have b=3D10000 but an a=3Drecv stream would have b=3D100000.

That was a misunderstanding on my part.  The solution to bandwidth
directionality is that there are two SDPs, an offer and an answer, and
each has a separate b=3D line.  The session-policy's bandwidth limit is
applied to the offer and answer as they are generated (or received).

Detail to remember:  An SDP offer or answer describes what the sender
of the SDP wishes to *receive*.  (Despite that a standalone SDP
describes what the sender will be sending.)

Detail to remember:  The format of the b=3D line in this case is:
        b=3DAS:<bandwidth in kbits/sec>

Thus, in the case of 10 kbits/sec sending and 100 kbits/sec receiving,
the SDP sent would have "b=3DAS:10" and the SDP received would have (or
would be modified to have) "b=3DAS:100" (as session-level attributes).
The session-policy XML would be:

        <session-policy>
          <max-bw direction=3D"sendonly">10</max-bw>
          <max-bw direction=3D"recvonly">100</max-bw>
          ...
        </session-policy>

Dale

From dworley@avaya.com  Mon May  9 12:26:32 2011
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 728B1E07EA for <sipping@ietfa.amsl.com>; Mon,  9 May 2011 12:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.004
X-Spam-Level: 
X-Spam-Status: No, score=-103.004 tagged_above=-999 required=5 tests=[AWL=0.595, 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 62aoOCkwXEjj for <sipping@ietfa.amsl.com>; Mon,  9 May 2011 12:26:31 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 97266E0713 for <sipping@ietf.org>; Mon,  9 May 2011 12:26:31 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACw/yE2HCzI1/2dsb2JhbACmAXerKQKbY4YMBJQqijQ
X-IronPort-AV: E=Sophos;i="4.64,342,1301889600"; d="scan'208";a="245597189"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 09 May 2011 15:26:29 -0400
X-IronPort-AV: E=Sophos;i="4.64,342,1301889600"; d="scan'208";a="649382900"
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 09 May 2011 15:26:27 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Mon, 9 May 2011 15:26:26 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, "sipping@ietf.org" <sipping@ietf.org>
Date: Mon, 9 May 2011 15:26:25 -0400
Thread-Topic: draft-ietf-sipping-media-policy-dataset: Bandwidth limitations
Thread-Index: AQHMDn78Hk6A5FQJT0WMWQEIG2PSDA==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22246BD46F@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: Bandwidth limitations
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: Mon, 09 May 2011 19:26:32 -0000

The media-policy-dataset provides 3 different bandwidth limitations:

max-bw
max-session-bw
max-stream-bw

Comparing the description of these (section 7.3 et seq.) with the descripti=
on of
the b=3D line in SDP (RFC 4566 section 5.8) turns up a lot of ambiguity in =
the
definitions.

It seems to me to be clear that the max-stream-bw number corresponds to the=
 "b=3DAS:..." line
in an SDP media description -- the bandwidth used by one direction of one m=
edia
stream.

The max-session-bw seems to correspond to the "b=3DAS:..." line in the *ses=
sion* description,
the total bandwidth used (in one direction) by the whole session.

The max-bw number is less clear.  It seems to be intended to limit the tota=
l bandwidth used
by an agent (across all of the sessions it participates in).  As such, it c=
an't be translated to
an SDP attribute.

Conversely, the "b=3DCT:..." line in an SDP session description seems to be=
 intended to
describe the total bandwidth used by a "conference" (whatever that is).  It=
's not clear
what the significance of that is exactly, since the agent in question may n=
ot be the conference
focus, and indeed, the session may not be part of a "conference".

Thoughts?

Dale

From dworley@avaya.com  Tue May 10 12:57:19 2011
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 907B0E0711 for <sipping@ietfa.amsl.com>; Tue, 10 May 2011 12:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.021
X-Spam-Level: 
X-Spam-Status: No, score=-100.021 tagged_above=-999 required=5 tests=[AWL=-2.422, BAYES_00=-2.599, GB_SUMOF=5, 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 gO4qW9h6NsZh for <sipping@ietfa.amsl.com>; Tue, 10 May 2011 12:57:18 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 53DAAE06AE for <sipping@ietf.org>; Tue, 10 May 2011 12:57:17 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHmXyU2HCzI1/2dsb2JhbACmC3erSwKbfoYPBJQ0ijY
X-IronPort-AV: E=Sophos;i="4.64,347,1301889600"; d="scan'208";a="187755413"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 10 May 2011 15:57:16 -0400
X-IronPort-AV: E=Sophos;i="4.64,347,1301889600"; d="scan'208";a="650060469"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 May 2011 15:57:16 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 10 May 2011 15:57:15 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, "sipping@ietf.org" <sipping@ietf.org>
Date: Tue, 10 May 2011 15:54:27 -0400
Thread-Topic: draft-ietf-sipping-media-policy-dataset: Bandwidth limitations
Thread-Index: AQHMDn78Hk6A5FQJT0WMWQEIG2PSDJSGeyWD
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22246BD47A@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B22246BD46F@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22246BD46F@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: Re: [Sipping] draft-ietf-sipping-media-policy-dataset: Bandwidth limitations
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: Tue, 10 May 2011 19:57:19 -0000

I see commented-out text about these bandwidth descriptions:

    The <max-bw-ti> Element

      The <max-bw-ti> element defined as the <max-bw>
      element with the following exceptions.
     =20
      The given bandwidth limit is transport independent and
      therefore does not include include the bandwidth needed for
      lower-layer transport and network protocols (e.g., UDP and
      IP).

      The bandwidth limit is given in bits per second (i.e., not in=20
      kilobits per second).

      The <max-bw-ti> element MAY have the following
      attribute (see <xref target=3D"sec_attributes" />): pprate. =20

   The maxprate attribute

      The <max-bw-ti> element has an optional attribute
      'maxprate'. The "maxprate" value is the maximum packet rate
      calculated over all the declared media streams.  If this can't
      be measured (stored media) or estimated (live), the sum of all
      media level values provides a ceiling value.

      All other attributes and merging rules are defined as for the=20
      <max-bw> element.

Do people think these data are significant, or can they be safely omitted f=
rom
the media-policy-dataset?

Dale

From dworley@avaya.com  Wed May 11 15:10:45 2011
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 573A2E0898 for <sipping@ietfa.amsl.com>; Wed, 11 May 2011 15:10:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[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 czF0pOJxt2Oy for <sipping@ietfa.amsl.com>; Wed, 11 May 2011 15:10:39 -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 B6FFBE0693 for <sipping@ietf.org>; Wed, 11 May 2011 15:10:39 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAB0Jy02HCzI1/2dsb2JhbAClb3etCQKcAIYQBJQ0ijk
X-IronPort-AV: E=Sophos;i="4.64,354,1301889600"; d="scan'208";a="279480131"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 11 May 2011 18:10:38 -0400
X-IronPort-AV: E=Sophos;i="4.64,354,1301889600"; d="scan'208";a="650771596"
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 11 May 2011 18:10:38 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Wed, 11 May 2011 18:10:38 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, "sipping@ietf.org" <sipping@ietf.org>
Date: Wed, 11 May 2011 18:10:21 -0400
Thread-Topic: draft-ietf-sipping-media-policy-dataset: Bandwidth limitations
Thread-Index: AQHMDn78Hk6A5FQJT0WMWQEIG2PSDJSGeyWDgAG4TS4=
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22246BD484@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B22246BD46F@DC-US1MBEX4.global.avaya.com>, <CD5674C3CD99574EBA7432465FC13C1B22246BD47A@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22246BD47A@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: Bandwidth limitations
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: Wed, 11 May 2011 22:10:45 -0000

I have updated the definition of the <max-stream-bw> element to remove
the "label" and "media-type" attributes, which in the previous version
were used to limit the effect of the bandwidth limitation to
particular media types or one particular stream.

Doing this makes <max-stream-bw> work the same way as other elements.

Limiting the bandwidth for streams of a particular media type can be
done by the usual method of a <stream> that has both <media-type> and
<max-stream-bw> children:

    <session-policy>
      <stream>
	<media-type>video</media-type>
	<max-stream-bw>1000</max-stream-bw>
      </stream>
    </session-policy>

Dale

From dworley@avaya.com  Wed May 18 09:33:33 2011
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 7A663E06A7 for <sipping@ietfa.amsl.com>; Wed, 18 May 2011 09:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[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 7rTi8PAilqbc for <sipping@ietfa.amsl.com>; Wed, 18 May 2011 09:33:32 -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 92AA0E0665 for <sipping@ietf.org>; Wed, 18 May 2011 09:33:32 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAOLz002HCzI1/2dsb2JhbACmG3eraQKbQ4YZBJRdikU
X-IronPort-AV: E=Sophos;i="4.65,231,1304308800"; d="scan'208";a="280587918"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 18 May 2011 12:33:31 -0400
X-IronPort-AV: E=Sophos;i="4.65,231,1304308800"; d="scan'208";a="653423623"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 18 May 2011 12:33:31 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Wed, 18 May 2011 12:33:30 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "sipping@ietf.org" <sipping@ietf.org>
Date: Wed, 18 May 2011 12:33:30 -0400
Thread-Topic: session-info <token> value
Thread-Index: AQHMFXlQM9TIGZzf+kqi/9oB1QhdWg==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22246BD4AE@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] session-info <token> value
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: Wed, 18 May 2011 16:33:33 -0000

There is a "token" value which is passed from a policy server to a UA.  The=
 token value is the content of a <token> element in the session-info docume=
nt, so in general it is a sequence of Unicode characters.  The UA uses it w=
hen it makes certain requests by adding a Policy-Info header of the form:

Policy-Info: sip:foo@example.com;token=3Dxyzzy

where the value of the "token" parameter is the content of the <token> elem=
ent in the session-info that it was given.

The question is what characters are permitted in the token value?

The only limitation on the session-info document is that it consist of Unic=
ode characters.  But in order to put it in a parameter value, it must be re=
presentable there.  Parameter values use %-escaping, so characters from U+0=
020 (space) to U+007E (~) can easily be accommodated.  If we use %80 to %FF=
 to represent the characters from U+0080 to U+00FF, we can add the Latin-1 =
set.  Or we could assume that %-escaping is used to encode *bytes* used in =
the *UTF-8* representation of characters, in which case the entire Unicode =
set is representable.  (Since the semantics of %-escaping is not described =
anywhere in RFC 3261, either of these is possible.)

It seems to me that limiting the characters to U+0020 through U+007E, the o=
rdinary ASCII set, is enough flexibility and avoids all sorts of complicati=
ons.

Dale

From gonzalo.camarillo@ericsson.com  Fri May 20 05:21:35 2011
Return-Path: <gonzalo.camarillo@ericsson.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 AC20DE0695 for <sipping@ietfa.amsl.com>; Fri, 20 May 2011 05:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 ez0Aw6PD6T-t for <sipping@ietfa.amsl.com>; Fri, 20 May 2011 05:21:35 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id ED150E065D for <sipping@ietf.org>; Fri, 20 May 2011 05:21:34 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-77-4dd65ccd3774
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 22.39.20773.DCC56DD4; Fri, 20 May 2011 14:21:33 +0200 (CEST)
Received: from [131.160.37.44] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Fri, 20 May 2011 14:21:32 +0200
Message-ID: <4DD65CCC.5000008@ericsson.com>
Date: Fri, 20 May 2011 15:21:32 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B22246BD4AE@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22246BD4AE@DC-US1MBEX4.global.avaya.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: "sipping@ietf.org" <sipping@ietf.org>
Subject: Re: [Sipping] session-info <token> value
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 12:21:35 -0000

Hi,

yes, I think limiting the valid characters to something simpler (UTF8 or
ASCII) makes sense.

Cheers,

Gonzalo

On 18/05/2011 7:33 PM, Worley, Dale R (Dale) wrote:
> There is a "token" value which is passed from a policy server to a UA.  The token value is the content of a <token> element in the session-info document, so in general it is a sequence of Unicode characters.  The UA uses it when it makes certain requests by adding a Policy-Info header of the form:
> 
> Policy-Info: sip:foo@example.com;token=xyzzy
> 
> where the value of the "token" parameter is the content of the <token> element in the session-info that it was given.
> 
> The question is what characters are permitted in the token value?
> 
> The only limitation on the session-info document is that it consist of Unicode characters.  But in order to put it in a parameter value, it must be representable there.  Parameter values use %-escaping, so characters from U+0020 (space) to U+007E (~) can easily be accommodated.  If we use %80 to %FF to represent the characters from U+0080 to U+00FF, we can add the Latin-1 set.  Or we could assume that %-escaping is used to encode *bytes* used in the *UTF-8* representation of characters, in which case the entire Unicode set is representable.  (Since the semantics of %-escaping is not described anywhere in RFC 3261, either of these is possible.)
> 
> It seems to me that limiting the characters to U+0020 through U+007E, the ordinary ASCII set, is enough flexibility and avoids all sorts of complications.
> 
> Dale


From dworley@avaya.com  Fri May 20 13:25:08 2011
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 o=
dd 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 va=
rious complexities to allow
particular intermediaries to be specified for particular streams.  But it s=
eems simpler to me to demote
<media-intermediaries> to a child of <stream>, so that the intermediaries f=
or each stream can be
specified directly.

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

Dale

From dworley@avaya.com  Mon May 23 11:49:29 2011
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 D268AE0804 for <sipping@ietfa.amsl.com>; Mon, 23 May 2011 11:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.456
X-Spam-Level: 
X-Spam-Status: No, score=-103.456 tagged_above=-999 required=5 tests=[AWL=0.143, 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 NB18OGzf1q-p for <sipping@ietfa.amsl.com>; Mon, 23 May 2011 11:49:29 -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 482F5E07E6 for <sipping@ietf.org>; Mon, 23 May 2011 11:49:29 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFABqj2k2HCzI1/2dsb2JhbACmJ3AHpi2DWQKbCoYZBJRdikU
X-IronPort-AV: E=Sophos;i="4.65,244,1304308800"; d="scan'208";a="281369727"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 23 May 2011 14:49:28 -0400
X-IronPort-AV: E=Sophos;i="4.65,257,1304308800"; d="scan'208";a="655290020"
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 23 May 2011 14:49:28 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.192]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Mon, 23 May 2011 14:49:27 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "sipping@ietf.org" <sipping@ietf.org>
Date: Mon, 23 May 2011 14:49:27 -0400
Thread-Topic: media-policy-dataset:  <local-ports>
Thread-Index: AQHMGXokilOGcK5spkGLMcVF3eBB1A==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222907E942@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] media-policy-dataset:  <local-ports>
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: Mon, 23 May 2011 18:49:29 -0000

draft-ietf-sipping-media-policy-dataset defines a <local-ports> restriction=
 which a policy server can use to inform a UA what ports it may use for sen=
ding/receiving media.  I'd like to make two changes to the current definiti=
on:

1) Allow specifications in which the "start" port is greater than the "end"=
 port.  These specifications permit *no* ports to be used, and hence no ses=
sions are in conformance with the policy.  This is not a useful facility fo=
r configured policies, but it makes it possible to to construct the logical=
 AND of two policies that make incompatible restrictions on the local port =
numbers.

2) Change the merging rule from "the local policy controls" to "the interse=
ction of the two specified ranges".  In practice, we expect only the most l=
ocal policy to restrict what ports can be used.  But it would help to make =
the merging process more consistent if it was specified as a "logical AND" =
of all the specified restrictions.

Dale

From dworley@avaya.com  Tue May 31 12:34:18 2011
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 882D1E06A8; Tue, 31 May 2011 12:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.293
X-Spam-Level: 
X-Spam-Status: No, score=-103.293 tagged_above=-999 required=5 tests=[AWL=0.306, 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 MDOhDlveQdz9; Tue, 31 May 2011 12:34:18 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 84E87E0681; Tue, 31 May 2011 12:34:17 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBAOlB5U3GmAcF/2dsb2JhbABTl06OU3erFQKbGYYeBJUqils
X-IronPort-AV: E=Sophos;i="4.65,299,1304308800"; d="scan'208";a="249136622"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 31 May 2011 15:34:15 -0400
X-IronPort-AV: E=Sophos;i="4.65,299,1304308800"; d="scan'208";a="628083057"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 31 May 2011 15:34:15 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.192]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Tue, 31 May 2011 15:34:14 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "rai@ietf.org" <rai@ietf.org>, "sipping@ietf.org" <sipping@ietf.org>
Date: Tue, 31 May 2011 15:33:35 -0400
Thread-Topic: Progressing draft-ietf-sipping-media-policy-dataset
Thread-Index: AcwPqcuH73yCHEGRRY6ypTrFrigFEABRGpg1A7ba+HQ=
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222907E97C@DC-US1MBEX4.global.avaya.com>
References: <4DA40B86.5060905@ericsson.com>,<4DBFE77A.4010303@ericsson.com> <CD5674C3CD99574EBA7432465FC13C1B22246BD463@DC-US1MBEX4.global.avaya.com>, <4DC8EE2C.6010409@ericsson.com> <CD5674C3CD99574EBA7432465FC13C1B22246BD479@DC-US1MBEX4.global.avaya.com>, <4DCA3507.9020708@ericsson.com>, <CD5674C3CD99574EBA7432465FC13C1B22246BD491@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22246BD491@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] FW: Progressing draft-ietf-sipping-media-policy-dataset
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: Tue, 31 May 2011 19:34:18 -0000

From: Worley, Dale R (Dale)
Sent: Thursday, May 12, 2011 5:56 PM
To: Gonzalo Camarillo
Subject: RE: Progressing draft-ietf-sipping-media-policy-dataset

I just ran into something I had overlooked.  I've been taking the Abstract =
seriously when it says "It can be used to describe the properties of a spec=
ific SIP session or to define policies that are then applied to different S=
IP sessions."  That is, I've assumed that a session-policy is sort of a gen=
eric session-info whose <stream>s show what sorts of <stream>s are permitte=
d in a conforming session-info.  This is what lead to the "implicit Boolean=
 logic" message.

But when I look at the examples, I see that session-policy and session-info=
 documents have completely different structure.  The session-policy is a co=
llection of elements, each of which specifies a particular restriction on c=
onforming session-info's.  And in particular, a session-policy does not con=
tain stream elements.

A certain amount of my editing has been driven by this misconception, altho=
ugh I don't think it would take much work to reverse those edits.

The high-level question is whether we want to stay with the original scheme=
, where session-policy's have a distinctly different structure, or whether =
we want to go with my misconception, where session-policy are template sess=
ion-info documents.

The original scheme would be easier for people to understand and thus to im=
plement, but it has the limitation that one has to specifically define an e=
lement to represent every restriction that anyone will want to use.  The "n=
ew" scheme requires more abstract thought, but it automatically provides wa=
ys to make restrictions in every feature that can be expressed in a session=
-info, and so extensions of the data set require less design, and the proce=
ssing code can be written in a more generic way.

What do you think?

Dale


