
From aallen@rim.com  Wed Jan  5 09:05:21 2011
Return-Path: <aallen@rim.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 2DB553A6C07; Wed,  5 Jan 2011 09:05:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.203
X-Spam-Level: 
X-Spam-Status: No, score=-5.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 d1VJPc6uamPV; Wed,  5 Jan 2011 09:05:19 -0800 (PST)
Received: from mhs04ykf.rim.net (mhs04ykf.rim.net [216.9.243.82]) by core3.amsl.com (Postfix) with ESMTP id CC3E83A6B89; Wed,  5 Jan 2011 09:05:17 -0800 (PST)
X-AuditID: 0a666446-b7bdeae000000a41-7f-4d24a54b0b87
Received: from XCH139CNC.rim.net ( [10.65.10.235]) by mhs04ykf.rim.net (RIM Mail) with SMTP id 14.A6.02625.B45A42D4; Wed,  5 Jan 2011 12:07:24 -0500 (EST)
Received: from XCH02DFW.rim.net ([10.150.100.31]) by XCH139CNC.rim.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 5 Jan 2011 12:07:23 -0500
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: Wed, 5 Jan 2011 11:07:32 -0600
Message-ID: <BDBFB6CE314EDF4CB80404CACAEFF5DE078F7748@XCH02DFW.rim.net>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B2202288A86@DC-US1MBEX4.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] draft-ietf-sipping-media-policy-dataset issues: mediatypes
Thread-Index: AQHLkybTlVHtE3vAWk+tHx2rb1eNZpPCz2lQ
References: <CD5674C3CD99574EBA7432465FC13C1B2202288A86@DC-US1MBEX4.global.avaya.com>
From: "Andrew Allen" <aallen@rim.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, <rai@ietf.org>, <sipping@ietf.org>
X-OriginalArrivalTime: 05 Jan 2011 17:07:23.0993 (UTC) FILETIME=[058A9C90:01CBACFB]
X-Brightmail-Tracker: AAAAAgAAAZEXFZJ3
Subject: Re: [RAI] [Sipping] draft-ietf-sipping-media-policy-dataset issues: mediatypes
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, 05 Jan 2011 17:05:21 -0000

Dale

I am OK with your proposed changes. 

I also would like to see this draft progress.

Andrew



-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Worley, Dale R (Dale)
Sent: Friday, December 03, 2010 2:15 PM
To: rai@ietf.org; sipping@ietf.org
Subject: [Sipping] draft-ietf-sipping-media-policy-dataset issues:
mediatypes

I am working on draft-ietf-sipping-media-policy-dataset to clean up some
issues.  These issues are minor technical changes to make the standard
more technically coherent and easier to implement.  As such, I don't
think they will be controversial in their essence, but I would like
people to look them over to ensure that I am not introducing new
problems.

The first issues revolve around media types:

1. In -10, all media type names that are mentioned in a MPDF are
explicitly required to be IANA-registered.  Technically, this means that
experimental or private-use types can not be used, even in situations
where all participants are aware of non-registered media types.  In
practice, people will go ahead and use them anyway.  I am proposing to
remove the "registered" requirement.

2. In a number of places, media types are called "MIME types".  The
latter is common usage, but it is not official, and as RFC 4288 makes
clear, media types are independent of their use within MIME.  I've fixed
the wording of the draft in a number of places to correct this.

The differences for the above two changes are attached, if you want to
see the details.

3. There is an element <mime-type> that is a child of the <codec>
element that carries a media type and subtype.  The natural fix would be
to change this to <media-type>, but there is already an element of that
name that is a child of <stream> that carries a media type (without
subtype).  I would like a name that means "media type and subtype", but
I can't think of a short one.  Suggestions?

Dale
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- draft-ietf-sipping-media-policy-dataset-11.xml	(revision 4412)
+++ draft-ietf-sipping-media-policy-dataset-11.xml	(working copy)
@@ -174,7 +174,7 @@
     <t>This section discusses fundamental properties of the Media
     Policy Dataset Format (MPDF).</t>
 
-    <section title=3D"Namespace and MIME Type">
+    <section title=3D"Namespace and Media Type">
 
       <t>The MPDF format is based on XML <xref
       target=3D"W3C.REC-xml-20040204" />. A MPDF document MUST be
@@ -195,7 +195,7 @@
         <t>urn:ietf:params:xml:ns:mediadataset</t>
       </list></t>
 
-      <t>The MIME type for the Media Policy Dataset Format is:</t> 
+      <t>The media type for the Media Policy Dataset Format is:</t> 
 
       <t><list style=3D"empty">
         <t>application/media-policy-dataset+xml</t>
@@ -949,10 +949,8 @@
     <section title=3D"The <media-type> Element" anchor=3D"sec:mediatype">
 
       <t>The &lt;media-type&gt; element identifies a specific media
-      type. The value of this element MUST be the name of a IANA
-      registered media type (see <xref
-      target=3D"RFC4566">RFC4566</xref>), such as 'audio', 'video',
-      'text', or 'application'. </t>
+      type. The value of this element MUST be the name of a 
+      media type such as 'audio', 'video', 'text', or 'application'.
</t>
 
       <t>This element MAY have the following attribute (see
       <xref target=3D"sec:attributes" />): q.</t>
@@ -968,11 +966,9 @@
     <section title=3D"The <codec> Element">
 	  
       <t>The &lt;codec&gt; element identifies a specific codec. The
-      content of this element MUST be a registered MIME type
-      <xref target=3D"RFC4855" /> using media type and subtype (e.g.,
+      content of this element MUST be a media type and subtype (e.g.,
       audio/PCMA <xref target=3D"RFC4856"/> or video/H263
-      <xref target=3D"RFC4629"/>) and possibly additional registered
-      MIME type parameters.</t>
+      <xref target=3D"RFC4629"/>), possibly with parameters.</t>
 
       <t>The &lt;codec&gt; element MAY have the following attribute
       (see <xref target=3D"sec:attributes" />): q.</t>
@@ -989,9 +985,9 @@
 
         <section title=3D"The <mime-type> Element">
 
-	  <t>The &lt;mime-type&gt; element contains a MIME type that
+	  <t>The &lt;mime-type&gt; element contains a media type and
subtype that
           identifies a codec. The value of this element MUST be a
-          combination of a registered MIME media type and subtype
+          media type and subtype
           <xref target=3D"RFC4855" /> separated by a "/"
           (e.g., audio/PCMA, audio/G726-16 <xref target=3D"RFC4856"/> or
           video/H263 <xref target=3D"RFC4629"/>). </t>
@@ -1003,7 +999,7 @@
 	  <t>The &lt;mime-parameter&gt; element may be needed for some
           codecs to identify a particular encoding or profile. The
           value of this element MUST be a name-value pair containing
-          the name and the value of a registered MIME type parameter
+          the name and the value of a media type parameter
           for the codec <xref target=3D"RFC4855" />. The name and value
           are separated by a "=3D". For example, the parameter
           "profile=3D0" can be used to specify a specific profile for
@@ -1145,9 +1141,7 @@
       &lt;max-stream-bw&gt; element only applies to streams of
       a certain media type. For example, it may only apply to audio
       streams. The value of the 'media-type' attribute MUST be the
-      name of a IANA registered media type (see <xref
-      target=3D"RFC4566">RFC4566</xref>), such as 'audio', 'video',
-      'text', or 'application'.</t>
+      media type such as 'audio', 'video', 'text', or
'application'.</t>
 
       <t>The label attribute is used to define a bandwidth limit for a
       specific media stream. The use of this attribute requires that
@@ -1190,10 +1184,8 @@
       <t>The media-type attribute is used to define that
       &lt;qos-dscp&gt; element only applies to streams of a certain
       media type. For example, it may only apply to audio streams. The
-      value of the 'media-type' attribute MUST be the name of a IANA
-      registered media type (see <xref
-      target=3D"RFC4566">RFC4566</xref>), such as 'audio', 'video',
-      'text', or 'application'.</t>
+      value of the 'media-type' attribute MUST be the name of a 
+      media type, such as 'audio', 'video', 'text', or
'application'.</t>
 
 <!--
       <t><list style=3D"empty">
@@ -2491,15 +2483,15 @@
 
   <section title=3D"IANA Considerations" anchor=3D"sec:iana">
 
-    <t>This document registers a new MIME type,
+    <t>This document registers a new media type,
     application/media-policy-dataset+xml, and a new XML 
     namespace. </t> 
 
-    <section title=3D"MIME Registration">
+    <section title=3D"Media type Registration">
 
-      <t>MIME media type name: application</t>
+      <t>Media type name: application</t>
 
-      <t>MIME subtype name: media-policy-dataset+xml</t>
+      <t>Media subtype name: media-policy-dataset+xml</t>
 
       <t>Mandatory parameters: none</t>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP

---------------------------------------------------------------------=0A=
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From dworley@avaya.com  Fri Jan  7 07:51:52 2011
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 79BC03A6905 for <rai@core3.amsl.com>; Fri,  7 Jan 2011 07:51:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.514
X-Spam-Level: 
X-Spam-Status: No, score=-103.514 tagged_above=-999 required=5 tests=[AWL=1.085, BAYES_00=-2.599, GB_I_LETTER=-2, 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 1Q9j04p0iJK7 for <rai@core3.amsl.com>; Fri,  7 Jan 2011 07:51:51 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id A49B93A6918 for <rai@ietf.org>; Fri,  7 Jan 2011 07:51:49 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAObFJk2HCzI1/2dsb2JhbACkKHOmBwKWG4VMBIRniVo
X-IronPort-AV: E=Sophos;i="4.60,289,1291611600"; d="scan'208";a="53314969"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 07 Jan 2011 10:53:55 -0500
X-IronPort-AV: E=Sophos;i="4.60,289,1291611600"; d="scan'208";a="579006192"
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; 07 Jan 2011 10:53:25 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Fri, 7 Jan 2011 10:53:24 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "rai@ietf.org" <rai@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
Date: Fri, 7 Jan 2011 10:52:20 -0500
Thread-Topic: RFC errata report on erra 1999, 1997, and 1998 to RFC 5688 (A SIP Media Feature Tag for MIME Application Subtypes) and erratum 2091 to RFC 5727 (Change Process for SIP and the RAI Area)
Thread-Index: AQHLroMEwnPgCK5tW0uFOifb6+n9Jg==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288B62@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] RFC errata report on erra 1999, 1997, and 1998 to RFC 5688 (A SIP Media Feature Tag for MIME Application Subtypes) and erratum 2091 to RFC 5727 (Change Process for SIP and the RAI Area)
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: Fri, 07 Jan 2011 15:51:52 -0000

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RFC5688, "A Session Initiation Protocol (SIP) Media Feature Tag for
MIME Application Subtypes"
Source of RFC: IETF - NON WORKING GROUP
Area Assignment: rai

Errata ID: 1999

Status: Reported
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2010-01-10

Section 3, 1st para says:

   The 'sip.app-subtype' media feature tag is of type token with a case-
   insensitive equality relationship.  Its value can be any registered
|  or private MIME application subtype compliant to the subtype-name
   grammar defined in [RFC4288].  When included in the Contact header
   field of a REGISTER request, an agent SHOULD include all application
   subtypes that it can support as streaming formats.  An application
|  subtype is supported if the user agent would be capable of processing
   a Session Description Protocol (SDP) [RFC4566] offer [RFC3264] that
   contained that subtype as a format in the m-line of the SDP.

It should say:

   The 'sip.app-subtype' media feature tag is of type token with a case-
   insensitive equality relationship.  Its value can be any registered
|  or private 'application' media subtype compliant to the subtype-name
   grammar defined in [RFC4288].  When included in the Contact header
   field of a REGISTER request, an agent SHOULD include all application
   subtypes that it can support as streaming formats.  An application
|  subtype is supported if the user agent would be capable of accepting
   a Session Description Protocol (SDP) [RFC4566] offer [RFC3264] that
   contained that subtype as a format in the m-line of the SDP.

Notes:

Rationale:

For clarity, the whole paragraph is shown here, including both changes.

a) editorial; see GLOBAL Errata note, EID=3D1997.

b) technical: the ability of "processing" an SDP offer does not
mean the ability to _accept_ it. The latter reasonably seems
to be synonymous to "supporting" the feature contained therein,
but the former isn't. Therefore, s/processing/accepting/ .
----------------------------------------------------------------------
Recommended status:  (correct) Hold for document update
Type: Editorial

I recommend removing the subjunctive from the final sentence of the
paragraph, along with some other changes:

   An application
   subtype is "supported" if the user agent can usefully accept
   a Session Description Protocol (SDP) [RFC4566] offer [RFC3264] that
   contains that subtype as the sole format in the sole m-line of the SDP.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RFC5688, "A Session Initiation Protocol (SIP) Media Feature Tag for
MIME Application Subtypes"
Source of RFC: IETF - NON WORKING GROUP
Area Assignment: rai

Errata ID: 1997

Status: Reported
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2010-01-10

Throughout the document, when it says:

a)   document title:

     A Session Initiation Protocol (SIP) Media Feature Tag for MIME
                          Application Subtypes

b)   Abstract

   The caller preferences specification for the Session Initiation
   Protocol (SIP) allows a caller to express preferences that the call
   be routed to a User Agent (UA) with particular capabilities.
   Similarly, a specification exists to allow a UA to indicate its
   capabilities in a registration.  Amongst those capabilities are the
|  type of media streams the agent supports, described as top-level MIME
|  types.  The 'application' MIME type is used to describe a broad range
   of stream types, and it provides insufficient granularity as a
   capability.  This specification allows a UA to indicate which
   application subtypes the agent supports.

c)  Section 3, 1st para

   The 'sip.app-subtype' media feature tag is of type token with a case-
   insensitive equality relationship.  Its value can be any registered
|  or private MIME application subtype compliant to the subtype-name
   grammar defined in [RFC4288].  [...]

[[ see also subsequent errata note covering another issue as well ! ]]

d)  Section 3, 3rd para

   It is important to note that this media feature tag is only
   indicating the streaming media types that a user agent is capable of
   supporting.  It says nothing about the functionality provided by the
|  user agent itself or the MIME types that the agent can send or
   receive in SIP messages or emails.  For example, let us assume that a
   SIP user agent is capable of supporting a chess game.  The game is
   played by each user sending chess moves as binary objects over UDP
|  between a pair of user agents.  Those objects have a MIME type of
   "application/example".  [...]

e)  Section 3, 4th para

   A consequence of this is that, as new streaming media type formats
   are defined (such as game stream formats, whiteboard session formats,
   and so on), they SHOULD be defined using the SDP application stream
|  and utilize a MIME application subtype.

f)  Section 6, 4th para

   Summary of the media feature indicated by this tag:  This feature tag
|     indicates the MIME application subtypes supported by the agent for
      purposes of streaming media.

It should say:

a)
        A Session Initiation Protocol (SIP) Media Feature Tag for
                      'Application' Media Subtypes

b)

   The caller preferences specification for the Session Initiation
   Protocol (SIP) allows a caller to express preferences that the call
   be routed to a User Agent (UA) with particular capabilities.
   Similarly, a specification exists to allow a UA to indicate its
   capabilities in a registration.  Amongst those capabilities are the
|  type of media streams the agent supports, described as top-level media
|  types.  The 'application' media type is used to describe a broad range
   of stream types, and it provides insufficient granularity as a
   capability.  This specification allows a UA to indicate which
   application subtypes the agent supports.

c)

   The 'sip.app-subtype' media feature tag is of type token with a case-
   insensitive equality relationship.  Its value can be any registered
|  or private 'application' media subtype compliant to the subtype-name
   grammar defined in [RFC4288].  [...]

d)
   It is important to note that this media feature tag is only
   indicating the streaming media types that a user agent is capable of
   supporting.  It says nothing about the functionality provided by the
|  user agent itself or the media types that the agent can send or
   receive in SIP messages or emails.  For example, let us assume that a
   SIP user agent is capable of supporting a chess game.  The game is
   played by each user sending chess moves as binary objects over UDP
|  between a pair of user agents.  Those objects have a media type of
   "application/example".  [...]

e)

   A consequence of this is that, as new streaming media type formats
   are defined (such as game stream formats, whiteboard session formats,
   and so on), they SHOULD be defined using the SDP application stream
|  and utilize an 'application' media subtype.

f)

   Summary of the media feature indicated by this tag:  This feature tag
|     indicates the 'application' media subtypes supported by the agent
      for purposes of streaming media.

Notes:

Rationale:
The subject of the RFC is SIP, not e-Mail, the 3rd letter in "MIME".
Therefore, the RFC should better follow the explanations given in
RFC 4288, which places the original concepts from MIME that have
proven generally useful into a more general context and strongly
recommends talking about "media types" and "media subtypes".
That reasoning similarly holds for Media Features, which for
obvious reasons not have been denoted "MIME Features".
----------------------------------------------------------------------
Recommended status:  (correct) Hold for document update
Type: Editorial
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RFC5688, "A Session Initiation Protocol (SIP) Media Feature Tag for
MIME Application Subtypes"
Source of RFC: IETF - NON WORKING GROUP
Area Assignment: rai

Errata ID: 1998

Status: Reported
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2010-01-10

Section 1, 4th para says:

   RFC 3840 defines media feature tags for each and every top-level
   media type, including 'application'.  This media type covers an
   extremely broad range of subtypes -- multiplayer games of all sorts,
   shared whiteboards and application sharing, and so on.  With audio
|  and video, where there is often a common codec supported by agents
   (i.e., a common subtype).  [...]

It should say:

   RFC 3840 defines media feature tags for each and every top-level
   media type, including 'application'.  This media type covers an
   extremely broad range of subtypes -- multiplayer games of all sorts,
   shared whiteboards and application sharing, and so on.  With audio
|  and video, there is often a common codec supported by agents (i.e.,
   a common subtype).  [...]

Notes:

Rationale: grammar; the original sentence sounds incomplete.
Therefore, strike "where".
----------------------------------------------------------------------
Recommended status:  (correct) Hold for document update
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RFC5727, "Change Process for the Session Initiation Protocol (SIP) and
the Real-time Applications and Infrastructure Area"
Source of RFC: IETF - NON WORKING GROUP
Area Assignment: rai

Errata ID: 2091

Status: Reported
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2010-03-21

Section 7. says:

[ 4th para of section, at the bottom of page 11: ]
 =20
|                                   [...], at the discretion the
   Designated Expert).  Short forms of header fields MUST only be
   assigned to Standards Track header fields.


It should say:

|                                   [...], at the discretion of the
   Designated Expert).  Short forms of header fields MUST only be
   assigned to Standards Track header fields.

Notes:

Rationale: missing word "of".

Remark -- another nit (keep for update):
The trailing period is missing from the first paragraph of Section 1.
----------------------------------------------------------------------
Recommended status:  (correct) Hold for document update
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Dale

From dworley@avaya.com  Fri Jan  7 19:58:53 2011
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 9F51F3A694F; Fri,  7 Jan 2011 19:58:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level: 
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, 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 oPkN+dPE0lDl; Fri,  7 Jan 2011 19:58:52 -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 699743A68F7; Fri,  7 Jan 2011 19:58:46 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJdvJ02HCzI1/2dsb2JhbACkPHOmHAKVfIVMBIRniV0
X-IronPort-AV: E=Sophos;i="4.60,292,1291611600"; d="scan'208";a="53396683"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 07 Jan 2011 23:00:52 -0500
X-IronPort-AV: E=Sophos;i="4.60,292,1291611600"; d="scan'208";a="579347004"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 07 Jan 2011 23:00:22 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 7 Jan 2011 23:00:22 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "sipping@ietf.org" <sipping@ietf.org>, "rai@ietf.org" <rai@ietf.org>
Date: Fri, 7 Jan 2011 22:59:57 -0500
Thread-Topic: draft-ietf-sipping-media-policy-dataset:  The implied boolean logic of policy operations
Thread-Index: AQHLruiRGh23zb4rIEW+il/SkQBD5w==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288B68@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: The implied boolean logic of policy operations
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: Sat, 08 Jan 2011 03:58:53 -0000

I am starting work on a messy part of the media policy dataset
definition:  Specifying the logic when a policy is applied to a
session-info, and also specifying how two policies are combined to
apply jointly to session-infos.  The goal is to implement one's
intuitive expectations while introducing as few special cases as
possible.

My current analysis is:

- The primary operation is applying a session-policy to a session-info
  to produce a possibly more restricted session-info.  This is done by
  applying the session-policy to each stream in turn, which may
  "restrict" the stream (in regard to bandwidth, codecs, etc.).

- A stream may be restricted to the point that it permits no media
  whatsoever.  Such "null" streams are all logically equivalent,
  although a null stream can be represented in many different ways.
  When translated back into SDP, a null stream becomes a rejected
  m=3D line.

- The different <stream> elements in a session-policy are effectively
  ORed together, in that the policy intends to permit any stream that
  conforms to *any one* of the <stream> elements.  This is necessary
  because e.g. a session-policy can contain one <stream> that specifies
  audio media and restricts the codecs permitted for audio, and
  another <stream> that specifies video media and restricts the codecs
  permitted for video.

- Thus, applying a session-policy to a stream involves applying each
  session-policy <stream> to the stream, and then choosing the "best"
  result.  In practice, we expect that the streams admitted by the
  session-policy <stream> elements to be disjoint (e.g., one is for
  audio, one is for video), so the result of applying any but one
  <stream> will be a null stream, and the "best" result will be the
  only non-null result.

- The alternative strategy of "unioning" the results of applying each
  <stream> element cannot be used because it can allow the resulting
  session to exceed all of the <stream> element policies.  Consider
  the policy

      <streams>
        <stream> codecs: audio/foo, bandwidth: 10 </stream>
        <stream> codecs: audio/foo,audio/bar, bandwidth: 1 </stream>
      </streams>

  applied to the requested stream "codecs: audio/foo,audio/bar,
  bandwidth: 10".  The result of restricting with the first <stream>
  is "codecs: audio/foo, bandwidth: 10" and the result of restricting
  with the second <stream> is "codecs: audio/foo,audio/bar, bandwidth:
  1".  The union of the two (the "smallest" stream that contains them
  both) is "codecs: audio/foo,audio/bar, bandwidth: 10", which is not
  allowed by either <stream>.

- Within this context, combining two policies to form a joint policy
  that enforces both their restrictions simultaneously is simple:  The
  resulting policy is made by "intersecting" all possible pairs of
  <stream>s, one from the first policy and one from the second policy.
  (Intersections that result in null policies can be dropped from the
  result.)

- I haven't studied the role of the directional attributes yet, but
  currently I believe that a bidirectional session-info <stream> can
  be treated as an abbreviation for two session-info <stream>s, one in
  each direction, and a bidirectional session-policy <stream> can be
  treated similarly.  Or, directionality can be treated as an
  attribute with two possible values, *with identical results*.

Comments?

Dale

From andreaf@cs.columbia.edu  Mon Jan 10 13:29:15 2011
Return-Path: <andreaf@cs.columbia.edu>
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 E31573A6802; Mon, 10 Jan 2011 13:29:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 jkNFspgN75Y8; Mon, 10 Jan 2011 13:29:14 -0800 (PST)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by core3.amsl.com (Postfix) with ESMTP id 1B30F3A67EE; Mon, 10 Jan 2011 13:29:14 -0800 (PST)
Received: from irtdesk1.cs.columbia.edu (irtdesk1.cs.columbia.edu [128.59.22.127]) (user=agf2104 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id p0ALVOJj008300 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 10 Jan 2011 16:31:25 -0500 (EST)
Message-ID: <4D2B7AAC.2080100@cs.columbia.edu>
Date: Mon, 10 Jan 2011 16:31:24 -0500
From: Andrea G Forte <andreaf@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Shida Schubert <shida@ntt-at.com>
References: <E4F25D10-B47A-43AC-9EB8-E8AB4E997968@ntt-at.com>
In-Reply-To: <E4F25D10-B47A-43AC-9EB8-E8AB4E997968@ntt-at.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.7
X-Mailman-Approved-At: Tue, 11 Jan 2011 07:47:04 -0800
Cc: Marc Linsner <mlinsner@cisco.com>, rai@ietf.org, ecrit@ietf.org
Subject: Re: [RAI] RAI-ART review for draft-forte-lost-extensions-02.txt
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: Mon, 10 Jan 2011 21:29:16 -0000

Please read comments inline.

Thanks,
-Andrea


On 12/31/10 6:26 AM, Shida Schubert wrote:
> I am the assigned RAI-ART reviewer for draft-forte-lost-extensions-02.txt.
>
> For background on RAI-ART, please see the FAQ at<http://www.softarmor.com/rai/art/FAQ.html>.
>
> Please resolve these comments along with any other comments you may receive.
>
> ***
> This draft is basically ready for publication, but has nits that should be fixed before publication.
> ***
>
> I am sending the nits to the authors so I am sending few technical concerns I have on the lists.
>
> ** Comments on the draft **
>
> 0. This draft	 alters a definition of region for non-emergency services, should this be
>       updating the RFC5222 in anyway? I am not sure if it should as emergency case
>       is obviously the main user of the protocol but will this be the case, say in 5 years?
I do not have any particular position on this.

> 1. Looking at the definition of "query" in RFC5222, the draft is not really defining
>      a new queries but defining a filter to limit the results. I don't feel that term
>      "queries" for this extension defined in this draft is appropriate. I apologize for not being
>      able to come up with a proposal but "query" just didn't sound right..
I do not agree with this. A filter as such, is applied on a number of 
existing results to further constrain
them based on some metric. In this case, we do not have a pre-existing 
set of results that we are filtering, here we
"ask" the server a more specific question and the server replies with 
the results fulfilling this specific question.

In RFC 5222 it reads:
"The query message carries location information and a service
    identifier encoded as a Uniform Resource Name (URN) (see [9]) from
    the LoST client to the LoST server.  The LoST server uses its
    database to map the input values to one or more Uniform Resource
    Identifiers (URIs) and returns those URIs along with optional
    information, such as hints about the service boundary, in a response
    message to the LoST client."

This is true also for our new queries. Can you please let me know where 
in RFC 5222 you see a definition of query
that is in contrast with what we define in the draft?

> 2. The draft clearly states that these extensions are NOT applicable to the
>       emergency uses. If that is the case the draft should probably say that it MUST NOT be
>       used in emergency cases somewhere in the draft, especially if it has negative
>       implication (I couldn't think of any but..).
OK, we will add the MUST NOT.

> 3.<region>  is used when you want to query the LoST server to find a service
>       that serves the requesting entity's location but default behavior of LoST as
>       defined in RFC5222 is to conduct a query based on the region so this seems
>       tad bit odd to me. Especially because when<region>  is absent, one is supposed
>       to conduct a search based on the distance from the user but it should be the
>       other way around. Either say that when<region>  is absent it is assumed true
>       or define alternative element which describes that it's for doing a "instance within
>       X distance".
Yes, to have a more consistent behavior between emergency and 
non-emergency services,
we can say that when <region> is absent, it is assumed to be true rather 
than false.
> ** General comments about the use of LoST for service other than emergency **
>
> I think this draft highlights lack of consideration during the creation of LoST generic uses
> beside emergency services and this raises some concerns not necessary with this draft
> but with the generic use of LoST in general.
>
> 1. When LoST server is used for generic uses, I believe the server will be stressed a lot
>      more than when used for Emergency cases due to unique computation required for
>      querying users's location to service region of the service or searching for services
>      within distance X. I just hope that encouraging
>      the use of LoST for generic uses will not interfere with the Emergency service in anyway..
>      I am assuming that in real deployment, the LoST server that handles the initial request
>      will probably dispatch or redirect the request to appropriate server that can handle the
>      requested service, so LoST serve that will handle the mapping of location to PSAP will
>      not be overwhelmed by trying to figure out what pizza delivery is close to Joe's current
>      location.
In real deployments I do not think that LoST servers in the ESInet will 
be available also for non-emergency
services. I think that access to the ESInet will be granted only for 
serving emergency queries or perhaps other
government-related needs.

>
>
> 2. Although, I am assuming most or all of the remaining queries will function as
>      defined in RFC5222, I think we should probably look at how the rest of the
>      query beside<findservice>  will look like and behave when used for generic uses.
>
>     e.g.
>      How useful is the listservice / listserviceresponse in generic uses as is now?
>>> Should there be an extension to query<listservice>  with a filter so
>              only a sub-element will be displayed (querying the LoST server with
>              urn:service:restaurants or urn:service:stores?
>
>     This has nothing to do with the draft in question.. But something we may want to
>     think about if we are going to encourage people to implement LoST for non-emergency services.
>
> Regards
>   Shida


From shida@ntt-at.com  Sun Jan 16 16:54:01 2011
Return-Path: <shida@ntt-at.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 5D7343A6BA2 for <rai@core3.amsl.com>; Sun, 16 Jan 2011 16:54:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 gcstEPZEbTfk for <rai@core3.amsl.com>; Sun, 16 Jan 2011 16:53:59 -0800 (PST)
Received: from gateway03.websitewelcome.com (gateway03.websitewelcome.com [69.93.239.22]) by core3.amsl.com (Postfix) with SMTP id 6359A3A67C0 for <rai@ietf.org>; Sun, 16 Jan 2011 16:53:59 -0800 (PST)
Received: (qmail 12083 invoked from network); 17 Jan 2011 00:55:35 -0000
Received: from gator465.hostgator.com (69.56.174.130) by gateway03.websitewelcome.com with SMTP; 17 Jan 2011 00:55:35 -0000
Received: from [60.237.173.240] (port=53385 helo=[192.168.1.10]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1PedOU-0005LV-13; Sun, 16 Jan 2011 18:56:27 -0600
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Shida Schubert <shida@ntt-at.com>
In-Reply-To: <4D2B7AAC.2080100@cs.columbia.edu>
Date: Mon, 17 Jan 2011 09:56:27 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD8ECF67-29F3-4D14-95DA-641665AA75B4@ntt-at.com>
References: <E4F25D10-B47A-43AC-9EB8-E8AB4E997968@ntt-at.com> <4D2B7AAC.2080100@cs.columbia.edu>
To: Andrea G Forte <andreaf@cs.columbia.edu>
X-Mailer: Apple Mail (2.1082)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
Cc: Marc Linsner <mlinsner@cisco.com>, rai@ietf.org, ecrit@ietf.org
Subject: Re: [RAI] RAI-ART review for draft-forte-lost-extensions-02.txt
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: Mon, 17 Jan 2011 00:54:01 -0000

Hi Andrea;

 My comments inline.

On Jan 11, 2011, at 6:31 AM, Andrea G Forte wrote:

> Please read comments inline.
>=20
> Thanks,
> -Andrea
>=20
>=20
> On 12/31/10 6:26 AM, Shida Schubert wrote:
>> I am the assigned RAI-ART reviewer for =
draft-forte-lost-extensions-02.txt.
>>=20
>> For background on RAI-ART, please see the FAQ =
at<http://www.softarmor.com/rai/art/FAQ.html>.
>>=20
>> Please resolve these comments along with any other comments you may =
receive.
>>=20
>> ***
>> This draft is basically ready for publication, but has nits that =
should be fixed before publication.
>> ***
>>=20
>> I am sending the nits to the authors so I am sending few technical =
concerns I have on the lists.
>>=20
>> ** Comments on the draft **
>>=20
>> 0. This draft	 alters a definition of region for non-emergency =
services, should this be
>>      updating the RFC5222 in anyway? I am not sure if it should as =
emergency case
>>      is obviously the main user of the protocol but will this be the =
case, say in 5 years?
> I do not have any particular position on this.

 Same here. I think we need additional feedback on this.=20

>=20
>> 1. Looking at the definition of "query" in RFC5222, the draft is not =
really defining
>>     a new queries but defining a filter to limit the results. I don't =
feel that term
>>     "queries" for this extension defined in this draft is =
appropriate. I apologize for not being
>>     able to come up with a proposal but "query" just didn't sound =
right..
> I do not agree with this. A filter as such, is applied on a number of =
existing results to further constrain
> them based on some metric. In this case, we do not have a pre-existing =
set of results that we are filtering, here we
> "ask" the server a more specific question and the server replies with =
the results fulfilling this specific question.
>=20
> In RFC 5222 it reads:
> "The query message carries location information and a service
>   identifier encoded as a Uniform Resource Name (URN) (see [9]) from
>   the LoST client to the LoST server.  The LoST server uses its
>   database to map the input values to one or more Uniform Resource
>   Identifiers (URIs) and returns those URIs along with optional
>   information, such as hints about the service boundary, in a response
>   message to the LoST client."
>=20
> This is true also for our new queries. Can you please let me know =
where in RFC 5222 you see a definition of query
> that is in contrast with what we define in the draft?

 The definition you are referring doesn't necessary contradict with what=20=

you are defining in the draft, but RFC5222 section 3 clearly=20
identifies type of queries associated to each request type.

 This draft definitely doesn't add any new request type, rather it=20
uses the pre-existing request type (findservice etc.) to allow=20
specific search to be conducted at LoST.=20

 AFAIK It's not a new query that you are defining, but an extension=20
to an existing query which alter the semantics of the request to get=20
desirable result.=20

 I don't really have a strong opinion on this, but when I was reading, =
it=20
was rather confusing to say that you are defining new queries.=20

 Furthermore does it make sense to have these extension elements=20
appear in other query type?=20

>=20
>> 2. The draft clearly states that these extensions are NOT applicable =
to the
>>      emergency uses. If that is the case the draft should probably =
say that it MUST NOT be
>>      used in emergency cases somewhere in the draft, especially if it =
has negative
>>      implication (I couldn't think of any but..).
> OK, we will add the MUST NOT.
>=20
>> 3.<region>  is used when you want to query the LoST server to find a =
service
>>      that serves the requesting entity's location but default =
behavior of LoST as
>>      defined in RFC5222 is to conduct a query based on the region so =
this seems
>>      tad bit odd to me. Especially because when<region>  is absent, =
one is supposed
>>      to conduct a search based on the distance from the user but it =
should be the
>>      other way around. Either say that when<region>  is absent it is =
assumed true
>>      or define alternative element which describes that it's for =
doing a "instance within
>>      X distance".
> Yes, to have a more consistent behavior between emergency and =
non-emergency services,
> we can say that when <region> is absent, it is assumed to be true =
rather than false.
>> ** General comments about the use of LoST for service other than =
emergency **
>>=20
>> I think this draft highlights lack of consideration during the =
creation of LoST generic uses
>> beside emergency services and this raises some concerns not necessary =
with this draft
>> but with the generic use of LoST in general.
>>=20
>> 1. When LoST server is used for generic uses, I believe the server =
will be stressed a lot
>>     more than when used for Emergency cases due to unique computation =
required for
>>     querying users's location to service region of the service or =
searching for services
>>     within distance X. I just hope that encouraging
>>     the use of LoST for generic uses will not interfere with the =
Emergency service in anyway..
>>     I am assuming that in real deployment, the LoST server that =
handles the initial request
>>     will probably dispatch or redirect the request to appropriate =
server that can handle the
>>     requested service, so LoST serve that will handle the mapping of =
location to PSAP will
>>     not be overwhelmed by trying to figure out what pizza delivery is =
close to Joe's current
>>     location.
> In real deployments I do not think that LoST servers in the ESInet =
will be available also for non-emergency
> services. I think that access to the ESInet will be granted only for =
serving emergency queries or perhaps other
> government-related needs.

 I don't think how you would do this.=20

 How would the client know which LoST server is for ESInet and which one =
isn't?=20

 LoST is not like DNS, where you can look at the root domain and =
dispatch/delegate=20
the request to appropriate server. With LoST, LoST server would have to =
parse the=20
XML to see if the request is for emergency or non-emergency service.=20

 However, it's an HTTP server after all and I do think scaling HTTP =
server=20
is probably trivial so I will withdraw my concern on this.=20

 Regards
  Shida

>=20
>>=20
>>=20
>> 2. Although, I am assuming most or all of the remaining queries will =
function as
>>     defined in RFC5222, I think we should probably look at how the =
rest of the
>>     query beside<findservice>  will look like and behave when used =
for generic uses.
>>=20
>>    e.g.
>>     How useful is the listservice / listserviceresponse in generic =
uses as is now?
>>>> Should there be an extension to query<listservice>  with a filter =
so
>>             only a sub-element will be displayed (querying the LoST =
server with
>>             urn:service:restaurants or urn:service:stores?
>>=20
>>    This has nothing to do with the draft in question.. But something =
we may want to
>>    think about if we are going to encourage people to implement LoST =
for non-emergency services.
>>=20
>> Regards
>>  Shida
>=20


From magnus.westerlund@ericsson.com  Wed Jan 19 07:08:30 2011
Return-Path: <magnus.westerlund@ericsson.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 EAB913A715D for <rai@core3.amsl.com>; Wed, 19 Jan 2011 07:08:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.489
X-Spam-Level: 
X-Spam-Status: No, score=-106.489 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 3qY4U6t8EEGA for <rai@core3.amsl.com>; Wed, 19 Jan 2011 07:08:30 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id D40623A713E for <rai@ietf.org>; Wed, 19 Jan 2011 07:08:29 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-a0-4d36ff0d3a4a
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id C8.59.23694.D0FF63D4; Wed, 19 Jan 2011 16:11:09 +0100 (CET)
Received: from [147.214.183.170] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.2.234.1; Wed, 19 Jan 2011 16:11:08 +0100
Message-ID: <4D36FF0D.8040002@ericsson.com>
Date: Wed, 19 Jan 2011 16:11:09 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "rai@ietf.org" <rai@ietf.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: [RAI] Fwd: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the	Service Name and Transport Protocol Port Number Registry) to BCP
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, 19 Jan 2011 15:08:31 -0000

Hi,

I just want to make people aware of this IETF last call for an update of
the IANA procedures for registration of Service Name and Transport
protocol port numbers.

Best Regards

Magnus Westerlund

-------- Ursprungligt meddelande --------
Ämne: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet
Assigned	Numbers Authority (IANA) Procedures for the Management of the
Service Name and Transport Protocol Port Number Registry) to BCP
Datum: Tue, 18 Jan 2011 22:26:03 +0100
Från: The IESG <iesg-secretary@ietf.org>
Till: IETF-Announce <ietf-announce@ietf.org>
Kopia: tsvwg@ietf.org <tsvwg@ietf.org>


The IESG has received a request from the Transport Area Working Group WG
(tsvwg) to consider the following document:
- 'Internet Assigned Numbers Authority (IANA) Procedures for the
   Management of the Service Name and Transport Protocol Port Number
   Registry'
  <draft-ietf-tsvwg-iana-ports-09.txt> as a BCP

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-02-01. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-iana-ports/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-iana-ports/


No IPR declarations have been submitted directly on this I-D.
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


From D.Malas@cablelabs.com  Mon Jan 24 13:13:24 2011
Return-Path: <D.Malas@cablelabs.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 286C43A6B40 for <rai@core3.amsl.com>; Mon, 24 Jan 2011 13:13:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.163
X-Spam-Level: 
X-Spam-Status: No, score=-100.163 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_93=0.6, 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 Q9dHSbVZ2ybz for <rai@core3.amsl.com>; Mon, 24 Jan 2011 13:13:23 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id DA5633A6B39 for <rai@ietf.org>; Mon, 24 Jan 2011 13:13:22 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id p0OLGH26009653 for <rai@ietf.org>; Mon, 24 Jan 2011 14:16:17 -0700
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Mon, 24 Jan 2011 14:16:17 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Mon, 24 Jan 2011 14:16:17 -0700
From: Daryl Malas <D.Malas@cablelabs.com>
To: "'rai@ietf.org'" <rai@ietf.org>
Date: Mon, 24 Jan 2011 14:16:17 -0700
Thread-Topic: [RAI] FW: RFC 6076 on Basic Telephony SIP End-to-End Performance Metrics
Thread-Index: Acu8C80eyAA5k8roSE+TtDtj6sW/4A==
Message-ID: <114DAD31379DFA438C0A2E39B3B8AF5D016D99A8B2@srvxchg>
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
X-Approved: ondar
Subject: [RAI] FW: RFC 6076 on Basic Telephony SIP End-to-End Performance Metrics
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: Mon, 24 Jan 2011 21:13:24 -0000

FYI...

-----Original Message-----
A new Request for Comments is now available in online RFC libraries.

       =20
        RFC 6076

        Title:      Basic Telephony SIP End-to-End Performance=20
                    Metrics=20
        Author:     D. Malas, A. Morton
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2011
        Mailbox:    d.malas@cablelabs.com,=20
                    acmorton@att.com
        Pages:      27
        Characters: 61559
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pmol-sip-perf-metrics-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6076.txt

This document defines a set of metrics and their usage to evaluate the perf=
ormance of end-to-end Session Initiation Protocol (SIP) for telephony servi=
ces in both production and testing environments.  The purpose of this docum=
ent is to combine a standard set of common metrics, allowing interoperable =
performance measurements, easing the comparison of industry implementations=
.  [STANDARDS-TRACK]

This document is a product of the Performance Metrics for Other Layers Work=
ing Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track protoc=
ol for the Internet community,and requests discussion and suggestions for i=
mprovements.  Please refer to the current edition of the Internet Official =
Protocol Standards (STD 1) for the standardization state and status of this=
 protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the author =
of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless specifical=
ly noted otherwise on the RFC itself, all RFCs are for unlimited distributi=
on.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
PMOL mailing list
PMOL@ietf.org
https://www.ietf.org/mailman/listinfo/pmol

From Martin.Thomson@andrew.com  Mon Jan 24 18:54:00 2011
Return-Path: <Martin.Thomson@andrew.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 DF7F43A6A0E for <rai@core3.amsl.com>; Mon, 24 Jan 2011 18:54:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599]
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 KKtUrLesYDtL for <rai@core3.amsl.com>; Mon, 24 Jan 2011 18:53:59 -0800 (PST)
Received: from csmailgw1.commscope.com (csmailgw1.commscope.com [198.135.207.244]) by core3.amsl.com (Postfix) with ESMTP id 71B6F3A699F for <rai@ietf.org>; Mon, 24 Jan 2011 18:53:59 -0800 (PST)
Received: from [10.86.20.103] ([10.86.20.103]:45145 "EHLO ACDCE7HC2.commscope.com") by csmailgw1.commscope.com with ESMTP id S41860031Ab1AYC4x (ORCPT <rfc822;rai@ietf.org>); Mon, 24 Jan 2011 20:56:53 -0600
Received: from SISPE7HC2.commscope.com (10.97.4.13) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.3.137.0; Mon, 24 Jan 2011 20:56:49 -0600
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC2.commscope.com ([fe80::58c3:2447:f977:57c3%10]) with mapi; Tue, 25 Jan 2011 10:56:46 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: "draft-forte-lost-extensions@tools.ietf.org"  <draft-forte-lost-extensions@tools.ietf.org>, "rai@ietf.org" <rai@ietf.org>
Date: Tue, 25 Jan 2011 10:56:43 +0800
Thread-Topic: Review of draft-forte-lost-extensions-02
Thread-Index: Acu8O37v0ZKyLmJNRLasKtY7VUK5ag==
Message-ID: <8B0A9FCBB9832F43971E38010638454F03FEA1493B@SISPE7MB1.commscope.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw1.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Cc: "rai-ads@tools.ietf.org" <rai-ads@tools.ietf.org>
Subject: [RAI] Review of draft-forte-lost-extensions-02
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: Tue, 25 Jan 2011 02:54:01 -0000

UmV2aWV3IG9mIGRyYWZ0LWZvcnRlLWxvc3QtZXh0ZW5zaW9ucy0wMg0KTWFydGluIFRob21zb24s
IDIwMTEtMDEtMjUNCg0KICBJIGRvbid0IHRoaW5rIHRoYXQgSSd2ZSBoYWQgdGhlIG9wcG9ydHVu
aXR5IHRvIGNvbW1lbnQgb24gdGhpcyBkcmFmdA0KICBiZWZvcmUuICBUaGVyZSBhcmUgc2V2ZXJh
bCBpc3N1ZXMgdGhhdCBJIHRoaW5rIHByZXZlbnQgdGhpcyBkcmFmdCBmcm9tDQogIGJlaW5nIHRo
ZSBiYXNpcyBmb3IgaW50ZXJvcGVyYWJsZSBpbXBsZW1lbnRhdGlvbnMuDQoNCiAgVGhlIG1vc3Qg
c2lnbmlmaWNhbnQgY29uY2VybiBJIGhhdmUgYXJpc2VzIGZyb20gdGhlIHVuZGVybHlpbmcgbW9k
ZWwgdGhhdA0KICBpcyB1c2VkIHRvIGRlZmluZSB0aGUgZXh0ZW5zaW9ucyB0byB0aGUgPGZpbmRT
ZXJ2aWNlPiBxdWVyeS4gIExhY2sgb2YNCiAgY2xhcml0eSBvbiBob3cgdGhlIGRyYWZ0IGRlZmlu
ZXMgdGhlIHByb2JsZW0gdHJhbnNsYXRlcyBpbnRvIHdoYXQgSSB0aGluaw0KICBpcyBhIGNvbmZ1
c2VkIHNvbHV0aW9uLg0KDQogIFRoZSBzb2x1dGlvbiBhcyBkZXNjcmliZWQgY2FuIGJlIG1hZGUg
dG8gd29yaywgYnV0IGl0IHJlbGllcyBvbg0KICBhc3N1bXB0aW9ucyB0aGF0IGFyZSBub3QgZG9j
dW1lbnRlZC4gIEFzIGRvY3VtZW50ZWQsIHRoZXJlIGFyZSBsaWtlbHkgdG8NCiAgYmUgaW50ZXJv
cGVyYWJpbGl0eSBpc3N1ZXMuDQoNClRlcm1pbm9sb2d5DQogIFNlY3Rpb24gMyBvZiB0aGlzIGRv
Y3VtZW50IHJlZmluZXMgdGhlIGNvbmNlcHQgb2YgYSBzZXJ2aWNlIHJlZ2lvbi4NCiAgVGhyZWUg
Y29uY2VwdHMgYXJlIGV4dHJhY3RlZCBmcm9tIHRoZSBiYXNpYyBpZGVhcyBpbiBSRkMgNTIyMjoN
Cg0KICAgIDEuIHNlcnZpY2VzIHdpdGhvdXQgdGhlIGNvbmNlcHQgb2YgYSBzZXJ2aWNlIHJlZ2lv
biAocG9pbnQtYmFzZWQNCiAgICAgICBzZXJ2aWNlcyB0aGF0IGFyZSBpZGVudGlmaWVkIHB1cmVs
eSBieSBwcm94aW1pdHkpDQoNCiAgICAyLiBzZXJ2aWNlcyB0aGF0IHNlcnZlIGEgZ2VvZ3JhcGhp
YyBhcmVhIHdoZXJlIHRoZSBnZW9ncmFwaGljIGFyZWEgZm9yDQogICAgICAgZGlmZmVyZW50IHNl
cnZpY2VzIG9mIHRoZSBzYW1lIGJhc2ljIHR5cGUgb3ZlcmxhcCBzaWduaWZpY2FudGx5IChmb3IN
CiAgICAgICBleGFtcGxlLCB0aGUgb3ZlcmxhcHBpbmcgc2VydmluZyBhcmVhIG9mIGNvbXBldGlu
ZyBob21lIGRlbGl2ZXJ5DQogICAgICAgc2VydmljZXMpDQoNCiAgICAzLiBzZXJ2aWNlcyB0aGF0
IHNlcnZlIHN0cmljdGx5IG5vbi1vdmVybGFwcGluZyBnZW9ncmFwaGljIGFyZWFzIGZvciBhDQog
ICAgICAgcGFydGljdWxhciBzZXJ2aWNlICh0aGF0IGlzLCBQU0FQcykNCg0KICBUaGUgbGF0dGVy
IHR3byBjYXNlcyBhcmUgYm90aCByZWZlcnJlZCB0byBhcyAic2VydmljZSByZWdpb24iIHdpdGhv
dXQNCiAgcXVhbGlmaWNhdGlvbi4gIEl0IGFwcGVhcnMgdGhhdCAoMikgaXMgdGhlIGNvbmNlcHQg
aW50ZW5kZWQgaW4gbW9zdA0KICBjYXNlcy4gIFNvbWUgY2xlYXJlciB0ZXJtaW5vbG9neSBtaWdo
dCBoZWxwLiAgUGVyaGFwcyBpZiB5b3UgdXNlICJzZXJ2aWNlDQogIGJvdW5kYXJ5IiAtIGFzIFJG
QyA1MjIyIHVzZXMgaXQgLSB0byByZWZlciB0byB0aGUgZmVuY2UgdGhhdCBpcyBjcm9zc2VkDQog
IHdoZXJlIGFuc3dlcnMgbWlnaHQgY2hhbmdlOyBhbmQgInNlcnZlZCByZWdpb24iIG9yIHRvIHJl
ZmVyIHRvIHRoZQ0KICBnZW9ncmFwaGljIGFyZWEgdGhhdCBpcyBzZXJ2ZWQgYnkgdGhlIHBhcnRp
Y3VsYXIgc2VydmljZSBpbnN0YW5jZS4NCg0KICBUaHVzIHlvdSBjYW4gb2JzZXJ2ZSB0aGF0IHNl
cnZpY2UgYm91bmRhcmllcyBtaWdodCBiZSBvZiBsaW1pdGVkIHVzZQ0KICB3aGVyZSBtdWx0aXBs
ZSBzZXJ2aWNlcyBvZiB0aGUgc2FtZSB0eXBlIGhhdmUgb3ZlcmxhcHBpbmcgc2VydmVkIHJlZ2lv
bnMuDQogIEFuZCB5b3UgY2FuIGFsc28gb2JzZXJ2ZSB0aGF0IHNvbWUgc2VydmljZXMgbGFjayBh
IHNlcnZlZCBhcmVhOyBhbmQgZm9yDQogIHRoZXNlIHNlcnZpY2VzLCBhIHNlcnZpY2UgYm91bmRh
cnkgbWF5IGZvciBkaWZmZXJlbnQgcmVhc29ucyAoaXQncyBvbmx5DQogIHRoZSBhcmVhIHdoZXJl
IHRoZSBOIHNlcnZpY2UgaW5zdGFuY2VzIHByb3ZpZGVkIGluIHRoZSBhbnN3ZXIgYXJlIGNsb3Nl
cg0KICB0aGFuIG90aGVyIGluc3RhbmNlcykuDQoNCkV4dGVuc2lvbiBwcm9wb3NhbHMNCiAgUkZD
IDUyMjIgaXMgZHJlYWRmdWxseSB2YWd1ZSBvbiB0aGUgdXNlIG9mIGdlb2dyYXBoaWMgYXJlYXMg
aW4gdGhlDQogIDxsb2NhdGlvbj4gZWxlbWVudC4gIFBhcnRpY3VsYXJseSB3aGVuIHRoZSBhcmVh
IGludGVyc2VjdHMgd2l0aCB0aGUgYXJlYXMNCiAgb2YgbXVsdGlwbGUgc2VydmljZXMuICBJIGhh
dmUgaW5mZXJyZWQgdGhhdCB0aGUgaWRlYSBpcyB0aGF0IHRoZSBMb1NUDQogIHNlcnZlciBwaWNr
cyB0aGUgc2luZ2xlIGJlc3QgY2hvaWNlLCBiZWNhdXNlIHRoYXQgbWFrZXMgdGhlIG1vc3Qgc2Vu
c2UNCiAgZm9yIGVtZXJnZW5jeSB1c2VzIChubyBnb29kIGNvbWVzIGZyb20gcHJlc2VudGluZyBh
IGNob2ljZSBpbiB0aGVzZQ0KICBjYXNlcykuDQoNCiAgV2hhdCB0aGlzIGRyYWZ0IHByb3Bvc2Vz
IGZvciAid2l0aGluIFgiIHJlbGllcyBvbiBzb21lIHNvcnQgb2YgaW1wbGljaXQNCiAgcHJvY2Vz
c2luZyB0aGF0IGlzIGluY29uc2lzdGVudCB3aXRoIFJGQzUyMjIuICBJdCByZWxpZXMgb24gdGhl
IGZhY3QgdGhhdA0KICB0aGUgTG9TVCBzZXJ2ZXIga25vd3MgdGhhdCBhIHBhcnRpY3VsYXIgc2Vy
dmljZSBpcyBzb21laG93IHNwZWNpYWwuDQoNCiAgVGhpcyBkb2Vzbid0IG1ha2UgZm9yIHZlcnkg
Y2xlYXIgcHJvdG9jb2wgc2VtYW50aWNzLiAgSXQncyBwcm9iYWJseSBzdGlsbA0KICB2aWFibGUs
IGJ1dCB0aGUgZG9jdW1lbnQgbmVlZHMgdG8gbWFrZSB0aGlzIGFzc3VtcHRpb24gY2xlYXIuDQoN
CiAgSSdtIG5vdCBzdXJlIGhvdyB0aGlzIG91dC1vZi1iYW5kIGluZm9ybWF0aW9uIGludGVyYWN0
cyB3aXRoIHJlY3Vyc2l2ZQ0KICByZXNvbHV0aW9uLiAgQSBMb1NUIGdhdGV3YXkgdGhhdCBwZXJm
b3JtcyByZWN1cnNpdmUgbG9va3VwcyBtaWdodCBub3QgYmUNCiAgYWJsZSBtYWtlIHRoZSByaWdo
dCBjaG9pY2Ugd2l0aG91dCBhbiBleHBsaWNpdCwgaW4tYmFuZCBpbmRpY2F0aW9uIG9mDQogIGlu
dGVudC4NCg0KICBBdHRlbXB0aW5nIHRvIG92ZXJsb2FkIHRoZSA8bG9jYXRpb24+IGVsZW1lbnQg
YXMgZGVzY3JpYmVkIGluIFNlY3Rpb24gNS4xDQogIGRvZXMgbm90IG1ha2UgZm9yIGNsZWFyIHBy
b3RvY29sIHNlbWFudGljcy4NCg0KICBNeSByZWFkaW5nIG9mIFJGQzUyMjIgbGVhZHMgbWUgdG8g
aW5mZXIgdGhhdCB0aGVyZSBpcyBhbiBpbXBsaWNpdA0KICA8bGU6bGltaXQ+IHBhcmFtZXRlciBp
biB0aGUgcHJvdG9jb2wgdGhhdCBpcyBzZXQgdG8gMS4gIFRoZXJlJ3MgYWx3YXlzDQogIHRoZSBw
b3NzaWJpbGl0eSB0aGF0IGEgbG9jYXRpb24gd2l0aCB1bmNlcnRhaW50eSBvdmVybGFwcyB0aGUg
c2VydmVkIGFyZWENCiAgb2YgbXVsdGlwbGUgUFNBUHMgLSBidXQgTG9TVCBhc3N1bWVzIHRoYXQg
dGhlcmUgaXMgb25seSBvbmUgcmlnaHQgYW5zd2VyLg0KDQogIEl0IHNlZW1zIGxpa2UgdGhlIHJp
Z2h0IHdheSB0byBhcHByb2FjaCB0aGUgcHJvcG9zZWQgZXh0ZW5zaW9ucyBpcyB0bw0KICBsaWZ0
IHRoZSBpbXBsaWVkIGxpbWl0IGJleW9uZCAxLiAgQWRkaW5nIHRoZSA8bGU6bGltaXQ+IGVsZW1l
bnQgc2VlbXMNCiAgbGlrZSB0aGUgcmlnaHQgdGhpbmcgdG8gZG8sIGJ1dCB0aGUgc2VtYW50aWNz
IHRoYXQgSSBhc3NvY2lhdGUgd2l0aA0KICA8bGU6cmVnaW9uPiBlbGVtZW50IGRvZXNuJ3Qgc2Vl
bSB0byBmaXQuDQoNCiAgSSdkIGVuY291cmFnZSB0aGUgYXV0aG9ycyB0byByZS1leGFtaW5lIHRo
ZSBiYXNpYyBtb2RlbCB0aGV5IGFyZSB1c2luZyB0bw0KICBjb25zdHJ1Y3QgdGhlaXIgcHJvcG9z
ZWQgc29sdXRpb24uDQoNCiAgU2VjdGlvbiA1LjMgc2VlbXMgdmVyeSBjb25mdXNlZCBmb3IgdGhl
c2UgcmVhc29ucy4gIEEgc2ltcGxlciBtb2RlbCB3b3VsZA0KICByZXF1aXJlIGxlc3MgZXhwbGFu
YXRpb24uDQoNCk9uIDxsZTpsaW1pdD4NCiAgU2VjdGlvbiA1LjQgc3RhdGVzOg0KDQogICBXaGVu
IHRoZSA8bGltaXQ+IGVsZW1lbnQgaXMgbm90IHByZXNlbnQgaW4gYSA8ZmluZFNlcnZpY2U+IHF1
ZXJ5IHRoZW4NCiAgIGFsbCBhdmFpbGFibGUgcG9pbnRzIG9mIGludGVyZXN0IGZvciB0aGUgcmVx
dWVzdGVkIHR5cGUgb2Ygc2VydmljZQ0KICAgU0hBTEwgYmUgcmV0dXJuZWQgYnkgdGhlIExvU1Qg
c2VydmVyLg0KDQogIFdoaWNoIHNlZW1zIGNvbnRyYXJ5IHRvIHdoYXQgaXMgaW1wbGljaXQgaW4g
UkZDNTIyMi4gIFNlZSBhYm92ZS4NCg0KT24gPGxlOnNlcnZpY2VMb2NhdGlvbj4NCiAgVGhlIGFk
bW9uaXRpb246DQoNCiAgIFsuLi5dIE9ubHkgZ2VvZGV0aWMgcHJvZmlsZXMgU0hPVUxEIGJlIHVz
ZWQgWy4uLl0NCg0KICAuLi4gYW5kIHN1YnNlcXVlbnQgdXNlIG9mIGFuIHVud3JhcHBlZCA8Y2E6
Y2l2aWNBZGRyZXNzPiBlbGVtZW50IGluIHRoZQ0KICA8bWFwcGluZz4gZWxlbWVudCBpcyBzdHJh
bmdlLiAgSG93IGlzIGEgY2l2aWMgYWRkcmVzcyBub3QgdGhlIGxvY2F0aW9uIG9mDQogIHRoZSBz
ZXJ2aWNlPyAgSWYgdGhlcmUgYXJlIG11bHRpcGxlIGZvcm1zIG9mIGxvY2F0aW9uLCBpdCB3b3Vs
ZCBiZSBiZXR0ZXINCiAgdG8gdXNlIHNpbWlsYXIgZ3VpZGFuY2UgdG8gd2hhdCBpcyBpbiBSRkM1
NDkxOg0KDQogICAgMS4gcmVjb21tZW5kIG11bHRpcGxlIDxsZTpzZXJ2aWNlTG9jYXRpb24+IGVs
ZW1lbnRzIHdoZW4gdGhlcmUgYXJlDQogICAgICAgbXVsdGlwbGUgZm9ybXMgYXZhaWxhYmxlDQoN
CiAgICAyLiByZWNvbW1lbmQgdGhhdCBhIGdlb2RldGljIGZvcm0gaXMgcHJvdmlkZWQgd2hlcmUg
cG9zc2libGUNCg0KICBUaGUgbG9jYXRpb24gcHJvZmlsZSBjYW4gYmUgdXNlZCB0byBpZGVudGlm
eSB3aGljaCBsb2NhdGlvbiB5b3Ugd2FudCB0bw0KICB1c2UgaWYgdGhlIGNvbnRlbnQgb2YgdGhl
IGVsZW1lbnQgaXMgbm90IHN1ZmZpY2llbnQuDQoNCiAgVGhlIHJlYXNvbiBnaXZlbiBmb3IgdGhl
c2UgcmVjb21tZW5kYXRpb25zOg0KDQogICAgWy4uLl0gYXMgdGhlIGNvbXB1dGF0aW9uIG9mIHRo
ZSBkaXN0YW5jZSwgcm91dGUgYW5kIG90aGVyIG1ldHJpY3MNCiAgIHdvdWxkIGF0IHNvbWUgcG9p
bnQgcmVxdWlyZSBnZW9jb2Rpbmcgb2YgdGhlIGNpdmljIGFkZHJlc3MgaW4NCiAgIGdlb2RldGlj
IGNvb3JkaW5hdGVzLiAgQmVjYXVzZSBvZiB0aGlzLCB0aGUgcG9zaXRpb24gc3BlY2lmaWVkIGlu
DQogICA8c2VydmljZUxvY2F0aW9uPiBTSE9VTEQgYmUgcmVwcmVzZW50ZWQgYnkgdXNpbmcgdGhl
IDxQb2ludD4gZWxlbWVudC4NCg0KICAuLi4gaXMgbm90IG5lY2Vzc2FyeSBmb3IgaW50ZXJvcGVy
YWJpbGl0eS4gIFRoaXMgc2VlbXMgbW9yZSBmb3IgdGhlDQogIGNvbnZlbmllbmNlIG9mIExvU1Qg
c2VydmVyIGltcGxlbWVudGF0aW9ucy4gIFdvdWxkbid0IHRoZXNlIHJlYXNvbnMgYmUNCiAgYmV0
dGVyIHN1aXRlZCB0byBhIExvU1Qgc2VydmVyIHByb3Zpc2lvbmluZyBndWlkZT8NCg0KICBBIGJl
dHRlciByZWFzb24gbWlnaHQgYmUgdGhhdCBhIHJlY2lwaWVudCBvZiB0aGUgbWFwcGluZyBpbmZv
cm1hdGlvbg0KICBtaWdodCBuZWVkIHRvIHVzZSB0aGlzIGluZm9ybWF0aW9uIHdpdGhvdXQgdGhl
IG5lY2Vzc2FyeSBjb250ZXh0IHRvDQogIHVuZGVyc3RhbmQgdGhlIGNpdmljIGFkZHJlc3MuICBI
b3dldmVyLCB0aGUgc2FtZSByZWFzb24gZG9lc24ndCBzdXBwb3J0DQogIHRoZSByZWNvbW1lbmRh
dGlvbiBmb3IgdXNpbmcgYSA8Z21sOlBvaW50Pi4NCg0KSXRlcmF0aXZlIFJlc3BvbnNlcw0KICBU
aGUgdXNlIG9mIGl0ZXJhdGl2ZSByZXNvbHV0aW9uIGluIExvU1QgaXMgYSB3ZWFrIHBvaW50IHRo
YXQgdGhlIGFiaWxpdHkNCiAgdG8gcHJvdmlkZSBtdWx0aXBsZSBtYXBwaW5ncyBkb2VzIG5vdCBo
ZWxwLiAgSW4gdGhlIGNhc2Ugd2hlcmUgYSBzZXJ2ZXINCiAgaXMgYWJsZSB0byBwcm92aWRlIG9u
bHkgc29tZSBhbnN3ZXJzLCB0aGVyZSBpcyBubyBmYWNpbGl0eSBmb3IgdGhlIHNlcnZlcg0KICB0
byBpbmRpY2F0ZSB3aGVyZSB0aGUgcmVtYWluZGVyIG9mIHRoZSBhbnN3ZXJzIGFyZSBmb3VuZCAo
dGhhdCBpcywgdGhlDQogIHJlZmVycmFsKS4NCg0KICBFdmVuIGlmIHlvdSBjYW4gYWRkcmVzcyB0
aGF0IGNvbmNlcm4sIHRoZXJlJ3MgYWxzbyB0aGUgY29uY2VybiB0aGF0IHRoZQ0KICByZWZlcnJl
ZCBMb1NUIHNlcnZlciBpcyBhYmxlIHRvIHByb3ZpZGUgYmV0dGVyIChjbG9zZXIpIGFuc3dlcnMg
dGhhbiB0aGUNCiAgb25lcyBwcm92aWRlZC4gIFRoZSBkcmFmdCBtaWdodCBvZmZlciBndWlkYW5j
ZSBvbiBob3cgdG8gcmVzb2x2ZSB0aGlzDQogIGlzc3VlLg0KDQpTZWN1cml0eQ0KICBUaGUgc2Vj
dXJpdHkgc2VjdGlvbiBjb3VsZCB1c2Ugc29tZSBleHBhbnNpb24uICBJdCdzIG5vdCBzdWZmaWNp
ZW50IHRvDQogIGp1c3QgcmVmZXIgdG8gUkZDNTIyMi4NCg0KICBUaGUgZGVuaWFsIG9mIHNlcnZp
Y2UgY29uY2VybnMgdGhhdCBTaGlkYSByYWlzZWQgaW4gaGlzIHJldmlldyBhcmUgd29ydGgNCiAg
ZGlzY3Vzc2luZy4gIEEgTG9TVCBzZXJ2ZXIgaXMgZGlzY292ZXJlZCB1c2luZyB0aGUgc2FtZSBt
ZWFucyB3aGV0aGVyIGl0DQogIGJlIGZvciBlbWVyZ2VuY3kgb3IgY29tbWVyY2lhbCB1c2VzLiAg
VGhlIHBvc3NpYmlsaXR5IHRoYXQgY29tbWVyY2lhbA0KICB1c2VzIGNvdWxkIGludGVyZmVyZSB3
aXRoIHB1YmxpYyBzYWZldHkgaXMgYSBzaWduaWZpY2FudCBjb25jZXJuLiAgQXMNCiAgU2hpZGEg
bm90ZXMsIHNjYWxpbmcgaXMgcHJvYmFibHkgdHJpdmlhbCB0byBhZGRyZXNzLCBidXQgdGhhdCdz
IG5vdCB0aGUNCiAgd2hvbGUgc3RvcnkuDQoNCiAgV2UndmUgc2VlbiBwcm9ibGVtcyB0aGF0IG92
ZXJ3aGVsbSBhIHN5c3RlbSwgZGVzcGl0ZSBjYWxjdWxhdGlvbnMNCiAgcHJlZGljdGluZyBhbXBs
ZSBjYXBhY2l0eSwgc2ltcGx5IGR1ZSB0byBoaWdoIGRlbWFuZCBmb3IgYSBwYXJ0aWN1bGFyDQog
IGFwcGxpY2F0aW9uIHRoYXQgaXMgcG9vcmx5IGNvbmZpZ3VyZWQuICBTcGVjaWZpYyBtZWNoYW5p
c21zIHRvIHByb3RlY3QNCiAgcHVibGljIHNhZmV0eSBxdWVyaWVzIG1pZ2h0IGJlIGRpZmZpY3Vs
dCB0byBkZXNpZ24sIGJ1dCB0aGUgZG9jdW1lbnQNCiAgc2hvdWxkIGF0IGEgbWluaW11bSBhY2tu
b3dsZWRnZSB0aGUgcHJvYmxlbS4NCg0KTml0czoNCiAgU2VjdGlvbiA1LjIgLSB0eXBvOiB3ZXRo
ZXINCg0KICBNb3N0IG9mIHRoZSBleGFtcGxlcyB1c2UgaHR0cDovL3d3dy50aGlzaXNub3Rkb25l
eWV0Lm5ldC9sb3N0TmUgc3RpbGwuDQoNCiAgVXNpbmcgYSBuYW1lc3BhY2UgcHJlZml4IG9mICJn
bWwiIHJhdGhlciB0aGFuICJwMiIgd291bGQgYmUgbW9yZSBoZWxwZnVsDQogIHRvIHRoZSByZWFk
ZXIuICBDb25zaXN0ZW50IHVzZSBvZiBuYW1lc3BhY2UgcHJlZml4ZXMgdGhyb3VnaG91dCB3b3Vs
ZA0KICBhbHNvIGhlbHAgZGlzYW1iaWd1YXRlIHRoZSB0aHJlZSBvciBzbyBuYW1lc3BhY2VzIHVz
ZWQuDQoNCi0tTWFydGluDQo=
