From sipping-bounces@ietf.org Sun Apr 01 11:31:25 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HY1zc-0000Q6-72; Sun, 01 Apr 2007 11:29:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HY1za-0000Lq-2d
	for sipping@ietf.org; Sun, 01 Apr 2007 11:29:18 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HY1zW-0003DQ-BS
	for sipping@ietf.org; Sun, 01 Apr 2007 11:29:18 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JFT0041WSBWGI@siemenscomms.co.uk> for sipping@ietf.org;
	Sun, 01 Apr 2007 16:28:44 +0100 (BST)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VC7R9D>; Sun, 01 Apr 2007 16:28:49 +0100
Content-return: allowed
Date: Sun, 01 Apr 2007 16:28:45 +0100
From: "Elwell, John" <john.elwell@siemens.com>
To: Sumanth Channabasappa <sumanth@cablelabs.com>, sipping@ietf.org
Message-id: <50B1CBA96870A34799A506B2313F26670B712023@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0
Cc: 
Subject: [Sipping] Comments on config-framework-11
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Sumanth,

As promised, I have reviewed sections 1-5 of draft-11. While this is heading
in the right direction, it took me two passes to understand it (even though
I had read earlier versions). So I think there is still considerable scope
for improving the readability, not least in the area of terminology. Also
some technical comments.

Specific comments:

1. "The devices are required to support all the
   three profile types, unless configured otherwise (at a minimum they
   need to support the device profile )"

Presumably this should say that devices are required to implement all three
profile types, but in a given deployment they might use only a subset, this
being determined by discovery or pre-configuration. Whether the device
profile should be a necessary part of that subset, I am not sure - see later
comment.

2. "The deployments  are required to
   support the device profile"
It is more important to say what has to be implemented in a PDS, rather than
what has to be deployed in a given situation.

3. "The life cycle is initiated when the device enrolls for profile data"
I have a real problem with this. This is supposed to be a "profile life
cycle". I think a profile exists before a device attempts to subscribe to it
and continues to exist even after that subscription expires or is cancelled.
Furthermore, multiple devices can be subscribed to the same profile at
different times or at the same time. Are you really talking about the life
cycle of a subscription instead?

4. "Profile Enrollment :  the process by which a device requests, and if
      successful, enrolls with a PDS capable of providing a profile"
This seems to correspond very precisely to the concept of subscription in
RFC 3265. On the other hand, the term "subscription" is used in some places
with apparently a different meaning, which I find confusing. Can't we use
"subscription" instead of "enrollment" for an RFC 3265 subscription and
avoid its use for other concepts?

5. "configuration management server"
This is not defined.

6. "The device is pre-configured to only request the device profile"
Why does the device have to be pre-configured? For example, the device
profile could indicate that no user profile is needed?

7. "The device performs Profile Enrollment for the device profile ;
        the device profile data is contained in the enrollment
        notification"
We should say something about how it discovers the PDS for the device
profile. I know procedures are rather complicated, but at least mention that
it can be by pre-configuration or discovery.

8. Section 4.2, figure.
This figure shows a SIP proxy, but the corresponding figure in 4.1 does not.
We should either be consistent or explain the reason for the difference.

9. "This also provides the local domain
        information to help with local-network profile enrollment"
Say more precisely how this helps, i.e., by enabling the device to determine
where to send the subscription request to.

10. "The device then requests profile enrollment for the device
        profile"
Again we should say something about how the device discovers the PDS for the
device profile.

11. "the device
   and the PDS MUST follow the Profile Life Cycle requirements stated in
   this section for all supported profile types."
We need to understand better what is required to be supported (implemented).
Can a single PDS support more than one profile type, or just one? If more
than one can be supported, is it mandatory to implement all (even though a
given deployment might not use them all)?

12. "
              |                 | NO; attempt
              |                 | Profile Request
              |                 | in specified  order"
Make it clear that this is specified later in this document (rather than at
implementation or deployment time).

13. Second figure in section 5. I don't find this figure intuitive. For
example, what happens after the boxes "Profile Change Operation" and
"Profile Content Retrieval"? What if both the initial notification and the
change notification require content indirection?

14. "The Profile Life Cycle is initiated when the device transmits an
   enrollment request for a specific profile"
See earlier comment on about life cycle. Also we need to say something about
how the device discovers where to send the request to.

15. "This framework defines three profile types and an order that
   MUST be followed by the device in requesting them (when it retrieves
   two or more of the defined profile types), as follows:

    o  local-network
   o  device
   o  user"
This order might apply to initial configuration, but not to change
notifications. For example, a device could receive notification of a change
of user profile without necessarily needing to go get the local-network and
device profiles again first.

16. "creating a profile enrollment subscription"
I think what is meant here is a "subscription request" rather than an
"enrollment subscription".

17. "Profile Notification Component (PNC), responsible for enrolling
      devices in Profile event subscriptions"
I find this wording odd. Presumably it should say something like
"responsible for acting as the notifier for profile event subscriptions".

18. "5.1.1.1.  SIP SUBSCRIBE for the Local-Network profile type

   Before attempting to create a SIP SUBSCRIBE"
This is the first mention of a SIP SUBSCRIBE request. It should probably say
something like "In order to subscribe to receive the local-network profile,
the device MUST send a SIP SUBSCRIBE request. Before it can do this , the
device MUST have...."

19. "Alice  may have a prior arrangement with the local
   network operator giving her special privileges.)"
Who is Alice in this context? We are talking about the local-network
profile, so the user should be irrelevant.

20. "the uniqueness of the "device-id"
   event header provides an important capability"
We should say what this important capability is.

21. "Having unique From
   fields allows the management of the local network to track devices
   present in the network and consequently also manage resources such as
   bandwidth and port allocation."
Should this be talking about the device-id in the Event header field
(relating to my comment above) rather than the From header field?

22. "Devices MUST follow the procedures specified below in the order
   presented, unless exceptions are made by device manufacturers  or
   Device Providers who may provide an option for the user to choose the
   order (to suit specific deployment models, for example)."
Frankly there are just too many options specified in the text that follows.
Can't we eliminate some?

23. "      The device MAY be pre-configured with information that can be
      utilized to identify the host and port of the Request URI.  The
      information can be provided - as examples - when the device is
      manufactured, by using Service Provider entities (flash card, SIM 
      card)"
Normally SIM cards and flash cards tend relate to users rather than devices.
I can move them between devices.

24. "      If pre-configuration is not an option, or not available, IP
      configuration"
What is "IP configuration" in this context? Is it specifically DHCP? Of
auto-discovery in general?

25. "This is based on the user's
   identity that is usually known in the network (for example,
   associated with a subscription)"
Here is an example where I think "subscription" might be used in a way that
is not consistent with the RFC 3265 meaning of the term.

26. "for example, users
   belonging to the same subscription"
And another example - the statement does not make sense in the context of an
RFC 3265 subscription.

27. "an example of an exception
   would be the re-use of devices across Service Providers"
This seems to be quite an important exception - the way it is written sounds
like it is a corner case, however.

28. "   The SIP infrastructure receiving such requests is expected to relay
   and process profile enrollment requests."
In the case of subscription to the user profile, the Request-URI is just the
AoR, so normal proxy behaviour will be to send it to any UAs registered as
contacts for that AoR. How do we ensure it goes only to the PDS?

29. "   Any changes to a Profile as a result of Profile Change Operation
MUST
   result in a Profile Notification to all enrolled devices  for that
   Profile, if any."
In the case of the device profile there can be only one device.

30. "   At a minimum, a device requires the device profile to be able to
   function effectively."
Why? I could argue that the local network profile should be the "must use"
one? First, it is easier to discover, assuming the device has discovered a
SIP proxy in the local network. Second, a device could be designed with
default settings for that particular device type, which would need to be
overridden only as a consequence of attaching to a different local-network
or supporting a particular user.

31. Throughout sections 1 to 5 there are numerous uses of the word "service"
or "services". This has always been a contentious issue as to exactly what
it means. So find a better term or explain exactly what is meant (e.g, SIP
registrar/proxy functions).

John



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 01 12:00:55 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HY2Tr-0007vM-Rm; Sun, 01 Apr 2007 12:00:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HY2Tq-0007v6-8N
	for sipping@ietf.org; Sun, 01 Apr 2007 12:00:34 -0400
Received: from smtp1.versatel.nl ([62.58.50.88])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HY2To-0000o5-RO
	for sipping@ietf.org; Sun, 01 Apr 2007 12:00:34 -0400
Received: (qmail 27748 invoked by uid 0); 1 Apr 2007 16:01:44 -0000
Received: from ip198-11-212-87.adsl2.versatel.nl (HELO BEMBUSTER)
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp1.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 1 Apr 2007 16:01:44 -0000
Message-ID: <006601c77476$c48434b0$0601a8c0@BEMBUSTER>
From: "Jeroen van Bemmel" <jbemmel@zonnet.nl>
To: "Dean Willis" <dean.willis@softarmor.com>,
	<Dale.Worley@comcast.net>
References: <989763567E51AB48BE015DF7BB960CAD029C8953@esealmw111><200703220239.l2M2d0Sj021023@dragon.ariadne.com><1174553260.3573.15.camel@dhcp-1642.ietf68.org><200703291850.l2TIogEJ028228@dragon.ariadne.com><D80311DB-EB22-492B-8965-37B3CA4F1ECD@softarmor.com><200703302231.l2UMVJc0019598@dragon.ariadne.com>
	<B2E5BE59-1061-43ED-AD63-AB129BB4B2DE@softarmor.com>
Subject: Re: [Sipping] Service Identification in SIP
Date: Sun, 1 Apr 2007 17:59:44 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dean,

There are providers that offer the Internet model. They are called "Internet 
Service Providers", or ISPs. If traditional telco's would adopt the internet 
model, they would not be considered telco's anymore. In many cases, your 
"old-school network operators" also act as ISP in one way or another. You 
can get a subscription from such an ISP, and implement the "in the UA" model 
on top of that.

If I understand the "in the UA" service model, the role of the operator 
would be to host only a SIP proxy service? In today's regulatory systems 
such a model would not work, because of requirements on legal intercept 
(amongst others). In order to fulfill such requirements, telco's have no 
choice but to deploy an infrastructure that provides the necessary control.

So perhaps it should be considered that it is not necessarily the operators 
that are blocking adoption of this "ideal" architecture

Regards,
Jeroen

Dean Willis wrote:
> On Mar 30, 2007, at 5:31 PM, Dale.Worley@comcast.net wrote:
>
>>
>> What I'm looking for is a service where application support must
>> necessarily be integral to the network, and cannot be provided by a
>> service that accesses the network "like any other UA".
>>
>
> There have been services defined to work this way ("in the network").
> However, I think that they could all be transformed without loss of
> function into "like any other UA" operation.
>
> However, the old-school network operators (carriers, whatever you
> want to call them) come from a background of doing things inside TDM
> circuit switches. They just don't get the INternet model. They don't
> WANT to get it. They don't want to recognize that their much-vaunted
> "in the network" services are not inherently "better" than "in the
> UA" services. The entire concept offends their world view and is as
> alien to their perspective as service-muddling "network elements" is
> to the Internet perspective. They were happy with broadband ISDN and
> BICC, they don't know why they switched to IP and SIP, and they have
> a hunch that if they can make the way IP works change to work like
> switched systems did then they'll magically be put back in control of
> all electronic communications, and that's where they want to be.
>
> This makes for very difficult negotiations.
>
> How many therapists does it take to change a light bulb?
>
> Only one, but the light bulb has to really WANT to change.
>
> Fortunately, unchanged light bulbs eventually burn out. 


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 01 12:14:51 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HY2hW-0002V9-T5; Sun, 01 Apr 2007 12:14:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HY2hV-0002V4-HX
	for sipping@ietf.org; Sun, 01 Apr 2007 12:14:41 -0400
Received: from rwcrmhc11.comcast.net ([204.127.192.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HY2hU-00046q-9m
	for sipping@ietf.org; Sun, 01 Apr 2007 12:14:41 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc11) with ESMTP
	id <20070401161439m11005i8ase>; Sun, 1 Apr 2007 16:14:39 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l31GEcLv017475
	for <sipping@ietf.org>; Sun, 1 Apr 2007 12:14:38 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l31GEbmi017471;
	Sun, 1 Apr 2007 12:14:37 -0400
Date: Sun, 1 Apr 2007 12:14:37 -0400
Message-Id: <200704011614.l31GEbmi017471@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <B2E5BE59-1061-43ED-AD63-AB129BB4B2DE@softarmor.com>
	(dean.willis@softarmor.com)
Subject: Re: [Sipping] Service Identification in SIP
References: <989763567E51AB48BE015DF7BB960CAD029C8953@esealmw111>
	<200703220239.l2M2d0Sj021023@dragon.ariadne.com>
	<1174553260.3573.15.camel@dhcp-1642.ietf68.org>
	<200703291850.l2TIogEJ028228@dragon.ariadne.com>
	<D80311DB-EB22-492B-8965-37B3CA4F1ECD@softarmor.com>
	<200703302231.l2UMVJc0019598@dragon.ariadne.com>
	<B2E5BE59-1061-43ED-AD63-AB129BB4B2DE@softarmor.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: Dean Willis <dean.willis@softarmor.com>

   There have been services defined to work this way ("in the network").  
   However, I think that they could all be transformed without loss of  
   function into "like any other UA" operation.

Yeah, that's the critical queston.

   they'll magically be put back in control of all electronic
   communications, and that's where they want to be.

It's certainly a more profitable situation.

   This makes for very difficult negotiations.

We don't need to negotiate, because there is nothing they have that we
want.

   Fortunately, unchanged light bulbs eventually burn out.

It's amazing how market competition drives IP adoption.

Dale

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 01 12:27:02 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HY2t7-00086j-0F; Sun, 01 Apr 2007 12:26:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HY2t5-00084N-AT
	for sipping@ietf.org; Sun, 01 Apr 2007 12:26:39 -0400
Received: from harjus.tutpro.com ([192.98.100.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HY2t3-0008CT-W2
	for sipping@ietf.org; Sun, 01 Apr 2007 12:26:39 -0400
Received: by harjus.tutpro.com (Postfix, from userid 1000)
	id C3BEFAC369; Sun,  1 Apr 2007 19:26:36 +0300 (EEST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17935.56636.697527.457792@harjus.tutpro.com>
Date: Sun, 1 Apr 2007 19:26:36 +0300
To: "Jeroen van Bemmel" <jbemmel@zonnet.nl>
Subject: Re: [Sipping] Service Identification in SIP
In-Reply-To: <006601c77476$c48434b0$0601a8c0@BEMBUSTER>
References: <989763567E51AB48BE015DF7BB960CAD029C8953@esealmw111>
	<200703220239.l2M2d0Sj021023@dragon.ariadne.com>
	<1174553260.3573.15.camel@dhcp-1642.ietf68.org>
	<200703291850.l2TIogEJ028228@dragon.ariadne.com>
	<D80311DB-EB22-492B-8965-37B3CA4F1ECD@softarmor.com>
	<200703302231.l2UMVJc0019598@dragon.ariadne.com>
	<B2E5BE59-1061-43ED-AD63-AB129BB4B2DE@softarmor.com>
	<006601c77476$c48434b0$0601a8c0@BEMBUSTER>
X-Mailer: VM 7.19 under Emacs 21.4.1
From: jh@tutpro.com (Juha Heinanen)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: sipping@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Jeroen van Bemmel writes:

 > If I understand the "in the UA" service model, the role of the operator 
 > would be to host only a SIP proxy service? In today's regulatory systems 
 > such a model would not work, because of requirements on legal intercept 
 > (amongst others). In order to fulfill such requirements, telco's have no 
 > choice but to deploy an infrastructure that provides the necessary
 > control.

so far there is no legal intercept requirement in eu at least regarding
internet telephony.  i don't understand how such a thing would work and
i think authorities know it.

-- juha

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 01 12:50:32 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HY3F1-0002a5-OZ; Sun, 01 Apr 2007 12:49:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HY3F1-0002Zz-4y
	for sipping@ietf.org; Sun, 01 Apr 2007 12:49:19 -0400
Received: from smtp3.versatel.nl ([62.58.50.90])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HY3Es-0008UH-5T
	for sipping@ietf.org; Sun, 01 Apr 2007 12:49:19 -0400
Received: (qmail 27826 invoked by uid 0); 1 Apr 2007 16:48:46 -0000
Received: from ip198-11-212-87.adsl2.versatel.nl (HELO BEMBUSTER)
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp3.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 1 Apr 2007 16:48:46 -0000
Message-ID: <008d01c7747d$8e3720a0$0601a8c0@BEMBUSTER>
From: "Jeroen van Bemmel" <jbemmel@zonnet.nl>
To: "Juha Heinanen" <jh@tutpro.com>
References: <989763567E51AB48BE015DF7BB960CAD029C8953@esealmw111><200703220239.l2M2d0Sj021023@dragon.ariadne.com><1174553260.3573.15.camel@dhcp-1642.ietf68.org><200703291850.l2TIogEJ028228@dragon.ariadne.com><D80311DB-EB22-492B-8965-37B3CA4F1ECD@softarmor.com><200703302231.l2UMVJc0019598@dragon.ariadne.com><B2E5BE59-1061-43ED-AD63-AB129BB4B2DE@softarmor.com><006601c77476$c48434b0$0601a8c0@BEMBUSTER>
	<17935.56636.697527.457792@harjus.tutpro.com>
Subject: Re: [Sipping] Service Identification in SIP
Date: Sun, 1 Apr 2007 18:48:20 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: sipping@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

At the very least there is discussion about it, and as such it forms a risk 
for deployment. See e.g. 
http://tweakers.net/nieuws/46916/Tweede-Kamer:-Voip-valt-onder-telecommunicatiewet.html 
(in Dutch, sorry), in translation it states that the Dutch government 
considers internet telephony to fall under the existing telecom laws. This 
implies that it must be interceptable.

Regards,
Jeroen

Juha Heinanen wrote:
> Jeroen van Bemmel writes:
>
>> If I understand the "in the UA" service model, the role of the
>> operator would be to host only a SIP proxy service? In today's
>> regulatory systems such a model would not work, because of
>> requirements on legal intercept (amongst others). In order to
>> fulfill such requirements, telco's have no choice but to deploy an
>> infrastructure that provides the necessary control.
>
> so far there is no legal intercept requirement in eu at least
> regarding internet telephony.  i don't understand how such a thing
> would work and i think authorities know it.
>
> -- juha 


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 01 13:04:51 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HY3Th-0007Wh-Gg; Sun, 01 Apr 2007 13:04:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HY3Tf-0007Tr-Rs; Sun, 01 Apr 2007 13:04:27 -0400
Received: from exprod6og53.obsmtp.com ([64.18.1.187])
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1HY3Tb-0001Xz-S8; Sun, 01 Apr 2007 13:04:27 -0400
Received: from source ([192.150.11.134]) by exprod6ob53.postini.com
	([64.18.5.12]) with SMTP; Sun, 01 Apr 2007 10:04:17 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l31H3kD1008108; Sun, 1 Apr 2007 10:03:50 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l31H4CI9010282; Sun, 1 Apr 2007 10:04:12 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 1 Apr 2007 10:04:11 -0700
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
Subject: RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Sun, 1 Apr 2007 09:59:22 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com>
In-Reply-To: <460D9D9C.1040304@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Thread-Index: AcdzI3OuuvqnstaoRUubQmppvBh64gBWJEqw
References: <24CCCC428EFEA2469BF046DB3C7A8D225274F4@namail5.corp.adobe.com>	
	<072C5B76F7CEAB488172C6F64B30B5E302C88E1B@xmb-rtp-20b.amer.cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADEC5@namail5.corp.adobe.com>	
	<4603929D.4070604@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADEC8@namail5.corp.adobe.com>	
	<EC0E1E0E-2E83-4674-BAC0-78CB94F0BD43@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADECA@namail5.corp.adobe.com>	
	<4FF5FA52-1B38-4964-87AE-72300CE89A1F@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADED9@namail5.corp.adobe.com>	
	<460D4825.2090800@cisco.com>
	<7b683f3f0703301556j95f2c10sf12d666994dedf6f@mail.gmail.com>
	<460D9D9C.1040304@cisco.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, "Eunsoo Shim" <eunsooshim@gmail.com>
X-OriginalArrivalTime: 01 Apr 2007 17:04:11.0191 (UTC)
	FILETIME=[C4A11C70:01C7747F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	David R Oran <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org,
	zhuxian <zhuxian@huawei.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Paul,

> I more or less agree with the final conclusion below.

This is good starting point to discuss some usage scenarios.

Putting on my former hat as an employee for a carrier, I cannot overlook
the following:

P2P SIP implemented correctly in the residential access box or cable
set-top box indeed is a good or better replacement for the entire VoIP
network infrastructure (cost, operations, new services, etc).=20
Integrated access devices for the enterprise can probably play a similar
role, not to mention existing P2P PBX products (please refer to all the
advantages of P2P that need not repeated here).

What do people think of these three usage scenarios for P2P SIP:
- SIP peer in the DSL access device,
- SIP peer in the cable access device,
- SIP peer in enterprise network integrated access device (IAD).

Note that these examples imply very low churn for the peers and add the
data retention resilience of P2P (geographic diversity is native and
mobile, etc.). Incidentally, NAT traversal may also not be a problem, or
at least an easier problem.

What do you all think?

I have taken the liberty to copy the P2P SIP list, since the low churn
scenarios are of interest for the DHT selection. Or just pick the same
DHT for all scenarios anyway? I don't think so.

Thanks, Henry


-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
Sent: Friday, March 30, 2007 6:31 PM
To: Eunsoo Shim
Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
p2prg@ietf.org; sipping@ietf.org; zhuxian
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario

I more or less agree with the final conclusion below.

My main point here is that P2P and C/S need not be enemies. Nor is a=20
total C/S system necessarily evil. What is most evil is *bundling* of=20
services that prevents freedom of choice.

I think I would be quite happy with a SP that provides a registrar/proxy

and allows me to provide all other features as I see fit - by taking=20
them ala carte from the SP, or subscribing to them from one or more=20
other SPs, or by providing them myself via appliances I own. If that=20
registrar/proxy was replaced by a P2P sip community, the differences, if

any, would hopefully be more a function of the implementation and the=20
business models of those involved than the architecture.

(I gather the general assumption is that a P2P setup will be *free*. But

I have a hard time believing that. If most of the usage is by mobile=20
devices that can't be peers, then somebody will have to pay for enough=20
peers to support them. If it isn't free, then how is it better than a=20
well engineered C/S system?)

So I think the key thing here is that some features will require getting

some help from another node. There ought to be the option to pick a=20
different source for each helper you require, and an ability for it all=20
to play together.

	Paul

Eunsoo Shim wrote:
> Please see my inline comment.
>=20
> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com=20
> <mailto:pkyzivat@cisco.com>> wrote:
>=20
>=20
>=20
>     Henry Sinnreich wrote:
>      > David Oran wrote (with regard to voice mail):
>      >
>      >> I'm not saying this can't be made to work, only that it isn't
>      > immediately >obvious that it has advantages over a classic
>     application
>      > server >approach.
>      >
>      > The answer for VM is "it depends":
>      >
>=20
>=20
> I agree. It really depends. Certainly there are tradeoffs.
>=20
>      > There are several commercial P2P IP PBX solutions without any
>     server for
>      > VM or anything else. No doubt the IT organization appreciates
just
>      > having to plug in the IP phones and GWY to the PSTN without any
>      > configuration ever for VM or any other PBX feature.
>=20
>     I don't understand. Are you saying they don't have VM, or that
they
>     don't have a *server* for VM?
>=20
>=20
> I guess they don't have a  *server* for  VM.
>=20
>      > For public P2P SIP networks there are two more scenarios where
VM can
>      > reside (and without ever spending one cent on VM servers + IT
>     systems):
>      >
>      > - In Cable and DSL service provider networks: The residential
>     router can
>      > act as a voice recorder
>=20
>     That is simply an example of the user having an appliance of his
own
>     that provides VM service.
>=20
>      > and P2P can cover the not too frequent cases,
>      > where the router is not in operation, so the data is backed up
in
>     other
>      > peer residential gateways (encrypted).
>=20
>     I guess I just need to have more info about how this would work
before I
>     will be convinced it is feasible and trustworthy.
>=20
>=20
> Well, 'trustworthy' could be  considered in many angles.
> If it is about privacy of the message, a public key based encryption=20
> would provide acceptable privacy.
> If it is about reliability of the message delivery, well, a P2P based=20
> asynchronous message delivery (like VM) is most likely less reliable=20
> than a well managed server based system.
> However, my experience with Skype's asynchronous message delivery was=20
> not bad. Actually I don't see any significant difference between it
and=20
> my cellular service provider's VM service. :-)
> Reliability is always a challenge for P2P, for sure. But, I believe it

> is feasible to build a P2P system for VM acceptable for many
scenarios.
>=20
>      > - In mobile networks: The VM can reside in quite stable peers
>     inside the
>      > wireless base station network. The peers in the base station
network
>      > need no configuration, etc.
>=20
>     I don't understand. I guess that could be true if the peers are
willing
>     to store an arbitrary amount of VM indefinitely for anybody. Is
that
>     believable?
>=20
>=20
> It depends.
> In a very nice environment where all the peers are willing to
cooperate=20
> at their best, the peers will store as much as they can. In a tough=20
> environment, the situation will be different.
>=20
>     This seems to translate to a model where it is assumed that those
nodes
>     that are on most of the time will be willing to provide VM storage
for
>     those nodes that aren't on most of the time.
>=20
>=20
> This is again related to reliability of P2P systems or topics like
free=20
> riders and reputation.
> A P2P system is a community or society. To be simple, if many of the=20
> members are bad, the community won't work well. If the majority of the

> members are good, the community will work well or reasonably.
>=20
>      > Add to this the conferencing capability coming from p2p
application
>      > layer multicast, the SIP e2e control capabilities (for such as
>      > auto-attendant, agent workstation, etc.) and one has to wonder
why IT
>      > networks, public VoIP networks and end users should support the
huge
>      > cost of hand engineering, testing, monitoring, maintaining
server
>     based
>      > VoIP networks. P2P self configuration is nothing less that
automation
>      > applied to VoIP, plus the shifting of computing to the
endpoints,
>     where
>      > there is an abundance of unused CPU, storage, bandwidth and
>     electricity.
>      >
>      > Eric Burger also notes IM changes completely the usage for VM
and may
>      > make unnecessary to place calls on VM in the first place.
>=20
>     I find this more promising.
>=20
>          =20
>=20
>=20
> In overall, are we discussing if P2P systems based VM can work? I
think=20
> it can work.  Just it depends on many things.
> If it is not super-reliable, should we disregard it? I would say no.
>=20
> On the other hand, do we have to abandon client server based VM and=20
> switch to P2P system based VM? It is upto each of us.
> Client server based VM systems are already there.
> So why don't we work on P2P based VM now?
> =20
> Thanks.
>=20
> Eunsoo

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 01 14:20:34 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HY4dx-0003WG-Hp; Sun, 01 Apr 2007 14:19:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HY4dw-0003W9-29
	for sipping@ietf.org; Sun, 01 Apr 2007 14:19:08 -0400
Received: from serrano.cc.columbia.edu ([128.59.29.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HY4du-0005KT-Qy
	for sipping@ietf.org; Sun, 01 Apr 2007 14:19:08 -0400
Received: from [192.168.0.41] (pool-70-21-193-163.nwrk.east.verizon.net
	[70.21.193.163]) (user=hgs10 mech=PLAIN bits=0)
	by serrano.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id l31IIpqb005134
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sun, 1 Apr 2007 14:18:56 -0400 (EDT)
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B712023@ntht201e.siemenscomms.co.uk>
References: <50B1CBA96870A34799A506B2313F26670B712023@ntht201e.siemenscomms.co.uk>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <CADF94D1-A6B5-43E4-B097-3CF9F3AA65E2@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Comments on config-framework-11
Date: Sun, 1 Apr 2007 14:18:50 -0400
To: "Elwell, John" <john.elwell@siemens.com>,
	Sumanth Channabasappa <sumanth@cablelabs.com>
X-Mailer: Apple Mail (2.752.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.6
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I strongly share the concern that we don't arrive at a situation  
where we need either pre-configuration or devices that are "class A",  
"class B" and "class C". All devices, in all situations, should try a  
small number of configuration options, without human intervention. We  
really don't want manual meta-configuration and the draft needs to  
make this patently clear. Judging from bad experience, software  
writers will make things configurable that shouldn't be, unless told  
otherwise.

If, for efficiency reasons, you want to avoid that a device tries the  
same non-existing service at every reboot, one might imagine some  
kind of negative caching mechanism that stores the non-existence of a  
certain method. I suspect this won't be necessary since DNS already  
supports negative caching and DHCP-induced options are observable as  
to whether they exist or not, but the design team needs to consider  
this issue, as not doing so will lead exactly to the "provide option  
to turn off configuration method X" we don't want. Naturally, this  
also argues for a minimalist approach to configuration. The more  
options, the more temptation there is to "profile".

Henning

On Apr 1, 2007, at 11:28 AM, Elwell, John wrote:

> Sumanth,
>
> As promised, I have reviewed sections 1-5 of draft-11. While this  
> is heading
> in the right direction, it took me two passes to understand it  
> (even though
> I had read earlier versions). So I think there is still  
> considerable scope
> for improving the readability, not least in the area of  
> terminology. Also
> some technical comments.
>
> Specific comments:
>
> 1. "The devices are required to support all the
>    three profile types, unless configured otherwise (at a minimum they
>    need to support the device profile )"
>
> Presumably this should say that devices are required to implement  
> all three
> profile types, but in a given deployment they might use only a  
> subset, this
> being determined by discovery or pre-configuration. Whether the device
> profile should be a necessary part of that subset, I am not sure -  
> see later
> comment.
>


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 01 14:49:18 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HY56N-00077f-0N; Sun, 01 Apr 2007 14:48:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HY56I-00075B-OT
	for sipping@ietf.org; Sun, 01 Apr 2007 14:48:26 -0400
Received: from smtp3.versatel.nl ([62.58.50.90])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HY569-0001RI-4n
	for sipping@ietf.org; Sun, 01 Apr 2007 14:48:26 -0400
Received: (qmail 14759 invoked by uid 0); 1 Apr 2007 18:47:54 -0000
Received: from ip198-11-212-87.adsl2.versatel.nl (HELO BEMBUSTER)
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp3.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 1 Apr 2007 18:47:54 -0000
Message-ID: <00b201c7748e$33067df0$0601a8c0@BEMBUSTER>
From: "Jeroen van Bemmel" <jbemmel@zonnet.nl>
To: "Henry Sinnreich" <hsinnrei@adobe.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>, "Eunsoo Shim" <eunsooshim@gmail.com>
References: <24CCCC428EFEA2469BF046DB3C7A8D225274F4@namail5.corp.adobe.com>	<072C5B76F7CEAB488172C6F64B30B5E302C88E1B@xmb-rtp-20b.amer.cisco.com>	<24CCCC428EFEA2469BF046DB3C7A8D223ADEC5@namail5.corp.adobe.com>	<4603929D.4070604@cisco.com>	<24CCCC428EFEA2469BF046DB3C7A8D223ADEC8@namail5.corp.adobe.com>	<EC0E1E0E-2E83-4674-BAC0-78CB94F0BD43@cisco.com>	<24CCCC428EFEA2469BF046DB3C7A8D223ADECA@namail5.corp.adobe.com>	<4FF5FA52-1B38-4964-87AE-72300CE89A1F@cisco.com>	<24CCCC428EFEA2469BF046DB3C7A8D223ADED9@namail5.corp.adobe.com>	<460D4825.2090800@cisco.com><7b683f3f0703301556j95f2c10sf12d666994dedf6f@mail.gmail.com><460D9D9C.1040304@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com>
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Sun, 1 Apr 2007 20:47:28 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a4a24b484706be629f915bfb1a3e4771
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	David R Oran <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org,
	zhuxian <zhuxian@huawei.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Henry,

Aren't you confusing "usage scenarios" with "deployment scenarios" here? Why 
restrict P2P SIP to only certain types of devices? And if you insist on 
that, why not mobile devices?

Regards,
Jeroen

Henry Sinnreich wrote:
> Paul,
>
>> I more or less agree with the final conclusion below.
>
> This is good starting point to discuss some usage scenarios.
>
> Putting on my former hat as an employee for a carrier, I cannot
> overlook the following:
>
> P2P SIP implemented correctly in the residential access box or cable
> set-top box indeed is a good or better replacement for the entire VoIP
> network infrastructure (cost, operations, new services, etc).
> Integrated access devices for the enterprise can probably play a
> similar role, not to mention existing P2P PBX products (please refer
> to all the advantages of P2P that need not repeated here).
>
> What do people think of these three usage scenarios for P2P SIP:
> - SIP peer in the DSL access device,
> - SIP peer in the cable access device,
> - SIP peer in enterprise network integrated access device (IAD).
>
> Note that these examples imply very low churn for the peers and add
> the data retention resilience of P2P (geographic diversity is native
> and mobile, etc.). Incidentally, NAT traversal may also not be a
> problem, or at least an easier problem.
>
> What do you all think?
>
> I have taken the liberty to copy the P2P SIP list, since the low churn
> scenarios are of interest for the DHT selection. Or just pick the same
> DHT for all scenarios anyway? I don't think so.
>
> Thanks, Henry
>
>
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Friday, March 30, 2007 6:31 PM
> To: Eunsoo Shim
> Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
> p2prg@ietf.org; sipping@ietf.org; zhuxian
> Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
>
> I more or less agree with the final conclusion below.
>
> My main point here is that P2P and C/S need not be enemies. Nor is a
> total C/S system necessarily evil. What is most evil is *bundling* of
> services that prevents freedom of choice.
>
> I think I would be quite happy with a SP that provides a
> registrar/proxy
>
> and allows me to provide all other features as I see fit - by taking
> them ala carte from the SP, or subscribing to them from one or more
> other SPs, or by providing them myself via appliances I own. If that
> registrar/proxy was replaced by a P2P sip community, the differences,
> if
>
> any, would hopefully be more a function of the implementation and the
> business models of those involved than the architecture.
>
> (I gather the general assumption is that a P2P setup will be *free*.
> But
>
> I have a hard time believing that. If most of the usage is by mobile
> devices that can't be peers, then somebody will have to pay for enough
> peers to support them. If it isn't free, then how is it better than a
> well engineered C/S system?)
>
> So I think the key thing here is that some features will require
> getting
>
> some help from another node. There ought to be the option to pick a
> different source for each helper you require, and an ability for it
> all to play together.
>
> Paul
>
> Eunsoo Shim wrote:
>> Please see my inline comment.
>>
>> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com
>> <mailto:pkyzivat@cisco.com>> wrote:
>>
>>
>>
>>     Henry Sinnreich wrote:
>>      > David Oran wrote (with regard to voice mail):
>>      >
>>      >> I'm not saying this can't be made to work, only that it isn't
>>      > immediately >obvious that it has advantages over a classic
>>     application
>>      > server >approach.
>>      >
>>      > The answer for VM is "it depends":
>>      >
>>
>>
>> I agree. It really depends. Certainly there are tradeoffs.
>>
>>      > There are several commercial P2P IP PBX solutions without any
>>     server for
>>      > VM or anything else. No doubt the IT organization appreciates
>>      just > having to plug in the IP phones and GWY to the PSTN
>>      without any > configuration ever for VM or any other PBX
>> feature.
>>
>>     I don't understand. Are you saying they don't have VM, or that
>>     they don't have a *server* for VM?
>>
>>
>> I guess they don't have a  *server* for  VM.
>>
>>      > For public P2P SIP networks there are two more scenarios
>>      where VM can > reside (and without ever spending one cent on VM
>>     servers + IT systems):
>>      >
>>      > - In Cable and DSL service provider networks: The residential
>>     router can
>>      > act as a voice recorder
>>
>>     That is simply an example of the user having an appliance of his
>>     own that provides VM service.
>>
>>      > and P2P can cover the not too frequent cases,
>>      > where the router is not in operation, so the data is backed
>>     up in other
>>      > peer residential gateways (encrypted).
>>
>>     I guess I just need to have more info about how this would work
>>     before I will be convinced it is feasible and trustworthy.
>>
>>
>> Well, 'trustworthy' could be  considered in many angles.
>> If it is about privacy of the message, a public key based encryption
>> would provide acceptable privacy.
>> If it is about reliability of the message delivery, well, a P2P based
>> asynchronous message delivery (like VM) is most likely less reliable
>> than a well managed server based system.
>> However, my experience with Skype's asynchronous message delivery was
>> not bad. Actually I don't see any significant difference between it
>> and my cellular service provider's VM service. :-)
>> Reliability is always a challenge for P2P, for sure. But, I believe
>> it
>
>> is feasible to build a P2P system for VM acceptable for many
>> scenarios.
>>
>>      > - In mobile networks: The VM can reside in quite stable peers
>>     inside the
>>      > wireless base station network. The peers in the base station
>>      network > need no configuration, etc.
>>
>>     I don't understand. I guess that could be true if the peers are
>>     willing to store an arbitrary amount of VM indefinitely for
>>     anybody. Is that believable?
>>
>>
>> It depends.
>> In a very nice environment where all the peers are willing to
>> cooperate at their best, the peers will store as much as they can.
>> In a tough environment, the situation will be different.
>>
>>     This seems to translate to a model where it is assumed that
>>     those nodes that are on most of the time will be willing to
>>     provide VM storage for those nodes that aren't on most of the
>> time.
>>
>>
>> This is again related to reliability of P2P systems or topics like
>> free riders and reputation.
>> A P2P system is a community or society. To be simple, if many of the
>> members are bad, the community won't work well. If the majority of
>> the
>
>> members are good, the community will work well or reasonably.
>>
>>      > Add to this the conferencing capability coming from p2p
>>      application > layer multicast, the SIP e2e control capabilities
>>      (for such as > auto-attendant, agent workstation, etc.) and one
>>      has to wonder why IT > networks, public VoIP networks and end
>>      users should support the huge > cost of hand engineering,
>>     testing, monitoring, maintaining server based
>>      > VoIP networks. P2P self configuration is nothing less that
>>      automation > applied to VoIP, plus the shifting of computing to
>>     the endpoints, where
>>      > there is an abundance of unused CPU, storage, bandwidth and
>>     electricity.
>>      >
>>      > Eric Burger also notes IM changes completely the usage for VM
>>      and may > make unnecessary to place calls on VM in the first
>> place.
>>
>>     I find this more promising.
>>
>>
>>
>>
>> In overall, are we discussing if P2P systems based VM can work? I
>> think it can work.  Just it depends on many things.
>> If it is not super-reliable, should we disregard it? I would say no.
>>
>> On the other hand, do we have to abandon client server based VM and
>> switch to P2P system based VM? It is upto each of us.
>> Client server based VM systems are already there.
>> So why don't we work on P2P based VM now?
>>
>> Thanks.
>>
>> Eunsoo
>
> _______________________________________________
> Sipping mailing list  https://www1.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 


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 01 23:50:51 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYDYC-0000PC-3P; Sun, 01 Apr 2007 23:49:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYDYA-0000P4-Uc
	for sipping@ietf.org; Sun, 01 Apr 2007 23:49:46 -0400
Received: from rwcrmhc13.comcast.net ([216.148.227.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYDY9-0003JU-Mw
	for sipping@ietf.org; Sun, 01 Apr 2007 23:49:46 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc13) with ESMTP
	id <20070402034944m130039ulue>; Mon, 2 Apr 2007 03:49:44 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l323nhLv003094
	for <sipping@ietf.org>; Sun, 1 Apr 2007 23:49:43 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l323nhCu003090;
	Sun, 1 Apr 2007 23:49:43 -0400
Date: Sun, 1 Apr 2007 23:49:43 -0400
Message-Id: <200704020349.l323nhCu003090@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <006601c77476$c48434b0$0601a8c0@BEMBUSTER> (jbemmel@zonnet.nl)
Subject: Re: [Sipping] Service Identification in SIP
References: <989763567E51AB48BE015DF7BB960CAD029C8953@esealmw111><200703220239.l2M2d0Sj021023@dragon.ariadne.com><1174553260.3573.15.camel@dhcp-1642.ietf68.org><200703291850.l2TIogEJ028228@dragon.ariadne.com><D80311DB-EB22-492B-8965-37B3CA4F1ECD@softarmor.com><200703302231.l2UMVJc0019598@dragon.ariadne.com>
	<B2E5BE59-1061-43ED-AD63-AB129BB4B2DE@softarmor.com>
	<006601c77476$c48434b0$0601a8c0@BEMBUSTER>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Jeroen van Bemmel" <jbemmel@zonnet.nl>

   If I understand the "in the UA" service model, the role of the operator 
   would be to host only a SIP proxy service? In today's regulatory systems 
   such a model would not work, because of requirements on legal intercept 
   (amongst others). In order to fulfill such requirements, telco's have no 
   choice but to deploy an infrastructure that provides the necessary control.

My impression is that in the US, the government agencies just vacuum
up all the packets going to your UA.

Dale

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 02 03:11:11 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYGgF-00047R-4h; Mon, 02 Apr 2007 03:10:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYGgD-000437-BL
	for sipping@ietf.org; Mon, 02 Apr 2007 03:10:17 -0400
Received: from sonussf1.sonusnet.com ([208.45.178.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYGgB-0002Oy-Lr
	for sipping@ietf.org; Mon, 02 Apr 2007 03:10:17 -0400
Received: from sonusmail06.sonusnet.com (sonusmail06.sonusnet.com
	[10.128.32.156])
	by sonussf1.sonusnet.com (8.13.7/8.13.7) with ESMTP id l3279vFh001986; 
	Mon, 2 Apr 2007 03:09:57 -0400
Received: from SONUSINMAIL01.sonusnet.com ([10.128.254.7]) by
	sonusmail06.sonusnet.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Apr 2007 03:09:57 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 2 Apr 2007 12:39:46 +0530
Message-ID: <70798CF421F00F4DA018059E5B7EEB8C0109AC2E@sonusinmail01.sonusnet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-sipping-ipv6-torture-tests-01.txt
Thread-Index: Acd09eU8w6xg7dpxR6eDYnvHMdON/Q==
From: "B, Nataraju" <bnataraju@sonusnet.com>
To: <vkg@alcatel-lucent.com>, <cboulton@ubiquitysoftware.com>,
	<RjS@estacado.net>
X-OriginalArrivalTime: 02 Apr 2007 07:09:57.0041 (UTC)
	FILETIME=[EB835210:01C774F5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 231d7929942febf3be8fd5be2903302f
Cc: sipping@ietf.org, Mary Barnes <mary.barnes@nortel.com>
Subject: [Sipping] Comments on draft-ietf-sipping-ipv6-torture-tests-01.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0470085288=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0470085288==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C774F5.E5758E45"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C774F5.E5758E45
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi All,=20

Here are few comments on the draft ipv6-torture-tests-01.txt.

1. Lets not allow IPV6 addresses with out [ & ], this is a deviation
from RFC 3261 also.
This would definitely lead to interoperability issues later.

		Snippet from rfc.3261

		IPv6reference  =3D  "[" IPv6address "]"
		Here "[" "]" means mandatory to have for this component

		Ref:
		IPv4address    =3D  1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "."
1*3DIGIT
		for instance we can't have IP address without . For an
IPv4 addresses

2. Replace all instances of umabiguous with unambiguous
Search for all the instances in the draft.

3. via-received not including delimiters [ & ] would make
implementations complex or why don't we make sure all IPv6 addresses
always accompany with delimiters [ & ]. This loop hole will definitely
lead to interoperability issues some time later....
	sec 4.5 of the draft ipv6-torture-tests-01.

Even though some implementations accept IPv6 addresses without [ ], that
is a deviation from standards, but that should not be the criteria to
allow IPv6 without [ ].

4.=20
Sec 4.5 param-2 of draft ipv6-torture-tests-01 is not valid with respect
to 3261
	hence let us remove this test case

   The OPTIONS request below contains an IPv6 address in the Via
   received parameter without the adorning "[" and "]".  This request is
   valid according to the grammar in RFC3261.

The above statement is a deviation from what is mentioned in 3261.

   Message Details: param-2

     OPTIONS sip:[2001:db8::10] SIP/2.0
     To: sip:user@example.com
     From: sip:user@example.com;tag=3D81x2
     <allOneLine>
     Via: SIP/2.0/UDP [2001:db8::9:1];received=3D2001:db8::9:255;
     branch=3Dz9hG4bKas3
     </allOneLine>
     Call-ID: SSG95523997077@hlau_4100
     Max-Forwards: 70
     Contact: "Caller" <sip:caller@[2001:db8::1]>
     CSeq: 921 OPTIONS
     Content-Length: 0


5.=20
Ref: 4.6.  SIP request with IPv6 addresses in SDP body

Even here also shall we mandate addresses are with [ & ]

This IPv6 address is definitely not inline with what is been specified
in 3261.=20

I understand we would not receive IP:PORT in SDP, we can assume what is
been mentioned here is valid to accept, but this is a deviation from
RFC.3261. if we agree that we are deviating from 3261. Shall we mention
the same as a note in the draft?=20

Thanks,
Nataraju A B
Technical Lead
bnataraju@sonusnet.com
t +91 80 4190 2681
f +91 80 4190 2610
Unit 2, 8th Floor, Inventor Block
ITPL, Whitefield Road
Bangalore- 560066, India
www.sonusnet.com <http://www.sonusnet.com/>    =20


=09
Deliver the Future First with Sonus Networks.


------_=_NextPart_001_01C774F5.E5758E45
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6603.0">
<TITLE>Comments on draft-ietf-sipping-ipv6-torture-tests-01.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">Hi All, </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">Here are few comments on the =
draft</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">ipv6-torture-tests-01</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">.txt</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">1. Lets not allow IPV6 address</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">es</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New"> with out [ &amp; ], this is a deviation =
from RFC 3261 also</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">This</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New"> =
would</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">definitely</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New"> =
lead to interop</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">erability</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New"> =
issues</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">later.</FONT></SPAN></P>
<UL><UL>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">Snippet from rfc.3261</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">IPv6reference&nbsp; =3D&nbsp; &quot;[&quot; =
IPv6address &quot;]&quot;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">Here &quot;[&quot; &quot;]&quot; means mandatory to =
have for this component</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">Ref:</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">IPv4address&nbsp;&nbsp;&nbsp; =3D&nbsp; 1*3DIGIT =
&quot;.&quot; 1*3DIGIT &quot;.&quot; 1*3DIGIT &quot;.&quot; =
1*3DIGIT</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">for instance we can't have IP address =
without</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Courier =
New">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">For</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New"> an =
IPv4 address</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">es</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>
</UL></UL>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">2.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">Replace</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New"> =
all instances of umabiguous with unambiguous</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">Search for all</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New"> instances in</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New"></FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">draft.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">3. via-received not including delimiters [ &amp; ] =
would make implementations complex or why</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">don&#8217;t</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New"> we make sure all IPv6 addresses always =
accompany with delimiters [ &amp; ]</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">. T</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">his loop hole will</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">definitely</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New"> lead to interop</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">erability</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New"> issues some time =
later....</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New">sec 4.5 =
of</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New">the =
draft</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">ipv6-torture-tests-01</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">Even</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New"> =
though some implementations accept</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">IPv6 addresses</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">without [ ], that is a deviation from =
standards, but that should not be the criteria to allow IPv6 without [ =
]</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New">.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">4.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> </SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">Sec</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">4.5 param-2</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New">of =
draft ipv6-torture-tests-01</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">is not valid with respect to =
3261</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New">hence let us remove this =
test case</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp; The OPTIONS request below contains an =
IPv6 address in the Via</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp; received parameter without the =
adorning &quot;[&quot; and &quot;]&quot;.&nbsp; This request =
is</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp; valid according to the grammar in =
RFC3261.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">The above statement is a deviation from what is =
mentioned in 3261.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp; Message Details: =
param-2</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; OPTIONS sip:[2001:db8::10] =
SIP/2.0</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; To: =
sip:user@example.com</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; From: =
sip:user@example.com;tag=3D81x2</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;allOneLine&gt;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; Via: SIP/2.0/UDP =
[2001:db8::9:1];received=3D</FONT></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><SPAN LANG=3D"en-us"><B><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">2001:db8::9:255</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; =
branch=3Dz9hG4bKas3</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;/allOneLine&gt;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; Call-ID: =
SSG95523997077@hlau_4100</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; Max-Forwards: =
70</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; Contact: =
&quot;Caller&quot; &lt;sip:caller@[2001:db8::1]&gt;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 921 =
OPTIONS</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp; Content-Length: =
0</FONT></SPAN></P>
<BR>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">5. </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">Ref:</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">4.6.&nbsp; SIP request with IPv6 addresses in SDP =
body</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">Even</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New"> =
here also shall we mandate addresses are with [ &amp; =
]</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">This</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New"> =
IPv6 address is</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">definitely</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New"> =
not inline with what is been specified in 3261</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">. </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">I understand we would not receive =
IP</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New">:PORT</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New"> in SDP, we can assume what is been =
mentioned here is valid to accept, but this</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">is a</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">deviation from RFC.3261</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">. if we agree that we are deviating from =
3261.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">Shall</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New"> we =
mention</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">the</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New">same as a note =
in</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New">the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New"> draft? </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN><A NAME=3D""><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF">Thanks,</FONT></SPAN></A><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DRIGHT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">Nataraju A B</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><BR>
</SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Technical =
Lead</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><BR>
</SPAN><SPAN LANG=3D"en-us"></SPAN><A =
HREF=3D"mailto:bnataraju@sonusnet.com"><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><U></U></SPAN><U><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D1 =
FACE=3D"Arial">bnataraju@sonusnet.com</FONT></SPAN></U><SPAN =
LANG=3D"en-us"></SPAN></A><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DRIGHT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D1 =
FACE=3D"Arial">t +91 80 4190 2681<BR>
f +91 80 4190 2610</FONT></SPAN></P>

<P ALIGN=3DRIGHT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D1 =
FACE=3D"Arial">Unit 2, 8th Floor, Inventor Block<BR>
ITPL, Whitefield Road<BR>
Bangalore- 560066, India<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><A =
HREF=3D"http://www.sonusnet.com/"><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" =
SIZE=3D1 FACE=3D"Arial">www.sonusnet.com</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></A><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" =
SIZE=3D1 FACE=3D"Arial">&nbsp;&nbsp;&nbsp; </FONT></SPAN></P>
<BR>

<P ALIGN=3DLEFT><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><BR>
</SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#144D29" SIZE=3D2 FACE=3D"Arial">Deliver =
the Future First with Sonus Networks.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C774F5.E5758E45--


--===============0470085288==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0470085288==--




From sipping-bounces@ietf.org Mon Apr 02 13:18:04 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYQ9k-0001Q6-A2; Mon, 02 Apr 2007 13:17:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYQ9j-0001Pg-7C; Mon, 02 Apr 2007 13:17:23 -0400
Received: from bay0-omc1-s36.bay0.hotmail.com ([65.54.246.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYQ9f-0002SY-TS; Mon, 02 Apr 2007 13:17:23 -0400
Received: from bayc1-pasmtp06.bayc1.hotmail.com ([65.54.191.166]) by
	bay0-omc1-s36.bay0.hotmail.com with Microsoft
	SMTPSVC(6.0.3790.2668); Mon, 2 Apr 2007 10:17:19 -0700
X-Originating-IP: [216.13.42.68]
X-Originating-Email: [eric_d_cooper@sympatico.ca]
Received: from ronin ([216.13.42.68]) by bayc1-pasmtp06.bayc1.hotmail.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Apr 2007 10:22:03 -0700
Message-ID: <0be101c7754a$c424bc40$65500a0a@ronin>
From: "Eric Cooper" <eric_d_cooper@sympatico.ca>
To: "David A. Bryan" <dbryan@sipeerior.com>,
	"Jeroen van Bemmel" <jbemmel@zonnet.nl>
References: <24CCCC428EFEA2469BF046DB3C7A8D225274F4@namail5.corp.adobe.com><EC0E1E0E-2E83-4674-BAC0-78CB94F0BD43@cisco.com><24CCCC428EFEA2469BF046DB3C7A8D223ADECA@namail5.corp.adobe.com><4FF5FA52-1B38-4964-87AE-72300CE89A1F@cisco.com><24CCCC428EFEA2469BF046DB3C7A8D223ADED9@namail5.corp.adobe.com><460D4825.2090800@cisco.com><7b683f3f0703301556j95f2c10sf12d666994dedf6f@mail.gmail.com><460D9D9C.1040304@cisco.com><24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com><00b201c7748e$33067df0$0601a8c0@BEMBUSTER>
	<4d4304a00704020632r71315532s1be1df106c4f426a@mail.gmail.com>
Subject: Re: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Mon, 2 Apr 2007 13:16:52 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-OriginalArrivalTime: 02 Apr 2007 17:22:03.0125 (UTC)
	FILETIME=[6DF70250:01C7754B]
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	David R Oran <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

> Personally, I think that putting P2PSIP peers in edge devices would be
> a good place to do it for home wireline users -- as Henry points out,
> it avoids the NAT issue, among other things.=20

Until some ISP NATs their networks.


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 02 15:08:24 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYRsV-0004uL-Ve; Mon, 02 Apr 2007 15:07:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYRsT-0004s3-DO; Mon, 02 Apr 2007 15:07:41 -0400
Received: from exprod6og55.obsmtp.com ([64.18.1.191])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HYRsP-0001fq-LY; Mon, 02 Apr 2007 15:07:41 -0400
Received: from source ([192.150.20.142]) by exprod6ob55.postini.com
	([64.18.5.12]) with SMTP; Mon, 02 Apr 2007 12:07:27 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l32J7OSd005509; Mon, 2 Apr 2007 12:07:25 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l32J7KI9005252; Mon, 2 Apr 2007 12:07:20 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Apr 2007 12:07:19 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Mon, 2 Apr 2007 12:07:09 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223ADF29@namail5.corp.adobe.com>
In-Reply-To: <00b201c7748e$33067df0$0601a8c0@BEMBUSTER>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Thread-Index: Acd0jlEP0S2okoXWTMqTvEX9i1NkUwAyxCog
References: <24CCCC428EFEA2469BF046DB3C7A8D225274F4@namail5.corp.adobe.com>	<072C5B76F7CEAB488172C6F64B30B5E302C88E1B@xmb-rtp-20b.amer.cisco.com>	<24CCCC428EFEA2469BF046DB3C7A8D223ADEC5@namail5.corp.adobe.com>	<4603929D.4070604@cisco.com>	<24CCCC428EFEA2469BF046DB3C7A8D223ADEC8@namail5.corp.adobe.com>	<EC0E1E0E-2E83-4674-BAC0-78CB94F0BD43@cisco.com>	<24CCCC428EFEA2469BF046DB3C7A8D223ADECA@namail5.corp.adobe.com>	<4FF5FA52-1B38-4964-87AE-72300CE89A1F@cisco.com>	<24CCCC428EFEA2469BF046DB3C7A8D223ADED9@namail5.corp.adobe.com>	<460D4825.2090800@cisco.com><7b683f3f0703301556j95f2c10sf12d666994dedf6f@mail.gmail.com><460D9D9C.1040304@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com>
	<00b201c7748e$33067df0$0601a8c0@BEMBUSTER>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Jeroen van Bemmel" <jbemmel@zonnet.nl>,
	"Paul Kyzivat" <pkyzivat@cisco.com>, "Eunsoo Shim" <eunsooshim@gmail.com>
X-OriginalArrivalTime: 02 Apr 2007 19:07:19.0860 (UTC)
	FILETIME=[23084740:01C7755A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dd7e0c3fd18d19cffdd4de99a114001d
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	David R Oran <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org,
	zhuxian <zhuxian@huawei.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Jeroen,

These are valid points.
As David Bryan has mentioned, we would like to have P2P SIP in all =
endpoints and in all devices.

Mobile devices require however the client protocol and I hope we will =
soon have a write-up to explain this.

Na=EFve question: How do we distinguish here between deployment scenario =
and usage scenario, unless we limit the usage scenario to the GUI =
capability?

Thanks, Henry

-----Original Message-----
From: Jeroen van Bemmel [mailto:jbemmel@zonnet.nl]=20
Sent: Sunday, April 01, 2007 1:47 PM
To: Henry Sinnreich; Paul Kyzivat; Eunsoo Shim
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; =
p2prg@ietf.org; sipping@ietf.org; zhuxian
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario

Henry,

Aren't you confusing "usage scenarios" with "deployment scenarios" here? =
Why=20
restrict P2P SIP to only certain types of devices? And if you insist on=20
that, why not mobile devices?

Regards,
Jeroen

Henry Sinnreich wrote:
> Paul,
>
>> I more or less agree with the final conclusion below.
>
> This is good starting point to discuss some usage scenarios.
>
> Putting on my former hat as an employee for a carrier, I cannot
> overlook the following:
>
> P2P SIP implemented correctly in the residential access box or cable
> set-top box indeed is a good or better replacement for the entire VoIP
> network infrastructure (cost, operations, new services, etc).
> Integrated access devices for the enterprise can probably play a
> similar role, not to mention existing P2P PBX products (please refer
> to all the advantages of P2P that need not repeated here).
>
> What do people think of these three usage scenarios for P2P SIP:
> - SIP peer in the DSL access device,
> - SIP peer in the cable access device,
> - SIP peer in enterprise network integrated access device (IAD).
>
> Note that these examples imply very low churn for the peers and add
> the data retention resilience of P2P (geographic diversity is native
> and mobile, etc.). Incidentally, NAT traversal may also not be a
> problem, or at least an easier problem.
>
> What do you all think?
>
> I have taken the liberty to copy the P2P SIP list, since the low churn
> scenarios are of interest for the DHT selection. Or just pick the same
> DHT for all scenarios anyway? I don't think so.
>
> Thanks, Henry
>
>
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Friday, March 30, 2007 6:31 PM
> To: Eunsoo Shim
> Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
> p2prg@ietf.org; sipping@ietf.org; zhuxian
> Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
>
> I more or less agree with the final conclusion below.
>
> My main point here is that P2P and C/S need not be enemies. Nor is a
> total C/S system necessarily evil. What is most evil is *bundling* of
> services that prevents freedom of choice.
>
> I think I would be quite happy with a SP that provides a
> registrar/proxy
>
> and allows me to provide all other features as I see fit - by taking
> them ala carte from the SP, or subscribing to them from one or more
> other SPs, or by providing them myself via appliances I own. If that
> registrar/proxy was replaced by a P2P sip community, the differences,
> if
>
> any, would hopefully be more a function of the implementation and the
> business models of those involved than the architecture.
>
> (I gather the general assumption is that a P2P setup will be *free*.
> But
>
> I have a hard time believing that. If most of the usage is by mobile
> devices that can't be peers, then somebody will have to pay for enough
> peers to support them. If it isn't free, then how is it better than a
> well engineered C/S system?)
>
> So I think the key thing here is that some features will require
> getting
>
> some help from another node. There ought to be the option to pick a
> different source for each helper you require, and an ability for it
> all to play together.
>
> Paul
>
> Eunsoo Shim wrote:
>> Please see my inline comment.
>>
>> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com
>> <mailto:pkyzivat@cisco.com>> wrote:
>>
>>
>>
>>     Henry Sinnreich wrote:
>>      > David Oran wrote (with regard to voice mail):
>>      >
>>      >> I'm not saying this can't be made to work, only that it isn't
>>      > immediately >obvious that it has advantages over a classic
>>     application
>>      > server >approach.
>>      >
>>      > The answer for VM is "it depends":
>>      >
>>
>>
>> I agree. It really depends. Certainly there are tradeoffs.
>>
>>      > There are several commercial P2P IP PBX solutions without any
>>     server for
>>      > VM or anything else. No doubt the IT organization appreciates
>>      just > having to plug in the IP phones and GWY to the PSTN
>>      without any > configuration ever for VM or any other PBX
>> feature.
>>
>>     I don't understand. Are you saying they don't have VM, or that
>>     they don't have a *server* for VM?
>>
>>
>> I guess they don't have a  *server* for  VM.
>>
>>      > For public P2P SIP networks there are two more scenarios
>>      where VM can > reside (and without ever spending one cent on VM
>>     servers + IT systems):
>>      >
>>      > - In Cable and DSL service provider networks: The residential
>>     router can
>>      > act as a voice recorder
>>
>>     That is simply an example of the user having an appliance of his
>>     own that provides VM service.
>>
>>      > and P2P can cover the not too frequent cases,
>>      > where the router is not in operation, so the data is backed
>>     up in other
>>      > peer residential gateways (encrypted).
>>
>>     I guess I just need to have more info about how this would work
>>     before I will be convinced it is feasible and trustworthy.
>>
>>
>> Well, 'trustworthy' could be  considered in many angles.
>> If it is about privacy of the message, a public key based encryption
>> would provide acceptable privacy.
>> If it is about reliability of the message delivery, well, a P2P based
>> asynchronous message delivery (like VM) is most likely less reliable
>> than a well managed server based system.
>> However, my experience with Skype's asynchronous message delivery was
>> not bad. Actually I don't see any significant difference between it
>> and my cellular service provider's VM service. :-)
>> Reliability is always a challenge for P2P, for sure. But, I believe
>> it
>
>> is feasible to build a P2P system for VM acceptable for many
>> scenarios.
>>
>>      > - In mobile networks: The VM can reside in quite stable peers
>>     inside the
>>      > wireless base station network. The peers in the base station
>>      network > need no configuration, etc.
>>
>>     I don't understand. I guess that could be true if the peers are
>>     willing to store an arbitrary amount of VM indefinitely for
>>     anybody. Is that believable?
>>
>>
>> It depends.
>> In a very nice environment where all the peers are willing to
>> cooperate at their best, the peers will store as much as they can.
>> In a tough environment, the situation will be different.
>>
>>     This seems to translate to a model where it is assumed that
>>     those nodes that are on most of the time will be willing to
>>     provide VM storage for those nodes that aren't on most of the
>> time.
>>
>>
>> This is again related to reliability of P2P systems or topics like
>> free riders and reputation.
>> A P2P system is a community or society. To be simple, if many of the
>> members are bad, the community won't work well. If the majority of
>> the
>
>> members are good, the community will work well or reasonably.
>>
>>      > Add to this the conferencing capability coming from p2p
>>      application > layer multicast, the SIP e2e control capabilities
>>      (for such as > auto-attendant, agent workstation, etc.) and one
>>      has to wonder why IT > networks, public VoIP networks and end
>>      users should support the huge > cost of hand engineering,
>>     testing, monitoring, maintaining server based
>>      > VoIP networks. P2P self configuration is nothing less that
>>      automation > applied to VoIP, plus the shifting of computing to
>>     the endpoints, where
>>      > there is an abundance of unused CPU, storage, bandwidth and
>>     electricity.
>>      >
>>      > Eric Burger also notes IM changes completely the usage for VM
>>      and may > make unnecessary to place calls on VM in the first
>> place.
>>
>>     I find this more promising.
>>
>>
>>
>>
>> In overall, are we discussing if P2P systems based VM can work? I
>> think it can work.  Just it depends on many things.
>> If it is not super-reliable, should we disregard it? I would say no.
>>
>> On the other hand, do we have to abandon client server based VM and
>> switch to P2P system based VM? It is upto each of us.
>> Client server based VM systems are already there.
>> So why don't we work on P2P based VM now?
>>
>> Thanks.
>>
>> Eunsoo
>
> _______________________________________________
> Sipping mailing list  https://www1.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=20


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 02 15:13:11 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYRxJ-0000Yb-TP; Mon, 02 Apr 2007 15:12:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYRxH-0000TK-Re
	for sipping@ietf.org; Mon, 02 Apr 2007 15:12:39 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYRxG-0002eE-Hh
	for sipping@ietf.org; Mon, 02 Apr 2007 15:12:39 -0400
Received: from [171.70.229.153] (dhcp-171-70-229-153.cisco.com
	[171.70.229.153]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l32IJ05Q022559
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 2 Apr 2007 13:19:02 -0500
In-Reply-To: <006601c77476$c48434b0$0601a8c0@BEMBUSTER>
References: <989763567E51AB48BE015DF7BB960CAD029C8953@esealmw111><200703220239.l2M2d0Sj021023@dragon.ariadne.com><1174553260.3573.15.camel@dhcp-1642.ietf68.org><200703291850.l2TIogEJ028228@dragon.ariadne.com><D80311DB-EB22-492B-8965-37B3CA4F1ECD@softarmor.com><200703302231.l2UMVJc0019598@dragon.ariadne.com>
	<B2E5BE59-1061-43ED-AD63-AB129BB4B2DE@softarmor.com>
	<006601c77476$c48434b0$0601a8c0@BEMBUSTER>
Mime-Version: 1.0 (Apple Message framework v752.3)
X-Priority: 3
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FCEEE44C-FE7A-4608-B9E6-CCDBA06A448E@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Service Identification in SIP
Date: Mon, 2 Apr 2007 14:12:30 -0500
To: Jeroen van Bemmel <jbemmel@zonnet.nl>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



On Apr 1, 2007, at 10:59 AM, Jeroen van Bemmel wrote:

> Dean,
>
> There are providers that offer the Internet model. They are called  
> "Internet Service Providers", or ISPs. If traditional telco's would  
> adopt the internet model, they would not be considered telco's  
> anymore. In many cases, your "old-school network operators" also  
> act as ISP in one way or another. You can get a subscription from  
> such an ISP, and implement the "in the UA" model on top of that.
>
> If I understand the "in the UA" service model, the role of the  
> operator would be to host only a SIP proxy service? In today's  
> regulatory systems such a model would not work, because of  
> requirements on legal intercept (amongst others). In order to  
> fulfill such requirements, telco's have no choice but to deploy an  
> infrastructure that provides the necessary control.
>
> So perhaps it should be considered that it is not necessarily the  
> operators that are blocking adoption of this "ideal" architecture


You seem to have missed my point.

UA is not a synonym for UE and User Agent is NOT the same as User  
Equipment.

A mobile phone and a carrier-class voicemail platform can both be SIP  
User Agents. It is unlikely that an operator would consider them both  
User Equipment.

Some people are trying to build services at the routing layer that  
should instead be built at the application layer, because they think  
that "in the network" means the former and since they think they  
control "the network" that the service has to be built this way.

But the fact is that operators control a lot more than just the  
routing layer. They control (or potentially control) large-scale user  
agents (like voice mail services, conference bridges, etc.) that  
could be reasonably offered as services to end users.

It's not that we object to operators using their advantageous  
position to offer services via user agents. We object to them messing  
up the routing layer so that it 1) doesn't work right as a general  
model, and 2) makes the operator-controlled shared user-agent  
platforms the ONLY things that end users can access.

--
Dean






_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 02 15:29:47 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYSCh-0004GY-F9; Mon, 02 Apr 2007 15:28:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYSCg-0004GT-KH
	for sipping@ietf.org; Mon, 02 Apr 2007 15:28:34 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYSCW-0005AT-2Y
	for sipping@ietf.org; Mon, 02 Apr 2007 15:28:32 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6E34A2051F; Mon,  2 Apr 2007 21:28:17 +0200 (CEST)
X-AuditID: c1b4fb3e-ad9eabb0000061ca-f0-461159511d56 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5F72820209; Mon,  2 Apr 2007 21:28:17 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Apr 2007 21:28:16 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Apr 2007 21:28:16 +0200
Received: from [131.160.126.167] (rvi2-126-167.lmf.ericsson.se
	[131.160.126.167])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 59040236A;
	Mon,  2 Apr 2007 22:28:16 +0300 (EEST)
Message-ID: <46115950.9020100@ericsson.com>
Date: Mon, 02 Apr 2007 22:28:16 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Apr 2007 19:28:16.0777 (UTC)
	FILETIME=[10369790:01C7755D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: Mary Barnes <mary.barnes@nortel.com>
Subject: [Sipping] Draft minutes of our Prague meeting
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Folks,

here you have the draft minutes of our last meeting in Prague:
http://www3.ietf.org/proceedings/07mar/minutes/sipping.txt

Any comments?

Thanks,

Gonzalo
SIPPING co-chair


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 02 15:30:38 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYSDn-0005O7-GB; Mon, 02 Apr 2007 15:29:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYSDl-0005Nz-6w
	for sipping@ietf.org; Mon, 02 Apr 2007 15:29:41 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYSDi-0005Rs-SE
	for sipping@ietf.org; Mon, 02 Apr 2007 15:29:41 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 02 Apr 2007 15:29:39 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l32JTcD1025238; 
	Mon, 2 Apr 2007 15:29:38 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l32JTXlI028688; 
	Mon, 2 Apr 2007 19:29:38 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Apr 2007 15:29:34 -0400
Received: from [161.44.174.244] ([161.44.174.244]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Apr 2007 15:29:34 -0400
Message-ID: <4611599E.7030302@cisco.com>
Date: Mon, 02 Apr 2007 15:29:34 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Service Identification in SIP
References: <989763567E51AB48BE015DF7BB960CAD029C8953@esealmw111><200703220239.l2M2d0Sj021023@dragon.ariadne.com><1174553260.3573.15.camel@dhcp-1642.ietf68.org><200703291850.l2TIogEJ028228@dragon.ariadne.com><D80311DB-EB22-492B-8965-37B3CA4F1ECD@softarmor.com><200703302231.l2UMVJc0019598@dragon.ariadne.com>	<B2E5BE59-1061-43ED-AD63-AB129BB4B2DE@softarmor.com>	<006601c77476$c48434b0$0601a8c0@BEMBUSTER>
	<FCEEE44C-FE7A-4608-B9E6-CCDBA06A448E@softarmor.com>
In-Reply-To: <FCEEE44C-FE7A-4608-B9E6-CCDBA06A448E@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Apr 2007 19:29:34.0427 (UTC)
	FILETIME=[3E7F0AB0:01C7755D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2683; t=1175542178;
	x=1176406178; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Service=20Identification=20in=20SIP
	|Sender:=20 |To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=sR/VeEWKu8ZtipCbgV+OkXIYJTPXFduCsxowTZ3u5JM=;
	b=b7nZlN2RUxIma6hUJiz/S+YuKqwEyn3npA7KiDGBQLXIsOqTJTgWyKLVAmik2drYIW2pJoNw
	qzsht69t+AZgoQ94X+/mABMn171FOqwkw5d/8ZdlyftoeCQjVTxGQaLQ;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dean,

You're on a roll today.

	Amen! (again)
	Paul

Dean Willis wrote:
> 
> 
> On Apr 1, 2007, at 10:59 AM, Jeroen van Bemmel wrote:
> 
>> Dean,
>>
>> There are providers that offer the Internet model. They are called 
>> "Internet Service Providers", or ISPs. If traditional telco's would 
>> adopt the internet model, they would not be considered telco's 
>> anymore. In many cases, your "old-school network operators" also act 
>> as ISP in one way or another. You can get a subscription from such an 
>> ISP, and implement the "in the UA" model on top of that.
>>
>> If I understand the "in the UA" service model, the role of the 
>> operator would be to host only a SIP proxy service? In today's 
>> regulatory systems such a model would not work, because of 
>> requirements on legal intercept (amongst others). In order to fulfill 
>> such requirements, telco's have no choice but to deploy an 
>> infrastructure that provides the necessary control.
>>
>> So perhaps it should be considered that it is not necessarily the 
>> operators that are blocking adoption of this "ideal" architecture
> 
> 
> You seem to have missed my point.
> 
> UA is not a synonym for UE and User Agent is NOT the same as User 
> Equipment.
> 
> A mobile phone and a carrier-class voicemail platform can both be SIP 
> User Agents. It is unlikely that an operator would consider them both 
> User Equipment.
> 
> Some people are trying to build services at the routing layer that 
> should instead be built at the application layer, because they think 
> that "in the network" means the former and since they think they control 
> "the network" that the service has to be built this way.
> 
> But the fact is that operators control a lot more than just the routing 
> layer. They control (or potentially control) large-scale user agents 
> (like voice mail services, conference bridges, etc.) that could be 
> reasonably offered as services to end users.
> 
> It's not that we object to operators using their advantageous position 
> to offer services via user agents. We object to them messing up the 
> routing layer so that it 1) doesn't work right as a general model, and 
> 2) makes the operator-controlled shared user-agent platforms the ONLY 
> things that end users can access.
> 
> -- 
> Dean
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.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
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 02 19:12:39 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYVgW-0003KY-TS; Mon, 02 Apr 2007 19:11:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYVgU-0003Jo-E8; Mon, 02 Apr 2007 19:11:34 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYVgS-00032p-VB; Mon, 02 Apr 2007 19:11:34 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 02 Apr 2007 19:11:33 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l32NBWuQ022823; 
	Mon, 2 Apr 2007 19:11:32 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l32NBSlI023686; 
	Mon, 2 Apr 2007 23:11:32 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Apr 2007 19:11:28 -0400
Received: from [161.44.174.244] ([161.44.174.244]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Apr 2007 19:11:28 -0400
Message-ID: <46118DA0.4070305@cisco.com>
Date: Mon, 02 Apr 2007 19:11:28 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Henry Sinnreich <hsinnrei@adobe.com>
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
References: <24CCCC428EFEA2469BF046DB3C7A8D225274F4@namail5.corp.adobe.com>	
	<072C5B76F7CEAB488172C6F64B30B5E302C88E1B@xmb-rtp-20b.amer.cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADEC5@namail5.corp.adobe.com>	
	<4603929D.4070604@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADEC8@namail5.corp.adobe.com>	
	<EC0E1E0E-2E83-4674-BAC0-78CB94F0BD43@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADECA@namail5.corp.adobe.com>	
	<4FF5FA52-1B38-4964-87AE-72300CE89A1F@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADED9@namail5.corp.adobe.com>	
	<460D4825.2090800@cisco.com>
	<7b683f3f0703301556j95f2c10sf12d666994dedf6f@mail.gmail.com>
	<460D9D9C.1040304@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com>
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Apr 2007 23:11:28.0358 (UTC)
	FILETIME=[3E37B060:01C7757C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8846; t=1175555492;
	x=1176419492; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[P2Prg]=20RE=3A=20[Sipping]=20Simple=20SIP=20usage=20
	scenario |Sender:=20
	|To:=20Henry=20Sinnreich=20<hsinnrei@adobe.com>;
	bh=nVRJsxrHKZvG+PMOZg7zoRES1kia/kZgTm8JH806kzo=;
	b=SdNIWWdklsVdEvCKtrYgm7JiCEZ/JGKRBiKuAc4qq/8edCckWYJeo7oamaP5BuSjKkXl8KRk
	/I0hVhIovnX4xTO0Qt2zKOd5hgDZFtwomCrtBUTaV5o1ztaBn0w7upgD;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6a45e05c1e4343200aa6b327df2c43fc
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	David R Oran <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org,
	zhuxian <zhuxian@huawei.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Henry Sinnreich wrote:
> Paul,
> 
>> I more or less agree with the final conclusion below.
> 
> This is good starting point to discuss some usage scenarios.
> 
> Putting on my former hat as an employee for a carrier, I cannot overlook
> the following:
> 
> P2P SIP implemented correctly in the residential access box or cable
> set-top box indeed is a good or better replacement for the entire VoIP
> network infrastructure (cost, operations, new services, etc). 
> Integrated access devices for the enterprise can probably play a similar
> role, not to mention existing P2P PBX products (please refer to all the
> advantages of P2P that need not repeated here).
> 
> What do people think of these three usage scenarios for P2P SIP:
> - SIP peer in the DSL access device,
> - SIP peer in the cable access device,

These seem quite reasonable, assuming that a device connected at this 
point is able to function properly as a peer. (I haven't been following 
what the assumptions are about required network capabilities of peers.)

> - SIP peer in enterprise network integrated access device (IAD).

I think this depends greatly on what expectations / contractual 
guarantees the enterprise has. Its unclear to me what guarantees can be 
made about a P2PSIP network will be able to make, and its unclear what 
kind of infrastructure would be installed by/for someone willing to make 
guarantees.

	Paul

> Note that these examples imply very low churn for the peers and add the
> data retention resilience of P2P (geographic diversity is native and
> mobile, etc.). Incidentally, NAT traversal may also not be a problem, or
> at least an easier problem.
> 
> What do you all think?
> 
> I have taken the liberty to copy the P2P SIP list, since the low churn
> scenarios are of interest for the DHT selection. Or just pick the same
> DHT for all scenarios anyway? I don't think so.
> 
> Thanks, Henry
> 
> 
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: Friday, March 30, 2007 6:31 PM
> To: Eunsoo Shim
> Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
> p2prg@ietf.org; sipping@ietf.org; zhuxian
> Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
> 
> I more or less agree with the final conclusion below.
> 
> My main point here is that P2P and C/S need not be enemies. Nor is a 
> total C/S system necessarily evil. What is most evil is *bundling* of 
> services that prevents freedom of choice.
> 
> I think I would be quite happy with a SP that provides a registrar/proxy
> 
> and allows me to provide all other features as I see fit - by taking 
> them ala carte from the SP, or subscribing to them from one or more 
> other SPs, or by providing them myself via appliances I own. If that 
> registrar/proxy was replaced by a P2P sip community, the differences, if
> 
> any, would hopefully be more a function of the implementation and the 
> business models of those involved than the architecture.
> 
> (I gather the general assumption is that a P2P setup will be *free*. But
> 
> I have a hard time believing that. If most of the usage is by mobile 
> devices that can't be peers, then somebody will have to pay for enough 
> peers to support them. If it isn't free, then how is it better than a 
> well engineered C/S system?)
> 
> So I think the key thing here is that some features will require getting
> 
> some help from another node. There ought to be the option to pick a 
> different source for each helper you require, and an ability for it all 
> to play together.
> 
> 	Paul
> 
> Eunsoo Shim wrote:
>> Please see my inline comment.
>>
>> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com 
>> <mailto:pkyzivat@cisco.com>> wrote:
>>
>>
>>
>>     Henry Sinnreich wrote:
>>      > David Oran wrote (with regard to voice mail):
>>      >
>>      >> I'm not saying this can't be made to work, only that it isn't
>>      > immediately >obvious that it has advantages over a classic
>>     application
>>      > server >approach.
>>      >
>>      > The answer for VM is "it depends":
>>      >
>>
>>
>> I agree. It really depends. Certainly there are tradeoffs.
>>
>>      > There are several commercial P2P IP PBX solutions without any
>>     server for
>>      > VM or anything else. No doubt the IT organization appreciates
> just
>>      > having to plug in the IP phones and GWY to the PSTN without any
>>      > configuration ever for VM or any other PBX feature.
>>
>>     I don't understand. Are you saying they don't have VM, or that
> they
>>     don't have a *server* for VM?
>>
>>
>> I guess they don't have a  *server* for  VM.
>>
>>      > For public P2P SIP networks there are two more scenarios where
> VM can
>>      > reside (and without ever spending one cent on VM servers + IT
>>     systems):
>>      >
>>      > - In Cable and DSL service provider networks: The residential
>>     router can
>>      > act as a voice recorder
>>
>>     That is simply an example of the user having an appliance of his
> own
>>     that provides VM service.
>>
>>      > and P2P can cover the not too frequent cases,
>>      > where the router is not in operation, so the data is backed up
> in
>>     other
>>      > peer residential gateways (encrypted).
>>
>>     I guess I just need to have more info about how this would work
> before I
>>     will be convinced it is feasible and trustworthy.
>>
>>
>> Well, 'trustworthy' could be  considered in many angles.
>> If it is about privacy of the message, a public key based encryption 
>> would provide acceptable privacy.
>> If it is about reliability of the message delivery, well, a P2P based 
>> asynchronous message delivery (like VM) is most likely less reliable 
>> than a well managed server based system.
>> However, my experience with Skype's asynchronous message delivery was 
>> not bad. Actually I don't see any significant difference between it
> and 
>> my cellular service provider's VM service. :-)
>> Reliability is always a challenge for P2P, for sure. But, I believe it
> 
>> is feasible to build a P2P system for VM acceptable for many
> scenarios.
>>      > - In mobile networks: The VM can reside in quite stable peers
>>     inside the
>>      > wireless base station network. The peers in the base station
> network
>>      > need no configuration, etc.
>>
>>     I don't understand. I guess that could be true if the peers are
> willing
>>     to store an arbitrary amount of VM indefinitely for anybody. Is
> that
>>     believable?
>>
>>
>> It depends.
>> In a very nice environment where all the peers are willing to
> cooperate 
>> at their best, the peers will store as much as they can. In a tough 
>> environment, the situation will be different.
>>
>>     This seems to translate to a model where it is assumed that those
> nodes
>>     that are on most of the time will be willing to provide VM storage
> for
>>     those nodes that aren't on most of the time.
>>
>>
>> This is again related to reliability of P2P systems or topics like
> free 
>> riders and reputation.
>> A P2P system is a community or society. To be simple, if many of the 
>> members are bad, the community won't work well. If the majority of the
> 
>> members are good, the community will work well or reasonably.
>>
>>      > Add to this the conferencing capability coming from p2p
> application
>>      > layer multicast, the SIP e2e control capabilities (for such as
>>      > auto-attendant, agent workstation, etc.) and one has to wonder
> why IT
>>      > networks, public VoIP networks and end users should support the
> huge
>>      > cost of hand engineering, testing, monitoring, maintaining
> server
>>     based
>>      > VoIP networks. P2P self configuration is nothing less that
> automation
>>      > applied to VoIP, plus the shifting of computing to the
> endpoints,
>>     where
>>      > there is an abundance of unused CPU, storage, bandwidth and
>>     electricity.
>>      >
>>      > Eric Burger also notes IM changes completely the usage for VM
> and may
>>      > make unnecessary to place calls on VM in the first place.
>>
>>     I find this more promising.
>>
>>           
>>
>>
>> In overall, are we discussing if P2P systems based VM can work? I
> think 
>> it can work.  Just it depends on many things.
>> If it is not super-reliable, should we disregard it? I would say no.
>>
>> On the other hand, do we have to abandon client server based VM and 
>> switch to P2P system based VM? It is upto each of us.
>> Client server based VM systems are already there.
>> So why don't we work on P2P based VM now?
>>  
>> Thanks.
>>
>> Eunsoo
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 02 21:14:38 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYXaS-0001aK-El; Mon, 02 Apr 2007 21:13:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYXaR-0001Zz-C3
	for sipping@ietf.org; Mon, 02 Apr 2007 21:13:27 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYXaO-00005S-Ir
	for sipping@ietf.org; Mon, 02 Apr 2007 21:13:27 -0400
Received: by ug-out-1314.google.com with SMTP id 72so113591ugd
	for <sipping@ietf.org>; Mon, 02 Apr 2007 18:13:19 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
	b=IiOmAag5dY8mR6qM+R3QwXtRxcm9MN4Ptg0u1n9+53VouLlgTq2GUoELfc9rPhsK48XH4WhJ3p8GGV5UzykMETWJN/ekYngYRzBOENIFXalrqEgV5bao7sx537FWNLRTGgguwdO2v5PWer7dF1bMrQE8vrO3poIKfyi+hDRAg+U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
	b=f+smpEQdonjOCN6P9DXbwwaASeS3u4oR5y8suMj10pTDzFkIs5VU+0ufSpy9J6idxqJvE+2rT0ayNIwGUCf65TX9YEbkbtnpc7ij405/4pEpOTKya5Az8R/yyWVYQPYJ3tG1ZK17iL5ZnaQHIu1pMDjqcmxN84xxddmgT3Ut6ds=
Received: by 10.78.83.15 with SMTP id g15mr1574802hub.1175562798363;
	Mon, 02 Apr 2007 18:13:18 -0700 (PDT)
Received: by 10.78.144.6 with HTTP; Mon, 2 Apr 2007 18:13:18 -0700 (PDT)
Message-ID: <1fc32c8f0704021813h4387c0c4uec60e7aa3f75606c@mail.gmail.com>
Date: Mon, 2 Apr 2007 21:13:18 -0400
From: "Michael Slavitch" <slavitch@objectworld.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, "Henry Sinnreich" <hsinnrei@adobe.com>
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
In-Reply-To: <46118DA0.4070305@cisco.com>
MIME-Version: 1.0
References: <24CCCC428EFEA2469BF046DB3C7A8D225274F4@namail5.corp.adobe.com>
	<EC0E1E0E-2E83-4674-BAC0-78CB94F0BD43@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADECA@namail5.corp.adobe.com>
	<4FF5FA52-1B38-4964-87AE-72300CE89A1F@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADED9@namail5.corp.adobe.com>
	<460D4825.2090800@cisco.com>
	<7b683f3f0703301556j95f2c10sf12d666994dedf6f@mail.gmail.com>
	<460D9D9C.1040304@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com>
	<46118DA0.4070305@cisco.com>
X-Google-Sender-Auth: d02fe10449386c3e
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	David R Oran <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org,
	zhuxian <zhuxian@huawei.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1538805413=="
Errors-To: sipping-bounces@ietf.org

--===============1538805413==
Content-Type: multipart/alternative; 
	boundary="----=_Part_283_16317225.1175562798221"

------=_Part_283_16317225.1175562798221
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Sorry for being late into this discussion, but client-server based VM isn't
truly client-server anymore in anything but the smallest or most monolithic
of enterprise networks, in fact the reality is that most if not all
enterprise networks contain just peers and superpeers with the difference
being partially a marketing decision by the vendors, as you can charge much
more for the servers, and a policy decision made either automatically by a
software deployment system or by IT staff which wants to place supernodes
with data sinks on appropriate equipment. In a highly distributed
environment there are potentially hundreds of possible data sinks for a
given application, with the sink based on subnet or geographic location or
balanced load, this can change rapidly over time and does.

In the case of the Microsoft environment such policy is administered and
published between supernodes, ie servers, by Active Directory.  It is
advertised to mere peers through DNS.  There was much discussion a while ago
about building service discovery environment using DNS instead of a P2P
DHT.  It can be argued that a case study of a P2P example done using DNS is
any large Windows Server 2003 based Microsoft network with many servers and
many more clients that also run applications themselves and are not just
dumb terminals. This is almost certainly always the case in all enterprises.
The big difference between C/S SIP and P2PSIP is automation. What is true is
that the square peg in round hole of overloading DNS makes deployments
clumsy and brittle within the enterprise domain and completely unmanageable
and unpublishable outside the firewall which is why the buck stops there in
current enterprise networking products.

The difference between C/S and P2P is largely policy and semantics with the
biggest difference being that the decisions and rules are highly
distributed.  Apart from that they are not just friends, they are fraternal
twins.

Regards

Michael Slavitch




  [image: corp_2colour]
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://www.objectworld.com/>



308 Legget Dr.
Ottawa Ontario
K2K 1Y6 Canada


<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://maps.google.ca/maps?f=q%26hl=en%26q=308%2BLegget%2BDrive%2BOttawa%2BOntario%2BK2K%2B1Y6%26layer=%26sll=45.341061,-75.904541%26sspn=0.007119,0.023839%26ie=UTF8%26z=18%26ll=45.341061,-75.904541%26spn=0.00178,0.00596%26t=h%26om=1>



Michael Slavitch

Lead, Technology Initiatives

slavitch@objectworld.com

PSTN:

+1.888.398.9698

x225

Fax:

+1.613.599.7457



Skype:

  Objectworld<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20MME.EML/>


x225


<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20MME.EML/>

------=_Part_283_16317225.1175562798221
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Sorry for being late into this discussion, but client-server based VM isn&#39;t truly client-server anymore in anything but the smallest or most monolithic of enterprise networks, in fact the reality is that most if not all enterprise networks contain just peers and superpeers with the difference being partially a marketing decision by the vendors, as you can charge much more for the servers, and a policy decision made either automatically by a software deployment system or by IT staff which wants to place supernodes with data sinks on appropriate equipment. In a highly distributed environment there are potentially hundreds of possible data sinks for a given application, with the sink based on subnet or geographic location or balanced load, this can change rapidly over time and does.
<br><br>In the case of the Microsoft environment such policy is administered and published between supernodes, ie servers, by Active Directory.&nbsp; It is advertised to mere peers through DNS.&nbsp;&nbsp;There was much discussion a while ago about building service discovery environment using DNS instead of a P2P DHT.&nbsp; 
It can be argued that a case study of a P2P example done using DNS is any large Windows Server 2003 based Microsoft network with many servers and many more clients that also run applications themselves and are not just dumb terminals. This is almost certainly always the case in all enterprises. The big difference between C/S SIP and P2PSIP is automation. What is true is that the square peg in round hole of overloading DNS makes deployments clumsy and brittle within the enterprise domain and completely unmanageable and unpublishable outside the firewall which is why the buck stops there in current enterprise networking products.
<br><br>The difference between C/S and P2P is largely policy and semantics with the biggest difference being that the decisions and rules are highly distributed.&nbsp; Apart from that they are not just friends, they are fraternal twins.
<br><br>Regards<br><br>Michael Slavitch<br><span></span>

<p><span>&nbsp;</span></p>

<table border="1" cellpadding="0" cellspacing="0" width="100%">
 <tbody><tr>
  <td colspan="4" valign="top" width="638">
  <p><span><br></span></p>
  </td>
 </tr>
 <tr>
  <td valign="top" width="286">
  <p><a href="https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://www.objectworld.com/" title="Objectworld Communications" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"><span><img src="https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20MME.EML/1_multipart/image001.jpg?Security=3" alt="corp_2colour" border="0" height="42" width="237">

</span></a><span></span></p>
  <p><span>&nbsp;</span></p>
  </td>
  <td valign="top" width="211">
  <p><span>308 Legget Dr. <br>
  Ottawa Ontario <br>
  K2K 1Y6 Canada</span><span></span></p>
  </td>
  <td valign="top" width="137">
  <p align="right"><a href="https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://maps.google.ca/maps?f=q%26hl=en%26q=308%2BLegget%2BDrive%2BOttawa%2BOntario%2BK2K%2B1Y6%26layer=%26sll=45.341061,-75.904541%26sspn=0.007119,0.023839%26ie=UTF8%26z=18%26ll=45.341061,-75.904541%26spn=0.00178,0.00596%26t=h%26om=1" title="308 Legget Drive Ottawa Ontario K2K 1Y6" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">

<span><img src="https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20MME.EML/1_multipart/image002.png?Security=3" border="0" height="29" width="29">

</span></a><span></span></p>
  </td>
  <td width="5"><p>&nbsp;</p></td>
 </tr>
 <tr>
  <td valign="top" width="286">
  <table border="0" cellpadding="0" cellspacing="0">
   <tbody><tr>
    <td valign="top" width="278">
    <p><span>Michael
    Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></p>
    </td>
   </tr>
   <tr>
    <td valign="top" width="278">
    <p><span>Lead, Technology Initiatives</span></p>
    </td>
   </tr>
   <tr>
    <td valign="top" width="278">
    <p><span><a href="mailto:slavitch@objectworld.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">slavitch@objectworld.com</a></span></p>
    </td>
   </tr>
  </tbody></table>
  </td>
  <td valign="top" width="211">
  <table border="0" cellpadding="0" cellspacing="0" width="204">
   <tbody><tr>
    <td valign="top" width="42">
    <p><span>PSTN:&nbsp; </span></p>
    </td>
    <td valign="top" width="131">
    <p><span>+1.888.398.9698</span></p>
    </td>
    <td valign="top" width="31">
    <p><span>x225</span></p>
    </td>
   </tr>
   <tr>
    <td valign="top" width="42">
    <p><span>Fax:</span></p>
    </td>
    <td valign="top" width="131">
    <p><span>+1.613.599.7457</span><span></span></p>
    </td>
    <td valign="top" width="31">
    <p><span>&nbsp;</span></p>
    </td>
   </tr>
   <tr>
    <td valign="top" width="42">
    <p><span>Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></p>
    </td>
    <td valign="top" width="131">
    <p><span>&nbsp;</span><span><a href="https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20MME.EML/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">

<span>Objectworld</span></a></span><span>&nbsp;&nbsp;
    </span></p>
    </td>
    <td valign="top" width="31">
    <p><span>x225</span></p>
    </td>
   </tr>
  </tbody></table>
  </td>
  <td valign="top" width="137">
  <p align="right"><a href="https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20MME.EML/" title="Objectworld" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">

<span><img src="https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20MME.EML/1_multipart/image003.png?Security=3" border="0" height="26" width="26">

</span></a><span></span></p>
  </td>
  <td width="5"><p>&nbsp;</p></td>
 </tr>
</tbody></table>

<p><span>&nbsp;</span></p><br>

------=_Part_283_16317225.1175562798221--


--===============1538805413==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1538805413==--




From sipping-bounces@ietf.org Tue Apr 03 06:29:46 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYgFk-0006dJ-HU; Tue, 03 Apr 2007 06:28:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYgFj-0006dD-Kv
	for sipping@ietf.org; Tue, 03 Apr 2007 06:28:39 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYgFc-0006aX-Ta
	for sipping@ietf.org; Tue, 03 Apr 2007 06:28:39 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	58E7720AC8; Tue,  3 Apr 2007 12:28:30 +0200 (CEST)
X-AuditID: c1b4fb3c-aa4eebb0000073d5-b4-46122c4e0d06 
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	39DB420505; Tue,  3 Apr 2007 12:28:30 +0200 (CEST)
Received: from esealmw106.eemea.ericsson.se ([153.88.200.69]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Apr 2007 12:28:29 +0200
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
Subject: RE: [Sipping] Session Establishment Efficiency Rate
Date: Tue, 3 Apr 2007 12:28:28 +0200
Message-ID: <97F2AD7AA4EAD948827639B06CF2745FC4D462@esealmw106.eemea.ericsson.se>
In-Reply-To: <3BC5D44AB71A754FAE3CA68A7597EABEB7BAE1@ZANEVS03.cc-ntd1.covad.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Session Establishment Efficiency Rate
thread-index: AcdXYkku4CAgr+eHTe2Vtg4MEn4t7AH1mCVwBKfN+4AAR6J0cAC1rfJg
From: "Marian Delkinov \(LN/EAB\)" <marian.delkinov@ericsson.com>
To: "Fardid, Reza" <RFardid@Covad.COM>,
	"Daryl Malas" <daryl@level3.net>
X-OriginalArrivalTime: 03 Apr 2007 10:28:29.0816 (UTC)
	FILETIME=[D27E4780:01C775DA]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Reza,=20

Exactly because of the analogy with NER and the meaning it has as
telephony metric I wanted to make clear the right counters, including
for release codes, are used to achieve the same meaning in SIP. I didn't
understand for when you foresee the implementation?

Best regards!
Mario.

-----Original Message-----
From: Fardid, Reza [mailto:RFardid@Covad.COM]=20
Sent: Friday, 30 March, 2007 22:02
To: Marian Delkinov (LN/EAB); Daryl Malas
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Mario,

What I had in mind when I proposed inclusion of SEER in this draft was a
SIP performance metric analogous to NER in the PSTN, within the
framework defined by Daryl:

Telephony Metric/Standard (ITU-T, BellCore, etc.) =3D=3D> SIP ETE Metric

Clearly some SIP metrics defined in this draft do not have a telephony
counterpart.  For the rest, IMO, it is good to stay within the above
framework and leave exclusion/inclusion of specific release codes from
defined metrics to implementation.

Regards,
Reza Fardid
Covad Communications


-----Original Message-----
From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
Sent: Thursday, March 29, 2007 1:07 AM
To: Daryl Malas
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Hi Daryl,

I haven't got your opinion about my comments on the SEER definition.
Have you considered them?=20
Would also be interested to know when a finalized document on the
performance metrics can be released.=20

Thanks!

Best regards!
Mario.

-----Original Message-----
From: Marian Delkinov (LN/EAB)
Sent: Monday, 05 March, 2007 17:06
To: 'Daryl Malas'
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Hi Daryl,

In principle, I agree with you in case we considered this from a user
perspective - then 3xx is not final. However my idea behind including
the 3xx codes was based on the involvement of "#Invite" in the formula.
If a 3xx code would result in sending a new Invite, then it sounds
logical to me to add the 3xx codes in the numerator. (NB: RFC3261
defines 3xx responses as "final" for the SIP transaction, ref. to page
21, Final Response).

Best regards!
Mario.

=20

-----Original Message-----
From: Daryl Malas [mailto:daryl@level3.net]
Sent: Friday, 23 February, 2007 17:00
To: Marian Delkinov (LN/EAB)
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

I don't think 3xx codes should be included, since they would not be
considered a "Final" release cause code.  --Daryl

On Fri, 2007-02-23 at 12:22 +0100, Marian Delkinov (LN/EAB) wrote:
> Hi,
>=20
> If the Network Efficiency Rate is designed to express the ability of=20
> the network to deliver calls (in SIP terms one should perhaps say=20
> "establish sessions"), I think that it might be reasonable to include=20
> few more cases (cause codes) in the numerator: e.g. all redirection=20
> 3xx codes, all 4xx except 408 codes and all 6xx codes. (If you agree=20
> that those are the ones that exclude network failures, congestion and=20
> any other network malfunction).
>=20
> Actually it sounds fair to me if it's the opposite of the Ineffective=20
> Session Attempts (ISA):
> SEER% =3D
> 	   Total # of Invite Requests - # of ISA
> ---------------------------------------------------- x 100
> 	   Total # of Invite Requests
>=20
> What do you think?
>=20
> Best regards!
> Mario.
>=20
> -----Original Message-----
> From: Daryl Malas [mailto:daryl@level3.net]
> Sent: Friday, 23 February, 2007 01:14
> To: sipping@ietf.org
> Subject: [Sipping] Session Establishment Efficiency Rate
>=20
> A couple more people have expressed to me that this adaptation of the=20
> ITU-T E.411 Network Efficiency Rate metric is very valuable.  The=20
> snapshot of the metric from the draft is:
>=20
> "This metric is similar to Session Establishment Rate, but it is=20
> intended to exclude the effects of customer behavior and user agent=20
> behavior.  Essentially, the attempts resulting with a final cause code

> of 480, 486, and 600 would be added to the SER numerator."
>=20
> Does anyone else want to see this metric in the draft?  I personally=20
> think it is an interesting metric.
>=20
> Thanks...
>=20
> --Daryl
>=20
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use=20
> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.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

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 03 08:59:00 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYiZr-0002g2-Bc; Tue, 03 Apr 2007 08:57:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYiZo-0002dQ-Up; Tue, 03 Apr 2007 08:57:32 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYiZm-0000UI-IR; Tue, 03 Apr 2007 08:57:32 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 03 Apr 2007 08:57:31 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l33CvUH8028899; 
	Tue, 3 Apr 2007 08:57:30 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l33CvUlG017038; 
	Tue, 3 Apr 2007 12:57:30 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Apr 2007 08:57:30 -0400
Received: from [161.44.174.244] ([161.44.174.244]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Apr 2007 08:57:29 -0400
Message-ID: <46124F38.7020005@cisco.com>
Date: Tue, 03 Apr 2007 08:57:28 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Michael Slavitch <slavitch@objectworld.com>
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
References: <24CCCC428EFEA2469BF046DB3C7A8D225274F4@namail5.corp.adobe.com>	
	<EC0E1E0E-2E83-4674-BAC0-78CB94F0BD43@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADECA@namail5.corp.adobe.com>	
	<4FF5FA52-1B38-4964-87AE-72300CE89A1F@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADED9@namail5.corp.adobe.com>	
	<460D4825.2090800@cisco.com>	
	<7b683f3f0703301556j95f2c10sf12d666994dedf6f@mail.gmail.com>	
	<460D9D9C.1040304@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com>	
	<46118DA0.4070305@cisco.com>
	<1fc32c8f0704021813h4387c0c4uec60e7aa3f75606c@mail.gmail.com>
In-Reply-To: <1fc32c8f0704021813h4387c0c4uec60e7aa3f75606c@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Apr 2007 12:57:29.0766 (UTC)
	FILETIME=[A31E6460:01C775EF]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3600; t=1175605050;
	x=1176469050; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[P2Prg]=20RE=3A=20[Sipping]=20Simple=20SIP=20usage=20
	scenario |Sender:=20
	|To:=20Michael=20Slavitch=20<slavitch@objectworld.com>;
	bh=pD3W8Ltw24iJlP61MuCtDTPRtqK5p683XEhdmeXTmT0=;
	b=tMCV89EYFmht94ElXG06HwhR/pwwO2WT/h9l4SDB8L77KlJ4qsIJGTGEpYdbxVmQjkouZ8RA
	8MDpE1iatCTW1hDeyZwM5NZ5aZQMQEKEWBJmqlRQ4+d+BfjW86Fitqf7;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	David R Oran <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org,
	zhuxian <zhuxian@huawei.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Michael Slavitch wrote:
> Sorry for being late into this discussion, but client-server based VM 
> isn't truly client-server anymore in anything but the smallest or most 
> monolithic of enterprise networks, in fact the reality is that most if 
> not all enterprise networks contain just peers and superpeers with the 
> difference being partially a marketing decision by the vendors, as you 
> can charge much more for the servers, and a policy decision made either 
> automatically by a software deployment system or by IT staff which wants 
> to place supernodes with data sinks on appropriate equipment.

I'm sorry, but I don't understand the point you are trying to make 
above. You are trying to draw some sort of distinction, but I don't get 
it. Can you try again.

	Thanks,
	Paul

> In a 
> highly distributed environment there are potentially hundreds of 
> possible data sinks for a given application, with the sink based on 
> subnet or geographic location or balanced load, this can change rapidly 
> over time and does.
> 
> In the case of the Microsoft environment such policy is administered and 
> published between supernodes, ie servers, by Active Directory.  It is 
> advertised to mere peers through DNS.  There was much discussion a while 
> ago about building service discovery environment using DNS instead of a 
> P2P DHT.  It can be argued that a case study of a P2P example done using 
> DNS is any large Windows Server 2003 based Microsoft network with many 
> servers and many more clients that also run applications themselves and 
> are not just dumb terminals. This is almost certainly always the case in 
> all enterprises. The big difference between C/S SIP and P2PSIP is 
> automation. What is true is that the square peg in round hole of 
> overloading DNS makes deployments clumsy and brittle within the 
> enterprise domain and completely unmanageable and unpublishable outside 
> the firewall which is why the buck stops there in current enterprise 
> networking products.
> 
> The difference between C/S and P2P is largely policy and semantics with 
> the biggest difference being that the decisions and rules are highly 
> distributed.  Apart from that they are not just friends, they are 
> fraternal twins.
> 
> Regards
> 
> Michael Slavitch
> 
>  
> 
> 
> corp_2colour 
> <https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://www.objectworld.com/>
> 
>  
> 
> 	
> 
> 308 Legget Dr.
> Ottawa Ontario
> K2K 1Y6 Canada
> 
> 	
> 
> <https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://maps.google.ca/maps?f=q%26hl=en%26q=308%2BLegget%2BDrive%2BOttawa%2BOntario%2BK2K%2B1Y6%26layer=%26sll=45.341061,-75.904541%26sspn=0.007119,0.023839%26ie=UTF8%26z=18%26ll=45.341061,-75.904541%26spn=0.00178,0.00596%26t=h%26om=1>
> 
> 	
> 
>  
> 
> Michael Slavitch             
> 
> Lead, Technology Initiatives
> 
> slavitch@objectworld.com <mailto:slavitch@objectworld.com>
> 
> 	
> 
> PSTN: 
> 
> 	
> 
> +1.888.398.9698
> 
> 	
> 
> x225
> 
> Fax:
> 
> 	
> 
> +1.613.599.7457
> 
> 	
> 
>  
> 
> Skype:      
> 
> 	
> 
>   Objectworld 
> <https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20MME.EML/>   
> 
> 
> 	
> 
> x225
> 
> 	
> 
> <https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20MME.EML/>
> 
> 	
> 
>  
> 
>  
> 
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 04 01:41:46 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYyE4-0004AO-C1; Wed, 04 Apr 2007 01:40:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYyE1-000492-Lk
	for sipping@ietf.org; Wed, 04 Apr 2007 01:40:05 -0400
Received: from smtpscan-nl3.aots.nl ([145.7.191.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYyDz-0001Fb-4D
	for sipping@ietf.org; Wed, 04 Apr 2007 01:40:05 -0400
Received: from smtpscan-nl3.aots.nl (localhost [127.0.0.1])
	by localhost.aots.nl (Postfix) with ESMTP id 4709350F;
	Wed,  4 Apr 2007 07:39:54 +0200 (MEST)
Received: from sat-relay1.telecom.ptt.nl (relay3.kpn-telecom.nl [145.7.200.29])
	by smtpscan-nl3.aots.nl (Postfix) with ESMTP id F207751C;
	Wed,  4 Apr 2007 07:39:53 +0200 (MEST)
Received: from KKWNLEX010.kpnnl.local (kkwnlex010.kpnnl.local [145.7.180.33])
	by sat-relay1.telecom.ptt.nl (8.11.6p2-20030924/8.11.6) with ESMTP
	id l345dqT06550; Wed, 4 Apr 2007 07:39:52 +0200
Received: from KKWNLEX181.kpnnl.local ([172.23.222.150]) by
	KKWNLEX010.kpnnl.local with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 4 Apr 2007 07:39:01 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] Service Identification in SIP
Date: Wed, 4 Apr 2007 07:37:58 +0200
Message-ID: <D3BA17190818B44CA969FB72EB43418D01832BBC@KKWNLEX181.kpnnl.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Service Identification in SIP
Thread-Index: Acd02gqbGsty0qcKRqCk7jFKxTM9qQBoVwyg
From: <colin.pons@kpn.com>
To: <Dale.Worley@comcast.net>, <sipping@ietf.org>
X-OriginalArrivalTime: 04 Apr 2007 05:39:01.0015 (UTC)
	FILETIME=[8C4B5270:01C7767B]
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1072215938=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1072215938==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7767B.8BD6CB55"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7767B.8BD6CB55
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

RGFsZSB3b3JsZXkgd3JvdGU6IA0KJyBNeSBpbXByZXNzaW9uIGlzIHRoYXQgaW4gdGhlIFVTLCB0
aGUgZ292ZXJubWVudCBhZ2VuY2llcyBqdXN0IHZhY3V1bQ0KdXAgYWxsIHRoZSBwYWNrZXRzIGdv
aW5nIHRvIHlvdXIgVUEuJyANCg0KSW4gdGhlIGV1IG1vcmUgb3IgbGVzcyB0aGUgc2FtZSBhcHBs
aWVzIHdpdGggcmVnYXJkIHRvICdpbnRlcm5ldCcgdHJhZmZpYy4gSW4gYWRkaXRpb24gSVNQcyBh
cmUgb2JsaWdhdGVkIHRvIHN0b3JlIHVzYWdlIGluZm9ybWF0aW9uIHVuZGVyIHRoZSBMSSByZWdp
bWUJIGZvciBhYm91dCBhIHllYXIgb3Igc28uIEhvd2V2ZXIsIHNvbWUgZ2l2ZXJubWVudHMgYW5k
IExFQXMgd2FudCB0aGUgc2FtZSBMSSBmYWNpbGl0aWVzIGFzIGFyZSBhdmFpbGFibGUgYXQgdGhl
IFBTVE4gKFRETSkuIFRoaXMgaW5jbHVkZXMgcmVhbC10aW1lIGZlZWRzIG9mIGNvbnZlcnNhdGlv
bnMgb2JzY3VyZWQgZnJvbSBib2h0IHRoZSBjYWxsZWQgcGFydHkgYW5kIGNhbGxpbmcgcGFydGll
cy4gSW4gYWRkaXRpb24gTEkgdGFwcyBtdXN0IG5vdCBiZSB2aXNpYmxlIGZvciBuZXR3b3JrIGVu
Z2luZWVycywgb25seSBmb3IgYSBzZWxlY3QgcXVhbGlmaWVkIGZldyBhcmUgYWxsb3dlZCB0byBr
bm93LiBUaGlzIGlzIGhvd2V2ZXIgYW4gaW1wbGVtZW50YXRpb24gaXN1ZSwgbm90IGEgdGVjaG5v
bG9neSBvciBzdGFuZGFyZHMgaXNzdWUuIHAycHNpcCBtYWtlIHNvbWUgb2YgdGhpcyBvYnNvbGV0
ZS4NCg0KQ29saW4gDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiAiRGFsZS5X
b3JsZXlAY29tY2FzdC5uZXQiIDxEYWxlLldvcmxleUBjb21jYXN0Lm5ldD4NClRvOiAic2lwcGlu
Z0BpZXRmLm9yZyIgPHNpcHBpbmdAaFrom sipping-bounces@ietf.org Wed Apr 04 01:41:46 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYyE4-0004AO-C1; Wed, 04 Apr 2007 01:40:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYyE1-000492-Lk
	for sipping@ietf.org; Wed, 04 Apr 2007 01:40:05 -0400
Received: from smtpscan-nl3.aots.nl ([145.7.191.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYyDz-0001Fb-4D
	for sipping@ietf.org; Wed, 04 Apr 2007 01:40:05 -0400
Received: from smtpscan-nl3.aots.nl (localhost [127.0.0.1])
	by localhost.aots.nl (Postfix) with ESMTP id 4709350F;
	Wed,  4 Apr 2007 07:39:54 +0200 (MEST)
Received: from sat-relay1.telecom.ptt.nl (relay3.kpn-telecom.nl [145.7.200.29])
	by smtpscan-nl3.aots.nl (Postfix) with ESMTP id F207751C;
	Wed,  4 Apr 2007 07:39:53 +0200 (MEST)
Received: from KKWNLEX010.kpnnl.local (kkwnlex010.kpnnl.local [145.7.180.33])
	by sat-relay1.telecom.ptt.nl (8.11.6p2-20030924/8.11.6) with ESMTP
	id l345dqT06550; Wed, 4 Apr 2007 07:39:52 +0200
Received: from KKWNLEX181.kpnnl.local ([172.23.222.150]) by
	KKWNLEX010.kpnnl.local with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 4 Apr 2007 07:39:01 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] Service Identification in SIP
Date: Wed, 4 Apr 2007 07:37:58 +0200
Message-ID: <D3BA17190818B44CA969FB72EB43418D01832BBC@KKWNLEX181.kpnnl.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Service Identification in SIP
Thread-Index: Acd02gqbGsty0qcKRqCk7jFKxTM9qQBoVwyg
From: <colin.pons@kpn.com>
To: <Dale.Worley@comcast.net>, <sipping@ietf.org>
X-OriginalArrivalTime: 04 Apr 2007 05:39:01.0015 (UTC)
	FILETIME=[8C4B5270:01C7767B]
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1072215938=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1072215938==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7767B.8BD6CB55"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7767B.8BD6CB55
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

RGFsZSB3b3JsZXkgd3JvdGU6IA0KJyBNeSBpbXByZXNzaW9uIGlzIHRoYXQgaW4gdGhlIFVTLCB0
aGUgZ292ZXJubWVudCBhZ2VuY2llcyBqdXN0IHZhY3V1bQ0KdXAgYWxsIHRoZSBwYWNrZXRzIGdv
aW5nIHRvIHlvdXIgVUEuJyANCg0KSW4gdGhlIGV1IG1vcmUgb3IgbGVzcyB0aGUgc2FtZSBhcHBs
aWVzIHdpdGggcmVnYXJkIHRvICdpbnRlcm5ldCcgdHJhZmZpYy4gSW4gYWRkaXRpb24gSVNQcyBh
cmUgb2JsaWdhdGVkIHRvIHN0b3JlIHVzYWdlIGluZm9ybWF0aW9uIHVuZGVyIHRoZSBMSSByZWdp
bWUJIGZvciBhYm91dCBhIHllYXIgb3Igc28uIEhvd2V2ZXIsIHNvbWUgZ2l2ZXJubWVudHMgYW5k
IExFQXMgd2FudCB0aGUgc2FtZSBMSSBmYWNpbGl0aWVzIGFzIGFyZSBhdmFpbGFibGUgYXQgdGhl
IFBTVE4gKFRETSkuIFRoaXMgaW5jbHVkZXMgcmVhbC10aW1lIGZlZWRzIG9mIGNvbnZlcnNhdGlv
bnMgb2JzY3VyZWQgZnJvbSBib2h0IHRoZSBjYWxsZWQgcGFydHkgYW5kIGNhbGxpbmcgcGFydGll
cy4gSW4gYWRkaXRpb24gTEkgdGFwcyBtdXN0IG5vdCBiZSB2aXNpYmxlIGZvciBuZXR3b3JrIGVu
Z2luZWVycywgb25seSBmb3IgYSBzZWxlY3QgcXVhbGlmaWVkIGZldyBhcmUgYWxsb3dlZCB0byBr
bm93LiBUaGlzIGlzIGhvd2V2ZXIgYW4gaW1wbGVtZW50YXRpb24gaXN1ZSwgbm90IGEgdGVjaG5v
bG9neSBvciBzdGFuZGFyZHMgaXNzdWUuIHAycHNpcCBtYWtlIHNvbWUgb2YgdGhpcyBvYnNvbGV0
ZS4NCg0KQ29saW4gDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiAiRGFsZS5X
b3JsZXlAY29tY2FzdC5uZXQiIDxEYWxlLldvcmxleUBjb21jYXN0Lm5ldD4NClRvOiAic2lwcGlu
Z0BpZXRmLm9yZyIgPHNpcHBpbmdAaWV0Zi5vcmc+DQpTZW50OiAyLTQtMDcgMDU6NTANClN1Ympl
Y3Q6IFJlOiBbU2lwcGluZ10gU2VydmljZSBJZGVudGlmaWNhdGlvbiBpbiBTSVANCg0KICAgRnJv
bTogIkplcm9lbiB2YW4gQmVtbWVsIiA8amJlbW1lbEB6b25uZXQubmw+DQoNCiAgIElmIEkgdW5k
ZXJzdGFuZCB0aGUgImluIHRoZSBVQSIgc2VydmljZSBtb2RlbCwgdGhlIHJvbGUgb2YgdGhlIG9w
ZXJhdG9yIA0KICAgd291bGQgYmUgdG8gaG9zdCBvbmx5IGEgU0lQIHByb3h5IHNlcnZpY2U/IElu
IHRvZGF5J3MgcmVndWxhdG9yeSBzeXN0ZW1zIA0KICAgc3VjaCBhIG1vZGVsIHdvdWxkIG5vdCB3
b3JrLCBiZWNhdXNlIG9mIHJlcXVpcmVtZW50cyBvbiBsZWdhbCBpbnRlcmNlcHQgDQogICAoYW1v
bmdzdCBvdGhlcnMpLiBJbiBvcmRlciB0byBmdWxmaWxsIHN1Y2ggcmVxdWlyZW1lbnRzLCB0ZWxj
bydzIGhhdmUgbm8gDQogICBjaG9pY2UgYnV0IHRvIGRlcGxveSBhbiBpbmZyYXN0cnVjdHVyZSB0
aGF0IHByb3ZpZGVzIHRoZSBuZWNlc3NhcnkgY29udHJvbC4NCg0KTXkgaW1wcmVzc2lvbiBpcyB0
aGF0IGluIHRoZSBVUywgdGhlIGdvdmVybm1lbnQgYWdlbmNpZXMganVzdCB2YWN1dW0NCnVwIGFs
bCB0aGUgcGFja2V0cyBnb2luZyB0byB5b3VyIFVBLg0KDQpEYWxlDQoNCl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpTaXBwaW5nIG1haWxpbmcgbGlzdCAg
aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lwcGluZw0KVGhpcyBsaXN0
IGlzIGZvciBORVcgZGV2ZWxvcG1lbnQgb2YgdGhlIGFwcGxpY2F0aW9uIG9mIFNJUA0KVXNlIHNp
cC1pbXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBz
aXANClVzZSBzaXBAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb2YgY29yZSBTSVANCg==

------_=_NextPart_001_01C7767B.8BD6CB55
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMg
RXhjaGFuZ2UgU2VydmVyIHZlcnNpb24gNi41Ljc2NTAuMjgiPg0KPFRJVExFPlJFOiBbU2lwcGlu
Z10gU2VydmljZSBJZGVudGlmaWNhdGlvbiBpbiBTSVA8L1RJVExFPg0KPC9IRUFEPg0KPEJPRFk+
DQo8IS0tIENvbnZlcnRlZCBmcm9tIHRleHQvcGxhaW4gZm9ybWF0IC0tPg0KDQo8UD48Rk9OVCBT
SVpFPTI+RGFsZSB3b3JsZXkgd3JvdGU6PEJSPg0KJyBNeSBpbXByZXNzaW9uIGlzIHRoYXQgaW4g
dGhlIFVTLCB0aGUgZ292ZXJubWVudCBhZ2VuY2llcyBqdXN0IHZhY3V1bTxCUj4NCnVwIGFsbCB0
aGUgcGFja2V0cyBnb2luZyB0byB5b3VyIFVBLic8QlI+DQo8QlI+DQpJbiB0aGUgZXUgbW9yZSBv
ciBsZXNzIHRoZSBzYW1lIGFwcGxpZXMgd2l0aCByZWdhcmQgdG8gJ2ludGVybmV0JyB0cmFmZmlj
LiBJbiBhZGRpdGlvbiBJU1BzIGFyZSBvYmxpZ2F0ZWQgdG8gc3RvcmUgdXNhZ2UgaW5mb3JtYXRp
b24gdW5kZXIgdGhlIExJIHJlZ2ltZSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBmb3IgYWJvdXQgYSB5ZWFyIG9yIHNvLiBIb3dldmVyLCBzb21lIGdpdmVy
bm1lbnRzIGFuZCBMRUFzIHdhbnQgdGhlIHNhbWUgTEkgZmFjaWxpdGllcyBhcyBhcmUgYXZhaWxh
YmxlIGF0IHRoZSBQU1ROIChURE0pLiBUaGlzIGluY2x1ZGVzIHJlYWwtdGltZSBmZWVkcyBvZiBj
b252ZXJzYXRpb25zIG9ic2N1cmVkIGZyb20gYm9odCB0aGUgY2FsbGVkIHBhcnR5IGFuZCBjYWxs
aW5nIHBhcnRpZXMuIEluIGFkZGl0aW9uIExJIHRhcHMgbXVzdCBub3QgYmUgdmlzaWJsZSBmb3Ig
bmV0d29yayBlbmdpbmVlcnMsIG9ubHkgZm9yIGEgc2VsZWN0IHF1YWxpZmllZCBmZXcgYXJlIGFs
bG93ZWQgdG8ga25vdy4gVGhpcyBpcyBob3dldmVyIGFuIGltcGxlbWVudGF0aW9uIGlzdWUsIG5v
dCBhIHRlY2hub2xvZ3kgb3Igc3RhbmRhcmRzIGlzc3VlLiBwMnBzaXAgbWFrZSBzb21lIG9mIHRo
aXMgb2Jzb2xldGUuPEJSPg0KPEJSPg0KQ29saW48QlI+DQo8QlI+DQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLTxCUj4NCkZyb206ICZxdW90O0RhbGUuV29ybGV5QGNvbWNhc3QubmV0JnF1b3Q7
ICZsdDtEYWxlLldvcmxleUBjb21jYXN0Lm5ldCZndDs8QlI+DQpUbzogJnF1b3Q7c2lwcGluZ0Bp
ZXRmLm9yZyZxdW90OyAmbHQ7c2lwcGluZ0BpZXRmLm9yZyZndDs8QlI+DQpTZW50OiAyLTQtMDcg
MDU6NTA8QlI+DQpTdWJqZWN0OiBSZTogW1NpcHBpbmddIFNlcnZpY2UgSWRlbnRpZmljYXRpb24g
aW4gU0lQPEJSPg0KPEJSPg0KJm5ic3A7Jm5ic3A7IEZyb206ICZxdW90O0plcm9lbiB2YW4gQmVt
bWVsJnF1b3Q7ICZsdDtqYmVtbWVsQHpvbm5ldC5ubCZndDs8QlI+DQo8QlI+DQombmJzcDsmbmJz
cDsgSWYgSSB1bmRlcnN0YW5kIHRoZSAmcXVvdDtpbiB0aGUgVUEmcXVvdDsgc2VydmljZSBtb2Rl
bCwgdGhlIHJvbGUgb2YgdGhlIG9wZXJhdG9yPEJSPg0KJm5ic3A7Jm5ic3A7IHdvdWxkIGJlIHRv
IGhvc3Qgb25seSBhIFNJUCBwcm94eSBzZXJ2aWNlPyBJbiB0b2RheSdzIHJlZ3VsYXRvcnkgc3lz
dGVtczxCUj4NCiZuYnNwOyZuYnNwOyBzdWNoIGEgbW9kZWwgd291bGQgbm90IHdvcmssIGJlY2F1
c2Ugb2YgcmVxdWlyZW1lbnRzIG9uIGxlZ2FsIGludGVyY2VwdDxCUj4NCiZuYnNwOyZuYnNwOyAo
YW1vbmdzdCBvdGhlcnMpLiBJbiBvcmRlciB0byBmdWxmaWxsIHN1Y2ggcmVxdWlyZW1lbnRzLCB0
ZWxjbydzIGhhdmUgbm88QlI+DQombmJzcDsmbmJzcDsgY2hvaWNlIGJ1dCB0byBkZXBsb3kgYW4g
aW5mcmFzdHJ1Y3R1cmUgdGhhdCBwcm92aWRlcyB0aGUgbmVjZXNzYXJ5IGNvbnRyb2wuPEJSPg0K
PEJWV0Zi5vcmc+DQpTZW50OiAyLTQtMDcgMDU6NTANClN1Ympl
Y3Q6IFJlOiBbU2lwcGluZ10gU2VydmljZSBJZGVudGlmaWNhdGlvbiBpbiBTSVANCg0KICAgRnJv
bTogIkplcm9lbiB2YW4gQmVtbWVsIiA8amJlbW1lbEB6b25uZXQubmw+DQoNCiAgIElmIEkgdW5k
ZXJzdGFuZCB0aGUgImluIHRoZSBVQSIgc2VydmljZSBtb2RlbCwgdGhlIHJvbGUgb2YgdGhlIG9w
ZXJhdG9yIA0KICAgd291bGQgYmUgdG8gaG9zdCBvbmx5IGEgU0lQIHByb3h5IHNlcnZpY2U/IElu
IHRvZGF5J3MgcmVndWxhdG9yeSBzeXN0ZW1zIA0KICAgc3VjaCBhIG1vZGVsIHdvdWxkIG5vdCB3
b3JrLCBiZWNhdXNlIG9mIHJlcXVpcmVtZW50cyBvbiBsZWdhbCBpbnRlcmNlcHQgDQogICAoYW1v
bmdzdCBvdGhlcnMpLiBJbiBvcmRlciB0byBmdWxmaWxsIHN1Y2ggcmVxdWlyZW1lbnRzLCB0ZWxj
bydzIGhhdmUgbm8gDQogICBjaG9pY2UgYnV0IHRvIGRlcGxveSBhbiBpbmZyYXN0cnVjdHVyZSB0
aGF0IHByb3ZpZGVzIHRoZSBuZWNlc3NhcnkgY29udHJvbC4NCg0KTXkgaW1wcmVzc2lvbiBpcyB0
aGF0IGluIHRoZSBVUywgdGhlIGdvdmVybm1lbnQgYWdlbmNpZXMganVzdCB2YWN1dW0NCnVwIGFs
bCB0aGUgcGFja2V0cyBnb2luZyB0byB5b3VyIFVBLg0KDQpEYWxlDQoNCl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpTaXBwaW5nIG1haWxpbmcgbGlzdCAg
aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lwcGluZw0KVGhpcyBsaXN0
IGlzIGZvciBORVcgZGV2ZWxvcG1lbnQgb2YgdGhlIGFwcGxpY2F0aW9uIG9mIFNJUA0KVXNlIHNp
cC1pbXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBz
aXANClVzZSBzaXBAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb2YgY29yZSBTSVANCg==

------_=_NextPart_001_01C7767B.8BD6CB55
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMg
RXhjaGFuZ2UgU2VydmVyIHZlcnNpb24gNi41Ljc2NTAuMjgiPg0KPFRJVExFPlJFOiBbU2lwcGlu
Z10gU2VydmljZSBJZGVudGlmaWNhdGlvbiBpbiBTSVA8L1RJVExFPg0KPC9IRUFEPg0KPEJPRFk+
DQo8IS0tIENvbnZlcnRlZCBmcm9tIHRleHQvcGxhaW4gZm9ybWF0IC0tPg0KDQo8UD48Rk9OVCBT
SVpFPTI+RGFsZSB3b3JsZXkgd3JvdGU6PEJSPg0KJyBNeSBpbXByZXNzaW9uIGlzIHRoYXQgaW4g
dGhlIFVTLCB0aGUgZ292ZXJubWVudCBhZ2VuY2llcyBqdXN0IHZhY3V1bTxCUj4NCnVwIGFsbCB0
aGUgcGFja2V0cyBnb2luZyB0byB5b3VyIFVBLic8QlI+DQo8QlI+DQpJbiB0aGUgZXUgbW9yZSBv
ciBsZXNzIHRoZSBzYW1lIGFwcGxpZXMgd2l0aCByZWdhcmQgdG8gJ2ludGVybmV0JyB0cmFmZmlj
LiBJbiBhZGRpdGlvbiBJU1BzIGFyZSBvYmxpZ2F0ZWQgdG8gc3RvcmUgdXNhZ2UgaW5mb3JtYXRp
b24gdW5kZXIgdGhlIExJIHJlZ2ltZSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBmb3IgYWJvdXQgYSB5ZWFyIG9yIHNvLiBIb3dldmVyLCBzb21lIGdpdmVy
bm1lbnRzIGFuZCBMRUFzIHdhbnQgdGhlIHNhbWUgTEkgZmFjaWxpdGllcyBhcyBhcmUgYXZhaWxh
YmxlIGF0IHRoZSBQU1ROIChURE0pLiBUaGlzIGluY2x1ZGVzIHJlYWwtdGltZSBmZWVkcyBvZiBj
b252ZXJzYXRpb25zIG9ic2N1cmVkIGZyb20gYm9odCB0aGUgY2FsbGVkIHBhcnR5IGFuZCBjYWxs
aW5nIHBhcnRpZXMuIEluIGFkZGl0aW9uIExJIHRhcHMgbXVzdCBub3QgYmUgdmlzaWJsZSBmb3Ig
bmV0d29yayBlbmdpbmVlcnMsIG9ubHkgZm9yIGEgc2VsZWN0IHF1YWxpZmllZCBmZXcgYXJlIGFs
bG93ZWQgdG8ga25vdy4gVGhpcyBpcyBob3dldmVyIGFuIGltcGxlbWVudGF0aW9uIGlzdWUsIG5v
dCBhIHRlY2hub2xvZ3kgb3Igc3RhbmRhcmRzIGlzc3VlLiBwMnBzaXAgbWFrZSBzb21lIG9mIHRo
aXMgb2Jzb2xldGUuPEJSPg0KPEJSPg0KQ29saW48QlI+DQo8QlI+DQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLTxCUj4NCkZyb206ICZxdW90O0RhbGUuV29ybGV5QGNvbWNhc3QubmV0JnF1b3Q7
ICZsdDtEYWxlLldvcmxleUBjb21jYXN0Lm5ldCZndDs8QlI+DQpUbzogJnF1b3Q7c2lwcGluZ0Bp
ZXRmLm9yZyZxdW90OyAmbHQ7c2lwcGluZ0BpZXRmLm9yZyZndDs8QlI+DQpTZW50OiAyLTQtMDcg
MDU6NTA8QlI+DQpTdWJqZWN0OiBSZTogW1NpcHBpbmddIFNlcnZpY2UgSWRlbnRpZmljYXRpb24g
aW4gU0lQPEJSPg0KPEJSPg0KJm5ic3A7Jm5ic3A7IEZyb206ICZxdW90O0plcm9lbiB2YW4gQmVt
bWVsJnF1b3Q7ICZsdDtqYmVtbWVsQHpvbm5ldC5ubCZndDs8QlI+DQo8QlI+DQombmJzcDsmbmJz
cDsgSWYgSSB1bmRlcnN0YW5kIHRoZSAmcXVvdDtpbiB0aGUgVUEmcXVvdDsgc2VydmljZSBtb2Rl
bCwgdGhlIHJvbGUgb2YgdGhlIG9wZXJhdG9yPEJSPg0KJm5ic3A7Jm5ic3A7IHdvdWxkIGJlIHRv
IGhvc3Qgb25seSBhIFNJUCBwcm94eSBzZXJ2aWNlPyBJbiB0b2RheSdzIHJlZ3VsYXRvcnkgc3lz
dGVtczxCUj4NCiZuYnNwOyZuYnNwOyBzdWNoIGEgbW9kZWwgd291bGQgbm90IHdvcmssIGJlY2F1
c2Ugb2YgcmVxdWlyZW1lbnRzIG9uIGxlZ2FsIGludGVyY2VwdDxCUj4NCiZuYnNwOyZuYnNwOyAo
YW1vbmdzdCBvdGhlcnMpLiBJbiBvcmRlciB0byBmdWxmaWxsIHN1Y2ggcmVxdWlyZW1lbnRzLCB0
ZWxjbydzIGhhdmUgbm88QlI+DQombmJzcDsmbmJzcDsgY2hvaWNlIGJ1dCB0byBkZXBsb3kgYW4g
aW5mcmFzdHJ1Y3R1cmUgdGhhdCBwcm92aWRlcyB0aGUgbmVjZXNzYXJ5IGNvbnRyb2wuPEJSPg0K
PEJSPg0KTXkgaW1wcmVzc2lvbiBpcyB0aGF0IGluIHRoZSBVUywgdGhlIGdvdmVybm1lbnQgYWdl
bmNpZXMganVzdCB2YWN1dW08QlI+DQp1cCBhbGwgdGhlIHBhY2tldHMgZ29pbmcgdG8geW91ciBV
QS48QlI+DQo8QlI+DQpEYWxlPEJSPg0KPEJSPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX188QlI+DQpTaXBwaW5nIG1haWxpbmcgbGlzdCZuYnNwOyA8QSBI
UkVGPSJodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXBwaW5nIj5odHRw
czovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXBwaW5nPC9BPjxCUj4NClRoaXMg
bGlzdCBpcyBmb3IgTkVXIGRldmVsb3BtZW50IG9mIHRoZSBhcHBsaWNhdGlvbiBvZiBTSVA8QlI+
DQpVc2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJpYS5lZHUgZm9yIHF1ZXN0aW9ucyBvbiBj
dXJyZW50IHNpcDxCUj4NClVzZSBzaXBAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb2Yg
Y29yZSBTSVA8QlI+DQo8L0ZPTlQ+DQo8L1A+DQoNCjwvQk9EWT4NCjwvSFRNTD4=

------_=_NextPart_001_01C7767B.8BD6CB55--


--===============1072215938==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1072215938==--




From sipping-bounces@ietf.org Wed Apr 04 01:41:46 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYyE3-00049P-9h; Wed, 04 Apr 2007 01:40:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYyE1-00048r-6y; Wed, 04 Apr 2007 01:40:05 -0400
Received: from smtpscan-nl3.aots.nl ([145.7.191.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYyDz-0001Fa-4D; Wed, 04 Apr 2007 01:40:05 -0400
Received: from smtpscan-nl3.aots.nl (localhost [127.0.0.1])
	by localhost.aots.nl (Postfix) with ESMTP id BD8B550E;
	Wed,  4 Apr 2007 07:39:54 +0200 (MEST)
Received: from sat-relay1.telecom.ptt.nl (relay3.kpn-telecom.nl [145.7.200.29])
	by smtpscan-nl3.aots.nl (Postfix) with ESMTP id 7A4CA51C;
	Wed,  4 Apr 2007 07:39:54 +0200 (MEST)
Received: from KKWNLEX010.kpnnl.local (kkwnlex010.kpnnl.local [145.7.180.33])
	by sat-relay1.telecom.ptt.nl (8.11.6p2-20030924/8.11.6) with ESMTP
	id l345drT06556; Wed, 4 Apr 2007 07:39:53 +0200
Received: from KKWNLEX181.kpnnl.local ([172.23.222.150]) by
	KKWNLEX010.kpnnl.local with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 4 Apr 2007 07:39:00 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Wed, 4 Apr 2007 07:37:57 +0200
Message-ID: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Thread-Index: Acd1fDvzIhowLornTwyehPLXZ9zr5AA/ypd/
From: <colin.pons@kpn.com>
To: <pkyzivat@cisco.com>, <hsinnrei@adobe.com>
X-OriginalArrivalTime: 04 Apr 2007 05:39:00.0578 (UTC)
	FILETIME=[8C08A420:01C7767B]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 23336e92cd9b2f166f17126afcdd84ec
Cc: sipping@ietf.org, p2prg@ietf.org, oran@cisco.com, p2psip@ietf.org,
	mhammer@cisco.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0100755479=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0100755479==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7SPg0KTXkgaW1wcmVzc2lvbiBpcyB0aGF0IGluIHRoZSBVUywgdGhlIGdvdmVybm1lbnQgYWdl
bmNpZXMganVzdCB2YWN1dW08QlI+DQp1cCBhbGwgdGhlIHBhY2tldHMgZ29pbmcgdG8geW91ciBV
QS48QlI+DQo8QlI+DQpEYWxlPEJSPg0KPEJSPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX188QlI+DQpTaXBwaW5nIG1haWxpbmcgbGlzdCZuYnNwOyA8QSBI
UkVGPSJodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXBwaW5nIj5odHRw
czovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXBwaW5nPC9BPjxCUj4NClRoaXMg
bGlzdCBpcyBmb3IgTkVXIGRldmVsb3BtZW50IG9mIHRoZSBhcHBsaWNhdGlvbiBvZiBTSVA8QlI+
DQpVc2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJpYS5lZHUgZm9yIHF1ZXN0aW9ucyBvbiBj
dXJyZW50IHNpcDxCUj4NClVzZSBzaXBAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb2Yg
Y29yZSBTSVA8QlI+DQo8L0ZPTlQ+DQo8L1A+DQoNCjwvQk9EWT4NCjwvSFRNTD4=

------_=_NextPart_001_01C7767B.8BD6CB55--


--===============1072215938==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1072215938==--




From sipping-bounces@ietf.org Wed Apr 04 01:41:46 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYyE3-00049P-9h; Wed, 04 Apr 2007 01:40:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYyE1-00048r-6y; Wed, 04 Apr 2007 01:40:05 -0400
Received: from smtpscan-nl3.aots.nl ([145.7.191.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYyDz-0001Fa-4D; Wed, 04 Apr 2007 01:40:05 -0400
Received: from smtpscan-nl3.aots.nl (localhost [127.0.0.1])
	by localhost.aots.nl (Postfix) with ESMTP id BD8B550E;
	Wed,  4 Apr 2007 07:39:54 +0200 (MEST)
Received: from sat-relay1.telecom.ptt.nl (relay3.kpn-telecom.nl [145.7.200.29])
	by smtpscan-nl3.aots.nl (Postfix) with ESMTP id 7A4CA51C;
	Wed,  4 Apr 2007 07:39:54 +0200 (MEST)
Received: from KKWNLEX010.kpnnl.local (kkwnlex010.kpnnl.local [145.7.180.33])
	by sat-relay1.telecom.ptt.nl (8.11.6p2-20030924/8.11.6) with ESMTP
	id l345drT06556; Wed, 4 Apr 2007 07:39:53 +0200
Received: from KKWNLEX181.kpnnl.local ([172.23.222.150]) by
	KKWNLEX010.kpnnl.local with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 4 Apr 2007 07:39:00 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Wed, 4 Apr 2007 07:37:57 +0200
Message-ID: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Thread-Index: Acd1fDvzIhowLornTwyehPLXZ9zr5AA/ypd/
From: <colin.pons@kpn.com>
To: <pkyzivat@cisco.com>, <hsinnrei@adobe.com>
X-OriginalArrivalTime: 04 Apr 2007 05:39:00.0578 (UTC)
	FILETIME=[8C08A420:01C7767B]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 23336e92cd9b2f166f17126afcdd84ec
Cc: sipping@ietf.org, p2prg@ietf.org, oran@cisco.com, p2psip@ietf.org,
	mhammer@cisco.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0100755479=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0100755479==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7767B.8BBEF331"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7767B.8BBEF331
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGVucnksDQoNCkkgbGlrZSB5b3VyIGlkZWEgb2YgZGVwbG95aW5nIHNpcCBwZWVycyBpbiBlZGdl
IGRldmljZXMuIEhvd2V2ZXIsIGFzIGFuIGVtcGxveWVlIG9mIGEgY2FycmllciBJIHdvdWxkIGxp
a2UgdG8gc2VlIGhvdyBhIGNhcnJpZXIgaXMgYWJsZSB0byBwcm92aWRlIHNlcnZpY2UgYXN1cmFu
Y2UgdG8gYmUgYWJsZSB0byBwcm92aWRlIGNvbXBsaWFudCBoYW5kbGluZy4gTWFueSBvZiBvdXIg
Y3VzdG9tZXJzIGRvIG5vdCB1bmRlcnN0YW5kIGhvdyB0byBpbnN0YWxsIHRoZXNlIGdhdGV3YXlz
IHRoZW1zZWx2ZXMsIGxldCBhbG9uZSBob3cgdG8gdHJvdWJsZXNob290Lg0KDQpUaGlzIGlzIGV2
ZW4gbW9yZSBpbXBvcnRhbnQgZm9yIGVudGVycHJpc2VzLCB3aGljaCBvZnRlbiAgaW5zaXN0IG9u
IFNMQXMgd2hpY2ggaW5jbHVkZSB0cm91Ymxlc2hvb3QgcmVzb2x1dGlvbiBsaW1pdHMuDQoNCi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiAiUGF1bCBLeXppdmF0IiA8cGt5eml2YXRA
Y2lzY28uY29tPg0KVG86ICJIZW5yeSBTaW5ucmVpY2giIDxoc2lubnJlaUBhZG9iZS5jb20+DQpD
YzogIlAyUFNJUCBNYWlsaW5nIExpc3QiIDxwMnBzaXBAaWV0Zi5vcmc+OyAiTWljaGFlbCBIYW1t
ZXIgKG1oYW1tZXIpIiA8bWhhbW1lckBjaXNjby5jb20+OyAiRGF2aWQgUiBPcmFuIiA8b3JhbkBj
aXNjby5jb20+OyAicDJwcmdAaWV0Zi5vcmciIDxwMnByZ0BpZXRmLm9yZz47ICJzaXBwaW5nQGll
dGYub3JnIiA8c2lwcGluZ0BpZXRmLm9yZz4NClNlbnQ6IDMtNC0wNyAwMToxMQ0KU3ViamVjdDog
W1AyUFNJUF0gUmU6IFtQMlByZ10gUkU6IFtTaXBwaW5nXSBTaW1wbGUgU0lQIHVzYWdlIHNjZW5h
cmlvDQoNCg0KDQpIZW5yeSBTaW5ucmVpY2ggd3JvdGU6DQo+IFBhdWwsDQo+IA0KPj4gSSBtb3Jl
IG9yIGxlc3MgYWdyZWUgd2l0aCB0aGUgZmluYWwgY29uY2x1c2lvbiBiZWxvdy4NCj4gDQo+IFRo
aXMgaXMgZ29vZCBzdGFydGluZyBwb2ludCB0byBkaXNjdXNzIHNvbWUgdXNhZ2Ugc2NlbmFyaW9z
Lg0KPiANCj4gUHV0dGluZyBvbiBteSBmb3JtZXIgaGF0IGFzIGFuIGVtcGxveWVlIGZvciBhIGNh
cnJpZXIsIEkgY2Fubm90IG92ZXJsb29rDQo+IHRoZSBmb2xsb3dpbmc6DQo+IA0KPiBQMlAgU0lQ
IGltcGxlbWVudGVkIGNvcnJlY3RseSBpbiB0aGUgcmVzaWRlbnRpYWwgYWNjZXNzIGJveCBvciBj
YWJsZQ0KPiBzZXQtdG9wIGJveCBpbmRlZWQgaXMgYSBnb29kIG9yIGJldHRlciByZXBsYWNlbWVu
dCBmb3IgdGhlIGVudGlyZSBWb0lQDQo+IG5ldHdvcmsgaW5mcmFzdHJ1Y3R1cmUgKGNvc3QsIG9w
ZXJhdGlvbnMsIG5ldyBzZXJ2aWNlcywgZXRjKS4gDQo+IEludGVncmF0ZWQgYWNjZXNzIGRldmlj
ZXMgZm9yIHRoZSBlbnRlcnByaXNlIGNhbiBwcm9iYWJseSBwbGF5IGEgc2ltaWxhcg0KPiByb2xl
LCBub3QgdG8gbWVudGlvbiBleGlzdGluZyBQMlAgUEJYIHByb2R1Y3RzIChwbGVhc2UgcmVmZXIg
dG8gYWxsIHRoZQ0KPiBhZHZhbnRhZ2VzIG9mIFAyUCB0aGF0IG5lZWQgbm90IHJlcGVhdGVkIGhl
cmUpLg0KPiANCj4gV2hhdCBkbyBwZW9wbGUgdGhpbmsgb2YgdGhlc2UgdGhyZWUgdXNhZ2Ugc2Nl
bmFyaW9zIGZvciBQMlAgU0lQOg0KPiAtIFNJUCBwZWVyIGluIHRoZSBEU0wgYWNjZXNzIGRldmlj
ZSwNCj4gLSBTSVAgcGVlciBpbiB0aGUgY2FibGUgYWNjZXNzIGRldmljZSwNCg0KVGhlc2Ugc2Vl
bSBxdWl0ZSByZWFzb25hYmxlLCBhc3N1bWluZyB0aGF0IGEgZGV2aWNlIGNvbm5lY3RlZCBhdCB0
aGlzIA0KcG9pbnQgaXMgYWJsZSB0byBmdW5jdGlvbiBwcm9wZXJseSBhcyBhIHBlZXIuIChJIGhh
dmVuJ3QgYmVlbiBmb2xsb3dpbmcgDQp3aGF0IHRoZSBhc3N1bXB0aW9ucyBhcmUgYWJvdXQgcmVx
dWlyZWQgbmV0d29yayBjYXBhYmlsaXRpZXMgb2YgcGVlcnMuKQ0KDQo+IC0gU0lQIHBlZXIgaW4g
ZW50ZXJwcmlzZSBuZXR3b3JrIGludGVncmF0ZWQgYWNjZXNzIGRldmljZSAoSUFEKS4NCg0KSSB0
aGluayB0aGlzIGRlcGVuZHMgZ3JlYXRseSBvbiB3aGF0IGV4cGVjdGF0aW9ucyAvIGNvbnRyYWN0
dWFsIA0KZ3VhcmFudGVlcyB0aGUgZW50ZXJwcmlzZSBoYXMuIEl0cyB1bmNsZWFyIHRvIG1lIHdo
YXQgZ3VhcmFudGVlcyBjYW4gYmUgDQptYWRlIGFib3V0IGEgUDJQU0lQIG5ldHdvcmsgd2lsbCBi
ZSBhYmxlIHRvIG1ha2UsIGFuZCBpdHMgdW5jbGVhciB3aGF0IA0Ka2luZCBvZiBpbmZyYXN0cnVj
dHVyZSB3b3VsZCBiZSBpbnN0YWxsZWQgYnkvZm9yIHNvbWVvbmUgd2lsbGluZyB0byBtYWtlIA0K
Z3VhcmFudGVlcy4NCg0KCVBhdWwNCg0KPiBOb3RlIHRoYXQgdGhlc2UgZXhhbXBsZXMgaW1wbHkg
dmVyeSBsb3cgY2h1cm4gZm9yIHRoZSBwZWVycyBhbmQgYWRkIHRoZQ0KPiBkYXRhIHJldGVudGlv
biByZXNpbGllbmNlIG9mIFAyUCAoZ2VvZ3JhcGhpYyBkaXZlcnNpdHkgaXMgbmF0aXZlIGFuZA0K
PiBtb2JpbGUsIGV0Yy4pLiBJbmNpZGVudGFsbHksIE5BVCB0cmF2ZXJzYWwgbWF5IGFsc28gbm90
IGJlIGEgcHJvYmxlbSwgb3INCj4gYXQgbGVhc3QgYW4gZWFzaWVyIHByb2JsZW0uDQo+IA0KPiBX
aGF0IGRvIHlvdSBhbGwgdGhpbms/DQo+IA0KPiBJIGhhdmUgdGFrZW4gdGhlIGxpYmVydHkgdG8g
Y29weSB0aGUgUDJQIFNJUCBsaXN0LCBzaW5jZSB0aGUgbG93IGNodXJuDQo+IHNjZW5hcmlvcyBh
cmUgb2YgaW50ZXJlc3QgZm9yIHRoZSBESFQgc2VsZWN0aW9uLiBPciBqdXN0IHBpY2sgdGhlIHNh
bWUNCj4gREhUIGZvciBhbGwgc2NlbmFyaW9zIGFueXdheT8gSSBkb24ndCB0aGluayBzby4NCj4g
DQo+IFRoYW5rcywgSGVucnkNCj4gDQo+IA0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
PiBGcm9tOiBQYXVsIEt5eml2YXQgW21haWx0bzpwa3l6aXZhdEBjaXNjby5jb21dIA767B.8BBEF331"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7767B.8BBEF331
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGVucnksDQoNCkkgbGlrZSB5b3VyIGlkZWEgb2YgZGVwbG95aW5nIHNpcCBwZWVycyBpbiBlZGdl
IGRldmljZXMuIEhvd2V2ZXIsIGFzIGFuIGVtcGxveWVlIG9mIGEgY2FycmllciBJIHdvdWxkIGxp
a2UgdG8gc2VlIGhvdyBhIGNhcnJpZXIgaXMgYWJsZSB0byBwcm92aWRlIHNlcnZpY2UgYXN1cmFu
Y2UgdG8gYmUgYWJsZSB0byBwcm92aWRlIGNvbXBsaWFudCBoYW5kbGluZy4gTWFueSBvZiBvdXIg
Y3VzdG9tZXJzIGRvIG5vdCB1bmRlcnN0YW5kIGhvdyB0byBpbnN0YWxsIHRoZXNlIGdhdGV3YXlz
IHRoZW1zZWx2ZXMsIGxldCBhbG9uZSBob3cgdG8gdHJvdWJsZXNob290Lg0KDQpUaGlzIGlzIGV2
ZW4gbW9yZSBpbXBvcnRhbnQgZm9yIGVudGVycHJpc2VzLCB3aGljaCBvZnRlbiAgaW5zaXN0IG9u
IFNMQXMgd2hpY2ggaW5jbHVkZSB0cm91Ymxlc2hvb3QgcmVzb2x1dGlvbiBsaW1pdHMuDQoNCi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiAiUGF1bCBLeXppdmF0IiA8cGt5eml2YXRA
Y2lzY28uY29tPg0KVG86ICJIZW5yeSBTaW5ucmVpY2giIDxoc2lubnJlaUBhZG9iZS5jb20+DQpD
YzogIlAyUFNJUCBNYWlsaW5nIExpc3QiIDxwMnBzaXBAaWV0Zi5vcmc+OyAiTWljaGFlbCBIYW1t
ZXIgKG1oYW1tZXIpIiA8bWhhbW1lckBjaXNjby5jb20+OyAiRGF2aWQgUiBPcmFuIiA8b3JhbkBj
aXNjby5jb20+OyAicDJwcmdAaWV0Zi5vcmciIDxwMnByZ0BpZXRmLm9yZz47ICJzaXBwaW5nQGll
dGYub3JnIiA8c2lwcGluZ0BpZXRmLm9yZz4NClNlbnQ6IDMtNC0wNyAwMToxMQ0KU3ViamVjdDog
W1AyUFNJUF0gUmU6IFtQMlByZ10gUkU6IFtTaXBwaW5nXSBTaW1wbGUgU0lQIHVzYWdlIHNjZW5h
cmlvDQoNCg0KDQpIZW5yeSBTaW5ucmVpY2ggd3JvdGU6DQo+IFBhdWwsDQo+IA0KPj4gSSBtb3Jl
IG9yIGxlc3MgYWdyZWUgd2l0aCB0aGUgZmluYWwgY29uY2x1c2lvbiBiZWxvdy4NCj4gDQo+IFRo
aXMgaXMgZ29vZCBzdGFydGluZyBwb2ludCB0byBkaXNjdXNzIHNvbWUgdXNhZ2Ugc2NlbmFyaW9z
Lg0KPiANCj4gUHV0dGluZyBvbiBteSBmb3JtZXIgaGF0IGFzIGFuIGVtcGxveWVlIGZvciBhIGNh
cnJpZXIsIEkgY2Fubm90IG92ZXJsb29rDQo+IHRoZSBmb2xsb3dpbmc6DQo+IA0KPiBQMlAgU0lQ
IGltcGxlbWVudGVkIGNvcnJlY3RseSBpbiB0aGUgcmVzaWRlbnRpYWwgYWNjZXNzIGJveCBvciBj
YWJsZQ0KPiBzZXQtdG9wIGJveCBpbmRlZWQgaXMgYSBnb29kIG9yIGJldHRlciByZXBsYWNlbWVu
dCBmb3IgdGhlIGVudGlyZSBWb0lQDQo+IG5ldHdvcmsgaW5mcmFzdHJ1Y3R1cmUgKGNvc3QsIG9w
ZXJhdGlvbnMsIG5ldyBzZXJ2aWNlcywgZXRjKS4gDQo+IEludGVncmF0ZWQgYWNjZXNzIGRldmlj
ZXMgZm9yIHRoZSBlbnRlcnByaXNlIGNhbiBwcm9iYWJseSBwbGF5IGEgc2ltaWxhcg0KPiByb2xl
LCBub3QgdG8gbWVudGlvbiBleGlzdGluZyBQMlAgUEJYIHByb2R1Y3RzIChwbGVhc2UgcmVmZXIg
dG8gYWxsIHRoZQ0KPiBhZHZhbnRhZ2VzIG9mIFAyUCB0aGF0IG5lZWQgbm90IHJlcGVhdGVkIGhl
cmUpLg0KPiANCj4gV2hhdCBkbyBwZW9wbGUgdGhpbmsgb2YgdGhlc2UgdGhyZWUgdXNhZ2Ugc2Nl
bmFyaW9zIGZvciBQMlAgU0lQOg0KPiAtIFNJUCBwZWVyIGluIHRoZSBEU0wgYWNjZXNzIGRldmlj
ZSwNCj4gLSBTSVAgcGVlciBpbiB0aGUgY2FibGUgYWNjZXNzIGRldmljZSwNCg0KVGhlc2Ugc2Vl
bSBxdWl0ZSByZWFzb25hYmxlLCBhc3N1bWluZyB0aGF0IGEgZGV2aWNlIGNvbm5lY3RlZCBhdCB0
aGlzIA0KcG9pbnQgaXMgYWJsZSB0byBmdW5jdGlvbiBwcm9wZXJseSBhcyBhIHBlZXIuIChJIGhh
dmVuJ3QgYmVlbiBmb2xsb3dpbmcgDQp3aGF0IHRoZSBhc3N1bXB0aW9ucyBhcmUgYWJvdXQgcmVx
dWlyZWQgbmV0d29yayBjYXBhYmlsaXRpZXMgb2YgcGVlcnMuKQ0KDQo+IC0gU0lQIHBlZXIgaW4g
ZW50ZXJwcmlzZSBuZXR3b3JrIGludGVncmF0ZWQgYWNjZXNzIGRldmljZSAoSUFEKS4NCg0KSSB0
aGluayB0aGlzIGRlcGVuZHMgZ3JlYXRseSBvbiB3aGF0IGV4cGVjdGF0aW9ucyAvIGNvbnRyYWN0
dWFsIA0KZ3VhcmFudGVlcyB0aGUgZW50ZXJwcmlzZSBoYXMuIEl0cyB1bmNsZWFyIHRvIG1lIHdo
YXQgZ3VhcmFudGVlcyBjYW4gYmUgDQptYWRlIGFib3V0IGEgUDJQU0lQIG5ldHdvcmsgd2lsbCBi
ZSBhYmxlIHRvIG1ha2UsIGFuZCBpdHMgdW5jbGVhciB3aGF0IA0Ka2luZCBvZiBpbmZyYXN0cnVj
dHVyZSB3b3VsZCBiZSBpbnN0YWxsZWQgYnkvZm9yIHNvbWVvbmUgd2lsbGluZyB0byBtYWtlIA0K
Z3VhcmFudGVlcy4NCg0KCVBhdWwNCg0KPiBOb3RlIHRoYXQgdGhlc2UgZXhhbXBsZXMgaW1wbHkg
dmVyeSBsb3cgY2h1cm4gZm9yIHRoZSBwZWVycyBhbmQgYWRkIHRoZQ0KPiBkYXRhIHJldGVudGlv
biByZXNpbGllbmNlIG9mIFAyUCAoZ2VvZ3JhcGhpYyBkaXZlcnNpdHkgaXMgbmF0aXZlIGFuZA0K
PiBtb2JpbGUsIGV0Yy4pLiBJbmNpZGVudGFsbHksIE5BVCB0cmF2ZXJzYWwgbWF5IGFsc28gbm90
IGJlIGEgcHJvYmxlbSwgb3INCj4gYXQgbGVhc3QgYW4gZWFzaWVyIHByb2JsZW0uDQo+IA0KPiBX
aGF0IGRvIHlvdSBhbGwgdGhpbms/DQo+IA0KPiBJIGhhdmUgdGFrZW4gdGhlIGxpYmVydHkgdG8g
Y29weSB0aGUgUDJQIFNJUCBsaXN0LCBzaW5jZSB0aGUgbG93IGNodXJuDQo+IHNjZW5hcmlvcyBh
cmUgb2YgaW50ZXJlc3QgZm9yIHRoZSBESFQgc2VsZWN0aW9uLiBPciBqdXN0IHBpY2sgdGhlIHNh
bWUNCj4gREhUIGZvciBhbGwgc2NlbmFyaW9zIGFueXdheT8gSSBkb24ndCB0aGluayBzby4NCj4g
DQo+IFRoYW5rcywgSGVucnkNCj4gDQo+IA0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
PiBGcm9tOiBQYXVsIEt5eml2YXQgW21haWx0bzpwa3l6aXZhdEBjaXNjby5jb21dIA0KPiBTZW50
OiBGcmlkYXksIE1hcmNoIDMwLCAyMDA3IDY6MzEgUE0NCj4gVG86IEV1bnNvbyBTaGltDQo+IENj
OiBIZW5yeSBTaW5ucmVpY2g7IE1pY2hhZWwgSGFtbWVyIChtaGFtbWVyKTsgRGF2aWQgUiBPcmFu
Ow0KPiBwMnByZ0BpZXRmLm9yZzsgc2lwcGluZ0BpZXRmLm9yZzsgemh1eGlhbg0KPiBTdWJqZWN0
OiBSZTogW1AyUHJnXSBSRTogW1NpcHBpbmddIFNpbXBsZSBTSVAgdXNhZ2Ugc2NlbmFyaW8NCj4g
DQo+IEkgbW9yZSBvciBsZXNzIGFncmVlIHdpdGggdGhlIGZpbmFsIGNvbmNsdXNpb24gYmVsb3cu
DQo+IA0KPiBNeSBtYWluIHBvaW50IGhlcmUgaXMgdGhhdCBQMlAgYW5kIEMvUyBuZWVkIG5vdCBi
ZSBlbmVtaWVzLiBOb3IgaXMgYSANCj4gdG90YWwgQy9TIHN5c3RlbSBuZWNlc3NhcmlseSBldmls
LiBXaGF0IGlzIG1vc3QgZXZpbCBpcyAqYnVuZGxpbmcqIG9mIA0KPiBzZXJ2aWNlcyB0aGF0IHBy
ZXZlbnRzIGZyZWVkb20gb2YgY2hvaWNlLg0KPiANCj4gSSB0aGluayBJIHdvdWxkIGJlIHF1aXRl
IGhhcHB5IHdpdGggYSBTUCB0aGF0IHByb3ZpZGVzIGEgcmVnaXN0cmFyL3Byb3h5DQo+IA0KPiBh
bmQgYWxsb3dzIG1lIHRvIHByb3ZpZGUgYWxsIG90aGVyIGZlYXR1cmVzIGFzIEkgc2VlIGZpdCAt
IGJ5IHRha2luZyANCj4gdGhlbSBhbGEgY2FydGUgZnJvbSB0aGUgU1AsIG9yIHN1YnNjcmliaW5n
IHRvIHRoZW0gZnJvbSBvbmUgb3IgbW9yZSANCj4gb3RoZXIgU1BzLCBvciBieSBwcm92aWRpbmcg
dGhlbSBteXNlbGYgdmlhIGFwcGxpYW5jZXMgSSBvd24uIElmIHRoYXQgDQo+IHJlZ2lzdHJhci9w
cm94eSB3YXMgcmVwbGFjZWQgYnkgYSBQMlAgc2lwIGNvbW11bml0eSwgdGhlIGRpZmZlcmVuY2Vz
LCBpZg0KPiANCj4gYW55LCB3b3VsZCBob3BlZnVsbHkgYmUgbW9yZSBhIGZ1bmN0aW9uIG9mIHRo
ZSBpbXBsZW1lbnRhdGlvbiBhbmQgdGhlIA0KPiBidXNpbmVzcyBtb2RlbHMgb2YgdGhvc2UgaW52
b2x2ZWQgdGhhbiB0aGUgYXJjaGl0ZWN0dXJlLg0KPiANCj4gKEkgZ2F0aGVyIHRoZSBnZW5lcmFs
IGFzc3VtcHRpb24gaXMgdGhhdCBhIFAyUCBzZXR1cCB3aWxsIGJlICpmcmVlKi4gQnV0DQo+IA0K
PiBJIGhhdmUgYSBoYXJkIHRpbWUgYmVsaWV2aW5nIHRoYXQuIElmIG1vc3Qgb2YgdGhlIHVzYWdl
IGlzIGJ5IG1vYmlsZSANCj4gZGV2aWNlcyB0aGF0IGNhbid0IGJlIHBlZXJzLCB0aGVuIHNvbWVi
b2R5IHdpbGwgaGF2ZSB0byBwYXkgZm9yIGVub3VnaCANCj4gcGVlcnMgdG8gc3VwcG9ydCB0aGVt
LiBJZiBpdCBpc24ndCBmcmVlLCB0aGVuIGhvdyBpcyBpdCBiZXR0ZXIgdGhhbiBhIA0KPiB3ZWxs
IGVuZ2luZWVyZWQgQy9TIHN5c3RlbT8pDQo+IA0KPiBTbyBJIHRoaW5rIHRoZSBrZXkgdGhpbmcg
aGVyZSBpcyB0aGF0IHNvbWUgZmVhdHVyZXMgd2lsbCByZXF1aXJlIGdldHRpbmcNCj4gDQo+IHNv
bWUgaGVscCBmcm9tIGFub3RoZXIgbm9kZS4gVGhlcmUgb3VnaHQgdG8gYmUgdGhlIG9wdGlvbiB0
byBwaWNrIGEgDQo+IGRpZmZlcmVudCBzb3VyY2UgZm9yIGVhY2ggaGVscGVyIHlvdSByZXF1aXJl
LCBhbmQgYW4gYWJpbGl0eSBmb3IgaXQgYWxsIA0KPiB0byBwbGF5IHRvZ2V0aGVyLg0KPiANCj4g
CVBhdWwNCj4gDQo+IEV1bnNvbyBTaGltIHdyb3RlOg0KPj4gUGxlYXNlIHNlZSBteSBpbmxpbmUg
Y29tbWVudC4NCj4+DQo+PiBPbiAzLzMwLzA3LCAqUGF1bCBLeXppdmF0KiA8cGt5eml2YXRAY2lz
Y28uY29tIA0KPj4gPG1haWx0bzpwa3l6aXZhdEBjaXNjby5jb20+PiB3cm90ZToNCj4+DQo+Pg0K
Pj4NCj4+ICAgICBIZW5yeSBTaW5ucmVpY2ggd3JvdGU6DQo+PiAgICAgID4gRGF2aWQgT3JhbiB3
cm90ZSAod2l0aCByZWdhcmQgdG8gdm9pY2UgbWFpbCk6DQo+PiAgICAgID4NCj4+ICAgICAgPj4g
SSdtIG5vdCBzYXlpbmcgdGhpcyBjYW4ndCBiZSBtYWRlIHRvIHdvcmssIG9ubHkgdGhhdCBpdCBp
c24ndA0KPj4gICAgICA+IGltbWVkaWF0ZWx5ID5vYnZpb3VzIHRoYXQgaXQgaGFzIGFkdmFudGFn
ZXMgb3ZlciBhIGNsYXNzaWMNCj4+ICAgICBhcHBsaWNhdGlvbg0KPj4gICAgICA+IHNlcnZlciA+
YXBwcm9hY2guDQo+PiAgICAgID4NCj4+ICAgICAgPiBUaGUgYW5zd2VyIGZvciBWTSBpcyAiaXQg
ZGVwZW5kcyI6DQo+PiAgICAgID4NCj4+DQo+Pg0KPj4gSSBhZ3JlZS4gSXQgcmVhbGx5IGRlcGVu
ZHMuIENlcnRhaW5seSB0aGVyZSBhcmUgdHJhZGVvZmZzLg0KPj4NCj4+ICAgICAgPiBUaGVyZSBh
cmUgc2V2ZXJhbCBjb21tZXJjaWFsIFAyUCBJUCBQQlggc29sdXRpb25zIHdpdGhvdXQgYW55DQo+
PiAgICAgc2VydmVyIGZvcg0KPj4gICAgICA+IFZNIG9yIGFueXRoaW5nIGVsc2UuIE5vIGRvdWJ0
IHRoZSBJVCBvcmdhbml6YXRpb24gYXBwcmVjaWF0ZXMNCj4ganVzdA0KPj4gICAgICA+IGhhdmlu
ZyB0byBwbHVnIGluIHRoZSBJUCBwaG9uZXMgYW5kIEdXWSB0byB0aGUgUFNUTiB3aXRob3V0IGFu
eQ0KPj4gICAgICA+IGNvbmZpZ3VyYXRpb24gZXZlciBmb3IgVk0gb3IgYW55IG90aGVyIFBCWCBm
ZWF0dXJlLg0KPj4NCj4+ICAgICBJIGRvbid0IHVuZGVyc3RhbmQuIEFyZSB5b3Ugc2F5aW5nIHRo
ZXkgZG9uJ3QgaGF2ZSBWTSwgb3IgdGhhdA0KPiB0aGV5DQo+PiAgICAgZG9uJ3QgaGF2ZSBhICpz
ZXJ2ZXIqIGZvciBWTT8NCj4+DQo+Pg0KPj4gSSBndWVzcyB0aGV5IGRvbid0IGhhdmUgYSAgKnNl
cnZlciogZm9yICBWTS4NCj4+DQo+PiAgICAgID4gRm9yIHB1YmxpYyBQMlAgU0lQIG5ldHdvcmtz
IHRoZXJlIGFyZSB0d28gbW9yZSBzY2VuYXJpb3Mgd2hlcmUNCj4gVk0gY2FuDQo+PiAgICAgID4g
cmVzaWRlIChhbmQgd2l0aG91dCBldmVyIHNwZW5kaW5nIG9uZSBjZW50IG9uIFZNIHNlcnZlcnMg
KyBJVA0KPj4gICAgIHN5c3RlbXMpOg0KPj4gICAgICA+DQo+PiAgICAgID4gLSBJbiBDYWJsZSBh
bmQgRFNMIHNlcnZpY2UgcHJvdmlkZXIgbmV0d29ya3M6IFRoZSByZXNpZGVudGlhbA0KPj4gICAg
IHJvdXRlciBjYW4NCj4+ICAgICAgPiBhY3QgYXMgYSB2b2ljZSByZWNvcmRlcg0KPj4NCj4+ICAg
ICBU0KPiBTZW50
OiBGcmlkYXksIE1hcmNoIDMwLCAyMDA3IDY6MzEgUE0NCj4gVG86IEV1bnNvbyBTaGltDQo+IENj
OiBIZW5yeSBTaW5ucmVpY2g7IE1pY2hhZWwgSGFtbWVyIChtaGFtbWVyKTsgRGF2aWQgUiBPcmFu
Ow0KPiBwMnByZ0BpZXRmLm9yZzsgc2lwcGluZ0BpZXRmLm9yZzsgemh1eGlhbg0KPiBTdWJqZWN0
OiBSZTogW1AyUHJnXSBSRTogW1NpcHBpbmddIFNpbXBsZSBTSVAgdXNhZ2Ugc2NlbmFyaW8NCj4g
DQo+IEkgbW9yZSBvciBsZXNzIGFncmVlIHdpdGggdGhlIGZpbmFsIGNvbmNsdXNpb24gYmVsb3cu
DQo+IA0KPiBNeSBtYWluIHBvaW50IGhlcmUgaXMgdGhhdCBQMlAgYW5kIEMvUyBuZWVkIG5vdCBi
ZSBlbmVtaWVzLiBOb3IgaXMgYSANCj4gdG90YWwgQy9TIHN5c3RlbSBuZWNlc3NhcmlseSBldmls
LiBXaGF0IGlzIG1vc3QgZXZpbCBpcyAqYnVuZGxpbmcqIG9mIA0KPiBzZXJ2aWNlcyB0aGF0IHBy
ZXZlbnRzIGZyZWVkb20gb2YgY2hvaWNlLg0KPiANCj4gSSB0aGluayBJIHdvdWxkIGJlIHF1aXRl
IGhhcHB5IHdpdGggYSBTUCB0aGF0IHByb3ZpZGVzIGEgcmVnaXN0cmFyL3Byb3h5DQo+IA0KPiBh
bmQgYWxsb3dzIG1lIHRvIHByb3ZpZGUgYWxsIG90aGVyIGZlYXR1cmVzIGFzIEkgc2VlIGZpdCAt
IGJ5IHRha2luZyANCj4gdGhlbSBhbGEgY2FydGUgZnJvbSB0aGUgU1AsIG9yIHN1YnNjcmliaW5n
IHRvIHRoZW0gZnJvbSBvbmUgb3IgbW9yZSANCj4gb3RoZXIgU1BzLCBvciBieSBwcm92aWRpbmcg
dGhlbSBteXNlbGYgdmlhIGFwcGxpYW5jZXMgSSBvd24uIElmIHRoYXQgDQo+IHJlZ2lzdHJhci9w
cm94eSB3YXMgcmVwbGFjZWQgYnkgYSBQMlAgc2lwIGNvbW11bml0eSwgdGhlIGRpZmZlcmVuY2Vz
LCBpZg0KPiANCj4gYW55LCB3b3VsZCBob3BlZnVsbHkgYmUgbW9yZSBhIGZ1bmN0aW9uIG9mIHRo
ZSBpbXBsZW1lbnRhdGlvbiBhbmQgdGhlIA0KPiBidXNpbmVzcyBtb2RlbHMgb2YgdGhvc2UgaW52
b2x2ZWQgdGhhbiB0aGUgYXJjaGl0ZWN0dXJlLg0KPiANCj4gKEkgZ2F0aGVyIHRoZSBnZW5lcmFs
IGFzc3VtcHRpb24gaXMgdGhhdCBhIFAyUCBzZXR1cCB3aWxsIGJlICpmcmVlKi4gQnV0DQo+IA0K
PiBJIGhhdmUgYSBoYXJkIHRpbWUgYmVsaWV2aW5nIHRoYXQuIElmIG1vc3Qgb2YgdGhlIHVzYWdl
IGlzIGJ5IG1vYmlsZSANCj4gZGV2aWNlcyB0aGF0IGNhbid0IGJlIHBlZXJzLCB0aGVuIHNvbWVi
b2R5IHdpbGwgaGF2ZSB0byBwYXkgZm9yIGVub3VnaCANCj4gcGVlcnMgdG8gc3VwcG9ydCB0aGVt
LiBJZiBpdCBpc24ndCBmcmVlLCB0aGVuIGhvdyBpcyBpdCBiZXR0ZXIgdGhhbiBhIA0KPiB3ZWxs
IGVuZ2luZWVyZWQgQy9TIHN5c3RlbT8pDQo+IA0KPiBTbyBJIHRoaW5rIHRoZSBrZXkgdGhpbmcg
aGVyZSBpcyB0aGF0IHNvbWUgZmVhdHVyZXMgd2lsbCByZXF1aXJlIGdldHRpbmcNCj4gDQo+IHNv
bWUgaGVscCBmcm9tIGFub3RoZXIgbm9kZS4gVGhlcmUgb3VnaHQgdG8gYmUgdGhlIG9wdGlvbiB0
byBwaWNrIGEgDQo+IGRpZmZlcmVudCBzb3VyY2UgZm9yIGVhY2ggaGVscGVyIHlvdSByZXF1aXJl
LCBhbmQgYW4gYWJpbGl0eSBmb3IgaXQgYWxsIA0KPiB0byBwbGF5IHRvZ2V0aGVyLg0KPiANCj4g
CVBhdWwNCj4gDQo+IEV1bnNvbyBTaGltIHdyb3RlOg0KPj4gUGxlYXNlIHNlZSBteSBpbmxpbmUg
Y29tbWVudC4NCj4+DQo+PiBPbiAzLzMwLzA3LCAqUGF1bCBLeXppdmF0KiA8cGt5eml2YXRAY2lz
Y28uY29tIA0KPj4gPG1haWx0bzpwa3l6aXZhdEBjaXNjby5jb20+PiB3cm90ZToNCj4+DQo+Pg0K
Pj4NCj4+ICAgICBIZW5yeSBTaW5ucmVpY2ggd3JvdGU6DQo+PiAgICAgID4gRGF2aWQgT3JhbiB3
cm90ZSAod2l0aCByZWdhcmQgdG8gdm9pY2UgbWFpbCk6DQo+PiAgICAgID4NCj4+ICAgICAgPj4g
SSdtIG5vdCBzYXlpbmcgdGhpcyBjYW4ndCBiZSBtYWRlIHRvIHdvcmssIG9ubHkgdGhhdCBpdCBp
c24ndA0KPj4gICAgICA+IGltbWVkaWF0ZWx5ID5vYnZpb3VzIHRoYXQgaXQgaGFzIGFkdmFudGFn
ZXMgb3ZlciBhIGNsYXNzaWMNCj4+ICAgICBhcHBsaWNhdGlvbg0KPj4gICAgICA+IHNlcnZlciA+
YXBwcm9hY2guDQo+PiAgICAgID4NCj4+ICAgICAgPiBUaGUgYW5zd2VyIGZvciBWTSBpcyAiaXQg
ZGVwZW5kcyI6DQo+PiAgICAgID4NCj4+DQo+Pg0KPj4gSSBhZ3JlZS4gSXQgcmVhbGx5IGRlcGVu
ZHMuIENlcnRhaW5seSB0aGVyZSBhcmUgdHJhZGVvZmZzLg0KPj4NCj4+ICAgICAgPiBUaGVyZSBh
cmUgc2V2ZXJhbCBjb21tZXJjaWFsIFAyUCBJUCBQQlggc29sdXRpb25zIHdpdGhvdXQgYW55DQo+
PiAgICAgc2VydmVyIGZvcg0KPj4gICAgICA+IFZNIG9yIGFueXRoaW5nIGVsc2UuIE5vIGRvdWJ0
IHRoZSBJVCBvcmdhbml6YXRpb24gYXBwcmVjaWF0ZXMNCj4ganVzdA0KPj4gICAgICA+IGhhdmlu
ZyB0byBwbHVnIGluIHRoZSBJUCBwaG9uZXMgYW5kIEdXWSB0byB0aGUgUFNUTiB3aXRob3V0IGFu
eQ0KPj4gICAgICA+IGNvbmZpZ3VyYXRpb24gZXZlciBmb3IgVk0gb3IgYW55IG90aGVyIFBCWCBm
ZWF0dXJlLg0KPj4NCj4+ICAgICBJIGRvbid0IHVuZGVyc3RhbmQuIEFyZSB5b3Ugc2F5aW5nIHRo
ZXkgZG9uJ3QgaGF2ZSBWTSwgb3IgdGhhdA0KPiB0aGV5DQo+PiAgICAgZG9uJ3QgaGF2ZSBhICpz
ZXJ2ZXIqIGZvciBWTT8NCj4+DQo+Pg0KPj4gSSBndWVzcyB0aGV5IGRvbid0IGhhdmUgYSAgKnNl
cnZlciogZm9yICBWTS4NCj4+DQo+PiAgICAgID4gRm9yIHB1YmxpYyBQMlAgU0lQIG5ldHdvcmtz
IHRoZXJlIGFyZSB0d28gbW9yZSBzY2VuYXJpb3Mgd2hlcmUNCj4gVk0gY2FuDQo+PiAgICAgID4g
cmVzaWRlIChhbmQgd2l0aG91dCBldmVyIHNwZW5kaW5nIG9uZSBjZW50IG9uIFZNIHNlcnZlcnMg
KyBJVA0KPj4gICAgIHN5c3RlbXMpOg0KPj4gICAgICA+DQo+PiAgICAgID4gLSBJbiBDYWJsZSBh
bmQgRFNMIHNlcnZpY2UgcHJvdmlkZXIgbmV0d29ya3M6IFRoZSByZXNpZGVudGlhbA0KPj4gICAg
IHJvdXRlciBjYW4NCj4+ICAgICAgPiBhY3QgYXMgYSB2b2ljZSByZWNvcmRlcg0KPj4NCj4+ICAg
ICBUaGF0IGlzIHNpbXBseSBhbiBleGFtcGxlIG9mIHRoZSB1c2VyIGhhdmluZyBhbiBhcHBsaWFu
Y2Ugb2YgaGlzDQo+IG93bg0KPj4gICAgIHRoYXQgcHJvdmlkZXMgVk0gc2VydmljZS4NCj4+DQo+
PiAgICAgID4gYW5kIFAyUCBjYW4gY292ZXIgdGhlIG5vdCB0b28gZnJlcXVlbnQgY2FzZXMsDQo+
PiAgICAgID4gd2hlcmUgdGhlIHJvdXRlciBpcyBub3QgaW4gb3BlcmF0aW9uLCBzbyB0aGUgZGF0
YSBpcyBiYWNrZWQgdXANCj4gaW4NCj4+ICAgICBvdGhlcg0KPj4gICAgICA+IHBlZXIgcmVzaWRl
bnRpYWwgZ2F0ZXdheXMgKGVuY3J5cHRlZCkuDQo+Pg0KPj4gICAgIEkgZ3Vlc3MgSSBqdXN0IG5l
ZWQgdG8gaGF2ZSBtb3JlIGluZm8gYWJvdXQgaG93IHRoaXMgd291bGQgd29yaw0KPiBiZWZvcmUg
SQ0KPj4gICAgIHdpbGwgYmUgY29udmluY2VkIGl0IGlzIGZlYXNpYmxlIGFuZCB0cnVzdHdvcnRo
eS4NCj4+DQo+Pg0KPj4gV2VsbCwgJ3RydXN0d29ydGh5JyBjb3VsZCBiZSAgY29uc2lkZXJlZCBp
biBtYW55IGFuZ2xlcy4NCj4+IElmIGl0IGlzIGFib3V0IHByaXZhY3kgb2YgdGhlIG1lc3NhZ2Us
IGEgcHVibGljIGtleSBiYXNlZCBlbmNyeXB0aW9uIA0KPj4gd291bGQgcHJvdmlkZSBhY2NlcHRh
YmxlIHByaXZhY3kuDQo+PiBJZiBpdCBpcyBhYm91dCByZWxpYWJpbGl0eSBvZiB0aGUgbWVzc2Fn
ZSBkZWxpdmVyeSwgd2VsbCwgYSBQMlAgYmFzZWQgDQo+PiBhc3luY2hyb25vdXMgbWVzc2FnZSBk
ZWxpdmVyeSAobGlrZSBWTSkgaXMgbW9zdCBsaWtlbHkgbGVzcyByZWxpYWJsZSANCj4+IHRoYW4g
YSB3ZWxsIG1hbmFnZWQgc2VydmVyIGJhc2VkIHN5c3RlbS4NCj4+IEhvd2V2ZXIsIG15IGV4cGVy
aWVuY2Ugd2l0aCBTa3lwZSdzIGFzeW5jaHJvbm91cyBtZXNzYWdlIGRlbGl2ZXJ5IHdhcyANCj4+
IG5vdCBiYWQuIEFjdHVhbGx5IEkgZG9uJ3Qgc2VlIGFueSBzaWduaWZpY2FudCBkaWZmZXJlbmNl
IGJldHdlZW4gaXQNCj4gYW5kIA0KPj4gbXkgY2VsbHVsYXIgc2VydmljZSBwcm92aWRlcidzIFZN
IHNlcnZpY2UuIDotKQ0KPj4gUmVsaWFiaWxpdHkgaXMgYWx3YXlzIGEgY2hhbGxlbmdlIGZvciBQ
MlAsIGZvciBzdXJlLiBCdXQsIEkgYmVsaWV2ZSBpdA0KPiANCj4+IGlzIGZlYXNpYmxlIHRvIGJ1
aWxkIGEgUDJQIHN5c3RlbSBmb3IgVk0gYWNjZXB0YWJsZSBmb3IgbWFueQ0KPiBzY2VuYXJpb3Mu
DQo+PiAgICAgID4gLSBJbiBtb2JpbGUgbmV0d29ya3M6IFRoZSBWTSBjYW4gcmVzaWRlIGluIHF1
aXRlIHN0YWJsZSBwZWVycw0KPj4gICAgIGluc2lkZSB0aGUNCj4+ICAgICAgPiB3aXJlbGVzcyBi
YXNlIHN0YXRpb24gbmV0d29yay4gVGhlIHBlZXJzIGluIHRoZSBiYXNlIHN0YXRpb24NCj4gbmV0
d29yaw0KPj4gICAgICA+IG5lZWQgbm8gY29uZmlndXJhdGlvbiwgZXRjLg0KPj4NCj4+ICAgICBJ
IGRvbid0IHVuZGVyc3RhbmQuIEkgZ3Vlc3MgdGhhdCBjb3VsZCBiZSB0cnVlIGlmIHRoZSBwZWVy
cyBhcmUNCj4gd2lsbGluZw0KPj4gICAgIHRvIHN0b3JlIGFuIGFyYml0cmFyeSBhbW91bnQgb2Yg
Vk0gaW5kZWZpbml0ZWx5IGZvciBhbnlib2R5LiBJcw0KPiB0aGF0DQo+PiAgICAgYmVsaWV2YWJs
ZT8NCj4+DQo+Pg0KPj4gSXQgZGVwZW5kcy4NCj4+IEluIGEgdmVyeSBuaWNlIGVudmlyb25tZW50
IHdoZXJlIGFsbCB0aGUgcGVlcnMgYXJlIHdpbGxpbmcgdG8NCj4gY29vcGVyYXRlIA0KPj4gYXQg
dGhlaXIgYmVzdCwgdGhlIHBlZXJzIHdpbGwgc3RvcmUgYXMgbXVjaCBhcyB0aGV5IGNhbi4gSW4g
YSB0b3VnaCANCj4+IGVudmlyb25tZW50LCB0aGUgc2l0dWF0aW9uIHdpbGwgYmUgZGlmZmVyZW50
Lg0KPj4NCj4+ICAgICBUaGlzIHNlZW1zIHRvIHRyYW5zbGF0ZSB0byBhIG1vZGVsIHdoZXJlIGl0
IGlzIGFzc3VtZWQgdGhhdCB0aG9zZQ0KPiBub2Rlcw0KPj4gICAgIHRoYXQgYXJlIG9uIG1vc3Qg
b2YgdGhlIHRpbWUgd2lsbCBiZSB3aWxsaW5nIHRvIHByb3ZpZGUgVk0gc3RvcmFnZQ0KPiBmb3IN
Cj4+ICAgICB0aG9zZSBub2RlcyB0aGF0IGFyZW4ndCBvbiBtb3N0IG9mIHRoZSB0aW1lLg0KPj4N
Cj4+DQo+PiBUaGlzIGlzIGFnYWluIHJlbGF0ZWQgdG8gcmVsaWFiaWxpdHkgb2YgUDJQIHN5c3Rl
bXMgb3IgdG9waWNzIGxpa2UNCj4gZnJlZSANCj4+IHJpZGVycyBhbmQgcmVwdXRhdGlvbi4NCj4+
IEEgUDJQIHN5c3RlbSBpcyBhIGNvbW11bml0eSBvciBzb2NpZXR5LiBUbyBiZSBzaW1wbGUsIGlm
IG1hbnkgb2YgdGhlIA0KPj4gbWVtYmVycyBhcmUgYmFkLCB0aGUgY29tbXVuaXR5IHdvbid0IHdv
cmsgd2VsbC4gSWYgdGhlIG1ham9yaXR5IG9mIHRoZQ0KPiANCj4+IG1lbWJlcnMgYXJlIGdvb2Qs
IHRoZSBjb21tdW5pdHkgd2lsbCB3b3JrIHdlbGwgb3IgcmVhc29uYWJseS4NCj4+DQo+PiAgICAg
ID4gQWRkIHRvIHRoaXMgdGhlIGNvbmZlcmVuY2luZyBjYXBhYmlsaXR5IGNvbWluZyBmcm9tIHAy
cA0KPiBhcHBsaWNhdGlvbg0KPj4gICAgICA+IGxheWVyIG11bHRpY2FzdCwgdGhlIFNJUCBlMmUg
Y29udHJvbCBjYXBhYmlsaXRpZXMgKGZvciBzdWNoIGFzDQo+PiAgICAgID4gYXV0by1hdHRlbmRh
bnQsIGFnZW50IHdvcmtzdGF0aW9uLCBldGMuKSBhbmQgb25lIGhhcyB0byB3b25kZXINCj4gd2h5
IElUDQo+PiAgICAgID4gbmV0d29ya3MsIHB1YmxpYyBWb0lQIG5ldHdvcmtzIGFuZCBlbmQgdXNl
cnMgc2hvdWxkIHN1cHBvcnQgdGhlDQo+IGh1Z2UNCj4+ICAgICAgPiBjb3N0IG9mIGhhbmQgZW5n
aW5lZXJpbmcsIHRlc3RpbmcsIG1vbml0b3JpbmcsIG1haW50YWluaW5nDQo+IHNlcnZlcg0KPj4g
ICAgIGJhc2VkDQo+PiAgICAgID4gVm9JUCBuZXR3b3Jrcy4gUDJQIHNlbGYgY29uZmlndXJhdGlv
biBpcyBub3RoaW5nIGxlc3MgdGhhdA0KPiBhdXRvbWF0aW9uDQo+PiAgICAgID4gYXBwbGllZCB0
byBWb0lQLCBwbHVzIHRoZSBzaGlmdGluZyBvZiBjb21wdXRpbmcgdG8gdGhlDQo+IGVuZHBvaW50
cywNCj4+ICAgICB3aGVyZQ0KPj4gICAgICA+IHRoZXJlIGlzIGFuIGFidW5kYW5jZSBvZiB1bnVz
ZWQgQ1BVLCBzdG9yYWdaGF0IGlzIHNpbXBseSBhbiBleGFtcGxlIG9mIHRoZSB1c2VyIGhhdmluZyBhbiBhcHBsaWFu
Y2Ugb2YgaGlzDQo+IG93bg0KPj4gICAgIHRoYXQgcHJvdmlkZXMgVk0gc2VydmljZS4NCj4+DQo+
PiAgICAgID4gYW5kIFAyUCBjYW4gY292ZXIgdGhlIG5vdCB0b28gZnJlcXVlbnQgY2FzZXMsDQo+
PiAgICAgID4gd2hlcmUgdGhlIHJvdXRlciBpcyBub3QgaW4gb3BlcmF0aW9uLCBzbyB0aGUgZGF0
YSBpcyBiYWNrZWQgdXANCj4gaW4NCj4+ICAgICBvdGhlcg0KPj4gICAgICA+IHBlZXIgcmVzaWRl
bnRpYWwgZ2F0ZXdheXMgKGVuY3J5cHRlZCkuDQo+Pg0KPj4gICAgIEkgZ3Vlc3MgSSBqdXN0IG5l
ZWQgdG8gaGF2ZSBtb3JlIGluZm8gYWJvdXQgaG93IHRoaXMgd291bGQgd29yaw0KPiBiZWZvcmUg
SQ0KPj4gICAgIHdpbGwgYmUgY29udmluY2VkIGl0IGlzIGZlYXNpYmxlIGFuZCB0cnVzdHdvcnRo
eS4NCj4+DQo+Pg0KPj4gV2VsbCwgJ3RydXN0d29ydGh5JyBjb3VsZCBiZSAgY29uc2lkZXJlZCBp
biBtYW55IGFuZ2xlcy4NCj4+IElmIGl0IGlzIGFib3V0IHByaXZhY3kgb2YgdGhlIG1lc3NhZ2Us
IGEgcHVibGljIGtleSBiYXNlZCBlbmNyeXB0aW9uIA0KPj4gd291bGQgcHJvdmlkZSBhY2NlcHRh
YmxlIHByaXZhY3kuDQo+PiBJZiBpdCBpcyBhYm91dCByZWxpYWJpbGl0eSBvZiB0aGUgbWVzc2Fn
ZSBkZWxpdmVyeSwgd2VsbCwgYSBQMlAgYmFzZWQgDQo+PiBhc3luY2hyb25vdXMgbWVzc2FnZSBk
ZWxpdmVyeSAobGlrZSBWTSkgaXMgbW9zdCBsaWtlbHkgbGVzcyByZWxpYWJsZSANCj4+IHRoYW4g
YSB3ZWxsIG1hbmFnZWQgc2VydmVyIGJhc2VkIHN5c3RlbS4NCj4+IEhvd2V2ZXIsIG15IGV4cGVy
aWVuY2Ugd2l0aCBTa3lwZSdzIGFzeW5jaHJvbm91cyBtZXNzYWdlIGRlbGl2ZXJ5IHdhcyANCj4+
IG5vdCBiYWQuIEFjdHVhbGx5IEkgZG9uJ3Qgc2VlIGFueSBzaWduaWZpY2FudCBkaWZmZXJlbmNl
IGJldHdlZW4gaXQNCj4gYW5kIA0KPj4gbXkgY2VsbHVsYXIgc2VydmljZSBwcm92aWRlcidzIFZN
IHNlcnZpY2UuIDotKQ0KPj4gUmVsaWFiaWxpdHkgaXMgYWx3YXlzIGEgY2hhbGxlbmdlIGZvciBQ
MlAsIGZvciBzdXJlLiBCdXQsIEkgYmVsaWV2ZSBpdA0KPiANCj4+IGlzIGZlYXNpYmxlIHRvIGJ1
aWxkIGEgUDJQIHN5c3RlbSBmb3IgVk0gYWNjZXB0YWJsZSBmb3IgbWFueQ0KPiBzY2VuYXJpb3Mu
DQo+PiAgICAgID4gLSBJbiBtb2JpbGUgbmV0d29ya3M6IFRoZSBWTSBjYW4gcmVzaWRlIGluIHF1
aXRlIHN0YWJsZSBwZWVycw0KPj4gICAgIGluc2lkZSB0aGUNCj4+ICAgICAgPiB3aXJlbGVzcyBi
YXNlIHN0YXRpb24gbmV0d29yay4gVGhlIHBlZXJzIGluIHRoZSBiYXNlIHN0YXRpb24NCj4gbmV0
d29yaw0KPj4gICAgICA+IG5lZWQgbm8gY29uZmlndXJhdGlvbiwgZXRjLg0KPj4NCj4+ICAgICBJ
IGRvbid0IHVuZGVyc3RhbmQuIEkgZ3Vlc3MgdGhhdCBjb3VsZCBiZSB0cnVlIGlmIHRoZSBwZWVy
cyBhcmUNCj4gd2lsbGluZw0KPj4gICAgIHRvIHN0b3JlIGFuIGFyYml0cmFyeSBhbW91bnQgb2Yg
Vk0gaW5kZWZpbml0ZWx5IGZvciBhbnlib2R5LiBJcw0KPiB0aGF0DQo+PiAgICAgYmVsaWV2YWJs
ZT8NCj4+DQo+Pg0KPj4gSXQgZGVwZW5kcy4NCj4+IEluIGEgdmVyeSBuaWNlIGVudmlyb25tZW50
IHdoZXJlIGFsbCB0aGUgcGVlcnMgYXJlIHdpbGxpbmcgdG8NCj4gY29vcGVyYXRlIA0KPj4gYXQg
dGhlaXIgYmVzdCwgdGhlIHBlZXJzIHdpbGwgc3RvcmUgYXMgbXVjaCBhcyB0aGV5IGNhbi4gSW4g
YSB0b3VnaCANCj4+IGVudmlyb25tZW50LCB0aGUgc2l0dWF0aW9uIHdpbGwgYmUgZGlmZmVyZW50
Lg0KPj4NCj4+ICAgICBUaGlzIHNlZW1zIHRvIHRyYW5zbGF0ZSB0byBhIG1vZGVsIHdoZXJlIGl0
IGlzIGFzc3VtZWQgdGhhdCB0aG9zZQ0KPiBub2Rlcw0KPj4gICAgIHRoYXQgYXJlIG9uIG1vc3Qg
b2YgdGhlIHRpbWUgd2lsbCBiZSB3aWxsaW5nIHRvIHByb3ZpZGUgVk0gc3RvcmFnZQ0KPiBmb3IN
Cj4+ICAgICB0aG9zZSBub2RlcyB0aGF0IGFyZW4ndCBvbiBtb3N0IG9mIHRoZSB0aW1lLg0KPj4N
Cj4+DQo+PiBUaGlzIGlzIGFnYWluIHJlbGF0ZWQgdG8gcmVsaWFiaWxpdHkgb2YgUDJQIHN5c3Rl
bXMgb3IgdG9waWNzIGxpa2UNCj4gZnJlZSANCj4+IHJpZGVycyBhbmQgcmVwdXRhdGlvbi4NCj4+
IEEgUDJQIHN5c3RlbSBpcyBhIGNvbW11bml0eSBvciBzb2NpZXR5LiBUbyBiZSBzaW1wbGUsIGlm
IG1hbnkgb2YgdGhlIA0KPj4gbWVtYmVycyBhcmUgYmFkLCB0aGUgY29tbXVuaXR5IHdvbid0IHdv
cmsgd2VsbC4gSWYgdGhlIG1ham9yaXR5IG9mIHRoZQ0KPiANCj4+IG1lbWJlcnMgYXJlIGdvb2Qs
IHRoZSBjb21tdW5pdHkgd2lsbCB3b3JrIHdlbGwgb3IgcmVhc29uYWJseS4NCj4+DQo+PiAgICAg
ID4gQWRkIHRvIHRoaXMgdGhlIGNvbmZlcmVuY2luZyBjYXBhYmlsaXR5IGNvbWluZyBmcm9tIHAy
cA0KPiBhcHBsaWNhdGlvbg0KPj4gICAgICA+IGxheWVyIG11bHRpY2FzdCwgdGhlIFNJUCBlMmUg
Y29udHJvbCBjYXBhYmlsaXRpZXMgKGZvciBzdWNoIGFzDQo+PiAgICAgID4gYXV0by1hdHRlbmRh
bnQsIGFnZW50IHdvcmtzdGF0aW9uLCBldGMuKSBhbmQgb25lIGhhcyB0byB3b25kZXINCj4gd2h5
IElUDQo+PiAgICAgID4gbmV0d29ya3MsIHB1YmxpYyBWb0lQIG5ldHdvcmtzIGFuZCBlbmQgdXNl
cnMgc2hvdWxkIHN1cHBvcnQgdGhlDQo+IGh1Z2UNCj4+ICAgICAgPiBjb3N0IG9mIGhhbmQgZW5n
aW5lZXJpbmcsIHRlc3RpbmcsIG1vbml0b3JpbmcsIG1haW50YWluaW5nDQo+IHNlcnZlcg0KPj4g
ICAgIGJhc2VkDQo+PiAgICAgID4gVm9JUCBuZXR3b3Jrcy4gUDJQIHNlbGYgY29uZmlndXJhdGlv
biBpcyBub3RoaW5nIGxlc3MgdGhhdA0KPiBhdXRvbWF0aW9uDQo+PiAgICAgID4gYXBwbGllZCB0
byBWb0lQLCBwbHVzIHRoZSBzaGlmdGluZyBvZiBjb21wdXRpbmcgdG8gdGhlDQo+IGVuZHBvaW50
cywNCj4+ICAgICB3aGVyZQ0KPj4gICAgICA+IHRoZXJlIGlzIGFuIGFidW5kYW5jZSBvZiB1bnVz
ZWQgQ1BVLCBzdG9yYWdlLCBiYW5kd2lkdGggYW5kDQo+PiAgICAgZWxlY3RyaWNpdHkuDQo+PiAg
ICAgID4NCj4+ICAgICAgPiBFcmljIEJ1cmdlciBhbHNvIG5vdGVzIElNIGNoYW5nZXMgY29tcGxl
dGVseSB0aGUgdXNhZ2UgZm9yIFZNDQo+IGFuZCBtYXkNCj4+ICAgICAgPiBtYWtlIHVubmVjZXNz
YXJ5IHRvIHBsYWNlIGNhbGxzIG9uIFZNIGluIHRoZSBmaXJzdCBwbGFjZS4NCj4+DQo+PiAgICAg
SSBmaW5kIHRoaXMgbW9yZSBwcm9taXNpbmcuDQo+Pg0KPj4gICAgICAgICAgIA0KPj4NCj4+DQo+
PiBJbiBvdmVyYWxsLCBhcmUgd2UgZGlzY3Vzc2luZyBpZiBQMlAgc3lzdGVtcyBiYXNlZCBWTSBj
YW4gd29yaz8gSQ0KPiB0aGluayANCj4+IGl0IGNhbiB3b3JrLiAgSnVzdCBpdCBkZXBlbmRzIG9u
IG1hbnkgdGhpbmdzLg0KPj4gSWYgaXQgaXMgbm90IHN1cGVyLXJlbGlhYmxlLCBzaG91bGQgd2Ug
ZGlzcmVnYXJkIGl0PyBJIHdvdWxkIHNheSBuby4NCj4+DQo+PiBPbiB0aGUgb3RoZXIgaGFuZCwg
ZG8gd2UgaGF2ZSB0byBhYmFuZG9uIGNsaWVudCBzZXJ2ZXIgYmFzZWQgVk0gYW5kIA0KPj4gc3dp
dGNoIHRvIFAyUCBzeXN0ZW0gYmFzZWQgVk0/IEl0IGlzIHVwdG8gZWFjaCBvZiB1cy4NCj4+IENs
aWVudCBzZXJ2ZXIgYmFzZWQgVk0gc3lzdGVtcyBhcmUgYWxyZWFkeSB0aGVyZS4NCj4+IFNvIHdo
eSBkb24ndCB3ZSB3b3JrIG9uIFAyUCBiYXNlZCBWTSBub3c/DQo+PiAgDQo+PiBUaGFua3MuDQo+
Pg0KPj4gRXVuc29vDQo+IA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KUDJQU0lQIG1haWxpbmcgbGlzdA0KUDJQU0lQQGlldGYub3JnDQpodHRwczov
L3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wMnBzaXANCg==

------_=_NextPart_001_01C7767B.8BBEF331
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMg
RXhjaGFuZ2UgU2VydmVyIHZlcnNpb24gNi41Ljc2NTAuMjgiPg0KPFRJVExFPlJFOiBbUDJQU0lQ
XSBSZTogW1AyUHJnXSBSRTogW1NpcHBpbmddIFNpbXBsZSBTSVAgdXNhZ2Ugc2NlbmFyaW88L1RJ
VExFPg0KPC9IRUFEPg0KPEJPRFk+DQo8IS0tIENvbnZlcnRlZCBmcm9tIHRleHQvcGxhaW4gZm9y
bWF0IC0tPg0KDQo8UD48Rk9OVCBTSVpFPTI+SGVucnksPEJSPg0KPEJSPg0KSSBsaWtlIHlvdXIg
aWRlYSBvZiBkZXBsb3lpbmcgc2lwIHBlZXJzIGluIGVkZ2UgZGV2aWNlcy4gSG93ZXZlciwgYXMg
YW4gZW1wbG95ZWUgb2YgYSBjYXJyaWVyIEkgd291bGQgbGlrZSB0byBzZWUgaG93IGEgY2Fycmll
ciBpcyBhYmxlIHRvIHByb3ZpZGUgc2VydmljZSBhc3VyYW5jZSB0byBiZSBhYmxlIHRvIHByb3Zp
ZGUgY29tcGxpYW50IGhhbmRsaW5nLiBNYW55IG9mIG91ciBjdXN0b21lcnMgZG8gbm90IHVuZGVy
c3RhbmQgaG93IHRvIGluc3RhbGwgdGhlc2UgZ2F0ZXdheXMgdGhlbXNlbHZlcywgbGV0IGFsb25l
IGhvdyB0byB0cm91Ymxlc2hvb3QuPEJSPg0KPEJSPg0KVGhpcyBpcyBldmVuIG1vcmUgaW1wb3J0
YW50IGZvciBlbnRlcnByaXNlcywgd2hpY2ggb2Z0ZW4mbmJzcDsgaW5zaXN0IG9uIFNMQXMgd2hp
Y2ggaW5jbHVkZSB0cm91Ymxlc2hvb3QgcmVzb2x1dGlvbiBsaW1pdHMuPEJSPg0KPEJSPg0KLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08QlI+DQpGcm9tOiAmcXVvdDtQYXVsIEt5eml2YXQmcXVv
dDsgJmx0O3BreXppdmF0QGNpc2NvLmNvbSZndDs8QlI+DQpUbzogJnF1b3Q7SGVucnkgU2lubnJl
aWNoJnF1b3Q7ICZsdDtoc2lubnJlaUBhZG9iZS5jb20mZ3Q7PEJSPg0KQ2M6ICZxdW90O1AyUFNJ
UCBNYWlsaW5nIExpc3QmcXVvdDsgJmx0O3AycHNpcEBpZXRmLm9yZyZndDs7ICZxdW90O01pY2hh
ZWwgSGFtbWVyIChtaGFtbWVyKSZxdW90OyAmbHQ7bWhhbW1lckBjaXNjby5jb20mZ3Q7OyAmcXVv
dDtEYXZpZCBSIE9yYW4mcXVvdDsgJmx0O29yYW5AY2lzY28uY29tJmd0OzsgJnF1b3Q7cDJwcmdA
aWV0Zi5vcmcmcXVvdDsgJmx0O3AycHJnQGlldGYub3JnJmd0OzsgJnF1b3Q7c2lwcGluZ0BpZXRm
Lm9yZyZxdW90OyAmbHQ7c2lwcGluZ0BpZXRmLm9yZyZndDs8QlI+DQpTZW50OiAzLTQtMDcgMDE6
MTE8QlI+DQpTdWJqZWN0OiBbUDJQU0lQXSBSZTogW1AyUHJnXSBSRTogW1NpcHBpbmddIFNpbXBs
ZSBTSVAgdXNhZ2Ugc2NlbmFyaW88QlI+DQo8QlI+DQo8QlI+DQo8QlI+DQpIZW5yeSBTaW5ucmVp
Y2ggd3JvdGU6PEJSPg0KJmd0OyBQYXVsLDxCUj4NCiZndDs8QlI+DQomZ3Q7Jmd0OyBJIG1vcmUg
b3IgbGVzcyBhZ3JlZSB3aXRoIHRoZSBmaW5hbCBjb25jbHVzaW9uIGJlbG93LjxCUj4NCiZndDs8
QlI+DQomZ3Q7IFRoaXMgaXMgZ29vZCBzdGFydGluZyBwb2ludCB0byBkaXNjdXNzIHNvbWUgdXNh
Z2Ugc2NlbmFyaW9zLjxCUj4NCiZndDs8QlI+DQomZ3Q7IFB1dHRpbmcgb24gbXkgZm9ybWVyIGhh
dCBhcyBhbiBlbXBsb3llZSBmb3IgYSBjYXJyaWVyLCBJIGNhbm5vdCBvdmVybG9vazxCUj4NCiZn
dDsgdGhlIGZvbGxvd2luZzo8QlI+DQomZ3Q7PEJSPg0KJmd0OyBQMlAgU0lQIGltcGxlbWVudGVk
IGNvcnJlY3RseSBpbiB0aGUgcmVzaWRlbnRpYWwgYWNjZXNzIGJveCBvciBjYWJsZTxCUj4NCiZn
dDsgc2V0LXRvcCBib3ggaW5kZWVkIGlzIGEgZ29vZCBvciBiZXR0ZXIgcmVwbGFjZW1lbnQgZm9y
IHRoZSBlbnRpcmUgVm9JUDxCUj4NCiZndDsgbmV0d29yayBpbmZyYXN0cnVjdHVyZSAoY29zdCwg
b3BlcmF0aW9ucywgbmV3IHNlcnZpY2VzLCBldGMpLjxCUj4NCiZndDsgSW50ZWdyYXRlZCBhY2Nl
c3MgZGV2aWNlcyBmb3IgdGhlIGVudGVycHJpc2UgY2FuIHByb2JhYmx5IHBsYXkgYSBzaW1pbGFy
PEJSPg0KJmd0OlLCBiYW5kd2lkdGggYW5kDQo+PiAgICAgZWxlY3RyaWNpdHkuDQo+PiAg
ICAgID4NCj4+ICAgICAgPiBFcmljIEJ1cmdlciBhbHNvIG5vdGVzIElNIGNoYW5nZXMgY29tcGxl
dGVseSB0aGUgdXNhZ2UgZm9yIFZNDQo+IGFuZCBtYXkNCj4+ICAgICAgPiBtYWtlIHVubmVjZXNz
YXJ5IHRvIHBsYWNlIGNhbGxzIG9uIFZNIGluIHRoZSBmaXJzdCBwbGFjZS4NCj4+DQo+PiAgICAg
SSBmaW5kIHRoaXMgbW9yZSBwcm9taXNpbmcuDQo+Pg0KPj4gICAgICAgICAgIA0KPj4NCj4+DQo+
PiBJbiBvdmVyYWxsLCBhcmUgd2UgZGlzY3Vzc2luZyBpZiBQMlAgc3lzdGVtcyBiYXNlZCBWTSBj
YW4gd29yaz8gSQ0KPiB0aGluayANCj4+IGl0IGNhbiB3b3JrLiAgSnVzdCBpdCBkZXBlbmRzIG9u
IG1hbnkgdGhpbmdzLg0KPj4gSWYgaXQgaXMgbm90IHN1cGVyLXJlbGlhYmxlLCBzaG91bGQgd2Ug
ZGlzcmVnYXJkIGl0PyBJIHdvdWxkIHNheSBuby4NCj4+DQo+PiBPbiB0aGUgb3RoZXIgaGFuZCwg
ZG8gd2UgaGF2ZSB0byBhYmFuZG9uIGNsaWVudCBzZXJ2ZXIgYmFzZWQgVk0gYW5kIA0KPj4gc3dp
dGNoIHRvIFAyUCBzeXN0ZW0gYmFzZWQgVk0/IEl0IGlzIHVwdG8gZWFjaCBvZiB1cy4NCj4+IENs
aWVudCBzZXJ2ZXIgYmFzZWQgVk0gc3lzdGVtcyBhcmUgYWxyZWFkeSB0aGVyZS4NCj4+IFNvIHdo
eSBkb24ndCB3ZSB3b3JrIG9uIFAyUCBiYXNlZCBWTSBub3c/DQo+PiAgDQo+PiBUaGFua3MuDQo+
Pg0KPj4gRXVuc29vDQo+IA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KUDJQU0lQIG1haWxpbmcgbGlzdA0KUDJQU0lQQGlldGYub3JnDQpodHRwczov
L3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wMnBzaXANCg==

------_=_NextPart_001_01C7767B.8BBEF331
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMg
RXhjaGFuZ2UgU2VydmVyIHZlcnNpb24gNi41Ljc2NTAuMjgiPg0KPFRJVExFPlJFOiBbUDJQU0lQ
XSBSZTogW1AyUHJnXSBSRTogW1NpcHBpbmddIFNpbXBsZSBTSVAgdXNhZ2Ugc2NlbmFyaW88L1RJ
VExFPg0KPC9IRUFEPg0KPEJPRFk+DQo8IS0tIENvbnZlcnRlZCBmcm9tIHRleHQvcGxhaW4gZm9y
bWF0IC0tPg0KDQo8UD48Rk9OVCBTSVpFPTI+SGVucnksPEJSPg0KPEJSPg0KSSBsaWtlIHlvdXIg
aWRlYSBvZiBkZXBsb3lpbmcgc2lwIHBlZXJzIGluIGVkZ2UgZGV2aWNlcy4gSG93ZXZlciwgYXMg
YW4gZW1wbG95ZWUgb2YgYSBjYXJyaWVyIEkgd291bGQgbGlrZSB0byBzZWUgaG93IGEgY2Fycmll
ciBpcyBhYmxlIHRvIHByb3ZpZGUgc2VydmljZSBhc3VyYW5jZSB0byBiZSBhYmxlIHRvIHByb3Zp
ZGUgY29tcGxpYW50IGhhbmRsaW5nLiBNYW55IG9mIG91ciBjdXN0b21lcnMgZG8gbm90IHVuZGVy
c3RhbmQgaG93IHRvIGluc3RhbGwgdGhlc2UgZ2F0ZXdheXMgdGhlbXNlbHZlcywgbGV0IGFsb25l
IGhvdyB0byB0cm91Ymxlc2hvb3QuPEJSPg0KPEJSPg0KVGhpcyBpcyBldmVuIG1vcmUgaW1wb3J0
YW50IGZvciBlbnRlcnByaXNlcywgd2hpY2ggb2Z0ZW4mbmJzcDsgaW5zaXN0IG9uIFNMQXMgd2hp
Y2ggaW5jbHVkZSB0cm91Ymxlc2hvb3QgcmVzb2x1dGlvbiBsaW1pdHMuPEJSPg0KPEJSPg0KLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08QlI+DQpGcm9tOiAmcXVvdDtQYXVsIEt5eml2YXQmcXVv
dDsgJmx0O3BreXppdmF0QGNpc2NvLmNvbSZndDs8QlI+DQpUbzogJnF1b3Q7SGVucnkgU2lubnJl
aWNoJnF1b3Q7ICZsdDtoc2lubnJlaUBhZG9iZS5jb20mZ3Q7PEJSPg0KQ2M6ICZxdW90O1AyUFNJ
UCBNYWlsaW5nIExpc3QmcXVvdDsgJmx0O3AycHNpcEBpZXRmLm9yZyZndDs7ICZxdW90O01pY2hh
ZWwgSGFtbWVyIChtaGFtbWVyKSZxdW90OyAmbHQ7bWhhbW1lckBjaXNjby5jb20mZ3Q7OyAmcXVv
dDtEYXZpZCBSIE9yYW4mcXVvdDsgJmx0O29yYW5AY2lzY28uY29tJmd0OzsgJnF1b3Q7cDJwcmdA
aWV0Zi5vcmcmcXVvdDsgJmx0O3AycHJnQGlldGYub3JnJmd0OzsgJnF1b3Q7c2lwcGluZ0BpZXRm
Lm9yZyZxdW90OyAmbHQ7c2lwcGluZ0BpZXRmLm9yZyZndDs8QlI+DQpTZW50OiAzLTQtMDcgMDE6
MTE8QlI+DQpTdWJqZWN0OiBbUDJQU0lQXSBSZTogW1AyUHJnXSBSRTogW1NpcHBpbmddIFNpbXBs
ZSBTSVAgdXNhZ2Ugc2NlbmFyaW88QlI+DQo8QlI+DQo8QlI+DQo8QlI+DQpIZW5yeSBTaW5ucmVp
Y2ggd3JvdGU6PEJSPg0KJmd0OyBQYXVsLDxCUj4NCiZndDs8QlI+DQomZ3Q7Jmd0OyBJIG1vcmUg
b3IgbGVzcyBhZ3JlZSB3aXRoIHRoZSBmaW5hbCBjb25jbHVzaW9uIGJlbG93LjxCUj4NCiZndDs8
QlI+DQomZ3Q7IFRoaXMgaXMgZ29vZCBzdGFydGluZyBwb2ludCB0byBkaXNjdXNzIHNvbWUgdXNh
Z2Ugc2NlbmFyaW9zLjxCUj4NCiZndDs8QlI+DQomZ3Q7IFB1dHRpbmcgb24gbXkgZm9ybWVyIGhh
dCBhcyBhbiBlbXBsb3llZSBmb3IgYSBjYXJyaWVyLCBJIGNhbm5vdCBvdmVybG9vazxCUj4NCiZn
dDsgdGhlIGZvbGxvd2luZzo8QlI+DQomZ3Q7PEJSPg0KJmd0OyBQMlAgU0lQIGltcGxlbWVudGVk
IGNvcnJlY3RseSBpbiB0aGUgcmVzaWRlbnRpYWwgYWNjZXNzIGJveCBvciBjYWJsZTxCUj4NCiZn
dDsgc2V0LXRvcCBib3ggaW5kZWVkIGlzIGEgZ29vZCBvciBiZXR0ZXIgcmVwbGFjZW1lbnQgZm9y
IHRoZSBlbnRpcmUgVm9JUDxCUj4NCiZndDsgbmV0d29yayBpbmZyYXN0cnVjdHVyZSAoY29zdCwg
b3BlcmF0aW9ucywgbmV3IHNlcnZpY2VzLCBldGMpLjxCUj4NCiZndDsgSW50ZWdyYXRlZCBhY2Nl
c3MgZGV2aWNlcyBmb3IgdGhlIGVudGVycHJpc2UgY2FuIHByb2JhYmx5IHBsYXkgYSBzaW1pbGFy
PEJSPg0KJmd0OyByb2xlLCBub3QgdG8gbWVudGlvbiBleGlzdGluZyBQMlAgUEJYIHByb2R1Y3Rz
IChwbGVhc2UgcmVmZXIgdG8gYWxsIHRoZTxCUj4NCiZndDsgYWR2YW50YWdlcyBvZiBQMlAgdGhh
dCBuZWVkIG5vdCByZXBlYXRlZCBoZXJlKS48QlI+DQomZ3Q7PEJSPg0KJmd0OyBXaGF0IGRvIHBl
b3BsZSB0aGluayBvZiB0aGVzZSB0aHJlZSB1c2FnZSBzY2VuYXJpb3MgZm9yIFAyUCBTSVA6PEJS
Pg0KJmd0OyAtIFNJUCBwZWVyIGluIHRoZSBEU0wgYWNjZXNzIGRldmljZSw8QlI+DQomZ3Q7IC0g
U0lQIHBlZXIgaW4gdGhlIGNhYmxlIGFjY2VzcyBkZXZpY2UsPEJSPg0KPEJSPg0KVGhlc2Ugc2Vl
bSBxdWl0ZSByZWFzb25hYmxlLCBhc3N1bWluZyB0aGF0IGEgZGV2aWNlIGNvbm5lY3RlZCBhdCB0
aGlzPEJSPg0KcG9pbnQgaXMgYWJsZSB0byBmdW5jdGlvbiBwcm9wZXJseSBhcyBhIHBlZXIuIChJ
IGhhdmVuJ3QgYmVlbiBmb2xsb3dpbmc8QlI+DQp3aGF0IHRoZSBhc3N1bXB0aW9ucyBhcmUgYWJv
dXQgcmVxdWlyZWQgbmV0d29yayBjYXBhYmlsaXRpZXMgb2YgcGVlcnMuKTxCUj4NCjxCUj4NCiZn
dDsgLSBTSVAgcGVlciBpbiBlbnRlcnByaXNlIG5ldHdvcmsgaW50ZWdyYXRlZCBhY2Nlc3MgZGV2
aWNlIChJQUQpLjxCUj4NCjxCUj4NCkkgdGhpbmsgdGhpcyBkZXBlbmRzIGdyZWF0bHkgb24gd2hh
dCBleHBlY3RhdGlvbnMgLyBjb250cmFjdHVhbDxCUj4NCmd1YXJhbnRlZXMgdGhlIGVudGVycHJp
c2UgaGFzLiBJdHMgdW5jbGVhciB0byBtZSB3aGF0IGd1YXJhbnRlZXMgY2FuIGJlPEJSPg0KbWFk
ZSBhYm91dCBhIFAyUFNJUCBuZXR3b3JrIHdpbGwgYmUgYWJsZSB0byBtYWtlLCBhbmQgaXRzIHVu
Y2xlYXIgd2hhdDxCUj4NCmtpbmQgb2YgaW5mcmFzdHJ1Y3R1cmUgd291bGQgYmUgaW5zdGFsbGVk
IGJ5L2ZvciBzb21lb25lIHdpbGxpbmcgdG8gbWFrZTxCUj4NCmd1YXJhbnRlZXMuPEJSPg0KPEJS
Pg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFBhdWw8QlI+DQo8
QlI+DQomZ3Q7IE5vdGUgdGhhdCB0aGVzZSBleGFtcGxlcyBpbXBseSB2ZXJ5IGxvdyBjaHVybiBm
b3IgdGhlIHBlZXJzIGFuZCBhZGQgdGhlPEJSPg0KJmd0OyBkYXRhIHJldGVudGlvbiByZXNpbGll
bmNlIG9mIFAyUCAoZ2VvZ3JhcGhpYyBkaXZlcnNpdHkgaXMgbmF0aXZlIGFuZDxCUj4NCiZndDsg
bW9iaWxlLCBldGMuKS4gSW5jaWRlbnRhbGx5LCBOQVQgdHJhdmVyc2FsIG1heSBhbHNvIG5vdCBi
ZSBhIHByb2JsZW0sIG9yPEJSPg0KJmd0OyBhdCBsZWFzdCBhbiBlYXNpZXIgcHJvYmxlbS48QlI+
DQomZ3Q7PEJSPg0KJmd0OyBXaGF0IGRvIHlvdSBhbGwgdGhpbms/PEJSPg0KJmd0OzxCUj4NCiZn
dDsgSSBoYXZlIHRha2VuIHRoZSBsaWJlcnR5IHRvIGNvcHkgdGhlIFAyUCBTSVAgbGlzdCwgc2lu
Y2UgdGhlIGxvdyBjaHVybjxCUj4NCiZndDsgc2NlbmFyaW9zIGFyZSBvZiBpbnRlcmVzdCBmb3Ig
dGhlIERIVCBzZWxlY3Rpb24uIE9yIGp1c3QgcGljayB0aGUgc2FtZTxCUj4NCiZndDsgREhUIGZv
ciBhbGwgc2NlbmFyaW9zIGFueXdheT8gSSBkb24ndCB0aGluayBzby48QlI+DQomZ3Q7PEJSPg0K
Jmd0OyBUaGFua3MsIEhlbnJ5PEJSPg0KJmd0OzxCUj4NCiZndDs8QlI+DQomZ3Q7IC0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tPEJSPg0KJmd0OyBGcm9tOiBQYXVsIEt5eml2YXQgWzxBIEhSRUY9
Im1haWx0bzpwa3l6aXZhdEBjaXNjby5jb20iPm1haWx0bzpwa3l6aXZhdEBjaXNjby5jb208L0E+
XTxCUj4NCiZndDsgU2VudDogRnJpZGF5LCBNYXJjaCAzMCwgMjAwNyA2OjMxIFBNPEJSPg0KJmd0
OyBUbzogRXVuc29vIFNoaW08QlI+DQomZ3Q7IENjOiBIZW5yeSBTaW5ucmVpY2g7IE1pY2hhZWwg
SGFtbWVyIChtaGFtbWVyKTsgRGF2aWQgUiBPcmFuOzxCUj4NCiZndDsgcDJwcmdAaWV0Zi5vcmc7
IHNpcHBpbmdAaWV0Zi5vcmc7IHpodXhpYW48QlI+DQomZ3Q7IFN1YmplY3Q6IFJlOiBbUDJQcmdd
IFJFOiBbU2lwcGluZ10gU2ltcGxlIFNJUCB1c2FnZSBzY2VuYXJpbzxCUj4NCiZndDs8QlI+DQom
Z3Q7IEkgbW9yZSBvciBsZXNzIGFncmVlIHdpdGggdGhlIGZpbmFsIGNvbmNsdXNpb24gYmVsb3cu
PEJSPg0KJmd0OzxCUj4NCiZndDsgTXkgbWFpbiBwb2ludCBoZXJlIGlzIHRoYXQgUDJQIGFuZCBD
L1MgbmVlZCBub3QgYmUgZW5lbWllcy4gTm9yIGlzIGE8QlI+DQomZ3Q7IHRvdGFsIEMvUyBzeXN0
ZW0gbmVjZXNzYXJpbHkgZXZpbC4gV2hhdCBpcyBtb3N0IGV2aWwgaXMgKmJ1bmRsaW5nKiBvZjxC
Uj4NCiZndDsgc2VydmljZXMgdGhhdCBwcmV2ZW50cyBmcmVlZG9tIG9mIGNob2ljZS48QlI+DQom
Z3Q7PEJSPg0KJmd0OyBJIHRoaW5rIEkgd291bGQgYmUgcXVpdGUgaGFwcHkgd2l0aCBhIFNQIHRo
YXQgcHJvdmlkZXMgYSByZWdpc3RyYXIvcHJveHk8QlI+DQomZ3Q7PEJSPg0KJmd0OyBhbmQgYWxs
b3dzIG1lIHRvIHByb3ZpZGUgYWxsIG90aGVyIGZlYXR1cmVzIGFzIEkgc2VlIGZpdCAtIGJ5IHRh
a2luZzxCUj4NCiZndDsgdGhlbSBhbGEgY2FydGUgZnJvbSB0aGUgU1AsIG9yIHN1YnNjcmliaW5n
IHRvIHRoZW0gZnJvbSBvbmUgb3IgbW9yZTxCUj4NCiZndDsgb3RoZXIgU1BzLCBvciBieSBwcm92
aWRpbmcgdGhlbSBteXNlbGYgdmlhIGFwcGxpYW5jZXMgSSBvd24uIElmIHRoYXQ8QlI+DQomZ3Q7
IHJlZ2lzdHJhci9wcm94eSB3YXMgcmVwbGFjZWQgYnkgYSBQMlAgc2lwIGNvbW11bml0eSwgdGhl
IGRpZmZlcmVuY2VzLCBpZjxCUj4NCiZndDs8QlI+DQomZ3Q7IGFueSwgd291bGQgaG9wZWZ1bGx5
IGJlIG1vcmUgYSBmdW5jdGlvbiBvZiB0aGUgaW1wbGVtZW50YXRpb24gYW5kIHRoZTxCUj4NCiZn
dDsgYnVzaW5lc3MgbW9kZWxzIG9mIHRob3NlIGludm9sdmVkIHRoYW4gdGhlIGFyY2hpdGVjdHVy
ZS48QlI+DQomZ3Q7PEJSPg0KJmd0OyAoSSBnYXRoZXIgdGhlIGdlbmVyYWwgYXNzdW1wdGlvbiBp
cyB0aGF0IGEgUDJQIHNldHVwIHdpbGwgYmUgKmZyZWUqLiBCdXQ8QlI+DQomZ3Q7PEJSPg0KJmd0
OyBJIGhhdmUgYSBoYXJkIHRpbWUgyByb2xlLCBub3QgdG8gbWVudGlvbiBleGlzdGluZyBQMlAgUEJYIHByb2R1Y3Rz
IChwbGVhc2UgcmVmZXIgdG8gYWxsIHRoZTxCUj4NCiZndDsgYWR2YW50YWdlcyBvZiBQMlAgdGhh
dCBuZWVkIG5vdCByZXBlYXRlZCBoZXJlKS48QlI+DQomZ3Q7PEJSPg0KJmd0OyBXaGF0IGRvIHBl
b3BsZSB0aGluayBvZiB0aGVzZSB0aHJlZSB1c2FnZSBzY2VuYXJpb3MgZm9yIFAyUCBTSVA6PEJS
Pg0KJmd0OyAtIFNJUCBwZWVyIGluIHRoZSBEU0wgYWNjZXNzIGRldmljZSw8QlI+DQomZ3Q7IC0g
U0lQIHBlZXIgaW4gdGhlIGNhYmxlIGFjY2VzcyBkZXZpY2UsPEJSPg0KPEJSPg0KVGhlc2Ugc2Vl
bSBxdWl0ZSByZWFzb25hYmxlLCBhc3N1bWluZyB0aGF0IGEgZGV2aWNlIGNvbm5lY3RlZCBhdCB0
aGlzPEJSPg0KcG9pbnQgaXMgYWJsZSB0byBmdW5jdGlvbiBwcm9wZXJseSBhcyBhIHBlZXIuIChJ
IGhhdmVuJ3QgYmVlbiBmb2xsb3dpbmc8QlI+DQp3aGF0IHRoZSBhc3N1bXB0aW9ucyBhcmUgYWJv
dXQgcmVxdWlyZWQgbmV0d29yayBjYXBhYmlsaXRpZXMgb2YgcGVlcnMuKTxCUj4NCjxCUj4NCiZn
dDsgLSBTSVAgcGVlciBpbiBlbnRlcnByaXNlIG5ldHdvcmsgaW50ZWdyYXRlZCBhY2Nlc3MgZGV2
aWNlIChJQUQpLjxCUj4NCjxCUj4NCkkgdGhpbmsgdGhpcyBkZXBlbmRzIGdyZWF0bHkgb24gd2hh
dCBleHBlY3RhdGlvbnMgLyBjb250cmFjdHVhbDxCUj4NCmd1YXJhbnRlZXMgdGhlIGVudGVycHJp
c2UgaGFzLiBJdHMgdW5jbGVhciB0byBtZSB3aGF0IGd1YXJhbnRlZXMgY2FuIGJlPEJSPg0KbWFk
ZSBhYm91dCBhIFAyUFNJUCBuZXR3b3JrIHdpbGwgYmUgYWJsZSB0byBtYWtlLCBhbmQgaXRzIHVu
Y2xlYXIgd2hhdDxCUj4NCmtpbmQgb2YgaW5mcmFzdHJ1Y3R1cmUgd291bGQgYmUgaW5zdGFsbGVk
IGJ5L2ZvciBzb21lb25lIHdpbGxpbmcgdG8gbWFrZTxCUj4NCmd1YXJhbnRlZXMuPEJSPg0KPEJS
Pg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFBhdWw8QlI+DQo8
QlI+DQomZ3Q7IE5vdGUgdGhhdCB0aGVzZSBleGFtcGxlcyBpbXBseSB2ZXJ5IGxvdyBjaHVybiBm
b3IgdGhlIHBlZXJzIGFuZCBhZGQgdGhlPEJSPg0KJmd0OyBkYXRhIHJldGVudGlvbiByZXNpbGll
bmNlIG9mIFAyUCAoZ2VvZ3JhcGhpYyBkaXZlcnNpdHkgaXMgbmF0aXZlIGFuZDxCUj4NCiZndDsg
bW9iaWxlLCBldGMuKS4gSW5jaWRlbnRhbGx5LCBOQVQgdHJhdmVyc2FsIG1heSBhbHNvIG5vdCBi
ZSBhIHByb2JsZW0sIG9yPEJSPg0KJmd0OyBhdCBsZWFzdCBhbiBlYXNpZXIgcHJvYmxlbS48QlI+
DQomZ3Q7PEJSPg0KJmd0OyBXaGF0IGRvIHlvdSBhbGwgdGhpbms/PEJSPg0KJmd0OzxCUj4NCiZn
dDsgSSBoYXZlIHRha2VuIHRoZSBsaWJlcnR5IHRvIGNvcHkgdGhlIFAyUCBTSVAgbGlzdCwgc2lu
Y2UgdGhlIGxvdyBjaHVybjxCUj4NCiZndDsgc2NlbmFyaW9zIGFyZSBvZiBpbnRlcmVzdCBmb3Ig
dGhlIERIVCBzZWxlY3Rpb24uIE9yIGp1c3QgcGljayB0aGUgc2FtZTxCUj4NCiZndDsgREhUIGZv
ciBhbGwgc2NlbmFyaW9zIGFueXdheT8gSSBkb24ndCB0aGluayBzby48QlI+DQomZ3Q7PEJSPg0K
Jmd0OyBUaGFua3MsIEhlbnJ5PEJSPg0KJmd0OzxCUj4NCiZndDs8QlI+DQomZ3Q7IC0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tPEJSPg0KJmd0OyBGcm9tOiBQYXVsIEt5eml2YXQgWzxBIEhSRUY9
Im1haWx0bzpwa3l6aXZhdEBjaXNjby5jb20iPm1haWx0bzpwa3l6aXZhdEBjaXNjby5jb208L0E+
XTxCUj4NCiZndDsgU2VudDogRnJpZGF5LCBNYXJjaCAzMCwgMjAwNyA2OjMxIFBNPEJSPg0KJmd0
OyBUbzogRXVuc29vIFNoaW08QlI+DQomZ3Q7IENjOiBIZW5yeSBTaW5ucmVpY2g7IE1pY2hhZWwg
SGFtbWVyIChtaGFtbWVyKTsgRGF2aWQgUiBPcmFuOzxCUj4NCiZndDsgcDJwcmdAaWV0Zi5vcmc7
IHNpcHBpbmdAaWV0Zi5vcmc7IHpodXhpYW48QlI+DQomZ3Q7IFN1YmplY3Q6IFJlOiBbUDJQcmdd
IFJFOiBbU2lwcGluZ10gU2ltcGxlIFNJUCB1c2FnZSBzY2VuYXJpbzxCUj4NCiZndDs8QlI+DQom
Z3Q7IEkgbW9yZSBvciBsZXNzIGFncmVlIHdpdGggdGhlIGZpbmFsIGNvbmNsdXNpb24gYmVsb3cu
PEJSPg0KJmd0OzxCUj4NCiZndDsgTXkgbWFpbiBwb2ludCBoZXJlIGlzIHRoYXQgUDJQIGFuZCBD
L1MgbmVlZCBub3QgYmUgZW5lbWllcy4gTm9yIGlzIGE8QlI+DQomZ3Q7IHRvdGFsIEMvUyBzeXN0
ZW0gbmVjZXNzYXJpbHkgZXZpbC4gV2hhdCBpcyBtb3N0IGV2aWwgaXMgKmJ1bmRsaW5nKiBvZjxC
Uj4NCiZndDsgc2VydmljZXMgdGhhdCBwcmV2ZW50cyBmcmVlZG9tIG9mIGNob2ljZS48QlI+DQom
Z3Q7PEJSPg0KJmd0OyBJIHRoaW5rIEkgd291bGQgYmUgcXVpdGUgaGFwcHkgd2l0aCBhIFNQIHRo
YXQgcHJvdmlkZXMgYSByZWdpc3RyYXIvcHJveHk8QlI+DQomZ3Q7PEJSPg0KJmd0OyBhbmQgYWxs
b3dzIG1lIHRvIHByb3ZpZGUgYWxsIG90aGVyIGZlYXR1cmVzIGFzIEkgc2VlIGZpdCAtIGJ5IHRh
a2luZzxCUj4NCiZndDsgdGhlbSBhbGEgY2FydGUgZnJvbSB0aGUgU1AsIG9yIHN1YnNjcmliaW5n
IHRvIHRoZW0gZnJvbSBvbmUgb3IgbW9yZTxCUj4NCiZndDsgb3RoZXIgU1BzLCBvciBieSBwcm92
aWRpbmcgdGhlbSBteXNlbGYgdmlhIGFwcGxpYW5jZXMgSSBvd24uIElmIHRoYXQ8QlI+DQomZ3Q7
IHJlZ2lzdHJhci9wcm94eSB3YXMgcmVwbGFjZWQgYnkgYSBQMlAgc2lwIGNvbW11bml0eSwgdGhl
IGRpZmZlcmVuY2VzLCBpZjxCUj4NCiZndDs8QlI+DQomZ3Q7IGFueSwgd291bGQgaG9wZWZ1bGx5
IGJlIG1vcmUgYSBmdW5jdGlvbiBvZiB0aGUgaW1wbGVtZW50YXRpb24gYW5kIHRoZTxCUj4NCiZn
dDsgYnVzaW5lc3MgbW9kZWxzIG9mIHRob3NlIGludm9sdmVkIHRoYW4gdGhlIGFyY2hpdGVjdHVy
ZS48QlI+DQomZ3Q7PEJSPg0KJmd0OyAoSSBnYXRoZXIgdGhlIGdlbmVyYWwgYXNzdW1wdGlvbiBp
cyB0aGF0IGEgUDJQIHNldHVwIHdpbGwgYmUgKmZyZWUqLiBCdXQ8QlI+DQomZ3Q7PEJSPg0KJmd0
OyBJIGhhdmUgYSBoYXJkIHRpbWUgYmVsaWV2aW5nIHRoYXQuIElmIG1vc3Qgb2YgdGhlIHVzYWdl
IGlzIGJ5IG1vYmlsZTxCUj4NCiZndDsgZGV2aWNlcyB0aGF0IGNhbid0IGJlIHBlZXJzLCB0aGVu
IHNvbWVib2R5IHdpbGwgaGF2ZSB0byBwYXkgZm9yIGVub3VnaDxCUj4NCiZndDsgcGVlcnMgdG8g
c3VwcG9ydCB0aGVtLiBJZiBpdCBpc24ndCBmcmVlLCB0aGVuIGhvdyBpcyBpdCBiZXR0ZXIgdGhh
biBhPEJSPg0KJmd0OyB3ZWxsIGVuZ2luZWVyZWQgQy9TIHN5c3RlbT8pPEJSPg0KJmd0OzxCUj4N
CiZndDsgU28gSSB0aGluayB0aGUga2V5IHRoaW5nIGhlcmUgaXMgdGhhdCBzb21lIGZlYXR1cmVz
IHdpbGwgcmVxdWlyZSBnZXR0aW5nPEJSPg0KJmd0OzxCUj4NCiZndDsgc29tZSBoZWxwIGZyb20g
YW5vdGhlciBub2RlLiBUaGVyZSBvdWdodCB0byBiZSB0aGUgb3B0aW9uIHRvIHBpY2sgYTxCUj4N
CiZndDsgZGlmZmVyZW50IHNvdXJjZSBmb3IgZWFjaCBoZWxwZXIgeW91IHJlcXVpcmUsIGFuZCBh
biBhYmlsaXR5IGZvciBpdCBhbGw8QlI+DQomZ3Q7IHRvIHBsYXkgdG9nZXRoZXIuPEJSPg0KJmd0
OzxCUj4NCiZndDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFBhdWw8QlI+DQomZ3Q7
PEJSPg0KJmd0OyBFdW5zb28gU2hpbSB3cm90ZTo8QlI+DQomZ3Q7Jmd0OyBQbGVhc2Ugc2VlIG15
IGlubGluZSBjb21tZW50LjxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0OyZndDsgT24gMy8zMC8wNywg
KlBhdWwgS3l6aXZhdCogJmx0O3BreXppdmF0QGNpc2NvLmNvbTxCUj4NCiZndDsmZ3Q7ICZsdDs8
QSBIUkVGPSJtYWlsdG86cGt5eml2YXRAY2lzY28uY29tIj5tYWlsdG86cGt5eml2YXRAY2lzY28u
Y29tPC9BPiZndDsmZ3Q7IHdyb3RlOjxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0OyZndDs8QlI+DQom
Z3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEhlbnJ5IFNpbm5y
ZWljaCB3cm90ZTo8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAm
Z3Q7IERhdmlkIE9yYW4gd3JvdGUgKHdpdGggcmVnYXJkIHRvIHZvaWNlIG1haWwpOjxCUj4NCiZn
dDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDs8QlI+DQomZ3Q7Jmd0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7Jmd0OyBJJ20gbm90IHNheWluZyB0aGlz
IGNhbid0IGJlIG1hZGUgdG8gd29yaywgb25seSB0aGF0IGl0IGlzbid0PEJSPg0KJmd0OyZndDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyBpbW1lZGlhdGVseSAmZ3Q7b2J2aW91
cyB0aGF0IGl0IGhhcyBhZHZhbnRhZ2VzIG92ZXIgYSBjbGFzc2ljPEJSPg0KJmd0OyZndDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgYXBwbGljYXRpb248QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IHNlcnZlciAmZ3Q7YXBwcm9hY2guPEJSPg0KJmd0OyZn
dDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJmd0OzxCUj4NCiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgVGhlIGFuc3dlciBmb3IgVk0gaXMgJnF1b3Q7
aXQgZGVwZW5kcyZxdW90Ozo8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyAmZ3Q7PEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7IEkgYWdy
ZWUuIEl0IHJlYWxseSBkZXBlbmRzLiBDZXJ0YWlubHkgdGhlcmUgYXJlIHRyYWRlb2Zmcy48QlI+
DQomZ3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZn
dDsgVGhlcmUgYXJlIHNldmVyYWwgY29tbWVyY2lhbCBQMlAgSVAgUEJYIHNvbHV0aW9ucyB3aXRo
b3V0IGFueTxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHNlcnZlciBmb3I8
QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IFZNIG9yIGFu
eXRoaW5nIGVsc2UuIE5vIGRvdWJ0IHRoZSBJVCBvcmdhbml6YXRpb24gYXBwcmVjaWF0ZXM8QlI+
DQomZ3Q7IGp1c3Q8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAm
Z3Q7IGhhdmluZyB0byBwbHVnIGluIHRoZSBJUCBwaG9uZXMgYW5kIEdXWSB0byB0aGUgUFNUTiB3
aXRob3V0IGFueTxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZn
dDsgY29uZmlndXJhdGlvbiBldmVyIGZvciBWTSBvciBhbnkgb3RoZXIgUEJYIGZlYXR1cmUuPEJS
Pg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBJIGRvbid0
IHVuZGVyc3RhbmQuIEFyZSB5b3Ugc2F5aW5nIHRoZXkgZG9uJ3QgaGF2ZSBWTSwgb3IgdGhhdDxC
Uj4NCiZndDsgdGhleTxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGRvbid0
IGhhdmUgYSAqc2VydmVyKiBmb3IgVk0/PEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OzxCUj4N
CiZndDsmZ3Q7IEkgZ3Vlc3MgdGhleSBkb24ndCBoYXZlIGEmbmJzcDsgKnNlcnZlciogZm9yJm5i
c3A7IFZNLjxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgJmd0OyBGb3IgcHVibGljIFAyUCBTSVAgbmV0d29ya3MgdGhlcmUgYXJlIHR3byBt
b3JlIHNjZW5hcmlvcyB3aGVyZTxCUj4NCiZndDsgVk0gY2FuPEJSPg0KJmd0OyZndDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyByZXNpZGUgKGFuZCB3aXRob3V0IGV2ZXIgc3Bl
bmRpbmcgb25lIGNlbnQgb24gVk0gc2VydmVycyArIElUPEJSPg0KJmd0OyZndDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgc3lzdGVtcyk6PEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgJmd0OzxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7ICZndDsgLSBJbiBDYWJsZSBhbmQgRFNMIHNlcnZpY2UgcHJvdmlkZXIgbmV0d29ya3M6IFRo
ZSByZXNpZGVudGlhbDxCUj4NCiZndDsmZ3Q7Jm5ic3AYmVsaWV2aW5nIHRoYXQuIElmIG1vc3Qgb2YgdGhlIHVzYWdl
IGlzIGJ5IG1vYmlsZTxCUj4NCiZndDsgZGV2aWNlcyB0aGF0IGNhbid0IGJlIHBlZXJzLCB0aGVu
IHNvbWVib2R5IHdpbGwgaGF2ZSB0byBwYXkgZm9yIGVub3VnaDxCUj4NCiZndDsgcGVlcnMgdG8g
c3VwcG9ydCB0aGVtLiBJZiBpdCBpc24ndCBmcmVlLCB0aGVuIGhvdyBpcyBpdCBiZXR0ZXIgdGhh
biBhPEJSPg0KJmd0OyB3ZWxsIGVuZ2luZWVyZWQgQy9TIHN5c3RlbT8pPEJSPg0KJmd0OzxCUj4N
CiZndDsgU28gSSB0aGluayB0aGUga2V5IHRoaW5nIGhlcmUgaXMgdGhhdCBzb21lIGZlYXR1cmVz
IHdpbGwgcmVxdWlyZSBnZXR0aW5nPEJSPg0KJmd0OzxCUj4NCiZndDsgc29tZSBoZWxwIGZyb20g
YW5vdGhlciBub2RlLiBUaGVyZSBvdWdodCB0byBiZSB0aGUgb3B0aW9uIHRvIHBpY2sgYTxCUj4N
CiZndDsgZGlmZmVyZW50IHNvdXJjZSBmb3IgZWFjaCBoZWxwZXIgeW91IHJlcXVpcmUsIGFuZCBh
biBhYmlsaXR5IGZvciBpdCBhbGw8QlI+DQomZ3Q7IHRvIHBsYXkgdG9nZXRoZXIuPEJSPg0KJmd0
OzxCUj4NCiZndDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFBhdWw8QlI+DQomZ3Q7
PEJSPg0KJmd0OyBFdW5zb28gU2hpbSB3cm90ZTo8QlI+DQomZ3Q7Jmd0OyBQbGVhc2Ugc2VlIG15
IGlubGluZSBjb21tZW50LjxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0OyZndDsgT24gMy8zMC8wNywg
KlBhdWwgS3l6aXZhdCogJmx0O3BreXppdmF0QGNpc2NvLmNvbTxCUj4NCiZndDsmZ3Q7ICZsdDs8
QSBIUkVGPSJtYWlsdG86cGt5eml2YXRAY2lzY28uY29tIj5tYWlsdG86cGt5eml2YXRAY2lzY28u
Y29tPC9BPiZndDsmZ3Q7IHdyb3RlOjxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0OyZndDs8QlI+DQom
Z3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEhlbnJ5IFNpbm5y
ZWljaCB3cm90ZTo8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAm
Z3Q7IERhdmlkIE9yYW4gd3JvdGUgKHdpdGggcmVnYXJkIHRvIHZvaWNlIG1haWwpOjxCUj4NCiZn
dDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDs8QlI+DQomZ3Q7Jmd0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7Jmd0OyBJJ20gbm90IHNheWluZyB0aGlz
IGNhbid0IGJlIG1hZGUgdG8gd29yaywgb25seSB0aGF0IGl0IGlzbid0PEJSPg0KJmd0OyZndDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyBpbW1lZGlhdGVseSAmZ3Q7b2J2aW91
cyB0aGF0IGl0IGhhcyBhZHZhbnRhZ2VzIG92ZXIgYSBjbGFzc2ljPEJSPg0KJmd0OyZndDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgYXBwbGljYXRpb248QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IHNlcnZlciAmZ3Q7YXBwcm9hY2guPEJSPg0KJmd0OyZn
dDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJmd0OzxCUj4NCiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgVGhlIGFuc3dlciBmb3IgVk0gaXMgJnF1b3Q7
aXQgZGVwZW5kcyZxdW90Ozo8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyAmZ3Q7PEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7IEkgYWdy
ZWUuIEl0IHJlYWxseSBkZXBlbmRzLiBDZXJ0YWlubHkgdGhlcmUgYXJlIHRyYWRlb2Zmcy48QlI+
DQomZ3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZn
dDsgVGhlcmUgYXJlIHNldmVyYWwgY29tbWVyY2lhbCBQMlAgSVAgUEJYIHNvbHV0aW9ucyB3aXRo
b3V0IGFueTxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHNlcnZlciBmb3I8
QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IFZNIG9yIGFu
eXRoaW5nIGVsc2UuIE5vIGRvdWJ0IHRoZSBJVCBvcmdhbml6YXRpb24gYXBwcmVjaWF0ZXM8QlI+
DQomZ3Q7IGp1c3Q8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAm
Z3Q7IGhhdmluZyB0byBwbHVnIGluIHRoZSBJUCBwaG9uZXMgYW5kIEdXWSB0byB0aGUgUFNUTiB3
aXRob3V0IGFueTxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZn
dDsgY29uZmlndXJhdGlvbiBldmVyIGZvciBWTSBvciBhbnkgb3RoZXIgUEJYIGZlYXR1cmUuPEJS
Pg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBJIGRvbid0
IHVuZGVyc3RhbmQuIEFyZSB5b3Ugc2F5aW5nIHRoZXkgZG9uJ3QgaGF2ZSBWTSwgb3IgdGhhdDxC
Uj4NCiZndDsgdGhleTxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGRvbid0
IGhhdmUgYSAqc2VydmVyKiBmb3IgVk0/PEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OzxCUj4N
CiZndDsmZ3Q7IEkgZ3Vlc3MgdGhleSBkb24ndCBoYXZlIGEmbmJzcDsgKnNlcnZlciogZm9yJm5i
c3A7IFZNLjxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgJmd0OyBGb3IgcHVibGljIFAyUCBTSVAgbmV0d29ya3MgdGhlcmUgYXJlIHR3byBt
b3JlIHNjZW5hcmlvcyB3aGVyZTxCUj4NCiZndDsgVk0gY2FuPEJSPg0KJmd0OyZndDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyByZXNpZGUgKGFuZCB3aXRob3V0IGV2ZXIgc3Bl
bmRpbmcgb25lIGNlbnQgb24gVk0gc2VydmVycyArIElUPEJSPg0KJmd0OyZndDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgc3lzdGVtcyk6PEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgJmd0OzxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7ICZndDsgLSBJbiBDYWJsZSBhbmQgRFNMIHNlcnZpY2UgcHJvdmlkZXIgbmV0d29ya3M6IFRo
ZSByZXNpZGVudGlhbDxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHJvdXRl
ciBjYW48QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IGFj
dCBhcyBhIHZvaWNlIHJlY29yZGVyPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyBUaGF0IGlzIHNpbXBseSBhbiBleGFtcGxlIG9mIHRoZSB1c2VyIGhh
dmluZyBhbiBhcHBsaWFuY2Ugb2YgaGlzPEJSPg0KJmd0OyBvd248QlI+DQomZ3Q7Jmd0OyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyB0aGF0IHByb3ZpZGVzIFZNIHNlcnZpY2UuPEJSPg0KJmd0OyZn
dDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IGFuZCBQ
MlAgY2FuIGNvdmVyIHRoZSBub3QgdG9vIGZyZXF1ZW50IGNhc2VzLDxCUj4NCiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgd2hlcmUgdGhlIHJvdXRlciBpcyBub3Qg
aW4gb3BlcmF0aW9uLCBzbyB0aGUgZGF0YSBpcyBiYWNrZWQgdXA8QlI+DQomZ3Q7IGluPEJSPg0K
Jmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgb3RoZXI8QlI+DQomZ3Q7Jmd0OyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IHBlZXIgcmVzaWRlbnRpYWwgZ2F0ZXdheXMg
KGVuY3J5cHRlZCkuPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyBJIGd1ZXNzIEkganVzdCBuZWVkIHRvIGhhdmUgbW9yZSBpbmZvIGFib3V0IGhvdyB0
aGlzIHdvdWxkIHdvcms8QlI+DQomZ3Q7IGJlZm9yZSBJPEJSPg0KJmd0OyZndDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgd2lsbCBiZSBjb252aW5jZWQgaXQgaXMgZmVhc2libGUgYW5kIHRydXN0
d29ydGh5LjxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyBXZWxsLCAn
dHJ1c3R3b3J0aHknIGNvdWxkIGJlJm5ic3A7IGNvbnNpZGVyZWQgaW4gbWFueSBhbmdsZXMuPEJS
Pg0KJmd0OyZndDsgSWYgaXQgaXMgYWJvdXQgcHJpdmFjeSBvZiB0aGUgbWVzc2FnZSwgYSBwdWJs
aWMga2V5IGJhc2VkIGVuY3J5cHRpb248QlI+DQomZ3Q7Jmd0OyB3b3VsZCBwcm92aWRlIGFjY2Vw
dGFibGUgcHJpdmFjeS48QlI+DQomZ3Q7Jmd0OyBJZiBpdCBpcyBhYm91dCByZWxpYWJpbGl0eSBv
ZiB0aGUgbWVzc2FnZSBkZWxpdmVyeSwgd2VsbCwgYSBQMlAgYmFzZWQ8QlI+DQomZ3Q7Jmd0OyBh
c3luY2hyb25vdXMgbWVzc2FnZSBkZWxpdmVyeSAobGlrZSBWTSkgaXMgbW9zdCBsaWtlbHkgbGVz
cyByZWxpYWJsZTxCUj4NCiZndDsmZ3Q7IHRoYW4gYSB3ZWxsIG1hbmFnZWQgc2VydmVyIGJhc2Vk
IHN5c3RlbS48QlI+DQomZ3Q7Jmd0OyBIb3dldmVyLCBteSBleHBlcmllbmNlIHdpdGggU2t5cGUn
cyBhc3luY2hyb25vdXMgbWVzc2FnZSBkZWxpdmVyeSB3YXM8QlI+DQomZ3Q7Jmd0OyBub3QgYmFk
LiBBY3R1YWxseSBJIGRvbid0IHNlZSBhbnkgc2lnbmlmaWNhbnQgZGlmZmVyZW5jZSBiZXR3ZWVu
IGl0PEJSPg0KJmd0OyBhbmQ8QlI+DQomZ3Q7Jmd0OyBteSBjZWxsdWxhciBzZXJ2aWNlIHByb3Zp
ZGVyJ3MgVk0gc2VydmljZS4gOi0pPEJSPg0KJmd0OyZndDsgUmVsaWFiaWxpdHkgaXMgYWx3YXlz
IGEgY2hhbGxlbmdlIGZvciBQMlAsIGZvciBzdXJlLiBCdXQsIEkgYmVsaWV2ZSBpdDxCUj4NCiZn
dDs8QlI+DQomZ3Q7Jmd0OyBpcyBmZWFzaWJsZSB0byBidWlsZCBhIFAyUCBzeXN0ZW0gZm9yIFZN
IGFjY2VwdGFibGUgZm9yIG1hbnk8QlI+DQomZ3Q7IHNjZW5hcmlvcy48QlI+DQomZ3Q7Jmd0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IC0gSW4gbW9iaWxlIG5ldHdvcmtzOiBU
aGUgVk0gY2FuIHJlc2lkZSBpbiBxdWl0ZSBzdGFibGUgcGVlcnM8QlI+DQomZ3Q7Jmd0OyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyBpbnNpZGUgdGhlPEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgJmd0OyB3aXJlbGVzcyBiYXNlIHN0YXRpb24gbmV0d29yay4gVGhl
IHBlZXJzIGluIHRoZSBiYXNlIHN0YXRpb248QlI+DQomZ3Q7IG5ldHdvcms8QlI+DQomZ3Q7Jmd0
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IG5lZWQgbm8gY29uZmlndXJhdGlv
biwgZXRjLjxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgSSBkb24ndCB1bmRlcnN0YW5kLiBJIGd1ZXNzIHRoYXQgY291bGQgYmUgdHJ1ZSBpZiB0aGUg
cGVlcnMgYXJlPEJSPg0KJmd0OyB3aWxsaW5nPEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgdG8gc3RvcmUgYW4gYXJiaXRyYXJ5IGFtb3VudCBvZiBWTSBpbmRlZmluaXRlbHkg
Zm9yIGFueWJvZHkuIElzPEJSPg0KJmd0OyB0aGF0PEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgYmVsaWV2YWJsZT88QlI+DQomZ3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7PEJSPg0K
Jmd0OyZndDsgSXQgZGVwZW5kcy48QlI+DQomZ3Q7Jmd0OyBJbiBhIHZlcnkgbmljZSBlbnZpcm9u
bWVudCB3aGVyZSBhbGwgdGhlIHBlZXJzIGFyZSB3aWxsaW5nIHRvPEJSPg0KJmd0OyBjb29wZXJh
dGU8QlI+DQomZ3Q7Jmd0OyBhdCB0aGVpciBiZXN0LCB0aGUgcGVlcnMgd2lsbCBzdG9yZSBhcyBt
dWNoIGFzIHRoZXkgY2FuLiBJbiBhIHRvdWdoPEJSPg0KJmd0OyZndDsgZW52aXJvbm1lbnQsIHRo
ZSBzaXR1YXRpb24gd2lsbCBiZSBkaWZmZXJlbnQuPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBUaGlzIHNlZW1zIHRvIHRyYW5zbGF0ZSB0byBhIG1v
ZGVsIHdoZXJlIGl0IGlzIGFzc3VtZWQgdGhhdCB0aG9zZTxCUj4NCiZndDsgbm9kZXM8QlI+DQom
Z3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB0aGF0IGFyZSBvbiBtb3N0IG9mIHRoZSB0
aW1lIHdpbGwgYmUgd2lsbGluZyB0byBwcm92aWRlIFZNIHN0b3JhZ2U8QlI+DQomZ3Q7IGZvcjxC
Uj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRob3NlIG7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHJvdXRl
ciBjYW48QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IGFj
dCBhcyBhIHZvaWNlIHJlY29yZGVyPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyBUaGF0IGlzIHNpbXBseSBhbiBleGFtcGxlIG9mIHRoZSB1c2VyIGhh
dmluZyBhbiBhcHBsaWFuY2Ugb2YgaGlzPEJSPg0KJmd0OyBvd248QlI+DQomZ3Q7Jmd0OyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyB0aGF0IHByb3ZpZGVzIFZNIHNlcnZpY2UuPEJSPg0KJmd0OyZn
dDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IGFuZCBQ
MlAgY2FuIGNvdmVyIHRoZSBub3QgdG9vIGZyZXF1ZW50IGNhc2VzLDxCUj4NCiZndDsmZ3Q7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgd2hlcmUgdGhlIHJvdXRlciBpcyBub3Qg
aW4gb3BlcmF0aW9uLCBzbyB0aGUgZGF0YSBpcyBiYWNrZWQgdXA8QlI+DQomZ3Q7IGluPEJSPg0K
Jmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgb3RoZXI8QlI+DQomZ3Q7Jmd0OyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IHBlZXIgcmVzaWRlbnRpYWwgZ2F0ZXdheXMg
KGVuY3J5cHRlZCkuPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyBJIGd1ZXNzIEkganVzdCBuZWVkIHRvIGhhdmUgbW9yZSBpbmZvIGFib3V0IGhvdyB0
aGlzIHdvdWxkIHdvcms8QlI+DQomZ3Q7IGJlZm9yZSBJPEJSPg0KJmd0OyZndDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgd2lsbCBiZSBjb252aW5jZWQgaXQgaXMgZmVhc2libGUgYW5kIHRydXN0
d29ydGh5LjxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyBXZWxsLCAn
dHJ1c3R3b3J0aHknIGNvdWxkIGJlJm5ic3A7IGNvbnNpZGVyZWQgaW4gbWFueSBhbmdsZXMuPEJS
Pg0KJmd0OyZndDsgSWYgaXQgaXMgYWJvdXQgcHJpdmFjeSBvZiB0aGUgbWVzc2FnZSwgYSBwdWJs
aWMga2V5IGJhc2VkIGVuY3J5cHRpb248QlI+DQomZ3Q7Jmd0OyB3b3VsZCBwcm92aWRlIGFjY2Vw
dGFibGUgcHJpdmFjeS48QlI+DQomZ3Q7Jmd0OyBJZiBpdCBpcyBhYm91dCByZWxpYWJpbGl0eSBv
ZiB0aGUgbWVzc2FnZSBkZWxpdmVyeSwgd2VsbCwgYSBQMlAgYmFzZWQ8QlI+DQomZ3Q7Jmd0OyBh
c3luY2hyb25vdXMgbWVzc2FnZSBkZWxpdmVyeSAobGlrZSBWTSkgaXMgbW9zdCBsaWtlbHkgbGVz
cyByZWxpYWJsZTxCUj4NCiZndDsmZ3Q7IHRoYW4gYSB3ZWxsIG1hbmFnZWQgc2VydmVyIGJhc2Vk
IHN5c3RlbS48QlI+DQomZ3Q7Jmd0OyBIb3dldmVyLCBteSBleHBlcmllbmNlIHdpdGggU2t5cGUn
cyBhc3luY2hyb25vdXMgbWVzc2FnZSBkZWxpdmVyeSB3YXM8QlI+DQomZ3Q7Jmd0OyBub3QgYmFk
LiBBY3R1YWxseSBJIGRvbid0IHNlZSBhbnkgc2lnbmlmaWNhbnQgZGlmZmVyZW5jZSBiZXR3ZWVu
IGl0PEJSPg0KJmd0OyBhbmQ8QlI+DQomZ3Q7Jmd0OyBteSBjZWxsdWxhciBzZXJ2aWNlIHByb3Zp
ZGVyJ3MgVk0gc2VydmljZS4gOi0pPEJSPg0KJmd0OyZndDsgUmVsaWFiaWxpdHkgaXMgYWx3YXlz
IGEgY2hhbGxlbmdlIGZvciBQMlAsIGZvciBzdXJlLiBCdXQsIEkgYmVsaWV2ZSBpdDxCUj4NCiZn
dDs8QlI+DQomZ3Q7Jmd0OyBpcyBmZWFzaWJsZSB0byBidWlsZCBhIFAyUCBzeXN0ZW0gZm9yIFZN
IGFjY2VwdGFibGUgZm9yIG1hbnk8QlI+DQomZ3Q7IHNjZW5hcmlvcy48QlI+DQomZ3Q7Jmd0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IC0gSW4gbW9iaWxlIG5ldHdvcmtzOiBU
aGUgVk0gY2FuIHJlc2lkZSBpbiBxdWl0ZSBzdGFibGUgcGVlcnM8QlI+DQomZ3Q7Jmd0OyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyBpbnNpZGUgdGhlPEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgJmd0OyB3aXJlbGVzcyBiYXNlIHN0YXRpb24gbmV0d29yay4gVGhl
IHBlZXJzIGluIHRoZSBiYXNlIHN0YXRpb248QlI+DQomZ3Q7IG5ldHdvcms8QlI+DQomZ3Q7Jmd0
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IG5lZWQgbm8gY29uZmlndXJhdGlv
biwgZXRjLjxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgSSBkb24ndCB1bmRlcnN0YW5kLiBJIGd1ZXNzIHRoYXQgY291bGQgYmUgdHJ1ZSBpZiB0aGUg
cGVlcnMgYXJlPEJSPg0KJmd0OyB3aWxsaW5nPEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgdG8gc3RvcmUgYW4gYXJiaXRyYXJ5IGFtb3VudCBvZiBWTSBpbmRlZmluaXRlbHkg
Zm9yIGFueWJvZHkuIElzPEJSPg0KJmd0OyB0aGF0PEJSPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgYmVsaWV2YWJsZT88QlI+DQomZ3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7PEJSPg0K
Jmd0OyZndDsgSXQgZGVwZW5kcy48QlI+DQomZ3Q7Jmd0OyBJbiBhIHZlcnkgbmljZSBlbnZpcm9u
bWVudCB3aGVyZSBhbGwgdGhlIHBlZXJzIGFyZSB3aWxsaW5nIHRvPEJSPg0KJmd0OyBjb29wZXJh
dGU8QlI+DQomZ3Q7Jmd0OyBhdCB0aGVpciBiZXN0LCB0aGUgcGVlcnMgd2lsbCBzdG9yZSBhcyBt
dWNoIGFzIHRoZXkgY2FuLiBJbiBhIHRvdWdoPEJSPg0KJmd0OyZndDsgZW52aXJvbm1lbnQsIHRo
ZSBzaXR1YXRpb24gd2lsbCBiZSBkaWZmZXJlbnQuPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBUaGlzIHNlZW1zIHRvIHRyYW5zbGF0ZSB0byBhIG1v
ZGVsIHdoZXJlIGl0IGlzIGFzc3VtZWQgdGhhdCB0aG9zZTxCUj4NCiZndDsgbm9kZXM8QlI+DQom
Z3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB0aGF0IGFyZSBvbiBtb3N0IG9mIHRoZSB0
aW1lIHdpbGwgYmUgd2lsbGluZyB0byBwcm92aWRlIFZNIHN0b3JhZ2U8QlI+DQomZ3Q7IGZvcjxC
Uj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRob3NlIG5vZGVzIHRoYXQgYXJl
bid0IG9uIG1vc3Qgb2YgdGhlIHRpbWUuPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OzxCUj4N
CiZndDsmZ3Q7IFRoaXMgaXMgYWdhaW4gcmVsYXRlZCB0byByZWxpYWJpbGl0eSBvZiBQMlAgc3lz
dGVtcyBvciB0b3BpY3MgbGlrZTxCUj4NCiZndDsgZnJlZTxCUj4NCiZndDsmZ3Q7IHJpZGVycyBh
bmQgcmVwdXRhdGlvbi48QlI+DQomZ3Q7Jmd0OyBBIFAyUCBzeXN0ZW0gaXMgYSBjb21tdW5pdHkg
b3Igc29jaWV0eS4gVG8gYmUgc2ltcGxlLCBpZiBtYW55IG9mIHRoZTxCUj4NCiZndDsmZ3Q7IG1l
bWJlcnMgYXJlIGJhZCwgdGhlIGNvbW11bml0eSB3b24ndCB3b3JrIHdlbGwuIElmIHRoZSBtYWpv
cml0eSBvZiB0aGU8QlI+DQomZ3Q7PEJSPg0KJmd0OyZndDsgbWVtYmVycyBhcmUgZ29vZCwgdGhl
IGNvbW11bml0eSB3aWxsIHdvcmsgd2VsbCBvciByZWFzb25hYmx5LjxCUj4NCiZndDsmZ3Q7PEJS
Pg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyBBZGQgdG8gdGhp
cyB0aGUgY29uZmVyZW5jaW5nIGNhcGFiaWxpdHkgY29taW5nIGZyb20gcDJwPEJSPg0KJmd0OyBh
cHBsaWNhdGlvbjxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZn
dDsgbGF5ZXIgbXVsdGljYXN0LCB0aGUgU0lQIGUyZSBjb250cm9sIGNhcGFiaWxpdGllcyAoZm9y
IHN1Y2ggYXM8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7
IGF1dG8tYXR0ZW5kYW50LCBhZ2VudCB3b3Jrc3RhdGlvbiwgZXRjLikgYW5kIG9uZSBoYXMgdG8g
d29uZGVyPEJSPg0KJmd0OyB3aHkgSVQ8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyAmZ3Q7IG5ldHdvcmtzLCBwdWJsaWMgVm9JUCBuZXR3b3JrcyBhbmQgZW5kIHVz
ZXJzIHNob3VsZCBzdXBwb3J0IHRoZTxCUj4NCiZndDsgaHVnZTxCUj4NCiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgY29zdCBvZiBoYW5kIGVuZ2luZWVyaW5nLCB0
ZXN0aW5nLCBtb25pdG9yaW5nLCBtYWludGFpbmluZzxCUj4NCiZndDsgc2VydmVyPEJSPg0KJmd0
OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgYmFzZWQ8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IFZvSVAgbmV0d29ya3MuIFAyUCBzZWxmIGNvbmZp
Z3VyYXRpb24gaXMgbm90aGluZyBsZXNzIHRoYXQ8QlI+DQomZ3Q7IGF1dG9tYXRpb248QlI+DQom
Z3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IGFwcGxpZWQgdG8gVm9J
UCwgcGx1cyB0aGUgc2hpZnRpbmcgb2YgY29tcHV0aW5nIHRvIHRoZTxCUj4NCiZndDsgZW5kcG9p
bnRzLDxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHdoZXJlPEJSPg0KJmd0
OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyB0aGVyZSBpcyBhbiBhYnVu
ZGFuY2Ugb2YgdW51c2VkIENQVSwgc3RvcmFnZSwgYmFuZHdpZHRoIGFuZDxCUj4NCiZndDsmZ3Q7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVsZWN0cmljaXR5LjxCUj4NCiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IEVyaWMgQnVyZ2VyIGFsc28gbm90ZXMgSU0gY2hhbmdlcyBj
b21wbGV0ZWx5IHRoZSB1c2FnZSBmb3IgVk08QlI+DQomZ3Q7IGFuZCBtYXk8QlI+DQomZ3Q7Jmd0
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IG1ha2UgdW5uZWNlc3NhcnkgdG8g
cGxhY2UgY2FsbHMgb24gVk0gaW4gdGhlIGZpcnN0IHBsYWNlLjxCUj4NCiZndDsmZ3Q7PEJSPg0K
Jmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgSSBmaW5kIHRoaXMgbW9yZSBwcm9taXNp
bmcuPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0
OyZndDs8QlI+DQomZ3Q7Jmd0OyBJbiBvdmVyYWxsLCBhcmUgd2UgZGlzY3Vzc2luZyBpZiBQMlAg
c3lzdGVtcyBiYXNlZCBWTSBjYW4gd29yaz8gSTxCUj4NCiZndDsgdGhpbms8QlI+DQomZ3Q7Jmd0
OyBpdCBjYW4gd29yay4mbmJzcDsgSnVzdCBpdCBkZXBlbmRzIG9uIG1hbnkgdGhpbmdzLjxCUj4N
CiZndDsmZ3Q7IElmIGl0IGlzIG5vdCBzdXBlci1yZWxpYWJsZSwgc2hvdWxkIHdlIGRpc3JlZ2Fy
ZCBpdD8gSSB3b3VsZCBzYXkgbm8uPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyBPbiB0aGUg
b3RoZXIgaGFuZCwgZG8gd2UgaGF2ZSB0byBhYmFuZG9uIGNsaWVudCBzZXJ2ZXIgYmFzZWQgVk0g
YW5kPEJSPg0KJmd0OyZndDsgc3dpdGNoIHRvIFAyUCBzeXN0ZW0gYmFzZWQgVk0/IEl0IGlzIHVw
dG8gZWFjaCBvZiB1cy48QlI+DQomZ3Q7Jmd0OyBDbGllbnQgc2VydmVyIGJhc2VkIFZNIHN5c3Rl
bXMgYXJlIGFscmVhZHkgdGhlcmUuPEJSPg0KJmd0OyZndDsgU28gd2h5IGRvbid0IHdlIHdvcmsg
b24gUDJQIGJhc2VkIFZNIG5vdz88QlI+DQomZ3Q7Jmd0OyZuYnNwOzxCUj4NCiZndDsmZ3Q7IFRo
YW5rcy48QlI+DQomZ3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7IEV1bnNvbzxCUj4NCiZndDs8QlI+DQo8
QlI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxCUj4N
ClAyUFNJUCBtYWlsaW5nIGxpc3Q8QlI+DQpQMlBTSVBAaWV0Zi5vcmc8QlI+DQo8QSBIUkVGPSJo
dHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wMnBzaXAiPmh0dHBzOi8vd3d3
MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3AycHNpcDwvQT48QlI+DQo8L0ZPTlQ+DQo8L1A+
DQoNCjwvQk9EWT4NCjwvSFRNTD4=

------_=_NextPart_001_01C7767B.8BBEF331--


--===============0100755479==
Content-Type: text/plain; charset="us-ascii"
M5vZGVzIHRoYXQgYXJl
bid0IG9uIG1vc3Qgb2YgdGhlIHRpbWUuPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OzxCUj4N
CiZndDsmZ3Q7IFRoaXMgaXMgYWdhaW4gcmVsYXRlZCB0byByZWxpYWJpbGl0eSBvZiBQMlAgc3lz
dGVtcyBvciB0b3BpY3MgbGlrZTxCUj4NCiZndDsgZnJlZTxCUj4NCiZndDsmZ3Q7IHJpZGVycyBh
bmQgcmVwdXRhdGlvbi48QlI+DQomZ3Q7Jmd0OyBBIFAyUCBzeXN0ZW0gaXMgYSBjb21tdW5pdHkg
b3Igc29jaWV0eS4gVG8gYmUgc2ltcGxlLCBpZiBtYW55IG9mIHRoZTxCUj4NCiZndDsmZ3Q7IG1l
bWJlcnMgYXJlIGJhZCwgdGhlIGNvbW11bml0eSB3b24ndCB3b3JrIHdlbGwuIElmIHRoZSBtYWpv
cml0eSBvZiB0aGU8QlI+DQomZ3Q7PEJSPg0KJmd0OyZndDsgbWVtYmVycyBhcmUgZ29vZCwgdGhl
IGNvbW11bml0eSB3aWxsIHdvcmsgd2VsbCBvciByZWFzb25hYmx5LjxCUj4NCiZndDsmZ3Q7PEJS
Pg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyBBZGQgdG8gdGhp
cyB0aGUgY29uZmVyZW5jaW5nIGNhcGFiaWxpdHkgY29taW5nIGZyb20gcDJwPEJSPg0KJmd0OyBh
cHBsaWNhdGlvbjxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZn
dDsgbGF5ZXIgbXVsdGljYXN0LCB0aGUgU0lQIGUyZSBjb250cm9sIGNhcGFiaWxpdGllcyAoZm9y
IHN1Y2ggYXM8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7
IGF1dG8tYXR0ZW5kYW50LCBhZ2VudCB3b3Jrc3RhdGlvbiwgZXRjLikgYW5kIG9uZSBoYXMgdG8g
d29uZGVyPEJSPg0KJmd0OyB3aHkgSVQ8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyAmZ3Q7IG5ldHdvcmtzLCBwdWJsaWMgVm9JUCBuZXR3b3JrcyBhbmQgZW5kIHVz
ZXJzIHNob3VsZCBzdXBwb3J0IHRoZTxCUj4NCiZndDsgaHVnZTxCUj4NCiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgY29zdCBvZiBoYW5kIGVuZ2luZWVyaW5nLCB0
ZXN0aW5nLCBtb25pdG9yaW5nLCBtYWludGFpbmluZzxCUj4NCiZndDsgc2VydmVyPEJSPg0KJmd0
OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgYmFzZWQ8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IFZvSVAgbmV0d29ya3MuIFAyUCBzZWxmIGNvbmZp
Z3VyYXRpb24gaXMgbm90aGluZyBsZXNzIHRoYXQ8QlI+DQomZ3Q7IGF1dG9tYXRpb248QlI+DQom
Z3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IGFwcGxpZWQgdG8gVm9J
UCwgcGx1cyB0aGUgc2hpZnRpbmcgb2YgY29tcHV0aW5nIHRvIHRoZTxCUj4NCiZndDsgZW5kcG9p
bnRzLDxCUj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHdoZXJlPEJSPg0KJmd0
OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyB0aGVyZSBpcyBhbiBhYnVu
ZGFuY2Ugb2YgdW51c2VkIENQVSwgc3RvcmFnZSwgYmFuZHdpZHRoIGFuZDxCUj4NCiZndDsmZ3Q7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVsZWN0cmljaXR5LjxCUj4NCiZndDsmZ3Q7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IEVyaWMgQnVyZ2VyIGFsc28gbm90ZXMgSU0gY2hhbmdlcyBj
b21wbGV0ZWx5IHRoZSB1c2FnZSBmb3IgVk08QlI+DQomZ3Q7IGFuZCBtYXk8QlI+DQomZ3Q7Jmd0
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IG1ha2UgdW5uZWNlc3NhcnkgdG8g
cGxhY2UgY2FsbHMgb24gVk0gaW4gdGhlIGZpcnN0IHBsYWNlLjxCUj4NCiZndDsmZ3Q7PEJSPg0K
Jmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgSSBmaW5kIHRoaXMgbW9yZSBwcm9taXNp
bmcuPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0
OyZndDs8QlI+DQomZ3Q7Jmd0OyBJbiBvdmVyYWxsLCBhcmUgd2UgZGlzY3Vzc2luZyBpZiBQMlAg
c3lzdGVtcyBiYXNlZCBWTSBjYW4gd29yaz8gSTxCUj4NCiZndDsgdGhpbms8QlI+DQomZ3Q7Jmd0
OyBpdCBjYW4gd29yay4mbmJzcDsgSnVzdCBpdCBkZXBlbmRzIG9uIG1hbnkgdGhpbmdzLjxCUj4N
CiZndDsmZ3Q7IElmIGl0IGlzIG5vdCBzdXBlci1yZWxpYWJsZSwgc2hvdWxkIHdlIGRpc3JlZ2Fy
ZCBpdD8gSSB3b3VsZCBzYXkgbm8uPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyBPbiB0aGUg
b3RoZXIgaGFuZCwgZG8gd2UgaGF2ZSB0byBhYmFuZG9uIGNsaWVudCBzZXJ2ZXIgYmFzZWQgVk0g
YW5kPEJSPg0KJmd0OyZndDsgc3dpdGNoIHRvIFAyUCBzeXN0ZW0gYmFzZWQgVk0/IEl0IGlzIHVw
dG8gZWFjaCBvZiB1cy48QlI+DQomZ3Q7Jmd0OyBDbGllbnQgc2VydmVyIGJhc2VkIFZNIHN5c3Rl
bXMgYXJlIGFscmVhZHkgdGhlcmUuPEJSPg0KJmd0OyZndDsgU28gd2h5IGRvbid0IHdlIHdvcmsg
b24gUDJQIGJhc2VkIFZNIG5vdz88QlI+DQomZ3Q7Jmd0OyZuYnNwOzxCUj4NCiZndDsmZ3Q7IFRo
YW5rcy48QlI+DQomZ3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7IEV1bnNvbzxCUj4NCiZndDs8QlI+DQo8
QlI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxCUj4N
ClAyUFNJUCBtYWlsaW5nIGxpc3Q8QlI+DQpQMlBTSVBAaWV0Zi5vcmc8QlI+DQo8QSBIUkVGPSJo
dHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wMnBzaXAiPmh0dHBzOi8vd3d3
MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3AycHNpcDwvQT48QlI+DQo8L0ZPTlQ+DQo8L1A+
DQoNCjwvQk9EWT4NCjwvSFRNTD4=

------_=_NextPart_001_01C7767B.8BBEF331--


--===============0100755479==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0100755479==--




IME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0100755479==--




From sipping-bounces@ietf.org Wed Apr 04 03:18:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzj8-00051H-QA; Wed, 04 Apr 2007 03:16:18 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYkJQ-0005R9-EW; Tue, 03 Apr 2007 10:48:44 -0400
Received: from canitpro.objectworld.com ([72.1.207.100])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HYkJA-00030Z-E4; Tue, 03 Apr 2007 10:48:44 -0400
Received: from photon.objectworld.com (photon.objectworld.com [10.10.8.2])
	by canitpro.objectworld.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP
	id l33EmBGj022963; Tue, 3 Apr 2007 10:48:11 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 3 Apr 2007 10:48:05 -0400
Message-ID: <4E2DC1ACE541B94A946B8D8657E372C57A903F@photon.objectworld.com>
In-Reply-To: <46124F38.7020005@cisco.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Thread-Index: Acd176Ya+p6xqIGMQfSJrn6cLV80rgACgCmQ
References: <24CCCC428EFEA2469BF046DB3C7A8D225274F4@namail5.corp.adobe.com>	
	<EC0E1E0E-2E83-4674-BAC0-78CB94F0BD43@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADECA@namail5.corp.adobe.com>	
	<4FF5FA52-1B38-4964-87AE-72300CE89A1F@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADED9@namail5.corp.adobe.com>	
	<460D4825.2090800@cisco.com>	
	<7b683f3f0703301556j95f2c10sf12d666994dedf6f@mail.gmail.com>	
	<460D9D9C.1040304@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com>	
	<46118DA0.4070305@cisco.com>
	<1fc32c8f0704021813h4387c0c4uec60e7aa3f75606c@mail.gmail.com>
	<46124F38.7020005@cisco.com>
From: "Michael Slavitch" <slavitch@objectworld.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-Spam-Score: 1.50 (*) [Tag at 20.00] EXTRA_MPART_TYPE, HTML_MESSAGE, SPF(none,
	0.1), 132(0.3), 131(0.3)
X-CanItPRO-Stream: outgoing (inherits from default)
X-Scanned-By: CanIt (www . roaringpenguin . com) on 10.10.8.9
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7323bea1d74976e0b97632725f4fc47a
X-Mailman-Approved-At: Wed, 04 Apr 2007 03:16:14 -0400
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	David R Oran <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org,
	zhuxian <zhuxian@huawei.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2083950269=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2083950269==
Content-class: urn:content-classes:message
Content-Type: multipart/related; type="multipart/alternative";
	boundary="----_=_NextPart_001_01C775FF.19CEFDE7"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C775FF.19CEFDE7
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C775FF.19CEFDE7"


------_=_NextPart_002_01C775FF.19CEFDE7
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64
Content-Disposition: inline

VGhlIHBvaW50IEkgYW0gbWFraW5nIGlzICB0aGF0IGluIHRoZSBlbnRlcnBy
aXNlIHRoZSBhY3R1YWwgdG9wb2xvZ2ljYWwgZGVwbG95bWVudHMgb2YgU0lQ
IGNsaWVudHMgYW5kIHNlcnZlcnMsIHdoZW4gaW1wbGVtZW50ZWQgYXMgc29m
dHdhcmUgb24gZ2VuZXJpYyBjb21wdXRpbmcgcGxhdGZvcm1zLCBhcyB3ZWxs
IGFzIHRoZSBtZWNoYW5pc21zIHRoYXQgbWFrZSB0aGF0IGRlcGxveW1lbnQg
aGFwcGVuLCBhcmUgYWxyZWFkeSB2ZXJ5IGRpZmZlcmVudCB3b3JsZCB0aGFu
IHRoZSBjYW5vbmljYWwgSU1TL0NTU0lQIG9uZSB3aGljaCAgYXNzdW1lcyBT
SVAgYXMgY29yZSBtbFrom sipping-bounces@ietf.org Wed Apr 04 03:18:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzj8-00051H-QA; Wed, 04 Apr 2007 03:16:18 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYkJQ-0005R9-EW; Tue, 03 Apr 2007 10:48:44 -0400
Received: from canitpro.objectworld.com ([72.1.207.100])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HYkJA-00030Z-E4; Tue, 03 Apr 2007 10:48:44 -0400
Received: from photon.objectworld.com (photon.objectworld.com [10.10.8.2])
	by canitpro.objectworld.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP
	id l33EmBGj022963; Tue, 3 Apr 2007 10:48:11 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 3 Apr 2007 10:48:05 -0400
Message-ID: <4E2DC1ACE541B94A946B8D8657E372C57A903F@photon.objectworld.com>
In-Reply-To: <46124F38.7020005@cisco.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Thread-Index: Acd176Ya+p6xqIGMQfSJrn6cLV80rgACgCmQ
References: <24CCCC428EFEA2469BF046DB3C7A8D225274F4@namail5.corp.adobe.com>	
	<EC0E1E0E-2E83-4674-BAC0-78CB94F0BD43@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADECA@namail5.corp.adobe.com>	
	<4FF5FA52-1B38-4964-87AE-72300CE89A1F@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADED9@namail5.corp.adobe.com>	
	<460D4825.2090800@cisco.com>	
	<7b683f3f0703301556j95f2c10sf12d666994dedf6f@mail.gmail.com>	
	<460D9D9C.1040304@cisco.com>	
	<24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com>	
	<46118DA0.4070305@cisco.com>
	<1fc32c8f0704021813h4387c0c4uec60e7aa3f75606c@mail.gmail.com>
	<46124F38.7020005@cisco.com>
From: "Michael Slavitch" <slavitch@objectworld.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-Spam-Score: 1.50 (*) [Tag at 20.00] EXTRA_MPART_TYPE, HTML_MESSAGE, SPF(none,
	0.1), 132(0.3), 131(0.3)
X-CanItPRO-Stream: outgoing (inherits from default)
X-Scanned-By: CanIt (www . roaringpenguin . com) on 10.10.8.9
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7323bea1d74976e0b97632725f4fc47a
X-Mailman-Approved-At: Wed, 04 Apr 2007 03:16:14 -0400
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	David R Oran <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org,
	zhuxian <zhuxian@huawei.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2083950269=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2083950269==
Content-class: urn:content-classes:message
Content-Type: multipart/related; type="multipart/alternative";
	boundary="----_=_NextPart_001_01C775FF.19CEFDE7"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C775FF.19CEFDE7
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C775FF.19CEFDE7"


------_=_NextPart_002_01C775FF.19CEFDE7
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64
Content-Disposition: inline

VGhlIHBvaW50IEkgYW0gbWFraW5nIGlzICB0aGF0IGluIHRoZSBlbnRlcnBy
aXNlIHRoZSBhY3R1YWwgdG9wb2xvZ2ljYWwgZGVwbG95bWVudHMgb2YgU0lQ
IGNsaWVudHMgYW5kIHNlcnZlcnMsIHdoZW4gaW1wbGVtZW50ZWQgYXMgc29m
dHdhcmUgb24gZ2VuZXJpYyBjb21wdXRpbmcgcGxhdGZvcm1zLCBhcyB3ZWxs
IGFzIHRoZSBtZWNoYW5pc21zIHRoYXQgbWFrZSB0aGF0IGRlcGxveW1lbnQg
aGFwcGVuLCBhcmUgYWxyZWFkeSB2ZXJ5IGRpZmZlcmVudCB3b3JsZCB0aGFu
IHRoZSBjYW5vbmljYWwgSU1TL0NTU0lQIG9uZSB3aGljaCAgYXNzdW1lcyBT
SVAgYXMgY29yZSBtb25vbGl0aGljIHNlcnZlcnMsIGZpeGVkIGVudGVycHJp
c2UgbmV0d29yayBpbnRlZ3JhdGVkIGFjY2VzcyBkZXZpY2VzIChJQUQpLCAg
QjJCVUEgZGVtYXJrcywgbmV0d29yayBlbGVtZW50cywgYW5kIGR1bWIgZml4
ZWQgZW5kcG9pbnRzLiAgVGFraW5nIGEgbmV0d29yayBhcyBhIHdob2xlIGVu
dGVycHJpc2UgYXBwbGljYXRpb24gc29mdHdhcmUgdXNpbmcgQy9TIFNJUCBw
cm94aWVzIGFuZCBVQeKAmXMgYWxyZWFkeSBhcHByb3hpbWF0ZXMgc29tZXRo
aW5nIHRoYXQgaXMgY2xvc2UgdG8gd2hhdCBpcyBiZWluZyBjYWxsZWQgUDJQ
U0lQLCBvbmx5IGluIGEgbWFubmVyIHRoYXQgaXMgaGlnaGx5IHByb3ByaWV0
YXJ5LCBjbG9zZWQsIHNvbWV3aGF0IGJyaXR0bGUgYW5kIGJhcm9xdWUsIGxv
Y2FsLCBhbmQgYWQtaG9jLCB3aXRoIGdhcGluZyB1Z2x5IGhvbGVzLiAgUDJQ
IGhhcyB0aGUgcG90ZW50aWFsIHRvIHRyYW5zZm9ybSB0aGF0Lg0KDQogDQoN
ClNvbWUgcG9pbnRzIEkgdGFrZSBmcm9tIHRoZSBwcmV2aW91cyBkaXNjdXNz
aW9uOg0KDQoNCg0K4oCcdGhhdCBhIFAyUCBzZXR1cCB3aWxsIGJlICpmcmVl
KuKAnQ0KDQogDQoNCi0gICAgICAgICAgIEEgUDJQIG5ldHdvcmsgbWF5IG5v
dCBiZSBmcmVlLCBidXQgdGhlIHNldHVwIChwcm92aXNpb25pbmcpIHdpbGwg
YmUgZnJlZSwgYW5kIGF1dG9tYXRpYy4gIFRoaXMgaXMgYSBtYWpvciBiZW5l
Zml0IG9ubHkgcGFydGlhbGx5IGFjaGlldmVkIGluIGVudGVycHJpc2UgbmV0
d29ya3MsICBhIGJlbmVmaXQgb2YgZ3JlYXQgdmFsdWUgdG8gZW50ZXJwcmlz
ZXMgdGhhdCBpcyB1bmRlcnNlcnZlZCBieSB2ZW5kb3JzLiAgVGhlcmUgaXMg
bm8gYmVuZWZpdCBpbiByZXF1aXJpbmcgY29tcGxleCBkZXBsb3ltZW50cyB3
aGVyZSBhdXRvbWF0aW9uIGNhbiB0YWtlIGl0cyBwbGFjZS4gIERlcGxveW1l
bnQgaXMgYWxtb3N0IGFsd2F5cyB0aGUgYmlnZ2VzdCBjb3N0IG9mIGVudGVy
cHJpc2Ugc3lzdGVtcyBkd2FyZmluZyB0aGUgY29zdCBvZiB0aGUgc3lzdGVt
cyB0aGVtc2VsdmVzLg0KDQogDQoNCuKAnEkgdGhpbmsgdGhpcyBkZXBlbmRz
IGdyZWF0bHkgb24gd2hhdCBleHBlY3RhdGlvbnMgLyBjb250cmFjdHVhbCBn
dWFyYW50ZWVzIHRoZSBlbnRlcnByaXNlIGhhcy4gSXTigJlzIHVuY2xlYXIg
dG8gbWUgd2hhdCBndWFyYW50ZWVzIGNhbiBiZSBtYWRlIGFib3V0IGEgUDJQ
U0lQIG5ldHdvcmsgd2lsbCBiZSBhYmxlIHRvIG1ha2UsIGFuZCBpdHMgdW5j
bGVhciB3aGF0IGtpbmQgb2YgaW5mcmFzdHJ1Y3R1cmUgd291bGQgYmUgaW5z
dGFsbGVkIGJ5L2ZvciBzb21lb25lIHdpbGxpbmcgdG8gbWFrZSBndWFyYW50
ZWVzLuKAnQ0KDQogDQoNCi0gICAgICAgICAgVGhhdCBpcyB3aHkg4oCYZXhw
ZWN0YXRpb25zL2NvbnRyYWN0dWFsIGd1YXJhbnRlZXPigJkgbmVlZCB0byBi
ZSBidWlsdCBpbnRvIHRoZSBhdXRvbWF0aW9uIHRoYXQgZXhpc3RzIGluIHRo
ZSBQMlAgb3ZlcmxheS4gIFNlbGYtY2FsY3VsYXRpb24gb2Ygc3VjaCBwZXJm
b3JtYW5jZSBtZXRyaWNzIGlzIGFscmVhZHkgdGhlcmUgaW4gYWxsIGVudGVy
cHJpc2UgZGV2aWNlcywgdGhlIGRpZmZlcmVuY2UgYmVpbmcgdGhhdCB3aGls
ZSBXTUkvU05NUCBkYXRhIGlzIG1lcmVseSBjb2xsZWN0ZWQgYSBQMlBTSVAg
bmV0d29yayBjYW4gYWN0IGF1dG9tYXRpY2FsbHkgYmFzZWQgb24gdGhlIG1l
dHJpY3Mgd2l0aGluIHRoZWlyIG93biBub2RlcywgdGhlcmUgaXMgYSBjb2xs
ZWN0aXZlIOKAmGFoYeKAmSB0aGF0IGZvcmNlcyBiZWhhdmlvciBjaGFuZ2Ug
YmFzZWQgb24gc3RyaWN0IGNvbnRyYWN0cywgYWthIHJ1bGVzLiAgQW4gU0xB
IGlzIGVhc2llciB0byBtYWludGFpbiBpZiB0aGUgb2JqZWN0cyBjYW4gcmVh
Y3QgYWNjb3JkaW5nbHksIGZvciBleGFtcGxlIGEgbm9kZSB3aXRoIGRlZ3Jh
ZGluZyBzZXJ2aWNlIGNhbiBub3RpZnkgdGhhdCBpdCBpcyBvbiB0aGUgZGVj
bGluZSBmb3JjaW5nIG90aGVycyB0byB0YWtlIG92ZXIuICANCg0KIA0KDQpU
aGVyZSBpcyBhbiBvbGQgdHJhZmZpYyBlbmdpbmVlcmluZyBheGlvbSBhYm91
dCBzZXJ2aWNlIGd1YXJhbnRlZXM6IGl0IGNhbiBiZSBhY2hpZXZlZCB0aHJv
dWdoIHR3byB3YXlzOiBvdmVyIGVuZ2luZWVyaW5nIG9yICBhdXRvbWF0aW9u
LiAgUDJQU0lQIGFsbG93cyBmb3IgYXV0b21hdGlvbi4NCg0KIA0KDQogRGF2
aWQgT3JhbiB3cm90ZToNCg0KIA0KDQrigJxJJ20gbm90IHNheWluZyB0aGlz
IGNhbid0IGJlIG1hZGUgdG8gd29yaywgb25seSB0aGF0IGl0IGlzbid0IGlt
bWVkaWF0ZWx5IG9idmlvdXMgdGhhdCBpdCBoYXMgYWR2YW50YWdlcyBvdmVy
IGEgY2xhc3NpYyBhcHBsaWNhdGlvbi9zZXJ2ZXIgYXBwcm9hY2gu4oCdDQoN
CiANCg0KVGhlIGltbWVkaWF0ZWx5IG9idmlvdXMgYWR2YW50YWdlIHRvIG1l
IGlzIHN0YW5kYXJkaXplZCBydWdnZWRpemVkIGF1dG9tYXRpb24gdGhhdCBo
YXMgZWNvbm9taWVzIG9mIHNjYWxlIGFuZCBvcGVyYXRlcyBvdmVyIG11bHRp
cGxlIGRvbWFpbnMsIGVsaW1pbmF0aW5nIHRoZSBuZWVkIGZvciBvdmVyLWVu
Z2luZWVyaW5nLCAgZGV0YWlsZWQgZnVzc3kgcHJvdmlzaW9uaW5nLCAgYW5k
IGFuIGFybXkgb2YgcGVvcGxlIGRvaW5nIGJhc2ljIG1vbml0b3JpbmcgYW5k
IGNhcmUtYW5kLWZlZWRpbmcuICBBdXRvbWF0aW9uIGlzIHRoZSBrZXksIGEg
ZHluYW1pYyBzdGF0aXN0aWNhbCBuZXR3b3JrIHZzLiBvbmUgdGhhdCBpcyBm
aXhlZCBhbmQgYXNzdW1lZCBkZXRlcm1pbmlzdGljIHdpbGwgYWx3YXlzIHdp
biBvdXQgb3ZlciB0aW1lIGdpdmVuIGEgZnJhY3RhbCBvcGVyYXRpbmcgZW52
aXJvbm1lbnQuICAgVGhpcyBpcyBiZWluZyBkb25lIGluIGZpdHMgYW5kIHN0
YXJ0cyBpbiB0aGUgZW50ZXJwcmlzZSBkYXRhIGNlbnRlci4gICBQMlBTSVAg
bWFrZXMgaXQgbXVjaCBtb3JlIGNvbXByZWhlbnNpdmUuICAgUGVvcGxlIHdh
bnQgdGhlIHdvcmxkIHRvIGJlIHByZWRpY3RhYmxlIGFuZCBkZXRlcm1pbmlz
dGljLCAgYW5kIEMvUyBiYXNlZCBzeXN0ZW1zIHJlZmxlY3QgdGhhdC4gVGhh
dCBpcyB0aGUgYmlnZ2VzdCBwcm9ibGVtIFAyUCBmYWNlcyBiZWNhdXNlIGl0
IGZsaWVzIGluIHRoZSBmYWNlIG9mIHRyYWRpdGlvbi4gICANCg0KIA0KDQpS
ZWdhcmRzDQoNCiANCg0KTWljaGFlbCBTbGF2aXRjaA0KDQogDQoNCiANCg0K
IA0KDQogDQoNCiANCg0KICA8aHR0cDovL3d3dy5vYmplY3R3b3JsZC5jb20v
PiANCg0KIA0KDQozMDggTGVnZ2V0IERyLiANCk90dGF3YSBPbnRhcmlvIA0K
SzJLIDFZNiBDYW5hZGENCg0KICA8aHR0cDovL21hcHMuZ29vZ2xlLmNhL21h
cHM/Zj1xJmhsPWVuJnE9MzA4K0xlZ2dldCtEcml2ZStPdHRhd2ErT250YXJp
bytLMksrMVk2JmxheWVyPSZzbGw9NDUuMzQxMDYxLC03NS45MDQ1NDEmc3Nw
bj0wLjAwNzExOSwwLjAyMzgzOSZpZT1VVEY4Jno9MTgmbGw9NDUuMzQxMDYx
LC03NS45MDQ1NDEmc3BuPTAuMDAxNzgsMC4wMDU5NiZ0PWgmb209MT4gDQoN
CiAJIA0KTWljaGFlbCBTbGF2aXRjaCAgICAgICAgICAgICAgDQoNCkxlYWQs
IFRlY2hub2xvZ3kgSW5pdGlhdGl2ZXMNCg0Kc2xhdml0Y2hAb2JqZWN0d29y
bGQuY29tDQoNClBTVE46ICANCg0KKzEuODg4LjM5OC45Njk4DQoNCngyMjUN
Cg0KRmF4Og0KDQorMS42MTMuNTk5Ljc0NTcNCg0KIA0KDQpTa3lwZTogICAg
ICAgDQoNCiBPYmplY3R3b3JsZCAgIA0KDQp4MjI1DQoNCiAgPHNreXBlOk9i
amVjdHdvcmxkPiANCg0KIAkgDQoNCiANCg0KIA0KDQotLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KRnJvbTogUGF1bCBLeXppdmF0IFttYWlsdG86cGt5
eml2YXRAY2lzY28uY29tXSANClNlbnQ6IFR1ZXNkYXksIEFwcmlsIDAzLCAy
MDA3IDg6NTcgQU0NClRvOiBNaWNoYWVsIFNsYXZpdGNoDQpDYzogSGVucnkg
U2lubnJlaWNoOyBQMlBTSVAgTWFpbGluZyBMaXN0OyBNaWNoYWVsIEhhbW1l
ciAobWhhbW1lcik7IERhdmlkIFIgT3JhbjsgcDJwcmdAaWV0Zi5vcmc7IHNp
cHBpbmdAaWV0Zi5vcmc7IHpodXhpYW4NClN1YmplY3Q6IFJlOiBbUDJQcmdd
IFJFOiBbU2lwcGluZ10gU2ltcGxlIFNJUCB1c2FnZSBzY2VuYXJpbw0KDQog
DQoNCiANCg0KIA0KDQpNaWNoYWVsIFNsYXZpdGNoIHdyb3RlOg0KDQo+IFNv
cnJ5IGZvciBiZWluZyBsYXRlIGludG8gdGhpcyBkaXNjdXNzaW9uLCBidXQg
Y2xpZW50LXNlcnZlciBiYXNlZCBWTSANCg0KPiBpc24ndCB0cnVseSBjbGll
bnQtc2VydmVyIGFueW1vcmUgaW4gYW55dGhpbmcgYnV0IHRoZSBzbWFsbGVz
dCBvciBtb3N0IA0KDQo+IG1vbm9saXRoaWMgb2YgZW50ZXJwcmlzZSBuZXR3
b3JrcywgaW4gZmFjdCB0aGUgcmVhbGl0eSBpcyB0aGF0IG1vc3QgaWYgDQoN
Cj4gbm90IGFsbCBlbnRlcnByaXNlIG5ldHdvcmtzIGNvbnRhaW4ganVzdCBw
ZWVycyBhbmQgc3VwZXJwZWVycyB3aXRoIHRoZSANCg0KPiBkaWZmZXJlbmNl
IGJlaW5nIHBhcnRpYWxseSBhIG1hcmtldGluZyBkZWNpc2lvbiBieSB0aGUg
dmVuZG9ycywgYXMgeW91IA0KDQo+IGNhbiBjaGFyZ2UgbXVjaCBtb3JlIGZv
ciB0aGUgc2VydmVycywgYW5kIGEgcG9saWN5IGRlY2lzaW9uIG1hZGUgZWl0
aGVyIA0KDQo+IGF1dG9tYXRpY2FsbHkgYnkgYSBzb2Z0d2FyZSBkZXBsb3lt
ZW50IHN5c3RlbSBvciBieSBJVCBzdGFmZiB3aGljaCB3YW50cyANCg0KPiB0
byBwbGFjZSBzdXBlcm5vZGVzIHdpdGggZGF0YSBzaW5rcyBvbiBhcHByb3By
aWF0ZSBlcXVpcG1lbnQuDQoNCiANCg0KSSdtIHNvcnJ5LCBidXQgSSBkb24n
dCB1bmRlcnN0YW5kIHRoZSBwb2ludCB5b3UgYXJlIHRyeWluZyB0byBtYWtl
IA0KDQphYm92ZS4gWW91IGFyZSB0cnlpbmcgdG8gZHJhdyBzb21lIHNvcnQg
b2YgZGlzdGluY3Rpb24sIGJ1dCBJIGRvbid0IGdldCANCg0KaXQuIENhbiB5
b3UgdHJ5IGFnYWluLg0KDQogDQoNCiAgICAgICAgICAgICAgICBUaGFua3Ms
DQoNCiAgICAgICAgICAgICAgICBQYXVsDQoNCiANCg0KPiBJbiBhIA0KDQo+
IGhpZ2hseSBkaXN0cmlidXRlZCBlbnZpcm9ubWVudCB0aGVyZSBhcmUgcG90
ZW50aWFsbHkgaHVuZHJlZHMgb2YgDQoNCj4gcG9zc2libGUgZGF0YSBzaW5r
cyBmb3IgYSBnaXZlbiBhcHBsaWNhdGlvbiwgd2l0aCB0aGUgc2luayBiYXNl
ZCBvbiANCg0KPiBzdWJuZXQgb3IgZ2VvZ3JhcGhpYyBsb2NhdGlvbiBvciBi
YWxhbmNlZCBsb2FkLCB0aGlzIGNhbiBjaGFuZ2UgcmFwaWRseSANCg0KPiBv
dmVyIHRpbWUgYW5kIGRvZXMuDQoNCj4gDQoNCj4gSW4gdGhlIGNhc2Ugb2Yg
dGhlIE1pY3Jvc29mdCBlbnZpcm9ubWVudCBzdWNoIHBvbGljeSBpcyBhZG1p
bmlzdGVyZWQgYW5kIA0KDQo+IHB1Ymxpc2hlZCBiZXR3ZWVuIHN1cGVybm9k
ZXMsIGllIHNlcnZlcnMsIGJ5IEFjdGl2ZSBEaXJlY3RvcnkuICBJdCBpcyAN
Cg0KPiBhZHZlcnRpc2VkIHRvIG1lcmUgcGVlcnMgdGhyb3VnaCBETlMuICBU
aGVyZSB3YXMgbXVjaCBkaXNjdXNzaW9uIGEgd2hpbGUgDQoNCj4gYWdvIGFi
b3V0IGJ1aWxkaW5nIHNlcnZpY2UgZGlzY292ZXJ5IGVudmlyb25tZW50IHVz
aW5nIEROUyBpbnN0ZWFkIG9mIGEgDQoNCj4gUDJQIERIVC4gIEl0IGNhbiBi
ZSBhcmd1ZWQgdGhhdCBhIGNhc2Ugc3R1ZHkgb2YgYSBQMlAgZXhhbXBsZSBk
b25lIHVzaW5nIA0KDQo+IEROUyBpcyBhbnkgbGFyZ2UgV2luZG93cyBTZXJ2
ZXIgMjAwMyBiYXNlZCBNaWNyb3NvZnQgbmV0d29yayB3aXRoIG1hbnkgDQoN
Cj4gc2VydmVycyBhbmQgbWFueSBtb3JlIGNsaWVudHMgdGhhdCBhbHNvIHJ1
biBhcHBsaWNhdGlvbnMgdGhlbXNlbHZlcyBhbmQgDQoNCj4gYXJlIG5vdCBq
dXN0IGR1bWIgdGVybWluYWxzLiBUaGlzIGlzIGFsbW9zdCBjZXJ0YWlubHkg
YWx3YXlzIHRoZSBjYXNlIGluIA0KDQo+IGFsbCBlbnRlcnByaXNlcy4gVGhl
IGJpZyBkaWZmZXJlbmNlIGJldHdlZW4gQy9TIFNJUCBhbmQgUDJQU0lQIGlz
IA0KDQo+IGF1dG9tYXRpb24uIFdoYXQgaXMgdHJ1ZSBpcyB0aGF0IHRoZSBz
cXVhcmUgcGVnIGluIHJvdW5kIGhvbGUgb2YgDQoNCj4gb3ZlcmxvYWRpbmcg
RE5TIG1ha2VzIGRlcGxveW1lbnRzIGNsdW1zeSBhbmQgYnJpdHRsZSB3aXRo
aW4gdGhlIA0KDQo+IGVudGVycHJpc2UgZG9tYWluIGFuZCBjb21wbGV0ZWx5
IHVubWFuYWdlYWJsZSBhbmQgdW5wdWJsaXNoYWJsZSBvdXRzaWRlIA0KDQo+
IHRoZSBmaXJld2FsbCB3aGljaCBpcyB3aHkgdGhlIGJ1Y2sgc3RvcHMgdGhl
cmUgaW4gY3VycmVudCBlbnRlcnByaXNlIA0KDQo+IG5ldHdvcmtpbmcgcHJv
ZHVjdHMuDQoNCj4gDQoNCj4gVGhlIGRpZmZlcmVuY2UgYmV0d2VlbiBDL1Mg
YW5kIFAyUCBpcyBsYXJnZWx5IHBvbGljeSBhbmQgc2VtYW50aWNzIHdpdGgg
DQoNCj4gdGhlIGJpZ2dlc3QgZGlmZmVyZW5jZSBiZWluZyB0aGF0IHRoZSBk
ZWNpc2lvbnMgYW5kIHJ1bGVzIGFyZSBoaWdobHkgDQoNCj4gZGlzdHJpYnV0
ZWQuICBBcGFydCBmcm9tIHRoYXQgdGhleSBhcmUgbm90IGp1c3QgZnJpZW5k
cywgdGhleSBhcmUgDQoNCj4gZnJhdGVybmFsIHR3aW5zLg0KDQo+IA0KDQo+
IFJlZ2FyZHMNCg0KPiANCg0KPiBNaWNoYWVsIFNsYXZpdGNoDQoNCj4gDQoN
Cj4gIA0KDQo+IA0KDQo+IA0KDQo+IGNvcnBfMmNvbG91ciANCg0KPiA8aHR0
cHM6Ly9maXJld2FsbC5vYmplY3R3b3JsZC5jb20vZXhjaHdlYi9iaW4vcmVk
aXIuYXNwP1VSTD1odHRwOi8vd3d3Lm9iamVjdHdvcmxkLmNvbS8+DQoNCj4g
DQoNCj4gIA0KDQo+IA0KDQo+ICAgICAgICAgICAgIA0KDQo+IA0KDQo+IDMw
OCBMZWdnZXQgRHIuDQoNCj4gT3R0YXdhIE9udGFyaW8NCg0KPiBLMksgMVk2
IENhbmFkYQ0KDQo+IA0KDQo+ICAgICAgICAgICAgIA0KDQo+IA0KDQo+IDxo
dHRwczovL2ZpcmV3YWxsLm9iamVjdHdvcmxkLmNvbS9leGNod2ViL2Jpbi9y
ZWRpci5hc3A/VVJMPWh0dHA6Ly9tYXBzLmdvb2dsZS5jYS9tYXBzP2Y9cSUy
NmhsPWVuJTI2cT0zMDglMkJMZWdnZXQlMkJEcml2ZSUyQk90dGF3YSUyQk9u
dGFyaW8lMkJLMkslMkIxWTYlMjZsYXllcj0lMjZzbGw9NDUuMzQxMDYxLC03
NS45MDQ1NDElMjZzc3BuPTAuMDA3MTE5LDAuMDIzODM5JTI2aWU9VVRGOCUy
Nno9MTglMjZsbD00NS4zNDEwNjEsLTc1LjkwNDU0MSUyNnNwbj0wLjAwMTc4
LDAuMDA1OTYlMjZ0PWglMjZvbT0xPg0KDQo+IA0KDQo+ICAgICAgICAgICAg
IA0KDQo+IA0KDQo+ICANCg0KPiANCg0KPiBNaWNoYWVsIFNsYXZpdGNoICAg
ICAgICAgICAgIA0KDQo+IA0KDQo+IExlYWQsIFRlY2hub2xvZ3kgSW5pdGlh
dGl2ZXMNCg0KPiANCg0KPiBzbGF2aXRjaEBvYmplY3R3b3JsZC5jb20gPG1h
aWx0bzpzbGF2aXRjaEBvYmplY3R3b3JsZC5jb20+DQoNCj4gDQoNCj4gICAg
ICAgICAgICAgDQoNCj4gDQoNCj4gUFNUTjogDQoNCj4gDQoNCj4gICAgICAg
ICAgICAgDQoNCj4gDQoNCj4gKzEuODg4LjM5OC45Njk4DQoNCj4gDQoNCj4g
ICAgICAgICAgICAgDQoNCj4gDQoNCj4geDIyNQ0KDQo+IA0KDQo+IEZheDoN
Cg0KPiANCg0KPiAgICAgICAgICAgICANCg0KPiANCg0KPiArMS42MTMuNTk5
Ljc0NTcNCg0KPiANCg0KPiAgICAgICAgICAgICANCg0KPiANCg0KPiAgDQoN
Cj4gDQoNCj4gU2t5cGU6ICAgICAgDQoNCj4gDQoNCj4gICAgICAgICAgICAg
DQoNCj4gDQoNCj4gICBPYmplY3R3b3JsZCANCg0KPiA8aHR0cHM6Ly9maXJl
d2FsbC5vYmplY3R3b3JsZC5jb20vZXhjaGFuZ2Uvc2xhdml0Y2gvU2VudCUy
MEl0ZW1zL05vcnRlbCwlMjBNU0ZUJTIwY2hhc2UlMjBjYXJyaWVycyUyMHdp
dGglMjBuZXclMjBob3N0ZWQlMjBvZmZlcmluZyUyMGZvciUyMFNNRSUyMGFu
ZCUyME1NRS5FTUwvPiAgIA0KDQo+IA0KDQo+IA0KDQo+ICAgICAgICAgICAg
IA0KDQo+IA0KDQo+IHgyMjUNCg0KPiANCg0KPiAgICAgICAgICAgICANCg0K
PiANCg0KPiA8aHR0cHM6Ly9maXJld2FsbC5vYmplY3R3b3JsZC5jb20vZXhj
aGFuZ2Uvc2xhdml0Y2gvU2VudCUyMEl0ZW1zL05vcnRlbCwlMjBNU0ZUJTIw
Y2hhc2UlMjBjYXJyaWVycyUyMHdpdGglMjBuZXclMjBob3N0ZWQlMjBvZmZl
cmluZyUyMGZvciUyMFNNRSUyMGFuZCUyME1NRS5FTUwvPg0KDQo+IA0KDQo+
ICAgICAgICAgICAgIA0KDQo+IA0KDQo+ICANCg0KPiANCg0KPiAgDQoNCj4g
DQoNCj4gDQoNCiANCg0KIA0KDQotLSANCg0KDQogDQoNCgotLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpUaGlz
IHRyYW5zbWlzc2lvbiAoaW5jbHVkaW5nIGFueSBhdHRhY2htZW50cykgbWF5
IGNvbnRhaW4gY29uZmlkZW50aWFsIGluZm9ybWF0aW9uLCBwcml2aWxlZ2Vk
IG1hdGVyaWFsIChpbmNsdWRpbmcgbWF0ZXJpYWwgcHJvdGVjdGVkIGJ5IHRo
ZSBzb2xpY2l0b3ItY2xpZW50IG9yIG90aGVyIGFwcGxpY2FibGUgcHJpdmls
ZWdlcyksIG9yIGNvbnN0aXR1dGUgbm9uLXB1YmxpYyBpbmZvcm1hdGlvbi4g
QW55IHVzZSBvZiB0aGlzIGluZm9ybWF0aW9uIGJ5IGFueW9uZSBvdGhlciB0
aGFuIHRoZSBpbnRlbmRlZCByZWNpcGllbnQgaXMgcHJvaGliaXRlZC4gSWYg
eW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4gZXJyb3Is
IHBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2VuZGVyIGFuZCBk
ZWxldGUgdGhpcyBpbmZvcm1hdGlvbiBmcm9tIHlvdXIgc3lzdGVtLiBVc2Us
IGRpc3NlbWluYXRpb24sIGRpc3RyaWJ1dGlvbiwgb3IgcmVwcm9kdWN0aW9u
IG9mIHRoaXMgdHJhbnNtaXNzaW9uIGJ5IHVuaW50ZW5kZWQgcmVjaXBpZW50
cyBpcyBub3QgYXV0aG9yaXplZCBhbmQgbWF5IGJlIHVubGF3ZnVsLiANCg0K
QW55IHZpZXdzLCBvcGluaW9ucyBhbmQgY29udGVudCBwcmVzZW50ZWQgaW4g
dGhpcyBlLW1haWwgYXJlIHNvbGVseSB0aG9zZSBvZiB0aGUgYXV0aG9yIGFu
ZCBtYXkgbm90IHJlcHJlc2VudCB0aG9zZSBvZiBPYmplY3R3b3JsZCBDb21t
dW5pY2F0aW9ucyBDb3JwLiAK

------_=_NextPart_002_01C775FF.19CEFDE7
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64
Content-Disposition: inline

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwi
IHhtbG5zOm89InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9m
ZmljZSIgeG1sbnM6dz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZp
Y2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNv
bS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5v
cmcvVFIvUkVDLWh0bWw0MCI+DQoNCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj1Db250ZW50LVR5cGUgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0
Zi04Ij4NCjxtZXRhIG5hbWU9R2VuZXJhdG9yIGNvbnRlbnQ9Ik1pY3Jvc29m
dCBXb3JkIDEyIChmaWx0ZXJlZCBtZWRpdW0pIj4NCjwhLS1baWYgIW1zb10+
DQo8c3R5bGU+DQp2XDoqIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9
DQpvXDoqIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQp3XDoqIHti
ZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQouc2hhcGUge2JlaGF2aW9y
OnVybCgjZGVmYXVsdCNWTUwpO30NCjwvc3R5bGU+DQo8IVtlbmRpZl0tLT4N
CjxzdHlsZT4NCjwhLS0NCiAvKiBGb250IERlZmluaXRpb25zICovDQogQGZv
bnQtZmFjZQ0KCXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6
NSAwIDAgMCAwIDAgMCAwIDAgMDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFt
aWx5OldpbmdkaW5nczsNCglwYW5vc2UtMTo1IDAgMCAwIDAgMCAwIDAgMCAw
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5v
c2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2Zv
bnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0
IDIgNDt9DQogLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCiBwLk1zb05vcm1h
bCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47
DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQphOmxp
bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5
OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7
fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1zb1BsYWluVGV4dCwgbGkuTXNv
UGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCBDaGFyIjsN
CgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250
LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z
ZXJpZiI7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNv
QWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxl
LWxpbms6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1h
cmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9u
dC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnNwYW4uUGxhaW5U
ZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiUGxhaW4gVGV4dCBDaGFyIjsN
Cgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBs
YWluIFRleHQiOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJp
ZiI7fQ0Kc3Bhbi5CYWxsb29uVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6
IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxvb24gVGV4dCI7DQoJZm9udC1mYW1p
bHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCi5Nc29DaHBEZWZhdWx0DQoJ
e21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5O30NCkBwYWdlIFNlY3Rpb24x
DQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAx
LjBpbiAxLjBpbjt9DQpkaXYuU2VjdGlvbjENCgl7cGFnZTpTZWN0aW9uMTt9
DQogLyogTGlzdCBEZWZpbml0aW9ucyAqLw0KIEBsaXN0IGwwDQoJe21zby1s
aXN0LWlkOjg0Njg2NzE5NzsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCglt
c28tbGlzdC10ZW1wbGF0ZS1pZHM6LTEzOTgwNTAzOCAtMTcxNDc4MzQ4MiA2
NzY5ODY5MSA2NzY5ODY5MyA2NzY5ODY4OSA2NzY5ODY5MSA2NzY5ODY5MyA2
NzY5ODY4OSA2NzY5ODY5MSA2NzY5ODY5Mzt9DQpAbGlzdCBsMDpsZXZlbDEN
Cgl7bXNvLWxldmVsLXN0YXJ0LWF0OjA7DQoJbXNvLWxldmVsLW51bWJlci1m
b3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Oi07DQoJbXNvLWxldmVs
LXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjps
ZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsInNhbnMtc2VyaWYiOw0KCW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5
OkNhbGlicmk7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBS
b21hbiI7fQ0Kb2wNCgl7bWFyZ2luLWJvdHRvbTowaW47fQ0KdWwNCgl7bWFy
Z2luLWJvdHRvbTowaW47fQ0KLS0+DQo8L3N0eWxlPg0KPCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQogPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIg
c3BpZG1heD0iMjA1MCIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYg
Z3RlIG1zbyA5XT48eG1sPg0KIDxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0
Ij4NCiAgPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQogPC9v
OnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KDQo8
Ym9keSBsYW5nPUVOLVVTIGxpbms9Ymx1ZSB2bGluaz1wdXJwbGU+DQoNCjxk
aXYgY2xhc3M9U2VjdGlvbjE+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD5U
aGUgcG9pbnQgSSBhbSBtYWtpbmcgaXPCoCB0aGF0IGluIHRoZSBlbnRlcnBy
aXNlIHRoZSBhY3R1YWwNCnRvcG9sb2dpY2FsIGRlcGxveW1lbnRzIG9mIFNJ
UCBjbGllbnRzIGFuZCBzZXJ2ZXJzLCA8aT53aGVuIGltcGxlbWVudGVkIGFz
IHNvZnR3YXJlDQpvbiBnZW5lcmljIGNvbXB1dGluZyBwbGF0Zm9ybXM8L2k+
LCBhcyB3ZWxsIGFzIHRoZSA8aT5tZWNoYW5pc21zIHRoYXQgbWFrZSB0aGF0
DQpkZXBsb3ltZW50IGhhcHBlbjwvaT4sIGFyZSBhbHJlYWR5IHZlcnkgZGlm
ZmVyZW50IHdvcmxkIHRoYW4gdGhlIGNhbm9uaWNhbA0KSU1TL0NTU0lQIG9u
ZSB3aGljaCDCoGFzc3VtZXMgU0lQIGFzIGNvcmUgbW9ub2xpdGhpYyBzZXJ2
ZXJzLCBmaXhlZCBlbnRlcnByaXNlDQpuZXR3b3JrIGludGVncmF0ZWQgYWNj
ZXNzIGRldmljZXMgKElBRCksIMKgQjJCVUEgZGVtYXJrcywgbmV0d29yayBl
bGVtZW50cywgYW5kIGR1bWINCmZpeGVkIGVuZHBvaW50cy7CoCBUYWtpbmcg
YSBuZXR3b3JrIGFzIGEgd2hvbGUgZW50ZXJwcmlzZSBhcHBsaWNhdGlvbiBz
b2Z0d2FyZSB1c2luZw0KQy9TIFNJUCBwcm94aWVzIGFuZCBVQeKAmXMgPGk+
YWxyZWFkeTwvaT4gYXBwcm94aW1hdGVzIHNvbWV0aGluZyB0aGF0IGlzIGNs
b3NlIHRvDQp3aGF0IGlzIGJlaW5nIGNhbGxlZCBQMlBTSVAsIG9ubHkgaW4g
YSBtYW5uZXIgdGhhdCBpcyBoaWdobHkgcHJvcHJpZXRhcnksDQpjbG9zZWQs
IHNvbWV3aGF0IGJyaXR0bGUgYW5kIGJhcm9xdWUsIGxvY2FsLCBhbmQgYWQt
aG9jLCB3aXRoIGdhcGluZyB1Z2x5IGhvbGVzLsKgDQpQMlAgaGFzIHRoZSBw
b3RlbnRpYWwgdG8gdHJhbnNmb3JtIHRoYXQuPG86cD48L286cD48L3A+DQoN
CjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
Cg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PlNvbWUgcG9pbnRzIEkgdGFrZSBm
cm9tIHRoZSBwcmV2aW91cyBkaXNjdXNzaW9uOjxicj4NCjxicj4NCjxvOnA+
PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+4oCcdGhhdCBh
IFAyUCBzZXR1cCB3aWxsIGJlICpmcmVlKuKAnTxvOnA+PC9vOnA+PC9wPg0K
DQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4mbmJzcDs8L286cD48L3A+
DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dCBzdHlsZT0nbWFyZ2luLWxlZnQ6
LjVpbjt0ZXh0LWluZGVudDotLjI1aW47bXNvLWxpc3Q6bDAgbGV2ZWwxIGxm
bzEnPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuDQpzdHlsZT0nbXNvLWxp
c3Q6SWdub3JlJz4tPHNwYW4gc3R5bGU9J2ZvbnQ6Ny4wcHQgIlRpbWVzIE5l
dyBSb21hbiInPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+
wqBBIFAyUCBuZXR3b3JrIG1heSBub3QgYmUgZnJlZSwgYnV0IHRoZSBzZXR1
cCAocHJvdmlzaW9uaW5nKQ0Kd2lsbCBiZSBmcmVlLCBhbmQgYXV0b21hdGlj
LsKgIFRoaXMgaXMgYSBtYWpvciBiZW5lZml0IG9ubHkgcGFydGlhbGx5IGFj
aGlldmVkDQppbiBlbnRlcnByaXNlIG5ldHdvcmtzLMKgIGEgYmVuZWZpdCBv
ZiBncmVhdCB2YWx1ZSB0byBlbnRlcnByaXNlcyB0aGF0IGlzDQp1bmRlcnNl
cnZlZCBieSB2ZW5kb3JzLsKgIFRoZXJlIGlzIG5vIGJlbmVmaXQgaW4gcmVx
dWlyaW5nIGNvbXBsZXggZGVwbG95bWVudHMNCndoZXJlIGF1dG9tYXRpb24g
Y2FuIHRha2UgaXRzIHBsYWNlLsKgIERlcGxveW1lbnQgaXMgYWxtb3N0IGFs
d2F5cyB0aGUgYmlnZ2VzdA0KY29zdCBvZiBlbnRlcnByaXNlIHN5c3RlbXMg
ZHdhcmZpbmcgdGhlIGNvc3Qgb2YgdGhlIHN5c3RlbXMgdGhlbXNlbHZlcy48
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0IHN0eWxl
PSdtYXJnaW4tbGVmdDouMjVpbic+PG86cD4mbmJzcDs8L286cD48L3A+DQoN
CjxwIGNsYXNzPU1zb1BsYWluVGV4dD7igJxJIHRoaW5rIHRoaXMgZGVwZW5k
cyBncmVhdGx5IG9uIHdoYXQgZXhwZWN0YXRpb25zIC8NCmNvbnRyYWN0dWFs
IGd1YXJhbnRlZXMgdGhlIGVudGVycHJpc2UgaGFzLiBJdOKAmXMgdW5jbGVh
ciB0byBtZSB3aGF0IGd1YXJhbnRlZXMNCmNhbiBiZSBtYWRlIGFib3V0IGEg
UDJQU0lQIG5ldHdvcmsgd2lsbCBiZSBhYmxlIHRvIG1ha2UsIGFuZCBpdHMg
dW5jbGVhciB3aGF0DQpraW5kIG9mIGluZnJhc3RydWN0dXJlIHdvdWxkIGJl
IGluc3RhbGxlZCBieS9mb3Igc29tZW9uZSB3aWxsaW5nIHRvIG1ha2UNCmd1
YXJhbnRlZXMu4oCdPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNv
UGxhaW5UZXh0IHN0eWxlPSdtYXJnaW4tbGVmdDouNWluO3RleHQtaW5kZW50
Oi0uMjVpbjttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSc+PCFbaWYgIXN1cHBv
cnRMaXN0c10+PHNwYW4NCnN0eWxlPSdtc28tbGlzdDpJZ25vcmUnPi08c3Bh
biBzdHlsZT0nZm9udDo3LjBwdCAiVGltZXMgTmV3IFJvbWFuIic+Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7DQo8L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT5UaGF0IGlzIHdoeSDigJhl
eHBlY3RhdGlvbnMvY29udHJhY3R1YWwgZ3VhcmFudGVlc+KAmSBuZWVkDQp0
byBiZSBidWlsdCBpbnRvIHRoZSBhdXRvbWF0aW9uIHRoYXQgZXhpc3RzIGlu
IHRoZSBQMlAgb3ZlcmxheS7CoA0KU2VsZi1jYWxjdWxhdGlvbiBvZiBzdWNo
IHBlcmZvcm1hbmNlIG1ldHJpY3MgaXMgYWxyZWFkeSB0aGVyZSBpbiBhbGwg
ZW50ZXJwcmlzZQ0KZGV2aWNlcywgdGhlIGRpZmZlcmVuY2UgYmVpbmcgdGhh
dCB3aGlsZSBXTUkvU05NUCBkYXRhIGlzIG1lcmVseSBjb2xsZWN0ZWQgYQ0K
UDJQU0lQIG5ldHdvcmsgY2FuIGFjdCBhdXRvbWF0aWNhbGx5IGJhc2VkIG9u
IHRoZSBtZXRyaWNzIHdpdGhpbiB0aGVpciBvd24gbm9kZXMsDQp0aGVyZSBp
cyBhIGNvbGxlY3RpdmUg4oCYYWhh4oCZIHRoYXQgZm9yY2VzIGJlaGF2aW9y
IGNoYW5nZSBiYXNlZCBvbiBzdHJpY3QNCmNvbnRyYWN0cywgYWthIHJ1bGVz
LsKgIEFuIFNMQSBpcyBlYXNpZXIgdG8gbWFpbnRhaW4gaWYgdGhlIG9iamVj
dHMgY2FuIHJlYWN0DQphY2NvcmRpbmdseSwgZm9yIGV4YW1wbGUgYSBub2Rl
IHdpdGggZGVncmFkaW5nIHNlcnZpY2UgY2FuIG5vdGlmeSB0aGF0IGl0IGlz
IG9uDQp0aGUgZGVjbGluZSBmb3JjaW5nIG90aGVycyB0byB0YWtlIG92ZXIu
wqAgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dCBz
dHlsZT0nbWFyZ2luLWxlZnQ6LjI1aW4nPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+VGhlcmUgaXMgYW4gb2xkIHRy
YWZmaWMgZW5naW5lZXJpbmcgYXhpb20gYWJvdXQgc2VydmljZSBndWFyYW50
ZWVzOg0KaXQgY2FuIGJlIGFjaGlldmVkIHRocm91Z2ggdHdvIHdheXM6IG92
ZXIgZW5naW5lZXJpbmcgb3IgwqBhdXRvbWF0aW9uLsKgIFAyUFNJUCBhbGxv
d3MNCmZvciBhdXRvbWF0aW9uLjxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFz
cz1Nc29QbGFpblRleHQ+PG86cD4mbmJzcDs8L286cD48L3A+DQoNCjxwIGNs
YXNzPU1zb1BsYWluVGV4dD7CoERhdmlkIE9yYW4gd3JvdGU6PG86cD48L286
cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PuKAnEknbSBub3Qg
c2F5aW5nIHRoaXMgY2FuJ3QgYmUgbWFkZSB0byB3b3JrLCBvbmx5IHRoYXQg
aXQNCmlzbid0IGltbWVkaWF0ZWx5IG9idmlvdXMgdGhhdCBpdCBoYXMgYWR2
YW50YWdlcyBvdmVyIGEgY2xhc3NpYyBhcHBsaWNhdGlvbi9zZXJ2ZXINCmFw
cHJvYWNoLuKAnTxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFp
blRleHQ+PG86cD4mbmJzcDs8L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD5UaGUgaW1tZWRpYXRlbHkgb2J2aW91cyBhZHZhbnRhZ2UgdG8g
bWUgaXMgc3RhbmRhcmRpemVkDQpydWdnZWRpemVkIGF1dG9tYXRpb24gdGhh
dCBoYXMgZWNvbm9taWVzIG9mIHNjYWxlIGFuZCBvcGVyYXRlcyBvdmVyIG11
bHRpcGxlDQpkb21haW5zLCBlbGltaW5hdGluZyB0aGUgbmVlZCBmb3Igb3Zl
ci1lbmdpbmVlcmluZyzCoCBkZXRhaWxlZCBmdXNzeQ0KcHJvdmlzaW9uaW5n
LMKgIGFuZCBhbiBhcm15IG9mIHBlb3BsZSBkb2luZyBiYXNpYyBtb25pdG9y
aW5nIGFuZCBjYXJlLWFuZC1mZWVkaW5nLsKgDQpBdXRvbWF0aW9uIGlzIHRo
ZSBrZXksIGEgZHluYW1pYyBzdGF0aXN0aWNhbCBuZXR3b3JrIHZzLiBvbmUg
dGhhdCBpcyBmaXhlZCBhbmQNCmFzc3VtZWQgZGV0ZXJtaW5pc3RpYyB3aWxs
IGFsd2F5cyB3aW4gb3V0IG92ZXIgdGltZSBnaXZlbiBhIGZyYWN0YWwgb3Bl
cmF0aW5nDQplbnZpcm9ubWVudC7CoMKgIFRoaXMgaXMgYmVpbmcgZG9uZSBp
biBmaXRzIGFuZCBzdGFydHMgaW4gdGhlIGVudGVycHJpc2UgZGF0YQ0KY2Vu
dGVyLsKgwqAgUDJQU0lQIG1ha2VzIGl0IG11Y2ggbW9yZSBjb21wcmVoZW5z
aXZlLsKgIMKgUGVvcGxlIHdhbnQgdGhlIHdvcmxkIHRvDQpiZSBwcmVkaWN0
YWJsZSBhbmQgZGV0ZXJtaW5pc3RpYyzCoCBhbmQgQy9TIGJhc2VkIHN5c3Rl
bXMgcmVmbGVjdCB0aGF0LiBUaGF0IGlzDQp0aGUgYmlnZ2VzdCBwcm9ibGVt
IFAyUCBmYWNlcyBiZWNhdXNlIGl0IGZsaWVzIGluIHRoZSBmYWNlIG9mIHRy
YWRpdGlvbi4gwqDCoDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29Q
bGFpblRleHQ+PG86cD4mbmJzcDs8L286cD48L3A+DQoNCjxwIGNsYXNzPU1z
b1BsYWluVGV4dD5SZWdhcmRzPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNz
PU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCg0KPHAgY2xh
c3M9TXNvUGxhaW5UZXh0Pk1pY2hhZWwgU2xhdml0Y2g8bzpwPjwvbzpwPjwv
cD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4mbmJzcDs8L286
cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD7CoDxvOnA+PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+wqA8bzpwPjwvbzpwPjwv
cD4NCg0KPHRhYmxlIGNsYXNzPU1zb05vcm1hbFRhYmxlIGJvcmRlcj0xIGNl
bGxzcGFjaW5nPTAgY2VsbHBhZGRpbmc9MCB3aWR0aD0iMTAwJSINCiBzdHls
ZT0nd2lkdGg6MTAwLjAlO2JvcmRlci1jb2xsYXBzZTpjb2xsYXBzZTtib3Jk
ZXI6bm9uZSc+DQogPHRyPg0KICA8dGQgd2lkdGg9NjM4IGNvbHNwYW49NCB2
YWxpZ249dG9wIHN0eWxlPSd3aWR0aDo2LjY1aW47Ym9yZGVyOm5vbmU7DQog
IGJvcmRlci10b3A6c29saWQgd2luZG93dGV4dCAxLjBwdDtiYWNrZ3JvdW5k
OndoaXRlO3BhZGRpbmc6MGluIDUuNHB0IDBpbiA1LjRwdCc+DQogIDxwIGNs
YXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCiAgPC90ZD4N
CiA8L3RyPg0KIDx0cj4NCiAgPHRkIHdpZHRoPTI4NiB2YWxpZ249dG9wIHN0
eWxlPSd3aWR0aDoyMTQuNTVwdDtib3JkZXI6bm9uZTtiYWNrZ3JvdW5kOndo
aXRlOw0KICBwYWRkaW5nOjBpbiAwaW4gMGluIDBpbic+DQogIDxwIGNsYXNz
PU1zb05vcm1hbD48YSBocmVmPSJodHRwOi8vd3d3Lm9iamVjdHdvcmxkLmNv
bS8iDQogIHRpdGxlPSJPYmplY3R3b3JsZCBDb21tdW5pY2F0aW9ucyI+PHNw
YW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQ7dGV4dC1kZWNvcmF0aW9uOg0K
ICBub25lJz48aW1nIGJvcmRlcj0wIHdpZHRoPTIzNyBoZWlnaHQ9NDIgaWQ9
IlBpY3R1cmVfeDAwMjBfMSINCiAgc3JjPSJjaWQ6aW1hZ2UwMDUuanBnQDAx
Qzc3NURELjhGMUQ0MUYwIiBhbHQ9ImNvcnBfMmNvbG91ciI+PC9zcGFuPjwv
YT48bzpwPjwvbzpwPjwvcD4NCiAgPHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KICA8L3RkPg0KICA8dGQgd2lkdGg9MjExIHZh
bGlnbj10b3Agc3R5bGU9J3dpZHRoOjE1OC4wNXB0O2JvcmRlcjpub25lO2Jh
Y2tncm91bmQ6d2hpdGU7DQogIHBhZGRpbmc6MGluIDBpbiAwaW4gMGluJz4N
CiAgPHAgY2xhc3M9TXNvTm9ybWFsPjMwOCBMZWdnZXQgRHIuIDxicj4NCiAg
T3R0YXdhIE9udGFyaW8gPGJyPg0KICBLMksgMVk2IENhbmFkYTxvOnA+PC9v
OnA+PC9wPg0KICA8L3RkPg0KICA8dGQgd2lkdGg9MTM3IHZhbGlnbj10b3Ag
c3R5bGU9J3dpZHRoOjEwMi42cHQ7Ym9yZGVyOm5vbmU7YmFja2dyb3VuZDp3
aGl0ZTsNCiAgcGFkZGluZzowaW4gMGluIDBpbiAwaW4nPg0KICA8cCBjbGFz
cz1Nc29Ob3JtYWwgYWxpZ249cmlnaHQgc3R5bGU9J3RleHQtYWxpZ246cmln
aHQnPjxhDQogIGhyZWY9Imh0dHA6Ly9tYXBzLmdvb2dsZS5jYS9tYXBzP2Y9
cSZhbXA7aGw9ZW4mYW1wO3E9MzA4K0xlZ2dldCtEcml2ZStPdHRhd2ErT250
YXJpbytLMksrMVk2JmFtcDtsYXllcj0mYW1wO3NsbD00NS4zNDEwNjEsLTc1
LjkwNDU0MSZhbXA7c3Nwbj0wLjAwNzExOSwwLjAyMzgzOSZhbXA7aWU9VVRG
OCZhbXA7ej0xOCZhbXA7bGw9NDUuMzQxMDYxLC03NS45MDQ1NDEmYW1wO3Nw
bj0wLjAwMTc4LDAuMDA1OTYmYW1wO3Q9aCZhbXA7b209MSINCiAgdGl0bGU9
IjMwOCBMZWdnZXQgRHJpdmUgT3R0YXdhIE9udGFyaW8gSzJLIDFZNiI+PHNw
YW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQ7DQogIHRleHQtZGVjb3JhdGlv
bjpub25lJz48aW1nIGJvcmRlcj0wIHdpZHRoPTI5IGhlaWdodD0yOSBpZD0i
UGljdHVyZV94MDAyMF82Ig0KICBzcmM9ImNpZDppbWFnZTAwMy5wbmdAMDFD
Nzc1RDkuNzNDNTZEQTAiPjwvc3Bhbj48L2E+PG86cD48L286cD48L3A+DQog
IDwvdGQ+DQogIDx0ZCBzdHlsZT0nYm9yZGVyOm5vbmU7cGFkZGluZzowaW4g
MGluIDBpbiAwaW4nIHdpZHRoPTU+PHAgY2xhc3M9J01zb05vcm1hbCc+Jm5i
c3A7PC90ZD4NCiA8L3RyPg0KIDx0cj4NCiAgPHRkIHdpZHRoPTI4NiB2YWxp
Z249dG9wIHN0eWxlPSd3aWR0aDoyMTQuNTVwdDtib3JkZXI6bm9uZTtiYWNr
Z3JvdW5kOndoaXRlOw0KICBwYWRkaW5nOjBpbiAwaW4gMGluIDBpbic+DQog
IDx0YWJsZSBjbGFzcz1Nc29Ob3JtYWxUYWJsZSBib3JkZXI9MCBjZWxsc3Bh
Y2luZz0wIGNlbGxwYWRkaW5nPTANCiAgIHN0eWxlPSdib3JkZXItY29sbGFw
c2U6Y29sbGFwc2UnPg0KICAgPHRyPg0KICAgIDx0ZCB3aWR0aD0yNzggdmFs
aWduPXRvcCBzdHlsZT0nd2lkdGg6MjA4LjRwdDtwYWRkaW5nOjBpbiAwaW4g
MGluIDBpbic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPk1pY2hhZWwNCiAg
ICBTbGF2aXRjaCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO8KgwqDCoCA8bzpwPjwvbzpwPjwv
cD4NCiAgICA8L3RkPg0KICAgPC90cj4NCiAgIDx0cj4NCiAgICA8dGQgd2lk
dGg9Mjc4IHZhbGlnbj10b3Agc3R5bGU9J3dpZHRoOjIwOC40cHQ7cGFkZGlu
ZzowaW4gMGluIDBpbiAwaW4nPg0KICAgIDxwIGNsYXNzPU1zb05vcm1hbD5M
ZWFkLCBUZWNobm9sb2d5IEluaXRpYXRpdmVzPG86cD48L286cD48L3A+DQog
ICAgPC90ZD4NCiAgIDwvdHI+DQogICA8dHI+DQogICAgPHRkIHdpZHRoPTI3
OCB2YWxpZ249dG9wIHN0eWxlPSd3aWR0aDoyMDguNHB0O3BhZGRpbmc6MGlu
IDBpbiAwaW4gMGluJz4NCiAgICA8cCBjbGFzcz1Nc29Ob3JtYWw+c2xhdml0
Y2hAb2JqZWN0d29ybGQuY29tPG86cD48L286cD48L3A+DQogICAgPC90ZD4N
CiAgIDwvdHI+DQogIDwvdGFibGU+DQogIDwvdGQ+DQogIDx0ZCB3aWR0aD0y
MTEgdmFsaWduPXRvcCBzdHlsZT0nd2lkdGg6MTU4LjA1cHQ7Ym9yZGVyOm5v
bmU7YmFja2dyb3VuZDp3aGl0ZTsNCiAgcGFkZGluZzowaW4gMGluIDBpbiAw
aW4nPg0KICA8dGFibGUgY2xhc3M9TXNvTm9ybWFsVGFibGUgYm9yZGVyPTAg
Y2VsbHNwYWNpbmc9MCBjZWxscGFkZGluZz0wIHdpZHRoPTIwNA0KICAgc3R5
bGU9J3dpZHRoOjE1Mi44NXB0O2JvcmRlci1jb2xsYXBzZTpjb2xsYXBzZSc+
DQogICA8dHI+DQogICAgPHRkIHdpZHRoPTQyIHZhbGlnbj10b3Agc3R5bGU9
J3dpZHRoOjMxLjI1cHQ7cGFkZGluZzowaW4gMGluIDBpbiAwaW4nPg0KICAg
IDxwIGNsYXNzPU1zb05vcm1hbD5QU1ROOsKgIDxvOnA+PC9vOnA+PC9wPg0K
ICAgIDwvdGQ+DQogICAgPHRkIHdpZHRoPTEzMSB2YWxpZ249dG9wIHN0eWxl
PSd3aWR0aDo5OC4wNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gMGluJz4NCiAg
ICA8cCBjbGFzcz1Nc29Ob3JtYWw+KzEuODg4LjM5OC45Njk4PG86cD48L286
cD48L3A+DQogICAgPC90ZD4NCiAgICA8dGQgd2lkdGg9MzEgdmFsaWduPXRv
cCBzdHlsZT0nd2lkdGg6MjMuNTVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDBp
bic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPngyMjU8bzpwPjwvbzpwPjwv
cD4NCiAgICA8L3RkPg0KICAgPC90cj4NCiAgIDx0cj4NCiAgICA8dGQgd2lk
dGg9NDIgdmFsaWduPXRvcCBzdHlsZT0nd2lkdGg6MzEuMjVwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDBpbic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPkZh
eDo8bzpwPjwvbzpwPjwvcD4NCiAgICA8L3RkPg0KICAgIDx0ZCB3aWR0aD0x
MzEgdmFsaWduPXRvcCBzdHlsZT0nd2lkdGg6OTguMDVwdDtwYWRkaW5nOjBp
biAwaW4gMGluIDBpbic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPisxLjYx
My41OTkuNzQ1NzxvOnA+PC9vOnA+PC9wPg0KICAgIDwvdGQ+DQogICAgPHRk
IHdpZHRoPTMxIHZhbGlnbj10b3Agc3R5bGU9J3dpZHRoOjIzLjU1cHQ7cGFk
ZGluZzowaW4gMGluIDBpbiAwaW4nPg0KICAgIDxwIGNsYXNzPU1zb05vcm1h
bD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCiAgICA8L3RkPg0KICAgPC90cj4N
CiAgIDx0cj4NCiAgICA8dGQgd2lkdGg9NDIgdmFsaWduPXRvcCBzdHlsZT0n
d2lkdGg6MzEuMjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDBpbic+DQogICAg
PHAgY2xhc3M9TXNvTm9ybWFsPlNreXBlOsKgwqDCoMKgwqDCoCA8bzpwPjwv
bzpwPjwvcD4NCiAgICA8L3RkPg0KICAgIDx0ZCB3aWR0aD0xMzEgdmFsaWdu
PXRvcCBzdHlsZT0nd2lkdGg6OTguMDVwdDtwYWRkaW5nOjBpbiAwaW4gMGlu
IDBpbic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPsKgPGEgaHJlZj0iU2t5
cGU6T2JqZWN0d29ybGQiPk9iamVjdHdvcmxkPC9hPsKgwqAgPG86cD48L286
cD48L3A+DQogICAgPC90ZD4NCiAgICA8dGQgd2lkdGg9MzEgdmFsaWduPXRv
cCBzdHlsZT0nd2lkdGg6MjMuNTVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDBp
bic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPngyMjU8bzpwPjwvbzpwPjwv
cD4NCiAgICA8L3RkPg0KICAgPC90cj4NCiAgPC90YWJsZT4NCiAgPC90ZD4N
CiAgPHRkIHdpZHRoPTEzNyB2YWxpZ249dG9wIHN0eWxlPSd3aWR0aDoxMDIu
NnB0O2JvcmRlcjpub25lO2JhY2tncm91bmQ6d2hpdGU7DQogIHBhZGRpbmc6
MGluIDBpbiAwaW4gMGluJz4NCiAgPHAgY2xhc3M9TXNvTm9ybWFsIGFsaWdu
PXJpZ2h0IHN0eWxlPSd0ZXh0LWFsaWduOnJpZ2h0Jz48YQ0KICBocmVmPSJz
a3lwZTpPYmplY3R3b3JsZCIgdGl0bGU9T2JqZWN0d29ybGQ+PHNwYW4gc3R5
bGU9J2NvbG9yOndpbmRvd3RleHQ7DQogIHRleHQtZGVjb3JhdGlvbjpub25l
Jz48aW1nIGJvcmRlcj0wIHdpZHRoPTI2IGhlaWdodD0yNiBpZD0iUGljdHVy
ZV94MDAyMF8zIg0KICBzcmM9ImNpZDppbWFnZTAwNC5wbmdAMDFDNzc1RDku
NzNDNTZEQTAiPjwvc3Bhbj48L2E+PG86cD48L286cD48L3A+DQogIDwvdGQ+
DQogIDx0ZCBzdHlsZT0nYm9yZGVyOm5vbmU7cGFkZGluZzowaW4gMGluIDBp
biAwaW4nIHdpZHRoPTU+PHAgY2xhc3M9J01zb05vcm1hbCc+Jm5ic3A7PC90
ZD4NCiA8L3RyPg0KPC90YWJsZT4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+
PG86cD4mbmJzcDs8L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4
dD4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IFBhdWwg
S3l6aXZhdCBbbWFpbHRvOnBreXppdmF0QGNpc2NvLmNvbV0gPGJyPg0KU2Vu
dDogVHVlc2RheSwgQXByaWwgMDMsIDIwMDcgODo1NyBBTTxicj4NClRvOiBN
aWNoYWVsIFNsYXZpdGNoPGJyPg0KQ2M6IEhlbnJ5IFNpbm5yZWljaDsgUDJQ
U0lQIE1haWxpbmcgTGlzdDsgTWljaGFlbCBIYW1tZXIgKG1oYW1tZXIpOyBE
YXZpZCBSDQpPcmFuOyBwMnByZ0BpZXRmLm9yZzsgc2lwcGluZ0BpZXRmLm9y
Zzsgemh1eGlhbjxicj4NClN1YmplY3Q6IFJlOiBbUDJQcmddIFJFOiBbU2lw
cGluZ10gU2ltcGxlIFNJUCB1c2FnZSBzY2VuYXJpbzxvOnA+PC9vOnA+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4mbmJzcDs8L286cD48
L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+TWljaGFlbCBTbGF2
aXRjaCB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxh
aW5UZXh0PiZndDsgU29ycnkgZm9yIGJlaW5nIGxhdGUgaW50byB0aGlzIGRp
c2N1c3Npb24sIGJ1dA0KY2xpZW50LXNlcnZlciBiYXNlZCBWTSA8bzpwPjwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgaXNuJ3Qg
dHJ1bHkgY2xpZW50LXNlcnZlciBhbnltb3JlIGluIGFueXRoaW5nIGJ1dA0K
dGhlIHNtYWxsZXN0IG9yIG1vc3QgPG86cD48L286cD48L3A+DQoNCjxwIGNs
YXNzPU1zb1BsYWluVGV4dD4mZ3Q7IG1vbm9saXRoaWMgb2YgZW50ZXJwcmlz
ZSBuZXR3b3JrcywgaW4gZmFjdCB0aGUNCnJlYWxpdHkgaXMgdGhhdCBtb3N0
IGlmIDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+
Jmd0OyBub3QgYWxsIGVudGVycHJpc2UgbmV0d29ya3MgY29udGFpbiBqdXN0
IHBlZXJzIGFuZA0Kc3VwZXJwZWVycyB3aXRoIHRoZSA8bzpwPjwvbzpwPjwv
cD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgZGlmZmVyZW5jZSBi
ZWluZyBwYXJ0aWFsbHkgYSBtYXJrZXRpbmcgZGVjaXNpb24gYnkNCnRoZSB2
ZW5kb3JzLCBhcyB5b3UgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1z
b1BsYWluVGV4dD4mZ3Q7IGNhbiBjaGFyZ2UgbXVjaCBtb3JlIGZvciB0aGUg
c2VydmVycywgYW5kIGEgcG9saWN5DQpkZWNpc2lvbiBtYWRlIGVpdGhlciA8
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
YXV0b21hdGljYWxseSBieSBhIHNvZnR3YXJlIGRlcGxveW1lbnQgc3lzdGVt
IG9yIGJ5DQpJVCBzdGFmZiB3aGljaCB3YW50cyA8bzpwPjwvbzpwPjwvcD4N
Cg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgdG8gcGxhY2Ugc3VwZXJu
b2RlcyB3aXRoIGRhdGEgc2lua3Mgb24gYXBwcm9wcmlhdGUNCmVxdWlwbWVu
dC48bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0Pjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+
SSdtIHNvcnJ5LCBidXQgSSBkb24ndCB1bmRlcnN0YW5kIHRoZSBwb2ludCB5
b3UgYXJlDQp0cnlpbmcgdG8gbWFrZSA8bzpwPjwvbzpwPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PmFib3ZlLiBZb3UgYXJlIHRyeWluZyB0byBk
cmF3IHNvbWUgc29ydCBvZiBkaXN0aW5jdGlvbiwNCmJ1dCBJIGRvbid0IGdl
dCA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0Pml0
LiBDYW4geW91IHRyeSBhZ2Fpbi48bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xh
c3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KDQo8cCBj
bGFzcz1Nc29QbGFpblRleHQ+wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC
oMKgIFRoYW5rcyw8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxh
aW5UZXh0PsKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBQYXVsPG86
cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
SW4gYSA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0
PiZndDsgaGlnaGx5IGRpc3RyaWJ1dGVkIGVudmlyb25tZW50IHRoZXJlIGFy
ZSBwb3RlbnRpYWxseQ0KaHVuZHJlZHMgb2YgPG86cD48L286cD48L3A+DQoN
CjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IHBvc3NpYmxlIGRhdGEgc2lu
a3MgZm9yIGEgZ2l2ZW4gYXBwbGljYXRpb24sIHdpdGgNCnRoZSBzaW5rIGJh
c2VkIG9uIDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jmd0OyBzdWJuZXQgb3IgZ2VvZ3JhcGhpYyBsb2NhdGlvbiBvciBiYWxh
bmNlZCBsb2FkLCB0aGlzDQpjYW4gY2hhbmdlIHJhcGlkbHkgPG86cD48L286
cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IG92ZXIgdGlt
ZSBhbmQgZG9lcy48bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxh
aW5UZXh0PiZndDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD4mZ3Q7IEluIHRoZSBjYXNlIG9mIHRoZSBNaWNyb3NvZnQgZW52
aXJvbm1lbnQgc3VjaCBwb2xpY3kNCmlzIGFkbWluaXN0ZXJlZCBhbmQgPG86
cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IHB1
Ymxpc2hlZCBiZXR3ZWVuIHN1cGVybm9kZXMsIGllIHNlcnZlcnMsIGJ5IEFj
dGl2ZQ0KRGlyZWN0b3J5LsKgIEl0IGlzIDxvOnA+PC9vOnA+PC9wPg0KDQo8
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBhZHZlcnRpc2VkIHRvIG1lcmUg
cGVlcnMgdGhyb3VnaCBETlMuwqAgVGhlcmUgd2FzDQptdWNoIGRpc2N1c3Np
b24gYSB3aGlsZSA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxh
aW5UZXh0PiZndDsgYWdvIGFib3V0IGJ1aWxkaW5nIHNlcnZpY2UgZGlzY292
ZXJ5IGVudmlyb25tZW50DQp1c2luZyBETlMgaW5zdGVhZCBvZiBhIDxvOnA+
PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBQMlAg
REhULsKgIEl0IGNhbiBiZSBhcmd1ZWQgdGhhdCBhIGNhc2Ugc3R1ZHkgb2Yg
YQ0KUDJQIGV4YW1wbGUgZG9uZSB1c2luZyA8bzpwPjwvbzpwPjwvcD4NCg0K
PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgRE5TIGlzIGFueSBsYXJnZSBX
aW5kb3dzIFNlcnZlciAyMDAzIGJhc2VkIE1pY3Jvc29mdA0KbmV0d29yayB3
aXRoIG1hbnkgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IHNlcnZlcnMgYW5kIG1hbnkgbW9yZSBjbGllbnRzIHRoYXQg
YWxzbyBydW4NCmFwcGxpY2F0aW9ucyB0aGVtc2VsdmVzIGFuZCA8bzpwPjwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgYXJlIG5v
dCBqdXN0IGR1bWIgdGVybWluYWxzLiBUaGlzIGlzIGFsbW9zdA0KY2VydGFp
bmx5IGFsd2F5cyB0aGUgY2FzZSBpbiA8bzpwPjwvbzpwPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgYWxsIGVudGVycHJpc2VzLiBUaGUg
YmlnIGRpZmZlcmVuY2UgYmV0d2VlbiBDL1MgU0lQDQphbmQgUDJQU0lQIGlz
IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0
OyBhdXRvbWF0aW9uLiBXaGF0IGlzIHRydWUgaXMgdGhhdCB0aGUgc3F1YXJl
IHBlZyBpbg0Kcm91bmQgaG9sZSBvZiA8bzpwPjwvbzpwPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgb3ZlcmxvYWRpbmcgRE5TIG1ha2Vz
IGRlcGxveW1lbnRzIGNsdW1zeSBhbmQgYnJpdHRsZQ0Kd2l0aGluIHRoZSA8
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
ZW50ZXJwcmlzZSBkb21haW4gYW5kIGNvbXBsZXRlbHkgdW5tYW5hZ2VhYmxl
IGFuZA0KdW5wdWJsaXNoYWJsZSBvdXRzaWRlIDxvOnA+PC9vOnA+PC9wPg0K
DQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyB0aGUgZmlyZXdhbGwgd2hp
Y2ggaXMgd2h5IHRoZSBidWNrIHN0b3BzIHRoZXJlIGluDQpjdXJyZW50IGVu
dGVycHJpc2UgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IG5ldHdvcmtpbmcgcHJvZHVjdHMuPG86cD48L286cD48L3A+
DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBUaGUgZGlmZmVyZW5j
ZSBiZXR3ZWVuIEMvUyBhbmQgUDJQIGlzIGxhcmdlbHkgcG9saWN5DQphbmQg
c2VtYW50aWNzIHdpdGggPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1z
b1BsYWluVGV4dD4mZ3Q7IHRoZSBiaWdnZXN0IGRpZmZlcmVuY2UgYmVpbmcg
dGhhdCB0aGUgZGVjaXNpb25zIGFuZA0KcnVsZXMgYXJlIGhpZ2hseSA8bzpw
PjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgZGlz
dHJpYnV0ZWQuwqAgQXBhcnQgZnJvbSB0aGF0IHRoZXkgYXJlIG5vdCBqdXN0
DQpmcmllbmRzLCB0aGV5IGFyZSA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xh
c3M9TXNvUGxhaW5UZXh0PiZndDsgZnJhdGVybmFsIHR3aW5zLjxvOnA+PC9v
OnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgUmVnYXJk
czxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0
OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgTWljaGFlbCBTbGF2aXRjaDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFz
cz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xh
c3M9TXNvUGxhaW5UZXh0PiZndDvCoCA8bzpwPjwvbzpwPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86cD48L286cD48L3A+DQoNCjxw
IGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBjb3JwXzJjb2xvdXIgPG86cD48
L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZsdDto
dHRwczovL2ZpcmV3YWxsLm9iamVjdHdvcmxkLmNvbS9leGNod2ViL2Jpbi9y
ZWRpci5hc3A/VVJMPWh0dHA6Ly93d3cub2JqZWN0d29ybGQuY29tLyZndDs8
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
PG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7
wqAgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4m
Z3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+
Jmd0OyDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDxvOnA+PC9vOnA+PC9wPg0K
DQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4N
Cg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgMzA4IExlZ2dldCBEci48
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
T3R0YXdhIE9udGFyaW88bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNv
UGxhaW5UZXh0PiZndDsgSzJLIDFZNiBDYW5hZGE8bzpwPjwvbzpwPjwvcD4N
Cg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86cD48L286cD48L3A+
DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IMKgwqDCoMKgwqDCoMKg
wqDCoMKgwqAgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFp
blRleHQ+Jmd0Ow0KJmx0O2h0dHBzOi8vZmlyZXdhbGwub2JqZWN0d29ybGQu
Y29tL2V4Y2h3ZWIvYmluL3JlZGlyLmFzcD9VUkw9aHR0cDovL21hcHMuZ29v
Z2xlLmNhL21hcHM/Zj1xJTI2aGw9ZW4lMjZxPTMwOCUyQkxlZ2dldCUyQkRy
aXZlJTJCT3R0YXdhJTJCT250YXJpbyUyQksySyUyQjFZNiUyNmxheWVyPSUy
NnNsbD00NS4zNDEwNjEsLTc1LjkwNDU0MSUyNnNzcG49MC4wMDcxMTksMC4w
MjM4MzklMjZpZT1VVEY4JTI2ej0xOCUyNmxsPTQ1LjM0MTA2MSwtNzUuOTA0
NTQxJTI2c3BuPTAuMDAxNzgsMC4wMDU5NiUyNnQ9aCUyNm9tPTEmZ3Q7PG86
cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxv
OnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyDC
oMKgwqDCoMKgwqDCoMKgwqDCoMKgIDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBj
bGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PiZndDvCoCA8bzpwPjwvbzpwPjwvcD4NCg0K
PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86cD48L286cD48L3A+DQoN
CjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IE1pY2hhZWwgU2xhdml0Y2jC
oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPG86cD48L286cD48L3A+DQoNCjxw
IGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBMZWFkLCBUZWNobm9sb2d5IElu
aXRpYXRpdmVzPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFp
blRleHQ+Jmd0OyBzbGF2aXRjaEBvYmplY3R3b3JsZC5jb20NCiZsdDttYWls
dG86c2xhdml0Y2hAb2JqZWN0d29ybGQuY29tJmd0OzxvOnA+PC9vOnA+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwv
cD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgwqDCoMKgwqDCoMKg
wqDCoMKgwqDCoCA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxh
aW5UZXh0PiZndDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD4mZ3Q7IFBTVE46IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFz
cz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xh
c3M9TXNvUGxhaW5UZXh0PiZndDsgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA8
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
PG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7
ICsxLjg4OC4zOTguOTY5ODxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1N
c29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9
TXNvUGxhaW5UZXh0PiZndDsgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA8bzpw
PjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86
cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IHgy
MjU8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4m
Z3Q7IEZheDo8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5U
ZXh0PiZndDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPG86cD48L286cD48
L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyArMS42MTMuNTk5
Ljc0NTc8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0
PiZndDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4
dD4mZ3Q7IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPG86cD48L286cD48L3A+
DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0O8KgIDxvOnA+PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpw
PjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgU2t5cGU6wqDC
oMKgwqDCoCA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5U
ZXh0PiZndDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPG86cD48L286cD48
L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0O8KgwqAgT2JqZWN0
d29ybGQgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4
dD4mZ3Q7DQombHQ7aHR0cHM6Ly9maXJld2FsbC5vYmplY3R3b3JsZC5jb20v
ZXhjaGFuZ2Uvc2xhdml0Y2gvU2VudCUyMEl0ZW1zL05vcnRlbCwlMjBNU0ZU
JTIwY2hhc2UlMjBjYXJyaWVycyUyMHdpdGglMjBuZXclMjBob3N0ZWQlMjBv
ZmZlcmluZyUyMGZvciUyMFNNRSUyMGFuZCUyME1NRS5FTUwvJmd0O8KgwqAN
CjxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0
OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4m
Z3Q7IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPG86cD48L286cD48L3A+DQoN
CjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0K
DQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyB4MjI1PG86cD48L286cD48
L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyDCoMKgwqDCoMKg
wqDCoMKgwqDCoMKgIDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29Q
bGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNv
UGxhaW5UZXh0PiZndDsNCiZsdDtodHRwczovL2ZpcmV3YWxsLm9iamVjdHdv
cmxkLmNvbS9leGNoYW5nZS9zbGF2aXRjaC9TZW50JTIwSXRlbXMvTm9ydGVs
LCUyME1TRlQlMjBjaGFzZSUyMGNhcnJpZXJzJTIwd2l0aCUyMG5ldyUyMGhv
c3RlZCUyMG9mZmVyaW5nJTIwZm9yJTIwU01FJTIwYW5kJTIwTU1FLkVNTC8m
Z3Q7PG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4m
Z3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+
Jmd0OyDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDxvOnA+PC9vOnA+PC9wPg0K
DQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4N
Cg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDvCoCA8bzpwPjwvbzpwPjwv
cD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86cD48L286cD48
L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7wqAgPG86cD48L286
cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9v
OnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4mbmJz
cDs8L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4tLSA8bzpw
PjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PkJFR0lOLUFO
VElTUEFNLVZPVElORy1MSU5LUzxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFz
cz1Nc29QbGFpblRleHQ+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPG86cD48L286cD48L3A+DQoNCjxw
IGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCg0K
PHAgY2xhc3M9TXNvUGxhaW5UZXh0PlRlYWNoIENhbkl0IGlmIHRoaXMgbWFp
bCAoSUQgNjU3ODA1KSBpcyBzcGFtOjxvOnA+PC9vOnA+PC9wPg0KDQo8cCBj
bGFzcz1Nc29QbGFpblRleHQ+U3BhbTrCoMKgwqDCoMKgwqDCoA0KaHR0cDov
L2Nhbml0cHJvLWludC5vYmplY3R3b3JsZC5jb20vY2FuaXQvYi5waHA/aT02
NTc4MDUmYW1wO209MmViMWZkZWU1NWI3JmFtcDtjPXM8bzpwPjwvbzpwPjwv
cD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0Pk5vdCBzcGFtOsKgwqDCoA0K
aHR0cDovL2Nhbml0cHJvLWludC5vYmplY3R3b3JsZC5jb20vY2FuaXQvYi5w
aHA/aT02NTc4MDUmYW1wO209MmViMWZkZWU1NWI3JmFtcDtjPW48bzpwPjwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PkZvcmdldCB2b3Rl
OiBodHRwOi8vY2FuaXRwcm8taW50Lm9iamVjdHdvcmxkLmNvbS9jYW5pdC9i
LnBocD9pPTY1NzgwNSZhbXA7bT0yZWIxZmRlZTU1YjcmYW1wO2M9ZjxvOnA+
PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+LS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
PG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD5FTkQt
QU5USVNQQU0tVk9USU5HLUxJTktTPG86cD48L286cD48L3A+DQoNCjxwIGNs
YXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCg0KPC9k
aXY+DQoNCjxociB3aWR0aD0iMTAwJSI+DQo8Zm9udCBzaXplPSItMiI+PHA+
DQpUaGlzIHRyYW5zbWlzc2lvbiAoaW5jbHVkaW5nIGFueSBhdHRhY2htZW50
cykgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIGluZm9ybWF0aW9uLCBwcml2
aWxlZ2VkIG1hdGVyaWFsIChpbmNsdWRpbmcgbWF0ZXJpYWwgcHJvdGVjdGVk
IGJ5IHRoZSBzb2xpY2l0b3ItY2xpZW50IG9yIG90aGVyIGFwcGxpY2FibGUg
cHJpdmlsZWdlcyksIG9yIGNvbnN0aXR1dGUgbm9uLXB1YmxpYyBpbmZvcm1h
dGlvbi4gQW55IHVzZSBvZiB0aGlzIGluZm9ybWF0aW9uIGJ5IGFueW9uZSBv
dGhlciB0aGFuIHRoZSBpbnRlbmRlZCByZWNpcGllbnQgaXMgcHJvaGliaXRl
ZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4g
ZXJyb3IsIHBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2VuZGVy
IGFuZCBkZWxldGUgdGhpcyBpbmZvcm1hdGlvbiBmcm9tIHlvdXIgc3lzdGVt
LiBVc2UsIGRpc3NlbWluYXRpb24sIGRpc3RyaWJ1dGlvbiwgb3IgcmVwcm9k
dWN0aW9uIG9mIHRoaXMgdHJhbnNtaXNzaW9uIGJ5IHVuaW50ZW5kZWQgcmVj
aXBpZW50cyBpcyBub3QgYXV0aG9yaXplZCBhbmQgbWF5IGJlIHVubGF3ZnVs
LjwvcD4NCg0KPHA+QW55IHZpZXdzLCBvcGluaW9ucyBhbmQgY29udGVudCBw
cmVzZW50ZWQgaW4gdGhpcyBlLW1haWwgYXJlIHNvbGVseSB0aG9zZSBvZiB0
aGUgYXV0aG9yIGFuZCBtYXkgbm90IHJlcHJlc2VudCB0aG9zZSBvZiBPYmpl
Y3R3b3JsZCBDb21tdW5pY2F0aW9ucyBDb3JwLjwvcD4NCjwvZm9udD4KPC9i
b2R5Pg0KDQo8L2h0bWw+DQo=

------_=_NextPart_002_01C775FF.19CEFDE7--

------_=_NextPart_001_01C775FF.19CEFDE7
Content-Type: image/png;
	name="image003.png"
Content-Transfer-Encoding: base64
Content-ID: <image003.png@01C775D9.73C56DA0>
Content-Description: image003.png
Content-Location: image003.png
Content-Disposition: inline

iVBORw0KGgoAAAANSUhEUgAAAB0AAAAdCAIAAADZ8fBYAAAAAXNSR0IArs4c
6QAABd1JREFUSEt1VklvHEUU7n2ZrT2Og2PHWRwnImLJIpEIIRkOHDgAQgoX
Dkgc4IbIf0DcuXCKhMQv4A8gESlYxCQE4oCUjQSvM97G09PT02ttfDU9scdO
KD3Z1d31vnr1ve+9GlUIobxoUC62IvrXRjq/lt7dSJpBPulZF444b0255444
h13d0FWMF/ripfo8LhfKakC/nW+tdMXscff8uD09atcsNcrZapAtbGY/L2Yn
PfXq5ZGpmvV/6Adxo5z/sNCZW0k/fsWbPVEyVSWmKuUcIaREy5hyqKRYmvhl
Jf7xfvDuSfuTV6sV29S0g4Hvw23F4rtbrbJtvzdT8Rytlwn2jKWYKA9abLMn
KpY+4qpnRjVH59cXu5Tmn1+s1Us2KBmmZQ8XkX5zo3V6rHRuvIQAhOD0GfOG
qmxEYskXo656YkTF9ssd4bnatCce7iTNTvzlpdqICydtF3qAy7n4+oaM9LWX
yrqq7MSsauujzl4ERdyapmDS6LInvnyuO9pUTdxvJQpLv3qjalnWLrRWJPSn
p70HLT7tuUs+m1smf2/xOw26FTEuBGHSIA8YnjuZCIlyqq6OV9TlgK4EAl53
NsRCI2RslzZF4hLKr93pvH2ish2LZshzxhnnnYxtRywmIuciYwPDI05zrKZW
TKUd4yvHenjB99pCliQJ54CWR5G4txpJyqFGvRnSMKcZ431jqqYi3pxJI1wa
JtBGRsVKlzaQM8GwHl7w3cz0+9sZIYT3xaOB2Zsr0bGa3U64n7GU8pRJyygL
M54QRR5fiISIpQ77rZH+uU7ubpA/mnlMOT5hPbzgC4R7zV6e54gXA7hsfi1z
Tb0V8zhnGeUZkYZdH+2Qe1vZZoi5mjPlaZs8bJHlDtnsUTA+WEmlF3yB8PuW
gngxwARw+aNWisjbSZ4QLuPtG6gIUvq4lc+vxdcXo6UOcQxJ3E4MXJLQ/sn6
Bi/44tO9Fu+DYnDJb0wVENfL+nBDhkdkxk/5kza5u55ahnZ50j4+Yo5XzBEH
FfYsAsrhCwSwAVyoQvKLf2OurH0KErE527OCaLxElUzW9LGSVrW1M4ess4fN
ixPOpaNlaL2XU0m0EEA4Xh0UkuQX2C97IsyJqiHd4PegRYRiTdnUBFehM4gB
lvZrEdtQBXMoRyKcrQzEMNDZ7FG9nTCIHkxJivcbxL4ZZbcb8VIgSRzIjkEn
HIIpUg1fIFyYLKHeikLTdF0/P1n5t42vkIDM8m5CdieEKRu9/HEr8VNZUcBB
VhshRQXHuYAXfIHwei0rQFH+En7GU9+fTPwcPCoZZP+c4Xg5B9EK0liU32pA
fl3trvdyrkgv+AKhbgnTNBFov5NommkYV06pW0GMGjUAvV8VxSPI6WQEPQ8+
a0F+c6271SNoQlgPL/gCQUKZprxF5FTTbbSxo97VmR2/l6C9mpoKlJzuN8b9
hHZTFqbiiZ9thOgiAiuxHl7wnbBJqVQCbh9axqsahuG4pQ/Ojn5YbwZhD1lG
k0Q3QC53Ow44RZmshvl6j7QiWaxYg5VYf2W08c5R07QdDLTKfrx9fg3DxKtS
pfrZhfqnY0t+p6Pq+pRne7Ze3C9IYCEDIKK0bEOZGnGwBiux/qPTjm5a5XLZ
dV0EW0hi0NcppVEUBRh++/Y/ze8XK0/Z4Wqt6lkqPiH7UJuuq46BrOhBLsJu
OKNvfzHdOzdVN2ynXq/XajXg2rZT3HUDXJwLhQdo3/fDoBN0OnNr6dy62syd
rl5NtCpTTV0Ql4c1Fk5a6eyEeHPCdFzXcVyAVioVxDt8X+zdb4BGdaM3I+hu
txvHUZZlfphsxyyIElDhGJpXdg+5qudahgkRGdUqoqwhXQAtFHbwfiv0XEQN
aIwwDBF+miZAZ5IH2U0kC7oG/SBMYAERA2EORzoojQO/S2SPQxXkOWgFepqm
RUsd3AJ9hRYDqcYGfUSEue+S3+O32GR3FIEDC+iY4G+x/UDxmgYSihIYvtuH
EV7wO2oYHWg4wIEzFQJ9PsZh3P8A9OAgCrvQHUQAAAAASUVORK5CYII=

------_=_NextPart_001_01C775FF.19CEFDE7
Content-Type: image/png;
	name="image004.png"
Content-Transfer-Encoding: base64
Content-ID: <image004.png@01C775D9.73C56DA0>
Content-Description: image004.png
Content-Location: image004.png
Content-Disposition: inline

iVBORw0KGgoAAAANSUhEUgAAABoAAAAaCAIAAAAmKNuZAAAAAXNSR0IArs4c
6QAAA0lJREFUSEutlVtIFFEYx3dm9uLu0qLrrlpmi0kpmilGJZRQQoTQS/kk
JV0kCaoniQgiCro82UtvPQRSYC9dEay37pRFWGq0G2SKruyue9Hdud/6jyPj
krOrgcuwzJxz5nf+3/f9vzOEqqqWtfuRa4fSSIShbiL99tX09Yn5dxgNePY2
l56vLjr0v5st4gAKpgYOVNz0FVQLSibO/noTvqVYZIKTkkRYUliPrbzYubW2
6HCjvzPPHhoOul5MXujY8oiWYqyUEGVGUNJ4Z14I62+KCpsRI3EuFGXGbJS7
bVNvLuEaru/nwZYNF51Wr8GSFYmTU7IqACTJHKfMiQqDR0Gm02J4lg02+U+1
BXqXy9RKgXx5HVWrYYkKTVooP1H1NXbvye8ucxxGJZXTY8yjCyxOnlM5nrGm
7aR7ZPZhMDnwD1FThzpGmNEVWTwdF6TMnspLokwLCo0XByd7THDwxIeZ2yRh
N/LFSsnsfEEXWBDVWnGtztsOhNNaRJH2eX7q2+yDbKKmDmWCJ1L8HyQb4YC1
UAQt98ZSxWGBjXRWAVXosnphHdyPJR7/i9PczEn6qKoooOwo6cpmyaq4v/yq
ztJ8ozKMlEAouI+yYyY4eFUfJUiSVNn1rsYm/0nYAhctRnaXnjWMNhy7nxEi
uBAE1iNeExx8jzARBUXY+YVDYbOntcF3dDoz1Fx2ztAF1vPxM8v9YYwsHgFI
BHZDvvCf5Mf1aVBO172vL+7QH01ZHsdGE3XoR2Rhih6Kc0FZ4SPsqL6o0BHI
w8IUSmyCq/MeibMhZApZl1X+2Y8TBjGXLp0SoUeyzbwYbIPvGHob/SjIGZK3
ZKhEf6h9hhnOz8Isgv0YuWMIXDrvsMnT8W6voxIehPvhBpKw7SzpxtllJZ25
0u931kylP13ZpTUJfks4PKCrQ6nBMlc9QkZZDDPCwwRhNSVWuLZ9ifWb4/DC
4ETP93g/9oRpcikyxlEHLIuyo8drXpqo04cQNXpbUcUSZ63bVqpz0QPwc6Gj
EsbUl9kpd6E98Dp8o72qL7CuJSdOn0Bvox9Rbt2GSDm0pPjJ7cUd6Bkb5UKP
f47ebfR17iu/bFKKFUPThaOOxucJIEPXCupWQ1++Zo2/s38BXn9nvLoJMR4A
AAAASUVORK5CYII=

------_=_NextPart_001_01C775FF.19CEFDE7
Content-Type: image/jpeg;
	name="image005.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image005.jpg@01C775DD.8F1D41F0>
Content-Description: image005.jpg
Content-Location: image005.jpg
Content-Disposition: inline

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N
Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/
2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIAAhEBAxEB/8QA
HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF
BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1
dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB
AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC
AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom
JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6+0Eb
NruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHEx
lWYK4wpGMhueleLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9
clnAj17UWQKd3+kNjPb+tN/s+6bR21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1
IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHNR/8AAlv8a9P8NWv/
AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1
U9W1W00TSrjU76Qx29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GF
E6eqnPpzXoHzp19FZniHXIPDmhXOr3McksNsoZkjxuOSBxn61ieHPiLpniHV
V0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc3dpDNClvcvbM
JQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq3
9uaTFqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jH
GM/M3Psa2tC1uy8RaPb6rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFrea
PqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+w3Vj5hYeRdJskXBxyKANGisR
vFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6vRZpDhd+8
n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA
2fxg0W4nTz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumt
pPNA+Zh3GD0oA26KiuJltraWdgSsSFyB1IAzXE6N8WtG1a7tIZNP1GxivZPK
t7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8kKcE9M5IrD1H4h6Hplta
zzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+jtPI
2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1Lvg
Ehv5V4sNKivtc+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m
1u7X7PGJ4vL+zRoFMe3J3YHY5x9a1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD
059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej3PAy/C1qWJTmmkt+
vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLN
d74l0OHxJ4evNInkMSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZ
rKOGLYFXGMse5wf/AK9ekfLl74p/8k31j/rmv/oa1xfhqXUW+IHhl/E0MVuf
7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5C4YHp+Fc5oHg
DVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu1
1WK/m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYH
A9OBQByXjWXV4fi9oj6Fb29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRq
Z0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xaWxgBkg8zqWycHjo1dFoNtq1p
paQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs9CsdDjg8
OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/g
K2/CHhuLwn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ce
FpvFmlWtlDdJbNBdpcFnUsCFB44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r
8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1Lx54N/4TPT7K2FwsDWt0
sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/AJoe
P+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6W
v+oH+7/SvnjT59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrz
ofC+5XwYNFXUoReQ6l9vt7nyzhD6YznpmgD0RFCIqDooArz34S/e8Uf9hmWv
Qk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2gYsC2SMnOOOOKAO4
1X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689G
HQ1lT+EdCuQBLYK2CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgB
umKworm4ESATyYCj+M0j3M5KZnk4bj5zXjey97c+4WK/dr3e39bG/ChiiCEj
Iz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5OW5+c+lCpbu4
5YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckx
Nyf99q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFA
BRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAH//Z

------_=_NextPart_001_01C775FF.19CEFDE7--


--===============2083950269==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============2083950269==--




From sipping-bounces@ietf.org Wed Apr 04 03:18:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzjA-00054n-PR; Wed, 04 Apr 2007 03:16:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYnH3-0005G0-05; Tue, 03 Apr 2007 13:58:29 -0400
Received: from canitpro.objectworld.com ([72.1.207.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYnGt-00044l-6m; Tue, 03 Apr 2007 13:58:28 -0400
Received: from photon.objectworld.com (photon.objectworld.com [10.10.8.2])
	by canitpro.objectworld.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP
	id l33Hw3KH026561; Tue, 3 Apr 2007 13:58:03 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 3 Apr 2007 13:58:02 -0400
Message-ID: <4E2DC1ACE541B94A946B8D8657E372C57A907B@photon.objectworld.com>
In-Reply-To: <1bdd01c77612$7586dcd0$81238182@cis.neustar.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Thread-Index: Acd176Ya+p6xqIGMQfSJrn6cLV80rgACgCmQAAX8woAAAZhX4A==
References: <4E2DC1ACE541B94A946B8D8657E372C57A903F@photon.objectworld.com>
	<1bdd01c77612$7586dcd0$81238182@cis.neustar.com>
From: "Michael Slavitch" <slavitch@objectworld.com>
To: "Brian Rosen" <br@brianrosen.net>, "Paul Kyzivat" <pkyzivat@cisco.com>
X-Spam-Score: 1.50 (*) [Tag at 20.00] EXTRA_MPART_TYPE, HTML_MESSAGE, SPF(none,
	0.1), 132(0.3), 131(0.3)
X-CanItPRO-Stream: outgoing (inherits from default)
X-Scanned-By: CanIt (www . roaringpenguin . com) on 10.10.8.9
X-Spam-Score: 0.6 (/)
X-Scan-Signature: e259f56175f28a8bef2b34d09ea68c34
X-Mailman-Approved-At: Wed, 04 Apr 2007 03:16:14 -0400
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	David R Oran <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0721435076=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0721435076==
Content-class: urn:content-classes:message
Content-Type: multipart/related; type="multipart/alternative";
	boundary="----_=_NextPart_001_01C77619.9FFAEC5B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C77619.9FFAEC5B
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C77619.9FFAEC5B"


------_=_NextPart_002_01C77619.9FFAEC5B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

"vendors will tell you the things you can automate about provisioning
have been automated."

=20

The vendors will tell you this because the things that they automate can
be summarized as:

=20

1.       "not much".

2.       What we automate is our proprietary stuff, sod the rest.

=20

t's things like TN assignment, and dial plans, and gateway routing, and
emergency call provisioning, and permissions, and feature enabling, etc,
etc that dominate provisioning of enterprise telephony systems.  P2P
doesn't help any of that.

=20

I strongly disagree with that.   Look at the documentation for products
from many of the major vendors, there are stacks of complex details
regarding deployment,  not very automatic at all, with many of them
depending on crufty TFTP or FTP with fixed file locations for
provisioning of endpoints.  It's horrible.

Secondly, "it doesn't help with any of that" is only true in a static
fixed universe where you provision once and go away and limit
functionality to very basic tasks.   Even in that world the number of
user change requests on a 2000 user system is on the order of .5%-1% of
all endpoints per day on today's relatively static systems, 10 to 20 per
day, and that's just basic stuff, done at gunpoint.  Routers used to
have only static routes too, and web pages were once coded by hand.=20=20=
=20

=20

Regards

=20

Michael

=20

=20

=20

  <http://www.objectworld.com/>=20

=20

=09=09=20=09=20
Michael Slavitch=20=20=20=20=20=20=20=20=20=20=20=20=20=20

Lead, Technology Initiatives

slavitch@objectworld.com

=09=09=20=09=20

=20

=20

From: Brian Rosen [mailto:br@brianrosen.net]=20
Sent: Tuesday, April 03, 2007 1:07 PM
To: Michael Slavitch; 'Paul Kyzivat'
Cc: 'P2PSIP Mailing List'; 'Michael Hammer (mhammer)'; 'David R Oran';
'Henry Sinnreich'; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage
scenario

=20

I think most enterprise "PBX" vendors will tell you that the things you
can automate about provisioning have been automated, and you won't get
much a win there.  It's things like TN assignment, and dial plans, and
gateway routing, and emergency call provisioning, and permissions, and
feature enabling, etc, etc that dominate provisioning of enterprise
telephony systems.  P2P doesn't help any of that.

=20

I worry, quite a bit, that perpetuating SIP UAs (the SIP client) will
perpetuate the dumb endpoint model, simply because the way they are made
now is that they are dumb endpoints.  They didn't have to be (SIP was
originally designed for smart endpoints).  If we make P2PSIP endpoints
more closely fit the smart endpoint model, then we make the peer that
serves the UAs be the smart box in the middle of the network.

=20

Brian

=20

________________________________

From: Michael Slavitch [mailto:slavitch@objectworld.com]=20
Sent: Tuesday, April 03, 2007 10:48 AM
To: Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

=20

The point I am making is  that in the enterprise the actual topological
deployments of SIP clients and servers, when implemented as software on
generic computing platforms, as well as the mechanisms that make that
deployment happen, are already very different world than the canonical
IMS/CSSIP one which  assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD),  B2BUA demarks,
network elements, and dumb fixed endpoints.  Taking a network as a whole
enterprise application software using C/S SIP proxies and UA's already
approximates something that is close to what is being called P2PSIP,
only in a manner that is highly proprietary, closed, somewhat brittle
and baroque, local, and ad-hoc, with gaping ugly holes.  P2P has the
potential to transform that.

=20

Some points I take from the previous discussion:

"that a P2P setup will be *free*"

=20

-           A P2P network may not be free, but the setup (provisioning)
will be free, and automatic.  This is a major benefit only partially
achieved in enterprise networks,  a benefit of great value to
enterprises that is underserved by vendors.  There is no benefit in
requiring complex deployments where automation can take its place.
Deployment is almost always the biggest cost of enterprise systems
dwarfing the cost of the systems themselves.

=20

"I think this depends greatly on what expectations / contractual
guarantees the enterprise has. It's unclear to me what guarantees can be
made about a P2PSIP network will be able to make, and its unclear what
kind of infrastructure would be installed by/for someone willing to make
guarantees."

=20

-          That is why 'expectations/contractual guarantees' need to be
built into the automation that exists in the P2P overlay.
Self-calculation of such performance metrics is already there in all
enterprise devices, the difference being that while WMI/SNMP data is
merely collected a P2PSIP network can act automatically based on the
metrics within their own nodes, there is a collective 'aha' that forces
behavior change based on strict contracts, aka rules.  An SLA is easier
to maintain if the objects can react accordingly, for example a node
with degrading service can notify that it is on the decline forcing
others to take over.=20=20

=20

There is an old traffic engineering axiom about service guarantees: it
can be achieved through two ways: over engineering or  automation.
P2PSIP allows for automation.

=20

 David Oran wrote:

=20

"I'm not saying this can't be made to work, only that it isn't
immediately obvious that it has advantages over a classic
application/server approach."

=20

The immediately obvious advantage to me is standardized ruggedized
automation that has economies of scale and operates over multiple
domains, eliminating the need for over-engineering,  detailed fussy
provisioning,  and an army of people doing basic monitoring and
care-and-feeding.  Automation is the key, a dynamic statistical network
vs. one that is fixed and assumed deterministic will always win out over
time given a fractal operating environment.   This is being done in fits
and starts in the enterprise data center.   P2PSIP makes it much more
comprehensive.   People want the world to be predictable and
deterministic,  and C/S based systems reflect that. That is the biggest
problem P2P faces because it flies in the face of tradition.=20=20=20

=20

Regards

=20

Michael Slavitch

=20

=20

=20

=20

=20

  <http://www.objectworld.com/>=20

=20

308 Legget Dr.=20
Ottawa Ontario=20
K2K 1Y6 Canada

=20
<http://maps.google.ca/maps?f=3Dq&hl=3Den&q=3D308+Legget+Drive+Ottawa+Ontar=
io+
K2K+1Y6&layer=3D&sll=3D45.341061,-75.904541&sspn=3D0.007119,0.023839&ie=3DU=
TF8&z
=3D18&ll=3D45.341061,-75.904541&spn=3D0.00178,0.00596&t=3Dh&om=3D1>=20

=20

Michael Slavitch=20=20=20=20=20=20=20=20=20=20=20=20=20=20

Lead, Technology Initiatives

slavitch@objectworld.com

PSTN:=20=20

+1.888.398.9698

x225

Fax:

+1.613.599.7457

=20

Skype:=20=20=20=20=20=20=20

 Objectworld=20=20=20

x225

  <skype:Objectworld>=20

=20

=20

=20

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
Sent: Tuesday, April 03, 2007 8:57 AM
To: Michael Slavitch
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer);
David R Oran; p2prg@ietf.org; sipping@ietf.org; zhuxian
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario

=20

=20

=20

Michael Slavitch wrote:

> Sorry for being late into this discussion, but client-server based VM=20

> isn't truly client-server anymore in anything but the smallest or most


> monolithic of enterprise networks, in fact the reality is that most if


> not all enterprise networks contain just peers and superpeers with the


> difference being partially a marketing decision by the vendors, as you


> can charge much more for the servers, and a policy decision made
either=20

> automatically by a software deployment system or by IT staff which
wants=20

> to place supernodes with data sinks on appropriate equipment.

=20

I'm sorry, but I don't understand the point you are trying to make=20

above. You are trying to draw some sort of distinction, but I don't get=20

it. Can you try again.

=20

                Thanks,

                Paul

=20

> In a=20

> highly distributed environment there are potentially hundreds of=20

> possible data sinks for a given application, with the sink based on=20

> subnet or geographic location or balanced load, this can change
rapidly=20

> over time and does.

>=20

> In the case of the Microsoft environment such policy is administered
and=20

> published between supernodes, ie servers, by Active Directory.  It is=20

> advertised to mere peers through DNS.  There was much discussion a
while=20

> ago about building service discovery environment using DNS instead of
a=20

> P2P DHT.  It can be argued that a case study of a P2P example done
using=20

> DNS is any large Windows Server 2003 based Microsoft network with many


> servers and many more clients that also run applications themselves
and=20

> are not just dumb terminals. This is almost certainly always the case
in=20

> all enterprises. The big difference between C/S SIP and P2PSIP is=20

> automation. What is true is that the square peg in round hole of=20

> overloading DNS makes deployments clumsy and brittle within the=20

> enterprise domain and completely unmanageable and unpublishable
outside=20

> the firewall which is why the buck stops there in current enterprise=20

> networking products.

>=20

> The difference between C/S and P2P is largely policy and semantics
with=20

> the biggest difference being that the decisions and rules are highly=20

> distributed.  Apart from that they are not just friends, they are=20

> fraternal twins.

>=20

> Regards

>=20

> Michael Slavitch

>=20

>=20=20

>=20

>=20

> corp_2colour=20

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://www.o
bjectworld.com/>

>=20

>=20=20

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> 308 Legget Dr.

> Ottawa Ontario

> K2K 1Y6 Canada

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://maps.
google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2BOntari=
o%2
BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.007119,0.0238=
39%
26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.00178,0.00596%26=
t=3Dh%2
6om=3D1>

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>=20=20

>=20

> Michael Slavitch=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> Lead, Technology Initiatives

>=20

> slavitch@objectworld.com <mailto:slavitch@objectworld.com>

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> PSTN:=20

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> +1.888.398.9698

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> x225

>=20

> Fax:

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> +1.613.599.7457

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>=20=20

>=20

> Skype:=20=20=20=20=20=20

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>   Objectworld=20

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%
20and%20MME.EML/>=20=20=20

>=20

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> x225

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%
20and%20MME.EML/>

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>=20=20

>=20

>=20=20

>=20

>=20

=20

=20

--=20


=20

________________________________

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete
this information from your system. Use, dissemination, distribution, or
reproduction of this transmission by unintended recipients is not
authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely
those of the author and may not represent those of Objectworld
Communications Corp.

________________________________


Spam
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0fe34
&c=3Ds>=20
Not spam
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0fe34
&c=3Dn>=20
Forget previous vote
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0fe34
&c=3Df>=20


-----------------------------------------------=0D
=0D
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful. =0D
=0D
Any views, opinions and content presented in this e-mail are solely those o=
f the author and may not represent those of Objectworld Communications Corp=
.=20

------_=_NextPart_002_01C77619.9FFAEC5B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:st1=3D"u=
rn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://www.w3.org/TR/RE=
C-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"countr=
y-region"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PostalCode"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.plaintextchar0
	{mso-style-name:plaintextchar;
	mso-style-priority:99;
	font-family:"Calibri","sans-serif";}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	mso-style-priority:99;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:navy;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:846867197;
	mso-list-type:hybrid;
	mso-list-template-ids:-139805038 -1714783482 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1197936675;
	mso-list-type:hybrid;
	mso-list-template-ids:-2146642626 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'color:black'>&#8220;</span><span style=
=3D'font-size:
10.0pt;font-family:"Arial","sans-serif";color:navy'>vendors will tell you t=
he
things you can automate about provisioning have been automated.</span><span
style=3D'color:black'>&#8221;<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:black'>The vendors will tell you =
this
because the things that they automate can be summarized as:<o:p></o:p></spa=
n></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l1 level1 =
lfo3'><![if !supportLists]><span
style=3D'color:black'><span style=3D'mso-list:Ignore'>1.<span style=3D'font=
:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D'color:black'>&#8220;not much&=
#8221;.<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l1 level1 =
lfo3'><![if !supportLists]><span
style=3D'color:black'><span style=3D'mso-list:Ignore'>2.<span style=3D'font=
:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D'color:black'>What we automate=
 is
our proprietary stuff, sod the rest.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>t&#8217;s things like TN assignment, and dial plans, and gatewa=
y routing,
and emergency call provisioning, and permissions, and feature enabling, etc,
etc that dominate provisioning of enterprise telephony systems. &nbsp;P2P
doesn&#8217;t help any of that.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:black'>I strongly disagree with t=
hat. &nbsp;&nbsp;Look
at the documentation for products from many of the major vendors, there are
stacks of complex details regarding deployment,&nbsp; not very automatic at=
 all,
with many of them depending on crufty TFTP or FTP with fixed file locations=
 for
provisioning of endpoints.&nbsp; It&#8217;s horrible.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'>Secondly, &#8220;it doesn&=
#8217;t help with
any of that&#8221; is only true in a static fixed universe where you provis=
ion once
and go away and limit functionality to very basic tasks.&nbsp; &nbsp;Even i=
n that world the
number of user change requests on a 2000 user system is on the order of .5%=
-1%
of all endpoints per day on today&#8217;s relatively static systems, 10 to =
20 per
day, and that&#8217;s just basic stuff, done at gunpoint.&nbsp; Routers use=
d to have only static
routes too, and web pages were once coded by hand.&nbsp;&nbsp; <o:p></o:p><=
/span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:black'>Regards<o:p></o:p></span><=
/p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:black'>Michael<o:p></o:p></span><=
/p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<div>

<table class=3DMsoNormalTable border=3D1 cellspacing=3D0 cellpadding=3D0 wi=
dth=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse;border:none'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop style=3D'width:6.65in;border:non=
e;
  border-top:solid windowtext 1.0pt;background:white;padding:0in 5.4pt 0in =
5.4pt'>
  <p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span>=
</p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop style=3D'width:214.55pt;border:none;backgrou=
nd:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><a href=3D"http://www.objectworld.com/"
  title=3D"Objectworld Communications"><span style=3D'color:black;text-deco=
ration:
  none'><img border=3D0 width=3D237 height=3D42 id=3D"Picture_x0020_1"
  src=3D"cid:image002.jpg@01C775F8.17EDD430" alt=3D"corp_2colour"></span></=
a><span
  style=3D'color:black'><o:p></o:p></span></p>
  <p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span>=
</p>
  </td>
  <td width=3D211 valign=3Dtop style=3D'width:158.05pt;border:none;backgrou=
nd:white;
  padding:0in 0in 0in 0in'></td>
  <td width=3D137 valign=3Dtop style=3D'width:102.6pt;border:none;backgroun=
d:white;
  padding:0in 0in 0in 0in'></td>
  <td style=3D'border:none;padding:0in 0in 0in 0in' width=3D2><p class=3D'M=
soNormal'>&nbsp;</td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop style=3D'width:214.55pt;border:none;backgrou=
nd:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal><span style=3D'color:black'>Michael
    Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; <o:p></o:p></span></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal><span style=3D'color:black'>Lead, Technology Initi=
atives<o:p></o:p></span></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal><span style=3D'color:black'>slavitch@objectworld.c=
om<o:p></o:p></span></p>
    </td>
   </tr>
  </table>
  </td>
  <td width=3D211 valign=3Dtop style=3D'width:158.05pt;border:none;backgrou=
nd:white;
  padding:0in 0in 0in 0in'></td>
  <td width=3D137 valign=3Dtop style=3D'width:102.6pt;border:none;backgroun=
d:white;
  padding:0in 0in 0in 0in'></td>
  <td style=3D'border:none;padding:0in 0in 0in 0in' width=3D2><p class=3D'M=
soNormal'>&nbsp;</td>
 </tr>
</table>

<p class=3DMsoNormal><span style=3D'color:black;letter-spacing:-.5pt'><o:p>=
&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Brian Rosen
[mailto:br@brianrosen.net] <br>
<b>Sent:</b> Tuesday, April 03, 2007 1:07 PM<br>
<b>To:</b> Michael Slavitch; 'Paul Kyzivat'<br>
<b>Cc:</b> 'P2PSIP Mailing List'; 'Michael Hammer (mhammer)'; 'David R Oran=
';
'Henry Sinnreich'; p2prg@ietf.org; sipping@ietf.org<br>
<b>Subject:</b> RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage
scenario<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>I think most enterprise &#8220;PBX&#8221; vendors will tell you=
 that the things
you can automate about provisioning have been automated, and you won&#8217;=
t get much
a win there. &nbsp;It&#8217;s things like TN assignment, and dial plans, an=
d gateway
routing, and emergency call provisioning, and permissions, and feature
enabling, etc, etc that dominate provisioning of enterprise telephony syste=
ms.
&nbsp;P2P doesn&#8217;t help any of that.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>I worry, quite a bit, that perpetuating SIP UAs (the SIP client)
will perpetuate the dumb endpoint model, simply because the way they are ma=
de
now is that they are dumb endpoints. &nbsp;They didn&#8217;t have to be (SI=
P was
originally designed for smart endpoints).&nbsp; If we make P2PSIP endpoints
more closely fit the smart endpoint model, then we make the peer that serves
the UAs be the smart box in the middle of the network.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>Brian<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Michael Slavi=
tch
[mailto:slavitch@objectworld.com] <br>
<b>Sent:</b> Tuesday, April 03, 2007 10:48 AM<br>
<b>To:</b> Paul Kyzivat<br>
<b>Cc:</b> P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Hen=
ry
Sinnreich; p2prg@ietf.org; sipping@ietf.org<br>
<b>Subject:</b> [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenari=
o</span><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p=
></span></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>The point I am making is&nbsp; that in the enterpri=
se the
actual topological deployments of SIP clients and servers, <i>when implemen=
ted
as software on generic computing platforms</i>, as well as the <i>mechanisms
that make that deployment happen</i>, are already very different world than=
 the
canonical IMS/CSSIP one which &nbsp;assumes SIP as core monolithic servers,
fixed enterprise network integrated access devices (IAD), &nbsp;B2BUA demar=
ks,
network elements, and dumb fixed endpoints.&nbsp; Taking a network as a who=
le
enterprise application software using C/S SIP proxies and UA&#8217;s <i>alr=
eady</i>
approximates something that is close to what is being called P2PSIP, only i=
n a
manner that is highly proprietary, closed, somewhat brittle and baroque, lo=
cal,
and ad-hoc, with gaping ugly holes.&nbsp; P2P has the potential to transform
that.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText style=3D'margin-bottom:12.0pt'>Some points I take f=
rom the
previous discussion:<o:p></o:p></p>

<p class=3DMsoPlainText>&#8220;that a P2P setup will be *free*&#8221;<o:p><=
/o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-li=
st:l0 level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New Roman"'>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>&nbsp;A P2P network may not be free, but the setup
(provisioning) will be free, and automatic.&nbsp; This is a major benefit o=
nly
partially achieved in enterprise networks,&nbsp; a benefit of great value to
enterprises that is underserved by vendors.&nbsp; There is no benefit in
requiring complex deployments where automation can take its place.&nbsp;
Deployment is almost always the biggest cost of enterprise systems dwarfing=
 the
cost of the systems themselves.<o:p></o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&#8220;I think this depends greatly on what expecta=
tions /
contractual guarantees the enterprise has. It&#8217;s unclear to me what gu=
arantees
can be made about a P2PSIP network will be able to make, and its unclear wh=
at
kind of infrastructure would be installed by/for someone willing to make
guarantees.&#8221;<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-li=
st:l0 level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New Roman"'>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>That is why &#8216;expectations/contractual guarant=
ees&#8217; need
to be built into the automation that exists in the P2P overlay.&nbsp;
Self-calculation of such performance metrics is already there in all enterp=
rise
devices, the difference being that while WMI/SNMP data is merely collected a
P2PSIP network can act automatically based on the metrics within their own
nodes, there is a collective &#8216;aha&#8217; that forces behavior change =
based on strict
contracts, aka rules.&nbsp; An <st1:place w:st=3D"on">SLA</st1:place> is ea=
sier
to maintain if the objects can react accordingly, for example a node with
degrading service can notify that it is on the decline forcing others to ta=
ke
over.&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>There is an old traffic engineering axiom about ser=
vice
guarantees: it can be achieved through two ways: over engineering or
&nbsp;automation.&nbsp; P2PSIP allows for automation.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&nbsp;David Oran wrote:<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&#8220;I'm not saying this can't be made to work, o=
nly that it
isn't immediately obvious that it has advantages over a classic
application/server approach.&#8221;<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>The immediately obvious advantage to me is standard=
ized
ruggedized automation that has economies of scale and operates over multiple
domains, eliminating the need for over-engineering,&nbsp; detailed fussy
provisioning,&nbsp; and an army of people doing basic monitoring and
care-and-feeding.&nbsp; Automation is the key, a dynamic statistical network
vs. one that is fixed and assumed deterministic will always win out over ti=
me
given a fractal operating environment.&nbsp;&nbsp; This is being done in fi=
ts
and starts in the enterprise data center.&nbsp;&nbsp; P2PSIP makes it much =
more
comprehensive.&nbsp; &nbsp;People want the world to be predictable and
deterministic,&nbsp; and C/S based systems reflect that. That is the biggest
problem P2P faces because it flies in the face of tradition. &nbsp;&nbsp;<o=
:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Regards<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Michael Slavitch<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&nbsp;<o:p></o:p></p>

<p class=3DMsoPlainText>&nbsp;<o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 wi=
dth=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop style=3D'width:6.65in;border:non=
e;
  border-top:solid windowtext 1.0pt;background:white;padding:0in 5.4pt 0in =
5.4pt'>
  <p class=3DMsoNormal><o:p>&nbsp;</o:p></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop style=3D'width:214.55pt;background:white;pad=
ding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><a href=3D"http://www.objectworld.com/"
  title=3D"Objectworld Communications"><span style=3D'color:windowtext;text=
-decoration:
  none'><img border=3D0 width=3D237 height=3D42 id=3D"Picture_x005f_x0020_1"
  src=3D"cid:image005.jpg@01C775F8.17EDD430" alt=3D"corp_2colour"></span></=
a><o:p></o:p></p>
  <p class=3DMsoNormal><o:p>&nbsp;</o:p></p>
  </td>
  <td width=3D211 valign=3Dtop style=3D'width:158.05pt;background:white;pad=
ding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><st1:Street w:st=3D"on"><st1:address w:st=3D"on">308=
 Legget Dr</st1:address></st1:Street>.
  <br>
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> <st1:State w=
:st=3D"on">Ontario</st1:State>
   <br>
<st1:PostalCode w:st=3D"on">K2K 1Y6</st1:PostalCode> <st1:country-region w:=
st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></p>
  </td>
  <td width=3D137 valign=3Dtop style=3D'width:102.6pt;background:white;padd=
ing:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><a
  href=3D"http://maps.google.ca/maps?f=3Dq&amp;hl=3Den&amp;q=3D308+Legget+D=
rive+Ottawa+Ontario+K2K+1Y6&amp;layer=3D&amp;sll=3D45.341061,-75.904541&amp=
;sspn=3D0.007119,0.023839&amp;ie=3DUTF8&amp;z=3D18&amp;ll=3D45.341061,-75.9=
04541&amp;spn=3D0.00178,0.00596&amp;t=3Dh&amp;om=3D1"
  title=3D"308 Legget Drive Ottawa Ontario K2K 1Y6"><span style=3D'color:wi=
ndowtext;
  text-decoration:none'><img border=3D0 width=3D29 height=3D29
  id=3D"Picture_x005f_x0020_6" src=3D"cid:image006.jpg@01C775F8.17EDD430"><=
/span></a><o:p></o:p></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal>&nbsp;<o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop style=3D'width:214.55pt;background:white;pad=
ding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>Michael
    Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
    <o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>Lead, Technology Initiatives<o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>slavitch@objectworld.com<o:p></o:p></p>
    </td>
   </tr>
  </table>
  </td>
  <td width=3D211 valign=3Dtop style=3D'width:158.05pt;background:white;pad=
ding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D204
   style=3D'width:152.85pt;border-collapse:collapse'>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal>PSTN:&nbsp; <o:p></o:p></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>+1.888.398.9698<o:p></o:p></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal>x225<o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal>Fax:<o:p></o:p></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>+1.613.599.7457<o:p></o:p></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal><o:p>&nbsp;</o:p></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal>Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></=
o:p></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>&nbsp;<a href=3D"Skype:Objectworld">Objectworld</a=
>&nbsp;&nbsp;
    <o:p></o:p></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal>x225<o:p></o:p></p>
    </td>
   </tr>
  </table>
  </td>
  <td width=3D137 valign=3Dtop style=3D'width:102.6pt;background:white;padd=
ing:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><a
  href=3D"skype:Objectworld" title=3DObjectworld><span style=3D'color:windo=
wtext;
  text-decoration:none'><img border=3D0 width=3D26 height=3D26
  id=3D"Picture_x005f_x0020_3" src=3D"cid:image007.jpg@01C775F8.17EDD430"><=
/span></a><o:p></o:p></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal>&nbsp;<o:p></o:p></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>-----Original Message-----<br>
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] <br>
Sent: Tuesday, April 03, 2007 8:57 AM<br>
To: Michael Slavitch<br>
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); David R
Oran; p2prg@ietf.org; sipping@ietf.org; zhuxian<br>
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Michael Slavitch wrote:<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Sorry for being late into this discussion, but
client-server based VM <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; isn't truly client-server anymore in anything =
but
the smallest or most <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; monolithic of enterprise networks, in fact the
reality is that most if <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; not all enterprise networks contain just peers=
 and
superpeers with the <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; difference being partially a marketing decisio=
n by the
vendors, as you <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; can charge much more for the servers, and a po=
licy
decision made either <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; automatically by a software deployment system =
or by
IT staff which wants <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; to place supernodes with data sinks on appropr=
iate
equipment.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>I'm sorry, but I don't understand the point you are
trying to make <o:p></o:p></p>

<p class=3DMsoPlainText>above. You are trying to draw some sort of distinct=
ion,
but I don't get <o:p></o:p></p>

<p class=3DMsoPlainText>it. Can you try again.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Thanks,<o:p></o:p></p>

<p class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Paul<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; In a <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; highly distributed environment there are poten=
tially
hundreds of <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; possible data sinks for a given application, w=
ith
the sink based on <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; subnet or geographic location or balanced load=
, this
can change rapidly <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; over time and does.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; In the case of the Microsoft environment such =
policy
is administered and <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; published between supernodes, ie servers, by A=
ctive
Directory.&nbsp; It is <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; advertised to mere peers through DNS.&nbsp; Th=
ere
was much discussion a while <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; ago about building service discovery environme=
nt
using DNS instead of a <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; P2P DHT.&nbsp; It can be argued that a case st=
udy of
a P2P example done using <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; DNS is any large Windows Server 2003 based Mic=
rosoft
network with many <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; servers and many more clients that also run
applications themselves and <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; are not just dumb terminals. This is almost
certainly always the case in <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; all enterprises. The big difference between C/=
S SIP
and P2PSIP is <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; automation. What is true is that the square pe=
g in
round hole of <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; overloading DNS makes deployments clumsy and b=
rittle
within the <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; enterprise domain and completely unmanageable =
and
unpublishable outside <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; the firewall which is why the buck stops there=
 in
current enterprise <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; networking products.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; The difference between C/S and P2P is largely =
policy
and semantics with <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; the biggest difference being that the decision=
s and
rules are highly <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; distributed.&nbsp; Apart from that they are no=
t just
friends, they are <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; fraternal twins.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Regards<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Michael Slavitch<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DM25vbGl0aGljIHNlcnZlcnMsIGZpeGVkIGVudGVycHJp
c2UgbmV0d29yayBpbnRlZ3JhdGVkIGFjY2VzcyBkZXZpY2VzIChJQUQpLCAg
QjJCVUEgZGVtYXJrcywgbmV0d29yayBlbGVtZW50cywgYW5kIGR1bWIgZml4
ZWQgZW5kcG9pbnRzLiAgVGFraW5nIGEgbmV0d29yayBhcyBhIHdob2xlIGVu
dGVycHJpc2UgYXBwbGljYXRpb24gc29mdHdhcmUgdXNpbmcgQy9TIFNJUCBw
cm94aWVzIGFuZCBVQeKAmXMgYWxyZWFkeSBhcHByb3hpbWF0ZXMgc29tZXRo
aW5nIHRoYXQgaXMgY2xvc2UgdG8gd2hhdCBpcyBiZWluZyBjYWxsZWQgUDJQ
U0lQLCBvbmx5IGluIGEgbWFubmVyIHRoYXQgaXMgaGlnaGx5IHByb3ByaWV0
YXJ5LCBjbG9zZWQsIHNvbWV3aGF0IGJyaXR0bGUgYW5kIGJhcm9xdWUsIGxv
Y2FsLCBhbmQgYWQtaG9jLCB3aXRoIGdhcGluZyB1Z2x5IGhvbGVzLiAgUDJQ
IGhhcyB0aGUgcG90ZW50aWFsIHRvIHRyYW5zZm9ybSB0aGF0Lg0KDQogDQoN
ClNvbWUgcG9pbnRzIEkgdGFrZSBmcm9tIHRoZSBwcmV2aW91cyBkaXNjdXNz
aW9uOg0KDQoNCg0K4oCcdGhhdCBhIFAyUCBzZXR1cCB3aWxsIGJlICpmcmVl
KuKAnQ0KDQogDQoNCi0gICAgICAgICAgIEEgUDJQIG5ldHdvcmsgbWF5IG5v
dCBiZSBmcmVlLCBidXQgdGhlIHNldHVwIChwcm92aXNpb25pbmcpIHdpbGwg
YmUgZnJlZSwgYW5kIGF1dG9tYXRpYy4gIFRoaXMgaXMgYSBtYWpvciBiZW5l
Zml0IG9ubHkgcGFydGlhbGx5IGFjaGlldmVkIGluIGVudGVycHJpc2UgbmV0
d29ya3MsICBhIGJlbmVmaXQgb2YgZ3JlYXQgdmFsdWUgdG8gZW50ZXJwcmlz
ZXMgdGhhdCBpcyB1bmRlcnNlcnZlZCBieSB2ZW5kb3JzLiAgVGhlcmUgaXMg
bm8gYmVuZWZpdCBpbiByZXF1aXJpbmcgY29tcGxleCBkZXBsb3ltZW50cyB3
aGVyZSBhdXRvbWF0aW9uIGNhbiB0YWtlIGl0cyBwbGFjZS4gIERlcGxveW1l
bnQgaXMgYWxtb3N0IGFsd2F5cyB0aGUgYmlnZ2VzdCBjb3N0IG9mIGVudGVy
cHJpc2Ugc3lzdGVtcyBkd2FyZmluZyB0aGUgY29zdCBvZiB0aGUgc3lzdGVt
cyB0aGVtc2VsdmVzLg0KDQogDQoNCuKAnEkgdGhpbmsgdGhpcyBkZXBlbmRz
IGdyZWF0bHkgb24gd2hhdCBleHBlY3RhdGlvbnMgLyBjb250cmFjdHVhbCBn
dWFyYW50ZWVzIHRoZSBlbnRlcnByaXNlIGhhcy4gSXTigJlzIHVuY2xlYXIg
dG8gbWUgd2hhdCBndWFyYW50ZWVzIGNhbiBiZSBtYWRlIGFib3V0IGEgUDJQ
U0lQIG5ldHdvcmsgd2lsbCBiZSBhYmxlIHRvIG1ha2UsIGFuZCBpdHMgdW5j
bGVhciB3aGF0IGtpbmQgb2YgaW5mcmFzdHJ1Y3R1cmUgd291bGQgYmUgaW5z
dGFsbGVkIGJ5L2ZvciBzb21lb25lIHdpbGxpbmcgdG8gbWFrZSBndWFyYW50
ZWVzLuKAnQ0KDQogDQoNCi0gICAgICAgICAgVGhhdCBpcyB3aHkg4oCYZXhw
ZWN0YXRpb25zL2NvbnRyYWN0dWFsIGd1YXJhbnRlZXPigJkgbmVlZCB0byBi
ZSBidWlsdCBpbnRvIHRoZSBhdXRvbWF0aW9uIHRoYXQgZXhpc3RzIGluIHRo
ZSBQMlAgb3ZlcmxheS4gIFNlbGYtY2FsY3VsYXRpb24gb2Ygc3VjaCBwZXJm
b3JtYW5jZSBtZXRyaWNzIGlzIGFscmVhZHkgdGhlcmUgaW4gYWxsIGVudGVy
cHJpc2UgZGV2aWNlcywgdGhlIGRpZmZlcmVuY2UgYmVpbmcgdGhhdCB3aGls
ZSBXTUkvU05NUCBkYXRhIGlzIG1lcmVseSBjb2xsZWN0ZWQgYSBQMlBTSVAg
bmV0d29yayBjYW4gYWN0IGF1dG9tYXRpY2FsbHkgYmFzZWQgb24gdGhlIG1l
dHJpY3Mgd2l0aGluIHRoZWlyIG93biBub2RlcywgdGhlcmUgaXMgYSBjb2xs
ZWN0aXZlIOKAmGFoYeKAmSB0aGF0IGZvcmNlcyBiZWhhdmlvciBjaGFuZ2Ug
YmFzZWQgb24gc3RyaWN0IGNvbnRyYWN0cywgYWthIHJ1bGVzLiAgQW4gU0xB
IGlzIGVhc2llciB0byBtYWludGFpbiBpZiB0aGUgb2JqZWN0cyBjYW4gcmVh
Y3QgYWNjb3JkaW5nbHksIGZvciBleGFtcGxlIGEgbm9kZSB3aXRoIGRlZ3Jh
ZGluZyBzZXJ2aWNlIGNhbiBub3RpZnkgdGhhdCBpdCBpcyBvbiB0aGUgZGVj
bGluZSBmb3JjaW5nIG90aGVycyB0byB0YWtlIG92ZXIuICANCg0KIA0KDQpU
aGVyZSBpcyBhbiBvbGQgdHJhZmZpYyBlbmdpbmVlcmluZyBheGlvbSBhYm91
dCBzZXJ2aWNlIGd1YXJhbnRlZXM6IGl0IGNhbiBiZSBhY2hpZXZlZCB0aHJv
dWdoIHR3byB3YXlzOiBvdmVyIGVuZ2luZWVyaW5nIG9yICBhdXRvbWF0aW9u
LiAgUDJQU0lQIGFsbG93cyBmb3IgYXV0b21hdGlvbi4NCg0KIA0KDQogRGF2
aWQgT3JhbiB3cm90ZToNCg0KIA0KDQrigJxJJ20gbm90IHNheWluZyB0aGlz
IGNhbid0IGJlIG1hZGUgdG8gd29yaywgb25seSB0aGF0IGl0IGlzbid0IGlt
bWVkaWF0ZWx5IG9idmlvdXMgdGhhdCBpdCBoYXMgYWR2YW50YWdlcyBvdmVy
IGEgY2xhc3NpYyBhcHBsaWNhdGlvbi9zZXJ2ZXIgYXBwcm9hY2gu4oCdDQoN
CiANCg0KVGhlIGltbWVkaWF0ZWx5IG9idmlvdXMgYWR2YW50YWdlIHRvIG1l
IGlzIHN0YW5kYXJkaXplZCBydWdnZWRpemVkIGF1dG9tYXRpb24gdGhhdCBo
YXMgZWNvbm9taWVzIG9mIHNjYWxlIGFuZCBvcGVyYXRlcyBvdmVyIG11bHRp
cGxlIGRvbWFpbnMsIGVsaW1pbmF0aW5nIHRoZSBuZWVkIGZvciBvdmVyLWVu
Z2luZWVyaW5nLCAgZGV0YWlsZWQgZnVzc3kgcHJvdmlzaW9uaW5nLCAgYW5k
IGFuIGFybXkgb2YgcGVvcGxlIGRvaW5nIGJhc2ljIG1vbml0b3JpbmcgYW5k
IGNhcmUtYW5kLWZlZWRpbmcuICBBdXRvbWF0aW9uIGlzIHRoZSBrZXksIGEg
ZHluYW1pYyBzdGF0aXN0aWNhbCBuZXR3b3JrIHZzLiBvbmUgdGhhdCBpcyBm
aXhlZCBhbmQgYXNzdW1lZCBkZXRlcm1pbmlzdGljIHdpbGwgYWx3YXlzIHdp
biBvdXQgb3ZlciB0aW1lIGdpdmVuIGEgZnJhY3RhbCBvcGVyYXRpbmcgZW52
aXJvbm1lbnQuICAgVGhpcyBpcyBiZWluZyBkb25lIGluIGZpdHMgYW5kIHN0
YXJ0cyBpbiB0aGUgZW50ZXJwcmlzZSBkYXRhIGNlbnRlci4gICBQMlBTSVAg
bWFrZXMgaXQgbXVjaCBtb3JlIGNvbXByZWhlbnNpdmUuICAgUGVvcGxlIHdh
bnQgdGhlIHdvcmxkIHRvIGJlIHByZWRpY3RhYmxlIGFuZCBkZXRlcm1pbmlz
dGljLCAgYW5kIEMvUyBiYXNlZCsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; corp_2colour <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; &lt;https://firewall.objectworld.com/exchweb/b=
in/redir.asp?URL=3Dhttp://www.objectworld.com/&gt;<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <st1:Street w:st=3D"on"><st1:address w:st=3D"o=
n">308
  Legget Dr</st1:address></st1:Street>.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <st1:place w:st=3D"on"><st1:City w:st=3D"on">O=
ttawa</st1:City>
 <st1:State w:st=3D"on">Ontario</st1:State></st1:place><o:p></o:p></p>

<p class=3DMsoPlainText>&gt; K2K 1Y6 <st1:country-region w:st=3D"on"><st1:p=
lace
 w:st=3D"on">Canada</st1:place></st1:country-region><o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://map=
s.google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2BOnta=
rio%2BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.007119,0=
.023839%26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.00178,0.=
00596%26t=3Dh%26om=3D1&gt;<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Michael
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Lead, Technology Initiatives<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; slavitch@objectworld.com
&lt;mailto:slavitch@objectworld.com&gt;<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; PSTN: <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; +1.888.398.9698<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; x225<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Fax:<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; +1.613.599.7457<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:=
p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p><BzeXN0ZW1zIHJlZmxlY3QgdGhhdC4gVGhh
dCBpcyB0aGUgYmlnZ2VzdCBwcm9ibGVtIFAyUCBmYWNlcyBiZWNhdXNlIGl0
IGZsaWVzIGluIHRoZSBmYWNlIG9mIHRyYWRpdGlvbi4gICANCg0KIA0KDQpS
ZWdhcmRzDQoNCiANCg0KTWljaGFlbCBTbGF2aXRjaA0KDQogDQoNCiANCg0K
IA0KDQogDQoNCiANCg0KICA8aHR0cDovL3d3dy5vYmplY3R3b3JsZC5jb20v
PiANCg0KIA0KDQozMDggTGVnZ2V0IERyLiANCk90dGF3YSBPbnRhcmlvIA0K
SzJLIDFZNiBDYW5hZGENCg0KICA8aHR0cDovL21hcHMuZ29vZ2xlLmNhL21h
cHM/Zj1xJmhsPWVuJnE9MzA4K0xlZ2dldCtEcml2ZStPdHRhd2ErT250YXJp
bytLMksrMVk2JmxheWVyPSZzbGw9NDUuMzQxMDYxLC03NS45MDQ1NDEmc3Nw
bj0wLjAwNzExOSwwLjAyMzgzOSZpZT1VVEY4Jno9MTgmbGw9NDUuMzQxMDYx
LC03NS45MDQ1NDEmc3BuPTAuMDAxNzgsMC4wMDU5NiZ0PWgmb209MT4gDQoN
CiAJIA0KTWljaGFlbCBTbGF2aXRjaCAgICAgICAgICAgICAgDQoNCkxlYWQs
IFRlY2hub2xvZ3kgSW5pdGlhdGl2ZXMNCg0Kc2xhdml0Y2hAb2JqZWN0d29y
bGQuY29tDQoNClBTVE46ICANCg0KKzEuODg4LjM5OC45Njk4DQoNCngyMjUN
Cg0KRmF4Og0KDQorMS42MTMuNTk5Ljc0NTcNCg0KIA0KDQpTa3lwZTogICAg
ICAgDQoNCiBPYmplY3R3b3JsZCAgIA0KDQp4MjI1DQoNCiAgPHNreXBlOk9i
amVjdHdvcmxkPiANCg0KIAkgDQoNCiANCg0KIA0KDQotLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KRnJvbTogUGF1bCBLeXppdmF0IFttYWlsdG86cGt5
eml2YXRAY2lzY28uY29tXSANClNlbnQ6IFR1ZXNkYXksIEFwcmlsIDAzLCAy
MDA3IDg6NTcgQU0NClRvOiBNaWNoYWVsIFNsYXZpdGNoDQpDYzogSGVucnkg
U2lubnJlaWNoOyBQMlBTSVAgTWFpbGluZyBMaXN0OyBNaWNoYWVsIEhhbW1l
ciAobWhhbW1lcik7IERhdmlkIFIgT3JhbjsgcDJwcmdAaWV0Zi5vcmc7IHNp
cHBpbmdAaWV0Zi5vcmc7IHpodXhpYW4NClN1YmplY3Q6IFJlOiBbUDJQcmdd
IFJFOiBbU2lwcGluZ10gU2ltcGxlIFNJUCB1c2FnZSBzY2VuYXJpbw0KDQog
DQoNCiANCg0KIA0KDQpNaWNoYWVsIFNsYXZpdGNoIHdyb3RlOg0KDQo+IFNv
cnJ5IGZvciBiZWluZyBsYXRlIGludG8gdGhpcyBkaXNjdXNzaW9uLCBidXQg
Y2xpZW50LXNlcnZlciBiYXNlZCBWTSANCg0KPiBpc24ndCB0cnVseSBjbGll
bnQtc2VydmVyIGFueW1vcmUgaW4gYW55dGhpbmcgYnV0IHRoZSBzbWFsbGVz
dCBvciBtb3N0IA0KDQo+IG1vbm9saXRoaWMgb2YgZW50ZXJwcmlzZSBuZXR3
b3JrcywgaW4gZmFjdCB0aGUgcmVhbGl0eSBpcyB0aGF0IG1vc3QgaWYgDQoN
Cj4gbm90IGFsbCBlbnRlcnByaXNlIG5ldHdvcmtzIGNvbnRhaW4ganVzdCBw
ZWVycyBhbmQgc3VwZXJwZWVycyB3aXRoIHRoZSANCg0KPiBkaWZmZXJlbmNl
IGJlaW5nIHBhcnRpYWxseSBhIG1hcmtldGluZyBkZWNpc2lvbiBieSB0aGUg
dmVuZG9ycywgYXMgeW91IA0KDQo+IGNhbiBjaGFyZ2UgbXVjaCBtb3JlIGZv
ciB0aGUgc2VydmVycywgYW5kIGEgcG9saWN5IGRlY2lzaW9uIG1hZGUgZWl0
aGVyIA0KDQo+IGF1dG9tYXRpY2FsbHkgYnkgYSBzb2Z0d2FyZSBkZXBsb3lt
ZW50IHN5c3RlbSBvciBieSBJVCBzdGFmZiB3aGljaCB3YW50cyANCg0KPiB0
byBwbGFjZSBzdXBlcm5vZGVzIHdpdGggZGF0YSBzaW5rcyBvbiBhcHByb3By
aWF0ZSBlcXVpcG1lbnQuDQoNCiANCg0KSSdtIHNvcnJ5LCBidXQgSSBkb24n
dCB1bmRlcnN0YW5kIHRoZSBwb2ludCB5b3UgYXJlIHRyeWluZyB0byBtYWtl
IA0KDQphYm92ZS4gWW91IGFyZSB0cnlpbmcgdG8gZHJhdyBzb21lIHNvcnQg
b2YgZGlzdGluY3Rpb24sIGJ1dCBJIGRvbid0IGdldCANCg0KaXQuIENhbiB5
b3UgdHJ5IGFnYWluLg0KDQogDQoNCiAgICAgICAgICAgICAgICBUaGFua3Ms
DQoNCiAgICAgICAgICAgICAgICBQYXVsDQoNCiANCg0KPiBJbiBhIA0KDQo+
IGhpZ2hseSBkaXN0cmlidXRlZCBlbnZpcm9ubWVudCB0aGVyZSBhcmUgcG90
ZW50aWFsbHkgaHVuZHJlZHMgb2YgDQoNCj4gcG9zc2libGUgZGF0YSBzaW5r
cyBmb3IgYSBnaXZlbiBhcHBsaWNhdGlvbiwgd2l0aCB0aGUgc2luayBiYXNl
ZCBvbiANCg0KPiBzdWJuZXQgb3IgZ2VvZ3JhcGhpYyBsb2NhdGlvbiBvciBi
YWxhbmNlZCBsb2FkLCB0aGlzIGNhbiBjaGFuZ2UgcmFwaWRseSANCg0KPiBv
dmVyIHRpbWUgYW5kIGRvZXMuDQoNCj4gDQoNCj4gSW4gdGhlIGNhc2Ugb2Yg
dGhlIE1pY3Jvc29mdCBlbnZpcm9ubWVudCBzdWNoIHBvbGljeSBpcyBhZG1p
bmlzdGVyZWQgYW5kIA0KDQo+IHB1Ymxpc2hlZCBiZXR3ZWVuIHN1cGVybm9k
ZXMsIGllIHNlcnZlcnMsIGJ5IEFjdGl2ZSBEaXJlY3RvcnkuICBJdCBpcyAN
Cg0KPiBhZHZlcnRpc2VkIHRvIG1lcmUgcGVlcnMgdGhyb3VnaCBETlMuICBU
aGVyZSB3YXMgbXVjaCBkaXNjdXNzaW9uIGEgd2hpbGUgDQoNCj4gYWdvIGFi
b3V0IGJ1aWxkaW5nIHNlcnZpY2UgZGlzY292ZXJ5IGVudmlyb25tZW50IHVz
aW5nIEROUyBpbnN0ZWFkIG9mIGEgDQoNCj4gUDJQIERIVC4gIEl0IGNhbiBi
ZSBhcmd1ZWQgdGhhdCBhIGNhc2Ugc3R1ZHkgb2YgYSBQMlAgZXhhbXBsZSBk
b25lIHVzaW5nIA0KDQo+IEROUyBpcyBhbnkgbGFyZ2UgV2luZG93cyBTZXJ2
ZXIgMjAwMyBiYXNlZCBNaWNyb3NvZnQgbmV0d29yayB3aXRoIG1hbnkgDQoN
Cj4gc2VydmVycyBhbmQgbWFueSBtb3JlIGNsaWVudHMgdGhhdCBhbHNvIHJ1
biBhcHBsaWNhdGlvbnMgdGhlbXNlbHZlcyBhbmQgDQoNCj4gYXJlIG5vdCBq
dXN0IGR1bWIgdGVybWluYWxzLiBUaGlzIGlzIGFsbW9zdCBjZXJ0YWlubHkg
YWx3YXlzIHRoZSBjYXNlIGluIA0KDQo+IGFsbCBlbnRlcnByaXNlcy4gVGhl
IGJpZyBkaWZmZXJlbmNlIGJldHdlZW4gQy9TIFNJUCBhbmQgUDJQU0lQIGlz
IA0KDQo+IGF1dG9tYXRpb24uIFdoYXQgaXMgdHJ1ZSBpcyB0aGF0IHRoZSBz
cXVhcmUgcGVnIGluIHJvdW5kIGhvbGUgb2YgDQoNCj4gb3ZlcmxvYWRpbmcg
RE5TIG1ha2VzIGRlcGxveW1lbnRzIGNsdW1/p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp;&nbsp; Objectworld <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,=
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20a=
nd%20MME.EML/&gt;&nbsp;&nbsp;
<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; x225<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,=
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20a=
nd%20MME.EML/&gt;<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>-- <o:p></o:p></p>

<p class=3DMsoPlainText>BEGIN-ANTISPAM-VOTING-LINKS<o:p></o:p></p>

<p class=3DMsoPlainText>---------------------------------------------------=
---<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Teach CanIt if this mail (ID 657805) is spam:<o:p><=
/o:p></p>

<p class=3DMsoPlainText>Spam:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fdee=
55b7&amp;c=3Ds<o:p></o:p></p>

<p class=3DMsoPlainText>Not spam:&nbsp;&nbsp;&nbsp; http://canitpro-int.obj=
ectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fdee55b7&amp;c=3Dn<o:p></o:=
p></p>

<p class=3DMsoPlainText>Forget vote:
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fdee=
55b7&amp;c=3Df<o:p></o:p></p>

<p class=3DMsoPlainText>---------------------------------------------------=
---<o:p></o:p></p>

<p class=3DMsoPlainText>END-ANTISPAM-VOTING-LINKS<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p><span style=3D'font-size:7.5pt'>This transmission (including any attachm=
ents)
may contain confidential information, privileged material (including materi=
al
protected by the solicitor-client or other applicable privileges), or
constitute non-public information. Any use of this information by anyone ot=
her
than the intended recipient is prohibited. If you have received this
transmission in error, please immediately reply to the sender and delete th=
is
information from your system. Use, dissemination, distribution, or reproduc=
tion
of this transmission by unintended recipients is not authorized and may be
unlawful.<o:p></o:p></span></p>

<p><span style=3D'font-size:7.5pt'>Any views, opinions and content presente=
d in
this e-mail are solely those of the author and may not represent those of
Objectworld Communications Corp.<o:p></o:p></span></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:13.5pt;font-family:"Times New Roman","serif";color:black;
background:white'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal><span style=3D'font-size:13.5pt;font-family:"Times New=
 Roman","serif";
color:black;background:white'><bzeSBhbmQgYnJpdHRsZSB3aXRo
aW4gdGhlIA0KDQo+IGVudGVycHJpc2UgZG9tYWluIGFuZCBjb21wbGV0ZWx5
IHVubWFuYWdlYWJsZSBhbmQgdW5wdWJsaXNoYWJsZSBvdXRzaWRlIA0KDQo+
IHRoZSBmaXJld2FsbCB3aGljaCBpcyB3aHkgdGhlIGJ1Y2sgc3RvcHMgdGhl
cmUgaW4gY3VycmVudCBlbnRlcnByaXNlIA0KDQo+IG5ldHdvcmtpbmcgcHJv
ZHVjdHMuDQoNCj4gDQoNCj4gVGhlIGRpZmZlcmVuY2UgYmV0d2VlbiBDL1Mg
YW5kIFAyUCBpcyBsYXJnZWx5IHBvbGljeSBhbmQgc2VtYW50aWNzIHdpdGgg
DQoNCj4gdGhlIGJpZ2dlc3QgZGlmZmVyZW5jZSBiZWluZyB0aGF0IHRoZSBk
ZWNpc2lvbnMgYW5kIHJ1bGVzIGFyZSBoaWdobHkgDQoNCj4gZGlzdHJpYnV0
ZWQuICBBcGFydCBmcm9tIHRoYXQgdGhleSBhcmUgbm90IGp1c3QgZnJpZW5k
cywgdGhleSBhcmUgDQoNCj4gZnJhdGVybmFsIHR3aW5zLg0KDQo+IA0KDQo+
IFJlZ2FyZHMNCg0KPiANCg0KPiBNaWNoYWVsIFNsYXZpdGNoDQoNCj4gDQoN
Cj4gIA0KDQo+IA0KDQo+IA0KDQo+IGNvcnBfMmNvbG91ciANCg0KPiA8aHR0
cHM6Ly9maXJld2FsbC5vYmplY3R3b3JsZC5jb20vZXhjaHdlYi9iaW4vcmVk
aXIuYXNwP1VSTD1odHRwOi8vd3d3Lm9iamVjdHdvcmxkLmNvbS8+DQoNCj4g
DQoNCj4gIA0KDQo+IA0KDQo+ICAgICAgICAgICAgIA0KDQo+IA0KDQo+IDMw
OCBMZWdnZXQgRHIuDQoNCj4gT3R0YXdhIE9udGFyaW8NCg0KPiBLMksgMVk2
IENhbmFkYQ0KDQo+IA0KDQo+ICAgICAgICAgICAgIA0KDQo+IA0KDQo+IDxo
dHRwczovL2ZpcmV3YWxsLm9iamVjdHdvcmxkLmNvbS9leGNod2ViL2Jpbi9y
ZWRpci5hc3A/VVJMPWh0dHA6Ly9tYXBzLmdvb2dsZS5jYS9tYXBzP2Y9cSUy
NmhsPWVuJTI2cT0zMDglMkJMZWdnZXQlMkJEcml2ZSUyQk90dGF3YSUyQk9u
dGFyaW8lMkJLMkslMkIxWTYlMjZsYXllcj0lMjZzbGw9NDUuMzQxMDYxLC03
NS45MDQ1NDElMjZzc3BuPTAuMDA3MTE5LDAuMDIzODM5JTI2aWU9VVRGOCUy
Nno9MTglMjZsbD00NS4zNDEwNjEsLTc1LjkwNDU0MSUyNnNwbj0wLjAwMTc4
LDAuMDA1OTYlMjZ0PWglMjZvbT0xPg0KDQo+IA0KDQo+ICAgICAgICAgICAg
IA0KDQo+IA0KDQo+ICANCg0KPiANCg0KPiBNaWNoYWVsIFNsYXZpdGNoICAg
ICAgICAgICAgIA0KDQo+IA0KDQo+IExlYWQsIFRlY2hub2xvZ3kgSW5pdGlh
dGl2ZXMNCg0KPiANCg0KPiBzbGF2aXRjaEBvYmplY3R3b3JsZC5jb20gPG1h
aWx0bzpzbGF2aXRjaEBvYmplY3R3b3JsZC5jb20+DQoNCj4gDQoNCj4gICAg
ICAgICAgICAgDQoNCj4gDQoNCj4gUFNUTjogDQoNCj4gDQoNCj4gICAgICAg
ICAgICAgDQoNCj4gDQoNCj4gKzEuODg4LjM5OC45Njk4DQoNCj4gDQoNCj4g
ICAgICAgICAgICAgDQoNCj4gDQoNCj4geDIyNQ0KDQo+IA0KDQo+IEZheDoN
Cg0KPiANCg0KPiAgICAgICAgICAgICANCg0KPiANCg0KPiArMS42MTMuNTk5
Ljc0NTcNCg0KPiANCg0KPiAgICAgICAgICAgICANCg0KPiANCg0KPiAgDQoN
Cj4gDQoNCj4gU2t5cGU6ICAgICAgDQoNCj4gDQoNCj4gICAgICAgICAgICAg
DQoNCj4gDQoNCj4gICBPYmplY3R3b3JsZCANCg0KPiA8aHR0cHM6Ly9maXJl
d2FsbC5vYmplY3R3b3JsZC5jb20vZXhjaGFuZ2Uvc2xhdml0Y2gvU2VudCUy
MEl0ZW1zL05vcnRlbCwlMjBNU0ZUJTIwY2hhc2UlMjBjYXJyaWVycyUyMHdp
dGglMjBuZXclMjBob3N0ZWQlMjBvZmZlcmluZyUyMGZvciUyMFNNRSUyMGFu
ZCUyME1NRS5FTUwvPiAgIA0KDQo+IA0KDQo+IA0KDQo+ICAgICAgICAgICAg
IA0KDQo+IA0KDQo+IHgyMjUNCg0KPiANCg0KPiAgICAgICAgICAgICANCg0K
PiANCg0KPiA8aHR0cHM6Ly9maXJld2FsbC5vYmplY3R3b3JsZC5jb20vZXhj
aGFuZ2Uvc2xhdml0Y2gvU2VudCUyMEl0ZW1zL05vcnRlbCwlMjBNU0ZUJTIw
Y2hhc2UlMjBjYXJyaWVycyUyMHdpdGglMjBuZXclMjBob3N0ZWQlMjBvZmZl
cmluZyUyMGZvciUyMFNNRSUyMGFuZCUyME1NRS5FTUwvPg0KDQo+IA0KDQo+
ICAgICAgICAgICAgIA0KDQo+IA0KDQo+ICANCg0KPiANCg0KPiAgDQoNCj4g
DQoNCj4gDQoNCiANCg0KIA0KDQotLSANCg0KDQogDQoNCgotLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpUaGlz
IHRyYW5zbWlzc2lvbiAoaW5jbHVkaW5nIGFueSBhdHRhY2htZW50cykgbWF5
IGNvbnRhaW4gY29uZmlkZW50aWFsIGluZm9ybWF0aW9uLCBwcml2aWxlZ2Vk
IG1hdGVyaWFsIChpbmNsdWRpbmcgbWF0ZXJpYWwgcHJvdGVjdGVkIGJ5IHRo
ZSBzb2xpY2l0b3ItY2xpZW50IG9yIG90aGVyIGFwcGxpY2FibGUgcHJpdmls
ZWdlcyksIG9yIGNvbnN0aXR1dGUgbm9uLXB1YmxpYyBpbmZvcm1hdGlvbi4g
QW55IHVzZSBvZiB0aGlzIGluZm9ybWF0aW9uIGJ5IGFueW9uZSBvdGhlciB0
aGFuIHRoZSBpbnRlbmRlZCByZWNpcGllbnQgaXMgcHJvaGliaXRlZC4gSWYg
eW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4gZXJyb3Is
IHBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2VuZGVyIGFuZCBk
ZWxldGUgdGhpcyBpbmZvcm1hdGlvbiBmcm9tIHlvdXIgc3lzdGVtLiBVc2Us
IGRpc3NlbWluYXRpb24sIGRpc3RyaWJ1dGlvbiwgb3IgcmVwcm9kdWN0aW9u
IG9mIHRoaXMgdHJhbnNtaXNzaW9uIGJ5IHVuaW50ZW5kZWQgcmVjaXBpZW50
cyBpcyBub3QgYXV0aG9yaXplZCBhbmQgbWF5IGJlIHVubGF3ZnVsLiANCg0K
QW55IHZpZXdzLCBvcGluaW9ucyBhbmQgY29udGVudCBwcmVzZW50ZWQgaW4g
dGhpcyBlLW1haWwgYXJlIHNvbGVseSB0aG9zZSBvZiB0aGUgYXV0aG9yIGFu
ZCBtYXkgbm90IHJlcHJlc2VudCB0aG9zZSBvZiBPYmplY3R3b3JsZCBDb21t
dW5pY2F0aW9ucyBDb3JwLiAK

------_=_NextPart_002_01C775FF.19CEFDE7
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64
Content-Disposition: inline

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2r>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Ds">Spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Dn">Not
spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Df">Forget
previous vote</a></span><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'><o:p></o:p></span></p>

</div>

</div>

</div>

<hr width=3D"100%">=0D
<font size=3D"-2"><p>=0D
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful.</p>=0D
=0D
<p>Any views, opinions and content presented in this e-mail are solely thos=
e of the author and may not represent those of Objectworld Communications C=
orp.</p>=0D
</font>
</body>

</html>

------_=_NextPart_002_01C77619.9FFAEC5B--

------_=_NextPart_001_01C77619.9FFAEC5B
Content-Type: image/jpeg;
	name="image002.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image002.jpg@01C775F8.17EDD430>
Content-Description: image002.jpg
Content-Location: image002.jpg
Content-Disposition: inline

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N
Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/
2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIAAhEBAxEB/8QA
HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF
BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1
dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB
AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC
AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom
JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6+0Eb
NruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHEx
lWYK4wpGMhueleLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9
clnAj17UWQKd3+kNjPb+tN/s+6bR21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1
IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHNR/8AAlv8a9P8NWv/
AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1
U9W1W00TSrjU76Qx29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GF
E6eqnPpzXoHzp19FZniHXIPDmhXOr3McksNsoZkjxuOSBxn61ieHPiLpniHV
V0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc3dpDNClvcvbM
JQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq3
9uaTFqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jH
GM/M3Psa2tC1uy8RaPb6rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFrea
PqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+w3Vj5hYeRdJskXBxyKANGisR
vFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6vRZpDhd+8
n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA
2fxg0W4nTz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumt
pPNA+Zh3GD0oA26KiuJltraWdgSsSFyB1IAzXE6N8WtG1a7tIZNP1GxivZPK
t7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8kKcE9M5IrD1H4h6Hplta
zzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+jtPI
2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1Lvg
Ehv5V4sNKivtc+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m
1u7X7PGJ4vL+zRoFMe3J3YHY5x9a1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD
059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej3PAy/C1qWJTmmkt+
vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLN
d74l0OHxJ4evNInkMSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZ
rKOGLYFXGMse5wf/AK9ekfLl74p/8k31j/rmv/oa1xfhqXUW+IHhl/E0MVuf
7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5C4YHp+Fc5oHg
DVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu1
1WK/m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYH
A9OBQByXjWXV4fi9oj6Fb29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRq
Z0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xaWxgBkg8zqWycHjo1dFoNtq1p
paQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs9CsdDjg8
OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/g
K2/CHhuLwn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ce
FpvFmlWtlDdJbNBdpcFnUsCFB44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r
8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1Lx54N/4TPT7K2FwsDWt0
sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/AJoe
P+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6W
v+oH+7/SvnjT59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrz
ofC+5XwYNFXUoReQ6l9vt7nyzhD6YznpmgD0RFCIqDooArz34S/e8Uf9hmWv
Qk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2gYsC2SMnOOOOKAO4
1X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689G
HQ1lT+EdCuQBLYK2CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgB
umKworm4ESATyYCj+M0j3M5KZnk4bj5zXjey97c+4WK/dr3e39bG/ChiiCEj
Iz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5OW5+c+lCpbu4
5YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckx
Nyf99q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFA
BRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAH//Z

------_=_NextPart_001_01C77619.9FFAEC5B
Content-Type: image/jpeg;
	name="image005.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image005.jpg@01C775F8.17EDD430>
Content-Description: image005.jpg
Content-Location: image005.jpg
Content-Disposition: inline

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N
Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/
2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIAAhEBAxEB/8QA
HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF
BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1
dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB
AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC
AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom
JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6+0Eb
NruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHEx
lWYK4wpGMhueleLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9
clnAj17UWQKd3+kNjPb+tN/s+6bR21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1
IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHNR/8AAlv8a9P8NWv/
AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1
U9W1W00TSrjU76Qx29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GF
E6eqnPpzXoHzp19FZniHXIPDmhXOr3McksNsoZkjxuOSBxn61ieHPiLpniHV
V0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc3dpDNClvcvbM
JQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq3
9uaTFqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jH
GM/M3Psa2tC1uy8RaPb6rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFrea
PqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+w3Vj5hYeRdJskXBxyKANGisR
vFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6vRZpDhd+8
n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA
2fxg0W4nTz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumt
pPNA+Zh3GD0oA26KiuJltraWdgSsSFyB1IAzXE6N8WtG1a7tIZNP1GxivZPK
t7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8kKcE9M5IrD1H4h6Hplta
zzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+jtPI
2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1Lvg
Ehv5V4sNKivtc+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m
1u7X7PGJ4vL+zRoFMe3J3YHY5x9a1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD
059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej3PAy/C1qWJTmmkt+
vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLN
d74l0OHxJ4evNInkMSXKbfbWwi
IHhtbG5zOm89InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9m
ZmljZSIgeG1sbnM6dz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZp
Y2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNv
bS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5v
cmcvVFIvUkVDLWh0bWw0MCI+DQoNCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj1Db250ZW50LVR5cGUgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0
Zi04Ij4NCjxtZXRhIG5hbWU9R2VuZXJhdG9yIGNvbnRlbnQ9Ik1pY3Jvc29m
dCBXb3JkIDEyIChmaWx0ZXJlZCBtZWRpdW0pIj4NCjwhLS1baWYgIW1zb10+
DQo8c3R5bGU+DQp2XDoqIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9
DQpvXDoqIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQp3XDoqIHti
ZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQouc2hhcGUge2JlaGF2aW9y
OnVybCgjZGVmYXVsdCNWTUwpO30NCjwvc3R5bGU+DQo8IVtlbmRpZl0tLT4N
CjxzdHlsZT4NCjwhLS0NCiAvKiBGb250IERlZmluaXRpb25zICovDQogQGZv
bnQtZmFjZQ0KCXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6
NSAwIDAgMCAwIDAgMCAwIDAgMDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFt
aWx5OldpbmdkaW5nczsNCglwYW5vc2UtMTo1IDAgMCAwIDAgMCAwIDAgMCAw
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5v
c2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2Zv
bnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0
IDIgNDt9DQogLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCiBwLk1zb05vcm1h
bCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47
DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQphOmxp
bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5
OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7
fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1zb1BsYWluVGV4dCwgbGkuTXNv
UGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCBDaGFyIjsN
CgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250
LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z
ZXJpZiI7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNv
QWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxl
LWxpbms6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1h
cmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9u
dC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnNwYW4uUGxhaW5U
ZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiUGxhaW4gVGV4dCBDaGFyIjsN
Cgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBs
YWluIFRleHQiOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJp
ZiI7fQ0Kc3Bhbi5CYWxsb29uVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6
IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxvb24gVGV4dCI7DQoJZm9udC1mYW1p
bHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCi5Nc29DaHBEZWZhdWx0DQoJ
e21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5O30NCkBwYWdlIFNlY3Rpb24x
DQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAx
LjBpbiAxLjBpbjt9DQpkaXYuU2VjdGlvbjENCgl7cGFnZTpTZWN0aW9uMTt9
DQogLyogTGlzdCBEZWZpbml0aW9ucyAqLw0KIEBsaXN0IGwwDQoJe21zby1s
aXN0LWlkOjg0Njg2NzE5NzsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCglt
c28tbGlzdC10ZW1wbGF0ZS1pZHM6LTEzOTgwNTAzOCAtMTcxNDc4MzQ4MiA2
NzY5ODY5MSA2NzY5ODY5MyA2NzY5ODY4OSA2NzY5ODY5MSA2NzY5ODY5MyA2
NzY5ODY4OSA2NzY5ODY5MSA2NzY5ODY5Mzt9DQpAbGlzdCBsMDpsZXZlbDEN
Cgl7bXNvLWxldmVsLXN0YXJ0LWF0OjA7DQoJbXNvLWxldmVsLW51bWJlci1m
b3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Oi07DQoJbXNvLWxldmVs
LXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjps
ZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsInNhbnMtc2VyaWYiOw0KCW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5
OkNhbGlicmk7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBS
b21hbiI7fQ0Kb2wNCgl7bWFyZ2luLWJvdHRvbTowaW47fQ0KdWwNCgl7bWFy
Z2luLWJvdHRvbTowaW47fQ0KLS0+DQo8L3N0eWxlPg0KPCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQogPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIg
c3BpZG1heD0iMjA1MCIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYg
Z3RlIG1zbyA5XT48eG1sPg0KIDxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0
Ij4NCiAgPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQogPC9v
OnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KDQo8
Ym9keSBsYW5nPUVOLVVTIGxpbms9Ymx1ZSB2bGluaz1wdXJwbGU+DQoNCjxk
aXYgY2xhc3M9U2VjdGlvbjE+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD5U
aGUgMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZ
rKOGLYFXGMse5wf/AK9ekfLl74p/8k31j/rmv/oa1xfhqXUW+IHhl/E0MVuf
7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5C4YHp+Fc5oHg
DVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu1
1WK/m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYH
A9OBQByXjWXV4fi9oj6Fb29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRq
Z0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xaWxgBkg8zqWycHjo1dFoNtq1p
paQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs9CsdDjg8
OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/g
K2/CHhuLwn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ce
FpvFmlWtlDdJbNBdpcFnUsCFB44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r
8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1Lx54N/4TPT7K2FwsDWt0
sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/AJoe
P+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6W
v+oH+7/SvnjT59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrz
ofC+5XwYNFXUoReQ6l9vt7nyzhD6YznpmgD0RFCIqDooArz34S/e8Uf9hmWv
Qk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2gYsC2SMnOOOOKAO4
1X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689G
HQ1lT+EdCuQBLYK2CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgB
umKworm4ESATyYCj+M0j3M5KZnk4bj5zXjey97c+4WK/dr3e39bG/ChiiCEj
Iz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5OW5+c+lCpbu4
5YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckx
Nyf99q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFA
BRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAH//Z

------_=_NextPart_001_01C77619.9FFAEC5B
Content-Type: image/jpeg;
	name="image006.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image006.jpg@01C775F8.17EDD430>
Content-Description: image006.jpg
Content-Location: image006.jpg
Content-Disposition: inline

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N
Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/
2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAdAB0DASIAAhEBAxEB/8QA
HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF
BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1
dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB
AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC
AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom
JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD0/VNWWCU2
0cnllQPMkAyVz0A9/wCVUylrNEHWKOZjysk+XP5nmua1W8kXU7pZDg+e/wCW
7A/TFPs9UmmUWquq8fK3cf4168cNywTR5EsTzTakdDFqT2M20l2j6mMknI7l
c8j6dK6GORJY1kjYMrDII7ivOruSeB0lklDljgHNdh4ald9Fi39iwX/dycfp
iufFUVGKmjowtZyk4M5/xhoUzXDX9qhbf/rFA5z6j1rjo5pILhGIHytzzivZ
nRZFKsAQazptCspX3NGM/SnQx0qceWSuia+AjUnzxdmef2ttd61f5XcIQcBs
cAe3qa9J0+1W0s44VGAqgAegotrC3th8ic+tWq56+IlWavokdFDDxop21b6n
/9k=

------_=_NextPart_001_01C77619.9FFAEC5B
Content-Type: image/jpeg;
	name="image007.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image007.jpg@01C775F8.17EDD430>
Content-Description: image007.jpg
Content-Location: image007.jpg
Content-Disposition: inline

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N
Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/
2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAaABoDASIAAhEBAxEB/8QA
HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF
BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1
dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB
AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC
AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom
JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1Ga7lkZ2S
dokV2VQgXJwcEnIPcG9pbnQgSSBhbSBtYWtpbmcgaXPCoCB0aGF0IGluIHRoZSBlbnRlcnBy
aXNlIHRoZSBhY3R1YWwNCnRvcG9sb2dpY2FsIGRlcGxveW1lbnRzIG9mIFNJ
UCBjbGllbnRzIGFuZCBzZXJ2ZXJzLCA8aT53aGVuIGltcGxlbWVudGVkIGFz
IHNvZnR3YXJlDQpvbiBnZW5lcmljIGNvbXB1dGluZyBwbGF0Zm9ybXM8L2k+
LCBhcyB3ZWxsIGFzIHRoZSA8aT5tZWNoYW5pc21zIHRoYXQgbWFrZSB0aGF0
DQpkZXBsb3ltZW50IGhhcHBlbjwvaT4sIGFyZSBhbHJlYWR5IHZlcnkgZGlm
ZmVyZW50IHdvcmxkIHRoYW4gdGhlIGNhbm9uaWNhbA0KSU1TL0NTU0lQIG9u
ZSB3aGljaCDCoGFzc3VtZXMgU0lQIGFzIGNvcmUgbW9ub2xpdGhpYyBzZXJ2
ZXJzLCBmaXhlZCBlbnRlcnByaXNlDQpuZXR3b3JrIGludGVncmF0ZWQgYWNj
ZXNzIGRldmljZXMgKElBRCksIMKgQjJCVUEgZGVtYXJrcywgbmV0d29yayBl
bGVtZW50cywgYW5kIGR1bWINCmZpeGVkIGVuZHBvaW50cy7CoCBUYWtpbmcg
YSBuZXR3b3JrIGFzIGEgd2hvbGUgZW50ZXJwcmlzZSBhcHBsaWNhdGlvbiBz
b2Z0d2FyZSB1c2luZw0KQy9TIFNJUCBwcm94aWVzIGFuZCBVQeKAmXMgPGk+
YWxyZWFkeTwvaT4gYXBwcm94aW1hdGVzIHNvbWV0aGluZyB0aGF0IGlzIGNs
b3NlIHRvDQp3aGF0IGlzIGJlaW5nIGNhbGxlZCBQMlBTSVAsIG9ubHkgaW4g
YSBtYW5uZXIgdGhhdCBpcyBoaWdobHkgcHJvcHJpZXRhcnksDQpjbG9zZWQs
IHNvbWV3aGF0IGJyaXR0bGUgYW5kIGJhcm9xdWUsIGxvY2FsLCBhbmQgYWQt
aG9jLCB3aXRoIGdhcGluZyB1Z2x5IGhvbGVzLsKgDQpQMlAgaGFzIHRoZSBw
b3RlbnRpYWwgdG8gdHJhbnNmb3JtIHRoYXQuPG86cD48L286cD48L3A+DQoN
CjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
Cg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PlNvbWUgcG9pbnRzIEkgdGFrZSBm
cm9tIHRoZSBwcmV2aW91cyBkaXNjdXNzaW9uOjxicj4NCjxicj4NCjxvOnA+
PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+4oCcdGhhdCBh
IFAyUCBzZXR1cCB3aWxsIGJlICpmcmVlKuKAnTxvOnA+PC9vOnA+PC9wPg0K
DQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4mbmJzcDs8L286cD48L3A+
DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dCBzdHlsZT0nbWFyZ2luLWxlZnQ6
LjVpbjt0ZXh0LWluZGVudDotLjI1aW47bXNvLWxpc3Q6bDAgbGV2ZWwxIGxm
bzEnPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuDQpzdHlsZT0nbXNvLWxp
c3Q6SWdub3JlJz4tPHNwYW4gc3R5bGU9J2ZvbnQ6Ny4wcHQgIlRpbWVzIE5l
dyBSb21hbiInPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+
wqBBIFAyUCBuZXR3b3JrIG1heSBub3QgYmUgZnJlZSwgYnV0IHRoZSBzZXR1
cCAocHJvdmlzaW9uaW5nKQ0Kd2lsbCBiZSBmcmVlLCBhbmQgYXV0b21hdGlj
LsKgIFRoaXMgaXMgYSBtYWpvciBiZW5lZml0IG9ubHkgcGFydGlhbGx5IGFj
aGlldmVkDQppbiBlbnRlcnByaXNlIG5ldHdvcmtzLMKgIGEgYmVuZWZpdCBv
ZiBncmVhdCB2YWx1ZSB0byBlbnRlcnByaXNlcyB0aGF0IGlzDQp1bmRlcnNl
cnZlZCBieSB2ZW5kb3JzLsKgIFRoZXJlIGlzIG5vIGJlbmVmaXQgaW4gcmVx
dWlyaW5nIGNvbXBsZXggZGVwbG95bWVudHMNCndoZXJlIGF1dG9tYXRpb24g
Y2FuIHRha2UgaXRzIHBsYWNlLsKgIERlcGxveW1lbnQgaXMgYWxtb3N0IGFs
d2F5cyB0aGUgYmlnZ2VzdA0KY29zdCBvZiBlbnRlcnByaXNlIHN5c3RlbXMg
ZHdhcmZpbmcgdGhlIGNvc3Qgb2YgdGhlIHN5c3RlbXMgdGhlbXNlbHZlcy48
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0IHN0eWxl
PSdtYXJnaW4tbGVmdDouMjVpbic+PG86cD4mbmJzcDs8L286cD48L3A+DQoN
CjxwIGNsYXNzPU1zb1BsYWluVGV4dD7igJxJIHRoaW5rIHRoaXMgZGVwZW5k
cyBncmVhdGx5IG9uIHdoYXQgZXhwZWN0YXRpb25zIC8NCmNvbnRyYWN0dWFs
IGd1YXJhbnRlZXMgdGhlIGVudGVycHJpc2UgaGFzLiBJdOKAmXMgdW5jbGVh
ciB0byBtZSB3aGF0IGd1YXJhbnRlZXMNCmNhbiBiZSBtYWRlIGFib3V0IGEg
UDJQU0lQIG5ldHdvcmsgd2lsbCBiZSBhYmxlIHRvIG1ha2UsIGFuZCBpdHMg
dW5jbGVhciB3aGF0DQpraW5kIG9mIGluZnJhc3RydWN0dXJlIHdvdWxkIGJl
IGluc3RhbGxlZCBieS9mb3Igc29tZW9uZSB3aWxsaW5nIHRvIG1ha2UNCmd1
YXJhbnRlZXMu4oCdPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNv
UGxhaW5UZXh0IHN0eWxlPSdtYXJnaW4tbGVmdDouNWluO3RleHQtaW5kZW50
Oi0uMjVpbjttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSc+PCFbaWYgIXN1cHBv
cnRMaXN0c10+PHNwYW4NCnN0eWxlPSdtc28tbGlzdDpJZ25vcmUnPi08c3Bh
biBzdHlsZT0nZm9udDo3LjBwdCAiVGltZXMgTmV3IFJvbWFuIic+Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7DQo8L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT5UaGF0IGlzIHdoeSDigJhl
eHBlY3RhdGlvbnMvY29udHJhY3R1YWwgZ3VhcmFudGVlc+KAmSBuZWVkDQp0
byBiZSBidWlsdCBpbnRvIHRoZSBhdXRvbWF0aW9uIHRoYXQgZXhpc3RzIGlu
IHRoZSBQMlAgb3ZlcmxheS7CoA0KU2VsZi1jYWxjdWxhdGlvbiBvZiBzdWNo
IHBlcmZvcm1hbmNlIG1ldHJpY3MgaXMgYWxyZWFkeSB0aGVyZSBpbiBhbGwg
ZW50ZXJwcmlzZQ0KZGV2aWNlcywgdGhlIGRpZmZlcmVuY2UgYmVpbmcgdGhh
dCB3aGlsZSBXTUkvU05NUCBkYXRhIGlzIG1lcmVseSBjb2xsZWN0ZWQgYQ0K
UDJQU0lQIG5ldHdvcmsgY2FuIGFjdCBhdXRvbWF0aWNhbGx5IGJhc2VkIG9u
IHRoZSBtZXRyaWNzIHdpdGhpbiB0aGVpciBvd24gbm9kZXMsDQp0aGVyZSBp
cyBhIGNvbGxlY3RpdmUg4oCYYWhh4oCZIHRoYXQgZm9yY2VzIGJlaGF2aW9y
IGNoYW5nZSBiYcHpVSTW7uHqYHA7bCCfxz/Skuiv9qSwFtitMoA/3gMn8
yab/AGWls8lxqTBbeE5HP+s/z6V4051nJ8j2ervov+AYty6GrpuqQ6lGxQFJ
E++hPT/EVdrjtEuvN8S+ZEuxJjISPbkj+Qrsa7MDiHXpcz3Tt6lwlzIyNa0h
r7E8GPNAwy5xvHb8axbu31G6jSO6W5ZYRwPKbH1JAwTXY0VFfAQqyck7X37M
UqaZx2k6cf7QheCQMUcFipyFAPOfTjj8a7GiitcLhY4eLinuOMeVH//Z

------_=_NextPart_001_01C77619.9FFAEC5B--


--===============0721435076==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0721435076==--




XNlZCBvbiBzdHJpY3QNCmNvbnRyYWN0cywgYWthIHJ1bGVz
LsKgIEFuIFNMQSBpcyBlYXNpZXIgdG8gbWFpbnRhaW4gaWYgdGhlIG9iamVj
dHMgY2FuIHJlYWN0DQphY2NvcmRpbmdseSwgZm9yIGV4YW1wbGUgYSBub2Rl
IHdpdGggZGVncmFkaW5nIHNlcnZpY2UgY2FuIG5vdGlmeSB0aGF0IGl0IGlz
IG9uDQp0aGUgZGVjbGluZSBmb3JjaW5nIG90aGVycyB0byB0YWtlIG92ZXIu
wqAgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dCBz
dHlsZT0nbWFyZ2luLWxlZnQ6LjI1aW4nPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+VGhlcmUgaXMgYW4gb2xkIHRy
YWZmaWMgZW5naW5lZXJpbmcgYXhpb20gYWJvdXQgc2VydmljZSBndWFyYW50
ZWVzOg0KaXQgY2FuIGJlIGFjaGlldmVkIHRocm91Z2ggdHdvIHdheXM6IG92
ZXIgZW5naW5lZXJpbmcgb3IgwqBhdXRvbWF0aW9uLsKgIFAyUFNJUCBhbGxv
d3MNCmZvciBhdXRvbWF0aW9uLjxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFz
cz1Nc29QbGFpblRleHQ+PG86cD4mbmJzcDs8L286cD48L3A+DQoNCjxwIGNs
YXNzPU1zb1BsYWluVGV4dD7CoERhdmlkIE9yYW4gd3JvdGU6PG86cD48L286
cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PuKAnEknbSBub3Qg
c2F5aW5nIHRoaXMgY2FuJ3QgYmUgbWFkZSB0byB3b3JrLCBvbmx5IHRoYXQg
aXQNCmlzbid0IGltbWVkaWF0ZWx5IG9idmlvdXMgdGhhdCBpdCBoYXMgYWR2
YW50YWdlcyBvdmVyIGEgY2xhc3NpYyBhcHBsaWNhdGlvbi9zZXJ2ZXINCmFw
cHJvYWNoLuKAnTxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFp
blRleHQ+PG86cD4mbmJzcDs8L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD5UaGUgaW1tZWRpYXRlbHkgb2J2aW91cyBhZHZhbnRhZ2UgdG8g
bWUgaXMgc3RhbmRhcmRpemVkDQpydWdnZWRpemVkIGF1dG9tYXRpb24gdGhh
dCBoYXMgZWNvbm9taWVzIG9mIHNjYWxlIGFuZCBvcGVyYXRlcyBvdmVyIG11
bHRpcGxlDQpkb21haW5zLCBlbGltaW5hdGluZyB0aGUgbmVlZCBmb3Igb3Zl
ci1lbmdpbmVlcmluZyzCoCBkZXRhaWxlZCBmdXNzeQ0KcHJvdmlzaW9uaW5n
LMKgIGFuZCBhbiBhcm15IG9mIHBlb3BsZSBkb2luZyBiYXNpYyBtb25pdG9y
aW5nIGFuZCBjYXJlLWFuZC1mZWVkaW5nLsKgDQpBdXRvbWF0aW9uIGlzIHRo
ZSBrZXksIGEgZHluYW1pYyBzdGF0aXN0aWNhbCBuZXR3b3JrIHZzLiBvbmUg
dGhhdCBpcyBmaXhlZCBhbmQNCmFzc3VtZWQgZGV0ZXJtaW5pc3RpYyB3aWxs
IGFsd2F5cyB3aW4gb3V0IG92ZXIgdGltZSBnaXZlbiBhIGZyYWN0YWwgb3Bl
cmF0aW5nDQplbnZpcm9ubWVudC7CoMKgIFRoaXMgaXMgYmVpbmcgZG9uZSBp
biBmaXRzIGFuZCBzdGFydHMgaW4gdGhlIGVudGVycHJpc2UgZGF0YQ0KY2Vu
dGVyLsKgwqAgUDJQU0lQIG1ha2VzIGl0IG11Y2ggbW9yZSBjb21wcmVoZW5z
aXZlLsKgIMKgUGVvcGxlIHdhbnQgdGhlIHdvcmxkIHRvDQpiZSBwcmVkaWN0
YWJsZSBhbmQgZGV0ZXJtaW5pc3RpYyzCoCBhbmQgQy9TIGJhc2VkIHN5c3Rl
bXMgcmVmbGVjdCB0aGF0LiBUaGF0IGlzDQp0aGUgYmlnZ2VzdCBwcm9ibGVt
IFAyUCBmYWNlcyBiZWNhdXNlIGl0IGZsaWVzIGluIHRoZSBmYWNlIG9mIHRy
YWRpdGlvbi4gwqDCoDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29Q
bGFpblRleHQ+PG86cD4mbmJzcDs8L286cD48L3A+DQoNCjxwIGNsYXNzPU1z
b1BsYWluVGV4dD5SZWdhcmRzPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNz
PU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCg0KPHAgY2xh
c3M9TXNvUGxhaW5UZXh0Pk1pY2hhZWwgU2xhdml0Y2g8bzpwPjwvbzpwPjwv
cD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4mbmJzcDs8L286
cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD7CoDxvOnA+PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+wqA8bzpwPjwvbzpwPjwv
cD4NCg0KPHRhYmxlIGNsYXNzPU1zb05vcm1hbFRhYmxlIGJvcmRlcj0xIGNl
bGxzcGFjaW5nPTAgY2VsbHBhZGRpbmc9MCB3aWR0aD0iMTAwJSINCiBzdHls
ZT0nd2lkdGg6MTAwLjAlO2JvcmRlci1jb2xsYXBzZTpjb2xsYXBzZTtib3Jk
ZXI6bm9uZSc+DQogPHRyPg0KICA8dGQgd2lkdGg9NjM4IGNvbHNwYW49NCB2
YWxpZ249dG9wIHN0eWxlPSd3aWR0aDo2LjY1aW47Ym9yZGVyOm5vbmU7DQog
IGJvcmRlci10b3A6c29saWQgd2luZG93dGV4dCAxLjBwdDtiYWNrZ3JvdW5k
OndoaXRlO3BhZGRpbmc6MGluIDUuNHB0IDBpbiA1LjRwdCc+DQogIDxwIGNs
YXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCiAgPC90ZD4N
CiA8L3RyPg0KIDx0cj4NCiAgPHRkIHdpZHRoPTI4NiB2YWxpZ249dG9wIHN0
eWxlPSd3aWR0aDoyMTQuNTVwdDtib3JkZXI6bm9uZTtiYWNrZ3JvdW5kOndo
aXRlOw0KICBwYWRkaW5nOjBpbiAwaW4gMGluIDBpbic+DQogIDxwIGNsYXNz
PU1zb05vcm1hbD48YSBocmVmPSJodHRwOi8vd3d3Lm9iamVjdHdvcmxkLmNv
bS8iDQogIHRpdGxlPSJPYmplY3R3b3JsZCBDb21tdW5pY2F0aW9ucyI+PHNw
YW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQ7dGV4dC1kZWNvcmF0aW9uOg0K
ICBub25lJz48aW1nIGJvcmRlcj0wIHdpZHRoPTIzNyBoZWlnaHQ9NDIgaWQ9
IlBpY3R1cmVfeDAwMjBfMSINCiAgc3JjPSJjaWQ6aW1hZ2UwMDUuanBnQDAx
Qzc3NURELjhGMUQ0MUYwIiBhbHQ9ImNvcnBfMmNvbG91ciI+PC9zcGFuPjwv
YT48bzpwPjwvbzpwPjwvcD4NCiAgPHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KICA8L3RkPg0KICA8dGQgd2lkdGg9MjExIHZh
bGlnbj10b3Agc3R5bGU9J3dpZHRoOjE1OC4wNXB0O2JvcmRlcjpub25lO2Jh
Y2tncm91bmQ6d2hpdGU7DQogIHBhZGRpbmc6MGluIDBpbiAwaW4gMGluJz4N
CiAgPHAgY2xhc3M9TXNvTm9ybWFsPjMwOCBMZWdnZXQgRHIuIDxicj4NCiAg
T3R0YXdhIE9udGFyaW8gPGJyPg0KICBLMksgMVk2IENhbmFkYTxvOnA+PC9v
OnA+PC9wPg0KICA8L3RkPg0KICA8dGQgd2lkdGg9MTM3IHZhbGlnbj10b3Ag
c3R5bGU9J3dpZHRoOjEwMi42cHQ7Ym9yZGVyOm5vbmU7YmFja2dyb3VuZDp3
aGl0ZTsNCiAgcGFkZGluZzowaW4gMGluIDBpbiAwaW4nPg0KICA8cCBjbGFz
cz1Nc29Ob3JtYWwgYWxpZ249cmlnaHQgc3R5bGU9J3RleHQtYWxpZ246cmln
aHQnPjxhDQogIGhyZWY9Imh0dHA6Ly9tYXBzLmdvb2dsZS5jYS9tYXBzP2Y9
cSZhbXA7aGw9ZW4mYW1wO3E9MzA4K0xlZ2dldCtEcml2ZStPdHRhd2ErT250
YXJpbytLMksrMVk2JmFtcDtsYXllcj0mYW1wO3NsbD00NS4zNDEwNjEsLTc1
LjkwNDU0MSZhbXA7c3Nwbj0wLjAwNzExOSwwLjAyMzgzOSZhbXA7aWU9VVRG
OCZhbXA7ej0xOCZhbXA7bGw9NDUuMzQxMDYxLC03NS45MDQ1NDEmYW1wO3Nw
bj0wLjAwMTc4LDAuMDA1OTYmYW1wO3Q9aCZhbXA7b209MSINCiAgdGl0bGU9
IjMwOCBMZWdnZXQgRHJpdmUgT3R0YXdhIE9udGFyaW8gSzJLIDFZNiI+PHNw
YW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQ7DQogIHRleHQtZGVjb3JhdGlv
bjpub25lJz48aW1nIGJvcmRlcj0wIHdpZHRoPTI5IGhlaWdodD0yOSBpZD0i
UGljdHVyZV94MDAyMF82Ig0KICBzcmM9ImNpZDppbWFnZTAwMy5wbmdAMDFD
Nzc1RDkuNzNDNTZEQTAiPjwvc3Bhbj48L2E+PG86cD48L286cD48L3A+DQog
IDwvdGQ+DQogIDx0ZCBzdHlsZT0nYm9yZGVyOm5vbmU7cGFkZGluZzowaW4g
MGluIDBpbiAwaW4nIHdpZHRoPTU+PHAgY2xhc3M9J01zb05vcm1hbCc+Jm5i
c3A7PC90ZD4NCiA8L3RyPg0KIDx0cj4NCiAgPHRkIHdpZHRoPTI4NiB2YWxp
Z249dG9wIHN0eWxlPSd3aWR0aDoyMTQuNTVwdDtib3JkZXI6bm9uZTtiYWNr
Z3JvdW5kOndoaXRlOw0KICBwYWRkaW5nOjBpbiAwaW4gMGluIDBpbic+DQog
IDx0YWJsZSBjbGFzcz1Nc29Ob3JtYWxUYWJsZSBib3JkZXI9MCBjZWxsc3Bh
Y2luZz0wIGNlbGxwYWRkaW5nPTANCiAgIHN0eWxlPSdib3JkZXItY29sbGFw
c2U6Y29sbGFwc2UnPg0KICAgPHRyPg0KICAgIDx0ZCB3aWR0aD0yNzggdmFs
aWduPXRvcCBzdHlsZT0nd2lkdGg6MjA4LjRwdDtwYWRkaW5nOjBpbiAwaW4g
MGluIDBpbic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPk1pY2hhZWwNCiAg
ICBTbGF2aXRjaCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO8KgwqDCoCA8bzpwPjwvbzpwPjwv
cD4NCiAgICA8L3RkPg0KICAgPC90cj4NCiAgIDx0cj4NCiAgICA8dGQgd2lk
dGg9Mjc4IHZhbGlnbj10b3Agc3R5bGU9J3dpZHRoOjIwOC40cHQ7cGFkZGlu
ZzowaW4gMGluIDBpbiAwaW4nPg0KICAgIDxwIGNsYXNzPU1zb05vcm1hbD5M
ZWFkLCBUZWNobm9sb2d5IEluaXRpYXRpdmVzPG86cD48L286cD48L3A+DQog
ICAgPC90ZD4NCiAgIDwvdHI+DQogICA8dHI+DQogICAgPHRkIHdpZHRoPTI3
OCB2YWxpZ249dG9wIHN0eWxlPSd3aWR0aDoyMDguNHB0O3BhZGRpbmc6MGlu
IDBpbiAwaW4gMGluJz4NCiAgICA8cCBjbGFzcz1Nc29Ob3JtYWw+c2xhdml0
Y2hAb2JqZWN0d29ybGQuY29tPG86cD48L286cD48L3A+DQogICAgPC90ZD4N
CiAgIDwvdHI+DQogIDwvdGFibGU+DQogIDwvdGQ+DQogIDx0ZCB3aWR0aD0y
MTEgdmFsaWduPXRvcCBzdHlsZT0nd2lkdGg6MTU4LjA1cHQ7Ym9yZGVyOm5v
bmU7YmFja2dyb3VuZDp3aGl0ZTsNCiAgcGFkZGluZzowaW4gMGluIDBpbiAw
aW4nPg0KICA8dGFibGUgY2xhc3M9TXNvTm9ybWFsVGFibGUgYm9yZGVyPTAg
Y2VsbHNwYWNpbmc9MCBjZWxscGFkZGluZz0wIHdpZHRoPTIwNA0KICAgc3R5
bGU9J3dpZHRoOjE1Mi44NXB0O2JvcmRlci1jb2xsYXBzZTpjb2xsYXBzZSc+
DQogICA8dHI+DQogICAgPHRkIHdpZHRoPTQyIHZhbGlnbj10b3Agc3R5bGU9
J3dpZHRoOjMxLjI1cHQ7cGFkZGluZzowaW4gMGluIDBpbiAwaW4nPg0KICAg
IDxwIGNsYXNzPU1zb05vcm1hbD5QU1ROOsKgIDxvOnA+PC9vOnA+PC9wPg0K
ICAgIDwvdGQ+DQogICAgPHRkIHdpZHRoPTEzMSB2YWxpZ249dG9wIHN0eWxl
PSd3aWR0aDo5OC4wNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gMGluJz4NCiAg
ICA8cCBjbGFzcz1Nc29Ob3JtYWw+KzEuODg4LjM5OC45Njk4PG86cD48L286
cD48L3A+DQogICAgPC90ZD4NCiAgICA8dGQgd2lkdGg9MzEgdmFsaWduPXRv
cCBzdHlsZT0nd2lkdGg6MjMuNTVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDBp
bic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPngyMjU8bzpwPjwvbzpwPjwv
cD4NCiAgICA8L3RkPg0KICAgPC90cj4NCiAgIDx0cj4NCiAgICA8dGQgd2lk
dGg9NDIgdmFsaWduPXRvcCBzdHlsZT0nd2lkdGg6MzEuMjVwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDBpbic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPkZh
eDo8bzpwPjwvbzpwPjwvcD4NCiAgICA8L3RkPg0KICAgIDx0ZCB3aWR0aD0x
MzEgdmFsaWduPXRvcCBzdHlsZT0nd2lkdGg6OTguMDVwdDtwYWRkaW5nOjBp
biAwaW4gMGluIDBpbic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPisxLjYx
My41OTkuNzQ1NzxvOnA+PC9vOnA+PC9wPg0KICAgIDwvdGQ+DQogICAgPHRk
IHdpZHRoPTMxIHZhbGlnbj10b3Agc3R5bGU9J3dpZHRoOjIzLjU1cHQ7cGFk
ZGluZzowaW4gMGluIDBpbiAwaW4nPg0KICAgIDxwIGNsYXNzPU1zb05vcm1h
bD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCiAgICA8L3RkPg0KICAgPC90cj4N
CiAgIDx0cj4NCiAgICA8dGQgd2lkdGg9NDIgdmFsaWduPXRvcCBzdHlsZT0n
d2lkdGg6MzEuMjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDBpbic+DQogICAg
PHAgY2xhc3M9TXNvTm9ybWFsPlNreXBlOsKgwqDCoMKgwqDCoCA8bzpwPjwv
bzpwPjwvcD4NCiAgICA8L3RkPg0KICAgIDx0ZCB3aWR0aD0xMzEgdmFsaWdu
PXRvcCBzdHlsZT0nd2lkdGg6OTguMDVwdDtwYWRkaW5nOjBpbiAwaW4gMGlu
IDBpbic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPsKgPGEgaHJlZj0iU2t5
cGU6T2JqZWN0d29ybGQiPk9iamVjdHdvcmxkPC9hPsKgwqAgPG86cD48L286
cD48L3A+DQogICAgPC90ZD4NCiAgICA8dGQgd2lkdGg9MzEgdmFsaWduPXRv
cCBzdHlsZT0nd2lkdGg6MjMuNTVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDBp
bic+DQogICAgPHAgY2xhc3M9TXNvTm9ybWFsPngyMjU8bzpwPjwvbzpwPjwv
cD4NCiAgICA8L3RkPg0KICAgPC90cj4NCiAgPC90YWJsZT4NCiAgPC90ZD4N
CiAgPHRkIHdpZHRoPTEzNyB2YWxpZ249dG9wIHN0eWxlPSd3aWR0aDoxMDIu
NnB0O2JvcmRlcjpub25lO2JhY2tncm91bmQ6d2hpdGU7DQogIHBhZGRpbmc6
MGluIDBpbiAwaW4gMGluJz4NCiAgPHAgY2xhc3M9TXNvTm9ybWFsIGFsaWdu
PXJpZ2h0IHN0eWxlPSd0ZXh0LWFsaWduOnJpZ2h0Jz48YQ0KICBocmVmPSJz
a3lwZTpPYmplY3R3b3JsZCIgdGl0bGU9T2JqZWN0d29ybGQ+PHNwYW4gc3R5
bGU9J2NvbG9yOndpbmRvd3RleHQ7DQogIHRleHQtZGVjb3JhdGlvbjpub25l
Jz48aW1nIGJvcmRlcj0wIHdpZHRoPTI2IGhlaWdodD0yNiBpZD0iUGljdHVy
ZV94MDAyMF8zIg0KICBzcmM9ImNpZDppbWFnZTAwNC5wbmdAMDFDNzc1RDku
NzNDNTZEQTAiPjwvc3Bhbj48L2E+PG86cD48L286cD48L3A+DQogIDwvdGQ+
DQogIDx0ZCBzdHlsZT0nYm9yZGVyOm5vbmU7cGFkZGluZzowaW4gMGluIDBp
biAwaW4nIHdpZHRoPTU+PHAgY2xhc3M9J01zb05vcm1hbCc+Jm5ic3A7PC90
ZD4NCiA8L3RyPg0KPC90YWJsZT4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+
PG86cD4mbmJzcDs8L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4
dD4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IFBhdWwg
S3l6aXZhdCBbbWFpbHRvOnBreXppdmF0QGNpc2NvLmNvbV0gPGJyPg0KU2Vu
dDogVHVlc2RheSwgQXByaWwgMDMsIDIwMDcgODo1NyBBTTxicj4NClRvOiBN
aWNoYWVsIFNsYXZpdGNoPGJyPg0KQ2M6IEhlbnJ5IFNpbm5yZWljaDsgUDJQ
U0lQIE1haWxpbmcgTGlzdDsgTWljaGFlbCBIYW1tZXIgKG1oYW1tZXIpOyBE
YXZpZCBSDQpPcmFuOyBwMnByZ0BpZXRmLm9yZzsgc2lwcGluZ0BpZXRmLm9y
Zzsgemh1eGlhbjxicj4NClN1YmplY3Q6IFJlOiBbUDJQcmddIFJFOiBbU2lw
cGluZ10gU2ltcGxlIFNJUCB1c2FnZSBzY2VuYXJpbzxvOnA+PC9vOnA+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4mbmJzcDs8L286cD48
L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+TWljaGFlbCBTbGF2
aXRjaCB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxh
aW5UZXh0PiZndDsgU29ycnkgZm9yIGJlaW5nIGxhdGUgaW50byB0aGlzIGRp
c2N1c3Npb24sIGJ1dA0KY2xpZW50LXNlcnZlciBiYXNlZCBWTSA8bzpwPjwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgaXNuJ3Qg
dHJ1bHkgY2xpZW50LXNlcnZlciBhbnltb3JlIGluIGFueXRoaW5nIGJ1dA0K
dGhlIHNtYWxsZXN0IG9yIG1vc3QgPG86cD48L286cD48L3A+DQoNCjxwIGNs
YXNzPU1zb1BsYWluVGV4dD4mZ3Q7IG1vbm9saXRoaWMgb2YgZW50ZXJwcmlz
ZSBuZXR3b3JrcywgaW4gZmFjdCB0aGUNCnJlYWxpdHkgaXMgdGhhdCBtb3N0
IGlmIDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+
Jmd0OyBub3QgYWxsIGVudGVycHJpc2UgbmV0d29ya3MgY29udGFpbiBqdXN0
IHBlZXJzIGFuZA0Kc3VwZXJwZWVycyB3aXRoIHRoZSA8bzpwPjwvbzpwPjwv
cD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgZGlmZmVyZW5jZSBi
ZWluZyBwYXJ0aWFsbHkgYSBtYXJrZXRpbmcgZGVjaXNpb24gYnkNCnRoZSB2
ZW5kb3JzLCBhcyB5b3UgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1z
b1BsYWluVGV4dD4mZ3Q7IGNhbiBjaGFyZ2UgbXVjaCBtb3JlIGZvciB0aGUg
c2VydmVycywgYW5kIGEgcG9saWN5DQpkZWNpc2lvbiBtYWRlIGVpdGhlciA8
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
YXV0b21hdGljYWxseSBieSBhIHNvZnR3YXJlIGRlcGxveW1lbnQgc3lzdGVt
IG9yIGJ5DQpJVCBzdGFmZiB3aGljaCB3YW50cyA8bzpwPjwvbzpwPjwvcD4N
Cg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgdG8gcGxhY2Ugc3VwZXJu
b2RlcyB3aXRoIGRhdGEgc2lua3Mgb24gYXBwcm9wcmlhdGUNCmVxdWlwbWVu
dC48bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0Pjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+
SSdtIHNvcnJ5LCBidXQgSSBkb24ndCB1bmRlcnN0YW5kIHRoZSBwb2ludCB5
b3UgYXJlDQp0cnlpbmcgdG8gbWFrZSA8bzpwPjwvbzpwPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PmFib3ZlLiBZb3UgYXJlIHRyeWluZyB0byBk
cmF3IHNvbWUgc29ydCBvZiBkaXN0aW5jdGlvbiwNCmJ1dCBJIGRvbid0IGdl
dCA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0Pml0
LiBDYW4geW91IHRyeSBhZ2Fpbi48bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xh
c3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KDQo8cCBj
bGFzcz1Nc29QbGFpblRleHQ+wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC
oMKgIFRoYW5rcyw8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxh
aW5UZXh0PsKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBQYXVsPG86
cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
SW4gYSA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0
PiZndDsgaGlnaGx5IGRpc3RyaWJ1dGVkIGVudmlyb25tZW50IHRoZXJlIGFy
ZSBwb3RlbnRpYWxseQ0KaHVuZHJlZHMgb2YgPG86cD48L286cD48L3A+DQoN
CjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IHBvc3NpYmxlIGRhdGEgc2lu
a3MgZm9yIGEgZ2l2ZW4gYXBwbGljYXRpb24sIHdpdGgNCnRoZSBzaW5rIGJh
c2VkIG9uIDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jmd0OyBzdWJuZXQgb3IgZ2VvZ3JhcGhpYyBsb2NhdGlvbiBvciBiYWxh
bmNlZCBsb2FkLCB0aGlzDQpjYW4gY2hhbmdlIHJhcGlkbHkgPG86cD48L286
cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IG92ZXIgdGlt
ZSBhbmQgZG9lcy48bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxh
aW5UZXh0PiZndDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD4mZ3Q7IEluIHRoZSBjYXNlIG9mIHRoZSBNaWNyb3NvZnQgZW52
aXJvbm1lbnQgc3VjaCBwb2xpY3kNCmlzIGFkbWluaXN0ZXJlZCBhbmQgPG86
cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IHB1
Ymxpc2hlZCBiZXR3ZWVuIHN1cGVybm9kZXMsIGllIHNlcnZlcnMsIGJ5IEFj
dGl2ZQ0KRGlyZWN0b3J5LsKgIEl0IGlzIDxvOnA+PC9vOnA+PC9wPg0KDQo8
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBhZHZlcnRpc2VkIHRvIG1lcmUg
cGVlcnMgdGhyb3VnaCBETlMuwqAgVGhlcmUgd2FzDQptdWNoIGRpc2N1c3Np
b24gYSB3aGlsZSA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxh
aW5UZXh0PiZndDsgYWdvIGFib3V0IGJ1aWxkaW5nIHNlcnZpY2UgZGlzY292
ZXJ5IGVudmlyb25tZW50DQp1c2luZyBETlMgaW5zdGVhZCBvZiBhIDxvOnA+
PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBQMlAg
REhULsKgIEl0IGNhbiBiZSBhcmd1ZWQgdGhhdCBhIGNhc2Ugc3R1ZHkgb2Yg
YQ0KUDJQIGV4YW1wbGUgZG9uZSB1c2luZyA8bzpwPjwvbzpwPjwvcD4NCg0K
PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgRE5TIGlzIGFueSBsYXJnZSBX
aW5kb3dzIFNlcnZlciAyMDAzIGJhc2VkIE1pY3Jvc29mdA0KbmV0d29yayB3
aXRoIG1hbnkgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IHNlcnZlcnMgYW5kIG1hbnkgbW9yZSBjbGllbnRzIHRoYXQg
YWxzbyBydW4NCmFwcGxpY2F0aW9ucyB0aGVtc2VsdmVzIGFuZCA8bzpwPjwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgYXJlIG5v
dCBqdXN0IGR1bWIgdGVybWluYWxzLiBUaGlzIGlzIGFsbW9zdA0KY2VydGFp
bmx5IGFsd2F5cyB0aGUgY2FzZSBpbiA8bzpwPjwvbzpwPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgYWxsIGVudGVycHJpc2VzLiBUaGUg
YmlnIGRpZmZlcmVuY2UgYmV0d2VlbiBDL1MgU0lQDQphbmQgUDJQU0lQIGlz
IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0
OyBhdXRvbWF0aW9uLiBXaGF0IGlzIHRydWUgaXMgdGhhdCB0aGUgc3F1YXJl
IHBlZyBpbg0Kcm91bmQgaG9sZSBvZiA8bzpwPjwvbzpwPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgb3ZlcmxvYWRpbmcgRE5TIG1ha2Vz
IGRlcGxveW1lbnRzIGNsdW1zeSBhbmQgYnJpdHRsZQ0Kd2l0aGluIHRoZSA8
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
ZW50ZXJwcmlzZSBkb21haW4gYW5kIGNvbXBsZXRlbHkgdW5tYW5hZ2VhYmxl
IGFuZA0KdW5wdWJsaXNoYWJsZSBvdXRzaWRlIDxvOnA+PC9vOnA+PC9wPg0K
DQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyB0aGUgZmlyZXdhbGwgd2hp
Y2ggaXMgd2h5IHRoZSBidWNrIHN0b3BzIHRoZXJlIGluDQpjdXJyZW50IGVu
dGVycHJpc2UgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IG5ldHdvcmtpbmcgcHJvZHVjdHMuPG86cD48L286cD48L3A+
DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBUaGUgZGlmZmVyZW5j
ZSBiZXR3ZWVuIEMvUyBhbmQgUDJQIGlzIGxhcmdlbHkgcG9saWN5DQphbmQg
c2VtYW50aWNzIHdpdGggPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1z
b1BsYWluVGV4dD4mZ3Q7IHRoZSBiaWdnZXN0IGRpZmZlcmVuY2UgYmVpbmcg
dGhhdCB0aGUgZGVjaXNpb25zIGFuZA0KcnVsZXMgYXJlIGhpZ2hseSA8bzpw
PjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgZGlz
dHJpYnV0ZWQuwqAgQXBhcnQgZnJvbSB0aGF0IHRoZXkgYXJlIG5vdCBqdXN0
DQpmcmllbmRzLCB0aGV5IGFyZSA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xh
c3M9TXNvUGxhaW5UZXh0PiZndDsgZnJhdGVybmFsIHR3aW5zLjxvOnA+PC9v
OnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgUmVnYXJk
czxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0
OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgTWljaGFlbCBTbGF2aXRjaDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFz
cz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xh
c3M9TXNvUGxhaW5UZXh0PiZndDvCoCA8bzpwPjwvbzpwPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86cD48L286cD48L3A+DQoNCjxw
IGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBjb3JwXzJjb2xvdXIgPG86cD48
L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7ICZsdDto
dHRwczovL2ZpcmV3YWxsLm9iamVjdHdvcmxkLmNvbS9leGNod2ViL2Jpbi9y
ZWRpci5hc3A/VVJMPWh0dHA6Ly93d3cub2JqZWN0d29ybGQuY29tLyZndDs8
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
PG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7
wqAgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4m
Z3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+
Jmd0OyDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDxvOnA+PC9vOnA+PC9wPg0K
DQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4N
Cg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgMzA4IExlZ2dldCBEci48
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
T3R0YXdhIE9udGFyaW88bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNv
UGxhaW5UZXh0PiZndDsgSzJLIDFZNiBDYW5hZGE8bzpwPjwvbzpwPjwvcD4N
Cg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86cD48L286cD48L3A+
DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IMKgwqDCoMKgwqDCoMKg
wqDCoMKgwqAgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFp
blRleHQ+Jmd0Ow0KJmx0O2h0dHBzOi8vZmlyZXdhbGwub2JqZWN0d29ybGQu
Y29tL2V4Y2h3ZWIvYmluL3JlZGlyLmFzcD9VUkw9aHR0cDovL21hcHMuZ29v
Z2xlLmNhL21hcHM/Zj1xJTI2aGw9ZW4lMjZxPTMwOCUyQkxlZ2dldCUyQkRy
aXZlJTJCT3R0YXdhJTJCT250YXJpbyUyQksySyUyQjFZNiUyNmxheWVyPSUy
NnNsbD00NS4zNDEwNjEsLTc1LjkwNDU0MSUyNnNzcG49MC4wMDcxMTksMC4w
MjM4MzklMjZpZT1VVEY4JTI2ej0xOCUyNmxsPTQ1LjM0MTA2MSwtNzUuOTA0
NTQxJTI2c3BuPTAuMDAxNzgsMC4wMDU5NiUyNnQ9aCUyNm9tPTEmZ3Q7PG86
cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxv
OnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyDC
oMKgwqDCoMKgwqDCoMKgwqDCoMKgIDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBj
bGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvUGxhaW5UZXh0PiZndDvCoCA8bzpwPjwvbzpwPjwvcD4NCg0K
PHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86cD48L286cD48L3A+DQoN
CjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IE1pY2hhZWwgU2xhdml0Y2jC
oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPG86cD48L286cD48L3A+DQoNCjxw
IGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8
cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyBMZWFkLCBUZWNobm9sb2d5IElu
aXRpYXRpdmVzPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFp
blRleHQ+Jmd0OyBzbGF2aXRjaEBvYmplY3R3b3JsZC5jb20NCiZsdDttYWls
dG86c2xhdml0Y2hAb2JqZWN0d29ybGQuY29tJmd0OzxvOnA+PC9vOnA+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwv
cD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgwqDCoMKgwqDCoMKg
wqDCoMKgwqDCoCA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxh
aW5UZXh0PiZndDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1Bs
YWluVGV4dD4mZ3Q7IFBTVE46IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFz
cz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xh
c3M9TXNvUGxhaW5UZXh0PiZndDsgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA8
bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsg
PG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7
ICsxLjg4OC4zOTguOTY5ODxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1N
c29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9
TXNvUGxhaW5UZXh0PiZndDsgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA8bzpw
PjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86
cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IHgy
MjU8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4m
Z3Q7IEZheDo8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5U
ZXh0PiZndDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPG86cD48L286cD48
L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyArMS42MTMuNTk5
Ljc0NTc8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0
PiZndDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4
dD4mZ3Q7IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPG86cD48L286cD48L3A+
DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0O8KgIDxvOnA+PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpw
PjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgU2t5cGU6wqDC
oMKgwqDCoCA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5U
ZXh0PiZndDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWlu
VGV4dD4mZ3Q7IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPG86cD48L286cD48
L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0O8KgwqAgT2JqZWN0
d29ybGQgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4
dD4mZ3Q7DQombHQ7aHR0cHM6Ly9maXJld2FsbC5vYmplY3R3b3JsZC5jb20v
ZXhjaGFuZ2Uvc2xhdml0Y2gvU2VudCUyMEl0ZW1zL05vcnRlbCwlMjBNU0ZU
JTIwY2hhc2UlMjBjYXJyaWVycyUyMHdpdGglMjBuZXclMjBob3N0ZWQlMjBv
ZmZlcmluZyUyMGZvciUyMFNNRSUyMGFuZCUyME1NRS5FTUwvJmd0O8KgwqAN
CjxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0
OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZn
dDsgPG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4m
Z3Q7IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgPG86cD48L286cD48L3A+DQoN
CjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0K
DQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyB4MjI1PG86cD48L286cD48
L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9vOnA+
PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyDCoMKgwqDCoMKg
wqDCoMKgwqDCoMKgIDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29Q
bGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNv
UGxhaW5UZXh0PiZndDsNCiZsdDtodHRwczovL2ZpcmV3YWxsLm9iamVjdHdv
cmxkLmNvbS9leGNoYW5nZS9zbGF2aXRjaC9TZW50JTIwSXRlbXMvTm9ydGVs
LCUyME1TRlQlMjBjaGFzZSUyMGNhcnJpZXJzJTIwd2l0aCUyMG5ldyUyMGhv
c3RlZCUyMG9mZmVyaW5nJTIwZm9yJTIwU01FJTIwYW5kJTIwTU1FLkVNTC8m
Z3Q7PG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4m
Z3Q7IDxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+
Jmd0OyDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIDxvOnA+PC9vOnA+PC9wPg0K
DQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwvbzpwPjwvcD4N
Cg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDvCoCA8bzpwPjwvbzpwPjwv
cD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PiZndDsgPG86cD48L286cD48
L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7wqAgPG86cD48L286
cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4mZ3Q7IDxvOnA+PC9v
OnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+Jmd0OyA8bzpwPjwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+PG86cD4mbmJz
cDs8L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD4tLSA8bzpw
PjwvbzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PkJFR0lOLUFO
VElTUEFNLVZPVElORy1MSU5LUzxvOnA+PC9vOnA+PC9wPg0KDQo8cCBjbGFz
cz1Nc29QbGFpblRleHQ+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPG86cD48L286cD48L3A+DQoNCjxw
IGNsYXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCg0K
PHAgY2xhc3M9TXNvUGxhaW5UZXh0PlRlYWNoIENhbkl0IGlmIHRoaXMgbWFp
bCAoSUQgNjU3ODA1KSBpcyBzcGFtOjxvOnA+PC9vOnA+PC9wPg0KDQo8cCBj
bGFzcz1Nc29QbGFpblRleHQ+U3BhbTrCoMKgwqDCoMKgwqDCoA0KaHR0cDov
L2Nhbml0cHJvLWludC5vYmplY3R3b3JsZC5jb20vY2FuaXQvYi5waHA/aT02
NTc4MDUmYW1wO209MmViMWZkZWU1NWI3JmFtcDtjPXM8bzpwPjwvbzpwPjwv
cD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0Pk5vdCBzcGFtOsKgwqDCoA0K
aHR0cDovL2Nhbml0cHJvLWludC5vYmplY3R3b3JsZC5jb20vY2FuaXQvYi5w
aHA/aT02NTc4MDUmYW1wO209MmViMWZkZWU1NWI3JmFtcDtjPW48bzpwPjwv
bzpwPjwvcD4NCg0KPHAgY2xhc3M9TXNvUGxhaW5UZXh0PkZvcmdldCB2b3Rl
OiBodHRwOi8vY2FuaXRwcm8taW50Lm9iamVjdHdvcmxkLmNvbS9jYW5pdC9i
LnBocD9pPTY1NzgwNSZhbXA7bT0yZWIxZmRlZTU1YjcmYW1wO2M9ZjxvOnA+
PC9vOnA+PC9wPg0KDQo8cCBjbGFzcz1Nc29QbGFpblRleHQ+LS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
PG86cD48L286cD48L3A+DQoNCjxwIGNsYXNzPU1zb1BsYWluVGV4dD5FTkQt
QU5USVNQQU0tVk9USU5HLUxJTktTPG86cD48L286cD48L3A+DQoNCjxwIGNs
YXNzPU1zb1BsYWluVGV4dD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCg0KPC9k
aXY+DQoNCjxociB3aWR0aD0iMTAwJSI+DQo8Zm9udCBzaXplPSItMiI+PHA+
DQpUaGlzIHRyYW5zbWlzc2lvbiAoaW5jbHVkaW5nIGFueSBhdHRhY2htZW50
cykgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIGluZm9ybWF0aW9uLCBwcml2
aWxlZ2VkIG1hdGVyaWFsIChpbmNsdWRpbmcgbWF0ZXJpYWwgcHJvdGVjdGVk
IGJ5IHRoZSBzb2xpY2l0b3ItY2xpZW50IG9yIG90aGVyIGFwcGxpY2FibGUg
cHJpdmlsZWdlcyksIG9yIGNvbnN0aXR1dGUgbm9uLXB1YmxpYyBpbmZvcm1h
dGlvbi4gQW55IHVzZSBvZiB0aGlzIGluZm9ybWF0aW9uIGJ5IGFueW9uZSBv
dGhlciB0aGFuIHRoZSBpbnRlbmRlZCByZWNpcGllbnQgaXMgcHJvaGliaXRl
ZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4g
ZXJyb3IsIHBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2VuZGVy
IGFuZCBkZWxldGUgdGhpcyBpbmZvcm1hdGlvbiBmcm9tIHlvdXIgc3lzdGVt
LiBVc2UsIGRpc3NlbWluYXRpb24sIGRpc3RyaWJ1dGlvbiwgb3IgcmVwcm9k
dWN0aW9uIG9mIHRoaXMgdHJhbnNtaXNzaW9uIGJ5IHVuaW50ZW5kZWQgcmVj
aXBpZW50cyBpcyBub3QgYXV0aG9yaXplZCBhbmQgbWF5IGJlIHVubGF3ZnVs
LjwvcD4NCg0KPHA+QW55IHZpZXdzLCBvcGluaW9ucyBhbmQgY29udGVudCBw
cmVzZW50ZWQgaW4gdGhpcyBlLW1haWwgYXJlIHNvbGVseSB0aG9zZSBvZiB0
aGUgYXV0aG9yIGFuZCBtYXkgbm90IHJlcHJlc2VudCB0aG9zZSBvZiBPYmpl
Y3R3b3JsZCBDb21tdW5pY2F0aW9ucyBDb3JwLjwvcD4NCjwvZm9udD4KPC9i
b2R5Pg0KDQo8L2h0bWw+DQo=

------_=_NextPart_002_01C775FF.19CEFDE7--

------_=_NextPart_001_01C775FF.19CEFDE7
Content-Type: image/png;
	name="image003.png"
Content-Transfer-Encoding: base64
Content-ID: <image003.png@01C775D9.73C56DA0>
Content-Description: image003.png
Content-Location: image003.png
Content-Disposition: inline

iVBORw0KGgoAAAANSUhEUgAAAB0AAAAdCAIAAADZ8fBYAAAAAXNSR0IArs4c
6QAABd1JREFUSEt1VklvHEUU7n2ZrT2Og2PHWRwnImLJIpEIIRkOHDgAQgoX
Dkgc4IbIf0DcuXCKhMQv4A8gESlYxCQE4oCUjQSvM97G09PT02ttfDU9scdO
KD3Z1d31vnr1ve+9GlUIobxoUC62IvrXRjq/lt7dSJpBPulZF444b0255444
h13d0FWMF/ripfo8LhfKakC/nW+tdMXscff8uD09atcsNcrZapAtbGY/L2Yn
PfXq5ZGpmvV/6Adxo5z/sNCZW0k/fsWbPVEyVSWmKuUcIaREy5hyqKRYmvhl
Jf7xfvDuSfuTV6sV29S0g4Hvw23F4rtbrbJtvzdT8Rytlwn2jKWYKA9abLMn
KpY+4qpnRjVH59cXu5Tmn1+s1Us2KBmmZQ8XkX5zo3V6rHRuvIQAhOD0GfOG
qmxEYskXo656YkTF9ssd4bnatCce7iTNTvzlpdqICydtF3qAy7n4+oaM9LWX
yrqq7MSsauujzl4ERdyapmDS6LInvnyuO9pUTdxvJQpLv3qjalnWLrRWJPSn
p70HLT7tuUs+m1smf2/xOw26FTEuBGHSIA8YnjuZCIlyqq6OV9TlgK4EAl53
NsRCI2RslzZF4hLKr93pvH2ish2LZshzxhnnnYxtRywmIuciYwPDI05zrKZW
TKUd4yvHenjB99pCliQJ54CWR5G4txpJyqFGvRnSMKcZ431jqqYi3pxJI1wa
JtBGRsVKlzaQM8GwHl7w3cz0+9sZIYT3xaOB2Zsr0bGa3U64n7GU8pRJyygL
M54QRR5fiISIpQ77rZH+uU7ubpA/mnlMOT5hPbzgC4R7zV6e54gXA7hsfi1z
Tb0V8zhnGeUZkYZdH+2Qe1vZZoi5mjPlaZs8bJHlDtnsUTA+WEmlF3yB8PuW
gngxwARw+aNWisjbSZ4QLuPtG6gIUvq4lc+vxdcXo6UOcQxJ3E4MXJLQ/sn6
Bi/44tO9Fu+DYnDJb0wVENfL+nBDhkdkxk/5kza5u55ahnZ50j4+Yo5XzBEH
FfYsAsrhCwSwAVyoQvKLf2OurH0KErE527OCaLxElUzW9LGSVrW1M4ess4fN
ixPOpaNlaL2XU0m0EEA4Xh0UkuQX2C97IsyJqiHd4PegRYRiTdnUBFehM4gB
lvZrEdtQBXMoRyKcrQzEMNDZ7FG9nTCIHkxJivcbxL4ZZbcb8VIgSRzIjkEn
HIIpUg1fIFyYLKHeikLTdF0/P1n5t42vkIDM8m5CdieEKRu9/HEr8VNZUcBB
VhshRQXHuYAXfIHwei0rQFH+En7GU9+fTPwcPCoZZP+c4Xg5B9EK0liU32pA
fl3trvdyrkgv+AKhbgnTNBFov5NommkYV06pW0GMGjUAvV8VxSPI6WQEPQ8+
a0F+c6271SNoQlgPL/gCQUKZprxF5FTTbbSxo97VmR2/l6C9mpoKlJzuN8b9
hHZTFqbiiZ9thOgiAiuxHl7wnbBJqVQCbh9axqsahuG4pQ/Ojn5YbwZhD1lG
k0Q3QC53Ow44RZmshvl6j7QiWaxYg5VYf2W08c5R07QdDLTKfrx9fg3DxKtS
pfrZhfqnY0t+p6Pq+pRne7Ze3C9IYCEDIKK0bEOZGnGwBiux/qPTjm5a5XLZ
dV0EW0hi0NcppVEUBRh++/Y/ze8XK0/Z4Wqt6lkqPiH7UJuuq46BrOhBLsJu
OKNvfzHdOzdVN2ynXq/XajXg2rZT3HUDXJwLhQdo3/fDoBN0OnNr6dy62syd
rl5NtCpTTV0Ql4c1Fk5a6eyEeHPCdFzXcVyAVioVxDt8X+zdb4BGdaM3I+hu
txvHUZZlfphsxyyIElDhGJpXdg+5qudahgkRGdUqoqwhXQAtFHbwfiv0XEQN
aIwwDBF+miZAZ5IH2U0kC7oG/SBMYAERA2EORzoojQO/S2SPQxXkOWgFepqm
RUsd3AJ9hRYDqcYGfUSEue+S3+O32GR3FIEDC+iY4G+x/UDxmgYSihIYvtuH
EV7wO2oYHWg4wIEzFQJ9PsZh3P8A9OAgCrvQHUQAAAAASUVORK5CYII=

------_=_NextPart_001_01C775FF.19CEFDE7
Content-Type: image/png;
	name="image004.png"
Content-Transfer-Encoding: base64
Content-ID: <image004.png@01C775D9.73C56DA0>
Content-Description: image004.png
Content-Location: image004.png
Content-Disposition: inline

iVBORw0KGgoAAAANSUhEUgAAABoAAAAaCAIAAAAmKNuZAAAAAXNSR0IArs4c
6QAAA0lJREFUSEutlVtIFFEYx3dm9uLu0qLrrlpmi0kpmilGJZRQQoTQS/kk
JV0kCaoniQgiCro82UtvPQRSYC9dEay37pRFWGq0G2SKruyue9Hdud/6jyPj
krOrgcuwzJxz5nf+3/f9vzOEqqqWtfuRa4fSSIShbiL99tX09Yn5dxgNePY2
l56vLjr0v5st4gAKpgYOVNz0FVQLSibO/noTvqVYZIKTkkRYUliPrbzYubW2
6HCjvzPPHhoOul5MXujY8oiWYqyUEGVGUNJ4Z14I62+KCpsRI3EuFGXGbJS7
bVNvLuEaru/nwZYNF51Wr8GSFYmTU7IqACTJHKfMiQqDR0Gm02J4lg02+U+1
BXqXy9RKgXx5HVWrYYkKTVooP1H1NXbvye8ucxxGJZXTY8yjCyxOnlM5nrGm
7aR7ZPZhMDnwD1FThzpGmNEVWTwdF6TMnspLokwLCo0XByd7THDwxIeZ2yRh
N/LFSsnsfEEXWBDVWnGtztsOhNNaRJH2eX7q2+yDbKKmDmWCJ1L8HyQb4YC1
UAQt98ZSxWGBjXRWAVXosnphHdyPJR7/i9PczEn6qKoooOwo6cpmyaq4v/yq
ztJ8ozKMlEAouI+yYyY4eFUfJUiSVNn1rsYm/0nYAhctRnaXnjWMNhy7nxEi
uBAE1iNeExx8jzARBUXY+YVDYbOntcF3dDoz1Fx2ztAF1vPxM8v9YYwsHgFI
BHZDvvCf5Mf1aVBO172vL+7QH01ZHsdGE3XoR2Rhih6Kc0FZ4SPsqL6o0BHI
w8IUSmyCq/MeibMhZApZl1X+2Y8TBjGXLp0SoUeyzbwYbIPvGHob/SjIGZK3
ZKhEf6h9hhnOz8Isgv0YuWMIXDrvsMnT8W6voxIehPvhBpKw7SzpxtllJZ25
0u931kylP13ZpTUJfks4PKCrQ6nBMlc9QkZZDDPCwwRhNSVWuLZ9ifWb4/DC
4ETP93g/9oRpcikyxlEHLIuyo8drXpqo04cQNXpbUcUSZ63bVqpz0QPwc6Gj
EsbUl9kpd6E98Dp8o72qL7CuJSdOn0Bvox9Rbt2GSDm0pPjJ7cUd6Bkb5UKP
f47ebfR17iu/bFKKFUPThaOOxucJIEPXCupWQ1++Zo2/s38BXn9nvLoJMR4A
AAAASUVORK5CYII=

------_=_NextPart_001_01C775FF.19CEFDE7
Content-Type: image/jpeg;
	name="image005.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image005.jpg@01C775DD.8F1D41F0>
Content-Description: image005.jpg
Content-Location: image005.jpg
Content-Disposition: inline

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N
Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/
2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIAAhEBAxEB/8QA
HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF
BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1
dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB
AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC
AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom
JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6+0Eb
NruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHEx
lWYK4wpGMhueleLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9
clnAj17UWQKd3+kNjPb+tN/s+6bR21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1
IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHNR/8AAlv8a9P8NWv/
AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1
U9W1W00TSrjU76Qx29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GF
E6eqnPpzXoHzp19FZniHXIPDmhXOr3McksNsoZkjxuOSBxn61ieHPiLpniHV
V0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc3dpDNClvcvbM
JQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq3
9uaTFqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jH
GM/M3Psa2tC1uy8RaPb6rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFrea
PqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+w3Vj5hYeRdJskXBxyKANGisR
vFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6vRZpDhd+8
n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA
2fxg0W4nTz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumt
pPNA+Zh3GD0oA26KiuJltraWdgSsSFyB1IAzXE6N8WtG1a7tIZNP1GxivZPK
t7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8kKcE9M5IrD1H4h6Hplta
zzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+jtPI
2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1Lvg
Ehv5V4sNKivtc+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m
1u7X7PGJ4vL+zRoFMe3J3YHY5x9a1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD
059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej3PAy/C1qWJTmmkt+
vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLN
d74l0OHxJ4evNInkMSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZ
rKOGLYFXGMse5wf/AK9ekfLl74p/8k31j/rmv/oa1xfhqXUW+IHhl/E0MVuf
7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5C4YHp+Fc5oHg
DVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu1
1WK/m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYH
A9OBQByXjWXV4fi9oj6Fb29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRq
Z0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xaWxgBkg8zqWycHjo1dFoNtq1p
paQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs9CsdDjg8
OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/g
K2/CHhuLwn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ce
FpvFmlWtlDdJbNBdpcFnUsCFB44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r
8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1Lx54N/4TPT7K2FwsDWt0
sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/AJoe
P+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6W
v+oH+7/SvnjT59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrz
ofC+5XwYNFXUoReQ6l9vt7nyzhD6YznpmgD0RFCIqDooArz34S/e8Uf9hmWv
Qk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2gYsC2SMnOOOOKAO4
1X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689G
HQ1lT+EdCuQBLYK2CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgB
umKworm4ESATyYCj+M0j3M5KZnk4bj5zXjey97c+4WK/dr3e39bG/ChiiCEj
Iz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5OW5+c+lCpbu4
5YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckx
Nyf99q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFA
BRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAH//Z

------_=_NextPart_001_01C775FF.19CEFDE7--


--===============2083950269==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============2083950269==--




From sipping-bounces@ietf.org Wed Apr 04 03:18:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzjA-00054n-PR; Wed, 04 Apr 2007 03:16:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYnH3-0005G0-05; Tue, 03 Apr 2007 13:58:29 -0400
Received: from canitpro.objectworld.com ([72.1.207.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYnGt-00044l-6m; Tue, 03 Apr 2007 13:58:28 -0400
Received: from photon.objectworld.com (photon.objectworld.com [10.10.8.2])
	by canitpro.objectworld.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP
	id l33Hw3KH026561; Tue, 3 Apr 2007 13:58:03 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 3 Apr 2007 13:58:02 -0400
Message-ID: <4E2DC1ACE541B94A946B8D8657E372C57A907B@photon.objectworld.com>
In-Reply-To: <1bdd01c77612$7586dcd0$81238182@cis.neustar.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Thread-Index: Acd176Ya+p6xqIGMQfSJrn6cLV80rgACgCmQAAX8woAAAZhX4A==
References: <4E2DC1ACE541B94A946B8D8657E372C57A903F@photon.objectworld.com>
	<1bdd01c77612$7586dcd0$81238182@cis.neustar.com>
From: "Michael Slavitch" <slavitch@objectworld.com>
To: "Brian Rosen" <br@brianrosen.net>, "Paul Kyzivat" <pkyzivat@cisco.com>
X-Spam-Score: 1.50 (*) [Tag at 20.00] EXTRA_MPART_TYPE, HTML_MESSAGE, SPF(none,
	0.1), 132(0.3), 131(0.3)
X-CanItPRO-Stream: outgoing (inherits from default)
X-Scanned-By: CanIt (www . roaringpenguin . com) on 10.10.8.9
X-Spam-Score: 0.6 (/)
X-Scan-Signature: e259f56175f28a8bef2b34d09ea68c34
X-Mailman-Approved-At: Wed, 04 Apr 2007 03:16:14 -0400
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	David R Oran <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0721435076=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0721435076==
Content-class: urn:content-classes:message
Content-Type: multipart/related; type="multipart/alternative";
	boundary="----_=_NextPart_001_01C77619.9FFAEC5B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C77619.9FFAEC5B
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C77619.9FFAEC5B"


------_=_NextPart_002_01C77619.9FFAEC5B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

"vendors will tell you the things you can automate about provisioning
have been automated."

=20

The vendors will tell you this because the things that they automate can
be summarized as:

=20

1.       "not much".

2.       What we automate is our proprietary stuff, sod the rest.

=20

t's things like TN assignment, and dial plans, and gateway routing, and
emergency call provisioning, and permissions, and feature enabling, etc,
etc that dominate provisioning of enterprise telephony systems.  P2P
doesn't help any of that.

=20

I strongly disagree with that.   Look at the documentation for products
from many of the major vendors, there are stacks of complex details
regarding deployment,  not very automatic at all, with many of them
depending on crufty TFTP or FTP with fixed file locations for
provisioning of endpoints.  It's horrible.

Secondly, "it doesn't help with any of that" is only true in a static
fixed universe where you provision once and go away and limit
functionality to very basic tasks.   Even in that world the number of
user change requests on a 2000 user system is on the order of .5%-1% of
all endpoints per day on today's relatively static systems, 10 to 20 per
day, and that's just basic stuff, done at gunpoint.  Routers used to
have only static routes too, and web pages were once coded by hand.=20=20=
=20

=20

Regards

=20

Michael

=20

=20

=20

  <http://www.objectworld.com/>=20

=20

=09=09=20=09=20
Michael Slavitch=20=20=20=20=20=20=20=20=20=20=20=20=20=20

Lead, Technology Initiatives

slavitch@objectworld.com

=09=09=20=09=20

=20

=20

From: Brian Rosen [mailto:br@brianrosen.net]=20
Sent: Tuesday, April 03, 2007 1:07 PM
To: Michael Slavitch; 'Paul Kyzivat'
Cc: 'P2PSIP Mailing List'; 'Michael Hammer (mhammer)'; 'David R Oran';
'Henry Sinnreich'; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage
scenario

=20

I think most enterprise "PBX" vendors will tell you that the things you
can automate about provisioning have been automated, and you won't get
much a win there.  It's things like TN assignment, and dial plans, and
gateway routing, and emergency call provisioning, and permissions, and
feature enabling, etc, etc that dominate provisioning of enterprise
telephony systems.  P2P doesn't help any of that.

=20

I worry, quite a bit, that perpetuating SIP UAs (the SIP client) will
perpetuate the dumb endpoint model, simply because the way they are made
now is that they are dumb endpoints.  They didn't have to be (SIP was
originally designed for smart endpoints).  If we make P2PSIP endpoints
more closely fit the smart endpoint model, then we make the peer that
serves the UAs be the smart box in the middle of the network.

=20

Brian

=20

________________________________

From: Michael Slavitch [mailto:slavitch@objectworld.com]=20
Sent: Tuesday, April 03, 2007 10:48 AM
To: Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

=20

The point I am making is  that in the enterprise the actual topological
deployments of SIP clients and servers, when implemented as software on
generic computing platforms, as well as the mechanisms that make that
deployment happen, are already very different world than the canonical
IMS/CSSIP one which  assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD),  B2BUA demarks,
network elements, and dumb fixed endpoints.  Taking a network as a whole
enterprise application software using C/S SIP proxies and UA's already
approximates something that is close to what is being called P2PSIP,
only in a manner that is highly proprietary, closed, somewhat brittle
and baroque, local, and ad-hoc, with gaping ugly holes.  P2P has the
potential to transform that.

=20

Some points I take from the previous discussion:

"that a P2P setup will be *free*"

=20

-           A P2P network may not be free, but the setup (provisioning)
will be free, and automatic.  This is a major benefit only partially
achieved in enterprise networks,  a benefit of great value to
enterprises that is underserved by vendors.  There is no benefit in
requiring complex deployments where automation can take its place.
Deployment is almost always the biggest cost of enterprise systems
dwarfing the cost of the systems themselves.

=20

"I think this depends greatly on what expectations / contractual
guarantees the enterprise has. It's unclear to me what guarantees can be
made about a P2PSIP network will be able to make, and its unclear what
kind of infrastructure would be installed by/for someone willing to make
guarantees."

=20

-          That is why 'expectations/contractual guarantees' need to be
built into the automation that exists in the P2P overlay.
Self-calculation of such performance metrics is already there in all
enterprise devices, the difference being that while WMI/SNMP data is
merely collected a P2PSIP network can act automatically based on the
metrics within their own nodes, there is a collective 'aha' that forces
behavior change based on strict contracts, aka rules.  An SLA is easier
to maintain if the objects can react accordingly, for example a node
with degrading service can notify that it is on the decline forcing
others to take over.=20=20

=20

There is an old traffic engineering axiom about service guarantees: it
can be achieved through two ways: over engineering or  automation.
P2PSIP allows for automation.

=20

 David Oran wrote:

=20

"I'm not saying this can't be made to work, only that it isn't
immediately obvious that it has advantages over a classic
application/server approach."

=20

The immediately obvious advantage to me is standardized ruggedized
automation that has economies of scale and operates over multiple
domains, eliminating the need for over-engineering,  detailed fussy
provisioning,  and an army of people doing basic monitoring and
care-and-feeding.  Automation is the key, a dynamic statistical network
vs. one that is fixed and assumed deterministic will always win out over
time given a fractal operating environment.   This is being done in fits
and starts in the enterprise data center.   P2PSIP makes it much more
comprehensive.   People want the world to be predictable and
deterministic,  and C/S based systems reflect that. That is the biggest
problem P2P faces because it flies in the face of tradition.=20=20=20

=20

Regards

=20

Michael Slavitch

=20

=20

=20

=20

=20

  <http://www.objectworld.com/>=20

=20

308 Legget Dr.=20
Ottawa Ontario=20
K2K 1Y6 Canada

=20
<http://maps.google.ca/maps?f=3Dq&hl=3Den&q=3D308+Legget+Drive+Ottawa+Ontar=
io+
K2K+1Y6&layer=3D&sll=3D45.341061,-75.904541&sspn=3D0.007119,0.023839&ie=3DU=
TF8&z
=3D18&ll=3D45.341061,-75.904541&spn=3D0.00178,0.00596&t=3Dh&om=3D1>=20

=20

Michael Slavitch=20=20=20=20=20=20=20=20=20=20=20=20=20=20

Lead, Technology Initiatives

slavitch@objectworld.com

PSTN:=20=20

+1.888.398.9698

x225

Fax:

+1.613.599.7457

=20

Skype:=20=20=20=20=20=20=20

 Objectworld=20=20=20

x225

  <skype:Objectworld>=20

=20

=20

=20

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
Sent: Tuesday, April 03, 2007 8:57 AM
To: Michael Slavitch
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer);
David R Oran; p2prg@ietf.org; sipping@ietf.org; zhuxian
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario

=20

=20

=20

Michael Slavitch wrote:

> Sorry for being late into this discussion, but client-server based VM=20

> isn't truly client-server anymore in anything but the smallest or most


> monolithic of enterprise networks, in fact the reality is that most if


> not all enterprise networks contain just peers and superpeers with the


> difference being partially a marketing decision by the vendors, as you


> can charge much more for the servers, and a policy decision made
either=20

> automatically by a software deployment system or by IT staff which
wants=20

> to place supernodes with data sinks on appropriate equipment.

=20

I'm sorry, but I don't understand the point you are trying to make=20

above. You are trying to draw some sort of distinction, but I don't get=20

it. Can you try again.

=20

                Thanks,

                Paul

=20

> In a=20

> highly distributed environment there are potentially hundreds of=20

> possible data sinks for a given application, with the sink based on=20

> subnet or geographic location or balanced load, this can change
rapidly=20

> over time and does.

>=20

> In the case of the Microsoft environment such policy is administered
and=20

> published between supernodes, ie servers, by Active Directory.  It is=20

> advertised to mere peers through DNS.  There was much discussion a
while=20

> ago about building service discovery environment using DNS instead of
a=20

> P2P DHT.  It can be argued that a case study of a P2P example done
using=20

> DNS is any large Windows Server 2003 based Microsoft network with many


> servers and many more clients that also run applications themselves
and=20

> are not just dumb terminals. This is almost certainly always the case
in=20

> all enterprises. The big difference between C/S SIP and P2PSIP is=20

> automation. What is true is that the square peg in round hole of=20

> overloading DNS makes deployments clumsy and brittle within the=20

> enterprise domain and completely unmanageable and unpublishable
outside=20

> the firewall which is why the buck stops there in current enterprise=20

> networking products.

>=20

> The difference between C/S and P2P is largely policy and semantics
with=20

> the biggest difference being that the decisions and rules are highly=20

> distributed.  Apart from that they are not just friends, they are=20

> fraternal twins.

>=20

> Regards

>=20

> Michael Slavitch

>=20

>=20=20

>=20

>=20

> corp_2colour=20

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://www.o
bjectworld.com/>

>=20

>=20=20

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> 308 Legget Dr.

> Ottawa Ontario

> K2K 1Y6 Canada

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://maps.
google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2BOntari=
o%2
BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.007119,0.0238=
39%
26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.00178,0.00596%26=
t=3Dh%2
6om=3D1>

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>=20=20

>=20

> Michael Slavitch=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> Lead, Technology Initiatives

>=20

> slavitch@objectworld.com <mailto:slavitch@objectworld.com>

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> PSTN:=20

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> +1.888.398.9698

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> x225

>=20

> Fax:

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> +1.613.599.7457

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>=20=20

>=20

> Skype:=20=20=20=20=20=20

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>   Objectworld=20

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%
20and%20MME.EML/>=20=20=20

>=20

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

> x225

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%
20and%20MME.EML/>

>=20

>=20=20=20=20=20=20=20=20=20=20=20=20=20

>=20

>=20=20

>=20

>=20=20

>=20

>=20

=20

=20

--=20


=20

________________________________

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete
this information from your system. Use, dissemination, distribution, or
reproduction of this transmission by unintended recipients is not
authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely
those of the author and may not represent those of Objectworld
Communications Corp.

________________________________


Spam
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0fe34
&c=3Ds>=20
Not spam
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0fe34
&c=3Dn>=20
Forget previous vote
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0fe34
&c=3Df>=20


-----------------------------------------------=0D
=0D
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful. =0D
=0D
Any views, opinions and content presented in this e-mail are solely those o=
f the author and may not represent those of Objectworld Communications Corp=
.=20

------_=_NextPart_002_01C77619.9FFAEC5B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:st1=3D"u=
rn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://www.w3.org/TR/RE=
C-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"countr=
y-region"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PostalCode"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.plaintextchar0
	{mso-style-name:plaintextchar;
	mso-style-priority:99;
	font-family:"Calibri","sans-serif";}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	mso-style-priority:99;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:navy;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:846867197;
	mso-list-type:hybrid;
	mso-list-template-ids:-139805038 -1714783482 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1197936675;
	mso-list-type:hybrid;
	mso-list-template-ids:-2146642626 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'color:black'>&#8220;</span><span style=
=3D'font-size:
10.0pt;font-family:"Arial","sans-serif";color:navy'>vendors will tell you t=
he
things you can automate about provisioning have been automated.</span><span
style=3D'color:black'>&#8221;<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:black'>The vendors will tell you =
this
because the things that they automate can be summarized as:<o:p></o:p></spa=
n></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l1 level1 =
lfo3'><![if !supportLists]><span
style=3D'color:black'><span style=3D'mso-list:Ignore'>1.<span style=3D'font=
:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D'color:black'>&#8220;not much&=
#8221;.<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l1 level1 =
lfo3'><![if !supportLists]><span
style=3D'color:black'><span style=3D'mso-list:Ignore'>2.<span style=3D'font=
:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D'color:black'>What we automate=
 is
our proprietary stuff, sod the rest.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>t&#8217;s things like TN assignment, and dial plans, and gatewa=
y routing,
and emergency call provisioning, and permissions, and feature enabling, etc,
etc that dominate provisioning of enterprise telephony systems. &nbsp;P2P
doesn&#8217;t help any of that.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:black'>I strongly disagree with t=
hat. &nbsp;&nbsp;Look
at the documentation for products from many of the major vendors, there are
stacks of complex details regarding deployment,&nbsp; not very automatic at=
 all,
with many of them depending on crufty TFTP or FTP with fixed file locations=
 for
provisioning of endpoints.&nbsp; It&#8217;s horrible.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'>Secondly, &#8220;it doesn&=
#8217;t help with
any of that&#8221; is only true in a static fixed universe where you provis=
ion once
and go away and limit functionality to very basic tasks.&nbsp; &nbsp;Even i=
n that world the
number of user change requests on a 2000 user system is on the order of .5%=
-1%
of all endpoints per day on today&#8217;s relatively static systems, 10 to =
20 per
day, and that&#8217;s just basic stuff, done at gunpoint.&nbsp; Routers use=
d to have only static
routes too, and web pages were once coded by hand.&nbsp;&nbsp; <o:p></o:p><=
/span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:black'>Regards<o:p></o:p></span><=
/p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:black'>Michael<o:p></o:p></span><=
/p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<div>

<table class=3DMsoNormalTable border=3D1 cellspacing=3D0 cellpadding=3D0 wi=
dth=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse;border:none'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop style=3D'width:6.65in;border:non=
e;
  border-top:solid windowtext 1.0pt;background:white;padding:0in 5.4pt 0in =
5.4pt'>
  <p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span>=
</p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop style=3D'width:214.55pt;border:none;backgrou=
nd:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><a href=3D"http://www.objectworld.com/"
  title=3D"Objectworld Communications"><span style=3D'color:black;text-deco=
ration:
  none'><img border=3D0 width=3D237 height=3D42 id=3D"Picture_x0020_1"
  src=3D"cid:image002.jpg@01C775F8.17EDD430" alt=3D"corp_2colour"></span></=
a><span
  style=3D'color:black'><o:p></o:p></span></p>
  <p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span>=
</p>
  </td>
  <td width=3D211 valign=3Dtop style=3D'width:158.05pt;border:none;backgrou=
nd:white;
  padding:0in 0in 0in 0in'></td>
  <td width=3D137 valign=3Dtop style=3D'width:102.6pt;border:none;backgroun=
d:white;
  padding:0in 0in 0in 0in'></td>
  <td style=3D'border:none;padding:0in 0in 0in 0in' width=3D2><p class=3D'M=
soNormal'>&nbsp;</td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop style=3D'width:214.55pt;border:none;backgrou=
nd:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal><span style=3D'color:black'>Michael
    Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; <o:p></o:p></span></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal><span style=3D'color:black'>Lead, Technology Initi=
atives<o:p></o:p></span></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal><span style=3D'color:black'>slavitch@objectworld.c=
om<o:p></o:p></span></p>
    </td>
   </tr>
  </table>
  </td>
  <td width=3D211 valign=3Dtop style=3D'width:158.05pt;border:none;backgrou=
nd:white;
  padding:0in 0in 0in 0in'></td>
  <td width=3D137 valign=3Dtop style=3D'width:102.6pt;border:none;backgroun=
d:white;
  padding:0in 0in 0in 0in'></td>
  <td style=3D'border:none;padding:0in 0in 0in 0in' width=3D2><p class=3D'M=
soNormal'>&nbsp;</td>
 </tr>
</table>

<p class=3DMsoNormal><span style=3D'color:black;letter-spacing:-.5pt'><o:p>=
&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Brian Rosen
[mailto:br@brianrosen.net] <br>
<b>Sent:</b> Tuesday, April 03, 2007 1:07 PM<br>
<b>To:</b> Michael Slavitch; 'Paul Kyzivat'<br>
<b>Cc:</b> 'P2PSIP Mailing List'; 'Michael Hammer (mhammer)'; 'David R Oran=
';
'Henry Sinnreich'; p2prg@ietf.org; sipping@ietf.org<br>
<b>Subject:</b> RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage
scenario<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>I think most enterprise &#8220;PBX&#8221; vendors will tell you=
 that the things
you can automate about provisioning have been automated, and you won&#8217;=
t get much
a win there. &nbsp;It&#8217;s things like TN assignment, and dial plans, an=
d gateway
routing, and emergency call provisioning, and permissions, and feature
enabling, etc, etc that dominate provisioning of enterprise telephony syste=
ms.
&nbsp;P2P doesn&#8217;t help any of that.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>I worry, quite a bit, that perpetuating SIP UAs (the SIP client)
will perpetuate the dumb endpoint model, simply because the way they are ma=
de
now is that they are dumb endpoints. &nbsp;They didn&#8217;t have to be (SI=
P was
originally designed for smart endpoints).&nbsp; If we make P2PSIP endpoints
more closely fit the smart endpoint model, then we make the peer that serves
the UAs be the smart box in the middle of the network.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>Brian<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Michael Slavi=
tch
[mailto:slavitch@objectworld.com] <br>
<b>Sent:</b> Tuesday, April 03, 2007 10:48 AM<br>
<b>To:</b> Paul Kyzivat<br>
<b>Cc:</b> P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Hen=
ry
Sinnreich; p2prg@ietf.org; sipping@ietf.org<br>
<b>Subject:</b> [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenari=
o</span><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p=
></span></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>The point I am making is&nbsp; that in the enterpri=
se the
actual topological deployments of SIP clients and servers, <i>when implemen=
ted
as software on generic computing platforms</i>, as well as the <i>mechanisms
that make that deployment happen</i>, are already very different world than=
 the
canonical IMS/CSSIP one which &nbsp;assumes SIP as core monolithic servers,
fixed enterprise network integrated access devices (IAD), &nbsp;B2BUA demar=
ks,
network elements, and dumb fixed endpoints.&nbsp; Taking a network as a who=
le
enterprise application software using C/S SIP proxies and UA&#8217;s <i>alr=
eady</i>
approximates something that is close to what is being called P2PSIP, only i=
n a
manner that is highly proprietary, closed, somewhat brittle and baroque, lo=
cal,
and ad-hoc, with gaping ugly holes.&nbsp; P2P has the potential to transform
that.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText style=3D'margin-bottom:12.0pt'>Some points I take f=
rom the
previous discussion:<o:p></o:p></p>

<p class=3DMsoPlainText>&#8220;that a P2P setup will be *free*&#8221;<o:p><=
/o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-li=
st:l0 level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New Roman"'>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>&nbsp;A P2P network may not be free, but the setup
(provisioning) will be free, and automatic.&nbsp; This is a major benefit o=
nly
partially achieved in enterprise networks,&nbsp; a benefit of great value to
enterprises that is underserved by vendors.&nbsp; There is no benefit in
requiring complex deployments where automation can take its place.&nbsp;
Deployment is almost always the biggest cost of enterprise systems dwarfing=
 the
cost of the systems themselves.<o:p></o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&#8220;I think this depends greatly on what expecta=
tions /
contractual guarantees the enterprise has. It&#8217;s unclear to me what gu=
arantees
can be made about a P2PSIP network will be able to make, and its unclear wh=
at
kind of infrastructure would be installed by/for someone willing to make
guarantees.&#8221;<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-li=
st:l0 level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New Roman"'>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>That is why &#8216;expectations/contractual guarant=
ees&#8217; need
to be built into the automation that exists in the P2P overlay.&nbsp;
Self-calculation of such performance metrics is already there in all enterp=
rise
devices, the difference being that while WMI/SNMP data is merely collected a
P2PSIP network can act automatically based on the metrics within their own
nodes, there is a collective &#8216;aha&#8217; that forces behavior change =
based on strict
contracts, aka rules.&nbsp; An <st1:place w:st=3D"on">SLA</st1:place> is ea=
sier
to maintain if the objects can react accordingly, for example a node with
degrading service can notify that it is on the decline forcing others to ta=
ke
over.&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>There is an old traffic engineering axiom about ser=
vice
guarantees: it can be achieved through two ways: over engineering or
&nbsp;automation.&nbsp; P2PSIP allows for automation.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&nbsp;David Oran wrote:<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&#8220;I'm not saying this can't be made to work, o=
nly that it
isn't immediately obvious that it has advantages over a classic
application/server approach.&#8221;<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>The immediately obvious advantage to me is standard=
ized
ruggedized automation that has economies of scale and operates over multiple
domains, eliminating the need for over-engineering,&nbsp; detailed fussy
provisioning,&nbsp; and an army of people doing basic monitoring and
care-and-feeding.&nbsp; Automation is the key, a dynamic statistical network
vs. one that is fixed and assumed deterministic will always win out over ti=
me
given a fractal operating environment.&nbsp;&nbsp; This is being done in fi=
ts
and starts in the enterprise data center.&nbsp;&nbsp; P2PSIP makes it much =
more
comprehensive.&nbsp; &nbsp;People want the world to be predictable and
deterministic,&nbsp; and C/S based systems reflect that. That is the biggest
problem P2P faces because it flies in the face of tradition. &nbsp;&nbsp;<o=
:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Regards<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Michael Slavitch<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&nbsp;<o:p></o:p></p>

<p class=3DMsoPlainText>&nbsp;<o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 wi=
dth=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop style=3D'width:6.65in;border:non=
e;
  border-top:solid windowtext 1.0pt;background:white;padding:0in 5.4pt 0in =
5.4pt'>
  <p class=3DMsoNormal><o:p>&nbsp;</o:p></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop style=3D'width:214.55pt;background:white;pad=
ding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><a href=3D"http://www.objectworld.com/"
  title=3D"Objectworld Communications"><span style=3D'color:windowtext;text=
-decoration:
  none'><img border=3D0 width=3D237 height=3D42 id=3D"Picture_x005f_x0020_1"
  src=3D"cid:image005.jpg@01C775F8.17EDD430" alt=3D"corp_2colour"></span></=
a><o:p></o:p></p>
  <p class=3DMsoNormal><o:p>&nbsp;</o:p></p>
  </td>
  <td width=3D211 valign=3Dtop style=3D'width:158.05pt;background:white;pad=
ding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><st1:Street w:st=3D"on"><st1:address w:st=3D"on">308=
 Legget Dr</st1:address></st1:Street>.
  <br>
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> <st1:State w=
:st=3D"on">Ontario</st1:State>
   <br>
<st1:PostalCode w:st=3D"on">K2K 1Y6</st1:PostalCode> <st1:country-region w:=
st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></p>
  </td>
  <td width=3D137 valign=3Dtop style=3D'width:102.6pt;background:white;padd=
ing:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><a
  href=3D"http://maps.google.ca/maps?f=3Dq&amp;hl=3Den&amp;q=3D308+Legget+D=
rive+Ottawa+Ontario+K2K+1Y6&amp;layer=3D&amp;sll=3D45.341061,-75.904541&amp=
;sspn=3D0.007119,0.023839&amp;ie=3DUTF8&amp;z=3D18&amp;ll=3D45.341061,-75.9=
04541&amp;spn=3D0.00178,0.00596&amp;t=3Dh&amp;om=3D1"
  title=3D"308 Legget Drive Ottawa Ontario K2K 1Y6"><span style=3D'color:wi=
ndowtext;
  text-decoration:none'><img border=3D0 width=3D29 height=3D29
  id=3D"Picture_x005f_x0020_6" src=3D"cid:image006.jpg@01C775F8.17EDD430"><=
/span></a><o:p></o:p></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal>&nbsp;<o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop style=3D'width:214.55pt;background:white;pad=
ding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>Michael
    Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
    <o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>Lead, Technology Initiatives<o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>slavitch@objectworld.com<o:p></o:p></p>
    </td>
   </tr>
  </table>
  </td>
  <td width=3D211 valign=3Dtop style=3D'width:158.05pt;background:white;pad=
ding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D204
   style=3D'width:152.85pt;border-collapse:collapse'>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal>PSTN:&nbsp; <o:p></o:p></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>+1.888.398.9698<o:p></o:p></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal>x225<o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal>Fax:<o:p></o:p></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>+1.613.599.7457<o:p></o:p></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal><o:p>&nbsp;</o:p></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal>Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></=
o:p></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal>&nbsp;<a href=3D"Skype:Objectworld">Objectworld</a=
>&nbsp;&nbsp;
    <o:p></o:p></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in 0in =
0in'>
    <p class=3DMsoNormal>x225<o:p></o:p></p>
    </td>
   </tr>
  </table>
  </td>
  <td width=3D137 valign=3Dtop style=3D'width:102.6pt;background:white;padd=
ing:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><a
  href=3D"skype:Objectworld" title=3DObjectworld><span style=3D'color:windo=
wtext;
  text-decoration:none'><img border=3D0 width=3D26 height=3D26
  id=3D"Picture_x005f_x0020_3" src=3D"cid:image007.jpg@01C775F8.17EDD430"><=
/span></a><o:p></o:p></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal>&nbsp;<o:p></o:p></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>-----Original Message-----<br>
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] <br>
Sent: Tuesday, April 03, 2007 8:57 AM<br>
To: Michael Slavitch<br>
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); David R
Oran; p2prg@ietf.org; sipping@ietf.org; zhuxian<br>
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Michael Slavitch wrote:<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Sorry for being late into this discussion, but
client-server based VM <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; isn't truly client-server anymore in anything =
but
the smallest or most <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; monolithic of enterprise networks, in fact the
reality is that most if <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; not all enterprise networks contain just peers=
 and
superpeers with the <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; difference being partially a marketing decisio=
n by the
vendors, as you <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; can charge much more for the servers, and a po=
licy
decision made either <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; automatically by a software deployment system =
or by
IT staff which wants <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; to place supernodes with data sinks on appropr=
iate
equipment.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>I'm sorry, but I don't understand the point you are
trying to make <o:p></o:p></p>

<p class=3DMsoPlainText>above. You are trying to draw some sort of distinct=
ion,
but I don't get <o:p></o:p></p>

<p class=3DMsoPlainText>it. Can you try again.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Thanks,<o:p></o:p></p>

<p class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Paul<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&gt; In a <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; highly distributed environment there are poten=
tially
hundreds of <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; possible data sinks for a given application, w=
ith
the sink based on <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; subnet or geographic location or balanced load=
, this
can change rapidly <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; over time and does.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; In the case of the Microsoft environment such =
policy
is administered and <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; published between supernodes, ie servers, by A=
ctive
Directory.&nbsp; It is <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; advertised to mere peers through DNS.&nbsp; Th=
ere
was much discussion a while <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; ago about building service discovery environme=
nt
using DNS instead of a <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; P2P DHT.&nbsp; It can be argued that a case st=
udy of
a P2P example done using <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; DNS is any large Windows Server 2003 based Mic=
rosoft
network with many <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; servers and many more clients that also run
applications themselves and <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; are not just dumb terminals. This is almost
certainly always the case in <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; all enterprises. The big difference between C/=
S SIP
and P2PSIP is <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; automation. What is true is that the square pe=
g in
round hole of <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; overloading DNS makes deployments clumsy and b=
rittle
within the <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; enterprise domain and completely unmanageable =
and
unpublishable outside <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; the firewall which is why the buck stops there=
 in
current enterprise <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; networking products.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; The difference between C/S and P2P is largely =
policy
and semantics with <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; the biggest difference being that the decision=
s and
rules are highly <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; distributed.&nbsp; Apart from that they are no=
t just
friends, they are <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; fraternal twins.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Regards<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Michael Slavitch<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; corp_2colour <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; &lt;https://firewall.objectworld.com/exchweb/b=
in/redir.asp?URL=3Dhttp://www.objectworld.com/&gt;<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <st1:Street w:st=3D"on"><st1:address w:st=3D"o=
n">308
  Legget Dr</st1:address></st1:Street>.<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <st1:place w:st=3D"on"><st1:City w:st=3D"on">O=
ttawa</st1:City>
 <st1:State w:st=3D"on">Ontario</st1:State></st1:place><o:p></o:p></p>

<p class=3DMsoPlainText>&gt; K2K 1Y6 <st1:country-region w:st=3D"on"><st1:p=
lace
 w:st=3D"on">Canada</st1:place></st1:country-region><o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://map=
s.google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2BOnta=
rio%2BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.007119,0=
.023839%26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.00178,0.=
00596%26t=3Dh%26om=3D1&gt;<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Michael
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Lead, Technology Initiatives<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; slavitch@objectworld.com
&lt;mailto:slavitch@objectworld.com&gt;<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; PSTN: <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; +1.888.398.9698<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; x225<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Fax:<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; +1.613.599.7457<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:=
p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp;&nbsp; Objectworld <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,=
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20a=
nd%20MME.EML/&gt;&nbsp;&nbsp;
<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; x225<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,=
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20a=
nd%20MME.EML/&gt;<o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o=
:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText>&gt; <o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>-- <o:p></o:p></p>

<p class=3DMsoPlainText>BEGIN-ANTISPAM-VOTING-LINKS<o:p></o:p></p>

<p class=3DMsoPlainText>---------------------------------------------------=
---<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Teach CanIt if this mail (ID 657805) is spam:<o:p><=
/o:p></p>

<p class=3DMsoPlainText>Spam:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fdee=
55b7&amp;c=3Ds<o:p></o:p></p>

<p class=3DMsoPlainText>Not spam:&nbsp;&nbsp;&nbsp; http://canitpro-int.obj=
ectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fdee55b7&amp;c=3Dn<o:p></o:=
p></p>

<p class=3DMsoPlainText>Forget vote:
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fdee=
55b7&amp;c=3Df<o:p></o:p></p>

<p class=3DMsoPlainText>---------------------------------------------------=
---<o:p></o:p></p>

<p class=3DMsoPlainText>END-ANTISPAM-VOTING-LINKS<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p><span style=3D'font-size:7.5pt'>This transmission (including any attachm=
ents)
may contain confidential information, privileged material (including materi=
al
protected by the solicitor-client or other applicable privileges), or
constitute non-public information. Any use of this information by anyone ot=
her
than the intended recipient is prohibited. If you have received this
transmission in error, please immediately reply to the sender and delete th=
is
information from your system. Use, dissemination, distribution, or reproduc=
tion
of this transmission by unintended recipients is not authorized and may be
unlawful.<o:p></o:p></span></p>

<p><span style=3D'font-size:7.5pt'>Any views, opinions and content presente=
d in
this e-mail are solely those of the author and may not represent those of
Objectworld Communications Corp.<o:p></o:p></span></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:13.5pt;font-family:"Times New Roman","serif";color:black;
background:white'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal><span style=3D'font-size:13.5pt;font-family:"Times New=
 Roman","serif";
color:black;background:white'><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Ds">Spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Dn">Not
spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Df">Forget
previous vote</a></span><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'><o:p></o:p></span></p>

</div>

</div>

</div>

<hr width=3D"100%">=0D
<font size=3D"-2"><p>=0D
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful.</p>=0D
=0D
<p>Any views, opinions and content presented in this e-mail are solely thos=
e of the author and may not represent those of Objectworld Communications C=
orp.</p>=0D
</font>
</body>

</html>

------_=_NextPart_002_01C77619.9FFAEC5B--

------_=_NextPart_001_01C77619.9FFAEC5B
Content-Type: image/jpeg;
	name="image002.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image002.jpg@01C775F8.17EDD430>
Content-Description: image002.jpg
Content-Location: image002.jpg
Content-Disposition: inline

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N
Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/
2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIAAhEBAxEB/8QA
HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF
BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1
dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB
AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC
AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom
JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6+0Eb
NruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHEx
lWYK4wpGMhueleLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9
clnAj17UWQKd3+kNjPb+tN/s+6bR21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1
IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHNR/8AAlv8a9P8NWv/
AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1
U9W1W00TSrjU76Qx29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GF
E6eqnPpzXoHzp19FZniHXIPDmhXOr3McksNsoZkjxuOSBxn61ieHPiLpniHV
V0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc3dpDNClvcvbM
JQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq3
9uaTFqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jH
GM/M3Psa2tC1uy8RaPb6rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFrea
PqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+w3Vj5hYeRdJskXBxyKANGisR
vFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6vRZpDhd+8
n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA
2fxg0W4nTz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumt
pPNA+Zh3GD0oA26KiuJltraWdgSsSFyB1IAzXE6N8WtG1a7tIZNP1GxivZPK
t7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8kKcE9M5IrD1H4h6Hplta
zzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+jtPI
2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1Lvg
Ehv5V4sNKivtc+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m
1u7X7PGJ4vL+zRoFMe3J3YHY5x9a1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD
059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej3PAy/C1qWJTmmkt+
vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLN
d74l0OHxJ4evNInkMSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZ
rKOGLYFXGMse5wf/AK9ekfLl74p/8k31j/rmv/oa1xfhqXUW+IHhl/E0MVuf
7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5C4YHp+Fc5oHg
DVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu1
1WK/m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYH
A9OBQByXjWXV4fi9oj6Fb29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRq
Z0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xaWxgBkg8zqWycHjo1dFoNtq1p
paQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs9CsdDjg8
OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/g
K2/CHhuLwn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ce
FpvFmlWtlDdJbNBdpcFnUsCFB44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r
8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1Lx54N/4TPT7K2FwsDWt0
sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/AJoe
P+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6W
v+oH+7/SvnjT59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrz
ofC+5XwYNFXUoReQ6l9vt7nyzhD6YznpmgD0RFCIqDooArz34S/e8Uf9hmWv
Qk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2gYsC2SMnOOOOKAO4
1X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689G
HQ1lT+EdCuQBLYK2CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgB
umKworm4ESATyYCj+M0j3M5KZnk4bj5zXjey97c+4WK/dr3e39bG/ChiiCEj
Iz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5OW5+c+lCpbu4
5YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckx
Nyf99q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFA
BRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAH//Z

------_=_NextPart_001_01C77619.9FFAEC5B
Content-Type: image/jpeg;
	name="image005.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image005.jpg@01C775F8.17EDD430>
Content-Description: image005.jpg
Content-Location: image005.jpg
Content-Disposition: inline

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N
Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/
2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIAAhEBAxEB/8QA
HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF
BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1
dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB
AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC
AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom
JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6+0Eb
NruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHEx
lWYK4wpGMhueleLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9
clnAj17UWQKd3+kNjPb+tN/s+6bR21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1
IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHNR/8AAlv8a9P8NWv/
AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1
U9W1W00TSrjU76Qx29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GF
E6eqnPpzXoHzp19FZniHXIPDmhXOr3McksNsoZkjxuOSBxn61ieHPiLpniHV
V0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc3dpDNClvcvbM
JQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq3
9uaTFqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jH
GM/M3Psa2tC1uy8RaPb6rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFrea
PqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+w3Vj5hYeRdJskXBxyKANGisR
vFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6vRZpDhd+8
n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA
2fxg0W4nTz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumt
pPNA+Zh3GD0oA26KiuJltraWdgSsSFyB1IAzXE6N8WtG1a7tIZNP1GxivZPK
t7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8kKcE9M5IrD1H4h6Hplta
zzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+jtPI
2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1Lvg
Ehv5V4sNKivtc+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m
1u7X7PGJ4vL+zRoFMe3J3YHY5x9a1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD
059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej3PAy/C1qWJTmmkt+
vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLN
d74l0OHxJ4evNInkMSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZ
rKOGLYFXGMse5wf/AK9ekfLl74p/8k31j/rmv/oa1xfhqXUW+IHhl/E0MVuf
7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5C4YHp+Fc5oHg
DVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu1
1WK/m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYH
A9OBQByXjWXV4fi9oj6Fb29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRq
Z0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xaWxgBkg8zqWycHjo1dFoNtq1p
paQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs9CsdDjg8
OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/g
K2/CHhuLwn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ce
FpvFmlWtlDdJbNBdpcFnUsCFB44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r
8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1Lx54N/4TPT7K2FwsDWt0
sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/AJoe
P+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6W
v+oH+7/SvnjT59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrz
ofC+5XwYNFXUoReQ6l9vt7nyzhD6YznpmgD0RFCIqDooArz34S/e8Uf9hmWv
Qk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2gYsC2SMnOOOOKAO4
1X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689G
HQ1lT+EdCuQBLYK2CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgB
umKworm4ESATyYCj+M0j3M5KZnk4bj5zXjey97c+4WK/dr3e39bG/ChiiCEj
Iz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5OW5+c+lCpbu4
5YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckx
Nyf99q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFA
BRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAH//Z

------_=_NextPart_001_01C77619.9FFAEC5B
Content-Type: image/jpeg;
	name="image006.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image006.jpg@01C775F8.17EDD430>
Content-Description: image006.jpg
Content-Location: image006.jpg
Content-Disposition: inline

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N
Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/
2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAdAB0DASIAAhEBAxEB/8QA
HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF
BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1
dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB
AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC
AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom
JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD0/VNWWCU2
0cnllQPMkAyVz0A9/wCVUylrNEHWKOZjysk+XP5nmua1W8kXU7pZDg+e/wCW
7A/TFPs9UmmUWquq8fK3cf4168cNywTR5EsTzTakdDFqT2M20l2j6mMknI7l
c8j6dK6GORJY1kjYMrDII7ivOruSeB0lklDljgHNdh4ald9Fi39iwX/dycfp
iufFUVGKmjowtZyk4M5/xhoUzXDX9qhbf/rFA5z6j1rjo5pILhGIHytzzivZ
nRZFKsAQazptCspX3NGM/SnQx0qceWSuia+AjUnzxdmef2ttd61f5XcIQcBs
cAe3qa9J0+1W0s44VGAqgAegotrC3th8ic+tWq56+IlWavokdFDDxop21b6n
/9k=

------_=_NextPart_001_01C77619.9FFAEC5B
Content-Type: image/jpeg;
	name="image007.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image007.jpg@01C775F8.17EDD430>
Content-Description: image007.jpg
Content-Location: image007.jpg
Content-Disposition: inline

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N
Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/
2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAaABoDASIAAhEBAxEB/8QA
HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF
BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1
dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB
AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC
AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom
JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1Ga7lkZ2S
dokV2VQgXJwcEnIPcHpVSTW7uHqYHA7bCCfxz/Skuiv9qSwFtitMoA/3gMn8
yab/AGWls8lxqTBbeE5HP+s/z6V4051nJ8j2ervov+AYty6GrpuqQ6lGxQFJ
E++hPT/EVdrjtEuvN8S+ZEuxJjISPbkj+Qrsa7MDiHXpcz3Tt6lwlzIyNa0h
r7E8GPNAwy5xvHb8axbu31G6jSO6W5ZYRwPKbH1JAwTXY0VFfAQqyck7X37M
UqaZx2k6cf7QheCQMUcFipyFAPOfTjj8a7GiitcLhY4eLinuOMeVH//Z

------_=_NextPart_001_01C77619.9FFAEC5B--


--===============0721435076==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0721435076==--




From sipping-bounces@ietf.org Wed Apr 04 03:18:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzjD-000554-0t; Wed, 04 Apr 2007 03:16:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYqwO-0004sm-57; Tue, 03 Apr 2007 17:53:24 -0400
Received: from exprod6og54.obsmtp.com ([64.18.1.189])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HYqwK-0005rF-MM; Tue, 03 Apr 2007 17:53:24 -0400
Received: from source ([192.150.11.134]) by exprod6ob54.postini.com
	([64.18.5.12]) with SMTP; Tue, 03 Apr 2007 14:53:10 PDT
Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com
	[192.150.20.198] (may be forged))
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l33LqUD1021567; Tue, 3 Apr 2007 14:52:35 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	l33Lqt0c028564; Tue, 3 Apr 2007 14:52:56 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Apr 2007 14:52:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Tue, 3 Apr 2007 14:52:47 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223ADF2F@namail5.corp.adobe.com>
In-Reply-To: <4E2DC1ACE541B94A946B8D8657E372C57A907B@photon.objectworld.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Thread-Index: Acd176Ya+p6xqIGMQfSJrn6cLV80rgACgCmQAAX8woAAAZhX4AAHz3sg
References: <4E2DC1ACE541B94A946B8D8657E372C57A903F@photon.objectworld.com>
	<1bdd01c77612$7586dcd0$81238182@cis.neustar.com>
	<4E2DC1ACE541B94A946B8D8657E372C57A907B@photon.objectworld.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Michael Slavitch" <slavitch@objectworld.com>,
	"Brian Rosen" <br@brianrosen.net>, "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 03 Apr 2007 21:52:54.0858 (UTC)
	FILETIME=[6F2A6AA0:01C7763A]
X-Spam-Score: 1.4 (+)
X-Scan-Signature: b20610989b0325858c8c5a1f4b6a50a0
X-Mailman-Approved-At: Wed, 04 Apr 2007 03:16:14 -0400
Cc: sipping@ietf.org, p2prg@ietf.org, David R Oran <oran@cisco.com>,
	P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0395340612=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0395340612==
Content-class: urn:content-classes:message
Content-Type: multipart/related; type="multipart/alternative";
	boundary="----_=_NextPart_001_01C7763A.6DADE46E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7763A.6DADE46E
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C7763A.6DADE46E"


------_=_NextPart_002_01C7763A.6DADE46E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I agree with Michael here. The voice-only PBX is pathetic as an
enterprise communication and productivity platform (no presence, IM, no
integration with apps, etc.) is also exactly the opposite of what self
organizing systems provide. As for the usability of those tiny screens
and remembering the various commands...

Why not just use Skype PC clients or Skype phones instead? At least,
they are WiFi and no configuration is required that cannot be done by
the user. And they can be used on travel as well.

=20

Just think what self organizing and usability means for the maintenance
headcount and budget. Not to mention the associated IT systems.

=20

P2P SIP in the enterprise is not a PBX replacement any more that SIP is
a PSTN replacement, though many decisions makers have not given up :-)

=20

Thanks, Henry

=20

________________________________

From: Michael Slavitch [mailto:slavitch@objectworld.com]=20
Sent: Tuesday, April 03, 2007 12:58 PM
To: Brian Rosen; Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage
scenario

=20

"vendors will tell you the things you can automate about provisioning
have been automated."

=20

The vendors will tell you this because the things that they automate can
be summarized as:

=20

1.      "not much".

2.      What we automate is our proprietary stuff, sod the rest.

=20

t's things like TN assignment, and dial plans, and gateway routing, and
emergency call provisioning, and permissions, and feature enabling, etc,
etc that dominate provisioning of enterprise telephony systems.  P2P
doesn't help any of that.

=20

I strongly disagree with that.   Look at the documentation for products
from many of the major vendors, there are stacks of complex details
regarding deployment,  not very automatic at all, with many of them
depending on crufty TFTP or FTP with fixed file locations for
provisioning of endpoints.  It's horrible.

Secondly, "it doesn't help with any of that" is only true in a static
fixed universe where you provision once and go away and limit
functionality to very basic tasks.   Even in that world the number of
user change requests on a 2000 user system is on the order of .5%-1% of
all endpoints per day on today's relatively static systems, 10 to 20 per
day, and that's just basic stuff, done at gunpoint.  Routers used to
have only static routes too, and web pages were once coded by hand.  =20

=20

Regards

=20

Michael

=20

=20

=20

  <http://www.objectworld.com/>=20

=20

=20

=20

=20

Michael Slavitch             =20

Lead, Technology Initiatives

slavitch@objectworld.com

=20

=20

=20

=20

=20

From: Brian Rosen [mailto:br@brianrosen.net]=20
Sent: Tuesday, April 03, 2007 1:07 PM
To: Michael Slavitch; 'Paul Kyzivat'
Cc: 'P2PSIP Mailing List'; 'Michael Hammer (mhammer)'; 'David R Oran';
'Henry Sinnreich'; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage
scenario

=20

I think most enterprise "PBX" vendors will tell you that the things you
can automate about provisioning have been automated, and you won't get
much a win there.  It's things like TN assignment, and dial plans, and
gateway routing, and emergency call provisioning, and permissions, and
feature enabling, etc, etc that dominate provisioning of enterprise
telephony systems.  P2P doesn't help any of that.

=20

I worry, quite a bit, that perpetuating SIP UAs (the SIP client) will
perpetuate the dumb endpoint model, simply because the way they are made
now is that they are dumb endpoints.  They didn't have to be (SIP was
originally designed for smart endpoints).  If we make P2PSIP endpoints
more closely fit the smart endpoint model, then we make the peer that
serves the UAs be the smart box in the middle of the network.

=20

Brian

=20

________________________________

From: Michael Slavitch [mailto:slavitch@objectworld.com]=20
Sent: Tuesday, April 03, 2007 10:48 AM
To: Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

=20

The point I am making is  that in the enterprise the actual topological
deployments of SIP clients and servers, when implemented as software on
generic computing platforms, as well as the mechanisms that make that
deployment happen, are already very different world than the canonical
IMS/CSSIP one which  assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD),  B2BUA demarks,
network elements, and dumb fixed endpoints.  Taking a network as a whole
enterprise application software using C/S SIP proxies and UA's already
approximates something that is close to what is being called P2PSIP,
only in a manner that is highly proprietary, closed, somewhat brittle
and baroque, local, and ad-hoc, with gaping ugly holes.  P2P has the
potential to transform that.

=20

Some points I take from the previous discussion:

"that a P2P setup will be *free*"

=20

-       A P2P network may not be free, but the setup (provisioning) will
be free, and automatic.  This is a major benefit only partially achieved
in enterprise networks,  a benefit of great value to enterprises that is
underserved by vendors.  There is no benefit in requiring complex
deployments where automation can take its place.  Deployment is almost
always the biggest cost of enterprise systems dwarfing the cost of the
systems themselves.

=20

"I think this depends greatly on what expectations / contractual
guarantees the enterprise has. It's unclear to me what guarantees can be
made about a P2PSIP network will be able to make, and its unclear what
kind of infrastructure would be installed by/for someone willing to make
guarantees."

=20

-      That is why 'expectations/contractual guarantees' need to be
built into the automation that exists in the P2P overlay.
Self-calculation of such performance metrics is already there in all
enterprise devices, the difference being that while WMI/SNMP data is
merely collected a P2PSIP network can act automatically based on the
metrics within their own nodes, there is a collective 'aha' that forces
behavior change based on strict contracts, aka rules.  An SLA is easier
to maintain if the objects can react accordingly, for example a node
with degrading service can notify that it is on the decline forcing
others to take over. =20

=20

There is an old traffic engineering axiom about service guarantees: it
can be achieved through two ways: over engineering or  automation.
P2PSIP allows for automation.

=20

 David Oran wrote:

=20

"I'm not saying this can't be made to work, only that it isn't
immediately obvious that it has advantages over a classic
application/server approach."

=20

The immediately obvious advantage to me is standardized ruggedized
automation that has economies of scale and operates over multiple
domains, eliminating the need for over-engineering,  detailed fussy
provisioning,  and an army of people doing basic monitoring and
care-and-feeding.  Automation is the key, a dynamic statistical network
vs. one that is fixed and assumed deterministic will always win out over
time given a fractal operating environment.   This is being done in fits
and starts in the enterprise data center.   P2PSIP makes it much more
comprehensive.   People want the world to be predictable and
deterministic,  and C/S based systems reflect that. That is the biggest
problem P2P faces because it flies in the face of tradition.  =20

=20

Regards

=20

Michael Slavitch

=20

=20

=20

=20

=20

 <http://www.objectworld.com/>=20

=20

308 Legget Dr.=20
Ottawa Ontario=20
K2K 1Y6 Canada

=20
<http://maps.google.ca/maps?f=3Dq&hl=3Den&q=3D308+Legget+Drive+Ottawa+Ont=
ario+
K2K+1Y6&layer=3D&sll=3D45.341061,-75.904541&sspn=3D0.007119,0.023839&ie=3D=
UTF8&z
=3D18&ll=3D45.341061,-75.904541&spn=3D0.00178,0.00596&t=3Dh&om=3D1>=20

=20

Michael Slavitch             =20

Lead, Technology Initiatives

slavitch@objectworld.com

PSTN: =20

+1.888.398.9698

x225

Fax:

+1.613.599.7457

=20

Skype:      =20

 Objectworld  =20

x225

  <skype:Objectworld>=20

=20

=20

=20

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
Sent: Tuesday, April 03, 2007 8:57 AM
To: Michael Slavitch
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer);
David R Oran; p2prg@ietf.org; sipping@ietf.org; zhuxian
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario

=20

=20

=20

Michael Slavitch wrote:

> Sorry for being late into this discussion, but client-server based VM=20

> isn't truly client-server anymore in anything but the smallest or most


> monolithic of enterprise networks, in fact the reality is that most if


> not all enterprise networks contain just peers and superpeers with the


> difference being partially a marketing decision by the vendors, as you


> can charge much more for the servers, and a policy decision made
either=20

> automatically by a software deployment system or by IT staff which
wants=20

> to place supernodes with data sinks on appropriate equipment.

=20

I'm sorry, but I don't understand the point you are trying to make=20

above. You are trying to draw some sort of distinction, but I don't get=20

it. Can you try again.

=20

                Thanks,

                Paul

=20

> In a=20

> highly distributed environment there are potentially hundreds of=20

> possible data sinks for a given application, with the sink based on=20

> subnet or geographic location or balanced load, this can change
rapidly=20

> over time and does.

>=20

> In the case of the Microsoft environment such policy is administered
and=20

> published between supernodes, ie servers, by Active Directory.  It is=20

> advertised to mere peers through DNS.  There was much discussion a
while=20

> ago about building service discovery environment using DNS instead of
a=20

> P2P DHT.  It can be argued that a case study of a P2P example done
using=20

> DNS is any large Windows Server 2003 based Microsoft network with many


> servers and many more clients that also run applications themselves
and=20

> are not just dumb terminals. This is almost certainly always the case
in=20

> all enterprises. The big difference between C/S SIP and P2PSIP is=20

> automation. What is true is that the square peg in round hole of=20

> overloading DNS makes deployments clumsy and brittle within the=20

> enterprise domain and completely unmanageable and unpublishable
outside=20

> the firewall which is why the buck stops there in current enterprise=20

> networking products.

>=20

> The difference between C/S and P2P is largely policy and semantics
with=20

> the biggest difference being that the decisions and rules are highly=20

> distributed.  Apart from that they are not just friends, they are=20

> fraternal twins.

>=20

> Regards

>=20

> Michael Slavitch

>=20

> =20

>=20

>=20

> corp_2colour=20

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://www.=
o
bjectworld.com/>

>=20

> =20

>=20

>            =20

>=20

> 308 Legget Dr.

> Ottawa Ontario

> K2K 1Y6 Canada

>=20

>            =20

>=20

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://maps=
.
google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2BOnta=
rio%2
BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.007119,0.02=
3839%
26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.00178,0.00596%=
26t=3Dh%2
6om=3D1>

>=20

>            =20

>=20

> =20

>=20

> Michael Slavitch            =20

>=20

> Lead, Technology Initiatives

>=20

> slavitch@objectworld.com <mailto:slavitch@objectworld.com>

>=20

>            =20

>=20

> PSTN:=20

>=20

>            =20

>=20

> +1.888.398.9698

>=20

>            =20

>=20

> x225

>=20

> Fax:

>=20

>            =20

>=20

> +1.613.599.7457

>=20

>            =20

>=20

> =20

>=20

> Skype:     =20

>=20

>            =20

>=20

>   Objectworld=20

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%
20and%20MME.EML/>  =20

>=20

>=20

>            =20

>=20

> x225

>=20

>            =20

>=20

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%
20and%20MME.EML/>

>=20

>            =20

>=20

> =20

>=20

> =20

>=20

>=20

=20

=20

--=20

BEGIN-ANTISPAM-VOTING-LINKS

------------------------------------------------------

=20

Teach CanIt if this mail (ID 657805) is spam:

Spam:
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&m=3D2eb1fdee55=
b7&
c=3Ds

Not spam:
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&m=3D2eb1fdee55=
b7&
c=3Dn

Forget vote:
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&m=3D2eb1fdee55=
b7&
c=3Df

------------------------------------------------------

END-ANTISPAM-VOTING-LINKS

=20

________________________________

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete
this information from your system. Use, dissemination, distribution, or
reproduction of this transmission by unintended recipients is not
authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely
those of the author and may not represent those of Objectworld
Communications Corp.

________________________________


Spam
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0f=
e34
&c=3Ds>=20
Not spam
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0f=
e34
&c=3Dn>=20
Forget previous vote
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0f=
e34
&c=3Df>=20

________________________________

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete
this information from your system. Use, dissemination, distribution, or
reproduction of this transmission by unintended recipients is not
authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely
those of the author and may not represent those of Objectworld
Communications Corp.


------_=_NextPart_002_01C7763A.6DADE46E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns0=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PostalCode"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}
p.MSOPLAINTEXT
	{mso-style-priority:99;}
li.MSOPLAINTEXT
	{mso-style-priority:99;}
div.MSOPLAINTEXT
	{mso-style-priority:99;}
p
	{mso-style-priority:99;}
p.MSOACETATE
	{mso-style-priority:99;}
li.MSOACETATE
	{mso-style-priority:99;}
div.MSOACETATE
	{mso-style-priority:99;}
p.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
li.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
div.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
span.PLAINTEXTCHAR
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR
	{mso-style-priority:99;}
span.PLAINTEXTCHAR0
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR0
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;}
@font-face
	{font-family:Consolas;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;}
p.msolistparagraph, li.msolistparagraph, div.msolistparagraph
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
span.plaintextchar
	{font-family:Consolas;}
span.balloontextchar
	{font-family:Tahoma;}
span.plaintextchar0
	{font-family:Calibri;}
span.balloontextchar0
	{font-family:Tahoma;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:Calibri;
	color:black;}
span.EmailStyle27
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:846867197;
	mso-list-type:hybrid;
	mso-list-template-ids:-139805038 -1714783482 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1197936675;
	mso-list-type:hybrid;
	mso-list-template-ids:-2146642626 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I agree with Michael here. The =
voice-only
PBX is pathetic as an enterprise communication and productivity platform =
(no
presence, IM, no integration with apps, etc.) is also exactly the =
opposite of
what self o<st1:PersonName w:st=3D"on">rg</st1:PersonName>anizing =
systems
provide. As for the usability of those tiny screens and remembering the =
various
commands&#8230;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Why not just use Skype PC clients =
or Skype
phones instead? At least, they are WiFi and no configuration is required =
that
cannot be done by the user. And they can be used on travel as =
well.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Just think what self =
o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>anizing and usability means for the =
maintenance
headcount and budget. Not to mention the associated IT =
systems.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>P2P SIP in the enterprise is not a =
PBX
replacement any more that SIP is a PSTN replacement, though many =
decisions
makers have not given up </span></font><font size=3D2 color=3Dnavy =
face=3DWingdings><span
style=3D'font-size:10.0pt;font-family:Wingdings;color:navy'>J</span></fon=
t><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, =
Henry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Slavitch
[mailto:slavitch@objectworld.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007
12:58 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">Brian
 Rosen</st1:PersonName>; Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; Henry Sinnreich; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>&#8220;</span></font><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>vendors will tell you the things you can automate about
provisioning have been automated.</span></font><font color=3Dblack><span
style=3D'color:black'>&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>The vendors will tell you this =
because the
things that they automate can be summarized =
as:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l1 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3Dblack face=3DCalibri><span =
style=3D'font-size:11.0pt;color:black'><span
style=3D'mso-list:Ignore'>1.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
color=3Dblack><span style=3D'color:black'>&#8220;not =
much&#8221;.<o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l1 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3Dblack face=3DCalibri><span =
style=3D'font-size:11.0pt;color:black'><span
style=3D'mso-list:Ignore'>2.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
color=3Dblack><span style=3D'color:black'>What we automate is our =
proprietary
stuff, sod the rest.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>t&#8217;s things like TN =
assignment, and
dial plans, and gateway routing, and eme<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ency
call provisioning, and permissions, and feature enabling, etc, etc that
dominate provisioning of enterprise telephony systems. &nbsp;P2P =
doesn&#8217;t
help any of that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>I strongly disagree with that. =
&nbsp;&nbsp;Look
at the documentation for products from many of the major vendors, there =
are
stacks of complex details regarding deployment,&nbsp; not very automatic =
at
all, with many of them depending on crufty TFTP or FTP with fixed file
locations for provisioning of endpoints.&nbsp; It&#8217;s =
horrible.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Secondly, &#8220;it doesn&#8217;t =
help
with any of that&#8221; is only true in a static fixed universe where =
you
provision once and go away and limit functionality to very basic =
tasks.&nbsp; &nbsp;Even
in that world the number of user change requests on a 2000 user system =
is on
the order of .5%-1% of all endpoints per day on today&#8217;s relatively =
static
systems, 10 to 20 per day, and that&#8217;s just basic stuff, done at =
gunpoint.&nbsp;
Routers used to have only static routes too, and web pages were once =
coded by
hand.&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Regards<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Michael<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<div>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:6.65in;
  border:none;border-top:solid windowtext =
1.0pt;background:white;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
  =
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><a
  href=3D"http://www.objectworld.com/" title=3D"Objectworld =
Communications"><font
  color=3Dblack><span style=3D'color:black;text-decoration:none'><img =
border=3D0
  width=3D237 height=3D42 id=3D"Picture_x005f_x005f_x005f_x0020_1"
  src=3D"cid:image001.jpg@01C77610.81C1E230" =
alt=3D"corp_2colour"></span></font></a><font
  color=3Dblack><span =
style=3D'color:black'><o:p></o:p></span></font></span></font></p>
  <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
  =
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    style=3D'font-size:11.0pt;color:black'>Michael =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    style=3D'font-size:11.0pt;color:black'>Lead, Technology =
Initiatives<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    =
style=3D'font-size:11.0pt;color:black'>slavitch@objectworld.com<o:p></o:p=
></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black;letter-spacing:-.5pt'><o:p>&nbsp;</=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
<st1:PersonName
w:st=3D"on">Brian Rosen</st1:PersonName> [mailto:br@brianrosen.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007 1:07
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Michael Slavitch; =
'Paul
Kyzivat'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> 'P2PSIP Mailing =
List';
'Michael Hammer (mhammer)'; 'David R Oran'; 'Henry Sinnreich'; =
p2p<st1:PersonName
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>;
sipping@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario<o:p></o:p></span></font></p>

</div>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I think most enterprise =
&#8220;PBX&#8221;
vendors will tell you that the things you can automate about =
provisioning have
been automated, and you won&#8217;t get much a win there. =
&nbsp;It&#8217;s
things like TN assignment, and dial plans, and gateway routing, and =
eme<st1:PersonName
w:st=3D"on">rg</st1:PersonName>ency call provisioning, and permissions, =
and
feature enabling, etc, etc that dominate provisioning of enterprise =
telephony
systems. &nbsp;P2P doesn&#8217;t help any of =
that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I worry, quite a bit, that =
perpetuating
SIP UAs (the SIP client) will perpetuate the dumb endpoint model, simply
because the way they are made now is that they are dumb endpoints. =
&nbsp;They
didn&#8217;t have to be (SIP was originally designed for smart =
endpoints).&nbsp;
If we make P2PSIP endpoints more closely fit the smart endpoint model, =
then we
make the peer that serves the UAs be the smart box in the middle of the
network.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Brian<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Slavitch
[mailto:slavitch@objectworld.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007 10:48
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; Henry Sinnreich; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
point I am making is&nbsp; that in the enterprise the actual topological
deployments of SIP clients and servers, <i><span =
style=3D'font-style:italic'>when
implemented as software on generic computing platforms</span></i>, as =
well as
the <i><span style=3D'font-style:italic'>mechanisms that make that =
deployment
happen</span></i>, are already very different world than the canonical
IMS/CSSIP one which &nbsp;assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD), &nbsp;B2BUA demarks,
network elements, and dumb fixed endpoints.&nbsp; Taking a network as a =
whole
enterprise application software using C/S SIP proxies and UA&#8217;s =
<i><span
style=3D'font-style:italic'>already</span></i> approximates something =
that is
close to what is being called P2PSIP, only in a manner that is highly
proprietary, closed, somewhat brittle and baroque, local, and ad-hoc, =
with
gaping ugly holes.&nbsp; P2P has the potential to transform =
that.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'>Some points I take from the previous =
discussion:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;that
a P2P setup will be *free*&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-list:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>&nbsp;A P2P network may not =
be
free, but the setup (provisioning) will be free, and automatic.&nbsp; =
This is a
major benefit only partially achieved in enterprise networks,&nbsp; a =
benefit of
great value to enterprises that is underserved by vendors.&nbsp; There =
is no
benefit in requiring complex deployments where automation can take its =
place.&nbsp;
Deployment is almost always the biggest cost of enterprise systems =
dwarfing the
cost of the systems themselves.<o:p></o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I
think this depends greatly on what expectations / contractual guarantees =
the
enterprise has. It&#8217;s unclear to me what guarantees can be made =
about a
P2PSIP network will be able to make, and its unclear what kind of
infrastructure would be installed by/for someone willing to make =
guarantees.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-list:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>That is why =
&#8216;expectations/contractual
guarantees&#8217; need to be built into the automation that exists in =
the P2P
overlay.&nbsp; Self-calculation of such performance metrics is already =
there in
all enterprise devices, the difference being that while WMI/SNMP data is =
merely
collected a P2PSIP network can act automatically based on the metrics =
within
their own nodes, there is a collective &#8216;aha&#8217; that forces =
behavior
change based on strict contracts, aka rules.&nbsp; An <st1:place =
w:st=3D"on">SLA</st1:place>
is easier to maintain if the objects can react accordingly, for example =
a node
with degrading service can notify that it is on the decline forcing =
others to
take over.&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>There
is an old traffic engineering axiom about service guarantees: it can be =
achieved
through two ways: over engineering or &nbsp;automation.&nbsp; P2PSIP =
allows for
automation.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;David
Oran wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I'm
not saying this can't be made to work, only that it isn't immediately =
obvious
that it has advantages over a classic application/server =
approach.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
immediately obvious advantage to me is standardized ruggedized =
automation that
has economies of scale and operates over multiple domains, eliminating =
the need
for over-engineering,&nbsp; detailed fussy provisioning,&nbsp; and an =
army of
people doing basic monitoring and care-and-feeding.&nbsp; Automation is =
the
key, a dynamic statistical network vs. one that is fixed and assumed
deterministic will always win out over time given a fractal operating
environment.&nbsp;&nbsp; This is being done in fits and starts in the
enterprise data center.&nbsp;&nbsp; P2PSIP makes it much more =
comprehensive.&nbsp;
&nbsp;People want the world to be predictable and deterministic,&nbsp; =
and C/S
based systems reflect that. That is the biggest problem P2P faces =
because it
flies in the face of tradition. =
&nbsp;&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:6.65in;
  border:none;border-top:solid windowtext =
1.0pt;background:white;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><a
  href=3D"http://www.objectworld.com/" title=3D"Objectworld =
Communications"><font
  color=3Dblack><span =
style=3D'color:windowtext;text-decoration:none'><img
  border=3D0 width=3D237 height=3D42
  id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x0020_1"
  src=3D"cid:image001.jpg@01C77610.81C1E230" =
alt=3D"corp_2colour"></span></font></a><o:p></o:p></span></font></p>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><st1:Street w:st=3D"on"><st1:address =
w:st=3D"on"><font size=3D2
    face=3DCalibri><span style=3D'font-size:11.0pt'>308 Legget =
Dr</span></font></st1:address></st1:Street>.
  <br>
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State w:st=3D"on">Ontario</st1:State>
   <br>
<st1:PostalCode w:st=3D"on">K2K 1Y6</st1:PostalCode> <st1:country-region =
w:st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a
  =
href=3D"http://maps.google.ca/maps?f=3Dq&amp;hl=3Den&amp;q=3D308+Legget+D=
rive+Ottawa+Ontario+K2K+1Y6&amp;layer=3D&amp;sll=3D45.341061,-75.904541&a=
mp;sspn=3D0.007119,0.023839&amp;ie=3DUTF8&amp;z=3D18&amp;ll=3D45.341061,-=
75.904541&amp;spn=3D0.00178,0.00596&amp;t=3Dh&amp;om=3D1"
  title=3D"308 Legget Drive Ottawa Ontario K2K 1Y6"><font =
color=3Dblack><span
  style=3D'color:windowtext;text-decoration:none'><img border=3D0 =
width=3D29
  height=3D29 =
id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x0020_6"
  =
src=3D"cid:image002.jpg@01C77610.81C1E230"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
    =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Lead,
    Technology Initiatives<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>slavitch@objectworld.com<o:p></o:p></span></fo=
nt></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0 width=3D204
   style=3D'width:152.85pt;border-collapse:collapse'>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>PSTN:&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.888.398.9698<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Fax:<o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.613.599.7457<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<a
    href=3D"Skype:Objectworld">Objectworld</a>&nbsp;&nbsp; =
<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a =
href=3D"skype:Objectworld"
  title=3DObjectworld><font color=3Dblack><span =
style=3D'color:windowtext;text-decoration:
  none'><img border=3D0 width=3D26 height=3D26
  id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x0020_3"
  =
src=3D"cid:image003.jpg@01C77610.81C1E230"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>-----Original
Message-----<br>
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] <br>
Sent: Tuesday, April 03, 2007 8:57 AM<br>
To: Michael Slavitch<br>
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); =
David R
Oran; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>;
zhuxian<br>
Subject: Re: [P2P<st1:PersonName w:st=3D"on">rg</st1:PersonName>] RE: =
[Sipping]
Simple SIP usage scenario<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Sorry for being late into this discussion, but client-server based VM =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
isn't truly client-server anymore in anything but the smallest or most =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
monolithic of enterprise networks, in fact the reality is that most if =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
not all enterprise networks contain just peers and superpeers with the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
difference being partially a marketing decision by the vendors, as you =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
can cha<st1:PersonName w:st=3D"on">rg</st1:PersonName>e much more for =
the servers,
and a policy decision made either <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automatically by a software deployment system or by IT staff which wants =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
to place supernodes with data sinks on appropriate =
equipment.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>I'm
sorry, but I don't understand the point you are trying to make =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>above.
You are trying to draw some sort of distinction, but I don't get =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>it.
Can you try again.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Paul<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In a <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
highly distributed environment there are potentially hundreds of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
possible data sinks for a given application, with the sink based on =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
subnet or geographic location or balanced load, this can change rapidly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
over time and does.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In the case of the Microsoft environment such policy is administered and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
published between supernodes, ie servers, by Active Directory.&nbsp; It =
is <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
advertised to mere peers through DNS.&nbsp; There was much discussion a =
while <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
ago about building service discovery environment using DNS instead of a =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
P2P DHT.&nbsp; It can be a<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ued that
a case study of a P2P example done using <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
DNS is any la<st1:PersonName w:st=3D"on">rg</st1:PersonName>e Windows =
Server 2003
based Microsoft network with many <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
servers and many more clients that also run applications themselves and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
are not just dumb terminals. This is almost certainly always the case in =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
all enterprises. The big difference between C/S SIP and P2PSIP is =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automation. What is true is that the square peg in round hole of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
overloading DNS makes deployments clumsy and brittle within the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
enterprise domain and completely unmanageable and unpublishable outside =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the firewall which is why the buck stops there in current enterprise =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
networking products.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
The difference between C/S and P2P is la<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ely
policy and semantics with <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the biggest difference being that the decisions and rules are highly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
distributed.&nbsp; Apart from that they are not just friends, they are =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
fraternal twins.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
corp_2colour <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://w=
ww.objectworld.com/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:Street w:st=3D"on"><st1:address w:st=3D"on">308 Legget =
Dr</st1:address></st1:Street>.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State =
w:st=3D"on">Ontario</st1:State></st1:place><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
K2K 1Y6 <st1:place w:st=3D"on"><st1:country-region =
w:st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></span></fo=
nt></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://m=
aps.google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2B=
Ontario%2BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.00=
7119,0.023839%26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.=
00178,0.00596%26t=3Dh%26om=3D1&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Lead, Technology Initiatives<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
slavitch@objectworld.com =
&lt;mailto:slavitch@objectworld.com&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
PSTN: <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.888.398.9698<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Fax:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.613.599.7457<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;&nbsp;
Objectworld <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>--
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>BEGIN-ANTISPAM-VOTING-LINKS<o:p></o:p></span><=
/font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Teach
CanIt if this mail (ID 657805) is spam:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Spam:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Ds<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Not
spam:&nbsp;&nbsp;&nbsp;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Dn<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Fo<st1:PersonName
w:st=3D"on">rg</st1:PersonName>et vote: =
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Df<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>END-ANTISPAM-VOTING-LINKS<o:p></o:p></span></f=
ont></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>This
transmission (including any attachments) may contain confidential =
information,
privileged material (including material protected by the =
solicitor-client 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 immediately reply =
to the
sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended =
recipients is
not authorized and may be unlawful.<o:p></o:p></span></font></p>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>Any views,
opinions and content presented in this e-mail are solely those of the =
author
and may not represent those of Objectworld Communications =
Corp.<o:p></o:p></span></font></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D4
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:13.5pt;font-family:
"Times New Roman";color:black;background:white'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><font size=3D4 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:13.5pt;font-family:"Times New =
Roman";color:black;background:
white'><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Ds">Spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Dn">Not
spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Df">Forget
previous vote</a></span></font><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

</div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>This
transmission (including any attachments) may contain confidential =
information,
privileged material (including material protected by the =
solicitor-client 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 immediately reply =
to the
sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended =
recipients is
not authorized and may be unlawful.<o:p></o:p></span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>Any
views, opinions and content presented in this e-mail are solely those of =
the
author and may not represent those of Objectworld Communications =
Corp.<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_002_01C7763A.6DADE46E--

------_=_NextPart_001_01C7763A.6DADE46E
Content-Type: image/jpeg;
	name="image001.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image001.jpg@01C77610.81C1E230>
Content-Description: image001.jpg
Content-Location: image001.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6
+0EbNruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHExlWYK4wpGMhue
leLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9clnAj17UWQKd3+kNjPb+tN/s+6bR
21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHN
R/8AAlv8a9P8NWv/AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1U9W1W00TSrjU76Qx
29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GFE6eqnPpzXoHzp19FZniHXIPDmhXOr3Mc
ksNsoZkjxuOSBxn61ieHPiLpniHVV0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc
3dpDNClvcvbMJQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq39uaT
FqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jHGM/M3Psa2tC1uy8RaPb6
rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFreaPqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+
w3Vj5hYeRdJskXBxyKANGisRvFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6v
RZpDhd+8n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA2fxg0W4n
Tz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumtpPNA+Zh3GD0oA26KiuJltraW
dgSsSFyB1IAzXE6N8WtG1a7tIZNP1GxivZPKt7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8
kKcE9M5IrD1H4h6Hpltazzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+
jtPI2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1LvgEhv5V4sNKivt
c+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m1u7X7PGJ4vL+zRoFMe3J3YHY5x9a
1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej
3PAy/C1qWJTmmkt+vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLNd74l0OHxJ4evNInk
MSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZrKOGLYFXGMse5wf/AK9ekfLl74p/8k31
j/rmv/oa1xfhqXUW+IHhl/E0MVuf7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5
C4YHp+Fc5oHgDVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu11WK/
m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYHA9OBQByXjWXV4fi9oj6F
b29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRqZ0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xa
WxgBkg8zqWycHjo1dFoNtq1ppaQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs
9CsdDjg8OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/gK2/CHhuL
wn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ceFpvFmlWtlDdJbNBdpcFnUsCF
B44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1
Lx54N/4TPT7K2FwsDWt0sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/
AJoeP+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6Wv+oH+7/SvnjT
59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrzofC+5XwYNFXUoReQ6l9vt7nyzhD6
YznpmgD0RFCIqDooArz34S/e8Uf9hmWvQk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2
gYsC2SMnOOOOKAO41X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689GHQ1lT+EdCuQBLYK2
CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgBumKworm4ESATyYCj+M0j3M5KZnk4bj5z
Xjey97c+4WK/dr3e39bG/ChiiCEjIz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5
OW5+c+lCpbu45YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckxNyf9
9q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRR
QAUUUUAFFFFAH//Z

------_=_NextPart_001_01C7763A.6DADE46E
Content-Type: image/jpeg;
	name="image002.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image002.jpg@01C77610.81C1E230>
Content-Description: image002.jpg
Content-Location: image002.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAdAB0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD0/VNW
WCU20cnllQPMkAyVz0A9/wCVUylrNEHWKOZjysk+XP5nmua1W8kXU7pZDg+e/wCW7A/TFPs9UmmU
Wquq8fK3cf4168cNywTR5EsTzTakdDFqT2M20l2j6mMknI7lc8j6dK6GORJY1kjYMrDII7ivOruS
eB0lklDljgHNdh4ald9Fi39iwX/dycfpiufFUVGKmjowtZyk4M5/xhoUzXDX9qhbf/rFA5z6j1rj
o5pILhGIHytzzivZnRZFKsAQazptCspX3NGM/SnQx0qceWSuia+AjUnzxdmef2ttd61f5XcIQcBs
cAe3qa9J0+1W0s44VGAqgAegotrC3th8ic+tWq56+IlWavokdFDDxop21b6n/9k=

------_=_NextPart_001_01C7763A.6DADE46E
Content-Type: image/jpeg;
	name="image003.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image003.jpg@01C77610.81C1E230>
Content-Description: image003.jpg
Content-Location: image003.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAaABoDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1Ga7l
kZ2SdokV2VQgXJwcEnIPcHpVSTW7uHqYHA7bCCfxz/Skuiv9qSwFtitMoA/3gMn8yab/AGWls8lx
qTBbeE5HP+s/z6V4051nJ8j2ervov+AYty6GrpuqQ6lGxQFJE++hPT/EVdrjtEuvN8S+ZEuxJjIS
Pbkj+Qrsa7MDiHXpcz3Tt6lwlzIyNa0hr7E8GPNAwy5xvHb8axbu31G6jSO6W5ZYRwPKbH1JAwTX
Y0VFfAQqyck7X37MUqaZx2k6cf7QheCQMUcFipyFAPOfTjj8a7GiitcLhY4eLinuOMeVH//Z

------_=_NextPart_001_01C7763A.6DADE46E--


--===============0395340612==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0395340612==--




From sipping-bounces@ietf.org Wed Apr 04 03:18:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzj6-00050D-E8; Wed, 04 Apr 2007 03:16:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYMe9-0001Jv-Er
	for sipping@ietf.org; Mon, 02 Apr 2007 09:32:33 -0400
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYMe7-0005LC-0V
	for sipping@ietf.org; Mon, 02 Apr 2007 09:32:33 -0400
Received: by ug-out-1314.google.com with SMTP id 72so1461317ugd
	for <sipping@ietf.org>; Mon, 02 Apr 2007 06:32:29 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=WfK1xBlUD9udSdbnbz299lIwb/lpdECIs3xIWBIBW/t7oxC2Gv9V5n8IJiWf2imAuxvbNugtqBhNlsCtpFAtELnLxTwegmrM8oykMT20oxYji8fE8xosj1N6P7Nc9CoPOKEPIP3E+StWPM9bSSAsDowYLkbez5SdVg6Lz7wvH34=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=a1TjbeIG7aTLhyoE+RG1kLGkJ1ItJW2kQ11VjfUuBRkIvZNjpHg5CUZCNAzsfT04NGFHt/GsiVOZcX18eWiIrElNPSGq6Ir+zXcA7ZHksqzGibC2eTXTzKhIjrm8JyLxFukeirj8iPE4cvF3pApvQyD1AMrR9sA5drqe0tT5gX8=
Received: by 10.82.154.2 with SMTP id b2mr1461004bue.1175520748792;
	Mon, 02 Apr 2007 06:32:28 -0700 (PDT)
Received: by 10.82.127.17 with HTTP; Mon, 2 Apr 2007 06:32:28 -0700 (PDT)
Message-ID: <4d4304a00704020632r71315532s1be1df106c4f426a@mail.gmail.com>
Date: Mon, 2 Apr 2007 09:32:28 -0400
From: "David A. Bryan" <dbryan@sipeerior.com>
To: "Jeroen van Bemmel" <jbemmel@zonnet.nl>
Subject: Re: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
In-Reply-To: <00b201c7748e$33067df0$0601a8c0@BEMBUSTER>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <24CCCC428EFEA2469BF046DB3C7A8D225274F4@namail5.corp.adobe.com>
	<EC0E1E0E-2E83-4674-BAC0-78CB94F0BD43@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADECA@namail5.corp.adobe.com>
	<4FF5FA52-1B38-4964-87AE-72300CE89A1F@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADED9@namail5.corp.adobe.com>
	<460D4825.2090800@cisco.com>
	<7b683f3f0703301556j95f2c10sf12d666994dedf6f@mail.gmail.com>
	<460D9D9C.1040304@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com>
	<00b201c7748e$33067df0$0601a8c0@BEMBUSTER>
X-Google-Sender-Auth: d7b6568599097134
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3f3e54d3c03ed638c06aa9fa6861237e
X-Mailman-Approved-At: Wed, 04 Apr 2007 03:16:13 -0400
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	Paul Kyzivat <pkyzivat@cisco.com>, David R Oran <oran@cisco.com>,
	p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I don't think Henry was saying only there -- just that that might be
another deployment we haven't thought about. I am pretty sure he is
very much in favor of having them in wireless devices.

Personally, I think that putting P2PSIP peers in edge devices would be
a good place to do it for home wireline users -- as Henry points out,
it avoids the NAT issue, among other things. Of course I would also
want to see them in UAs, softphones, wireless devices, maybe even
consumer devices, etc. (and I am sure Henry wants to see P2PSIP peers
everywhere too!)

David

On 4/1/07, Jeroen van Bemmel <jbemmel@zonnet.nl> wrote:
> Henry,
>
> Aren't you confusing "usage scenarios" with "deployment scenarios" here? Why
> restrict P2P SIP to only certain types of devices? And if you insist on
> that, why not mobile devices?
>
> Regards,
> Jeroen
>
> Henry Sinnreich wrote:
> > Paul,
> >
> >> I more or less agree with the final conclusion below.
> >
> > This is good starting point to discuss some usage scenarios.
> >
> > Putting on my former hat as an employee for a carrier, I cannot
> > overlook the following:
> >
> > P2P SIP implemented correctly in the residential access box or cable
> > set-top box indeed is a good or better replacement for the entire VoIP
> > network infrastructure (cost, operations, new services, etc).
> > Integrated access devices for the enterprise can probably play a
> > similar role, not to mention existing P2P PBX products (please refer
> > to all the advantages of P2P that need not repeated here).
> >
> > What do people think of these three usage scenarios for P2P SIP:
> > - SIP peer in the DSL access device,
> > - SIP peer in the cable access device,
> > - SIP peer in enterprise network integrated access device (IAD).
> >
> > Note that these examples imply very low churn for the peers and add
> > the data retention resilience of P2P (geographic diversity is native
> > and mobile, etc.). Incidentally, NAT traversal may also not be a
> > problem, or at least an easier problem.
> >
> > What do you all think?
> >
> > I have taken the liberty to copy the P2P SIP list, since the low churn
> > scenarios are of interest for the DHT selection. Or just pick the same
> > DHT for all scenarios anyway? I don't think so.
> >
> > Thanks, Henry
> >
> >
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: Friday, March 30, 2007 6:31 PM
> > To: Eunsoo Shim
> > Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
> > p2prg@ietf.org; sipping@ietf.org; zhuxian
> > Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
> >
> > I more or less agree with the final conclusion below.
> >
> > My main point here is that P2P and C/S need not be enemies. Nor is a
> > total C/S system necessarily evil. What is most evil is *bundling* of
> > services that prevents freedom of choice.
> >
> > I think I would be quite happy with a SP that provides a
> > registrar/proxy
> >
> > and allows me to provide all other features as I see fit - by taking
> > them ala carte from the SP, or subscribing to them from one or more
> > other SPs, or by providing them myself via appliances I own. If that
> > registrar/proxy was replaced by a P2P sip community, the differences,
> > if
> >
> > any, would hopefully be more a function of the implementation and the
> > business models of those involved than the architecture.
> >
> > (I gather the general assumption is that a P2P setup will be *free*.
> > But
> >
> > I have a hard time believing that. If most of the usage is by mobile
> > devices that can't be peers, then somebody will have to pay for enough
> > peers to support them. If it isn't free, then how is it better than a
> > well engineered C/S system?)
> >
> > So I think the key thing here is that some features will require
> > getting
> >
> > some help from another node. There ought to be the option to pick a
> > different source for each helper you require, and an ability for it
> > all to play together.
> >
> > Paul
> >
> > Eunsoo Shim wrote:
> >> Please see my inline comment.
> >>
> >> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com
> >> <mailto:pkyzivat@cisco.com>> wrote:
> >>
> >>
> >>
> >>     Henry Sinnreich wrote:
> >>      > David Oran wrote (with regard to voice mail):
> >>      >
> >>      >> I'm not saying this can't be made to work, only that it isn't
> >>      > immediately >obvious that it has advantages over a classic
> >>     application
> >>      > server >approach.
> >>      >
> >>      > The answer for VM is "it depends":
> >>      >
> >>
> >>
> >> I agree. It really depends. Certainly there are tradeoffs.
> >>
> >>      > There are several commercial P2P IP PBX solutions without any
> >>     server for
> >>      > VM or anything else. No doubt the IT organization appreciates
> >>      just > having to plug in the IP phones and GWY to the PSTN
> >>      without any > configuration ever for VM or any other PBX
> >> feature.
> >>
> >>     I don't understand. Are you saying they don't have VM, or that
> >>     they don't have a *server* for VM?
> >>
> >>
> >> I guess they don't have a  *server* for  VM.
> >>
> >>      > For public P2P SIP networks there are two more scenarios
> >>      where VM can > reside (and without ever spending one cent on VM
> >>     servers + IT systems):
> >>      >
> >>      > - In Cable and DSL service provider networks: The residential
> >>     router can
> >>      > act as a voice recorder
> >>
> >>     That is simply an example of the user having an appliance of his
> >>     own that provides VM service.
> >>
> >>      > and P2P can cover the not too frequent cases,
> >>      > where the router is not in operation, so the data is backed
> >>     up in other
> >>      > peer residential gateways (encrypted).
> >>
> >>     I guess I just need to have more info about how this would work
> >>     before I will be convinced it is feasible and trustworthy.
> >>
> >>
> >> Well, 'trustworthy' could be  considered in many angles.
> >> If it is about privacy of the message, a public key based encryption
> >> would provide acceptable privacy.
> >> If it is about reliability of the message delivery, well, a P2P based
> >> asynchronous message delivery (like VM) is most likely less reliable
> >> than a well managed server based system.
> >> However, my experience with Skype's asynchronous message delivery was
> >> not bad. Actually I don't see any significant difference between it
> >> and my cellular service provider's VM service. :-)
> >> Reliability is always a challenge for P2P, for sure. But, I believe
> >> it
> >
> >> is feasible to build a P2P system for VM acceptable for many
> >> scenarios.
> >>
> >>      > - In mobile networks: The VM can reside in quite stable peers
> >>     inside the
> >>      > wireless base station network. The peers in the base station
> >>      network > need no configuration, etc.
> >>
> >>     I don't understand. I guess that could be true if the peers are
> >>     willing to store an arbitrary amount of VM indefinitely for
> >>     anybody. Is that believable?
> >>
> >>
> >> It depends.
> >> In a very nice environment where all the peers are willing to
> >> cooperate at their best, the peers will store as much as they can.
> >> In a tough environment, the situation will be different.
> >>
> >>     This seems to translate to a model where it is assumed that
> >>     those nodes that are on most of the time will be willing to
> >>     provide VM storage for those nodes that aren't on most of the
> >> time.
> >>
> >>
> >> This is again related to reliability of P2P systems or topics like
> >> free riders and reputation.
> >> A P2P system is a community or society. To be simple, if many of the
> >> members are bad, the community won't work well. If the majority of
> >> the
> >
> >> members are good, the community will work well or reasonably.
> >>
> >>      > Add to this the conferencing capability coming from p2p
> >>      application > layer multicast, the SIP e2e control capabilities
> >>      (for such as > auto-attendant, agent workstation, etc.) and one
> >>      has to wonder why IT > networks, public VoIP networks and end
> >>      users should support the huge > cost of hand engineering,
> >>     testing, monitoring, maintaining server based
> >>      > VoIP networks. P2P self configuration is nothing less that
> >>      automation > applied to VoIP, plus the shifting of computing to
> >>     the endpoints, where
> >>      > there is an abundance of unused CPU, storage, bandwidth and
> >>     electricity.
> >>      >
> >>      > Eric Burger also notes IM changes completely the usage for VM
> >>      and may > make unnecessary to place calls on VM in the first
> >> place.
> >>
> >>     I find this more promising.
> >>
> >>
> >>
> >>
> >> In overall, are we discussing if P2P systems based VM can work? I
> >> think it can work.  Just it depends on many things.
> >> If it is not super-reliable, should we disregard it? I would say no.
> >>
> >> On the other hand, do we have to abandon client server based VM and
> >> switch to P2P system based VM? It is upto each of us.
> >> Client server based VM systems are already there.
> >> So why don't we work on P2P based VM now?
> >>
> >> Thanks.
> >>
> >> Eunsoo
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.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
>
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
>


-- 
David A. Bryan
dbryan@SIPeerior.com
+1.757.565.0101 x101
+1.757.565.0088 (fax)
www.SIPeerior.com

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 04 03:18:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzjD-000554-0t; Wed, 04 Apr 2007 03:16:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYqwO-0004sm-57; Tue, 03 Apr 2007 17:53:24 -0400
Received: from exprod6og54.obsmtp.com ([64.18.1.189])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HYqwK-0005rF-MM; Tue, 03 Apr 2007 17:53:24 -0400
Received: from source ([192.150.11.134]) by exprod6ob54.postini.com
	([64.18.5.12]) with SMTP; Tue, 03 Apr 2007 14:53:10 PDT
Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com
	[192.150.20.198] (may be forged))
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l33LqUD1021567; Tue, 3 Apr 2007 14:52:35 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	l33Lqt0c028564; Tue, 3 Apr 2007 14:52:56 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Apr 2007 14:52:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Tue, 3 Apr 2007 14:52:47 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223ADF2F@namail5.corp.adobe.com>
In-Reply-To: <4E2DC1ACE541B94A946B8D8657E372C57A907B@photon.objectworld.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Thread-Index: Acd176Ya+p6xqIGMQfSJrn6cLV80rgACgCmQAAX8woAAAZhX4AAHz3sg
References: <4E2DC1ACE541B94A946B8D8657E372C57A903F@photon.objectworld.com>
	<1bdd01c77612$7586dcd0$81238182@cis.neustar.com>
	<4E2DC1ACE541B94A946B8D8657E372C57A907B@photon.objectworld.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Michael Slavitch" <slavitch@objectworld.com>,
	"Brian Rosen" <br@brianrosen.net>, "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 03 Apr 2007 21:52:54.0858 (UTC)
	FILETIME=[6F2A6AA0:01C7763A]
X-Spam-Score: 1.4 (+)
X-Scan-Signature: b20610989b0325858c8c5a1f4b6a50a0
X-Mailman-Approved-At: Wed, 04 Apr 2007 03:16:14 -0400
Cc: sipping@ietf.org, p2prg@ietf.org, David R Oran <oran@cisco.com>,
	P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0395340612=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0395340612==
Content-class: urn:content-classes:message
Content-Type: multipart/related; type="multipart/alternative";
	boundary="----_=_NextPart_001_01C7763A.6DADE46E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7763A.6DADE46E
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C7763A.6DADE46E"


------_=_NextPart_002_01C7763A.6DADE46E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I agree with Michael here. The voice-only PBX is pathetic as an
enterprise communication and productivity platform (no presence, IM, no
integration with apps, etc.) is also exactly the opposite of what self
organizing systems provide. As for the usability of those tiny screens
and remembering the various commands...

Why not just use Skype PC clients or Skype phones instead? At least,
they are WiFi and no configuration is required that cannot be done by
the user. And they can be used on travel as well.

=20

Just think what self organizing and usability means for the maintenance
headcount and budget. Not to mention the associated IT systems.

=20

P2P SIP in the enterprise is not a PBX replacement any more that SIP is
a PSTN replacement, though many decisions makers have not given up :-)

=20

Thanks, Henry

=20

________________________________

From: Michael Slavitch [mailto:slavitch@objectworld.com]=20
Sent: Tuesday, April 03, 2007 12:58 PM
To: Brian Rosen; Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage
scenario

=20

"vendors will tell you the things you can automate about provisioning
have been automated."

=20

The vendors will tell you this because the things that they automate can
be summarized as:

=20

1.      "not much".

2.      What we automate is our proprietary stuff, sod the rest.

=20

t's things like TN assignment, and dial plans, and gateway routing, and
emergency call provisioning, and permissions, and feature enabling, etc,
etc that dominate provisioning of enterprise telephony systems.  P2P
doesn't help any of that.

=20

I strongly disagree with that.   Look at the documentation for products
from many of the major vendors, there are stacks of complex details
regarding deployment,  not very automatic at all, with many of them
depending on crufty TFTP or FTP with fixed file locations for
provisioning of endpoints.  It's horrible.

Secondly, "it doesn't help with any of that" is only true in a static
fixed universe where you provision once and go away and limit
functionality to very basic tasks.   Even in that world the number of
user change requests on a 2000 user system is on the order of .5%-1% of
all endpoints per day on today's relatively static systems, 10 to 20 per
day, and that's just basic stuff, done at gunpoint.  Routers used to
have only static routes too, and web pages were once coded by hand.  =20

=20

Regards

=20

Michael

=20

=20

=20

  <http://www.objectworld.com/>=20

=20

=20

=20

=20

Michael Slavitch             =20

Lead, Technology Initiatives

slavitch@objectworld.com

=20

=20

=20

=20

=20

From: Brian Rosen [mailto:br@brianrosen.net]=20
Sent: Tuesday, April 03, 2007 1:07 PM
To: Michael Slavitch; 'Paul Kyzivat'
Cc: 'P2PSIP Mailing List'; 'Michael Hammer (mhammer)'; 'David R Oran';
'Henry Sinnreich'; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage
scenario

=20

I think most enterprise "PBX" vendors will tell you that the things you
can automate about provisioning have been automated, and you won't get
much a win there.  It's things like TN assignment, and dial plans, and
gateway routing, and emergency call provisioning, and permissions, and
feature enabling, etc, etc that dominate provisioning of enterprise
telephony systems.  P2P doesn't help any of that.

=20

I worry, quite a bit, that perpetuating SIP UAs (the SIP client) will
perpetuate the dumb endpoint model, simply because the way they are made
now is that they are dumb endpoints.  They didn't have to be (SIP was
originally designed for smart endpoints).  If we make P2PSIP endpoints
more closely fit the smart endpoint model, then we make the peer that
serves the UAs be the smart box in the middle of the network.

=20

Brian

=20

________________________________

From: Michael Slavitch [mailto:slavitch@objectworld.com]=20
Sent: Tuesday, April 03, 2007 10:48 AM
To: Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

=20

The point I am making is  that in the enterprise the actual topological
deployments of SIP clients and servers, when implemented as software on
generic computing platforms, as well as the mechanisms that make that
deployment happen, are already very different world than the canonical
IMS/CSSIP one which  assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD),  B2BUA demarks,
network elements, and dumb fixed endpoints.  Taking a network as a whole
enterprise application software using C/S SIP proxies and UA's already
approximates something that is close to what is being called P2PSIP,
only in a manner that is highly proprietary, closed, somewhat brittle
and baroque, local, and ad-hoc, with gaping ugly holes.  P2P has the
potential to transform that.

=20

Some points I take from the previous discussion:

"that a P2P setup will be *free*"

=20

-       A P2P network may not be free, but the setup (provisioning) will
be free, and automatic.  This is a major benefit only partially achieved
in enterprise networks,  a benefit of great value to enterprises that is
underserved by vendors.  There is no benefit in requiring complex
deployments where automation can take its place.  Deployment is almost
always the biggest cost of enterprise systems dwarfing the cost of the
systems themselves.

=20

"I think this depends greatly on what expectations / contractual
guarantees the enterprise has. It's unclear to me what guarantees can be
made about a P2PSIP network will be able to make, and its unclear what
kind of infrastructure would be installed by/for someone willing to make
guarantees."

=20

-      That is why 'expectations/contractual guarantees' need to be
built into the automation that exists in the P2P overlay.
Self-calculation of such performance metrics is already there in all
enterprise devices, the difference being that while WMI/SNMP data is
merely collected a P2PSIP network can act automatically based on the
metrics within their own nodes, there is a collective 'aha' that forces
behavior change based on strict contracts, aka rules.  An SLA is easier
to maintain if the objects can react accordingly, for example a node
with degrading service can notify that it is on the decline forcing
others to take over. =20

=20

There is an old traffic engineering axiom about service guarantees: it
can be achieved through two ways: over engineering or  automation.
P2PSIP allows for automation.

=20

 David Oran wrote:

=20

"I'm not saying this can't be made to work, only that it isn't
immediately obvious that it has advantages over a classic
application/server approach."

=20

The immediately obvious advantage to me is standardized ruggedized
automation that has economies of scale and operates over multiple
domains, eliminating the need for over-engineering,  detailed fussy
provisioning,  and an army of people doing basic monitoring and
care-and-feeding.  Automation is the key, a dynamic statistical network
vs. one that is fixed and assumed deterministic will always win out over
time given a fractal operating environment.   This is being done in fits
and starts in the enterprise data center.   P2PSIP makes it much more
comprehensive.   People want the world to be predictable and
deterministic,  and C/S based systems reflect that. That is the biggest
problem P2P faces because it flies in the face of tradition.  =20

=20

Regards

=20

Michael Slavitch

=20

=20

=20

=20

=20

 <http://www.objectworld.com/>=20

=20

308 Legget Dr.=20
Ottawa Ontario=20
K2K 1Y6 Canada

=20
<http://maps.google.ca/maps?f=3Dq&hl=3Den&q=3D308+Legget+Drive+Ottawa+Ont=
ario+
K2K+1Y6&layer=3D&sll=3D45.341061,-75.904541&sspn=3D0.007119,0.023839&ie=3D=
UTF8&z
=3D18&ll=3D45.341061,-75.904541&spn=3D0.00178,0.00596&t=3Dh&om=3D1>=20

=20

Michael Slavitch             =20

Lead, Technology Initiatives

slavitch@objectworld.com

PSTN: =20

+1.888.398.9698

x225

Fax:

+1.613.599.7457

=20

Skype:      =20

 Objectworld  =20

x225

  <skype:Objectworld>=20

=20

=20

=20

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
Sent: Tuesday, April 03, 2007 8:57 AM
To: Michael Slavitch
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer);
David R Oran; p2prg@ietf.org; sipping@ietf.org; zhuxian
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario

=20

=20

=20

Michael Slavitch wrote:

> Sorry for being late into this discussion, but client-server based VM=20

> isn't truly client-server anymore in anything but the smallest or most


> monolithic of enterprise networks, in fact the reality is that most if


> not all enterprise networks contain just peers and superpeers with the


> difference being partially a marketing decision by the vendors, as you


> can charge much more for the servers, and a policy decision made
either=20

> automatically by a software deployment system or by IT staff which
wants=20

> to place supernodes with data sinks on appropriate equipment.

=20

I'm sorry, but I don't understand the point you are trying to make=20

above. You are trying to draw some sort of distinction, but I don't get=20

it. Can you try again.

=20

                Thanks,

                Paul

=20

> In a=20

> highly distributed environment there are potentially hundreds of=20

> possible data sinks for a given application, with the sink based on=20

> subnet or geographic location or balanced load, this can change
rapidly=20

> over time and does.

>=20

> In the case of the Microsoft environment such policy is administered
and=20

> published between supernodes, ie servers, by Active Directory.  It is=20

> advertised to mere peers through DNS.  There was much discussion a
while=20

> ago about building service discovery environment using DNS instead of
a=20

> P2P DHT.  It can be argued that a case study of a P2P example done
using=20

> DNS is any large Windows Server 2003 based Microsoft network with many


> servers and many more clients that also run applications themselves
and=20

> are not just dumb terminals. This is almost certainly always the case
in=20

> all enterprises. The big difference between C/S SIP and P2PSIP is=20

> automation. What is true is that the square peg in round hole of=20

> overloading DNS makes deployments clumsy and brittle within the=20

> enterprise domain and completely unmanageable and unpublishable
outside=20

> the firewall which is why the buck stops there in current enterprise=20

> networking products.

>=20

> The difference between C/S and P2P is largely policy and semantics
with=20

> the biggest difference being that the decisions and rules are highly=20

> distributed.  Apart from that they are not just friends, they are=20

> fraternal twins.

>=20

> Regards

>=20

> Michael Slavitch

>=20

> =20

>=20

>=20

> corp_2colour=20

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://www.=
o
bjectworld.com/>

>=20

> =20

>=20

>            =20

>=20

> 308 Legget Dr.

> Ottawa Ontario

> K2K 1Y6 Canada

>=20

>            =20

>=20

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://maps=
.
google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2BOnta=
rio%2
BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.007119,0.02=
3839%
26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.00178,0.00596%=
26t=3Dh%2
6om=3D1>

>=20

>            =20

>=20

> =20

>=20

> Michael Slavitch            =20

>=20

> Lead, Technology Initiatives

>=20

> slavitch@objectworld.com <mailto:slavitch@objectworld.com>

>=20

>            =20

>=20

> PSTN:=20

>=20

>            =20

>=20

> +1.888.398.9698

>=20

>            =20

>=20

> x225

>=20

> Fax:

>=20

>            =20

>=20

> +1.613.599.7457

>=20

>            =20

>=20

> =20

>=20

> Skype:     =20

>=20

>            =20

>=20

>   Objectworld=20

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%
20and%20MME.EML/>  =20

>=20

>=20

>            =20

>=20

> x225

>=20

>            =20

>=20

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,
%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%
20and%20MME.EML/>

>=20

>            =20

>=20

> =20

>=20

> =20

>=20

>=20

=20

=20

--=20

BEGIN-ANTISPAM-VOTING-LINKS

------------------------------------------------------

=20

Teach CanIt if this mail (ID 657805) is spam:

Spam:
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&m=3D2eb1fdee55=
b7&
c=3Ds

Not spam:
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&m=3D2eb1fdee55=
b7&
c=3Dn

Forget vote:
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&m=3D2eb1fdee55=
b7&
c=3Df

------------------------------------------------------

END-ANTISPAM-VOTING-LINKS

=20

________________________________

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete
this information from your system. Use, dissemination, distribution, or
reproduction of this transmission by unintended recipients is not
authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely
those of the author and may not represent those of Objectworld
Communications Corp.

________________________________


Spam
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0f=
e34
&c=3Ds>=20
Not spam
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0f=
e34
&c=3Dn>=20
Forget previous vote
<http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&m=3D5b6a6dc0f=
e34
&c=3Df>=20

________________________________

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete
this information from your system. Use, dissemination, distribution, or
reproduction of this transmission by unintended recipients is not
authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely
those of the author and may not represent those of Objectworld
Communications Corp.


------_=_NextPart_002_01C7763A.6DADE46E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns0=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PostalCode"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}
p.MSOPLAINTEXT
	{mso-style-priority:99;}
li.MSOPLAINTEXT
	{mso-style-priority:99;}
div.MSOPLAINTEXT
	{mso-style-priority:99;}
p
	{mso-style-priority:99;}
p.MSOACETATE
	{mso-style-priority:99;}
li.MSOACETATE
	{mso-style-priority:99;}
div.MSOACETATE
	{mso-style-priority:99;}
p.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
li.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
div.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
span.PLAINTEXTCHAR
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR
	{mso-style-priority:99;}
span.PLAINTEXTCHAR0
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR0
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;}
@font-face
	{font-family:Consolas;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;}
p.msolistparagraph, li.msolistparagraph, div.msolistparagraph
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
span.plaintextchar
	{font-family:Consolas;}
span.balloontextchar
	{font-family:Tahoma;}
span.plaintextchar0
	{font-family:Calibri;}
span.balloontextchar0
	{font-family:Tahoma;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:Calibri;
	color:black;}
span.EmailStyle27
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:846867197;
	mso-list-type:hybrid;
	mso-list-template-ids:-139805038 -1714783482 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1197936675;
	mso-list-type:hybrid;
	mso-list-template-ids:-2146642626 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I agree with Michael here. The =
voice-only
PBX is pathetic as an enterprise communication and productivity platform =
(no
presence, IM, no integration with apps, etc.) is also exactly the =
opposite of
what self o<st1:PersonName w:st=3D"on">rg</st1:PersonName>anizing =
systems
provide. As for the usability of those tiny screens and remembering the =
various
commands&#8230;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Why not just use Skype PC clients =
or Skype
phones instead? At least, they are WiFi and no configuration is required =
that
cannot be done by the user. And they can be used on travel as =
well.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Just think what self =
o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>anizing and usability means for the =
maintenance
headcount and budget. Not to mention the associated IT =
systems.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>P2P SIP in the enterprise is not a =
PBX
replacement any more that SIP is a PSTN replacement, though many =
decisions
makers have not given up </span></font><font size=3D2 color=3Dnavy =
face=3DWingdings><span
style=3D'font-size:10.0pt;font-family:Wingdings;color:navy'>J</span></fon=
t><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, =
Henry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Slavitch
[mailto:slavitch@objectworld.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007
12:58 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">Brian
 Rosen</st1:PersonName>; Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; Henry Sinnreich; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>&#8220;</span></font><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>vendors will tell you the things you can automate about
provisioning have been automated.</span></font><font color=3Dblack><span
style=3D'color:black'>&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>The vendors will tell you this =
because the
things that they automate can be summarized =
as:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l1 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3Dblack face=3DCalibri><span =
style=3D'font-size:11.0pt;color:black'><span
style=3D'mso-list:Ignore'>1.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
color=3Dblack><span style=3D'color:black'>&#8220;not =
much&#8221;.<o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l1 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3Dblack face=3DCalibri><span =
style=3D'font-size:11.0pt;color:black'><span
style=3D'mso-list:Ignore'>2.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
color=3Dblack><span style=3D'color:black'>What we automate is our =
proprietary
stuff, sod the rest.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>t&#8217;s things like TN =
assignment, and
dial plans, and gateway routing, and eme<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ency
call provisioning, and permissions, and feature enabling, etc, etc that
dominate provisioning of enterprise telephony systems. &nbsp;P2P =
doesn&#8217;t
help any of that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>I strongly disagree with that. =
&nbsp;&nbsp;Look
at the documentation for products from many of the major vendors, there =
are
stacks of complex details regarding deployment,&nbsp; not very automatic =
at
all, with many of them depending on crufty TFTP or FTP with fixed file
locations for provisioning of endpoints.&nbsp; It&#8217;s =
horrible.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Secondly, &#8220;it doesn&#8217;t =
help
with any of that&#8221; is only true in a static fixed universe where =
you
provision once and go away and limit functionality to very basic =
tasks.&nbsp; &nbsp;Even
in that world the number of user change requests on a 2000 user system =
is on
the order of .5%-1% of all endpoints per day on today&#8217;s relatively =
static
systems, 10 to 20 per day, and that&#8217;s just basic stuff, done at =
gunpoint.&nbsp;
Routers used to have only static routes too, and web pages were once =
coded by
hand.&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Regards<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Michael<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<div>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:6.65in;
  border:none;border-top:solid windowtext =
1.0pt;background:white;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
  =
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><a
  href=3D"http://www.objectworld.com/" title=3D"Objectworld =
Communications"><font
  color=3Dblack><span style=3D'color:black;text-decoration:none'><img =
border=3D0
  width=3D237 height=3D42 id=3D"Picture_x005f_x005f_x005f_x0020_1"
  src=3D"cid:image001.jpg@01C77610.81C1E230" =
alt=3D"corp_2colour"></span></font></a><font
  color=3Dblack><span =
style=3D'color:black'><o:p></o:p></span></font></span></font></p>
  <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
  =
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    style=3D'font-size:11.0pt;color:black'>Michael =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    style=3D'font-size:11.0pt;color:black'>Lead, Technology =
Initiatives<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    =
style=3D'font-size:11.0pt;color:black'>slavitch@objectworld.com<o:p></o:p=
></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black;letter-spacing:-.5pt'><o:p>&nbsp;</=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
<st1:PersonName
w:st=3D"on">Brian Rosen</st1:PersonName> [mailto:br@brianrosen.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007 1:07
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Michael Slavitch; =
'Paul
Kyzivat'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> 'P2PSIP Mailing =
List';
'Michael Hammer (mhammer)'; 'David R Oran'; 'Henry Sinnreich'; =
p2p<st1:PersonName
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>;
sipping@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario<o:p></o:p></span></font></p>

</div>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I think most enterprise =
&#8220;PBX&#8221;
vendors will tell you that the things you can automate about =
provisioning have
been automated, and you won&#8217;t get much a win there. =
&nbsp;It&#8217;s
things like TN assignment, and dial plans, and gateway routing, and =
eme<st1:PersonName
w:st=3D"on">rg</st1:PersonName>ency call provisioning, and permissions, =
and
feature enabling, etc, etc that dominate provisioning of enterprise =
telephony
systems. &nbsp;P2P doesn&#8217;t help any of =
that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I worry, quite a bit, that =
perpetuating
SIP UAs (the SIP client) will perpetuate the dumb endpoint model, simply
because the way they are made now is that they are dumb endpoints. =
&nbsp;They
didn&#8217;t have to be (SIP was originally designed for smart =
endpoints).&nbsp;
If we make P2PSIP endpoints more closely fit the smart endpoint model, =
then we
make the peer that serves the UAs be the smart box in the middle of the
network.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Brian<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Slavitch
[mailto:slavitch@objectworld.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007 10:48
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; Henry Sinnreich; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
point I am making is&nbsp; that in the enterprise the actual topological
deployments of SIP clients and servers, <i><span =
style=3D'font-style:italic'>when
implemented as software on generic computing platforms</span></i>, as =
well as
the <i><span style=3D'font-style:italic'>mechanisms that make that =
deployment
happen</span></i>, are already very different world than the canonical
IMS/CSSIP one which &nbsp;assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD), &nbsp;B2BUA demarks,
network elements, and dumb fixed endpoints.&nbsp; Taking a network as a =
whole
enterprise application software using C/S SIP proxies and UA&#8217;s =
<i><span
style=3D'font-style:italic'>already</span></i> approximates something =
that is
close to what is being called P2PSIP, only in a manner that is highly
proprietary, closed, somewhat brittle and baroque, local, and ad-hoc, =
with
gaping ugly holes.&nbsp; P2P has the potential to transform =
that.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'>Some points I take from the previous =
discussion:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;that
a P2P setup will be *free*&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-list:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>&nbsp;A P2P network may not =
be
free, but the setup (provisioning) will be free, and automatic.&nbsp; =
This is a
major benefit only partially achieved in enterprise networks,&nbsp; a =
benefit of
great value to enterprises that is underserved by vendors.&nbsp; There =
is no
benefit in requiring complex deployments where automation can take its =
place.&nbsp;
Deployment is almost always the biggest cost of enterprise systems =
dwarfing the
cost of the systems themselves.<o:p></o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I
think this depends greatly on what expectations / contractual guarantees =
the
enterprise has. It&#8217;s unclear to me what guarantees can be made =
about a
P2PSIP network will be able to make, and its unclear what kind of
infrastructure would be installed by/for someone willing to make =
guarantees.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-list:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>That is why =
&#8216;expectations/contractual
guarantees&#8217; need to be built into the automation that exists in =
the P2P
overlay.&nbsp; Self-calculation of such performance metrics is already =
there in
all enterprise devices, the difference being that while WMI/SNMP data is =
merely
collected a P2PSIP network can act automatically based on the metrics =
within
their own nodes, there is a collective &#8216;aha&#8217; that forces =
behavior
change based on strict contracts, aka rules.&nbsp; An <st1:place =
w:st=3D"on">SLA</st1:place>
is easier to maintain if the objects can react accordingly, for example =
a node
with degrading service can notify that it is on the decline forcing =
others to
take over.&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>There
is an old traffic engineering axiom about service guarantees: it can be =
achieved
through two ways: over engineering or &nbsp;automation.&nbsp; P2PSIP =
allows for
automation.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;David
Oran wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I'm
not saying this can't be made to work, only that it isn't immediately =
obvious
that it has advantages over a classic application/server =
approach.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
immediately obvious advantage to me is standardized ruggedized =
automation that
has economies of scale and operates over multiple domains, eliminating =
the need
for over-engineering,&nbsp; detailed fussy provisioning,&nbsp; and an =
army of
people doing basic monitoring and care-and-feeding.&nbsp; Automation is =
the
key, a dynamic statistical network vs. one that is fixed and assumed
deterministic will always win out over time given a fractal operating
environment.&nbsp;&nbsp; This is being done in fits and starts in the
enterprise data center.&nbsp;&nbsp; P2PSIP makes it much more =
comprehensive.&nbsp;
&nbsp;People want the world to be predictable and deterministic,&nbsp; =
and C/S
based systems reflect that. That is the biggest problem P2P faces =
because it
flies in the face of tradition. =
&nbsp;&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:6.65in;
  border:none;border-top:solid windowtext =
1.0pt;background:white;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><a
  href=3D"http://www.objectworld.com/" title=3D"Objectworld =
Communications"><font
  color=3Dblack><span =
style=3D'color:windowtext;text-decoration:none'><img
  border=3D0 width=3D237 height=3D42
  id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x0020_1"
  src=3D"cid:image001.jpg@01C77610.81C1E230" =
alt=3D"corp_2colour"></span></font></a><o:p></o:p></span></font></p>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><st1:Street w:st=3D"on"><st1:address =
w:st=3D"on"><font size=3D2
    face=3DCalibri><span style=3D'font-size:11.0pt'>308 Legget =
Dr</span></font></st1:address></st1:Street>.
  <br>
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State w:st=3D"on">Ontario</st1:State>
   <br>
<st1:PostalCode w:st=3D"on">K2K 1Y6</st1:PostalCode> <st1:country-region =
w:st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a
  =
href=3D"http://maps.google.ca/maps?f=3Dq&amp;hl=3Den&amp;q=3D308+Legget+D=
rive+Ottawa+Ontario+K2K+1Y6&amp;layer=3D&amp;sll=3D45.341061,-75.904541&a=
mp;sspn=3D0.007119,0.023839&amp;ie=3DUTF8&amp;z=3D18&amp;ll=3D45.341061,-=
75.904541&amp;spn=3D0.00178,0.00596&amp;t=3Dh&amp;om=3D1"
  title=3D"308 Legget Drive Ottawa Ontario K2K 1Y6"><font =
color=3Dblack><span
  style=3D'color:windowtext;text-decoration:none'><img border=3D0 =
width=3D29
  height=3D29 =
id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x0020_6"
  =
src=3D"cid:image002.jpg@01C77610.81C1E230"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
    =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Lead,
    Technology Initiatives<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>slavitch@objectworld.com<o:p></o:p></span></fo=
nt></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0 width=3D204
   style=3D'width:152.85pt;border-collapse:collapse'>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>PSTN:&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.888.398.9698<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Fax:<o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.613.599.7457<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<a
    href=3D"Skype:Objectworld">Objectworld</a>&nbsp;&nbsp; =
<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a =
href=3D"skype:Objectworld"
  title=3DObjectworld><font color=3Dblack><span =
style=3D'color:windowtext;text-decoration:
  none'><img border=3D0 width=3D26 height=3D26
  id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x0020_3"
  =
src=3D"cid:image003.jpg@01C77610.81C1E230"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>-----Original
Message-----<br>
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] <br>
Sent: Tuesday, April 03, 2007 8:57 AM<br>
To: Michael Slavitch<br>
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); =
David R
Oran; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>;
zhuxian<br>
Subject: Re: [P2P<st1:PersonName w:st=3D"on">rg</st1:PersonName>] RE: =
[Sipping]
Simple SIP usage scenario<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Sorry for being late into this discussion, but client-server based VM =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
isn't truly client-server anymore in anything but the smallest or most =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
monolithic of enterprise networks, in fact the reality is that most if =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
not all enterprise networks contain just peers and superpeers with the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
difference being partially a marketing decision by the vendors, as you =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
can cha<st1:PersonName w:st=3D"on">rg</st1:PersonName>e much more for =
the servers,
and a policy decision made either <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automatically by a software deployment system or by IT staff which wants =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
to place supernodes with data sinks on appropriate =
equipment.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>I'm
sorry, but I don't understand the point you are trying to make =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>above.
You are trying to draw some sort of distinction, but I don't get =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>it.
Can you try again.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Paul<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In a <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
highly distributed environment there are potentially hundreds of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
possible data sinks for a given application, with the sink based on =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
subnet or geographic location or balanced load, this can change rapidly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
over time and does.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In the case of the Microsoft environment such policy is administered and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
published between supernodes, ie servers, by Active Directory.&nbsp; It =
is <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
advertised to mere peers through DNS.&nbsp; There was much discussion a =
while <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
ago about building service discovery environment using DNS instead of a =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
P2P DHT.&nbsp; It can be a<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ued that
a case study of a P2P example done using <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
DNS is any la<st1:PersonName w:st=3D"on">rg</st1:PersonName>e Windows =
Server 2003
based Microsoft network with many <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
servers and many more clients that also run applications themselves and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
are not just dumb terminals. This is almost certainly always the case in =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
all enterprises. The big difference between C/S SIP and P2PSIP is =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automation. What is true is that the square peg in round hole of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
overloading DNS makes deployments clumsy and brittle within the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
enterprise domain and completely unmanageable and unpublishable outside =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the firewall which is why the buck stops there in current enterprise =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
networking products.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
The difference between C/S and P2P is la<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ely
policy and semantics with <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the biggest difference being that the decisions and rules are highly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
distributed.&nbsp; Apart from that they are not just friends, they are =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
fraternal twins.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
corp_2colour <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://w=
ww.objectworld.com/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:Street w:st=3D"on"><st1:address w:st=3D"on">308 Legget =
Dr</st1:address></st1:Street>.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State =
w:st=3D"on">Ontario</st1:State></st1:place><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
K2K 1Y6 <st1:place w:st=3D"on"><st1:country-region =
w:st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></span></fo=
nt></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://m=
aps.google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2B=
Ontario%2BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.00=
7119,0.023839%26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.=
00178,0.00596%26t=3Dh%26om=3D1&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Lead, Technology Initiatives<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
slavitch@objectworld.com =
&lt;mailto:slavitch@objectworld.com&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
PSTN: <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.888.398.9698<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Fax:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.613.599.7457<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;&nbsp;
Objectworld <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>--
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>BEGIN-ANTISPAM-VOTING-LINKS<o:p></o:p></span><=
/font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Teach
CanIt if this mail (ID 657805) is spam:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Spam:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Ds<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Not
spam:&nbsp;&nbsp;&nbsp;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Dn<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Fo<st1:PersonName
w:st=3D"on">rg</st1:PersonName>et vote: =
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Df<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>END-ANTISPAM-VOTING-LINKS<o:p></o:p></span></f=
ont></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>This
transmission (including any attachments) may contain confidential =
information,
privileged material (including material protected by the =
solicitor-client 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 immediately reply =
to the
sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended =
recipients is
not authorized and may be unlawful.<o:p></o:p></span></font></p>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>Any views,
opinions and content presented in this e-mail are solely those of the =
author
and may not represent those of Objectworld Communications =
Corp.<o:p></o:p></span></font></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D4
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:13.5pt;font-family:
"Times New Roman";color:black;background:white'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><font size=3D4 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:13.5pt;font-family:"Times New =
Roman";color:black;background:
white'><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Ds">Spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Dn">Not
spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Df">Forget
previous vote</a></span></font><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

</div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>This
transmission (including any attachments) may contain confidential =
information,
privileged material (including material protected by the =
solicitor-client 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 immediately reply =
to the
sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended =
recipients is
not authorized and may be unlawful.<o:p></o:p></span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>Any
views, opinions and content presented in this e-mail are solely those of =
the
author and may not represent those of Objectworld Communications =
Corp.<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_002_01C7763A.6DADE46E--

------_=_NextPart_001_01C7763A.6DADE46E
Content-Type: image/jpeg;
	name="image001.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image001.jpg@01C77610.81C1E230>
Content-Description: image001.jpg
Content-Location: image001.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6
+0EbNruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHExlWYK4wpGMhue
leLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9clnAj17UWQKd3+kNjPb+tN/s+6bR
21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHN
R/8AAlv8a9P8NWv/AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1U9W1W00TSrjU76Qx
29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GFE6eqnPpzXoHzp19FZniHXIPDmhXOr3Mc
ksNsoZkjxuOSBxn61ieHPiLpniHVV0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc
3dpDNClvcvbMJQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq39uaT
FqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jHGM/M3Psa2tC1uy8RaPb6
rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFreaPqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+
w3Vj5hYeRdJskXBxyKANGisRvFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6v
RZpDhd+8n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA2fxg0W4n
Tz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumtpPNA+Zh3GD0oA26KiuJltraW
dgSsSFyB1IAzXE6N8WtG1a7tIZNP1GxivZPKt7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8
kKcE9M5IrD1H4h6Hpltazzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+
jtPI2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1LvgEhv5V4sNKivt
c+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m1u7X7PGJ4vL+zRoFMe3J3YHY5x9a
1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej
3PAy/C1qWJTmmkt+vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLNd74l0OHxJ4evNInk
MSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZrKOGLYFXGMse5wf/AK9ekfLl74p/8k31
j/rmv/oa1xfhqXUW+IHhl/E0MVuf7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5
C4YHp+Fc5oHgDVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu11WK/
m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYHA9OBQByXjWXV4fi9oj6F
b29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRqZ0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xa
WxgBkg8zqWycHjo1dFoNtq1ppaQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs
9CsdDjg8OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/gK2/CHhuL
wn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ceFpvFmlWtlDdJbNBdpcFnUsCF
B44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1
Lx54N/4TPT7K2FwsDWt0sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/
AJoeP+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6Wv+oH+7/SvnjT
59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrzofC+5XwYNFXUoReQ6l9vt7nyzhD6
YznpmgD0RFCIqDooArz34S/e8Uf9hmWvQk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2
gYsC2SMnOOOOKAO41X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689GHQ1lT+EdCuQBLYK2
CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgBumKworm4ESATyYCj+M0j3M5KZnk4bj5z
Xjey97c+4WK/dr3e39bG/ChiiCEjIz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5
OW5+c+lCpbu45YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckxNyf9
9q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRR
QAUUUUAFFFFAH//Z

------_=_NextPart_001_01C7763A.6DADE46E
Content-Type: image/jpeg;
	name="image002.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image002.jpg@01C77610.81C1E230>
Content-Description: image002.jpg
Content-Location: image002.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAdAB0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD0/VNW
WCU20cnllQPMkAyVz0A9/wCVUylrNEHWKOZjysk+XP5nmua1W8kXU7pZDg+e/wCW7A/TFPs9UmmU
Wquq8fK3cf4168cNywTR5EsTzTakdDFqT2M20l2j6mMknI7lc8j6dK6GORJY1kjYMrDII7ivOruS
eB0lklDljgHNdh4ald9Fi39iwX/dycfpiufFUVGKmjowtZyk4M5/xhoUzXDX9qhbf/rFA5z6j1rj
o5pILhGIHytzzivZnRZFKsAQazptCspX3NGM/SnQx0qceWSuia+AjUnzxdmef2ttd61f5XcIQcBs
cAe3qa9J0+1W0s44VGAqgAegotrC3th8ic+tWq56+IlWavokdFDDxop21b6n/9k=

------_=_NextPart_001_01C7763A.6DADE46E
Content-Type: image/jpeg;
	name="image003.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image003.jpg@01C77610.81C1E230>
Content-Description: image003.jpg
Content-Location: image003.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAaABoDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1Ga7l
kZ2SdokV2VQgXJwcEnIPcHpVSTW7uHqYHA7bCCfxz/Skuiv9qSwFtitMoA/3gMn8yab/AGWls8lx
qTBbeE5HP+s/z6V4051nJ8j2ervov+AYty6GrpuqQ6lGxQFJE++hPT/EVdrjtEuvN8S+ZEuxJjIS
Pbkj+Qrsa7MDiHXpcz3Tt6lwlzIyNa0hr7E8GPNAwy5xvHb8axbu31G6jSO6W5ZYRwPKbH1JAwTX
Y0VFfAQqyck7X37MUqaZx2k6cf7QheCQMUcFipyFAPOfTjj8a7GiitcLhY4eLinuOMeVH//Z

------_=_NextPart_001_01C7763A.6DADE46E--


--===============0395340612==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0395340612==--




From sipping-bounces@ietf.org Wed Apr 04 03:18:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzj6-00050D-E8; Wed, 04 Apr 2007 03:16:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HYMe9-0001Jv-Er
	for sipping@ietf.org; Mon, 02 Apr 2007 09:32:33 -0400
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYMe7-0005LC-0V
	for sipping@ietf.org; Mon, 02 Apr 2007 09:32:33 -0400
Received: by ug-out-1314.google.com with SMTP id 72so1461317ugd
	for <sipping@ietf.org>; Mon, 02 Apr 2007 06:32:29 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=WfK1xBlUD9udSdbnbz299lIwb/lpdECIs3xIWBIBW/t7oxC2Gv9V5n8IJiWf2imAuxvbNugtqBhNlsCtpFAtELnLxTwegmrM8oykMT20oxYji8fE8xosj1N6P7Nc9CoPOKEPIP3E+StWPM9bSSAsDowYLkbez5SdVg6Lz7wvH34=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=a1TjbeIG7aTLhyoE+RG1kLGkJ1ItJW2kQ11VjfUuBRkIvZNjpHg5CUZCNAzsfT04NGFHt/GsiVOZcX18eWiIrElNPSGq6Ir+zXcA7ZHksqzGibC2eTXTzKhIjrm8JyLxFukeirj8iPE4cvF3pApvQyD1AMrR9sA5drqe0tT5gX8=
Received: by 10.82.154.2 with SMTP id b2mr1461004bue.1175520748792;
	Mon, 02 Apr 2007 06:32:28 -0700 (PDT)
Received: by 10.82.127.17 with HTTP; Mon, 2 Apr 2007 06:32:28 -0700 (PDT)
Message-ID: <4d4304a00704020632r71315532s1be1df106c4f426a@mail.gmail.com>
Date: Mon, 2 Apr 2007 09:32:28 -0400
From: "David A. Bryan" <dbryan@sipeerior.com>
To: "Jeroen van Bemmel" <jbemmel@zonnet.nl>
Subject: Re: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
In-Reply-To: <00b201c7748e$33067df0$0601a8c0@BEMBUSTER>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <24CCCC428EFEA2469BF046DB3C7A8D225274F4@namail5.corp.adobe.com>
	<EC0E1E0E-2E83-4674-BAC0-78CB94F0BD43@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADECA@namail5.corp.adobe.com>
	<4FF5FA52-1B38-4964-87AE-72300CE89A1F@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADED9@namail5.corp.adobe.com>
	<460D4825.2090800@cisco.com>
	<7b683f3f0703301556j95f2c10sf12d666994dedf6f@mail.gmail.com>
	<460D9D9C.1040304@cisco.com>
	<24CCCC428EFEA2469BF046DB3C7A8D223ADF22@namail5.corp.adobe.com>
	<00b201c7748e$33067df0$0601a8c0@BEMBUSTER>
X-Google-Sender-Auth: d7b6568599097134
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3f3e54d3c03ed638c06aa9fa6861237e
X-Mailman-Approved-At: Wed, 04 Apr 2007 03:16:13 -0400
Cc: P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>,
	Paul Kyzivat <pkyzivat@cisco.com>, David R Oran <oran@cisco.com>,
	p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I don't think Henry was saying only there -- just that that might be
another deployment we haven't thought about. I am pretty sure he is
very much in favor of having them in wireless devices.

Personally, I think that putting P2PSIP peers in edge devices would be
a good place to do it for home wireline users -- as Henry points out,
it avoids the NAT issue, among other things. Of course I would also
want to see them in UAs, softphones, wireless devices, maybe even
consumer devices, etc. (and I am sure Henry wants to see P2PSIP peers
everywhere too!)

David

On 4/1/07, Jeroen van Bemmel <jbemmel@zonnet.nl> wrote:
> Henry,
>
> Aren't you confusing "usage scenarios" with "deployment scenarios" here? Why
> restrict P2P SIP to only certain types of devices? And if you insist on
> that, why not mobile devices?
>
> Regards,
> Jeroen
>
> Henry Sinnreich wrote:
> > Paul,
> >
> >> I more or less agree with the final conclusion below.
> >
> > This is good starting point to discuss some usage scenarios.
> >
> > Putting on my former hat as an employee for a carrier, I cannot
> > overlook the following:
> >
> > P2P SIP implemented correctly in the residential access box or cable
> > set-top box indeed is a good or better replacement for the entire VoIP
> > network infrastructure (cost, operations, new services, etc).
> > Integrated access devices for the enterprise can probably play a
> > similar role, not to mention existing P2P PBX products (please refer
> > to all the advantages of P2P that need not repeated here).
> >
> > What do people think of these three usage scenarios for P2P SIP:
> > - SIP peer in the DSL access device,
> > - SIP peer in the cable access device,
> > - SIP peer in enterprise network integrated access device (IAD).
> >
> > Note that these examples imply very low churn for the peers and add
> > the data retention resilience of P2P (geographic diversity is native
> > and mobile, etc.). Incidentally, NAT traversal may also not be a
> > problem, or at least an easier problem.
> >
> > What do you all think?
> >
> > I have taken the liberty to copy the P2P SIP list, since the low churn
> > scenarios are of interest for the DHT selection. Or just pick the same
> > DHT for all scenarios anyway? I don't think so.
> >
> > Thanks, Henry
> >
> >
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: Friday, March 30, 2007 6:31 PM
> > To: Eunsoo Shim
> > Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
> > p2prg@ietf.org; sipping@ietf.org; zhuxian
> > Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
> >
> > I more or less agree with the final conclusion below.
> >
> > My main point here is that P2P and C/S need not be enemies. Nor is a
> > total C/S system necessarily evil. What is most evil is *bundling* of
> > services that prevents freedom of choice.
> >
> > I think I would be quite happy with a SP that provides a
> > registrar/proxy
> >
> > and allows me to provide all other features as I see fit - by taking
> > them ala carte from the SP, or subscribing to them from one or more
> > other SPs, or by providing them myself via appliances I own. If that
> > registrar/proxy was replaced by a P2P sip community, the differences,
> > if
> >
> > any, would hopefully be more a function of the implementation and the
> > business models of those involved than the architecture.
> >
> > (I gather the general assumption is that a P2P setup will be *free*.
> > But
> >
> > I have a hard time believing that. If most of the usage is by mobile
> > devices that can't be peers, then somebody will have to pay for enough
> > peers to support them. If it isn't free, then how is it better than a
> > well engineered C/S system?)
> >
> > So I think the key thing here is that some features will require
> > getting
> >
> > some help from another node. There ought to be the option to pick a
> > different source for each helper you require, and an ability for it
> > all to play together.
> >
> > Paul
> >
> > Eunsoo Shim wrote:
> >> Please see my inline comment.
> >>
> >> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com
> >> <mailto:pkyzivat@cisco.com>> wrote:
> >>
> >>
> >>
> >>     Henry Sinnreich wrote:
> >>      > David Oran wrote (with regard to voice mail):
> >>      >
> >>      >> I'm not saying this can't be made to work, only that it isn't
> >>      > immediately >obvious that it has advantages over a classic
> >>     application
> >>      > server >approach.
> >>      >
> >>      > The answer for VM is "it depends":
> >>      >
> >>
> >>
> >> I agree. It really depends. Certainly there are tradeoffs.
> >>
> >>      > There are several commercial P2P IP PBX solutions without any
> >>     server for
> >>      > VM or anything else. No doubt the IT organization appreciates
> >>      just > having to plug in the IP phones and GWY to the PSTN
> >>      without any > configuration ever for VM or any other PBX
> >> feature.
> >>
> >>     I don't understand. Are you saying they don't have VM, or that
> >>     they don't have a *server* for VM?
> >>
> >>
> >> I guess they don't have a  *server* for  VM.
> >>
> >>      > For public P2P SIP networks there are two more scenarios
> >>      where VM can > reside (and without ever spending one cent on VM
> >>     servers + IT systems):
> >>      >
> >>      > - In Cable and DSL service provider networks: The residential
> >>     router can
> >>      > act as a voice recorder
> >>
> >>     That is simply an example of the user having an appliance of his
> >>     own that provides VM service.
> >>
> >>      > and P2P can cover the not too frequent cases,
> >>      > where the router is not in operation, so the data is backed
> >>     up in other
> >>      > peer residential gateways (encrypted).
> >>
> >>     I guess I just need to have more info about how this would work
> >>     before I will be convinced it is feasible and trustworthy.
> >>
> >>
> >> Well, 'trustworthy' could be  considered in many angles.
> >> If it is about privacy of the message, a public key based encryption
> >> would provide acceptable privacy.
> >> If it is about reliability of the message delivery, well, a P2P based
> >> asynchronous message delivery (like VM) is most likely less reliable
> >> than a well managed server based system.
> >> However, my experience with Skype's asynchronous message delivery was
> >> not bad. Actually I don't see any significant difference between it
> >> and my cellular service provider's VM service. :-)
> >> Reliability is always a challenge for P2P, for sure. But, I believe
> >> it
> >
> >> is feasible to build a P2P system for VM acceptable for many
> >> scenarios.
> >>
> >>      > - In mobile networks: The VM can reside in quite stable peers
> >>     inside the
> >>      > wireless base station network. The peers in the base station
> >>      network > need no configuration, etc.
> >>
> >>     I don't understand. I guess that could be true if the peers are
> >>     willing to store an arbitrary amount of VM indefinitely for
> >>     anybody. Is that believable?
> >>
> >>
> >> It depends.
> >> In a very nice environment where all the peers are willing to
> >> cooperate at their best, the peers will store as much as they can.
> >> In a tough environment, the situation will be different.
> >>
> >>     This seems to translate to a model where it is assumed that
> >>     those nodes that are on most of the time will be willing to
> >>     provide VM storage for those nodes that aren't on most of the
> >> time.
> >>
> >>
> >> This is again related to reliability of P2P systems or topics like
> >> free riders and reputation.
> >> A P2P system is a community or society. To be simple, if many of the
> >> members are bad, the community won't work well. If the majority of
> >> the
> >
> >> members are good, the community will work well or reasonably.
> >>
> >>      > Add to this the conferencing capability coming from p2p
> >>      application > layer multicast, the SIP e2e control capabilities
> >>      (for such as > auto-attendant, agent workstation, etc.) and one
> >>      has to wonder why IT > networks, public VoIP networks and end
> >>      users should support the huge > cost of hand engineering,
> >>     testing, monitoring, maintaining server based
> >>      > VoIP networks. P2P self configuration is nothing less that
> >>      automation > applied to VoIP, plus the shifting of computing to
> >>     the endpoints, where
> >>      > there is an abundance of unused CPU, storage, bandwidth and
> >>     electricity.
> >>      >
> >>      > Eric Burger also notes IM changes completely the usage for VM
> >>      and may > make unnecessary to place calls on VM in the first
> >> place.
> >>
> >>     I find this more promising.
> >>
> >>
> >>
> >>
> >> In overall, are we discussing if P2P systems based VM can work? I
> >> think it can work.  Just it depends on many things.
> >> If it is not super-reliable, should we disregard it? I would say no.
> >>
> >> On the other hand, do we have to abandon client server based VM and
> >> switch to P2P system based VM? It is upto each of us.
> >> Client server based VM systems are already there.
> >> So why don't we work on P2P based VM now?
> >>
> >> Thanks.
> >>
> >> Eunsoo
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.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
>
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
>


-- 
David A. Bryan
dbryan@SIPeerior.com
+1.757.565.0101 x101
+1.757.565.0088 (fax)
www.SIPeerior.com

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 04 03:18:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzj9-00054I-Qw; Wed, 04 Apr 2007 03:16:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYmTC-0000Ch-3l; Tue, 03 Apr 2007 13:06:58 -0400
Received: from ebru.winwebhosting.com ([74.52.236.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYmT7-0005gr-G6; Tue, 03 Apr 2007 13:06:58 -0400
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROSENLT40xp)
	by ebru.winwebhosting.com with esmtpa (Exim 4.63)
	(envelope-from <br@brianrosen.net>)
	id 1HYmSs-0007B4-Hs; Tue, 03 Apr 2007 12:06:43 -0500
From: "Brian Rosen" <br@brianrosen.net>
To: "'Michael Slavitch'" <slavitch@objectworld.com>,
	"'Paul Kyzivat'" <pkyzivat@cisco.com>
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Tue, 3 Apr 2007 13:06:38 -0400
Message-ID: <1bdd01c77612$7586dcd0$81238182@cis.neustar.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <4E2DC1ACE541B94A946B8D8657E372C57A903F@photon.objectworld.com>
Thread-Index: Acd176Ya+p6xqIGMQfSJrn6cLV80rgACgCmQAAX8woA=
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 485c16ccf4ca6ef309699ad6279bf354
X-Mailman-Approved-At: Wed, 04 Apr 2007 03:16:14 -0400
Cc: 'P2PSIP Mailing List' <p2psip@ietf.org>,
	"'Michael Hammer \(mhammer\)'" <mhammer@cisco.com>,
	'David R Oran' <oran@cisco.com>, p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0026181625=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0026181625==
Content-Type: multipart/related;
	boundary="----=_NextPart_000_1BDE_01C775F0.EE753CD0"

This is a multi-part message in MIME format.

------=_NextPart_000_1BDE_01C775F0.EE753CD0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_1BDF_01C775F0.EE82F870"


------=_NextPart_001_1BDF_01C775F0.EE82F870
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I think most enterprise "PBX" vendors will tell you that the things you can
automate about provisioning have been automated, and you won't get much a
win there.  It's things like TN assignment, and dial plans, and gateway
routing, and emergency call provisioning, and permissions, and feature
enabling, etc, etc that dominate provisioning of enterprise telephony
systems.  P2P doesn't help any of that.

 

I worry, quite a bit, that perpetuating SIP UAs (the SIP client) will
perpetuate the dumb endpoint model, simply because the way they are made now
is that they are dumb endpoints.  They didn't have to be (SIP was originally
designed for smart endpoints).  If we make P2PSIP endpoints more closely fit
the smart endpoint model, then we make the peer that serves the UAs be the
smart box in the middle of the network.

 

Brian

 

  _____  

From: Michael Slavitch [mailto:slavitch@objectworld.com] 
Sent: Tuesday, April 03, 2007 10:48 AM
To: Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

The point I am making is  that in the enterprise the actual topological
deployments of SIP clients and servers, when implemented as software on
generic computing platforms, as well as the mechanisms that make that
deployment happen, are already very different world than the canonical
IMS/CSSIP one which  assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD),  B2BUA demarks, network
elements, and dumb fixed endpoints.  Taking a network as a whole enterprise
application software using C/S SIP proxies and UA's already approximates
something that is close to what is being called P2PSIP, only in a manner
that is highly proprietary, closed, somewhat brittle and baroque, local, and
ad-hoc, with gaping ugly holes.  P2P has the potential to transform that.

 

Some points I take from the previous discussion:

"that a P2P setup will be *free*"

 

-       A P2P network may not be free, but the setup (provisioning) will be
free, and automatic.  This is a major benefit only partially achieved in
enterprise networks,  a benefit of great value to enterprises that is
underserved by vendors.  There is no benefit in requiring complex
deployments where automation can take its place.  Deployment is almost
always the biggest cost of enterprise systems dwarfing the cost of the
systems themselves.

 

"I think this depends greatly on what expectations / contractual guarantees
the enterprise has. It's unclear to me what guarantees can be made about a
P2PSIP network will be able to make, and its unclear what kind of
infrastructure would be installed by/for someone willing to make
guarantees."

 

-      That is why 'expectations/contractual guarantees' need to be built
into the automation that exists in the P2P overlay.  Self-calculation of
such performance metrics is already there in all enterprise devices, the
difference being that while WMI/SNMP data is merely collected a P2PSIP
network can act automatically based on the metrics within their own nodes,
there is a collective 'aha' that forces behavior change based on strict
contracts, aka rules.  An SLA is easier to maintain if the objects can react
accordingly, for example a node with degrading service can notify that it is
on the decline forcing others to take over.  

 

There is an old traffic engineering axiom about service guarantees: it can
be achieved through two ways: over engineering or  automation.  P2PSIP
allows for automation.

 

 David Oran wrote:

 

"I'm not saying this can't be made to work, only that it isn't immediately
obvious that it has advantages over a classic application/server approach."

 

The immediately obvious advantage to me is standardized ruggedized
automation that has economies of scale and operates over multiple domains,
eliminating the need for over-engineering,  detailed fussy provisioning,
and an army of people doing basic monitoring and care-and-feeding.
Automation is the key, a dynamic statistical network vs. one that is fixed
and assumed deterministic will always win out over time given a fractal
operating environment.   This is being done in fits and starts in the
enterprise data center.   P2PSIP makes it much more comprehensive.   People
want the world to be predictable and deterministic,  and C/S based systems
reflect that. That is the biggest problem P2P faces because it flies in the
face of tradition.   

 

Regards

 

Michael Slavitch

 

 

 

 


 


 <http://www.objectworld.com/> corp_2colour

 

308 Legget Dr. 
Ottawa Ontario 
K2K 1Y6 Canada

 
<http://maps.google.ca/maps?f=q&hl=en&q=308+Legget+Drive+Ottawa+Ontario+K2K+
1Y6&layer=&sll=45.341061,-75.904541&sspn=0.007119,0.023839&ie=UTF8&z=18&ll=4
5.341061,-75.904541&spn=0.00178,0.00596&t=h&om=1> 

 



Michael Slavitch              


Lead, Technology Initiatives


slavitch@objectworld.com


PSTN:  

+1.888.398.9698

x225


Fax:

+1.613.599.7457

 


Skype:       

 Objectworld   

x225

 <skype:Objectworld> 

 

 

 

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
Sent: Tuesday, April 03, 2007 8:57 AM
To: Michael Slavitch
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); David R
Oran; p2prg@ietf.org; sipping@ietf.org; zhuxian
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

 

 

Michael Slavitch wrote:

> Sorry for being late into this discussion, but client-server based VM 

> isn't truly client-server anymore in anything but the smallest or most 

> monolithic of enterprise networks, in fact the reality is that most if 

> not all enterprise networks contain just peers and superpeers with the 

> difference being partially a marketing decision by the vendors, as you 

> can charge much more for the servers, and a policy decision made either 

> automatically by a software deployment system or by IT staff which wants 

> to place supernodes with data sinks on appropriate equipment.

 

I'm sorry, but I don't understand the point you are trying to make 

above. You are trying to draw some sort of distinction, but I don't get 

it. Can you try again.

 

                Thanks,

                Paul

 

> In a 

> highly distributed environment there are potentially hundreds of 

> possible data sinks for a given application, with the sink based on 

> subnet or geographic location or balanced load, this can change rapidly 

> over time and does.

> 

> In the case of the Microsoft environment such policy is administered and 

> published between supernodes, ie servers, by Active Directory.  It is 

> advertised to mere peers through DNS.  There was much discussion a while 

> ago about building service discovery environment using DNS instead of a 

> P2P DHT.  It can be argued that a case study of a P2P example done using 

> DNS is any large Windows Server 2003 based Microsoft network with many 

> servers and many more clients that also run applications themselves and 

> are not just dumb terminals. This is almost certainly always the case in 

> all enterprises. The big difference between C/S SIP and P2PSIP is 

> automation. What is true is that the square peg in round hole of 

> overloading DNS makes deployments clumsy and brittle within the 

> enterprise domain and completely unmanageable and unpublishable outside 

> the firewall which is why the buck stops there in current enterprise 

> networking products.

> 

> The difference between C/S and P2P is largely policy and semantics with 

> the biggest difference being that the decisions and rules are highly 

> distributed.  Apart from that they are not just friends, they are 

> fraternal twins.

> 

> Regards

> 

> Michael Slavitch

> 

>  

> 

> 

> corp_2colour 

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://www.objec
tworld.com/>

> 

>  

> 

>             

> 

> 308 Legget Dr.

> Ottawa Ontario

> K2K 1Y6 Canada

> 

>             

> 

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://maps.goog
le.ca/maps?f=q%26hl=en%26q=308%2BLegget%2BDrive%2BOttawa%2BOntario%2BK2K%2B1
Y6%26layer=%26sll=45.341061,-75.904541%26sspn=0.007119,0.023839%26ie=UTF8%26
z=18%26ll=45.341061,-75.904541%26spn=0.00178,0.00596%26t=h%26om=1>

> 

>             

> 

>  

> 

> Michael Slavitch             

> 

> Lead, Technology Initiatives

> 

> slavitch@objectworld.com <mailto:slavitch@objectworld.com>

> 

>             

> 

> PSTN: 

> 

>             

> 

> +1.888.398.9698

> 

>             

> 

> x225

> 

> Fax:

> 

>             

> 

> +1.613.599.7457

> 

>             

> 

>  

> 

> Skype:      

> 

>             

> 

>   Objectworld 

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20M
SFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20
MME.EML/>   

> 

> 

>             

> 

> x225

> 

>             

> 

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20M
SFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20
MME.EML/>

> 

>             

> 

>  

> 

>  

> 

> 

 

 

-- 

BEGIN-ANTISPAM-VOTING-LINKS

------------------------------------------------------

 

Teach CanIt if this mail (ID 657805) is spam:

Spam:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=s

Not spam:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=n

Forget vote:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=f

------------------------------------------------------

END-ANTISPAM-VOTING-LINKS

 

  _____  

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete this information from your
system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely those of
the author and may not represent those of Objectworld Communications Corp.


------=_NextPart_001_1BDF_01C775F0.EE82F870
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns1=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PostalCode"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}
p.MSOPLAINTEXT
	{mso-style-priority:99;}
li.MSOPLAINTEXT
	{mso-style-priority:99;}
div.MSOPLAINTEXT
	{mso-style-priority:99;}
p.MSOACETATE
	{mso-style-priority:99;}
li.MSOACETATE
	{mso-style-priority:99;}
div.MSOACETATE
	{mso-style-priority:99;}
span.PLAINTEXTCHAR
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;}
span.PlainTextChar
	{font-family:Calibri;}
span.BalloonTextChar
	{font-family:Tahoma;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:846867197;
	mso-list-type:hybrid;
	mso-list-template-ids:-139805038 -1714783482 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I think most enterprise =
&#8220;PBX&#8221; vendors will
tell you that the things you can automate about provisioning have been
automated, and you won&#8217;t get much a win there. &nbsp;It&#8217;s =
things like TN assignment,
and dial plans, and gateway routing, and emergency call provisioning, =
and
permissions, and feature enabling, etc, etc that dominate provisioning =
of
enterprise telephony systems. &nbsp;P2P doesn&#8217;t help any of =
that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I worry, quite a bit, that =
perpetuating
SIP UAs (the SIP client) will perpetuate the dumb endpoint model, simply
because the way they are made now is that they are dumb endpoints. =
&nbsp;They didn&#8217;t
have to be (SIP was originally designed for smart endpoints).&nbsp; If =
we make
P2PSIP endpoints more closely fit the smart endpoint model, then we make =
the peer
that serves the UAs be the smart box in the middle of the =
network.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Brian<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Slavitch
[mailto:slavitch@objectworld.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007
10:48 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; Henry Sinnreich; p2prg@ietf.org;
sipping@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [P2PSIP] RE: =
[P2Prg] RE:
[Sipping] Simple SIP usage scenario</span></font><font size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
point I am making is&nbsp; that in the enterprise the actual topological
deployments of SIP clients and servers, <i><span =
style=3D'font-style:italic'>when
implemented as software on generic computing platforms</span></i>, as =
well as
the <i><span style=3D'font-style:italic'>mechanisms that make that =
deployment
happen</span></i>, are already very different world than the canonical
IMS/CSSIP one which &nbsp;assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD), &nbsp;B2BUA demarks,
network elements, and dumb fixed endpoints.&nbsp; Taking a network as a =
whole
enterprise application software using C/S SIP proxies and UA&#8217;s =
<i><span
style=3D'font-style:italic'>already</span></i> approximates something =
that is
close to what is being called P2PSIP, only in a manner that is highly
proprietary, closed, somewhat brittle and baroque, local, and ad-hoc, =
with
gaping ugly holes.&nbsp; P2P has the potential to transform =
that.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'>Some points I take from the previous =
discussion:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;that
a P2P setup will be *free*&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-list:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><span dir=3DLTR>&nbsp;A P2P =
network
may not be free, but the setup (provisioning) will be free, and
automatic.&nbsp; This is a major benefit only partially achieved in =
enterprise
networks,&nbsp; a benefit of great value to enterprises that is =
underserved by
vendors.&nbsp; There is no benefit in requiring complex deployments =
where
automation can take its place.&nbsp; Deployment is almost always the =
biggest
cost of enterprise systems dwarfing the cost of the systems =
themselves.<o:p></o:p></span></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I
think this depends greatly on what expectations / contractual guarantees =
the
enterprise has. It&#8217;s unclear to me what guarantees can be made =
about a P2PSIP
network will be able to make, and its unclear what kind of =
infrastructure would
be installed by/for someone willing to make =
guarantees.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-list:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><span dir=3DLTR>That is why
&#8216;expectations/contractual guarantees&#8217; need to be built into =
the automation that
exists in the P2P overlay.&nbsp; Self-calculation of such performance =
metrics
is already there in all enterprise devices, the difference being that =
while
WMI/SNMP data is merely collected a P2PSIP network can act automatically =
based
on the metrics within their own nodes, there is a collective =
&#8216;aha&#8217; that forces
behavior change based on strict contracts, aka rules.&nbsp; An =
<st1:place
w:st=3D"on">SLA</st1:place> is easier to maintain if the objects can =
react
accordingly, for example a node with degrading service can notify that =
it is on
the decline forcing others to take over.&nbsp; <o:p></o:p></span></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>There
is an old traffic engineering axiom about service guarantees: it can be
achieved through two ways: over engineering or &nbsp;automation.&nbsp; =
P2PSIP
allows for automation.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;David
Oran wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I'm
not saying this can't be made to work, only that it isn't immediately =
obvious
that it has advantages over a classic application/server =
approach.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
immediately obvious advantage to me is standardized ruggedized =
automation that
has economies of scale and operates over multiple domains, eliminating =
the need
for over-engineering,&nbsp; detailed fussy provisioning,&nbsp; and an =
army of
people doing basic monitoring and care-and-feeding.&nbsp; Automation is =
the
key, a dynamic statistical network vs. one that is fixed and assumed
deterministic will always win out over time given a fractal operating
environment.&nbsp;&nbsp; This is being done in fits and starts in the
enterprise data center.&nbsp;&nbsp; P2PSIP makes it much more =
comprehensive.&nbsp;
&nbsp;People want the world to be predictable and deterministic,&nbsp; =
and C/S
based systems reflect that. That is the biggest problem P2P faces =
because it
flies in the face of tradition. =
&nbsp;&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:6.65in;
  border:none;border-top:solid windowtext =
1.0pt;background:white;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><a
  href=3D"http://www.objectworld.com/" title=3D"Objectworld =
Communications"><font
  color=3Dblack><span =
style=3D'color:windowtext;text-decoration:none'><img
  border=3D0 width=3D237 height=3D42 id=3D"Picture_x005f_x0020_1"
  src=3D"cid:image001.jpg@01C775F0.E9CBB1F0" =
alt=3D"corp_2colour"></span></font></a><o:p></o:p></span></font></p>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><st1:Street w:st=3D"on"><st1:address =
w:st=3D"on"><font size=3D2
    face=3DCalibri><span style=3D'font-size:11.0pt'>308 Legget =
Dr</span></font></st1:address></st1:Street>.
  <br>
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State w:st=3D"on">Ontario</st1:State>
   <br>
<st1:PostalCode w:st=3D"on">K2K 1Y6</st1:PostalCode> <st1:country-region =
w:st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a
  =
href=3D"http://maps.google.ca/maps?f=3Dq&amp;hl=3Den&amp;q=3D308+Legget+D=
rive+Ottawa+Ontario+K2K+1Y6&amp;layer=3D&amp;sll=3D45.341061,-75.904541&a=
mp;sspn=3D0.007119,0.023839&amp;ie=3DUTF8&amp;z=3D18&amp;ll=3D45.341061,-=
75.904541&amp;spn=3D0.00178,0.00596&amp;t=3Dh&amp;om=3D1"
  title=3D"308 Legget Drive Ottawa Ontario K2K 1Y6"><font =
color=3Dblack><span
  style=3D'color:windowtext;text-decoration:none'><img border=3D0 =
width=3D29
  height=3D29 id=3D"Picture_x005f_x0020_6" =
src=3D"cid:image003.jpg@01C775F0.E9CBB1F0"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
    =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Lead,
    Technology Initiatives<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>slavitch@objectworld.com<o:p></o:p></span></fo=
nt></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0 width=3D204
   style=3D'width:152.85pt;border-collapse:collapse'>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>PSTN:&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.888.398.9698<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Fax:<o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.613.599.7457<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<a
    href=3D"Skype:Objectworld">Objectworld</a>&nbsp;&nbsp; =
<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a =
href=3D"skype:Objectworld"
  title=3DObjectworld><font color=3Dblack><span =
style=3D'color:windowtext;text-decoration:
  none'><img border=3D0 width=3D26 height=3D26 =
id=3D"Picture_x005f_x0020_3"
  =
src=3D"cid:image004.jpg@01C775F0.E9CBB1F0"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>-----Original
Message-----<br>
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] <br>
Sent: Tuesday, April 03, 2007 8:57 AM<br>
To: Michael Slavitch<br>
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); =
David R
Oran; p2prg@ietf.org; sipping@ietf.org; zhuxian<br>
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage =
scenario<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Sorry for being late into this discussion, but client-server based VM =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
isn't truly client-server anymore in anything but the smallest or most =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
monolithic of enterprise networks, in fact the reality is that most if =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
not all enterprise networks contain just peers and superpeers with the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
difference being partially a marketing decision by the vendors, as you =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
can charge much more for the servers, and a policy decision made either =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automatically by a software deployment system or by IT staff which wants =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
to place supernodes with data sinks on appropriate =
equipment.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>I'm
sorry, but I don't understand the point you are trying to make =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>above.
You are trying to draw some sort of distinction, but I don't get =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>it.
Can you try again.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Paul<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In a <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
highly distributed environment there are potentially hundreds of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
possible data sinks for a given application, with the sink based on =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
subnet or geographic location or balanced load, this can change rapidly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
over time and does.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In the case of the Microsoft environment such policy is administered and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
published between supernodes, ie servers, by Active Directory.&nbsp; It =
is <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
advertised to mere peers through DNS.&nbsp; There was much discussion a =
while <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
ago about building service discovery environment using DNS instead of a =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
P2P DHT.&nbsp; It can be argued that a case study of a P2P example done =
using <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
DNS is any large Windows Server 2003 based Microsoft network with many =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
servers and many more clients that also run applications themselves and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
are not just dumb terminals. This is almost certainly always the case in =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
all enterprises. The big difference between C/S SIP and P2PSIP is =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automation. What is true is that the square peg in round hole of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
overloading DNS makes deployments clumsy and brittle within the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
enterprise domain and completely unmanageable and unpublishable outside =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the firewall which is why the buck stops there in current enterprise =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
networking products.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
The difference between C/S and P2P is largely policy and semantics with =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the biggest difference being that the decisions and rules are highly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
distributed.&nbsp; Apart from that they are not just friends, they are =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
fraternal twins.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
corp_2colour <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://w=
ww.objectworld.com/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:Street w:st=3D"on"><st1:address w:st=3D"on">308 Legget =
Dr</st1:address></st1:Street>.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State =
w:st=3D"on">Ontario</st1:State></st1:place><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
K2K 1Y6 <st1:country-region w:st=3D"on"><st1:place =
w:st=3D"on">Canada</st1:place></st1:country-region><o:p></o:p></span></fo=
nt></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://m=
aps.google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2B=
Ontario%2BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.00=
7119,0.023839%26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.=
00178,0.00596%26t=3Dh%26om=3D1&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Lead, Technology Initiatives<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
slavitch@objectworld.com =
&lt;mailto:slavitch@objectworld.com&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
PSTN: <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.888.398.9698<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Fax:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.613.599.7457<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;&nbsp;
Objectworld <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>--
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>BEGIN-ANTISPAM-VOTING-LINKS<o:p></o:p></span><=
/font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Teach
CanIt if this mail (ID 657805) is spam:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Spam:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Ds<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Not
spam:&nbsp;&nbsp;&nbsp;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Dn<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Forget
vote: =
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Df<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>END-ANTISPAM-VOTING-LINKS<o:p></o:p></span></f=
ont></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>This
transmission (including any attachments) may contain confidential =
information,
privileged material (including material protected by the =
solicitor-client 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 immediately reply =
to the
sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended =
recipients is
not authorized and may be unlawful.<o:p></o:p></span></font></p>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>Any views,
opinions and content presented in this e-mail are solely those of the =
author
and may not represent those of Objectworld Communications =
Corp.<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------=_NextPart_001_1BDF_01C775F0.EE82F870--

------=_NextPart_000_1BDE_01C775F0.EE753CD0
Content-Type: image/jpeg;
	name="image001.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image001.jpg@01C775F0.E9CBB1F0>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6
+0EbNruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHExlWYK4wpGMhue
leLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9clnAj17UWQKd3+kNjPb+tN/s+6bR
21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHN
R/8AAlv8a9P8NWv/AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1U9W1W00TSrjU76Qx
29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GFE6eqnPpzXoHzp19FZniHXIPDmhXOr3Mc
ksNsoZkjxuOSBxn61ieHPiLpniHVV0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc
3dpDNClvcvbMJQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq39uaT
FqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jHGM/M3Psa2tC1uy8RaPb6
rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFreaPqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+
w3Vj5hYeRdJskXBxyKANGisRvFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6v
RZpDhd+8n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA2fxg0W4n
Tz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumtpPNA+Zh3GD0oA26KiuJltraW
dgSsSFyB1IAzXE6N8WtG1a7tIZNP1GxivZPKt7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8
kKcE9M5IrD1H4h6Hpltazzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+
jtPI2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1LvgEhv5V4sNKivt
c+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m1u7X7PGJ4vL+zRoFMe3J3YHY5x9a
1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej
3PAy/C1qWJTmmkt+vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLNd74l0OHxJ4evNInk
MSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZrKOGLYFXGMse5wf/AK9ekfLl74p/8k31
j/rmv/oa1xfhqXUW+IHhl/E0MVuf7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5
C4YHp+Fc5oHgDVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu11WK/
m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYHA9OBQByXjWXV4fi9oj6F
b29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRqZ0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xa
WxgBkg8zqWycHjo1dFoNtq1ppaQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs
9CsdDjg8OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/gK2/CHhuL
wn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ceFpvFmlWtlDdJbNBdpcFnUsCF
B44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1
Lx54N/4TPT7K2FwsDWt0sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/
AJoeP+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6Wv+oH+7/SvnjT
59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrzofC+5XwYNFXUoReQ6l9vt7nyzhD6
YznpmgD0RFCIqDooArz34S/e8Uf9hmWvQk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2
gYsC2SMnOOOOKAO41X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689GHQ1lT+EdCuQBLYK2
CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgBumKworm4ESATyYCj+M0j3M5KZnk4bj5z
Xjey97c+4WK/dr3e39bG/ChiiCEjIz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5
OW5+c+lCpbu45YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckxNyf9
9q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRR
QAUUUUAFFFFAH//Z

------=_NextPart_000_1BDE_01C775F0.EE753CD0
Content-Type: image/jpeg;
	name="image003.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image003.jpg@01C775F0.E9CBB1F0>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAdAB0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD0/VNW
WCU20cnllQPMkAyVz0A9/wCVUylrNEHWKOZjysk+XP5nmua1W8kXU7pZDg+e/wCW7A/TFPs9UmmU
Wquq8fK3cf4168cNywTR5EsTzTakdDFqT2M20l2j6mMknI7lc8j6dK6GORJY1kjYMrDII7ivOruS
eB0lklDljgHNdh4ald9Fi39iwX/dycfpiufFUVGKmjowtZyk4M5/xhoUzXDX9qhbf/rFA5z6j1rj
o5pILhGIHytzzivZnRZFKsAQazptCspX3NGM/SnQx0qceWSuia+AjUnzxdmef2ttd61f5XcIQcBs
cAe3qa9J0+1W0s44VGAqgAegotrC3th8ic+tWq56+IlWavokdFDDxop21b6n/9k=

------=_NextPart_000_1BDE_01C775F0.EE753CD0
Content-Type: image/jpeg;
	name="image004.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image004.jpg@01C775F0.E9CBB1F0>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAaABoDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1Ga7l
kZ2SdokV2VQgXJwcEnIPcHpVSTW7uHqYHA7bCCfxz/Skuiv9qSwFtitMoA/3gMn8yab/AGWls8lx
qTBbeE5HP+s/z6V4051nJ8j2ervov+AYty6GrpuqQ6lGxQFJE++hPT/EVdrjtEuvN8S+ZEuxJjIS
Pbkj+Qrsa7MDiHXpcz3Tt6lwlzIyNa0hr7E8GPNAwy5xvHb8axbu31G6jSO6W5ZYRwPKbH1JAwTX
Y0VFfAQqyck7X37MUqaZx2k6cf7QheCQMUcFipyFAPOfTjj8a7GiitcLhY4eLinuOMeVH//Z

------=_NextPart_000_1BDE_01C775F0.EE753CD0--



--===============0026181625==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0026181625==--





From sipping-bounces@ietf.org Wed Apr 04 11:11:46 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ78E-0004JG-W0; Wed, 04 Apr 2007 11:10:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZ78E-0004JB-2X
	for sipping@ietf.org; Wed, 04 Apr 2007 11:10:42 -0400
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZ78A-0007DY-Q9
	for sipping@ietf.org; Wed, 04 Apr 2007 11:10:42 -0400
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail1.lucent.com (8.13.8/IER-o) with ESMTP id l34FASVb001636;
	Wed, 4 Apr 2007 10:10:28 -0500 (CDT)
Received: from [127.0.0.1] ([135.104.20.65])
	by homail.ho.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l34FASn10188; Wed, 4 Apr 2007 11:10:28 -0400 (EDT)
Message-ID: <4613BFD4.9090107@bell-labs.com>
Date: Wed, 04 Apr 2007 11:10:12 -0400
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 192.11.226.41
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: Martin C Dolly <mdolly@att.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: [Sipping] Conclusion for merging
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

One of the remaining issues for config and policy data sets is whether 
merging of data sets is needed or not.

A UA can receive data sets from multiple different sources (local 
network provider, device provider and SIP service provider) and needs to 
combine these sets into a single data set it can work with. In 
principle, the following strategies exist for enable this:

1. For each property, define exactly one source that can set this 
property. For example, define that codec usage can only be set by the 
local network provider.
-> It seems impossible to assign each property to exactly one source. 
For example, if codec usage is assigned to the local network provider, 
it can never be part of the user profile.

2. Define an order of precedence between sources so that, for example, 
local profile overrides user profile and user profile overrides device 
profile.
-> This also does not seem to be practical. For example, a single codec 
setting in the local profile would override all codec settings in the 
user profile. Thus, the effects of the user profile would depend on 
whether or not there is a local profile.

3. Define rules for each property that specify how data from different 
sources is merged. Ideally, there are a small number of common rules 
that can be referred to for each property. Examples: use the lowest 
number for the allowed bandwidth, disable codecs if they are disallowed 
in a data set.
-> This approach seems feasible, however, it requires the implementation 
of multiple merging rules.

The current drafts uses option 3. Are there any concerns, comments, 
thoughts on using this approach? Are we missing something?

Thanks!

Volker



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 04 11:19:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ7GX-0000jE-2L; Wed, 04 Apr 2007 11:19:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ7GV-0000iy-2j; Wed, 04 Apr 2007 11:19:15 -0400
Received: from canitpro.objectworld.com ([72.1.207.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HZ7GR-00011V-2H; Wed, 04 Apr 2007 11:19:15 -0400
Received: from photon.objectworld.com (photon.objectworld.com [10.10.8.2])
	by canitpro.objectworld.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP
	id l34FJ0P5013315; Wed, 4 Apr 2007 11:19:00 -0400
MIME-Version: 1.0
x-cr-hashedpuzzle: CXpr HeV3 IpEd JFuk QBsk RlEd d8ux loYF 2XQU 2XjS ACu5FA==
	ACwSaQ== AIV41Q== AIhHbA== AIvxIQ== AJauZA==; 8;
	YgByAEAAYgByAGkAYQBuAHIAbwBzAGUAbgAuAG4AZQB0ADsAaABzAGkAbgBuAHIAZQBpAEAAYQBkAG8AYgBlAC4AYwBvAG0AOwBtAGgAYQBtAG0AZQByAEAAYwBpAHMAYwBvAC4AYwBvAG0AOwBvAHIAYQBuAEAAYwBpAHMAYwBvAC4AYwBvAG0AOwBwADIAcAByAGcAQABpAGUAdABmAC4AbwByAGcAOwBwADIAcABzAGkAcABAAGkAZQB0AGYALgBvAHIAZwA7AHAAawB5AHoAaQB2AGEAdABAAGMAaQBzAGMAbwAuAGMAbwBtADsAcwBpAHAAcABpAG4AZwBAAGkAZQB0AGYALgBvAHIAZwA=;
	Sosha1_v1; 7; {AA783291-6F0C-47A3-AFFF-C0AB3DD8D50D};
	cwBsAGEAdgBpAHQAYwBoAEAAbwBiAGoAZQBjAHQAdwBvAHIAbABkAC4AYwBvAG0A;
	Wed, 04 Apr 2007 15:18:22 GMT;
	UgBFADoAIABbAFAAMgBQAFMASQBQAF0AIABSAEUAOgAgAFsAUAAyAFAAcgBnAF0AIABSAEUAOgAgAFsAUwBpAHAAcABpAG4AZwBdACAAUwBpAG0AcABsAGUAIABTAEkAUAAgAHUAcwBhAGcAZQAgAHMAYwBlAG4AYQByAGkAbwA=
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
x-cr-puzzleid: {AA783291-6F0C-47A3-AFFF-C0AB3DD8D50D}
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Wed, 4 Apr 2007 11:18:22 -0400
Message-ID: <4E2DC1ACE541B94A946B8D8657E372C57A90BF@photon.objectworld.com>
In-Reply-To: <1e0501c776c1$6bd6bf70$81238182@cis.neustar.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Thread-Index: Acd176Ya+p6xqIGMQfSJrn6cLV80rgACgCmQAAX8woAAAZhX4AAHz3sgACH445AAAJ5BUA==
References: <24CCCC428EFEA2469BF046DB3C7A8D223ADF2F@namail5.corp.adobe.com>
	<1e0501c776c1$6bd6bf70$81238182@cis.neustar.com>
From: "Michael Slavitch" <slavitch@objectworld.com>
To: "Brian Rosen" <br@brianrosen.net>, "Henry Sinnreich" <hsinnrei@adobe.com>, 
	"Paul Kyzivat" <pkyzivat@cisco.com>
X-Spam-Score: 1.50 (*) [Tag at 20.00] EXTRA_MPART_TYPE, HTML_MESSAGE, SPF(none,
	0.1), 132(0.3), 131(0.3)
X-CanItPRO-Stream: outgoing (inherits from default)
X-Scanned-By: CanIt (www . roaringpenguin . com) on 10.10.8.9
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 97b8643c8d9cc60b17ea5996f3e435cb
Cc: sipping@ietf.org, p2prg@ietf.org, David R Oran <oran@cisco.com>,
	P2PSIP Mailing List <p2psip@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1535550020=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1535550020==
Content-Type: multipart/related; type="multipart/alternative";
	boundary="----_=_NextPart_001_01C776CC.922B3E63"
Content-class: urn:content-classes:message

This is a multi-part message in MIME format.

------_=_NextPart_001_01C776CC.922B3E63
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C776CC.922B3E63"


------_=_NextPart_002_01C776CC.922B3E63
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

A  response to troll rant inline.  Only for the curious.  Apologies in
advance.

=20

=20

  <http://www.objectworld.com/>=20

=20

=09=09=20

Michael Slavitch=20=20=20=20=20=20=20=20=20=20=20=20=20=20

Lead, Technology Initiatives

slavitch@objectworld.com

=09=09=20

=20

=20

From: Brian Rosen [mailto:br@brianrosen.net]=20
Sent: Wednesday, April 04, 2007 9:59 AM
To: 'Henry Sinnreich'; Michael Slavitch; 'Paul Kyzivat'
Cc: 'P2PSIP Mailing List'; 'Michael Hammer (mhammer)'; 'David R Oran';
p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage
scenario

=20

Have you actually ever built an enterprise telephony system?  Maybe
installed a recent one?

=20

[MNS>  ]  Rather than being 'who do you think you are' condescending,
you might instead consider Google as your friend,  Brian.  Since you
asked, you might consider clicking on the logo in my signature.  Going
way back I built the IP stack on the Mitel SX-2000 in the late 1980's.
Back then it was considered novel to have provisioning over something
called 'telnet' . On the provisioning side things haven't progressed
much since then, but at least I got to prove my thesis advisor wrong as
indeed voice over packet won.  Apparently they are using the IP same
stack today, hopefully with all my bugs fixed.=20

=20

Look, every product can be improved, and I do agree with Henry that the
enterprise telephony folks haven't caught on (or haven't figured out how
to make money on) presence and IM integration.  I think there have been
plenty of attempts to allow other app integration that have failed
pretty much completely despite what we would have thought.

=20

My take on this is that enterprise IT (which now owns phones), demands
the level of feature set the enterprise PBX guys give them, are pretty
much afraid of doing any serious app interaction except in call centers,
and would not see any inherent benefit in p2p.  "Self Organizing" is not
what we are talking about any more than current systems are self
organizing.

=20

[MNS>  ] PBX vendors are afraid because it is too complicated and
applications are not in their DNA.  They push boxes. Applications are
fully in the DNA of others, however, especially enterprise IT
departments because applications are what they do.  Enterprise IT
departments are not afraid of building applications.  They are afraid of
touching brittle PBX systems with limited badly documented interfaces
from incompetent PBX vendors that want to charge a mint for basic CTI
that doesn't even work. Want a reference? I have several.  BTW: Have you
been reading the trade press lately?  For the record: My interest is not
in improving PBX products. My interest is eliminating them and replacing
them with software without forcing changes in end-user behavior.

=20

In current systems, except in the very largest systems, there is a
server, you configure it, and plug the phones in.  They self configure.
The configuration on the server is complex, but it's not something that
needs a large staff; in most enterprises I know, there is usually one
guy (or sometimes one per site) who maintains the configuration part
time.  How much less do you think you could get, and what do you think
you could simplify with p2p?

=20

[MNS>  ] Well, that's true, at least in the press releases.  Reality
does differ.  I actually have real numbers: A cost reduction of at least
90% when moving from traditional PBX to well-automated C/S SIP, which is
what my employer currently does, and a further cost reduction of 90%
between C/S SIP and P2P SIP.  In the incumbent PBX case the biggest cost
of a deployment is almost always configuration and installation and
on-going maintenance.  In the last case the biggest cost of deployment
Want a reference?

=20

Skype?  In an enterprise?  Try talking to YOUR staff about that idea and
see how far you get.   Skype does not provide the feature set enterprise
wants.  You can claim the staff doesn't know its business I suppose.

=20

[MNS>  ]  Oracle? Selling SIP servers? Try talking to IT staff  and see
how far you get.  Skype? Supporting one-click monetization and
settlement with millions of customers over voice and other media? Why
would a business want that
<http://www.e2exchange.com-a.googlepages.com/skype4e.pps> ? Why would
someone like me put a Skype address in his signature?

=20

Let's take one simple example: dial plans.  Every enterprise has one.
Does Skype?  What would p2p do for dial plans that any current system
can't do right now?

=20

[MNS>  ] I'd love to get into that but that would be under NDA and the
IETF has strict rules about disclosure, sorry.

=20

What is the problem: dial plans are evil, we should get rid of them, or
dial plans are useful, and SOMEONE has to use some kind of tool to
configure them, and having done that, assign extension numbers within
the dial plan?  What would p2p do for us?  D'you want users configuring
their own extensions?=20=20

=20

[MNS>  ] NDA again and rules about disclosure. Sorry.   This is after
all a competitive industry.

=20

I see many benefits to p2p, but significantly simplifying enterprise
deployment isn't one of them.

=20

[MNS>  ] Excellent!  You must understand that in my line of work this is
considered a very positive development and confirmation. Money in the
bank. Thanks.


-----------------------------------------------=0D
=0D
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful. =0D
=0D
Any views, opinions and content presented in this e-mail are solely those o=
f the author and may not represent those of Objectworld Communications Corp=
.=20

------_=_NextPart_002_01C776CC.922B3E63
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.plaintextchar0
	{mso-style-name:plaintextchar;
	mso-style-priority:99;
	font-family:Consolas;}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	mso-style-priority:99;
	font-family:"Tahoma","sans-serif";}
span.plaintextchar00
	{mso-style-name:plaintextchar0;
	mso-style-priority:99;
	font-family:"Calibri","sans-serif";}
span.balloontextchar00
	{mso-style-name:balloontextchar0;
	mso-style-priority:99;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:navy;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:black;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:navy;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:navy;}
span.EmailStyle31
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'color:black'>A &nbsp;response to troll =
rant inline.&nbsp;
Only for the curious.&nbsp; Apologies in advance.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<div>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 wi=
dth=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop style=3D'width:6.65in;border:non=
e;
  border-top:solid windowtext 1.0pt;background:white;padding:0in 5.4pt 0in =
5.4pt'>
  <p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span>=
</p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop style=3D'width:214.55pt;background:white;pad=
ding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><a href=3D"http://www.objectworld.com/"
  title=3D"Objectworld Communications"><span style=3D'color:black;text-deco=
ration:
  none'><img border=3D0 width=3D237 height=3D42 id=3D"Picture_x0020_1"
  src=3D"cid:image004.jpg@01C776A2.38ADEB10" alt=3D"corp_2colour"></span></=
a><span
  style=3D'color:black'><o:p></o:p></span></p>
  <p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span>=
</p>
  </td>
  <td width=3D211 valign=3Dtop style=3D'width:158.05pt;background:white;pad=
ding:0in 0in 0in 0in'></td>
  <td width=3D137 valign=3Dtop style=3D'width:102.6pt;background:white;padd=
ing:0in 0in 0in 0in'></td>
  <td width=3D2 style=3D'width:1.5pt;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal>&nbsp;<o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop style=3D'width:214.55pt;background:white;pad=
ding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal><span style=3D'color:black'>Michael
    Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
    <o:p></o:p></span></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal><span style=3D'color:black'>Lead, Technology Initi=
atives<o:p></o:p></span></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in 0in=
 0in'>
    <p class=3DMsoNormal><span style=3D'color:black'><a
    href=3D"mailto:slavitch@objectworld.com">slavitch@objectworld.com</a><o=
:p></o:p></span></p>
    </td>
   </tr>
  </table>
  </td>
  <td width=3D211 valign=3Dtop style=3D'width:158.05pt;background:white;pad=
ding:0in 0in 0in 0in'></td>
  <td width=3D137 valign=3Dtop style=3D'width:102.6pt;background:white;padd=
ing:0in 0in 0in 0in'></td>
  <td width=3D2 style=3D'width:1.5pt;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal>&nbsp;<o:p></o:p></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><span style=3D'color:black;letter-spacing:-.5pt'><o:p>=
&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Brian Rosen
[mailto:br@brianrosen.net] <br>
<b>Sent:</b> Wednesday, April 04, 2007 9:59 AM<br>
<b>To:</b> 'Henry Sinnreich'; Michael Slavitch; 'Paul Kyzivat'<br>
<b>Cc:</b> 'P2PSIP Mailing List'; 'Michael Hammer (mhammer)'; 'David R Oran=
';
p2prg@ietf.org; sipping@ietf.org<br>
<b>Subject:</b> RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage
scenario<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>Have you actually ever built an enterprise telephony system?
&nbsp;Maybe installed a recent one?<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><i><span style=3D'color:black'>[MNS&gt;&nbsp; ] &nbsp;=
Rather
than being &#8216;who do you think you are&#8217; condescending, you might
instead consider Google as your friend,&nbsp; Brian. &nbsp;Since you asked,=
 you
might consider clicking on the logo in my signature.&nbsp; Going way back I
built the IP stack on the Mitel SX-2000 in the late 1980&#8217;s. Back then=
 it
was considered novel to have provisioning over something called &#8216;teln=
et&#8217;
. On the provisioning side things haven&#8217;t progressed much since then,=
 but
at least I got to prove my thesis advisor wrong as indeed voice over packet=
 won.&nbsp;
Apparently they are using the IP same stack today, hopefully with all my bu=
gs
fixed. <o:p></o:p></span></i></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>Look, every product can be improved, and I do agree with Henry =
that
the enterprise telephony folks haven&#8217;t caught on (or haven&#8217;t
figured out how to make money on) presence and IM integration.&nbsp; I think
there have been plenty of attempts to allow other app integration that have
failed pretty much completely despite what we would have thought.<o:p></o:p=
></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>My take on this is that enterprise IT (which now owns phones),
demands the level of feature set the enterprise PBX guys give them, are pre=
tty
much afraid of doing any serious app interaction except in call centers, and
would not see any inherent benefit in p2p.&nbsp; &#8220;Self Organizing&#82=
21;
is not what we are talking about any more than current systems are self
organizing.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><i><span style=3D'color:black'>[MNS&gt;&nbsp; ] PBX ve=
ndors
are afraid because it is too complicated and applications are not in their
DNA.&nbsp; They push boxes. Applications are fully in the DNA of others,
however, especially enterprise IT departments because </span><span
style=3D'color:red'>applications are what they do</span><span style=3D'colo=
r:black'>.
&nbsp;Enterprise IT departments are not afraid of building applications.&nb=
sp;
They are afraid of touching brittle PBX systems with limited badly document=
ed
interfaces from incompetent PBX vendors that want to charge a mint for basic
CTI that doesn&#8217;t even work. Want a reference? I have several.&nbsp; B=
TW: Have
you been reading the trade press lately? &nbsp;For the record: My interest =
is
not in improving PBX products. My interest is eliminating them and replacing
them with software without forcing changes in end-user behavior.<o:p></o:p>=
</span></i></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>In current systems, except in the very largest systems, there i=
s a
server, you configure it, and plug the phones in. &nbsp;They self
configure.&nbsp; The configuration on the server is complex, but it&#8217;s=
 not
something that needs a large staff; in most enterprises I know, there is
usually one guy (or sometimes one per site) who maintains the configuration
part time. &nbsp;How much less do you think you could get, and what do you
think you could simplify with p2p?<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><i><span style=3D'color:black'>[MNS&gt;&nbsp; ] Well, =
that&#8217;s
true, at least in the press releases.&nbsp; Reality does differ.&nbsp; I
actually have real numbers: A cost reduction of at least 90% when moving fr=
om
traditional PBX to well-automated C/S SIP, which is what my employer curren=
tly
does, and a further cost reduction of 90% between C/S SIP and P2P SIP. &nbs=
p;In
the incumbent PBX case the biggest cost of a deployment is almost always co=
nfiguration
and installation and on-going maintenance.&nbsp; In the last case the bigge=
st
cost of deployment &nbsp;Want a reference?</span></i><span style=3D'font-si=
ze:
10.0pt;font-family:"Arial","sans-serif";color:black'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>Skype?&nbsp; In an enterprise?&nbsp; Try talking to YOUR staff
about that idea and see how far you get.&nbsp; &nbsp;Skype does not provide=
 the
feature set enterprise wants.&nbsp; You can claim the staff doesn&#8217;t k=
now
its business I suppose.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><i><span style=3D'color:black'>[MNS&gt;&nbsp; ] &nbsp;=
Oracle?
Selling SIP servers? Try talking to IT staff &nbsp;and see how far you
get.&nbsp; Skype? Supporting one-click monetization and settlement with
millions of customers over voice and other media? Why would <a
href=3D"http://www.e2exchange.com-a.googlepages.com/skype4e.pps">a business=
 want
that</a>? Why would someone like me put a Skype address in his signature?<o=
:p></o:p></span></i></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>Let&#8217;s take one simple example: dial plans. &nbsp;Every
enterprise has one.&nbsp; Does Skype?&nbsp; What would p2p do for dial plans
that any current system can&#8217;t do right now?<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><i><span style=3D'color:black'>[MNS&gt;&nbsp; ] I&#821=
7;d love
to get into that but that would be under NDA and the IETF has strict rules
about disclosure, sorry.<o:p></o:p></span></i></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>What is the problem: dial plans are evil, we should get rid of
them, or dial plans are useful, and SOMEONE has to use some kind of tool to
configure them, and having done that, assign extension numbers within the d=
ial
plan? &nbsp;What would p2p do for us?&nbsp; D&#8217;you want users configur=
ing
their own extensions? &nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><i><span style=3D'color:black'>[MNS&gt;&nbsp; ] NDA ag=
ain and
rules about disclosure. Sorry.&nbsp;&nbsp; This is after all a competitive
industry.<o:p></o:p></span></i></p>

<p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></=
p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:navy'>I see many benefits to p2p, but significantly simplifying
enterprise deployment isn&#8217;t one of them.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:black'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><i><span style=3D'color:black'>[MNS&gt;&nbsp; ]
Excellent!&nbsp; You must understand that in my line of work this is consid=
ered
a very positive development and confirmation. Money in the bank. Thanks.</s=
pan></i><span
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'><o:p=
></o:p></span></p>

</div>

</div>

<hr width=3D"100%">=0D
<font size=3D"-2"><p>=0D
This transmission (including any attachments) may contain confidential info=
rmation, privileged material (including material protected by the solicitor=
-client or other applicable privileges), or constitute non-public informati=
on. Any use of this information by anyone other than the intended recipient=
 is prohibited. If you have received this transmission in error, please imm=
ediately reply to the sender and delete this information from your system. =
Use, dissemination, distribution, or reproduction of this transmission by u=
nintended recipients is not authorized and may be unlawful.</p>=0D
=0D
<p>Any views, opinions and content presented in this e-mail are solely thos=
e of the author and may not represent those of Objectworld Communications C=
orp.</p>=0D
</font>
</body>

</html>

------_=_NextPart_002_01C776CC.922B3E63--

------_=_NextPart_001_01C776CC.922B3E63
Content-Type: image/jpeg;
	name="image004.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image004.jpg@01C776A2.38ADEB10>
Content-Description: image004.jpg
Content-Location: image004.jpg
Content-Disposition: inline

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N
Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/
2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIAAhEBAxEB/8QA
HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF
BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1
dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB
AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC
AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom
JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6+0Eb
NruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHEx
lWYK4wpGMhueleLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9
clnAj17UWQKd3+kNjPb+tN/s+6bR21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1
IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHNR/8AAlv8a9P8NWv/
AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1
U9W1W00TSrjU76Qx29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GF
E6eqnPpzXoHzp19FZniHXIPDmhXOr3McksNsoZkjxuOSBxn61ieHPiLpniHV
V0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc3dpDNClvcvbM
JQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq3
9uaTFqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jH
GM/M3Psa2tC1uy8RaPb6rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFrea
PqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+w3Vj5hYeRdJskXBxyKANGisR
vFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6vRZpDhd+8
n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA
2fxg0W4nTz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumt
pPNA+Zh3GD0oA26KiuJltraWdgSsSFyB1IAzXE6N8WtG1a7tIZNP1GxivZPK
t7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8kKcE9M5IrD1H4h6Hplta
zzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+jtPI
2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1Lvg
Ehv5V4sNKivtc+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m
1u7X7PGJ4vL+zRoFMe3J3YHY5x9a1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD
059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej3PAy/C1qWJTmmkt+
vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLN
d74l0OHxJ4evNInkMSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZ
rKOGLYFXGMse5wf/AK9ekfLl74p/8k31j/rmv/oa1xfhqXUW+IHhl/E0MVuf
7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5C4YHp+Fc5oHg
DVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu1
1WK/m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYH
A9OBQByXjWXV4fi9oj6Fb29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRq
Z0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xaWxgBkg8zqWycHjo1dFoNtq1p
paQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs9CsdDjg8
OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/g
K2/CHhuLwn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ce
FpvFmlWtlDdJbNBdpcFnUsCFB44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r
8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1Lx54N/4TPT7K2FwsDWt0
sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/AJoe
P+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6W
v+oH+7/SvnjT59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrz
ofC+5XwYNFXUoReQ6l9vt7nyzhD6YznpmgD0RFCIqDooArz34S/e8Uf9hmWv
Qk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2gYsC2SMnOOOOKAO4
1X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689G
HQ1lT+EdCuQBLYK2CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgB
umKworm4ESATyYCj+M0j3M5KZnk4bj5zXjey97c+4WK/dr3e39bG/ChiiCEj
Iz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5OW5+c+lCpbu4
5YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckx
Nyf99q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFA
BRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAH//Z

------_=_NextPart_001_01C776CC.922B3E63--


--===============1535550020==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1535550020==--




From sipping-bounces@ietf.org Wed Apr 04 11:59:25 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ7sI-0007QM-UR; Wed, 04 Apr 2007 11:58:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZ7sG-0007Oh-7c
	for sipping@ietf.org; Wed, 04 Apr 2007 11:58:16 -0400
Received: from serrano.cc.columbia.edu ([128.59.29.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZ7sE-0000L7-Ud
	for sipping@ietf.org; Wed, 04 Apr 2007 11:58:16 -0400
Received: from [160.39.254.112] (dyn-160-39-254-112.dyn.columbia.edu
	[160.39.254.112]) (user=hgs10 mech=PLAIN bits=0)
	by serrano.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id l34Fw7Ka000680
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 4 Apr 2007 11:58:07 -0400 (EDT)
In-Reply-To: <4613BFD4.9090107@bell-labs.com>
References: <4613BFD4.9090107@bell-labs.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <870BBE78-990E-41A4-B985-04C5781EBD4C@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Conclusion for merging
Date: Wed, 4 Apr 2007 11:58:10 -0400
To: Volker Hilt <volkerh@bell-labs.com>
X-Mailer: Apple Mail (2.752.3)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.6
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: Martin C Dolly <mdolly@att.com>, sipping <sipping@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I'm concerned about complexity and predictability. As soon as you  
allow merging or overriding, things can change mid-call if  
configuration data suddenly becomes available or changes (by  
notification).

While theoretically, multiple providers can provide input for many of  
the parameters, I think it would be worthwhile to look at the likely  
scenarios. For that, it would be helpful to have a more complete list  
of likely configuration parameters. I actually see restricting codecs  
as a somewhat unlikely configuration option, except for the most  
paranoid corporations.

On Apr 4, 2007, at 11:10 AM, Volker Hilt wrote:

> One of the remaining issues for config and policy data sets is  
> whether merging of data sets is needed or not.
>
> A UA can receive data sets from multiple different sources (local  
> network provider, device provider and SIP service provider) and  
> needs to combine these sets into a single data set it can work  
> with. In principle, the following strategies exist for enable this:
>
> 1. For each property, define exactly one source that can set this  
> property. For example, define that codec usage can only be set by  
> the local network provider.
> -> It seems impossible to assign each property to exactly one  
> source. For example, if codec usage is assigned to the local  
> network provider, it can never be part of the user profile.
>
> 2. Define an order of precedence between sources so that, for  
> example, local profile overrides user profile and user profile  
> overrides device profile.
> -> This also does not seem to be practical. For example, a single  
> codec setting in the local profile would override all codec  
> settings in the user profile. Thus, the effects of the user profile  
> would depend on whether or not there is a local profile.
>
> 3. Define rules for each property that specify how data from  
> different sources is merged. Ideally, there are a small number of  
> common rules that can be referred to for each property. Examples:  
> use the lowest number for the allowed bandwidth, disable codecs if  
> they are disallowed in a data set.
> -> This approach seems feasible, however, it requires the  
> implementation of multiple merging rules.
>
> The current drafts uses option 3. Are there any concerns, comments,  
> thoughts on using this approach? Are we missing something?
>
> Thanks!
>
> Volker
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 04 12:14:45 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ87X-0003VZ-I0; Wed, 04 Apr 2007 12:14:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZ87V-0003VL-C8
	for sipping@ietf.org; Wed, 04 Apr 2007 12:14:01 -0400
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZ87U-0004z7-26
	for sipping@ietf.org; Wed, 04 Apr 2007 12:14:01 -0400
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l34GDnqY011964; 
	Wed, 4 Apr 2007 11:13:50 -0500 (CDT)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90])
	by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l34GDjA14547; Wed, 4 Apr 2007 11:13:45 -0500 (CDT)
Message-ID: <4613CEB9.2030209@alcatel-lucent.com>
Date: Wed, 04 Apr 2007 11:13:45 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "B, Nataraju" <bnataraju@sonusnet.com>
References: <70798CF421F00F4DA018059E5B7EEB8C0109AC2E@sonusinmail01.sonusnet.com>
In-Reply-To: <70798CF421F00F4DA018059E5B7EEB8C0109AC2E@sonusinmail01.sonusnet.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ihemail1.lucent.com id
	l34GDnqY011964
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: RjS@estacado.net, cboulton@ubiquitysoftware.com, sipping@ietf.org,
	Mary Barnes <mary.barnes@nortel.com>
Subject: [Sipping] Re: Comments on
	draft-ietf-sipping-ipv6-torture-tests-01.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

B, Nataraju wrote:
> Hi All,
>=20
> Here are few comments on the draft ipv6-torture-tests-01.txt.

Hi Nataraju: Thanks for reviewing the draft.  Please see inline.

> 1. Lets not allow IPV6 addresses with out [ & ], this is a deviation=20
> from RFC 3261 also.

Pedantically speaking, rfc3261 only wants the "[" and "]"
delimiting tokens for the IPv6reference production rule.  It
does NOT require these for the IPv6address production rule.

There has not been WG consensus on mandating the "[" and "]"
delimiting tokens for the IPv6address production rule -- this
is reflected in the ipv6-torture-tests draft.  That is
why it takes the position that a receiving implementation must
be robust enough to parse the IPv6address symbols with and
without the delimiters.

> This would definitely lead to interoperability issues later.

Hopefully these will be mitigated if implementors followed the
Robustness Principle of rfc1122 (also referenced in S4.5 of
ipv6-torture-tests.)

> 2. Replace all instances of umabiguous with unambiguous

Ouch; thanks!  Will do.

> 3. via-received not including delimiters [ & ] would make=20
> implementations complex or why don=92t we make sure all IPv6 addresses=20
> always accompany with delimiters [ & ]. This loop hole will definitely=20
> lead to interoperability issues some time later....

See discussion above.

> 4.
>=20
> Sec 4.5 param-2 of draft ipv6-torture-tests-01 is not valid with respec=
t=20
> to 3261
>=20
>         hence let us remove this test case

Actually, it is valid as per the ABNF in rfc3261.  The received
parameter contains an IPv6 address that follows the IPv6address
production rule, which does NOT require the delimiters.

> Ref: 4.6.  SIP request with IPv6 addresses in SDP body
>=20
> Even here also shall we mandate addresses are with [ & ]

Unfortunately, we cannot do that.  RFC4566 (SDP) does not require
that an IPv6 address be delimited by "[" and "]" (see IP6-address
production rule in the ABNF of rfc4566.)  Thus, rfc3261 cannot
over-ride it, and neither can this draft.

Thanks.

- vijay
--=20
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 04 12:23:29 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ8GD-0001j2-Kc; Wed, 04 Apr 2007 12:23:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZ8GC-0001iv-KB
	for sipping@ietf.org; Wed, 04 Apr 2007 12:23:00 -0400
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZ8G4-00082q-JB
	for sipping@ietf.org; Wed, 04 Apr 2007 12:23:00 -0400
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l34GMdXm019374; 
	Wed, 4 Apr 2007 11:22:39 -0500 (CDT)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90])
	by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l34GMdA19280; Wed, 4 Apr 2007 11:22:39 -0500 (CDT)
Message-ID: <4613D0CF.8070804@alcatel-lucent.com>
Date: Wed, 04 Apr 2007 11:22:39 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [Sipping] Additional SIPPING page
References: <45FFD370.2030502@ericsson.com>
In-Reply-To: <45FFD370.2030502@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: sipping <sipping@ietf.org>, Mary Barnes <mary.barnes@nortel.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Gonzalo Camarillo wrote:
> Hi,
> 
> on Monday, folks suggested to simplify our additional web page so that 
> it is easier to find the spreadsheets with the reviews (including due 
> dates, cached reviews, etc.).
> 
> Right now you can find them under [WG Review] at:
> 
> http://www.softarmor.com/sipping/
> 
> We would appreciate feedback on whether or not somebody who opens the 
> web page for the first time would be able to find the spreadsheets. 
> Other type of feedback would also be appreciated.

This is much better.  I had the need to consult the WG review
schedule today and was able to quickly navigate to it off the
softarmor SIPPING page.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 04 12:25:14 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ8IA-0002aw-GB; Wed, 04 Apr 2007 12:25:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ8I9-0002ai-Ea; Wed, 04 Apr 2007 12:25:01 -0400
Received: from exprod6og51.obsmtp.com ([64.18.1.183])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HZ8I6-0000Sn-CI; Wed, 04 Apr 2007 12:25:01 -0400
Received: from source ([192.150.20.142]) by exprod6ob51.postini.com
	([64.18.5.12]) with SMTP; Wed, 04 Apr 2007 09:24:50 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l34GOgSd010990; Wed, 4 Apr 2007 09:24:47 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l34GOaI9002310; Wed, 4 Apr 2007 09:24:36 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 4 Apr 2007 09:24:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 4 Apr 2007 09:24:35 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223ADF3E@namail5.corp.adobe.com>
In-Reply-To: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: P2P SIP service assurance (was Simple SIP usage scenario) -
	shortened
Thread-Index: Acd1fDvzIhowLornTwyehPLXZ9zr5AA/ypd/ABGlquA=
References: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: <colin.pons@kpn.com>, <pkyzivat@cisco.com>
X-OriginalArrivalTime: 04 Apr 2007 16:24:40.0606 (UTC)
	FILETIME=[BEE3CBE0:01C776D5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 813368b10167e7c87c318e91999bcea9
Cc: sipping@ietf.org, oran@cisco.com, p2psip@ietf.org, mhammer@cisco.com
Subject: [Sipping] P2P SIP service assurance (was Simple SIP usage scenario)
	- shortened
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0739106806=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0739106806==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C776D5.BE640658"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C776D5.BE640658
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Colin, Paul,

=20

Thanks for raising the valid issue about service assurance.=20

As engineers, we know the service assurance is more than a piece of
legal paper and must be based on the following:

=20

-          Adequate bandwidth,

-          Geographic diversity,

-          Simplicity; so things can be managed,

-          Security that can be audited,

-          Safe data retention: Replication and the geographic diversity
of peer nodes of the overlay,

-          Economy of scale: All peers have software with identical
behavior,

-          No configuration is required or possible. The customer just
plugs in the gateway box. This is real service automation.

-          Cost containment: P2P self configuration is unbeatable. Count
all the savings in CAPEX and OPEX by not having any network based VoIP
infrastructure. Save all that electricity and real estate in the data
centers.

-          Flexibility for new applications: The API between SIP and the
DHT overlay,

-          No lock-in from single source: The applications are in the
endpoints. Buy them from anywhere.

-          Automatic updates from the application provider: This is
current PC SW state of the art and works for both the (1) P2P software
in the access device and (2) for the application software, such as
presence, IM, voice, multimedia, etc. No or minimal is staff required.

-          Last but not least, besides SIP enabled communications, the
overlay can also serve for many other applications for your users:
Content distribution, application layer multicast for conferences,
directory search, IM+A/V chat rooms, name services, etc.

=20

All of the above can be easily implemented by porting well documented
open source software into the residential access box or in the
integrated access device (IAD) for enterprises. Just check out
http://opendht.org/ and other similar sites.

=20

Please don't take my word for it, just make for yourself a comparison
table for your network. If you can't share the comparison with the list,
can you share it with me in private? :-)

=20

*       as an employee of a carrier

=20

I worked most of my career for carriers, so that's what prompted the
above considerations.

=20

Thanks, Henry

=20

________________________________

From: colin.pons@kpn.com [mailto:colin.pons@kpn.com]=20
Sent: Wednesday, April 04, 2007 12:38 AM
To: pkyzivat@cisco.com; Henry Sinnreich
Cc: p2psip@ietf.org; mhammer@cisco.com; oran@cisco.com; p2prg@ietf.org;
sipping@ietf.org
Subject: RE: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage
scenario

=20

Henry,

I like your idea of deploying sip peers in edge devices. However, as an
employee of a carrier I would like to see how a carrier is able to
provide service asurance to be able to provide compliant handling. Many
of our customers do not understand how to install these gateways
themselves, let alone how to troubleshoot.

This is even more important for enterprises, which often  insist on SLAs
which include troubleshoot resolution limits.

-----Original Message-----
From: "Paul Kyzivat" <pkyzivat@cisco.com>
To: "Henry Sinnreich" <hsinnrei@adobe.com>
Cc: "P2PSIP Mailing List" <p2psip@ietf.org>; "Michael Hammer (mhammer)"
<mhammer@cisco.com>; "David R Oran" <oran@cisco.com>; "p2prg@ietf.org"
<p2prg@ietf.org>; "sipping@ietf.org" <sipping@ietf.org>
Sent: 3-4-07 01:11
Subject: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario



Henry Sinnreich wrote:
> Paul,
>
>> I more or less agree with the final conclusion below.
>
> This is good starting point to discuss some usage scenarios.
>
> Putting on my former hat as an employee for a carrier, I cannot
overlook
> the following:
>
> P2P SIP implemented correctly in the residential access box or cable
> set-top box indeed is a good or better replacement for the entire VoIP
> network infrastructure (cost, operations, new services, etc).
> Integrated access devices for the enterprise can probably play a
similar
> role, not to mention existing P2P PBX products (please refer to all
the
> advantages of P2P that need not repeated here).
>
> What do people think of these three usage scenarios for P2P SIP:
> - SIP peer in the DSL access device,
> - SIP peer in the cable access device,

These seem quite reasonable, assuming that a device connected at this
point is able to function properly as a peer. (I haven't been following
what the assumptions are about required network capabilities of peers.)

> - SIP peer in enterprise network integrated access device (IAD).

I think this depends greatly on what expectations / contractual
guarantees the enterprise has. Its unclear to me what guarantees can be
made about a P2PSIP network will be able to make, and its unclear what
kind of infrastructure would be installed by/for someone willing to make
guarantees.

        Paul

https://www1.ietf.org/mailman/listinfo/p2psip


------_=_NextPart_001_01C776D5.BE640658
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>RE: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage =
scenario</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:319894744;
	mso-list-type:hybrid;
	mso-list-template-ids:1009410942 -487147662 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Arial;
	mso-fareast-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1298990762;
	mso-list-type:hybrid;
	mso-list-template-ids:1053834342 -46605914 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:Arial;
	color:navy;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Colin, =
Paul,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks for raising the valid issue =
about
service assurance. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>As engineers, we know the service
assurance is more than a piece of legal paper and must be based on the
following:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Adequate
bandwidth,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Geographic
diversity,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Simplicity;
so things can be managed,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Security
that <u>can be audited</u>,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Safe
data retention: Replication and the geographic diversity of peer nodes =
of the overlay,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Economy
of scale: All peers have software with identical =
behavior,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>No
configuration is required or possible. The customer just plugs in the =
gateway
box. This is real service automation.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Cost
containment: P2P self configuration is unbeatable. Count all the savings =
in
CAPEX and OPEX by not having any network based VoIP infrastructure. Save =
all
that electricity and real estate in the data =
centers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Flexibility
for new applications: The API between SIP and the DHT =
overlay,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>No
lock-in from single source: The applications are in the endpoints. Buy =
them
from anywhere.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Automatic
updates from the application provider: This is current PC SW state of =
the art
and works for both the (1) P2P software in the access device and (2) for =
the
application software, such as presence, IM, voice, multimedia, etc. No =
or
minimal is staff required.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Last but
not least, besides SIP enabled communications, the overlay can also =
serve for
many other applications for your users: Content distribution, =
application layer
multicast for conferences, directory search, IM+A/V chat rooms, name =
services,
etc.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>All of the above can be easily =
implemented
by porting well documented open source software into the residential =
access box
or in the integrated access device (IAD) for enterprises. Just check out =
<a
href=3D"http://opendht.org/">http://opendht.org/</a> and other similar =
sites.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Please don&#8217;t take my word for =
it,
just make for yourself a comparison table for your network. If you =
can&#8217;t
share the comparison with the list, can you share it with me in private? =
</span></font><font
size=3D2 color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:
Wingdings;color:navy'>J</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo4'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:
Wingdings;color:navy'><span style=3D'mso-list:Ignore'>&Oslash;<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2><span
style=3D'font-size:10.0pt'>as an employee of a =
carrier<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>I worked most of my career for carriers, so that&#8217;s what =
prompted
the above considerations.</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, =
Henry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
colin.pons@kpn.com [mailto:colin.pons@kpn.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, April =
04, 2007
12:38 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> pkyzivat@cisco.com; =
Henry
Sinnreich<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
p2psip@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; mhammer@cisco.com; oran@cisco.com; =
<st1:PersonName
w:st=3D"on">p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>; <st1:PersonName =
w:st=3D"on">sipping@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] Re: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>Henry,<br>
<br>
I like your idea of deploying sip peers in edge devices. However, as an
employee of a carrier I would like to see how a carrier is able to =
provide
service asurance to be able to provide compliant handling. Many of our
customers do not understand how to install these gateways themselves, =
let alone
how to troubleshoot.<br>
<br>
This is even more important for enterprises, which often&nbsp; insist on =
SLAs
which include troubleshoot resolution limits.<br>
<br>
-----Original Message-----<br>
From: &quot;<st1:PersonName w:st=3D"on">Paul =
Kyzivat</st1:PersonName>&quot;
&lt;pkyzivat@cisco.com&gt;<br>
To: &quot;Henry Sinnreich&quot; &lt;hsinnrei@adobe.com&gt;<br>
Cc: &quot;<st1:PersonName w:st=3D"on">P2PSIP Mailing =
List</st1:PersonName>&quot;
&lt;p2psip@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName>&gt;; =
&quot;<st1:PersonName
w:st=3D"on">Michael Hammer</st1:PersonName> (mhammer)&quot;
&lt;mhammer@cisco.com&gt;; &quot;<st1:PersonName w:st=3D"on">David R =
<st1:City
 w:st=3D"on"><st1:place =
w:st=3D"on">Oran</st1:place></st1:City></st1:PersonName>&quot;
&lt;oran@cisco.com&gt;; &quot;<st1:PersonName =
w:st=3D"on">p2p<st1:PersonName
 w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&quot;
&lt;<st1:PersonName w:st=3D"on">p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>&gt;; =
&quot;<st1:PersonName
w:st=3D"on">sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&quot;
&lt;<st1:PersonName w:st=3D"on">sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&gt;<br>
Sent: 3-4-07 01:11<br>
Subject: [P2PSIP] Re: [P2P<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>] RE:
[Sipping] Simple SIP usage scenario<br>
<br>
<br>
<br>
Henry Sinnreich wrote:<br>
&gt; Paul,<br>
&gt;<br>
&gt;&gt; I more or less agree with the final conclusion below.<br>
&gt;<br>
&gt; This is good starting point to discuss some usage scenarios.<br>
&gt;<br>
&gt; Putting on my former hat as an employee for a carrier, I cannot =
overlook<br>
&gt; the following:<br>
&gt;<br>
&gt; P2P SIP implemented correctly in the residential access box or =
cable<br>
&gt; set-top box indeed is a good or better replacement for the entire =
VoIP<br>
&gt; network infrastructure (cost, operations, new services, etc).<br>
&gt; Integrated access devices for the enterprise can probably play a =
similar<br>
&gt; role, not to mention existing P2P PBX products (please refer to all =
the<br>
&gt; advantages of P2P that need not repeated here).<br>
&gt;<br>
&gt; What do people think of these three usage scenarios for P2P =
SIP:<br>
&gt; - SIP peer in the DSL access device,<br>
&gt; - SIP peer in the cable access device,<br>
<br>
These seem quite reasonable, assuming that a device connected at =
this<br>
point is able to function properly as a peer. (I haven't been =
following<br>
what the assumptions are about required network capabilities of =
peers.)<br>
<br>
&gt; - SIP peer in enterprise network integrated access device =
(IAD).<br>
<br>
I think this depends greatly on what expectations / contractual<br>
guarantees the enterprise has. Its unclear to me what guarantees can =
be<br>
made about a P2PSIP network will be able to make, and its unclear =
what<br>
kind of infrastructure would be installed by/for someone willing to =
make<br>
guarantees.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Paul<br>
<br>
<a =
href=3D"https://www1.ietf.org/mailman/listinfo/p2psip">https://www1.ietf.=
org/mailman/listinfo/p2psip</a></span></font><o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01C776D5.BE640658--


--===============0739106806==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0739106806==--




From sipping-bounces@ietf.org Wed Apr 04 15:51:28 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZBUi-0004LH-B7; Wed, 04 Apr 2007 15:50:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZBUb-0004Ie-ET; Wed, 04 Apr 2007 15:50:05 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HZBUY-0000yB-D8; Wed, 04 Apr 2007 15:50:05 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 5E6E5329F4;
	Wed,  4 Apr 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HZBUY-0001gT-7j; Wed, 04 Apr 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HZBUY-0001gT-7j@stiedprstage1.ietf.org>
Date: Wed, 04 Apr 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-pending-additions-02.txt 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: The Session Initiation Protocol (SIP) Pending Additions Event Package
	Author(s)	: G. Camarillo
	Filename	: draft-ietf-sipping-pending-additions-02.txt
	Pages		: 12
	Date		: 2007-4-4
	
This document defines the SIP Pending Additions event package.  This
   event package is used by SIP relays to inform user agents about the
   consent-related status of the entries to be added to a resource list.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-pending-additions-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sipping-pending-additions-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-pending-additions-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-4-4133401.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-pending-additions-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-pending-additions-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-4-4133401.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--NextPart--





From sipping-bounces@ietf.org Wed Apr 04 15:51:28 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZBVO-0004z6-9L; Wed, 04 Apr 2007 15:50:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZBV6-0004fE-TN; Wed, 04 Apr 2007 15:50:36 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HZBV6-0000pG-DH; Wed, 04 Apr 2007 15:50:36 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 726362ACAA;
	Wed,  4 Apr 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HZBUY-0001gQ-6q; Wed, 04 Apr 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HZBUY-0001gQ-6q@stiedprstage1.ietf.org>
Date: Wed, 04 Apr 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-consent-format-02.txt 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: A Document Format for Requesting Consent
	Author(s)	: G. Camarillo
	Filename	: draft-ietf-sipping-consent-format-02.txt
	Pages		: 13
	Date		: 2007-4-4
	
This document defines an Extensible Markup Language (XML) format for
   a permission document used to request consent.  A permission document
   written in this format is used by a relay to request a specific
   recipient permission to perform a particular routing translation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-consent-format-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sipping-consent-format-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-consent-format-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-4-4133233.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-consent-format-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-consent-format-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-4-4133233.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--NextPart--





From sipping-bounces@ietf.org Wed Apr 04 17:02:23 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZCaO-0002pQ-Ip; Wed, 04 Apr 2007 17:00:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZCaN-0002pF-J4
	for sipping@ietf.org; Wed, 04 Apr 2007 17:00:07 -0400
Received: from outbound.cantata.com ([208.236.123.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZCaM-0002U8-2T
	for sipping@ietf.org; Wed, 04 Apr 2007 17:00:07 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 4 Apr 2007 17:00:00 -0400
Message-ID: <AACB65FB607E074997DD8E482426D6F1E4C761@MA01EXCH01.Cantata.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Rejecting an unacceptable PRACK offer
Thread-Index: Acd2/DYTF4W95KJJQhSOuZo3aGDTTw==
From: "Kiyanda, Bernard" <bkiyanda@cantata.com>
To: <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
Subject: [Sipping] Rejecting an unacceptable PRACK offer
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0363901196=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0363901196==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C776FC.35CEE283"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C776FC.35CEE283
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Have there been additional clarifications on how to handle unacceptable
PRACK SDP offers, i.e. how a PRACK response would reject the request
(draft-sawada-sipping-sip-offeranswer-01)?

=20

Is the draft statement the desired behavior in section 1.2?

"When a UA receives a PRACK request with an offer which it can not

 accept, it may respond with a 200 response with a syntactically

 correct session description"

=20

The last discussion on this clarification was:

http://www1.ietf.org/mail-archive/web/sipping/current/msg11309.html

and proposing to create a new chapter and summarize the problem and
possible change/extensions to the existing rules to resolve it.

=20

Thanks,

Bernard

=20


------_=_NextPart_001_01C776FC.35CEE283
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Have there been additional clarifications on how to =
handle
unacceptable PRACK SDP offers, i.e. how a PRACK response would reject =
the request
(draft-sawada-sipping-sip-offeranswer-01)?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Is the draft statement the desired behavior in =
section 1.2?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&quot;When a UA receives a PRACK request with an =
offer which
it can not<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;accept, it may respond with a 200 response with =
a
syntactically<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;correct session =
description&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The last discussion on this clarification =
was:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>http://www1.ietf.org/mail-archive/web/sipping/current/=
msg11309.html<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>and proposing to create a new chapter and summarize =
the
problem and possible change/extensions to the existing rules to resolve =
it.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Bernard<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C776FC.35CEE283--


--===============0363901196==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0363901196==--




From sipping-bounces@ietf.org Wed Apr 04 21:42:33 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZGyT-0004QU-I4; Wed, 04 Apr 2007 21:41:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZGyR-0004Ol-Kw
	for sipping@ietf.org; Wed, 04 Apr 2007 21:41:15 -0400
Received: from hoemail2.lucent.com ([192.11.226.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZGyQ-0004jr-BE
	for sipping@ietf.org; Wed, 04 Apr 2007 21:41:15 -0400
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail2.lucent.com (8.13.8/IER-o) with ESMTP id l351f54d002186;
	Wed, 4 Apr 2007 20:41:05 -0500 (CDT)
Received: from [127.0.0.1] ([135.104.20.65])
	by homail.ho.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l351f4n29943; Wed, 4 Apr 2007 21:41:05 -0400 (EDT)
Message-ID: <461453A9.6080209@bell-labs.com>
Date: Wed, 04 Apr 2007 21:40:57 -0400
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Conclusion for merging
References: <4613BFD4.9090107@bell-labs.com>
	<870BBE78-990E-41A4-B985-04C5781EBD4C@cs.columbia.edu>
In-Reply-To: <870BBE78-990E-41A4-B985-04C5781EBD4C@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 192.11.226.42
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: Martin C Dolly <mdolly@att.com>, sipping <sipping@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Henning Schulzrinne wrote:
> I'm concerned about complexity and predictability. As soon as you allow
> merging or overriding, things can change mid-call if configuration data 
> suddenly becomes available or changes (by notification).
> 
I'm not sure if this is specific to merging. Even if there is only one 
source for profiles, this source may suddenly update config data 
mid-call through a notify.

> While theoretically, multiple providers can provide input for many of 
> the parameters, I think it would be worthwhile to look at the likely 
> scenarios. For that, it would be helpful to have a more complete list of 
> likely configuration parameters. I actually see restricting codecs as a 
> somewhat unlikely configuration option, except for the most paranoid 
> corporations.
> 
I think there are other examples as well in which it seems hard to 
assign a parameter to a specific provider. For example, a local provider 
as well as a SIP provider might want to restrict the use of video (both 
for different reasons). Or both providers may want to add a media 
intermediary. Or both want to restrict the bandwidth available for a 
session. Nevertheless, there might be parameters that can be assigned to 
a specific source. In this case, instead of specifying a merging rule, 
we might say that it can only come from a local/SIP/device provider.

The following drafts contain an initial list of configuration parameters 
for different areas:
- draft-petrie-sipping-profile-datasets-04.txt
- draft-petrie-sipping-sip-dataset-02.txt
- draft-petrie-sipping-identity-dataset-01.txt
- draft-petrie-sipping-voip-features-dataset-01.txt
- draft-ietf-sipping-media-policy-dataset-03

Thanks,

Volker





> On Apr 4, 2007, at 11:10 AM, Volker Hilt wrote:
> 
>> One of the remaining issues for config and policy data sets is whether 
>> merging of data sets is needed or not.
>>
>> A UA can receive data sets from multiple different sources (local 
>> network provider, device provider and SIP service provider) and needs 
>> to combine these sets into a single data set it can work with. In 
>> principle, the following strategies exist for enable this:
>>
>> 1. For each property, define exactly one source that can set this 
>> property. For example, define that codec usage can only be set by the 
>> local network provider.
>> -> It seems impossible to assign each property to exactly one source. 
>> For example, if codec usage is assigned to the local network provider, 
>> it can never be part of the user profile.
>>
>> 2. Define an order of precedence between sources so that, for example, 
>> local profile overrides user profile and user profile overrides device 
>> profile.
>> -> This also does not seem to be practical. For example, a single 
>> codec setting in the local profile would override all codec settings 
>> in the user profile. Thus, the effects of the user profile would 
>> depend on whether or not there is a local profile.
>>
>> 3. Define rules for each property that specify how data from different 
>> sources is merged. Ideally, there are a small number of common rules 
>> that can be referred to for each property. Examples: use the lowest 
>> number for the allowed bandwidth, disable codecs if they are 
>> disallowed in a data set.
>> -> This approach seems feasible, however, it requires the 
>> implementation of multiple merging rules.
>>
>> The current drafts uses option 3. Are there any concerns, comments, 
>> thoughts on using this approach? Are we missing something?
>>
>> Thanks!
>>
>> Volker
>>
>>
>>


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 05 08:05:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZQgF-0006lf-3C; Thu, 05 Apr 2007 08:03:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ619-0007sq-3D; Wed, 04 Apr 2007 09:59:19 -0400
Received: from ebru.winwebhosting.com ([74.52.236.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HZ615-0001mS-KM; Wed, 04 Apr 2007 09:59:19 -0400
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROSENLT40xp)
	by ebru.winwebhosting.com with esmtpa (Exim 4.63)
	(envelope-from <br@brianrosen.net>)
	id 1HZ60h-0000rA-D1; Wed, 04 Apr 2007 08:58:56 -0500
From: "Brian Rosen" <br@brianrosen.net>
To: "'Henry Sinnreich'" <hsinnrei@adobe.com>,
	"'Michael Slavitch'" <slavitch@objectworld.com>,
	"'Paul Kyzivat'" <pkyzivat@cisco.com>
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Wed, 4 Apr 2007 09:59:04 -0400
Message-ID: <1e0501c776c1$6bd6bf70$81238182@cis.neustar.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D223ADF2F@namail5.corp.adobe.com>
Thread-Index: Acd176Ya+p6xqIGMQfSJrn6cLV80rgACgCmQAAX8woAAAZhX4AAHz3sgACH445A=
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 6ddc52d7a0516c9ec326a2a741eefd1a
X-Mailman-Approved-At: Thu, 05 Apr 2007 08:03:04 -0400
Cc: sipping@ietf.org, p2prg@ietf.org, 'David R Oran' <oran@cisco.com>,
	'P2PSIP Mailing List' <p2psip@ietf.org>,
	"'Michael Hammer \(mhammer\)'" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0513198450=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0513198450==
Content-Type: multipart/related;
	boundary="----=_NextPart_000_1E06_01C7769F.E4C51F70"

This is a multi-part message in MIME format.

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_1E07_01C7769F.E4C51F70"


------=_NextPart_001_1E07_01C7769F.E4C51F70
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Have you actually ever built an enterprise telephony system?  Maybe
installed a recent one?

 

Look, every product can be improved, and I do agree with Henry that the
enterprise telephony folks haven't caught on (or haven't figured out how to
make money on) presence and IM integration.  I think there have been plenty
of attempts to allow other app integration that have failed pretty much
completely despite what we would have thought.

 

My take on this is that enterprise IT (which now owns phones), demands the
level of feature set the enterprise PBX guys give them, are pretty much
afraid of doing any serious app interaction except in call centers, and
would not see any inherent benefit in p2p.  "Self Organizing" is not what we
are talking about any more than current systems are self organizing.  In
current systems, except in the very largest systems, there is a server, you
configure it, and plug the phones in.  They self configure.  The
configuration on the server is complex, but it's not sFrom sipping-bounces@ietf.org Thu Apr 05 08:05:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZQgF-0006lf-3C; Thu, 05 Apr 2007 08:03:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ619-0007sq-3D; Wed, 04 Apr 2007 09:59:19 -0400
Received: from ebru.winwebhosting.com ([74.52.236.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HZ615-0001mS-KM; Wed, 04 Apr 2007 09:59:19 -0400
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROSENLT40xp)
	by ebru.winwebhosting.com with esmtpa (Exim 4.63)
	(envelope-from <br@brianrosen.net>)
	id 1HZ60h-0000rA-D1; Wed, 04 Apr 2007 08:58:56 -0500
From: "Brian Rosen" <br@brianrosen.net>
To: "'Henry Sinnreich'" <hsinnrei@adobe.com>,
	"'Michael Slavitch'" <slavitch@objectworld.com>,
	"'Paul Kyzivat'" <pkyzivat@cisco.com>
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Wed, 4 Apr 2007 09:59:04 -0400
Message-ID: <1e0501c776c1$6bd6bf70$81238182@cis.neustar.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D223ADF2F@namail5.corp.adobe.com>
Thread-Index: Acd176Ya+p6xqIGMQfSJrn6cLV80rgACgCmQAAX8woAAAZhX4AAHz3sgACH445A=
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 6ddc52d7a0516c9ec326a2a741eefd1a
X-Mailman-Approved-At: Thu, 05 Apr 2007 08:03:04 -0400
Cc: sipping@ietf.org, p2prg@ietf.org, 'David R Oran' <oran@cisco.com>,
	'P2PSIP Mailing List' <p2psip@ietf.org>,
	"'Michael Hammer \(mhammer\)'" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0513198450=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0513198450==
Content-Type: multipart/related;
	boundary="----=_NextPart_000_1E06_01C7769F.E4C51F70"

This is a multi-part message in MIME format.

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_1E07_01C7769F.E4C51F70"


------=_NextPart_001_1E07_01C7769F.E4C51F70
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Have you actually ever built an enterprise telephony system?  Maybe
installed a recent one?

 

Look, every product can be improved, and I do agree with Henry that the
enterprise telephony folks haven't caught on (or haven't figured out how to
make money on) presence and IM integration.  I think there have been plenty
of attempts to allow other app integration that have failed pretty much
completely despite what we would have thought.

 

My take on this is that enterprise IT (which now owns phones), demands the
level of feature set the enterprise PBX guys give them, are pretty much
afraid of doing any serious app interaction except in call centers, and
would not see any inherent benefit in p2p.  "Self Organizing" is not what we
are talking about any more than current systems are self organizing.  In
current systems, except in the very largest systems, there is a server, you
configure it, and plug the phones in.  They self configure.  The
configuration on the server is complex, but it's not sFrom sipping-bounces@ietf.org Thu Apr 05 08:05:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZQgF-0006lf-3C; Thu, 05 Apr 2007 08:03:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ619-0007sq-3D; Wed, 04 Apr 2007 09:59:19 -0400
Received: from ebru.winwebhosting.com ([74.52.236.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HZ615-0001mS-KM; Wed, 04 Apr 2007 09:59:19 -0400
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROSENLT40xp)
	by ebru.winwebhosting.com with esmtpa (Exim 4.63)
	(envelope-from <br@brianrosen.net>)
	id 1HZ60h-0000rA-D1; Wed, 04 Apr 2007 08:58:56 -0500
From: "Brian Rosen" <br@brianrosen.net>
To: "'Henry Sinnreich'" <hsinnrei@adobe.com>,
	"'Michael Slavitch'" <slavitch@objectworld.com>,
	"'Paul Kyzivat'" <pkyzivat@cisco.com>
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Wed, 4 Apr 2007 09:59:04 -0400
Message-ID: <1e0501c776c1$6bd6bf70$81238182@cis.neustar.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D223ADF2F@namail5.corp.adobe.com>
Thread-Index: Acd176Ya+p6xqIGMQfSJrn6cLV80rgACgCmQAAX8woAAAZhX4AAHz3sgACH445A=
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 6ddc52d7a0516c9ec326a2a741eefd1a
X-Mailman-Approved-At: Thu, 05 Apr 2007 08:03:04 -0400
Cc: sipping@ietf.org, p2prg@ietf.org, 'David R Oran' <oran@cisco.com>,
	'P2PSIP Mailing List' <p2psip@ietf.org>,
	"'Michael Hammer \(mhammer\)'" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0513198450=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0513198450==
Content-Type: multipart/related;
	boundary="----=_NextPart_000_1E06_01C7769F.E4C51F70"

This is a multi-part message in MIME format.

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_1E07_01C7769F.E4C51F70"


------=_NextPart_001_1E07_01C7769F.E4C51F70
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Have you actually ever built an enterprise telephony system?  Maybe
installed a recent one?

 

Look, every product can be improved, and I do agree with Henry that the
enterprise telephony folks haven't caught on (or haven't figured out how to
make money on) presence and IM integration.  I think there have been plenty
of attempts to allow other app integration that have failed pretty much
completely despite what we would have thought.

 

My take on this is that enterprise IT (which now owns phones), demands the
level of feature set the enterprise PBX guys give them, are pretty much
afraid of doing any serious app interaction except in call centers, and
would not see any inherent benefit in p2p.  "Self Organizing" is not what we
are talking about any more than current systems are self organizing.  In
current systems, except in the very largest systems, there is a server, you
configure it, and plug the phones in.  They self configure.  The
configuration on the server is complex, but it's not something that needs a
large staff; in most enterprises I know, there is usually one guy (or
sometimes one per site) who maintains the configuration part time.  How much
less do you think you could get, and what do you think you could simplify
with p2p?

 

Skype?  In an enterprise?  Try talking to YOUR staff about that idea and see
how far you get.   Skype does not provide the feature set enterprise wants.
You can claim the staff doesn't know its business I suppose.

 

Let's take one simple example: dial plans.  Every enterprise has one.  Does
Skype?  What would p2p do for dial plans that any current system can't do
right now?

 

What is the problem: dial plans are evil, we should get rid of them, or dial
plans are useful, and SOMEONE has to use some kind of tool to configure
them, and having done that, assign extension numbers within the dial plan?
What would p2p do for us?  D'you want users configuring their own
extensions?  

 

I see many benefits to p2p, but significantly simplifying enterprise
deployment isn't one of them.

 

Brian

 

  _____  

From: Henry Sinnreich [mailto:hsinnrei@adobe.com] 
Sent: Tuesday, April 03, 2007 5:53 PM
To: Michael Slavitch; Brian Rosen; Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran;
p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

I agree with Michael here. The voice-only PBX is pathetic as an enterprise
communication and productivity platform (no presence, IM, no integration
with apps, etc.) is also exactly the opposite of what self organizing
systems provide. As for the usability of those tiny screens and remembering
the various commands.

Why not just use Skype PC clients or Skype phones instead? At least, they
are WiFi and no configuration is required that cannot be done by the user.
And they can be used on travel as well.

 

Just think what self organizing and usability means for the maintenance
headcount and budget. Not to mention the associated IT systems.

 

P2P SIP in the enterprise is not a PBX replacement any more that SIP is a
PSTN replacement, though many decisions makers have not given up :-)

 

Thanks, Henry

 

  _____  

From: Michael Slavitch [mailto:slavitch@objectworld.com] 
Sent: Tuesday, April 03, 2007 12:58 PM
To: Brian Rosen; Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

"vendors will tell you the things you can automate about provisioning have
been automated."

 

The vendors will tell you this because the things that they automate can be
summarized as:

 

1.   "not much".

2.   What we automate is our proprietary stuff, sod the rest.

 

t's things like TN assignment, and dial plans, and gateway routing, and
emergency call provisioning, and permissions, and feature enabling, etc, etc
that dominate provisioning of enterprise telephony systems.  P2P doesn't
help any of that.

 

I strongly disagree with that.   Look at the documentation for products from
many of the major vendors, there are stacks of complex details regarding
deployment,  not very automatic at all, with many of them depending on
crufty TFTP or FTP with fixed file locations for provisioning of endpoints.
It's horrible.

Secondly, "it doesn't help with any of that" is only true in a static fixed
universe where you provision once and go away and limit functionality to
very basic tasks.   Even in that world the number of user change requests on
a 2000 user system is on the order of .5%-1% of all endpoints per day on
today's relatively static systems, 10 to 20 per day, and that's just basic
stuff, done at gunpoint.  Routers used to have only static routes too, and
web pages were once coded by hand.   

 

Regards

 

Michael

 

 


 


 <http://www.objectworld.com/> corp_2colour

 

 

 

 



Michael Slavitch              


Lead, Technology Initiatives


slavitch@objectworld.com

 

 

 

 

 

From: Brian Rosen [mailto:br@brianrosen.net] 
omething that needs a
large staff; in most enterprises I know, there is usually one guy (or
sometimes one per site) who maintains the configuration part time.  How much
less do you think you could get, and what do you think you could simplify
with p2p?

 

Skype?  In an enterprise?  Try talking to YOUR staff about that idea and see
how far you get.   Skype does not provide the feature set enterprise wants.
You can claim the staff doesn't know its business I suppose.

 

Let's take one simple example: dial plans.  Every enterprise has one.  Does
Skype?  What would p2p do for dial plans that any current system can't do
right now?

 

What is the problem: dial plans are evil, we should get rid of them, or dial
plans are useful, and SOMEONE has to use some kind of tool to configure
them, and having done that, assign extension numbers within the dial plan?
What would p2p do for us?  D'you want users configuring their own
extensions?  

 

I see many benefits to p2p, but significantly simplifying enterprise
deployment isn't one of them.

 

Brian

 

  _____  

From: Henry Sinnreich [mailto:hsinnrei@adobe.com] 
Sent: Tuesday, April 03, 2007 5:53 PM
To: Michael Slavitch; Brian Rosen; Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran;
p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

I agree with Michael here. The voice-only PBX is pathetic as an enterprise
communication and productivity platform (no presence, IM, no integration
with apps, etc.) is also exactly the opposite of what self organizing
systems provide. As for the usability of those tiny screens and remembering
the various commands.

Why not just use Skype PC clients or Skype phones instead? At least, they
are WiFi and no configuration is required that cannot be done by the user.
And they can be used on travel as well.

 

Just think what self organizing and usability means for the maintenance
headcount and budget. Not to mention the associated IT systems.

 

P2P SIP in the enterprise is not a PBX replacement any more that SIP is a
PSTN replacement, though many decisions makers have not given up :-)

 

Thanks, Henry

 

  _____  

From: Michael Slavitch [mailto:slavitch@objectworld.com] 
Sent: Tuesday, April 03, 2007 12:58 PM
To: Brian Rosen; Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

"vendors will tell you the things you can automate about provisioning have
been automated."

 

The vendors will tell you this because the things that they automate can be
summarized as:

 

1.   "not much".

2.   What we automate is our proprietary stuff, sod the rest.

 

t's things like TN assignment, and dial plans, and gateway routing, and
emergency call provisioning, and permissions, and feature enabling, etc, etc
that dominate provisioning of enterprise telephony systems.  P2P doesn't
help any of that.

 

I strongly disagree with that.   Look at the documentation for products from
many of the major vendors, there are stacks of complex details regarding
deployment,  not very automatic at all, with many of them depending on
crufty TFTP or FTP with fixed file locations for provisioning of endpoints.
It's horrible.

Secondly, "it doesn't help with any of that" is only true in a static fixed
universe where you provision once and go away and limit functionality to
very basic tasks.   Even in that world the number of user change requests on
a 2000 user system is on the order of .5%-1% of all endpoints per day on
today's relatively static systems, 10 to 20 per day, and that's just basic
stuff, done at gunpoint.  Routers used to have only static routes too, and
web pages were once coded by hand.   

 

Regards

 

Michael

 

 


 


 <http://www.objectworld.com/> corp_2colour

 

 

 

 



Michael Slavitch              


Lead, Technology Initiatives


slavitch@objectworld.com

 

 

 

 

 

From: Brian Rosen [mailto:br@brianrosen.net] 
omething that needs a
large staff; in most enterprises I know, there is usually one guy (or
sometimes one per site) who maintains the configuration part time.  How much
less do you think you could get, and what do you think you could simplify
with p2p?

 

Skype?  In an enterprise?  Try talking to YOUR staff about that idea and see
how far you get.   Skype does not provide the feature set enterprise wants.
You can claim the staff doesn't know its business I suppose.

 

Let's take one simple example: dial plans.  Every enterprise has one.  Does
Skype?  What would p2p do for dial plans that any current system can't do
right now?

 

What is the problem: dial plans are evil, we should get rid of them, or dial
plans are useful, and SOMEONE has to use some kind of tool to configure
them, and having done that, assign extension numbers within the dial plan?
What would p2p do for us?  D'you want users configuring their own
extensions?  

 

I see many benefits to p2p, but significantly simplifying enterprise
deployment isn't one of them.

 

Brian

 

  _____  

From: Henry Sinnreich [mailto:hsinnrei@adobe.com] 
Sent: Tuesday, April 03, 2007 5:53 PM
To: Michael Slavitch; Brian Rosen; Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran;
p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

I agree with Michael here. The voice-only PBX is pathetic as an enterprise
communication and productivity platform (no presence, IM, no integration
with apps, etc.) is also exactly the opposite of what self organizing
systems provide. As for the usability of those tiny screens and remembering
the various commands.

Why not just use Skype PC clients or Skype phones instead? At least, they
are WiFi and no configuration is required that cannot be done by the user.
And they can be used on travel as well.

 

Just think what self organizing and usability means for the maintenance
headcount and budget. Not to mention the associated IT systems.

 

P2P SIP in the enterprise is not a PBX replacement any more that SIP is a
PSTN replacement, though many decisions makers have not given up :-)

 

Thanks, Henry

 

  _____  

From: Michael Slavitch [mailto:slavitch@objectworld.com] 
Sent: Tuesday, April 03, 2007 12:58 PM
To: Brian Rosen; Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

"vendors will tell you the things you can automate about provisioning have
been automated."

 

The vendors will tell you this because the things that they automate can be
summarized as:

 

1.   "not much".

2.   What we automate is our proprietary stuff, sod the rest.

 

t's things like TN assignment, and dial plans, and gateway routing, and
emergency call provisioning, and permissions, and feature enabling, etc, etc
that dominate provisioning of enterprise telephony systems.  P2P doesn't
help any of that.

 

I strongly disagree with that.   Look at the documentation for products from
many of the major vendors, there are stacks of complex details regarding
deployment,  not very automatic at all, with many of them depending on
crufty TFTP or FTP with fixed file locations for provisioning of endpoints.
It's horrible.

Secondly, "it doesn't help with any of that" is only true in a static fixed
universe where you provision once and go away and limit functionality to
very basic tasks.   Even in that world the number of user change requests on
a 2000 user system is on the order of .5%-1% of all endpoints per day on
today's relatively static systems, 10 to 20 per day, and that's just basic
stuff, done at gunpoint.  Routers used to have only static routes too, and
web pages were once coded by hand.   

 

Regards

 

Michael

 

 


 


 <http://www.objectworld.com/> corp_2colour

 

 

 

 



Michael Slavitch              


Lead, Technology Initiatives


slavitch@objectworld.com

 

 

 

 

 

From: Brian Rosen [mailto:br@brianrosen.net] 
Sent: Tuesday, April 03, 2007 1:07 PM
To: Michael Slavitch; 'Paul Kyzivat'
Cc: 'P2PSIP Mailing List'; 'Michael Hammer (mhammer)'; 'David R Oran';
'Henry Sinnreich'; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

I think most enterprise "PBX" vendors will tell you that the things you can
automate about provisioning have been automated, and you won't get much a
win there.  It's things like TN assignment, and dial plans, and gateway
routing, and emergency call provisioning, and permissions, and feature
enabling, etc, etc that dominate provisioning of enterprise telephony
systems.  P2P doesn't help any of that.

 

I worry, quite a bit, that perpetuating SIP UAs (the SIP client) will
perpetuate the dumb endpoint model, simply because the way they are made now
is that they are dumb endpoints.  They didn't have to be (SIP was originally
designed for smart endpoints).  If we make P2PSIP endpoints more closely fit
the smart endpoint model, then we make the peer that serves the UAs be the
smart box in the middle of the network.

 

Brian

 

  _____  

From: Michael Slavitch [mailto:slavitch@objectworld.com] 
Sent: Tuesday, April 03, 2007 10:48 AM
To: Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

The point I am making is  that in the enterprise the actual topological
deployments of SIP clients and servers, when implemented as software on
generic computing platforms, as well as the mechanisms that make that
deployment happen, are already very different world than the canonical
IMS/CSSIP one which  assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD),  B2BUA demarks, network
elements, and dumb fixed endpoints.  Taking a network as a whole enterprise
application software using C/S SIP proxies and UA's already approximates
something that is close to what is being called P2PSIP, only in a manner
that is highly proprietary, closed, somewhat brittle and baroque, local, and
ad-hoc, with gaping ugly holes.  P2P has the potential to transform that.

 

Some points I take from the previous discussion:

"that a P2P setup will be *free*"

 

-    A P2P network may not be free, but the setup (provisioning) will be
free, and automatic.  This is a major benefit only partially achieved in
enterprise networks,  a benefit of great value to enterprises that is
underserved by vendors.  There is no benefit in requiring complex
deployments where automation can take its place.  Deployment is almost
always the biggest cost of enterprise systems dwarfing the cost of the
systems themselves.

 

"I think this depends greatly on what expectations / contractual guarantees
the enterprise has. It's unclear to me what guarantees can be made about a
P2PSIP network will be able to make, and its unclear what kind of
infrastructure would be installed by/for someone willing to make
guarantees."

 

-   That is why 'expectations/contractual guarantees' need to be built into
the automation that exists in the P2P overlay.  Self-calculation of such
performance metrics is already there in all enterprise devices, the
difference being that while WMI/SNMP data is merely collected a P2PSIP
network can act automatically based on the metrics within their own nodes,
there is a collective 'aha' that forces behavior change based on strict
contracts, aka rules.  An SLA is easier to maintain if the objects can react
accordingly, for example a node with degrading service can notify that it is
on the decline forcing others to take over.  

 

There is an old traffic engineering axiom about service guarantees: it can
be achieved through two ways: over engineering or  automation.  P2PSIP
allows for automation.

 

 David Oran wrote:

 

"I'm not saying this can't be made to work, only that it isn't immediately
obvious that it has advantages over a classic application/server approach."

 

The immediately obvious advantage to meSent: Tuesday, April 03, 2007 1:07 PM
To: Michael Slavitch; 'Paul Kyzivat'
Cc: 'P2PSIP Mailing List'; 'Michael Hammer (mhammer)'; 'David R Oran';
'Henry Sinnreich'; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

I think most enterprise "PBX" vendors will tell you that the things you can
automate about provisioning have been automated, and you won't get much a
win there.  It's things like TN assignment, and dial plans, and gateway
routing, and emergency call provisioning, and permissions, and feature
enabling, etc, etc that dominate provisioning of enterprise telephony
systems.  P2P doesn't help any of that.

 

I worry, quite a bit, that perpetuating SIP UAs (the SIP client) will
perpetuate the dumb endpoint model, simply because the way they are made now
is that they are dumb endpoints.  They didn't have to be (SIP was originally
designed for smart endpoints).  If we make P2PSIP endpoints more closely fit
the smart endpoint model, then we make the peer that serves the UAs be the
smart box in the middle of the network.

 

Brian

 

  _____  

From: Michael Slavitch [mailto:slavitch@objectworld.com] 
Sent: Tuesday, April 03, 2007 10:48 AM
To: Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

The point I am making is  that in the enterprise the actual topological
deployments of SIP clients and servers, when implemented as software on
generic computing platforms, as well as the mechanisms that make that
deployment happen, are already very different world than the canonical
IMS/CSSIP one which  assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD),  B2BUA demarks, network
elements, and dumb fixed endpoints.  Taking a network as a whole enterprise
application software using C/S SIP proxies and UA's already approximates
something that is close to what is being called P2PSIP, only in a manner
that is highly proprietary, closed, somewhat brittle and baroque, local, and
ad-hoc, with gaping ugly holes.  P2P has the potential to transform that.

 

Some points I take from the previous discussion:

"that a P2P setup will be *free*"

 

-    A P2P network may not be free, but the setup (provisioning) will be
free, and automatic.  This is a major benefit only partially achieved in
enterprise networks,  a benefit of great value to enterprises that is
underserved by vendors.  There is no benefit in requiring complex
deployments where automation can take its place.  Deployment is almost
always the biggest cost of enterprise systems dwarfing the cost of the
systems themselves.

 

"I think this depends greatly on what expectations / contractual guarantees
the enterprise has. It's unclear to me what guarantees can be made about a
P2PSIP network will be able to make, and its unclear what kind of
infrastructure would be installed by/for someone willing to make
guarantees."

 

-   That is why 'expectations/contractual guarantees' need to be built into
the automation that exists in the P2P overlay.  Self-calculation of such
performance metrics is already there in all enterprise devices, the
difference being that while WMI/SNMP data is merely collected a P2PSIP
network can act automatically based on the metrics within their own nodes,
there is a collective 'aha' that forces behavior change based on strict
contracts, aka rules.  An SLA is easier to maintain if the objects can react
accordingly, for example a node with degrading service can notify that it is
on the decline forcing others to take over.  

 

There is an old traffic engineering axiom about service guarantees: it can
be achieved through two ways: over engineering or  automation.  P2PSIP
allows for automation.

 

 David Oran wrote:

 

"I'm not saying this can't be made to work, only that it isn't immediately
obvious that it has advantages over a classic application/server approach."

 

The immediately obvious advantage to meSent: Tuesday, April 03, 2007 1:07 PM
To: Michael Slavitch; 'Paul Kyzivat'
Cc: 'P2PSIP Mailing List'; 'Michael Hammer (mhammer)'; 'David R Oran';
'Henry Sinnreich'; p2prg@ietf.org; sipping@ietf.org
Subject: RE: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

I think most enterprise "PBX" vendors will tell you that the things you can
automate about provisioning have been automated, and you won't get much a
win there.  It's things like TN assignment, and dial plans, and gateway
routing, and emergency call provisioning, and permissions, and feature
enabling, etc, etc that dominate provisioning of enterprise telephony
systems.  P2P doesn't help any of that.

 

I worry, quite a bit, that perpetuating SIP UAs (the SIP client) will
perpetuate the dumb endpoint model, simply because the way they are made now
is that they are dumb endpoints.  They didn't have to be (SIP was originally
designed for smart endpoints).  If we make P2PSIP endpoints more closely fit
the smart endpoint model, then we make the peer that serves the UAs be the
smart box in the middle of the network.

 

Brian

 

  _____  

From: Michael Slavitch [mailto:slavitch@objectworld.com] 
Sent: Tuesday, April 03, 2007 10:48 AM
To: Paul Kyzivat
Cc: P2PSIP Mailing List; Michael Hammer (mhammer); David R Oran; Henry
Sinnreich; p2prg@ietf.org; sipping@ietf.org
Subject: [P2PSIP] RE: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

The point I am making is  that in the enterprise the actual topological
deployments of SIP clients and servers, when implemented as software on
generic computing platforms, as well as the mechanisms that make that
deployment happen, are already very different world than the canonical
IMS/CSSIP one which  assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD),  B2BUA demarks, network
elements, and dumb fixed endpoints.  Taking a network as a whole enterprise
application software using C/S SIP proxies and UA's already approximates
something that is close to what is being called P2PSIP, only in a manner
that is highly proprietary, closed, somewhat brittle and baroque, local, and
ad-hoc, with gaping ugly holes.  P2P has the potential to transform that.

 

Some points I take from the previous discussion:

"that a P2P setup will be *free*"

 

-    A P2P network may not be free, but the setup (provisioning) will be
free, and automatic.  This is a major benefit only partially achieved in
enterprise networks,  a benefit of great value to enterprises that is
underserved by vendors.  There is no benefit in requiring complex
deployments where automation can take its place.  Deployment is almost
always the biggest cost of enterprise systems dwarfing the cost of the
systems themselves.

 

"I think this depends greatly on what expectations / contractual guarantees
the enterprise has. It's unclear to me what guarantees can be made about a
P2PSIP network will be able to make, and its unclear what kind of
infrastructure would be installed by/for someone willing to make
guarantees."

 

-   That is why 'expectations/contractual guarantees' need to be built into
the automation that exists in the P2P overlay.  Self-calculation of such
performance metrics is already there in all enterprise devices, the
difference being that while WMI/SNMP data is merely collected a P2PSIP
network can act automatically based on the metrics within their own nodes,
there is a collective 'aha' that forces behavior change based on strict
contracts, aka rules.  An SLA is easier to maintain if the objects can react
accordingly, for example a node with degrading service can notify that it is
on the decline forcing others to take over.  

 

There is an old traffic engineering axiom about service guarantees: it can
be achieved through two ways: over engineering or  automation.  P2PSIP
allows for automation.

 

 David Oran wrote:

 

"I'm not saying this can't be made to work, only that it isn't immediately
obvious that it has advantages over a classic application/server approach."

 

The immediately obvious advantage to me is standardized ruggedized
automation that has economies of scale and operates over multiple domains,
eliminating the need for over-engineering,  detailed fussy provisioning,
and an army of people doing basic monitoring and care-and-feeding.
Automation is the key, a dynamic statistical network vs. one that is fixed
and assumed deterministic will always win out over time given a fractal
operating environment.   This is being done in fits and starts in the
enterprise data center.   P2PSIP makes it much more comprehensive.   People
want the world to be predictable and deterministic,  and C/S based systems
reflect that. That is the biggest problem P2P faces because it flies in the
face of tradition.   

 

Regards

 

Michael Slavitch

 

 

 

 


 


 <http://www.objectworld.com/> corp_2colour

 

308 Legget Dr. 
Ottawa Ontario 
K2K 1Y6 Canada

 
<http://maps.google.ca/maps?f=q&hl=en&q=308+Legget+Drive+Ottawa+Ontario+K2K+
1Y6&layer=&sll=45.341061,-75.904541&sspn=0.007119,0.023839&ie=UTF8&z=18&ll=4
5.341061,-75.904541&spn=0.00178,0.00596&t=h&om=1> 

 



Michael Slavitch              


Lead, Technology Initiatives


slavitch@objectworld.com


PSTN:  

+1.888.398.9698

x225


Fax:

+1.613.599.7457

 


Skype:       

 Objectworld   

x225

 <skype:Objectworld> 

 

 

 

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
Sent: Tuesday, April 03, 2007 8:57 AM
To: Michael Slavitch
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); David R
Oran; p2prg@ietf.org; sipping@ietf.org; zhuxian
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

 

 

Michael Slavitch wrote:

> Sorry for being late into this discussion, but client-server based VM 

> isn't truly client-server anymore in anything but the smallest or most 

> monolithic of enterprise networks, in fact the reality is that most if 

> not all enterprise networks contain just peers and superpeers with the 

> difference being partially a marketing decision by the vendors, as you 

> can charge much more for the servers, and a policy decision made either 

> automatically by a software deployment system or by IT staff which wants 

> to place supernodes with data sinks on appropriate equipment.

 

I'm sorry, but I don't understand the point you are trying to make 

above. You are trying to draw some sort of distinction, but I don't get 

it. Can you try again.

 

                Thanks,

                Paul

 

> In a 

> highly distributed environment there are potentially hundreds of 

> possible data sinks for a given application, with the sink based on 

> subnet or geographic location or balanced load, this can change rapidly 

> over time and does.

> 

> In the case of the Microsoft environment such policy is administered and 

> published between supernodes, ie servers, by Active Directory.  It is 

> advertised to mere peers through DNS.  There was much discussion a while 

> ago about building service discovery environment using DNS instead of a 

> P2P DHT.  It can be argued that a case study of a P2P example done using 

> DNS is any large Windows Server 2003 based Microsoft network with many 

> servers and many more clients that also run applications themselves and 

> are not just dumb terminals. This is almost certainly always the case in 

> all enterprises. The big difference between C/S SIP and P2PSIP is 

> automation. What is true is that the square peg in round hole of 

> overloading DNS makes deployments clumsy and brittle within the 

> enterprise domain and completely unmanageable and unpublishable outside 

> the firewall which is why the buck stops there in current enterprise 

> networking products.

> 

> The difference between C/S and P2P is largely policy and semantics with 

> the biggest difference being that the decisions and rules are highly 

> distributed.  Apart from that they are not just friends, they are 

> fraternal twins.

> 

> Regards

> 

> Michael Slavitch

> 

>  

> 

> 

> corp_2colour 

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://www.objec
 is standardized ruggedized
automation that has economies of scale and operates over multiple domains,
eliminating the need for over-engineering,  detailed fussy provisioning,
and an army of people doing basic monitoring and care-and-feeding.
Automation is the key, a dynamic statistical network vs. one that is fixed
and assumed deterministic will always win out over time given a fractal
operating environment.   This is being done in fits and starts in the
enterprise data center.   P2PSIP makes it much more comprehensive.   People
want the world to be predictable and deterministic,  and C/S based systems
reflect that. That is the biggest problem P2P faces because it flies in the
face of tradition.   

 

Regards

 

Michael Slavitch

 

 

 

 


 


 <http://www.objectworld.com/> corp_2colour

 

308 Legget Dr. 
Ottawa Ontario 
K2K 1Y6 Canada

 
<http://maps.google.ca/maps?f=q&hl=en&q=308+Legget+Drive+Ottawa+Ontario+K2K+
1Y6&layer=&sll=45.341061,-75.904541&sspn=0.007119,0.023839&ie=UTF8&z=18&ll=4
5.341061,-75.904541&spn=0.00178,0.00596&t=h&om=1> 

 



Michael Slavitch              


Lead, Technology Initiatives


slavitch@objectworld.com


PSTN:  

+1.888.398.9698

x225


Fax:

+1.613.599.7457

 


Skype:       

 Objectworld   

x225

 <skype:Objectworld> 

 

 

 

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
Sent: Tuesday, April 03, 2007 8:57 AM
To: Michael Slavitch
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); David R
Oran; p2prg@ietf.org; sipping@ietf.org; zhuxian
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

 

 

Michael Slavitch wrote:

> Sorry for being late into this discussion, but client-server based VM 

> isn't truly client-server anymore in anything but the smallest or most 

> monolithic of enterprise networks, in fact the reality is that most if 

> not all enterprise networks contain just peers and superpeers with the 

> difference being partially a marketing decision by the vendors, as you 

> can charge much more for the servers, and a policy decision made either 

> automatically by a software deployment system or by IT staff which wants 

> to place supernodes with data sinks on appropriate equipment.

 

I'm sorry, but I don't understand the point you are trying to make 

above. You are trying to draw some sort of distinction, but I don't get 

it. Can you try again.

 

                Thanks,

                Paul

 

> In a 

> highly distributed environment there are potentially hundreds of 

> possible data sinks for a given application, with the sink based on 

> subnet or geographic location or balanced load, this can change rapidly 

> over time and does.

> 

> In the case of the Microsoft environment such policy is administered and 

> published between supernodes, ie servers, by Active Directory.  It is 

> advertised to mere peers through DNS.  There was much discussion a while 

> ago about building service discovery environment using DNS instead of a 

> P2P DHT.  It can be argued that a case study of a P2P example done using 

> DNS is any large Windows Server 2003 based Microsoft network with many 

> servers and many more clients that also run applications themselves and 

> are not just dumb terminals. This is almost certainly always the case in 

> all enterprises. The big difference between C/S SIP and P2PSIP is 

> automation. What is true is that the square peg in round hole of 

> overloading DNS makes deployments clumsy and brittle within the 

> enterprise domain and completely unmanageable and unpublishable outside 

> the firewall which is why the buck stops there in current enterprise 

> networking products.

> 

> The difference between C/S and P2P is largely policy and semantics with 

> the biggest difference being that the decisions and rules are highly 

> distributed.  Apart from that they are not just friends, they are 

> fraternal twins.

> 

> Regards

> 

> Michael Slavitch

> 

>  

> 

> 

> corp_2colour 

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://www.objec
 is standardized ruggedized
automation that has economies of scale and operates over multiple domains,
eliminating the need for over-engineering,  detailed fussy provisioning,
and an army of people doing basic monitoring and care-and-feeding.
Automation is the key, a dynamic statistical network vs. one that is fixed
and assumed deterministic will always win out over time given a fractal
operating environment.   This is being done in fits and starts in the
enterprise data center.   P2PSIP makes it much more comprehensive.   People
want the world to be predictable and deterministic,  and C/S based systems
reflect that. That is the biggest problem P2P faces because it flies in the
face of tradition.   

 

Regards

 

Michael Slavitch

 

 

 

 


 


 <http://www.objectworld.com/> corp_2colour

 

308 Legget Dr. 
Ottawa Ontario 
K2K 1Y6 Canada

 
<http://maps.google.ca/maps?f=q&hl=en&q=308+Legget+Drive+Ottawa+Ontario+K2K+
1Y6&layer=&sll=45.341061,-75.904541&sspn=0.007119,0.023839&ie=UTF8&z=18&ll=4
5.341061,-75.904541&spn=0.00178,0.00596&t=h&om=1> 

 



Michael Slavitch              


Lead, Technology Initiatives


slavitch@objectworld.com


PSTN:  

+1.888.398.9698

x225


Fax:

+1.613.599.7457

 


Skype:       

 Objectworld   

x225

 <skype:Objectworld> 

 

 

 

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
Sent: Tuesday, April 03, 2007 8:57 AM
To: Michael Slavitch
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); David R
Oran; p2prg@ietf.org; sipping@ietf.org; zhuxian
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario

 

 

 

Michael Slavitch wrote:

> Sorry for being late into this discussion, but client-server based VM 

> isn't truly client-server anymore in anything but the smallest or most 

> monolithic of enterprise networks, in fact the reality is that most if 

> not all enterprise networks contain just peers and superpeers with the 

> difference being partially a marketing decision by the vendors, as you 

> can charge much more for the servers, and a policy decision made either 

> automatically by a software deployment system or by IT staff which wants 

> to place supernodes with data sinks on appropriate equipment.

 

I'm sorry, but I don't understand the point you are trying to make 

above. You are trying to draw some sort of distinction, but I don't get 

it. Can you try again.

 

                Thanks,

                Paul

 

> In a 

> highly distributed environment there are potentially hundreds of 

> possible data sinks for a given application, with the sink based on 

> subnet or geographic location or balanced load, this can change rapidly 

> over time and does.

> 

> In the case of the Microsoft environment such policy is administered and 

> published between supernodes, ie servers, by Active Directory.  It is 

> advertised to mere peers through DNS.  There was much discussion a while 

> ago about building service discovery environment using DNS instead of a 

> P2P DHT.  It can be argued that a case study of a P2P example done using 

> DNS is any large Windows Server 2003 based Microsoft network with many 

> servers and many more clients that also run applications themselves and 

> are not just dumb terminals. This is almost certainly always the case in 

> all enterprises. The big difference between C/S SIP and P2PSIP is 

> automation. What is true is that the square peg in round hole of 

> overloading DNS makes deployments clumsy and brittle within the 

> enterprise domain and completely unmanageable and unpublishable outside 

> the firewall which is why the buck stops there in current enterprise 

> networking products.

> 

> The difference between C/S and P2P is largely policy and semantics with 

> the biggest difference being that the decisions and rules are highly 

> distributed.  Apart from that they are not just friends, they are 

> fraternal twins.

> 

> Regards

> 

> Michael Slavitch

> 

>  

> 

> 

> corp_2colour 

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://www.objec
tworld.com/>

> 

>  

> 

>             

> 

> 308 Legget Dr.

> Ottawa Ontario

> K2K 1Y6 Canada

> 

>             

> 

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://maps.goog
le.ca/maps?f=q%26hl=en%26q=308%2BLegget%2BDrive%2BOttawa%2BOntario%2BK2K%2B1
Y6%26layer=%26sll=45.341061,-75.904541%26sspn=0.007119,0.023839%26ie=UTF8%26
z=18%26ll=45.341061,-75.904541%26spn=0.00178,0.00596%26t=h%26om=1>

> 

>             

> 

>  

> 

> Michael Slavitch             

> 

> Lead, Technology Initiatives

> 

> slavitch@objectworld.com <mailto:slavitch@objectworld.com>

> 

>             

> 

> PSTN: 

> 

>             

> 

> +1.888.398.9698

> 

>             

> 

> x225

> 

> Fax:

> 

>             

> 

> +1.613.599.7457

> 

>             

> 

>  

> 

> Skype:      

> 

>             

> 

>   Objectworld 

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20M
SFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20
MME.EML/>   

> 

> 

>             

> 

> x225

> 

>             

> 

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20M
SFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20
MME.EML/>

> 

>             

> 

>  

> 

>  

> 

> 

 

 

-- 

BEGIN-ANTISPAM-VOTING-LINKS

------------------------------------------------------

 

Teach CanIt if this mail (ID 657805) is spam:

Spam:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=s

Not spam:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=n

Forget vote:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=f

------------------------------------------------------

END-ANTISPAM-VOTING-LINKS

 

  _____  

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete this information from your
system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely those of
the author and may not represent those of Objectworld Communications Corp.

  _____  


Spam
<http://canitpro-int.objectworld.com/canit/b.php?i=657949&m=5b6a6dc0fe34&c=s
> 
Not
<http://canitpro-int.objectworld.com/canit/b.php?i=657949&m=5b6a6dc0fe34&c=n
>  spam
Forget
<http://canitpro-int.objectworld.com/canit/b.php?i=657949&m=5b6a6dc0fe34&c=f
>  previous vote

  _____  

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete this information from your
system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely those of
the author and may not represent those of Objectworld Communications Corp.


------=_NextPart_001_1E07_01C7769F.E4C51F70
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns1=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
chartworld.com/>

> 

>  

> 

>             

> 

> 308 Legget Dr.

> Ottawa Ontario

> K2K 1Y6 Canada

> 

>             

> 

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://maps.goog
le.ca/maps?f=q%26hl=en%26q=308%2BLegget%2BDrive%2BOttawa%2BOntario%2BK2K%2B1
Y6%26layer=%26sll=45.341061,-75.904541%26sspn=0.007119,0.023839%26ie=UTF8%26
z=18%26ll=45.341061,-75.904541%26spn=0.00178,0.00596%26t=h%26om=1>

> 

>             

> 

>  

> 

> Michael Slavitch             

> 

> Lead, Technology Initiatives

> 

> slavitch@objectworld.com <mailto:slavitch@objectworld.com>

> 

>             

> 

> PSTN: 

> 

>             

> 

> +1.888.398.9698

> 

>             

> 

> x225

> 

> Fax:

> 

>             

> 

> +1.613.599.7457

> 

>             

> 

>  

> 

> Skype:      

> 

>             

> 

>   Objectworld 

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20M
SFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20
MME.EML/>   

> 

> 

>             

> 

> x225

> 

>             

> 

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20M
SFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20
MME.EML/>

> 

>             

> 

>  

> 

>  

> 

> 

 

 

-- 

BEGIN-ANTISPAM-VOTING-LINKS

------------------------------------------------------

 

Teach CanIt if this mail (ID 657805) is spam:

Spam:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=s

Not spam:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=n

Forget vote:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=f

------------------------------------------------------

END-ANTISPAM-VOTING-LINKS

 

  _____  

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete this information from your
system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely those of
the author and may not represent those of Objectworld Communications Corp.

  _____  


Spam
<http://canitpro-int.objectworld.com/canit/b.php?i=657949&m=5b6a6dc0fe34&c=s
> 
Not
<http://canitpro-int.objectworld.com/canit/b.php?i=657949&m=5b6a6dc0fe34&c=n
>  spam
Forget
<http://canitpro-int.objectworld.com/canit/b.php?i=657949&m=5b6a6dc0fe34&c=f
>  previous vote

  _____  

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete this information from your
system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely those of
the author and may not represent those of Objectworld Communications Corp.


------=_NextPart_001_1E07_01C7769F.E4C51F70
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns1=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
chartworld.com/>

> 

>  

> 

>             

> 

> 308 Legget Dr.

> Ottawa Ontario

> K2K 1Y6 Canada

> 

>             

> 

>
<https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=http://maps.goog
le.ca/maps?f=q%26hl=en%26q=308%2BLegget%2BDrive%2BOttawa%2BOntario%2BK2K%2B1
Y6%26layer=%26sll=45.341061,-75.904541%26sspn=0.007119,0.023839%26ie=UTF8%26
z=18%26ll=45.341061,-75.904541%26spn=0.00178,0.00596%26t=h%26om=1>

> 

>             

> 

>  

> 

> Michael Slavitch             

> 

> Lead, Technology Initiatives

> 

> slavitch@objectworld.com <mailto:slavitch@objectworld.com>

> 

>             

> 

> PSTN: 

> 

>             

> 

> +1.888.398.9698

> 

>             

> 

> x225

> 

> Fax:

> 

>             

> 

> +1.613.599.7457

> 

>             

> 

>  

> 

> Skype:      

> 

>             

> 

>   Objectworld 

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20M
SFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20
MME.EML/>   

> 

> 

>             

> 

> x225

> 

>             

> 

>
<https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Nortel,%20M
SFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME%20and%20
MME.EML/>

> 

>             

> 

>  

> 

>  

> 

> 

 

 

-- 

BEGIN-ANTISPAM-VOTING-LINKS

------------------------------------------------------

 

Teach CanIt if this mail (ID 657805) is spam:

Spam:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=s

Not spam:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=n

Forget vote:
http://canitpro-int.objectworld.com/canit/b.php?i=657805&m=2eb1fdee55b7&c=f

------------------------------------------------------

END-ANTISPAM-VOTING-LINKS

 

  _____  

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete this information from your
system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely those of
the author and may not represent those of Objectworld Communications Corp.

  _____  


Spam
<http://canitpro-int.objectworld.com/canit/b.php?i=657949&m=5b6a6dc0fe34&c=s
> 
Not
<http://canitpro-int.objectworld.com/canit/b.php?i=657949&m=5b6a6dc0fe34&c=n
>  spam
Forget
<http://canitpro-int.objectworld.com/canit/b.php?i=657949&m=5b6a6dc0fe34&c=f
>  previous vote

  _____  

This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client 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 immediately reply to the sender and delete this information from your
system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be unlawful.

Any views, opinions and content presented in this e-mail are solely those of
the author and may not represent those of Objectworld Communications Corp.


------=_NextPart_001_1E07_01C7769F.E4C51F70
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns1=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PostalCode"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}
p.MSOPLAINTEXT
	{mso-style-priority:99;}
li.MSOPLAINTEXT
	{mso-style-priority:99;}
div.MSOPLAINTEXT
	{mso-style-priority:99;}
p
	{mso-style-priority:99;}
p.MSOACETATE
	{mso-style-priority:99;}
li.MSOACETATE
	{mso-style-priority:99;}
div.MSOACETATE
	{mso-style-priority:99;}
p.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
li.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
div.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
span.PLAINTEXTCHAR
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR
	{mso-style-priority:99;}
span.PLAINTEXTCHAR0
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR0
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;}
@font-face
	{font-family:Consolas;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;}
p.msolistparagraph, li.msolistparagraph, div.msolistparagraph
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
span.plaintextchar
	{font-family:Consolas;}
span.balloontextchar
	{font-family:Tahoma;}
span.plaintextchar0
	{font-family:Calibri;}
span.balloontextchar0
	{font-family:Tahoma;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:Calibri;
	color:black;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle28
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:846867197;
	mso-list-type:hybrid;
	mso-list-template-ids:-139805038 -1714783482 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-bset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PostalCode"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}
p.MSOPLAINTEXT
	{mso-style-priority:99;}
li.MSOPLAINTEXT
	{mso-style-priority:99;}
div.MSOPLAINTEXT
	{mso-style-priority:99;}
p
	{mso-style-priority:99;}
p.MSOACETATE
	{mso-style-priority:99;}
li.MSOACETATE
	{mso-style-priority:99;}
div.MSOACETATE
	{mso-style-priority:99;}
p.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
li.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
div.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
span.PLAINTEXTCHAR
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR
	{mso-style-priority:99;}
span.PLAINTEXTCHAR0
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR0
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;}
@font-face
	{font-family:Consolas;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;}
p.msolistparagraph, li.msolistparagraph, div.msolistparagraph
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
span.plaintextchar
	{font-family:Consolas;}
span.balloontextchar
	{font-family:Tahoma;}
span.plaintextchar0
	{font-family:Calibri;}
span.balloontextchar0
	{font-family:Tahoma;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:Calibri;
	color:black;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle28
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:846867197;
	mso-list-type:hybrid;
	mso-list-template-ids:-139805038 -1714783482 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-bset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PostalCode"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}
p.MSOPLAINTEXT
	{mso-style-priority:99;}
li.MSOPLAINTEXT
	{mso-style-priority:99;}
div.MSOPLAINTEXT
	{mso-style-priority:99;}
p
	{mso-style-priority:99;}
p.MSOACETATE
	{mso-style-priority:99;}
li.MSOACETATE
	{mso-style-priority:99;}
div.MSOACETATE
	{mso-style-priority:99;}
p.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
li.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
div.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
span.PLAINTEXTCHAR
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR
	{mso-style-priority:99;}
span.PLAINTEXTCHAR0
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR0
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;}
@font-face
	{font-family:Consolas;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;}
p.msolistparagraph, li.msolistparagraph, div.msolistparagraph
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
span.plaintextchar
	{font-family:Consolas;}
span.balloontextchar
	{font-family:Tahoma;}
span.plaintextchar0
	{font-family:Calibri;}
span.balloontextchar0
	{font-family:Tahoma;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:Calibri;
	color:black;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle28
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:846867197;
	mso-list-type:hybrid;
	mso-list-template-ids:-139805038 -1714783482 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1197936675;
	mso-list-type:hybrid;
	mso-list-template-ids:-2146642626 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Have you actually ever built an =
enterprise
telephony system? &nbsp;Maybe installed a recent =
one?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Look, every product can be =
improved, and I
do agree with Henry that the enterprise telephony folks haven&#8217;t =
caught on
(or haven&#8217;t figured out how to make money on) presence and IM
integration.&nbsp; I think there have been plenty of attempts to allow =
other
app integration that have failed pretty much completely despite what we =
would
have thought.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>My take on this is that enterprise =
IT
(which now owns phones), demands the level of feature set the enterprise =
PBX
guys give them, are pretty much afraid of doing any serious app =
interaction except
in call centers, and would not see any inherent benefit in p2p.&nbsp; =
&#8220;Self
Organizing&#8221; is not what we are talking about any more than current
systems are self organizing. &nbsp;In current systems, except in the =
very
largest systems, there is a server, you configure it, and plug the =
phones in. &nbsp;They
self configure.&nbsp; The configuration on the server is compidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1197936675;
	mso-list-type:hybrid;
	mso-list-template-ids:-2146642626 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Have you actually ever built an =
enterprise
telephony system? &nbsp;Maybe installed a recent =
one?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Look, every product can be =
improved, and I
do agree with Henry that the enterprise telephony folks haven&#8217;t =
caught on
(or haven&#8217;t figured out how to make money on) presence and IM
integration.&nbsp; I think there have been plenty of attempts to allow =
other
app integration that have failed pretty much completely despite what we =
would
have thought.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>My take on this is that enterprise =
IT
(which now owns phones), demands the level of feature set the enterprise =
PBX
guys give them, are pretty much afraid of doing any serious app =
interaction except
in call centers, and would not see any inherent benefit in p2p.&nbsp; =
&#8220;Self
Organizing&#8221; is not what we are talking about any more than current
systems are self organizing. &nbsp;In current systems, except in the =
very
largest systems, there is a server, you configure it, and plug the =
phones in. &nbsp;They
self configure.&nbsp; The configuration on the server is compidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1197936675;
	mso-list-type:hybrid;
	mso-list-template-ids:-2146642626 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Have you actually ever built an =
enterprise
telephony system? &nbsp;Maybe installed a recent =
one?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Look, every product can be =
improved, and I
do agree with Henry that the enterprise telephony folks haven&#8217;t =
caught on
(or haven&#8217;t figured out how to make money on) presence and IM
integration.&nbsp; I think there have been plenty of attempts to allow =
other
app integration that have failed pretty much completely despite what we =
would
have thought.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>My take on this is that enterprise =
IT
(which now owns phones), demands the level of feature set the enterprise =
PBX
guys give them, are pretty much afraid of doing any serious app =
interaction except
in call centers, and would not see any inherent benefit in p2p.&nbsp; =
&#8220;Self
Organizing&#8221; is not what we are talking about any more than current
systems are self organizing. &nbsp;In current systems, except in the =
very
largest systems, there is a server, you configure it, and plug the =
phones in. &nbsp;They
self configure.&nbsp; The configuration on the server is complex, but =
it&#8217;s
not something that needs a large staff; in most enterprises I know, =
there is
usually one guy (or sometimes one per site) who maintains the =
configuration
part time. &nbsp;How much less do you think you could get, and what do =
you
think you could simplify with p2p?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Skype?&nbsp; In an =
enterprise?&nbsp; Try
talking to YOUR staff about that idea and see how far you get.&nbsp; =
&nbsp;Skype
does not provide the feature set enterprise wants.&nbsp; You can claim =
the
staff doesn&#8217;t know its business I =
suppose.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Let&#8217;s take one simple =
example: dial
plans. &nbsp;Every enterprise has one.&nbsp; Does Skype?&nbsp; What =
would p2p
do for dial plans that any current system can&#8217;t do right =
now?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>What is the problem: dial plans are =
evil,
we should get rid of them, or dial plans are useful, and SOMEONE has to =
use
some kind of tool to configure them, and having done that, assign =
extension
numbers within the dial plan? &nbsp;What would p2p do for us?&nbsp; =
D&#8217;you
want users configuring their own extensions? =
&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I see many benefits to p2p, but =
significantly
simplifying enterprise deployment isn&#8217;t one of =
them.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Brian<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Henry =
Sinnreich
[mailto:hsinnrei@adobe.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007 5:53
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Michael Slavitch; =
Brian Rosen;
Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; p2prg@ietf.org; sipping@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2Prg]
RE: [Sipping] Simple SIP usage scenario</span></flex, but =
it&#8217;s
not something that needs a large staff; in most enterprises I know, =
there is
usually one guy (or sometimes one per site) who maintains the =
configuration
part time. &nbsp;How much less do you think you could get, and what do =
you
think you could simplify with p2p?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Skype?&nbsp; In an =
enterprise?&nbsp; Try
talking to YOUR staff about that idea and see how far you get.&nbsp; =
&nbsp;Skype
does not provide the feature set enterprise wants.&nbsp; You can claim =
the
staff doesn&#8217;t know its business I =
suppose.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Let&#8217;s take one simple =
example: dial
plans. &nbsp;Every enterprise has one.&nbsp; Does Skype?&nbsp; What =
would p2p
do for dial plans that any current system can&#8217;t do right =
now?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>What is the problem: dial plans are =
evil,
we should get rid of them, or dial plans are useful, and SOMEONE has to =
use
some kind of tool to configure them, and having done that, assign =
extension
numbers within the dial plan? &nbsp;What would p2p do for us?&nbsp; =
D&#8217;you
want users configuring their own extensions? =
&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I see many benefits to p2p, but =
significantly
simplifying enterprise deployment isn&#8217;t one of =
them.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Brian<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Henry =
Sinnreich
[mailto:hsinnrei@adobe.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007 5:53
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Michael Slavitch; =
Brian Rosen;
Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; p2prg@ietf.org; sipping@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2Prg]
RE: [Sipping] Simple SIP usage scenario</span></flex, but =
it&#8217;s
not something that needs a large staff; in most enterprises I know, =
there is
usually one guy (or sometimes one per site) who maintains the =
configuration
part time. &nbsp;How much less do you think you could get, and what do =
you
think you could simplify with p2p?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Skype?&nbsp; In an =
enterprise?&nbsp; Try
talking to YOUR staff about that idea and see how far you get.&nbsp; =
&nbsp;Skype
does not provide the feature set enterprise wants.&nbsp; You can claim =
the
staff doesn&#8217;t know its business I =
suppose.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Let&#8217;s take one simple =
example: dial
plans. &nbsp;Every enterprise has one.&nbsp; Does Skype?&nbsp; What =
would p2p
do for dial plans that any current system can&#8217;t do right =
now?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>What is the problem: dial plans are =
evil,
we should get rid of them, or dial plans are useful, and SOMEONE has to =
use
some kind of tool to configure them, and having done that, assign =
extension
numbers within the dial plan? &nbsp;What would p2p do for us?&nbsp; =
D&#8217;you
want users configuring their own extensions? =
&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I see many benefits to p2p, but =
significantly
simplifying enterprise deployment isn&#8217;t one of =
them.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Brian<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Henry =
Sinnreich
[mailto:hsinnrei@adobe.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007 5:53
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Michael Slavitch; =
Brian Rosen;
Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; p2prg@ietf.org; sipping@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2Prg]
RE: [Sipping] Simple SIP usage scenario</span></font><font size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I agree with Michael here. The =
voice-only PBX
is pathetic as an enterprise communication and productivity platform (no
presence, IM, no integration with apps, etc.) is also exactly the =
opposite of
what self o<st1:PersonName w:st=3D"on">rg</st1:PersonName>anizing =
systems
provide. As for the usability of those tiny screens and remembering the =
various
commands&#8230;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Why not just use Skype PC clients =
or Skype
phones instead? At least, they are WiFi and no configuration is required =
that
cannot be done by the user. And they can be used on travel as =
well.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Just think what self =
o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>anizing and usability means for the =
maintenance
headcount and budget. Not to mention the associated IT =
systems.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>P2P SIP in the enterprise is not a =
PBX
replacement any more that SIP is a PSTN replacement, though many =
decisions
makers have not given up </span></font><font size=3D2 color=3Dnavy =
face=3DWingdings><span
style=3D'font-size:10.0pt;font-family:Wingdings;color:navy'>J</span></fon=
t><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, =
Henry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Slavitch
[mailto:slavitch@objectworld.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007
12:58 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">Brian
 Rosen</st1:PersonName>; Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; Henry Sinnreich; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sont><font size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I agree with Michael here. The =
voice-only PBX
is pathetic as an enterprise communication and productivity platform (no
presence, IM, no integration with apps, etc.) is also exactly the =
opposite of
what self o<st1:PersonName w:st=3D"on">rg</st1:PersonName>anizing =
systems
provide. As for the usability of those tiny screens and remembering the =
various
commands&#8230;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Why not just use Skype PC clients =
or Skype
phones instead? At least, they are WiFi and no configuration is required =
that
cannot be done by the user. And they can be used on travel as =
well.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Just think what self =
o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>anizing and usability means for the =
maintenance
headcount and budget. Not to mention the associated IT =
systems.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>P2P SIP in the enterprise is not a =
PBX
replacement any more that SIP is a PSTN replacement, though many =
decisions
makers have not given up </span></font><font size=3D2 color=3Dnavy =
face=3DWingdings><span
style=3D'font-size:10.0pt;font-family:Wingdings;color:navy'>J</span></fon=
t><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, =
Henry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Slavitch
[mailto:slavitch@objectworld.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007
12:58 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">Brian
 Rosen</st1:PersonName>; Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; Henry Sinnreich; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sont><font size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I agree with Michael here. The =
voice-only PBX
is pathetic as an enterprise communication and productivity platform (no
presence, IM, no integration with apps, etc.) is also exactly the =
opposite of
what self o<st1:PersonName w:st=3D"on">rg</st1:PersonName>anizing =
systems
provide. As for the usability of those tiny screens and remembering the =
various
commands&#8230;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Why not just use Skype PC clients =
or Skype
phones instead? At least, they are WiFi and no configuration is required =
that
cannot be done by the user. And they can be used on travel as =
well.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Just think what self =
o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>anizing and usability means for the =
maintenance
headcount and budget. Not to mention the associated IT =
systems.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>P2P SIP in the enterprise is not a =
PBX
replacement any more that SIP is a PSTN replacement, though many =
decisions
makers have not given up </span></font><font size=3D2 color=3Dnavy =
face=3DWingdings><span
style=3D'font-size:10.0pt;font-family:Wingdings;color:navy'>J</span></fon=
t><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, =
Henry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Slavitch
[mailto:slavitch@objectworld.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007
12:58 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">Brian
 Rosen</st1:PersonName>; Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; Henry Sinnreich; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>&#8220;</span></font><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>vendors will tell you the things you can automate about
provisioning have been automated.</span></font><font color=3Dblack><span
style=3D'color:black'>&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>The vendors will tell you this =
because the
things that they automate can be summarized =
as:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l1 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3Dblack face=3DCalibri><span =
style=3D'font-size:11.0pt;color:black'><span
style=3D'mso-list:Ignore'>1.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
dir=3DLTR><font color=3Dblack><span style=3D'color:black'>&#8220;not =
much&#8221;.<o:p></o:p></span></font></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l1 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3Dblack face=3DCalibri><span =
style=3D'font-size:11.0pt;color:black'><span
style=3D'mso-list:Ignore'>2.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
dir=3DLTR><font color=3Dblack><span style=3D'color:black'>What we =
automate is our
proprietary stuff, sod the rest.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>t&#8217;s things like TN =
assignment, and
dial plans, and gateway routing, and eme<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ency
call provisioning, and permissions, and feature enabling, etc, etc that
dominate provisioning of enterprise telephony systems. &nbsp;P2P =
doesn&#8217;t
help any of that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>I strongly disagree with that. =
&nbsp;&nbsp;Look
at the documentation for products from many of the major vendors, there =
are
stacks of complex details regarding deployment,&nbsp; not very automatic =
at
all, with many of them depending on crufty TFTP or FTP with fixed file
locations for provisioning of endpoints.&nbsp; It&#8217;s =
horrible.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Secondly, &#8220;it doesn&#8217;t =
help
with any of that&#8221; is only true in a static fixed universe where =
you
provision once and go away and limit functionality to very basic =
tasks.&nbsp; &nbsp;Even
in that world the number of user change requests on a 2000 user system =
is on
the order of .5%-1% of all endpoints per day on today&#8217;s relatively =
static
systems, 10 to 20 per day, and that&#8217;s just ipping] Simple SIP usage =
scenario</span></font><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>&#8220;</span></font><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>vendors will tell you the things you can automate about
provisioning have been automated.</span></font><font color=3Dblack><span
style=3D'color:black'>&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>The vendors will tell you this =
because the
things that they automate can be summarized =
as:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l1 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3Dblack face=3DCalibri><span =
style=3D'font-size:11.0pt;color:black'><span
style=3D'mso-list:Ignore'>1.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
dir=3DLTR><font color=3Dblack><span style=3D'color:black'>&#8220;not =
much&#8221;.<o:p></o:p></span></font></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l1 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3Dblack face=3DCalibri><span =
style=3D'font-size:11.0pt;color:black'><span
style=3D'mso-list:Ignore'>2.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
dir=3DLTR><font color=3Dblack><span style=3D'color:black'>What we =
automate is our
proprietary stuff, sod the rest.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>t&#8217;s things like TN =
assignment, and
dial plans, and gateway routing, and eme<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ency
call provisioning, and permissions, and feature enabling, etc, etc that
dominate provisioning of enterprise telephony systems. &nbsp;P2P =
doesn&#8217;t
help any of that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>I strongly disagree with that. =
&nbsp;&nbsp;Look
at the documentation for products from many of the major vendors, there =
are
stacks of complex details regarding deployment,&nbsp; not very automatic =
at
all, with many of them depending on crufty TFTP or FTP with fixed file
locations for provisioning of endpoints.&nbsp; It&#8217;s =
horrible.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Secondly, &#8220;it doesn&#8217;t =
help
with any of that&#8221; is only true in a static fixed universe where =
you
provision once and go away and limit functionality to very basic =
tasks.&nbsp; &nbsp;Even
in that world the number of user change requests on a 2000 user system =
is on
the order of .5%-1% of all endpoints per day on today&#8217;s relatively =
static
systems, 10 to 20 per day, and that&#8217;s just ipping] Simple SIP usage =
scenario</span></font><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>&#8220;</span></font><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>vendors will tell you the things you can automate about
provisioning have been automated.</span></font><font color=3Dblack><span
style=3D'color:black'>&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>The vendors will tell you this =
because the
things that they automate can be summarized =
as:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l1 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3Dblack face=3DCalibri><span =
style=3D'font-size:11.0pt;color:black'><span
style=3D'mso-list:Ignore'>1.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
dir=3DLTR><font color=3Dblack><span style=3D'color:black'>&#8220;not =
much&#8221;.<o:p></o:p></span></font></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l1 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3Dblack face=3DCalibri><span =
style=3D'font-size:11.0pt;color:black'><span
style=3D'mso-list:Ignore'>2.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
dir=3DLTR><font color=3Dblack><span style=3D'color:black'>What we =
automate is our
proprietary stuff, sod the rest.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>t&#8217;s things like TN =
assignment, and
dial plans, and gateway routing, and eme<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ency
call provisioning, and permissions, and feature enabling, etc, etc that
dominate provisioning of enterprise telephony systems. &nbsp;P2P =
doesn&#8217;t
help any of that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>I strongly disagree with that. =
&nbsp;&nbsp;Look
at the documentation for products from many of the major vendors, there =
are
stacks of complex details regarding deployment,&nbsp; not very automatic =
at
all, with many of them depending on crufty TFTP or FTP with fixed file
locations for provisioning of endpoints.&nbsp; It&#8217;s =
horrible.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Secondly, &#8220;it doesn&#8217;t =
help
with any of that&#8221; is only true in a static fixed universe where =
you
provision once and go away and limit functionality to very basic =
tasks.&nbsp; &nbsp;Even
in that world the number of user change requests on a 2000 user system =
is on
the order of .5%-1% of all endpoints per day on today&#8217;s relatively =
static
systems, 10 to 20 per day, and that&#8217;s just basic stuff, done at =
gunpoint.&nbsp;
Routers used to have only static routes too, and web pages were once =
coded by
hand.&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Regards<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Michael<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<div>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:6.65in;
  border:none;border-top:solid windowtext =
1.0pt;background:white;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
  =
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><a
  href=3D"http://www.objectworld.com/" title=3D"Objectworld =
Communications"><font
  color=3Dblack><span style=3D'color:black;text-decoration:none'><img =
border=3D0
  width=3D237 height=3D42
  id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x0020_1"
  src=3D"cid:image001.jpg@01C7769F.7AEDF040" =
alt=3D"corp_2colour"></span></font></a><font
  color=3Dblack><span =
style=3D'color:black'><o:p></o:p></span></font></span></font></p>
  <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
  =
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    style=3D'font-size:11.0pt;color:black'>Michael =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    style=3D'font-size:11.0pt;color:black'>Lead, Technology =
Initiatives<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D27basic stuff, done at =
gunpoint.&nbsp;
Routers used to have only static routes too, and web pages were once =
coded by
hand.&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Regards<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Michael<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<div>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:6.65in;
  border:none;border-top:solid windowtext =
1.0pt;background:white;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
  =
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><a
  href=3D"http://www.objectworld.com/" title=3D"Objectworld =
Communications"><font
  color=3Dblack><span style=3D'color:black;text-decoration:none'><img =
border=3D0
  width=3D237 height=3D42
  id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x0020_1"
  src=3D"cid:image001.jpg@01C7769F.7AEDF040" =
alt=3D"corp_2colour"></span></font></a><font
  color=3Dblack><span =
style=3D'color:black'><o:p></o:p></span></font></span></font></p>
  <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
  =
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    style=3D'font-size:11.0pt;color:black'>Michael =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    style=3D'font-size:11.0pt;color:black'>Lead, Technology =
Initiatives<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D27basic stuff, done at =
gunpoint.&nbsp;
Routers used to have only static routes too, and web pages were once =
coded by
hand.&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Regards<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'>Michael<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<div>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:6.65in;
  border:none;border-top:solid windowtext =
1.0pt;background:white;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
  =
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><a
  href=3D"http://www.objectworld.com/" title=3D"Objectworld =
Communications"><font
  color=3Dblack><span style=3D'color:black;text-decoration:none'><img =
border=3D0
  width=3D237 height=3D42
  id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x0020_1"
  src=3D"cid:image001.jpg@01C7769F.7AEDF040" =
alt=3D"corp_2colour"></span></font></a><font
  color=3Dblack><span =
style=3D'color:black'><o:p></o:p></span></font></span></font></p>
  <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
  =
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    style=3D'font-size:11.0pt;color:black'>Michael =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    style=3D'font-size:11.0pt;color:black'>Lead, Technology =
Initiatives<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    =
style=3D'font-size:11.0pt;color:black'>slavitch@objectworld.com<o:p></o:p=
></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black;letter-spacing:-.5pt'><o:p>&nbsp;</=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
<st1:PersonName
w:st=3D"on">Brian Rosen</st1:PersonName> [mailto:br@brianrosen.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007 1:07
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Michael Slavitch; =
'Paul
Kyzivat'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> 'P2PSIP Mailing =
List';
'Michael Hammer (mhammer)'; 'David R Oran'; 'Henry Sinnreich'; =
p2p<st1:PersonName
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>;
sipping@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario<o:p></o:p></span></font></p>

</div>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I think most enterprise =
&#8220;PBX&#8221;
vendors will tell you that the things you can automate about =
provisioning have
been automated, and you won&#8217;t get much a win there. =
&nbsp;It&#8217;s
things like TN assignment, and dial plans, and gateway routing, and =
eme<st1:PersonName
w:st=3D"on">rg</st1:PersonName>ency call provisioning, and permissions, =
and
feature enabling, etc, etc that dominate provisioning of enterprise =
telephony
systems. &nbsp;P2P doesn&#8217;t help any of =
that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I worry, quite a bit, that =
perpetuating
SIP UAs (the SIP client) will perpetuate the dumb endpoint model, simply
because the way they are made now is that they are dumb endpoints. =
&nbsp;They
didn&#8217;t have to be (SIP was originally designed for smart
endpoints).&nbsp; If we make P2PSIP endpoints more closely fit the smart
endp8 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    =
style=3D'font-size:11.0pt;color:black'>slavitch@objectworld.com<o:p></o:p=
></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black;letter-spacing:-.5pt'><o:p>&nbsp;</=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
<st1:PersonName
w:st=3D"on">Brian Rosen</st1:PersonName> [mailto:br@brianrosen.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007 1:07
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Michael Slavitch; =
'Paul
Kyzivat'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> 'P2PSIP Mailing =
List';
'Michael Hammer (mhammer)'; 'David R Oran'; 'Henry Sinnreich'; =
p2p<st1:PersonName
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>;
sipping@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario<o:p></o:p></span></font></p>

</div>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I think most enterprise =
&#8220;PBX&#8221;
vendors will tell you that the things you can automate about =
provisioning have
been automated, and you won&#8217;t get much a win there. =
&nbsp;It&#8217;s
things like TN assignment, and dial plans, and gateway routing, and =
eme<st1:PersonName
w:st=3D"on">rg</st1:PersonName>ency call provisioning, and permissions, =
and
feature enabling, etc, etc that dominate provisioning of enterprise =
telephony
systems. &nbsp;P2P doesn&#8217;t help any of =
that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I worry, quite a bit, that =
perpetuating
SIP UAs (the SIP client) will perpetuate the dumb endpoint model, simply
because the way they are made now is that they are dumb endpoints. =
&nbsp;They
didn&#8217;t have to be (SIP was originally designed for smart
endpoints).&nbsp; If we make P2PSIP endpoints more closely fit the smart
endp8 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 color=3Dblack =
face=3DCalibri><span
    =
style=3D'font-size:11.0pt;color:black'>slavitch@objectworld.com<o:p></o:p=
></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black;letter-spacing:-.5pt'><o:p>&nbsp;</=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DCalibri><span
style=3D'font-size:11.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
<st1:PersonName
w:st=3D"on">Brian Rosen</st1:PersonName> [mailto:br@brianrosen.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007 1:07
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Michael Slavitch; =
'Paul
Kyzivat'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> 'P2PSIP Mailing =
List';
'Michael Hammer (mhammer)'; 'David R Oran'; 'Henry Sinnreich'; =
p2p<st1:PersonName
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>;
sipping@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario<o:p></o:p></span></font></p>

</div>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I think most enterprise =
&#8220;PBX&#8221;
vendors will tell you that the things you can automate about =
provisioning have
been automated, and you won&#8217;t get much a win there. =
&nbsp;It&#8217;s
things like TN assignment, and dial plans, and gateway routing, and =
eme<st1:PersonName
w:st=3D"on">rg</st1:PersonName>ency call provisioning, and permissions, =
and
feature enabling, etc, etc that dominate provisioning of enterprise =
telephony
systems. &nbsp;P2P doesn&#8217;t help any of =
that.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I worry, quite a bit, that =
perpetuating
SIP UAs (the SIP client) will perpetuate the dumb endpoint model, simply
because the way they are made now is that they are dumb endpoints. =
&nbsp;They
didn&#8217;t have to be (SIP was originally designed for smart
endpoints).&nbsp; If we make P2PSIP endpoints more closely fit the smart
endpoint model, then we make the peer that serves the UAs be the smart =
box in
the middle of the network.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Brian<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Slavitch
[mailto:slavitch@objectworld.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007
10:48 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; Henry Sinnreich; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
point I am making is&nbsp; that in the enterprise the actual topological
deployments of SIP clients and servers, <i><span =
style=3D'font-style:italic'>when
implemented as software on generic computing platforms</span></i>, as =
well as
the <i><span style=3D'font-style:italic'>mechanisms that make that =
deployment
happen</span></i>, are already very different world than the canonical
IMS/CSSIP one which &nbsp;assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD), &nbsp;B2BUA demarks,
network elements, and dumb fixed endpoints.&nbsp; Taking a network as a =
whole
enterprise application software using C/S SIP proxies and UA&#8217;s =
<i><span
style=3D'font-style:italic'>already</span></i> approximates something =
that is
close to what is being called P2PSIP, only in a manner that is highly
proprietary, closed, somewhat brittle and baroque, local, and ad-hoc, =
with
gaping ugly holes.&nbsp; P2P has the potential to transform =
that.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'>Some points I take from the previous =
discussion:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;that
a P2P setup will be *free*&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-oint model, then we make the peer that serves the UAs be the smart =
box in
the middle of the network.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Brian<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Slavitch
[mailto:slavitch@objectworld.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007
10:48 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; Henry Sinnreich; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
point I am making is&nbsp; that in the enterprise the actual topological
deployments of SIP clients and servers, <i><span =
style=3D'font-style:italic'>when
implemented as software on generic computing platforms</span></i>, as =
well as
the <i><span style=3D'font-style:italic'>mechanisms that make that =
deployment
happen</span></i>, are already very different world than the canonical
IMS/CSSIP one which &nbsp;assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD), &nbsp;B2BUA demarks,
network elements, and dumb fixed endpoints.&nbsp; Taking a network as a =
whole
enterprise application software using C/S SIP proxies and UA&#8217;s =
<i><span
style=3D'font-style:italic'>already</span></i> approximates something =
that is
close to what is being called P2PSIP, only in a manner that is highly
proprietary, closed, somewhat brittle and baroque, local, and ad-hoc, =
with
gaping ugly holes.&nbsp; P2P has the potential to transform =
that.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'>Some points I take from the previous =
discussion:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;that
a P2P setup will be *free*&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-oint model, then we make the peer that serves the UAs be the smart =
box in
the middle of the network.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Brian<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Michael Slavitch
[mailto:slavitch@objectworld.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 03, =
2007
10:48 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Paul Kyzivat<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> P2PSIP Mailing List; =
Michael
Hammer (mhammer); David R Oran; Henry Sinnreich; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [P2PSIP] RE: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
point I am making is&nbsp; that in the enterprise the actual topological
deployments of SIP clients and servers, <i><span =
style=3D'font-style:italic'>when
implemented as software on generic computing platforms</span></i>, as =
well as
the <i><span style=3D'font-style:italic'>mechanisms that make that =
deployment
happen</span></i>, are already very different world than the canonical
IMS/CSSIP one which &nbsp;assumes SIP as core monolithic servers, fixed
enterprise network integrated access devices (IAD), &nbsp;B2BUA demarks,
network elements, and dumb fixed endpoints.&nbsp; Taking a network as a =
whole
enterprise application software using C/S SIP proxies and UA&#8217;s =
<i><span
style=3D'font-style:italic'>already</span></i> approximates something =
that is
close to what is being called P2PSIP, only in a manner that is highly
proprietary, closed, somewhat brittle and baroque, local, and ad-hoc, =
with
gaping ugly holes.&nbsp; P2P has the potential to transform =
that.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'>Some points I take from the previous =
discussion:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;that
a P2P setup will be *free*&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-list:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;
</span></font></span></span></font><![endif]><span dir=3DLTR>&nbsp;A P2P =
network
may not be free, but the setup (provisioning) will be free, and =
automatic.&nbsp;
This is a major benefit only partially achieved in enterprise =
networks,&nbsp; a
benefit of great value to enterprises that is underserved by =
vendors.&nbsp;
There is no benefit in requiring complex deployments where automation =
can take
its place.&nbsp; Deployment is almost always the biggest cost of =
enterprise
systems dwarfing the cost of the systems =
themselves.<o:p></o:p></span></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I
think this depends greatly on what expectations / contractual guarantees =
the
enterprise has. It&#8217;s unclear to me what guarantees can be made =
about a
P2PSIP network will be able to make, and its unclear what kind of
infrastructure would be installed by/for someone willing to make =
guarantees.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-list:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;
</span></font></span></span></font><![endif]><span dir=3DLTR>That is why =
&#8216;expectations/contractual
guarantees&#8217; need to be built into the automation that exists in =
the P2P
overlay.&nbsp; Self-calculation of such performance metrics is already =
there in
all enterprise devices, the difference being that while WMI/SNMP data is =
merely
collected a P2PSIP network can act automatically based on the metrics =
within
their own nodes, there is a collective &#8216;aha&#8217; that forces =
behavior
change based on strict contracts, aka rules.&nbsp; An <st1:place =
w:st=3D"on">SLA</st1:place>
is easier to maintain if the objects can react accordingly, for example =
a node
with degrading service can notify that it is on the decline forcing =
others to
take over.&nbsp; <o:p></o:p></span></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>There
is an old traffic engineering axiom about service guarantees: it can be
achieved through two ways: over engineering or &nbsp;automation.&nbsp; =
P2PSIP
allows for automation.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;David
Oran wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I'm
not saying this can't be made to work, only that it isn't immediately =
obvious
that it has advantages over a classic application/server =
approach.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
immediately obvious advantage to me is standardized ruggedized =
automation that
has economies of scale and operates over multiple domains, eliminating =
the need
for over-engineering,&nbsp; detailed fussy provisioning,&nbslist:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;
</span></font></span></span></font><![endif]><span dir=3DLTR>&nbsp;A P2P =
network
may not be free, but the setup (provisioning) will be free, and =
automatic.&nbsp;
This is a major benefit only partially achieved in enterprise =
networks,&nbsp; a
benefit of great value to enterprises that is underserved by =
vendors.&nbsp;
There is no benefit in requiring complex deployments where automation =
can take
its place.&nbsp; Deployment is almost always the biggest cost of =
enterprise
systems dwarfing the cost of the systems =
themselves.<o:p></o:p></span></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I
think this depends greatly on what expectations / contractual guarantees =
the
enterprise has. It&#8217;s unclear to me what guarantees can be made =
about a
P2PSIP network will be able to make, and its unclear what kind of
infrastructure would be installed by/for someone willing to make =
guarantees.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-list:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;
</span></font></span></span></font><![endif]><span dir=3DLTR>That is why =
&#8216;expectations/contractual
guarantees&#8217; need to be built into the automation that exists in =
the P2P
overlay.&nbsp; Self-calculation of such performance metrics is already =
there in
all enterprise devices, the difference being that while WMI/SNMP data is =
merely
collected a P2PSIP network can act automatically based on the metrics =
within
their own nodes, there is a collective &#8216;aha&#8217; that forces =
behavior
change based on strict contracts, aka rules.&nbsp; An <st1:place =
w:st=3D"on">SLA</st1:place>
is easier to maintain if the objects can react accordingly, for example =
a node
with degrading service can notify that it is on the decline forcing =
others to
take over.&nbsp; <o:p></o:p></span></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>There
is an old traffic engineering axiom about service guarantees: it can be
achieved through two ways: over engineering or &nbsp;automation.&nbsp; =
P2PSIP
allows for automation.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;David
Oran wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I'm
not saying this can't be made to work, only that it isn't immediately =
obvious
that it has advantages over a classic application/server =
approach.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
immediately obvious advantage to me is standardized ruggedized =
automation that
has economies of scale and operates over multiple domains, eliminating =
the need
for over-engineering,&nbsp; detailed fussy provisioning,&nbslist:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;
</span></font></span></span></font><![endif]><span dir=3DLTR>&nbsp;A P2P =
network
may not be free, but the setup (provisioning) will be free, and =
automatic.&nbsp;
This is a major benefit only partially achieved in enterprise =
networks,&nbsp; a
benefit of great value to enterprises that is underserved by =
vendors.&nbsp;
There is no benefit in requiring complex deployments where automation =
can take
its place.&nbsp; Deployment is almost always the biggest cost of =
enterprise
systems dwarfing the cost of the systems =
themselves.<o:p></o:p></span></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I
think this depends greatly on what expectations / contractual guarantees =
the
enterprise has. It&#8217;s unclear to me what guarantees can be made =
about a
P2PSIP network will be able to make, and its unclear what kind of
infrastructure would be installed by/for someone willing to make =
guarantees.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><font
size=3D2 face=3DCalibri><span style=3D'font-size:11.0pt'><span =
style=3D'mso-list:Ignore'>-<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;
</span></font></span></span></font><![endif]><span dir=3DLTR>That is why =
&#8216;expectations/contractual
guarantees&#8217; need to be built into the automation that exists in =
the P2P
overlay.&nbsp; Self-calculation of such performance metrics is already =
there in
all enterprise devices, the difference being that while WMI/SNMP data is =
merely
collected a P2PSIP network can act automatically based on the metrics =
within
their own nodes, there is a collective &#8216;aha&#8217; that forces =
behavior
change based on strict contracts, aka rules.&nbsp; An <st1:place =
w:st=3D"on">SLA</st1:place>
is easier to maintain if the objects can react accordingly, for example =
a node
with degrading service can notify that it is on the decline forcing =
others to
take over.&nbsp; <o:p></o:p></span></p>

<p class=3DMsoPlainText style=3D'margin-left:.25in'><font size=3D2 =
face=3DCalibri><span
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>There
is an old traffic engineering axiom about service guarantees: it can be
achieved through two ways: over engineering or &nbsp;automation.&nbsp; =
P2PSIP
allows for automation.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;David
Oran wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&#8220;I'm
not saying this can't be made to work, only that it isn't immediately =
obvious
that it has advantages over a classic application/server =
approach.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>The
immediately obvious advantage to me is standardized ruggedized =
automation that
has economies of scale and operates over multiple domains, eliminating =
the need
for over-engineering,&nbsp; detailed fussy provisioning,&nbsp; and an =
army of
people doing basic monitoring and care-and-feeding.&nbsp; Automation is =
the
key, a dynamic statistical network vs. one that is fixed and assumed
deterministic will always win out over time given a fractal operating
environment.&nbsp;&nbsp; This is being done in fits and starts in the
enterprise data center.&nbsp;&nbsp; P2PSIP makes it much more =
comprehensive.&nbsp;
&nbsp;People want the world to be predictable and deterministic,&nbsp; =
and C/S
based systems reflect that. That is the biggest problem P2P faces =
because it
flies in the face of tradition. =
&nbsp;&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:6.65in;
  border:none;border-top:solid windowtext =
1.0pt;background:white;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><a
  href=3D"http://www.objectworld.com/" title=3D"Objectworld =
Communications"><font
  color=3Dblack><span =
style=3D'color:windowtext;text-decoration:none'><img
  border=3D0 width=3D237 height=3D42
  =
id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f=
_x005f_x005f_x005f_x005f_x005f_x0020_1"
  src=3D"cid:image001.jpg@01C7769F.7AEDF040" =
alt=3D"corp_2colour"></span></font></a><o:p></o:p></span></font></p>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><st1:Street w:st=3D"on"><st1:address =
w:st=3D"on"><font size=3D2
    face=3DCalibri><span style=3D'font-size:11.0pt'>308 Legget =
Dr</span></font></st1:address></st1:Street>.
  <br>
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State w:st=3D"on">Ontario</st1:State>
   <br>
<st1:PostalCode w:st=3D"on">K2K 1Y6</st1:PostalCode> <st1:country-region =
w:st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a
  =
href=3D"http://maps.google.ca/maps?f=3Dq&amp;hl=3Den&amp;q=3D308+Legget+D=
rive+Ottawa+Ontario+K2K+1Y6&amp;layer=3D&amp;sll=3D45.341061,-75.904541&a=
mp;sspn=3D0.007119,0.023839&amp;ie=3DUTF8&amp;z=3D18&amp;ll=3D45.341061,-=
75.904541&amp;spn=3D0.00178,0.00596&amp;t=3Dh&amp;om=3D1"
  title=3D"308 Legget Drive Ottawa Ontario K2K 1Y6"><font =
color=3Dblap; and an =
army of
people doing basic monitoring and care-and-feeding.&nbsp; Automation is =
the
key, a dynamic statistical network vs. one that is fixed and assumed
deterministic will always win out over time given a fractal operating
environment.&nbsp;&nbsp; This is being done in fits and starts in the
enterprise data center.&nbsp;&nbsp; P2PSIP makes it much more =
comprehensive.&nbsp;
&nbsp;People want the world to be predictable and deterministic,&nbsp; =
and C/S
based systems reflect that. That is the biggest problem P2P faces =
because it
flies in the face of tradition. =
&nbsp;&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:6.65in;
  border:none;border-top:solid windowtext =
1.0pt;background:white;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><a
  href=3D"http://www.objectworld.com/" title=3D"Objectworld =
Communications"><font
  color=3Dblack><span =
style=3D'color:windowtext;text-decoration:none'><img
  border=3D0 width=3D237 height=3D42
  =
id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f=
_x005f_x005f_x005f_x005f_x005f_x0020_1"
  src=3D"cid:image001.jpg@01C7769F.7AEDF040" =
alt=3D"corp_2colour"></span></font></a><o:p></o:p></span></font></p>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><st1:Street w:st=3D"on"><st1:address =
w:st=3D"on"><font size=3D2
    face=3DCalibri><span style=3D'font-size:11.0pt'>308 Legget =
Dr</span></font></st1:address></st1:Street>.
  <br>
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State w:st=3D"on">Ontario</st1:State>
   <br>
<st1:PostalCode w:st=3D"on">K2K 1Y6</st1:PostalCode> <st1:country-region =
w:st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a
  =
href=3D"http://maps.google.ca/maps?f=3Dq&amp;hl=3Den&amp;q=3D308+Legget+D=
rive+Ottawa+Ontario+K2K+1Y6&amp;layer=3D&amp;sll=3D45.341061,-75.904541&a=
mp;sspn=3D0.007119,0.023839&amp;ie=3DUTF8&amp;z=3D18&amp;ll=3D45.341061,-=
75.904541&amp;spn=3D0.00178,0.00596&amp;t=3Dh&amp;om=3D1"
  title=3D"308 Legget Drive Ottawa Ontario K2K 1Y6"><font =
color=3Dblap; and an =
army of
people doing basic monitoring and care-and-feeding.&nbsp; Automation is =
the
key, a dynamic statistical network vs. one that is fixed and assumed
deterministic will always win out over time given a fractal operating
environment.&nbsp;&nbsp; This is being done in fits and starts in the
enterprise data center.&nbsp;&nbsp; P2PSIP makes it much more =
comprehensive.&nbsp;
&nbsp;People want the world to be predictable and deterministic,&nbsp; =
and C/S
based systems reflect that. That is the biggest problem P2P faces =
because it
flies in the face of tradition. =
&nbsp;&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D"100%"
 style=3D'width:100.0%;border-collapse:collapse'>
 <tr>
  <td width=3D638 colspan=3D4 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:6.65in;
  border:none;border-top:solid windowtext =
1.0pt;background:white;padding:0in 5.4pt 0in 5.4pt'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><a
  href=3D"http://www.objectworld.com/" title=3D"Objectworld =
Communications"><font
  color=3Dblack><span =
style=3D'color:windowtext;text-decoration:none'><img
  border=3D0 width=3D237 height=3D42
  =
id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f=
_x005f_x005f_x005f_x005f_x005f_x0020_1"
  src=3D"cid:image001.jpg@01C7769F.7AEDF040" =
alt=3D"corp_2colour"></span></font></a><o:p></o:p></span></font></p>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><st1:Street w:st=3D"on"><st1:address =
w:st=3D"on"><font size=3D2
    face=3DCalibri><span style=3D'font-size:11.0pt'>308 Legget =
Dr</span></font></st1:address></st1:Street>.
  <br>
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State w:st=3D"on">Ontario</st1:State>
   <br>
<st1:PostalCode w:st=3D"on">K2K 1Y6</st1:PostalCode> <st1:country-region =
w:st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a
  =
href=3D"http://maps.google.ca/maps?f=3Dq&amp;hl=3Den&amp;q=3D308+Legget+D=
rive+Ottawa+Ontario+K2K+1Y6&amp;layer=3D&amp;sll=3D45.341061,-75.904541&a=
mp;sspn=3D0.007119,0.023839&amp;ie=3DUTF8&amp;z=3D18&amp;ll=3D45.341061,-=
75.904541&amp;spn=3D0.00178,0.00596&amp;t=3Dh&amp;om=3D1"
  title=3D"308 Legget Drive Ottawa Ontario K2K 1Y6"><font =
color=3Dblack><span
  style=3D'color:windowtext;text-decoration:none'><img border=3D0 =
width=3D29
  height=3D29
  =
id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f=
_x005f_x005f_x005f_x005f_x005f_x0020_6"
  =
src=3D"cid:image002.jpg@01C7769F.7AEDF040"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
    =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Lead,
    Technology Initiatives<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>slavitch@objectworld.com<o:p></o:p></span></fo=
nt></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0 width=3D204
   style=3D'width:152.85pt;border-collapse:collapse'>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>PSTN:&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.888.398.9698<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Fax:<o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.613.599.7457<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<a
    href=3D"Skype:Objectworld">Objectworld</a>&nbsp;&nbsp; =
<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNck><span
  style=3D'color:windowtext;text-decoration:none'><img border=3D0 =
width=3D29
  height=3D29
  =
id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f=
_x005f_x005f_x005f_x005f_x005f_x0020_6"
  =
src=3D"cid:image002.jpg@01C7769F.7AEDF040"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
    =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Lead,
    Technology Initiatives<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>slavitch@objectworld.com<o:p></o:p></span></fo=
nt></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0 width=3D204
   style=3D'width:152.85pt;border-collapse:collapse'>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>PSTN:&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.888.398.9698<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Fax:<o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.613.599.7457<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<a
    href=3D"Skype:Objectworld">Objectworld</a>&nbsp;&nbsp; =
<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNck><span
  style=3D'color:windowtext;text-decoration:none'><img border=3D0 =
width=3D29
  height=3D29
  =
id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f=
_x005f_x005f_x005f_x005f_x005f_x0020_6"
  =
src=3D"cid:image002.jpg@01C7769F.7AEDF040"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
 <tr>
  <td width=3D286 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:214.55pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0
   style=3D'border-collapse:collapse'>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
    =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Lead,
    Technology Initiatives<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D278 valign=3Dtop style=3D'width:208.4pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>slavitch@objectworld.com<o:p></o:p></span></fo=
nt></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D211 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:158.05pt;background:white;
  padding:0in 0in 0in 0in'>
  <table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0 width=3D204
   style=3D'width:152.85pt;border-collapse:collapse'>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>PSTN:&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.888.398.9698<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Fax:<o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>+1.613.599.7457<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>
    </td>
   </tr>
   <tr>
    <td width=3D42 valign=3Dtop style=3D'width:31.25pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    <o:p></o:p></span></font></p>
    </td>
    <td width=3D131 valign=3Dtop style=3D'width:98.05pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<a
    href=3D"Skype:Objectworld">Objectworld</a>&nbsp;&nbsp; =
<o:p></o:p></span></font></p>
    </td>
    <td width=3D31 valign=3Dtop style=3D'width:23.55pt;padding:0in 0in =
0in 0in'>
    <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a =
href=3D"skype:Objectworld"
  title=3DObjectworld><font color=3Dblack><span =
style=3D'color:windowtext;text-decoration:
  none'><img border=3D0 width=3D26 height=3D26
  =
id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f=
_x005f_x005f_x005f_x005f_x005f_x0020_3"
  =
src=3D"cid:image003.jpg@01C7769F.7AEDF040"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>-----Original
Message-----<br>
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] <br>
Sent: Tuesday, April 03, 2007 8:57 AM<br>
To: Michael Slavitch<br>
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); =
David R
Oran; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>;
zhuxian<br>
Subject: Re: [P2P<st1:PersonName w:st=3D"on">rg</st1:PersonName>] RE: =
[Sipping]
Simple SIP usage scenario<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Sorry for being late into this discussion, but client-server based VM =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
isn't truly client-server anymore in anything but the smallest or most =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
monolithic of enterprise networks, in fact the reality is that most if =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
not all enterprise networks contain just peers and superpeers with the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
difference being partially a marketing decision by the vendors, as you =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
can cha<st1:PersonName w:st=3D"on">rg</st1:PersonName>e much more for =
the
servers, and a policy decision made either <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automatically by a software deployment system or by IT staff which wants =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0ptormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a =
href=3D"skype:Objectworld"
  title=3DObjectworld><font color=3Dblack><span =
style=3D'color:windowtext;text-decoration:
  none'><img border=3D0 width=3D26 height=3D26
  =
id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f=
_x005f_x005f_x005f_x005f_x005f_x0020_3"
  =
src=3D"cid:image003.jpg@01C7769F.7AEDF040"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>-----Original
Message-----<br>
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] <br>
Sent: Tuesday, April 03, 2007 8:57 AM<br>
To: Michael Slavitch<br>
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); =
David R
Oran; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>;
zhuxian<br>
Subject: Re: [P2P<st1:PersonName w:st=3D"on">rg</st1:PersonName>] RE: =
[Sipping]
Simple SIP usage scenario<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Sorry for being late into this discussion, but client-server based VM =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
isn't truly client-server anymore in anything but the smallest or most =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
monolithic of enterprise networks, in fact the reality is that most if =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
not all enterprise networks contain just peers and superpeers with the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
difference being partially a marketing decision by the vendors, as you =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
can cha<st1:PersonName w:st=3D"on">rg</st1:PersonName>e much more for =
the
servers, and a policy decision made either <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automatically by a software deployment system or by IT staff which wants =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0ptormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>x225<o:p></o:p></span></font></p>
    </td>
   </tr>
  </table>
  <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
  style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>
  </td>
  <td width=3D137 valign=3Dtop bgcolor=3Dwhite =
style=3D'width:102.6pt;background:white;
  padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><font =
size=3D2
  face=3DCalibri><span style=3D'font-size:11.0pt'><a =
href=3D"skype:Objectworld"
  title=3DObjectworld><font color=3Dblack><span =
style=3D'color:windowtext;text-decoration:
  none'><img border=3D0 width=3D26 height=3D26
  =
id=3D"Picture_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f_x005f=
_x005f_x005f_x005f_x005f_x005f_x0020_3"
  =
src=3D"cid:image003.jpg@01C7769F.7AEDF040"></span></font></a><o:p></o:p><=
/span></font></p>
  </td>
  <td width=3D10 style=3D'width:.1in;padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;<o:p></o:p></span></font></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>-----Original
Message-----<br>
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] <br>
Sent: Tuesday, April 03, 2007 8:57 AM<br>
To: Michael Slavitch<br>
Cc: Henry Sinnreich; P2PSIP Mailing List; Michael Hammer (mhammer); =
David R
Oran; p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>;
zhuxian<br>
Subject: Re: [P2P<st1:PersonName w:st=3D"on">rg</st1:PersonName>] RE: =
[Sipping]
Simple SIP usage scenario<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Michael
Slavitch wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Sorry for being late into this discussion, but client-server based VM =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
isn't truly client-server anymore in anything but the smallest or most =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
monolithic of enterprise networks, in fact the reality is that most if =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
not all enterprise networks contain just peers and superpeers with the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
difference being partially a marketing decision by the vendors, as you =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
can cha<st1:PersonName w:st=3D"on">rg</st1:PersonName>e much more for =
the
servers, and a policy decision made either <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automatically by a software deployment system or by IT staff which wants =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
to place supernodes with data sinks on appropriate =
equipment.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>I'm
sorry, but I don't understand the point you are trying to make =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>above.
You are trying to draw some sort of distinction, but I don't get =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>it.
Can you try again.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Paul<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In a <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
highly distributed environment there are potentially hundreds of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
possible data sinks for a given application, with the sink based on =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
subnet or geographic location or balanced load, this can change rapidly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
over time and does.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In the case of the Microsoft environment such policy is administered and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
published between supernodes, ie servers, by Active Directory.&nbsp; It =
is <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
advertised to mere peers through DNS.&nbsp; There was much discussion a =
while <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
ago about building service discovery environment using DNS instead of a =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
P2P DHT.&nbsp; It can be a<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ued that
a case study of a P2P example done using <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
DNS is any la<st1:PersonName w:st=3D"on">rg</st1:PersonName>e Windows =
Server 2003
based Microsoft network with many <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
servers and many more clients that also run applications themselves and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
are not just dumb terminals. This is almost certainly always the case in =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
all enterprises. The big difference between C/S SIP and P2PSIP is =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automation. What is true is that the square peg in round hole of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
overloading DNS makes deployments clumsy and brittle within the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
enterprise domain and completely unmanageable and unpublishable outside =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the firewall which is why the buck stops there in current enterprise =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
networking products.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
The difference between C/S and P2P is la<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ely
policy and semantics with <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the biggest difference being that the decisions and rules are highly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
distributed.&nbsp; Apart from that they are not just friends, they are =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
fraternal twins.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
corp_2colour <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://w=
ww.objectworld.com/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:Street w:st=3D"on"><st1:address w:st=3D"on">308 Legget =
Dr</st1:address></st1:Street>.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State =
w:st=3D"on">Ontario</st1:State></st1:place><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
K2K 1Y6 <st1:place w:st=3D"on"><st1:country-region =
w:st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></span></fo=
nt></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://m=
aps.google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2B=
Ontario%2BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.00=
7119,0.023839%26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.=
00178,0.00596%26t=3Dh%26om=3D1&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Lead, Technology Initiatives<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
slavitch@objectworld.com =
&lt;mailto:slavitch@objectworld.com&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
PSTN: <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalib'>&gt;
to place supernodes with data sinks on appropriate =
equipment.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>I'm
sorry, but I don't understand the point you are trying to make =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>above.
You are trying to draw some sort of distinction, but I don't get =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>it.
Can you try again.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Paul<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In a <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
highly distributed environment there are potentially hundreds of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
possible data sinks for a given application, with the sink based on =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
subnet or geographic location or balanced load, this can change rapidly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
over time and does.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In the case of the Microsoft environment such policy is administered and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
published between supernodes, ie servers, by Active Directory.&nbsp; It =
is <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
advertised to mere peers through DNS.&nbsp; There was much discussion a =
while <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
ago about building service discovery environment using DNS instead of a =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
P2P DHT.&nbsp; It can be a<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ued that
a case study of a P2P example done using <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
DNS is any la<st1:PersonName w:st=3D"on">rg</st1:PersonName>e Windows =
Server 2003
based Microsoft network with many <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
servers and many more clients that also run applications themselves and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
are not just dumb terminals. This is almost certainly always the case in =
<o:'>&gt;
to place supernodes with data sinks on appropriate =
equipment.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>I'm
sorry, but I don't understand the point you are trying to make =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>above.
You are trying to draw some sort of distinction, but I don't get =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>it.
Can you try again.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Paul<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In a <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
highly distributed environment there are potentially hundreds of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
possible data sinks for a given application, with the sink based on =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
subnet or geographic location or balanced load, this can change rapidly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
over time and does.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
In the case of the Microsoft environment such policy is administered and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
published between supernodes, ie servers, by Active Directory.&nbsp; It =
is <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
advertised to mere peers through DNS.&nbsp; There was much discussion a =
while <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
ago about building service discovery environment using DNS instead of a =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
P2P DHT.&nbsp; It can be a<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ued that
a case study of a P2P example done using <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
DNS is any la<st1:PersonName w:st=3D"on">rg</st1:PersonName>e Windows =
Server 2003
based Microsoft network with many <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
servers and many more clients that also run applications themselves and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
are not just dumb terminals. This is almost certainly always the case in =
<o:ri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.888.398.9698<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Fax:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.613.599.7457<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;&nbsp;
Objectworld <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>--
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>BEGIN-ANTISPAM-VOTING-LINKS<o:p></o:p></span><=
/font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Teach
CanIt if this mail (ID 657805) is spam:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Spam:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Ds<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Not
spam:&nbsp;&nbsp;&nbsp;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Dn<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Fo<st1:PersonName
w:st=3D"on">rg</st1:PersonName>et vote: =
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Df<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>END-ANTISPAM-VOTING-LINKS<o:p></o:p></span></f=
ont></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>This
transmission (including any attachments) may contain confidential =
information,
privileged material (including material protected by the =
solicitor-client 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 immediately reply =
to the
sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended =
recipients is
not authorized and may be unlawful.<o:p></o:p></span></font></p>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>Any views,
opinions and content presented in this e-mail are solely those of the =
author
and may not represent those of Objectworld Communications =
Corp.<o:p></o:p></span></font></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D4
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:13.5pt;font-family:
"Times New Roman";color:black;background:white'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><font size=3D4 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:13.5pt;font-family:"Times New =
Roman";color:black;background:
white'><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Ds">Spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Dn">Not
spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Df">Forget
previous vote</a></span></font><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

</div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>This
transmission (including any attachments) may contain confidential =
information,
privileged material (including material protected by the =
solicitor-client 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 immediately reply =
to the
sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended =
recipients is
not authorized and may be unlawful.<o:p></o:p></span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>Any
views, opinions and content presented in this e-mail are solely those of =
the
author and may not represent those of Objectworld Communications =
Corp.<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------=_NextPart_001_1E07_01C7769F.E4C51F70--

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: image/jpeg;
	name="image003.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image003.jpg@01C7769F.7AEDF040>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAaABoDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1Ga7l
kZ2SdokV2VQgXJwcEnIPcHpVSTW7uHqYHA7bCCfxz/Skuiv9qSwFtitMoA/3gMn8yab/AGWls8lx
qTBbeE5HP+s/z6V4051nJ8j2ervov+AYty6GrpuqQ6lGxQFJE++hPT/EVdrjtEuvN8S+ZEuxJjIS
Pbkj+Qrsa7MDiHXpcz3Tt6lwlzIyNa0hr7E8GPNAwy5xvHb8axbu31G6jSO6W5ZYRwPKbH1JAwTX
Y0VFfAQqyck7X37MUqaZx2k6cf7QheCQMUcFipyFAPOfTjj8a7GiitcLhY4eLinuOMeVH//Z

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: image/jpeg;
	name="image002.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image002.jpg@01C7769F.7AEDF040>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAdAB0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD0/VNW
WCU20cnllQPMkAyVz0A9/wCVUylrNEHWKOZjysk+XP5nmua1W8kXU7pZDg+e/wCW7A/TFPs9UmmU
Wquq8fK3cf4168cNywTR5EsTzTakdDFqT2M20l2j6mMknI7lc8j6dK6GORJY1kjYMrDII7ivOruS
eB0lklDljgHNdh4ald9Fi39iwX/dycfpiufFUVGKmjowtZyk4M5/xhoUzXDX9qhbf/rFA5z6j1rj
o5pILhGIHytzzivZnRZFKsAQazptCspX3NGM/SnQx0qceWSuia+AjUnzxdmef2ttd61f5XcIQcBs
cAe3qa9J0+1W0s44VGAqgAegotrC3th8ic+tWq56+IlWavokdFDDxop21b6n/9k=

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: image/jpeg;
	name="image001.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image001.jpg@01C7769F.7AEDF040>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6
+0EbNruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHExlWYK4wpGMhue
leLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9clnAj17UWQKd3+kNjPb+tN/s+6bR
21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHN
R/8AAlv8a9P8NWv/AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1U9W1W00TSrjU76Qx
29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GFE6eqnPpzXoHzp19FZniHXIPDmhXOr3Mc
ksNsoZkjxuOSBxn61ieHPiLpniHVV0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc
3dpDNClvcvbMJQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq39uaT
FqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jHGM/M3Psa2tC1uy8RaPb6
rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFreaPqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+
w3Vj5hYeRdJskXBxyKANGisRvFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6v
RZpDhd+8n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA2fxg0W4n
Tz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumtpPNA+Zh3GD0oA26KiuJltraW
dgSsSFyB1IAzXE6N8WtG1a7tIZNP1GxivZPKt7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8
kKcE9M5IrD1H4h6Hpltazzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+
jtPI2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1LvgEhv5V4sNKivt
c+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m1u7X7PGJ4vL+zRoFMe3J3YHY5x9a
1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej
3PAy/C1qWJTmmkt+vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLNd74l0OHxJ4evNInk
MSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZrKOGLYFXGMse5wf/AK9ekfLl74p/8k31
j/rmv/oa1xfhqXUW+IHhl/E0MVuf7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5
C4YHp+Fc5oHgDVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu11WK/
m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYHA9OBQByXjWXV4fi9oj6F
b29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRqZ0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xa
WxgBkg8zqWycHjo1dFoNtq1ppaQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs
9CsdDjg8OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/gK2/CHhuL
wn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ceFpvFmlWtlDdJbNBdpcFnUsCF
B44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1
Lx54N/4TPT7K2FwsDWt0sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/
AJoeP+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6Wv+oH+7/SvnjT
59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrzofC+5XwYNFXUoReQ6l9vt7nyzhD6
YznpmgD0RFCIqDooArz34S/e8Uf9hmWvQk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2
gYsC2SMnOOOOKAO41X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689GHQ1lT+EdCuQBLYK2
CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgBumKworm4ESATyYCj+M0j3M5KZnk4bj5z
Xjey97c+4WK/dr3e39bG/ChiiCEjIz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5
OW5+c+lCpbu45YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckxNyf9
9q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRR
QAUUUUAFFFFAH//Z

------=_NextPart_000_1E06_01C7769F.E4C51F70--



--===============0513198450==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0513198450==--



From sipping-bounces@ietf.org Thu Apr 05 08:05:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZQgF-0006lm-QE; Thu, 05 Apr 2007 08:03:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ6wU-0000k7-F9; Wed, 04 Apr 2007 10:58:34 -0400
Received: from exprod6og52.obsmtp.com ([64.18.1.185])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HZ6jQ-0006Ms-J7; Wed, 04 Apr 2007 10:45:11 -0400
Received: from source ([192.150.11.134]) by exprod6ob52.postini.com
	([64.18.5.12]) with SMTP; Wed, 04 Apr 2007 07:45:02 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l34EiQD1028170; Wed, 4 Apr 2007 07:44:33 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l34EinI9007073; Wed, 4 Apr 2007 07:44:49 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 4 Apr 2007 07:44:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 4 Apr 2007 07:44:08 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223ADF38@namail5.corp.adobe.com>
In-Reply-To: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: P2P SIPp></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
all enterprises. The big difference between C/S SIP and P2PSIP is =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automation. What is true is that the square peg in round hole of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
overloading DNS makes deployments clumsy and brittle within the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
enterprise domain and completely unmanageable and unpublishable outside =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the firewall which is why the buck stops there in current enterprise =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
networking products.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
The difference between C/S and P2P is la<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ely
policy and semantics with <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the biggest difference being that the decisions and rules are highly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
distributed.&nbsp; Apart from that they are not just friends, they are =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
fraternal twins.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
corp_2colour <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://w=
ww.objectworld.com/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
all enterprises. The big difference between C/S SIP and P2PSIP is =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
automation. What is true is that the square peg in round hole of =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
overloading DNS makes deployments clumsy and brittle within the =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
enterprise domain and completely unmanageable and unpublishable outside =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the firewall which is why the buck stops there in current enterprise =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
networking products.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
The difference between C/S and P2P is la<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>ely
policy and semantics with <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
the biggest difference being that the decisions and rules are highly =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
distributed.&nbsp; Apart from that they are not just friends, they are =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
fraternal twins.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael Slavitch<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
corp_2colour <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://w=
ww.objectworld.com/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11 service assurance (was Simple SIP usage scenario)
Thread-Index: Acd1fDvzIhowLornTwyehPLXZ9zr5AA/ypd/ABGlquA=
References: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: <colin.pons@kpn.com>, <pkyzivat@cisco.com>
X-OriginalArrivalTime: 04 Apr 2007 14:44:54.0268 (UTC)
	FILETIME=[CEC11BC0:01C776C7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8cc9f19007352bcbade9ec25b8f17862
X-Mailman-Approved-At: Thu, 05 Apr 2007 08:03:04 -0400
Cc: sipping@ietf.org, p2prg@ietf.org, oran@cisco.com, p2psip@ietf.org,
	mhammer@cisco.com
Subject: [Sipping] P2P SIP service assurance (was Simple SIP usage scenario)
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1723679838=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1723679838==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C776C7.CE6A1169"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C776C7.CE6A1169
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Colin, Paul,

=20

Thanks for raising the valid issue about service assurance.=20

As engineers, we know the service assurance is more than a piece of
legal paper and must be based on the following:

=20

-          Adequate bandwidth,

-          Geographic diversity,

-          Simplicity; so things can be managed,

-          Security that can be audited,

-          Safe data retention: Replication and the geographic diversity
of peer nodes of the overlay,

-          Economy of scale: All peers have software with identical
behavior,

-          No configuration is required or possible. The customer just
plugs in the gateway box. This is real service automation.

-          Cost containment: P2P self configuration is unbeatable. Count
all the savings in CAPEX and OPEX by not having any network based VoIP
infrastructure. Save all that electricity and real estate in the data
centers.

-          Flexibility for new applications: The API between SIP and the
DHT overlay,

-          No lock-in from single source: The applications are in the
endpoints. Buy them from anywhere.

-          Automatic updates from the application provider: This is
current PC SW state of the art and works for both the (1) P2P software
in the access device and (2) for the application software, such as
presence, IM, voice, multimedia, etc. No or minimal is staff required.

-          Last but not least, besides SIP enabled communications, the
overlay can also serve for many other applications for your users:
Content distribution, application layer multicast for conferences,
directory search, IM+A/V chat rooms, name services, etc.

=20

All of the above can be easily implemented by porting well documented
open source software into the residential access box or in the
integrated access device (IAD) for enterprises. Just check out
http://opendht.org/ and other similar sites.

=20

Please don't take my word for it, just make for yourself a comparison
table for your network. If you can't share the comparison with the list,
can you share it with me in private? :-)

=20

*       as an employee of a carrier

=20

I worked most of my career for carriers, so that's what prompted the
above considerations.

=20

Thanks, Henry

=20

________________________________

From: colin.pons@kpn.com [mailto:colin.pons@kpn.com]=20
Sent: Wednesday, April 04, 2007 12:38 AM
To: pkyzivat@cisco.com; Henry Sinnreich
Cc: p2psip@ietf.org; mhammer@cisco.com; oran@cisco.co.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:Street w:st=3D"on"><st1:address w:st=3D"on">308 Legget =
Dr</st1:address></st1:Street>.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State =
w:st=3D"on">Ontario</st1:State></st1:place><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
K2K 1Y6 <st1:place w:st=3D"on"><st1:country-region =
w:st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></span></fo=
nt></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://m=
aps.google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2B=
Ontario%2BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.00=
7119,0.023839%26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.=
00178,0.00596%26t=3Dh%26om=3D1&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Lead, Technology Initiatives<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
slavitch@objectworld.com =
&lt;mailto:slavitch@objectworld.com&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
PSTN: <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalib.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:Street w:st=3D"on"><st1:address w:st=3D"on">308 Legget =
Dr</st1:address></st1:Street>.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Ottawa</st1:City> =
<st1:State =
w:st=3D"on">Ontario</st1:State></st1:place><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
K2K 1Y6 <st1:place w:st=3D"on"><st1:country-region =
w:st=3D"on">Canada</st1:country-region></st1:place><o:p></o:p></span></fo=
nt></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchweb/bin/redir.asp?URL=3Dhttp://m=
aps.google.ca/maps?f=3Dq%26hl=3Den%26q=3D308%2BLegget%2BDrive%2BOttawa%2B=
Ontario%2BK2K%2B1Y6%26layer=3D%26sll=3D45.341061,-75.904541%26sspn=3D0.00=
7119,0.023839%26ie=3DUTF8%26z=3D18%26ll=3D45.341061,-75.904541%26spn=3D0.=
00178,0.00596%26t=3Dh%26om=3D1&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Michael =
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Lead, Technology Initiatives<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
slavitch@objectworld.com =
&lt;mailto:slavitch@objectworld.com&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
PSTN: <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibm; p2prg@ietf.org;
sipping@ietf.org
Subject: RE: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage
scenario

=20

Henry,

I like your idea of deploying sip peers in edge devices. However, as an
employee of a carrier I would like to see how a carrier is able to
provide service asurance to be able to provide compliant handling. Many
of our customers do not understand how to install these gateways
themselves, let alone how to troubleshoot.

This is even more important for enterprises, which often  insist on SLAs
which include troubleshoot resolution limits.

-----Original Message-----
From: "Paul Kyzivat" <pkyzivat@cisco.com>
To: "Henry Sinnreich" <hsinnrei@adobe.com>
Cc: "P2PSIP Mailing List" <p2psip@ietf.org>; "Michael Hammer (mhammer)"
<mhammer@cisco.com>; "David R Oran" <oran@cisco.com>; "p2prg@ietf.org"
<p2prg@ietf.org>; "sipping@ietf.org" <sipping@ietf.org>
Sent: 3-4-07 01:11
Subject: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario



Henry Sinnreich wrote:
> Paul,
>
>> I more or less agree with the final conclusion below.
>
> This is good starting point to discuss some usage scenarios.
>
> Putting on my former hat as an employee for a carrier, I cannot
overlook
> the following:
>
> P2P SIP implemented correctly in the residential access box or cable
> set-top box indeed is a good or better replacement for the entire VoIP
> network infrastructure (cost, operations, new services, etc).
> Integrated access devices for the enterprise can probably play a
similar
> role, not to mention existing P2P PBX products (please refer to all
the
> advantages of P2P that need not repeated here).
>
> What do people think of these three usage scenarios for P2P SIP:
> - SIP peer in the DSL access device,
> - SIP peer in the cable access device,

These seem quite reasonable, assuming that a device connected at this
point is able to function properly as a peer. (I haven't been following
what the assumptions are about required network capabilities of peers.)

> - SIP peer in enterprise network integrated access device (IAD).

I think this depends greatly on what expectations / contractual
guarantees the enterprise has. Its unclear to me what guarantees can be
made about a P2PSIP network will be able to make, and its unclear what
kind of infrastructure would be installed by/for someone willing to make
guarantees.

        Paul

> Note that these examples imply very low churn for the peers and add
the
> data retention resilience of P2P (geographic diversity is native and
> mobile, etc.). Incidentally, NAT traversal may also not be a problem,
or
> at least an easier problem.
>
> What do you all think?
>
> I have taken the liberty to copy the P2P SIP list, since the low churn
> scenarios are of interest for the DHT selection. Or just pick the same
> DHT for all scenarios anyway? I don't think so.
>
> Thanks, Henry
>
>
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Friday, March 30, 2007 6:31 PM
> To: Eunsoo Shim
> Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
> p2prg@ietf.org; sipping@ietf.org; zhuxian
> Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
>
> I more or less agree with the final conclusion below.
>
> My main point here is that P2P and C/S need not be enemies. Nor is a
> total C/S system necessarily evil. What is most evil is *bundling* of
> services that prevents freedom of choice.
>
> I think I would be quite happy with a SP that provides a
registrar/proxy
>
> and allows me to provide all other features as I see fit - by taking
> them ala carte from the SP, or subscribing to them from one or more
> other SPs, or by providing them myself via appliances I own. If that
> registrar/proxy was replaced by a P2P sip community, the differences,
if
>
> any, would hopefully be more a function of the implementation and the
> business models of those involved than the architecture.
>
> (I gather the general assumption is that a P2P setup will be *free*.
But
>
> I have a hard time believing that. If most of the usage is by mobile
> devices that can't be peers, thri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.888.398.9698<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Fax:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.613.599.7457<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;&nbsp;
Objectworld <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=ri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.888.398.9698<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Fax:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
+1.613.599.7457<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
Skype:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;&nbsp;
Objectworld <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
x225<o:p></o:p></span></font></p>

<p class=en somebody will have to pay for enough
> peers to support them. If it isn't free, then how is it better than a
> well engineered C/S system?)
>
> So I think the key thing here is that some features will require
getting
>
> some help from another node. There ought to be the option to pick a
> different source for each helper you require, and an ability for it
all
> to play together.
>
>       Paul
>
> Eunsoo Shim wrote:
>> Please see my inline comment.
>>
>> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com
>> <mailto:pkyzivat@cisco.com>> wrote:
>>
>>
>>
>>     Henry Sinnreich wrote:
>>      > David Oran wrote (with regard to voice mail):
>>      >
>>      >> I'm not saying this can't be made to work, only that it isn't
>>      > immediately >obvious that it has advantages over a classic
>>     application
>>      > server >approach.
>>      >
>>      > The answer for VM is "it depends":
>>      >
>>
>>
>> I agree. It really depends. Certainly there are tradeoffs.
>>
>>      > There are several commercial P2P IP PBX solutions without any
>>     server for
>>      > VM or anything else. No doubt the IT organization appreciates
> just
>>      > having to plug in the IP phones and GWY to the PSTN without
any
>>      > configuration ever for VM or any other PBX feature.
>>
>>     I don't understand. Are you saying they don't have VM, or that
> they
>>     don't have a *server* for VM?
>>
>>
>> I guess they don't have a  *server* for  VM.
>>
>>      > For public P2P SIP networks there are two more scenarios where
> VM can
>>      > reside (and without ever spending one cent on VM servers + IT
>>     systems):
>>      >
>>      > - In Cable and DSL service provider networks: The residential
>>     router can
>>      > act as a voice recorder
>>
>>     That is simply an example of the user having an appliance of his
> own
>>     that provides VM service.
>>
>>      > and P2P can cover the not too frequent cases,
>>      > where the router is not in operation, so the data is backed up
> in
>>     other
>>      > peer residential gateways (encrypted).
>>
>>     I guess I just need to have more info about how this would work
> before I
>>     will be convinced it is feasible and trustworthy.
>>
>>
>> Well, 'trustworthy' could be  considered in many angles.
>> If it is about privacy of the message, a public key based encryption
>> would provide acceptable privacy.
>> If it is about reliability of the message delivery, well, a P2P based
>> asynchronous message delivery (like VM) is most likely less reliable
>> than a well managed server based system.
>> However, my experience with Skype's asynchronous message delivery was
>> not bad. Actually I don't see any significant difference between it
> and
>> my cellular service provider's VM service. :-)
>> Reliability is always a challenge for P2P, for sure. But, I believe
it
>
>> is feasible to build a P2P system for VM acceptable for many
> scenarios.
>>      > - In mobile networks: The VM can reside in quite stable peers
>>     inside the
>>      > wireless base station network. The peers in the base station
> network
>>      > need no configuration, etc.
>>
>>     I don't understand. I guess that could be true if the peers are
> willing
>>     to store an arbitrary amount of VM indefinitely for anybody. Is
> that
>>     believable?
>>
>>
>> It depends.
>> In a very nice environment where all the peers are willing to
> cooperate
>> at their best, the peers will store as much as they can. In a tough
>> environment, the situation will be different.
>>
>>     This seems to translate to a model where it is assumed that those
> nodes
>>     that are on most of the time will be willing to provide VM
storage
> for
>>     those nodes that aren't on most of the time.
>>
>>
>> This is again related to reliability of P2P systems or topics like
> free
>> riders and reputation.
>> A P2P system is a community or society. To be simple, if many of the
>> members are bad, the community won't work well. If the majority of
the
>
>> members are good, the community will work well or reasonably.
>>
>>      > Ad3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>--
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>BEGIN-ANTISPAM-VOTING-LINKS<o:p></o:p></span><=
/font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Teach
CanIt if this mail (ID 657805) is spam:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Spam:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Ds<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Not
spam:&nbsp;&nbsp;&nbsp;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Dn<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Fo<st1:PersonName
w:st=3D"on">rg</st1:PersonName>et vote: =
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Df<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>END-ANTISPAM-VOTING-LINKS<o:p></o:p></span></f=
ont></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&lt;https://firewall.objectworld.com/exchange/slavitch/Sent%20Items/Norte=
l,%20MSFT%20chase%20carriers%20with%20new%20hosted%20offering%20for%20SME=
%20and%20MME.EML/&gt;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>&gt;
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>--
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>BEGIN-ANTISPAM-VOTING-LINKS<o:p></o:p></span><=
/font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Teach
CanIt if this mail (ID 657805) is spam:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Spam:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Ds<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Not
spam:&nbsp;&nbsp;&nbsp;
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Dn<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>Fo<st1:PersonName
w:st=3D"on">rg</st1:PersonName>et vote: =
http://canitpro-int.objectworld.com/canit/b.php?i=3D657805&amp;m=3D2eb1fd=
ee55b7&amp;c=3Df<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>----------------------------------------------=
--------<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'>END-ANTISPAM-VOTING-LINKS<o:p></o:p></span></f=
ont></p>

<p class=3DMsoPlainText><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =d to this the conferencing capability coming from p2p
> application
>>      > layer multicast, the SIP e2e control capabilities (for such as
>>      > auto-attendant, agent workstation, etc.) and one has to wonder
> why IT
>>      > networks, public VoIP networks and end users should support
the
> huge
>>      > cost of hand engineering, testing, monitoring, maintaining
> server
>>     based
>>      > VoIP networks. P2P self configuration is nothing less that
> automation
>>      > applied to VoIP, plus the shifting of computing to the
> endpoints,
>>     where
>>      > there is an abundance of unused CPU, storage, bandwidth and
>>     electricity.
>>      >
>>      > Eric Burger also notes IM changes completely the usage for VM
> and may
>>      > make unnecessary to place calls on VM in the first place.
>>
>>     I find this more promising.
>>
>>         =20
>>
>>
>> In overall, are we discussing if P2P systems based VM can work? I
> think
>> it can work.  Just it depends on many things.
>> If it is not super-reliable, should we disregard it? I would say no.
>>
>> On the other hand, do we have to abandon client server based VM and
>> switch to P2P system based VM? It is upto each of us.
>> Client server based VM systems are already there.
>> So why don't we work on P2P based VM now?
>>=20
>> Thanks.
>>
>> Eunsoo
>

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www1.ietf.org/mailman/listinfo/p2psip


------_=_NextPart_001_01C776C7.CE6A1169
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>RE: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage =
scenario</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft
-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:319894744;
	mso-list-type:hybrid;
	mso-list-template-ids:1009410942 -487147662 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Arial;
	mso-fareast-font-family:"Times New Roman";}
@list l1
	{mso-list-id:1298990762;
	mso-list-type:hybrid;
	mso-list-template-ids:1053834342 -46605914 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@l
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>This
transmission (including any attachments) may contain confidential =
information,
privileged material (including material protected by the =
solicitor-client 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 immediately reply =
to the
sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended =
recipients is
not authorized and may be unlawful.<o:p></o:p></span></font></p>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>Any views,
opinions and content presented in this e-mail are solely those of the =
author
and may not represent those of Objectworld Communications =
Corp.<o:p></o:p></span></font></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D4
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:13.5pt;font-family:
"Times New Roman";color:black;background:white'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><font size=3D4 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:13.5pt;font-family:"Times New =
Roman";color:black;background:
white'><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Ds">Spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Dn">Not
spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Df">Forget
previous vote</a></span></font><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

</div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>This
transmission (including any attachments) may contain confidential =
information,
privileged material (including material protected by the =
solicitor-client 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 immediately reply =
to the
sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended =
recipients is
not authorized and may be unlawful.<o:p></o:p></span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>Any
views, opinions and content presented in this e-mail are solely those of =
the
author and may not represent those of Objectworld Communications =
Corp.<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------=_NextPart_001_1E07_01C7769F.E4C51F70--

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: image/jpeg;
	name="image003.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image003.jpg@01C7769F.7AEDF040>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAaABoDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMX
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>This
transmission (including any attachments) may contain confidential =
information,
privileged material (including material protected by the =
solicitor-client 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 immediately reply =
to the
sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended =
recipients is
not authorized and may be unlawful.<o:p></o:p></span></font></p>

<p><font size=3D1 face=3D"Times New Roman"><span =
style=3D'font-size:7.5pt'>Any views,
opinions and content presented in this e-mail are solely those of the =
author
and may not represent those of Objectworld Communications =
Corp.<o:p></o:p></span></font></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D4
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:13.5pt;font-family:
"Times New Roman";color:black;background:white'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><font size=3D4 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:13.5pt;font-family:"Times New =
Roman";color:black;background:
white'><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Ds">Spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Dn">Not
spam</a><br>
<a
href=3D"http://canitpro-int.objectworld.com/canit/b.php?i=3D657949&amp;m=3D=
5b6a6dc0fe34&amp;c=3Df">Forget
previous vote</a></span></font><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

</div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>This
transmission (including any attachments) may contain confidential =
information,
privileged material (including material protected by the =
solicitor-client 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 immediately reply =
to the
sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended =
recipients is
not authorized and may be unlawful.<o:p></o:p></span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>Any
views, opinions and content presented in this e-mail are solely those of =
the
author and may not represent those of Objectworld Communications =
Corp.<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------=_NextPart_001_1E07_01C7769F.E4C51F70--

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: image/jpeg;
	name="image003.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image003.jpg@01C7769F.7AEDF040>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAaABoDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXist l1:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:Arial;
	color:navy;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Colin, =
Paul,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks for raising the valid issue =
about
service assurance. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>As engineers, we know the service
assurance is more than a piece of legal paper and must be based on the
following:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Adequate
bandwidth,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Geographic
diversity,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Simplicity;
so things can be managed,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Security
that <u>can be audited</u>,<o:p></o:p></span></font></p>

<p class=3DMsoGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1Ga7l
kZ2SdokV2VQgXJwcEnIPcHpVSTW7uHqYHA7bCCfxz/Skuiv9qSwFtitMoA/3gMn8yab/AGWls8lx
qTBbeE5HP+s/z6V4051nJ8j2ervov+AYty6GrpuqQ6lGxQFJE++hPT/EVdrjtEuvN8S+ZEuxJjIS
Pbkj+Qrsa7MDiHXpcz3Tt6lwlzIyNa0hr7E8GPNAwy5xvHb8axbu31G6jSO6W5ZYRwPKbH1JAwTX
Y0VFfAQqyck7X37MUqaZx2k6cf7QheCQMUcFipyFAPOfTjj8a7GiitcLhY4eLinuOMeVH//Z

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: image/jpeg;
	name="image002.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image002.jpg@01C7769F.7AEDF040>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAdAB0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD0/VNW
WCU20cnllQPMkAyVz0A9/wCVUylrNEHWKOZjysk+XP5nmua1W8kXU7pZDg+e/wCW7A/TFPs9UmmU
Wquq8fK3cf4168cNywTR5EsTzTakdDFqT2M20l2j6mMknI7lc8j6dK6GORJY1kjYMrDII7ivOruS
eB0lklDljgHNdh4ald9Fi39iwX/dycfpiufFUVGKmjowtZyk4M5/xhoUzXDX9qhbf/rFA5z6j1rj
o5pILhGIHytzzivZnRZFKsAQazptCspX3NGM/SnQx0qceWSuia+AjUnzxdmef2ttd61f5XcIQcBs
cAe3qa9J0+1W0s44VGAqgAegotrC3th8ic+tWq56+IlWavokdFDDxop21b6n/9k=

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: image/jpeg;
	name="image001.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image001.jpg@01C7769F.7AEDF040>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6
+0EbNruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHExlWYK4wpGMhue
leLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9clnAj17UWQKd3+kNjPb+tN/s+6bR
21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHN
R/8AAlv8a9P8NWv/AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1U9W1W00TSrjU76Qx
29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GFE6eqnPpzXoHzp19FZniHXIPDmhXOr3Mc
ksNsoZkjxuOSBxn61ieHPiLpniHVV0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc
3dpDNClvcvbMJQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq39uaT
FqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jHGM/M3Psa2tC1uy8RaPb6
rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFreaPqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+
w3Vj5hYeRdJskXBxyKANGisRvFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6v
RZpDhd+8n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA2fxg0W4n
Tz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumtpPNA+Zh3GD0oA26KiuJltraW
dgSsSFyB1IAzXE6N8WGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD1Ga7l
kZ2SdokV2VQgXJwcEnIPcHpVSTW7uHqYHA7bCCfxz/Skuiv9qSwFtitMoA/3gMn8yab/AGWls8lx
qTBbeE5HP+s/z6V4051nJ8j2ervov+AYty6GrpuqQ6lGxQFJE++hPT/EVdrjtEuvN8S+ZEuxJjIS
Pbkj+Qrsa7MDiHXpcz3Tt6lwlzIyNa0hr7E8GPNAwy5xvHb8axbu31G6jSO6W5ZYRwPKbH1JAwTX
Y0VFfAQqyck7X37MUqaZx2k6cf7QheCQMUcFipyFAPOfTjj8a7GiitcLhY4eLinuOMeVH//Z

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: image/jpeg;
	name="image002.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image002.jpg@01C7769F.7AEDF040>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAdAB0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD0/VNW
WCU20cnllQPMkAyVz0A9/wCVUylrNEHWKOZjysk+XP5nmua1W8kXU7pZDg+e/wCW7A/TFPs9UmmU
Wquq8fK3cf4168cNywTR5EsTzTakdDFqT2M20l2j6mMknI7lc8j6dK6GORJY1kjYMrDII7ivOruS
eB0lklDljgHNdh4ald9Fi39iwX/dycfpiufFUVGKmjowtZyk4M5/xhoUzXDX9qhbf/rFA5z6j1rj
o5pILhGIHytzzivZnRZFKsAQazptCspX3NGM/SnQx0qceWSuia+AjUnzxdmef2ttd61f5XcIQcBs
cAe3qa9J0+1W0s44VGAqgAegotrC3th8ic+tWq56+IlWavokdFDDxop21b6n/9k=

------=_NextPart_000_1E06_01C7769F.E4C51F70
Content-Type: image/jpeg;
	name="image001.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image001.jpg@01C7769F.7AEDF040>

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAqAO0DASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDIh8R6
+0EbNruoklASftLelNn8T65GhX+3tRDsDtAuGJzWZbTDyIFKOu5FAJHBOKbPNHExlWYK4wpGMhue
leLz1Oe12fc+wwyoqXKvuRtL4h1/aM65qGcc/wCkt/jUK+J9clnAj17UWQKd3+kNjPb+tN/s+6bR
21cRqbBZ/s5l3j7309OcZrNjnihmNuZ1IVNy5I4HTFHNVW7YvZYOTSjGNk7PRbm1/wAJDrv/AEHN
R/8AAlv8a9P8NWv/AAkHgnTJNRlaebZJmWUB3Od69T7H9BXjMc7jY0wCq4yMA/KfQ17d8PiD4G0w
joUb/wBDaurCObk+Z3PJziFGNODpxSd+1jV0rTRpds8Inecu+8u/XoB/ICr1U9W1W00TSrjU76Qx
29shdyBk/QD1PSuc8NfEbTvEWqpph0++0+4mi863F3GFE6eqnPpzXoHzp19FZniHXIPDmhXOr3Mc
ksNsoZkjxuOSBxn61ieHPiLpniHVV0s2V9p93LF50Md5Ft85MZypBOeOfwoA66iisTwv4otPFVlc
3dpDNClvcvbMJQMllAJIwTxzQBt0Vynijx9a+GNYt9KfS9Qv7m4h85Fs4w5xkjpnPY1taFq39uaT
FqH2K6svMJHkXSbJFwccigDRorlfFPj+w8MahHp32G81C8eIzNDaR7jHGM/M3Psa2tC1uy8RaPb6
rp7l7ecZXcMFSDggj1BFAGhRXH+K/iLaeEdQFreaPqU6MqlbiGIGMs2cKGJHPHSt/QdX/tzSYtQ+
w3Vj5hYeRdJskXBxyKANGisRvFNnH4qm8PSRSpPFZ/a/MONjJnBxznIrJi+JekzeF7bX47W6aG6v
RZpDhd+8n64x3oA7Gikrhf8AhbWif2p9n+x3/wBh+0/Zv7S8r9x5npnPSgDu6KQnAzXA2fxg0W4n
Tz9N1O1tXn8gXkkIMIfPQsDQB39FJ1rF8N+KbTxMdQFrDNF9gumtpPNA+Zh3GD0oA26KiuJltraW
dgSsSFyB1IAzXE6N8WNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Safe data
retention: Replication and the geographic diversity of peer nodes of the
overlay,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Economy
of scale: All peers have software with identical =
behavior,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>No
configuration is required or possible. The customer just plugs in the =
gateway
box. This is real service automation.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Cost
containment: P2P self configuration is unbeatable. Count all the savings =
in
CAPEX and OPEX by not having any network based VoIP infrastructure. Save =
all
that electricity and real estate in the data =
centers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Flexibility
for new applications: The API between SIP and the DHT =
overlay,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>No
lock-in from single source: The applications are in the endpoints. Buy =
them
from anytG1a7tIZNP1GxivZPKt7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8
kKcE9M5IrD1H4h6Hpltazzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+
jtPI2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1LvgEhv5V4sNKivt
c+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m1u7X7PGJ4vL+zRoFMe3J3YHY5x9a
1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej
3PAy/C1qWJTmmkt+vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLNd74l0OHxJ4evNInk
MSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZrKOGLYFXGMse5wf/AK9ekfLl74p/8k31
j/rmv/oa1xfhqXUW+IHhl/E0MVuf7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5
C4YHp+Fc5oHgDVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu11WK/
m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYHA9OBQByXjWXV4fi9oj6F
b29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRqZ0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xa
WxgBkg8zqWycHjo1dFoNtq1ppaQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs
9CsdDjg8OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/gK2/CHhuL
wn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ceFpvFmlWtlDdJbNBdpcFnUsCF
B44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1
Lx54N/4TPT7K2FwsDWt0sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/
AJoeP+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6Wv+oH+7/SvnjT
59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrzofC+5XwYNFXUoReQ6l9vt7nyzhD6
YznpmgD0RFCIqDooArz34S/e8Uf9hmWvQk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2
gYsC2SMnOOOOKAO41X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689GHQ1lT+EdCuQBLYK2
CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgBumKworm4ESATyYCj+M0j3M5KZnk4bj5z
Xjey97c+4WK/dr3e39bG/ChiiCEjIz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5
OW5+c+lCpbu45YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckxNyf9
9q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRR
QAUUUUAFFFFAH//Z

------=_NextPart_000_1E06_01C7769F.E4C51F70--



--===============0513198450==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0513198450==--



From sipping-bounces@ietf.org Thu Apr 05 08:05:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZQgF-0006lm-QE; Thu, 05 Apr 2007 08:03:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ6wU-0000k7-F9; Wed, 04 Apr 2007 10:58:34 -0400
Received: from exprod6og52.obsmtp.com ([64.18.1.185])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HZ6jQ-0006Ms-J7; Wed, 04 Apr 2007 10:45:11 -0400
Received: from source ([192.150.11.134]) by exprod6ob52.postini.com
	([64.18.5.12]) with SMTP; Wed, 04 Apr 2007 07:45:02 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l34EiQD1028170; Wed, 4 Apr 2007 07:44:33 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l34EinI9007073; Wed, 4 Apr 2007 07:44:49 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 4 Apr 2007 07:44:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 4 Apr 2007 07:44:08 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223ADF38@namail5.corp.adobe.com>
In-Reply-To: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: P2P SIPtG1a7tIZNP1GxivZPKt7m4iAikfONu4E9+KAO7oqlqOojThCWtZ5/OkEY8
kKcE9M5IrD1H4h6Hpltazzrdst1v2COAsV2NtO4duelAHjEUayWkIOeEUgg4IOK3vCOgJresJaC+
jtPI2zgOu5pcNkgcj05+tc7BLIkFv5gQK6qoweRx3qza6jJZX1rfwwq/2a4R1LvgEhv5V4sNKivt
c+5xHv4ZqGkrdvI+hmtoHgMDwRtCRgxlAVP4V5T8StEs9O1m1u7X7PGJ4vL+zRoFMe3J3YHY5x9a
1tO+Ko+xXbapaRR3MaBrZIWbFwf7vIOD059K4LXtZn1zxDc6gbOOJpkTKCbOMLjqQOOK7q9SEqej
3PAy/C1qWJTmmkt+vyK9ez/D/wD5EfTP9xv/AENq8Rjt2i2lHG/GHyCQx9a9u+H2f+EG0zPXY3T/
AH2rHBJKTszuzyTdKF1bX9Cj8Wf+Sbar9I//AEYtc/8A81H8C/8AYHP/AKLNd74l0OHxJ4evNInk
MSXKbfMUZKEHIOO/IFcv4a8B6xZ+ILPV/EGtRX7aZbfZrKOGLYFXGMse5wf/AK9ekfLl74p/8k31
j/rmv/oa1xfhqXUW+IHhl/E0MVuf7L2aV9m+ZJBs/jJOQdpP44r0nxdocniXwve6PFOsD3KhRIy5
C4YHp+Fc5oHgDVLbXtP1bX9cTUDpUHk2UMUAjVBjbk+vFAHeV598G/8AkXtW/wCwvP8AySu11WK/
m0u4j0u4jt71kxDLKu5Ub1I71j+BfCsnhHQnsp7sXdxPcPcTSKu1SzYHA9OBQByXjWXV4fi9oj6F
b29xfDTpNkdwxVCMvnJHtXpGntePp9u+oRxxXbRqZ0iOVV8cgH0zXKeKvB2tat4qsvEGiazDp1xa
WxgBkg8zqWycHjo1dFoNtq1ppaQ61qEd/eBmLTxxCMEZ4GB6CgDjMI3x4uRJjYdEw2T23DNdZ4Vs
9CsdDjg8OSRSaeHYo0U3mruJ5+bJ71heKfBWrX/iNPEHh7V49PvWtTaTCaLerIe49D/gK2/CHhuL
wn4bttHimM5iyzyEY3MTknHYUAcz8ZP+RY0//sKQ/wAmr0Gua8ceFpvFmlWtlDdJbNBdpcFnUsCF
B44+tdLQB5V8V7xvD/iGw1pQQLnTbuyJH94r8n6t+lczodi9l4j0fwVKWfyNWi1Agjgr5Csf1Br1
Lx54N/4TPT7K2FwsDWt0sxZlzlcEMPxpG8Fg/EiPxYs6BEtPJ8jZzvwRuz6beKAOnl/1T/7prwX/
AJoeP+w5/WvfCAQQehrzH/hVOqbv7I/t5P8AhHPtv2z7N5P73P8Ad3envn3xQB6Wv+oH+7/SvnjT
59S1Pw1a+FDaRQWGp60wXUHk/jBGV2joenPevorb8u0ccYrzofC+5XwYNFXUoReQ6l9vt7nyzhD6
YznpmgD0RFCIqDooArz34S/e8Uf9hmWvQk3CNd5BfA3EdM159pPgXxXoWq3c2meJbaGzvL1rmaA2
gYsC2SMnOOOOKAO41X/kEXn/AF7v/wCgmvEF/wCSSeEj3GuDH/fT17peQG5sp7cMFMsbICe2RivN
9H+FWqwJpdhquvx3Gk6ZcfaY7WG32lnznluuMk/nQB6TNbxXAQSru8tw689GHQ1lT+EdCuQBLYK2
CSPnb0A9fYVtUUAfOEADWkQYAgxrwR7Usp2qsaorFzgBumKworm4ESATyYCj+M0j3M5KZnk4bj5z
Xjey97c+4WK/dr3e39bG/ChiiCEjIz06D2qIq00wYKqrG+N38Rx1H0rI+1XH/PeT/vs0xLmcO+J5
OW5+c+lCpbu45YlWUeXT1Oir2f4f/wDIj6Z/uN/6G1fPP2q4/wCe8n/fZr6C+HBJ8AaSSckxNyf9
9q6cJDlkzyc5r+0hBWtqdPRRRXoHzgUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRR
QAUUUUAFFFFAH//Z

------=_NextPart_000_1E06_01C7769F.E4C51F70--



--===============0513198450==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0513198450==--



From sipping-bounces@ietf.org Thu Apr 05 08:05:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZQgF-0006lm-QE; Thu, 05 Apr 2007 08:03:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZ6wU-0000k7-F9; Wed, 04 Apr 2007 10:58:34 -0400
Received: from exprod6og52.obsmtp.com ([64.18.1.185])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HZ6jQ-0006Ms-J7; Wed, 04 Apr 2007 10:45:11 -0400
Received: from source ([192.150.11.134]) by exprod6ob52.postini.com
	([64.18.5.12]) with SMTP; Wed, 04 Apr 2007 07:45:02 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l34EiQD1028170; Wed, 4 Apr 2007 07:44:33 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l34EinI9007073; Wed, 4 Apr 2007 07:44:49 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 4 Apr 2007 07:44:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 4 Apr 2007 07:44:08 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223ADF38@namail5.corp.adobe.com>
In-Reply-To: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: P2P SIPwhere.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Automatic
updates from the application provider: This is current PC SW state of =
the art
and works for both the (1) P2P software in the access device and (2) for =
the
application software, such as presence, IM, voice, multimedia, etc. No =
or
minimal is staff required.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Last but
not least, besides SIP enabled communications, the overlay can also =
serve for many
other applications for your users: Content distribution, application =
layer
multicast for conferences, directory search, IM+A/V chat rooms, name =
services, etc.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>All of the above can be easily =
implemented
by porting well documented open source software into the residential =
access box
or in the integrated access device (IAD) for enterprises. Just check out =
<a
href=3D"http://opendht.org/">http://opendht.org/</a> and other similar =
sites.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Please don&#8217;t take my word for =
it,
just make for yourself a comparison table for your network. If you =
can&#8217;t
share the comparison with the list, can you share it with me in private? =
</span></font><font
size=3D2 color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:
Wingdings;color:navy'>J</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:
Wingdings;color:navy'><span style=3D'mso-list:Ignore'>&Oslash;<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2><span
style=3D'font-size:10.0pt'>as an employee of a =
carrier<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>I worked most of my career for carriers, so that&#82 service assurance (was Simple SIP usage scenario)
Thread-Index: Acd1fDvzIhowLornTwyehPLXZ9zr5AA/ypd/ABGlquA=
References: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: <colin.pons@kpn.com>, <pkyzivat@cisco.com>
X-OriginalArrivalTime: 04 Apr 2007 14:44:54.0268 (UTC)
	FILETIME=[CEC11BC0:01C776C7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8cc9f19007352bcbade9ec25b8f17862
X-Mailman-Approved-At: Thu, 05 Apr 2007 08:03:04 -0400
Cc: sipping@ietf.org, p2prg@ietf.org, oran@cisco.com, p2psip@ietf.org,
	mhammer@cisco.com
Subject: [Sipping] P2P SIP service assurance (was Simple SIP usage scenario)
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1723679838=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1723679838==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C776C7.CE6A1169"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C776C7.CE6A1169
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Colin, Paul,

=20

Thanks for raising the valid issue about service assurance.=20

As engineers, we know the service assurance is more than a piece of
legal paper and must be based on the following:

=20

-          Adequate bandwidth,

-          Geographic diversity,

-          Simplicity; so things can be managed,

-          Security that can be audited,

-          Safe data retention: Replication and the geographic diversity
of peer nodes of the overlay,

-          Economy of scale: All peers have software with identical
behavior,

-          No configuration is required or possible. The customer just
plugs in the gateway box. This is real service automation.

-          Cost containment: P2P self configuration is unbeatable. Count
all the savings in CAPEX and OPEX by not having any network based VoIP
infrastructure. Save all that electricity and real estate in the data
centers.

-          Flexibility for new applications: The API between SIP and the
DHT overlay,

-          No lock-in from single source: The applications are in the
endpoints. Buy them from anywhere.

-          Automatic updates from the application provider: This is
current PC SW state of the art and works for both the (1) P2P software
in the access device and (2) for the application software, such as
presence, IM, voice, multimedia, etc. No or minimal is staff required.

-          Last but not least, besides SIP enabled communications, the
overlay can also serve for many other applications for your users:
Content distribution, application layer multicast for conferences,
directory search, IM+A/V chat rooms, name services, etc.

=20

All of the above can be easily implemented by porting well documented
open source software into the residential access box or in the
integrated access device (IAD) for enterprises. Just check out
http://opendht.org/ and other similar sites.

=20

Please don't take my word for it, just make for yourself a comparison
table for your network. If you can't share the comparison with the list,
can you share it with me in private? :-)

=20

*       as an employee of a carrier

=20

I worked most of my career for carriers, so that's what prompted the
above considerations.

=20

Thanks, Henry

=20

________________________________

From: colin.pons@kpn.com [mailto:colin.pons@kpn.com]=20
Sent: Wednesday, April 04, 2007 12:38 AM
To: pkyzivat@cisco.com; Henry Sinnreich
Cc: p2psip@ietf.org; mhammer@cisco.com; oran@cisco.co service assurance (was Simple SIP usage scenario)
Thread-Index: Acd1fDvzIhowLornTwyehPLXZ9zr5AA/ypd/ABGlquA=
References: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: <colin.pons@kpn.com>, <pkyzivat@cisco.com>
X-OriginalArrivalTime: 04 Apr 2007 14:44:54.0268 (UTC)
	FILETIME=[CEC11BC0:01C776C7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8cc9f19007352bcbade9ec25b8f17862
X-Mailman-Approved-At: Thu, 05 Apr 2007 08:03:04 -0400
Cc: sipping@ietf.org, p2prg@ietf.org, oran@cisco.com, p2psip@ietf.org,
	mhammer@cisco.com
Subject: [Sipping] P2P SIP service assurance (was Simple SIP usage scenario)
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1723679838=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1723679838==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C776C7.CE6A1169"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C776C7.CE6A1169
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Colin, Paul,

=20

Thanks for raising the valid issue about service assurance.=20

As engineers, we know the service assurance is more than a piece of
legal paper and must be based on the following:

=20

-          Adequate bandwidth,

-          Geographic diversity,

-          Simplicity; so things can be managed,

-          Security that can be audited,

-          Safe data retention: Replication and the geographic diversity
of peer nodes of the overlay,

-          Economy of scale: All peers have software with identical
behavior,

-          No configuration is required or possible. The customer just
plugs in the gateway box. This is real service automation.

-          Cost containment: P2P self configuration is unbeatable. Count
all the savings in CAPEX and OPEX by not having any network based VoIP
infrastructure. Save all that electricity and real estate in the data
centers.

-          Flexibility for new applications: The API between SIP and the
DHT overlay,

-          No lock-in from single source: The applications are in the
endpoints. Buy them from anywhere.

-          Automatic updates from the application provider: This is
current PC SW state of the art and works for both the (1) P2P software
in the access device and (2) for the application software, such as
presence, IM, voice, multimedia, etc. No or minimal is staff required.

-          Last but not least, besides SIP enabled communications, the
overlay can also serve for many other applications for your users:
Content distribution, application layer multicast for conferences,
directory search, IM+A/V chat rooms, name services, etc.

=20

All of the above can be easily implemented by porting well documented
open source software into the residential access box or in the
integrated access device (IAD) for enterprises. Just check out
http://opendht.org/ and other similar sites.

=20

Please don't take my word for it, just make for yourself a comparison
table for your network. If you can't share the comparison with the list,
can you share it with me in private? :-)

=20

*       as an employee of a carrier

=20

I worked most of my career for carriers, so that's what prompted the
above considerations.

=20

Thanks, Henry

=20

________________________________

From: colin.pons@kpn.com [mailto:colin.pons@kpn.com]=20
Sent: Wednesday, April 04, 2007 12:38 AM
To: pkyzivat@cisco.com; Henry Sinnreich
Cc: p2psip@ietf.org; mhammer@cisco.com; oran@cisco.co17;s what =
prompted
the above considerations.</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, =
Henry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
colin.pons@kpn.com [mailto:colin.pons@kpn.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, April =
04, 2007
12:38 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> pkyzivat@cisco.com; =
Henry
Sinnreich<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
p2psip@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; mhammer@cisco.com; oran@cisco.com; =
<st1:PersonName
w:st=3D"on">p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>; <st1:PersonName =
w:st=3D"on">sipping@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] Re: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>Henry,<br>
<br>
I like your idea of deploying sip peers in edge devices. However, as an
employee of a carrier I would like to see how a carrier is able to =
provide
service asurance to be able to provide compliant handling. Many of our
customers do not understand how to install these gateways themselves, =
let alone
how to troubleshoot.<br>
<br>
This is even more important for enterprises, which often&nbsp; insist on =
SLAs
which include troubleshoot resolution limits.<br>
<br>
-----Original Message-----<br>
From: &quot;<st1:PersonName w:st=3D"on">Paul =
Kyzivat</st1:PersonName>&quot;
&lt;pkyzivat@cisco.com&gt;<br>
To: &quot;Henry Sinnreich&quot; &lt;hsinnrei@adobe.com&gt;<br>
Cc: &quot;<st1:PersonName w:st=3D"on">P2PSIP Mailing =
List</st1:PersonName>&quot;
&lt;p2psip@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName>&gt;; =
&quot;<st1:PersonName
w:st=3D"on">Michael Hammer</st1:PersonName> (mhammer)&quot;
&lt;mhammer@cisco.com&gt;; &quot;<st1:PersonName w:st=3D"on">David R =
<st1:City
 w:st=3D"on"><st1:place =
w:st=3D"on">Oran</st1:place></st1:City></st1:PersonName>&quot;
&lt;oran@cisco.com&gt;; &quot;<st1:PersonName =
w:st=3D"on">p2p<st1:PersonName
 w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&quot;
&lt;<st1:PersonName w:st=3D"on">p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>&gt;; =
&quot;<st1:PersonName
w:st=3D"on">sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&quot;
&lt;<st1:PersonName w:st=3D"on">sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&gt;<br>
Sent: 3-4-07 01:11<br>
Subject: [P2PSIP] Re: [P2P<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>] RE:
[Sipping] Simple SIP usage scenario<br>
<br>
<br>
<br>
Henry m; p2prg@ietf.org;
sipping@ietf.org
Subject: RE: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage
scenario

=20

Henry,

I like your idea of deploying sip peers in edge devices. However, as an
employee of a carrier I would like to see how a carrier is able to
provide service asurance to be able to provide compliant handling. Many
of our customers do not understand how to install these gateways
themselves, let alone how to troubleshoot.

This is even more important for enterprises, which often  insist on SLAs
which include troubleshoot resolution limits.

-----Original Message-----
From: "Paul Kyzivat" <pkyzivat@cisco.com>
To: "Henry Sinnreich" <hsinnrei@adobe.com>
Cc: "P2PSIP Mailing List" <p2psip@ietf.org>; "Michael Hammer (mhammer)"
<mhammer@cisco.com>; "David R Oran" <oran@cisco.com>; "p2prg@ietf.org"
<p2prg@ietf.org>; "sipping@ietf.org" <sipping@ietf.org>
Sent: 3-4-07 01:11
Subject: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario



Henry Sinnreich wrote:
> Paul,
>
>> I more or less agree with the final conclusion below.
>
> This is good starting point to discuss some usage scenarios.
>
> Putting on my former hat as an employee for a carrier, I cannot
overlook
> the following:
>
> P2P SIP implemented correctly in the residential access box or cable
> set-top box indeed is a good or better replacement for the entire VoIP
> network infrastructure (cost, operations, new services, etc).
> Integrated access devices for the enterprise can probably play a
similar
> role, not to mention existing P2P PBX products (please refer to all
the
> advantages of P2P that need not repeated here).
>
> What do people think of these three usage scenarios for P2P SIP:
> - SIP peer in the DSL access device,
> - SIP peer in the cable access device,

These seem quite reasonable, assuming that a device connected at this
point is able to function properly as a peer. (I haven't been following
what the assumptions are about required network capabilities of peers.)

> - SIP peer in enterprise network integrated access device (IAD).

I think this depends greatly on what expectations / contractual
guarantees the enterprise has. Its unclear to me what guarantees can be
made about a P2PSIP network will be able to make, and its unclear what
kind of infrastructure would be installed by/for someone willing to make
guarantees.

        Paul

> Note that these examples imply very low churn for the peers and add
the
> data retention resilience of P2P (geographic diversity is native and
> mobile, etc.). Incidentally, NAT traversal may also not be a problem,
or
> at least an easier problem.
>
> What do you all think?
>
> I have taken the liberty to copy the P2P SIP list, since the low churn
> scenarios are of interest for the DHT selection. Or just pick the same
> DHT for all scenarios anyway? I don't think so.
>
> Thanks, Henry
>
>
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Friday, March 30, 2007 6:31 PM
> To: Eunsoo Shim
> Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
> p2prg@ietf.org; sipping@ietf.org; zhuxian
> Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
>
> I more or less agree with the final conclusion below.
>
> My main point here is that P2P and C/S need not be enemies. Nor is a
> total C/S system necessarily evil. What is most evil is *bundling* of
> services that prevents freedom of choice.
>
> I think I would be quite happy with a SP that provides a
registrar/proxy
>
> and allows me to provide all other features as I see fit - by taking
> them ala carte from the SP, or subscribing to them from one or more
> other SPs, or by providing them myself via appliances I own. If that
> registrar/proxy was replaced by a P2P sip community, the differences,
if
>
> any, would hopefully be more a function of the implementation and the
> business models of those involved than the architecture.
>
> (I gather the general assumption is that a P2P setup will be *free*.
But
>
> I have a hard time believing that. If most of the usage is by mobile
> devices that can't be peers, thm; p2prg@ietf.org;
sipping@ietf.org
Subject: RE: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage
scenario

=20

Henry,

I like your idea of deploying sip peers in edge devices. However, as an
employee of a carrier I would like to see how a carrier is able to
provide service asurance to be able to provide compliant handling. Many
of our customers do not understand how to install these gateways
themselves, let alone how to troubleshoot.

This is even more important for enterprises, which often  insist on SLAs
which include troubleshoot resolution limits.

-----Original Message-----
From: "Paul Kyzivat" <pkyzivat@cisco.com>
To: "Henry Sinnreich" <hsinnrei@adobe.com>
Cc: "P2PSIP Mailing List" <p2psip@ietf.org>; "Michael Hammer (mhammer)"
<mhammer@cisco.com>; "David R Oran" <oran@cisco.com>; "p2prg@ietf.org"
<p2prg@ietf.org>; "sipping@ietf.org" <sipping@ietf.org>
Sent: 3-4-07 01:11
Subject: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario



Henry Sinnreich wrote:
> Paul,
>
>> I more or less agree with the final conclusion below.
>
> This is good starting point to discuss some usage scenarios.
>
> Putting on my former hat as an employee for a carrier, I cannot
overlook
> the following:
>
> P2P SIP implemented correctly in the residential access box or cable
> set-top box indeed is a good or better replacement for the entire VoIP
> network infrastructure (cost, operations, new services, etc).
> Integrated access devices for the enterprise can probably play a
similar
> role, not to mention existing P2P PBX products (please refer to all
the
> advantages of P2P that need not repeated here).
>
> What do people think of these three usage scenarios for P2P SIP:
> - SIP peer in the DSL access device,
> - SIP peer in the cable access device,

These seem quite reasonable, assuming that a device connected at this
point is able to function properly as a peer. (I haven't been following
what the assumptions are about required network capabilities of peers.)

> - SIP peer in enterprise network integrated access device (IAD).

I think this depends greatly on what expectations / contractual
guarantees the enterprise has. Its unclear to me what guarantees can be
made about a P2PSIP network will be able to make, and its unclear what
kind of infrastructure would be installed by/for someone willing to make
guarantees.

        Paul

> Note that these examples imply very low churn for the peers and add
the
> data retention resilience of P2P (geographic diversity is native and
> mobile, etc.). Incidentally, NAT traversal may also not be a problem,
or
> at least an easier problem.
>
> What do you all think?
>
> I have taken the liberty to copy the P2P SIP list, since the low churn
> scenarios are of interest for the DHT selection. Or just pick the same
> DHT for all scenarios anyway? I don't think so.
>
> Thanks, Henry
>
>
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Friday, March 30, 2007 6:31 PM
> To: Eunsoo Shim
> Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
> p2prg@ietf.org; sipping@ietf.org; zhuxian
> Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
>
> I more or less agree with the final conclusion below.
>
> My main point here is that P2P and C/S need not be enemies. Nor is a
> total C/S system necessarily evil. What is most evil is *bundling* of
> services that prevents freedom of choice.
>
> I think I would be quite happy with a SP that provides a
registrar/proxy
>
> and allows me to provide all other features as I see fit - by taking
> them ala carte from the SP, or subscribing to them from one or more
> other SPs, or by providing them myself via appliances I own. If that
> registrar/proxy was replaced by a P2P sip community, the differences,
if
>
> any, would hopefully be more a function of the implementation and the
> business models of those involved than the architecture.
>
> (I gather the general assumption is that a P2P setup will be *free*.
But
>
> I have a hard time believing that. If most of the usage is by mobile
> devices that can't be peers, thSinnreich wrote:<br>
&gt; Paul,<br>
&gt;<br>
&gt;&gt; I more or less agree with the final conclusion below.<br>
&gt;<br>
&gt; This is good starting point to discuss some usage scenarios.<br>
&gt;<br>
&gt; Putting on my former hat as an employee for a carrier, I cannot =
overlook<br>
&gt; the following:<br>
&gt;<br>
&gt; P2P SIP implemented correctly in the residential access box or =
cable<br>
&gt; set-top box indeed is a good or better replacement for the entire =
VoIP<br>
&gt; network infrastructure (cost, operations, new services, etc).<br>
&gt; Integrated access devices for the enterprise can probably play a =
similar<br>
&gt; role, not to mention existing P2P PBX products (please refer to all =
the<br>
&gt; advantages of P2P that need not repeated here).<br>
&gt;<br>
&gt; What do people think of these three usage scenarios for P2P =
SIP:<br>
&gt; - SIP peer in the DSL access device,<br>
&gt; - SIP peer in the cable access device,<br>
<br>
These seem quite reasonable, assuming that a device connected at =
this<br>
point is able to function properly as a peer. (I haven't been =
following<br>
what the assumptions are about required network capabilities of =
peers.)<br>
<br>
&gt; - SIP peer in enterprise network integrated access device =
(IAD).<br>
<br>
I think this depends greatly on what expectations / contractual<br>
guarantees the enterprise has. Its unclear to me what guarantees can =
be<br>
made about a P2PSIP network will be able to make, and its unclear =
what<br>
kind of infrastructure would be installed by/for someone willing to =
make<br>
guarantees.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Paul<br>
<br>
&gt; Note that these examples imply very low churn for the peers and add =
the<br>
&gt; data retention resilience of P2P (geographic diversity is native =
and<br>
&gt; mobile, etc.). Incidentally, NAT traversal may also not be a =
problem, or<br>
&gt; at least an easier problem.<br>
&gt;<br>
&gt; What do you all think?<br>
&gt;<br>
&gt; I have taken the liberty to copy the P2P SIP list, since the low =
churn<br>
&gt; scenarios are of interest for the DHT selection. Or just pick the =
same<br>
&gt; DHT for all scenarios anyway? I don't think so.<br>
&gt;<br>
&gt; Thanks, Henry<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: <st1:PersonName w:st=3D"on">Paul Kyzivat</st1:PersonName> [<a
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</a>]<br>
&gt; Sent: Friday, March 30, 2007 6:31 PM<br>
&gt; To: <st1:PersonName w:st=3D"on">Eunsoo Shim</st1:PersonName><br>
&gt; Cc: Henry Sinnreich; <st1:PersonName w:st=3D"on">Michael =
Hammer</st1:PersonName>
(mhammer); <st1:PersonName w:st=3D"on">David R =
Oran</st1:PersonName>;<br>
&gt; <st1:PersonName w:st=3D"on">p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>; <st1:PersonName =
w:st=3D"on">sipping@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>; zhuxian<br>
&gt; Subject: Re: [P2P<st1:PersonName w:st=3D"on">rg</st1:PersonName>] =
RE:
[Sipping] Simple SIP usage scenario<br>
&gt;<br>
&gt; I more or less agree with the final conclusion below.<br>
&gt;<br>
&gt; My main point here is that P2P and C/S need not be enemies. Nor is =
a<br>
&gt; total C/S system necessarily evil. What is most evil is *bundling* =
of<br>
&gt; services that prevents freedom of choice.<br>
&gt;<br>
&gt; I think I would be quite happy with a SP that provides a =
registrar/proxy<br>
&gt;<br>
&gt; and allows me to provide all other features as I see fit - by =
taking<br>
&gt; them ala carte from the SP, or subscribing to them from one or =
more<br>
&gt; other SPs, or by providing them myself via appliances I own. If =
that<br>
&gt; registrar/proxy was replaced by a P2P sip community, the =
differences, if<br>
&gt;<br>
&gt; any, would hopefully be more a function of the implementation and =
the<br>
&gt; business models of those involved than the architecture.<br>
&gt;<br>
&gt; (I gather the general assumption is that a P2P setup will be =
*free*. But<br>
&gt;<br>
&en somebody will have to pay for enough
> peers to support them. If it isn't free, then how is it better than a
> well engineered C/S system?)
>
> So I think the key thing here is that some features will require
getting
>
> some help from another node. There ought to be the option to pick a
> different source for each helper you require, and an ability for it
all
> to play together.
>
>       Paul
>
> Eunsoo Shim wrote:
>> Please see my inline comment.
>>
>> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com
>> <mailto:pkyzivat@cisco.com>> wrote:
>>
>>
>>
>>     Henry Sinnreich wrote:
>>      > David Oran wrote (with regard to voice mail):
>>      >
>>      >> I'm not saying this can't be made to work, only that it isn't
>>      > immediately >obvious that it has advantages over a classic
>>     application
>>      > server >approach.
>>      >
>>      > The answer for VM is "it depends":
>>      >
>>
>>
>> I agree. It really depends. Certainly there are tradeoffs.
>>
>>      > There are several commercial P2P IP PBX solutions without any
>>     server for
>>      > VM or anything else. No doubt the IT organization appreciates
> just
>>      > having to plug in the IP phones and GWY to the PSTN without
any
>>      > configuration ever for VM or any other PBX feature.
>>
>>     I don't understand. Are you saying they don't have VM, or that
> they
>>     don't have a *server* for VM?
>>
>>
>> I guess they don't have a  *server* for  VM.
>>
>>      > For public P2P SIP networks there are two more scenarios where
> VM can
>>      > reside (and without ever spending one cent on VM servers + IT
>>     systems):
>>      >
>>      > - In Cable and DSL service provider networks: The residential
>>     router can
>>      > act as a voice recorder
>>
>>     That is simply an example of the user having an appliance of his
> own
>>     that provides VM service.
>>
>>      > and P2P can cover the not too frequent cases,
>>      > where the router is not in operation, so the data is backed up
> in
>>     other
>>      > peer residential gateways (encrypted).
>>
>>     I guess I just need to have more info about how this would work
> before I
>>     will be convinced it is feasible and trustworthy.
>>
>>
>> Well, 'trustworthy' could be  considered in many angles.
>> If it is about privacy of the message, a public key based encryption
>> would provide acceptable privacy.
>> If it is about reliability of the message delivery, well, a P2P based
>> asynchronous message delivery (like VM) is most likely less reliable
>> than a well managed server based system.
>> However, my experience with Skype's asynchronous message delivery was
>> not bad. Actually I don't see any significant difference between it
> and
>> my cellular service provider's VM service. :-)
>> Reliability is always a challenge for P2P, for sure. But, I believe
it
>
>> is feasible to build a P2P system for VM acceptable for many
> scenarios.
>>      > - In mobile networks: The VM can reside in quite stable peers
>>     inside the
>>      > wireless base station network. The peers in the base station
> network
>>      > need no configuration, etc.
>>
>>     I don't understand. I guess that could be true if the peers are
> willing
>>     to store an arbitrary amount of VM indefinitely for anybody. Is
> that
>>     believable?
>>
>>
>> It depends.
>> In a very nice environment where all the peers are willing to
> cooperate
>> at their best, the peers will store as much as they can. In a tough
>> environment, the situation will be different.
>>
>>     This seems to translate to a model where it is assumed that those
> nodes
>>     that are on most of the time will be willing to provide VM
storage
> for
>>     those nodes that aren't on most of the time.
>>
>>
>> This is again related to reliability of P2P systems or topics like
> free
>> riders and reputation.
>> A P2P system is a community or society. To be simple, if many of the
>> members are bad, the community won't work well. If the majority of
the
>
>> members are good, the community will work well or reasonably.
>>
>>      > Aden somebody will have to pay for enough
> peers to support them. If it isn't free, then how is it better than a
> well engineered C/S system?)
>
> So I think the key thing here is that some features will require
getting
>
> some help from another node. There ought to be the option to pick a
> different source for each helper you require, and an ability for it
all
> to play together.
>
>       Paul
>
> Eunsoo Shim wrote:
>> Please see my inline comment.
>>
>> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com
>> <mailto:pkyzivat@cisco.com>> wrote:
>>
>>
>>
>>     Henry Sinnreich wrote:
>>      > David Oran wrote (with regard to voice mail):
>>      >
>>      >> I'm not saying this can't be made to work, only that it isn't
>>      > immediately >obvious that it has advantages over a classic
>>     application
>>      > server >approach.
>>      >
>>      > The answer for VM is "it depends":
>>      >
>>
>>
>> I agree. It really depends. Certainly there are tradeoffs.
>>
>>      > There are several commercial P2P IP PBX solutions without any
>>     server for
>>      > VM or anything else. No doubt the IT organization appreciates
> just
>>      > having to plug in the IP phones and GWY to the PSTN without
any
>>      > configuration ever for VM or any other PBX feature.
>>
>>     I don't understand. Are you saying they don't have VM, or that
> they
>>     don't have a *server* for VM?
>>
>>
>> I guess they don't have a  *server* for  VM.
>>
>>      > For public P2P SIP networks there are two more scenarios where
> VM can
>>      > reside (and without ever spending one cent on VM servers + IT
>>     systems):
>>      >
>>      > - In Cable and DSL service provider networks: The residential
>>     router can
>>      > act as a voice recorder
>>
>>     That is simply an example of the user having an appliance of his
> own
>>     that provides VM service.
>>
>>      > and P2P can cover the not too frequent cases,
>>      > where the router is not in operation, so the data is backed up
> in
>>     other
>>      > peer residential gateways (encrypted).
>>
>>     I guess I just need to have more info about how this would work
> before I
>>     will be convinced it is feasible and trustworthy.
>>
>>
>> Well, 'trustworthy' could be  considered in many angles.
>> If it is about privacy of the message, a public key based encryption
>> would provide acceptable privacy.
>> If it is about reliability of the message delivery, well, a P2P based
>> asynchronous message delivery (like VM) is most likely less reliable
>> than a well managed server based system.
>> However, my experience with Skype's asynchronous message delivery was
>> not bad. Actually I don't see any significant difference between it
> and
>> my cellular service provider's VM service. :-)
>> Reliability is always a challenge for P2P, for sure. But, I believe
it
>
>> is feasible to build a P2P system for VM acceptable for many
> scenarios.
>>      > - In mobile networks: The VM can reside in quite stable peers
>>     inside the
>>      > wireless base station network. The peers in the base station
> network
>>      > need no configuration, etc.
>>
>>     I don't understand. I guess that could be true if the peers are
> willing
>>     to store an arbitrary amount of VM indefinitely for anybody. Is
> that
>>     believable?
>>
>>
>> It depends.
>> In a very nice environment where all the peers are willing to
> cooperate
>> at their best, the peers will store as much as they can. In a tough
>> environment, the situation will be different.
>>
>>     This seems to translate to a model where it is assumed that those
> nodes
>>     that are on most of the time will be willing to provide VM
storage
> for
>>     those nodes that aren't on most of the time.
>>
>>
>> This is again related to reliability of P2P systems or topics like
> free
>> riders and reputation.
>> A P2P system is a community or society. To be simple, if many of the
>> members are bad, the community won't work well. If the majority of
the
>
>> members are good, the community will work well or reasonably.
>>
>>      > Adgt; I have a hard time believing that. If most of the usage is by =
mobile<br>
&gt; devices that can't be peers, then somebody will have to pay for =
enough<br>
&gt; peers to support them. If it isn't free, then how is it better than =
a<br>
&gt; well engineered C/S system?)<br>
&gt;<br>
&gt; So I think the key thing here is that some features will require =
getting<br>
&gt;<br>
&gt; some help from another node. There ought to be the option to pick =
a<br>
&gt; different source for each helper you require, and an ability for it =
all<br>
&gt; to play together.<br>
&gt;<br>
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Paul<br>
&gt;<br>
&gt; <st1:PersonName w:st=3D"on">Eunsoo Shim</st1:PersonName> wrote:<br>
&gt;&gt; Please see my inline comment.<br>
&gt;&gt;<br>
&gt;&gt; On 3/30/07, *<st1:PersonName w:st=3D"on">Paul =
Kyzivat</st1:PersonName>*
&lt;pkyzivat@cisco.com<br>
&gt;&gt; &lt;<a =
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</a>&gt;&gt;
wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; Henry Sinnreich wrote:<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; David Oran wrote (with =
regard to
voice mail):<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;&gt; I'm not saying this =
can't be
made to work, only that it isn't<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; immediately &gt;obvious that =
it has
advantages over a classic<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; application<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; server &gt;approach.<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; The answer for VM is =
&quot;it
depends&quot;:<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; I agree. It really depends. Certainly there are tradeoffs.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; There are several commercial =
P2P IP
PBX solutions without any<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; server for<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; VM or anything else. No =
doubt the
IT o<st1:PersonName w:st=3D"on">rg</st1:PersonName>anization =
appreciates<br>
&gt; just<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; having to plug in the IP =
phones and
GWY to the PSTN without any<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; configuration ever for VM or =
any
other PBX feature.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I don't understand. Are you saying they =
don't
have VM, or that<br>
&gt; they<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; don't have a *server* for VM?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; I guess they don't have a&nbsp; *server* for&nbsp; VM.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; For public P2P SIP networks =
there
are two more scenarios where<br>
&gt; VM can<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; reside (and without ever =
spending
one cent on VM servers + IT<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; systems):<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; - In Cable and DSL service =
provider
networks: The residential<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; router can<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; act as a voice recorder<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; That is simply an example of the user =
having
an appliance of his<br>
&gt; own<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; that provides VM service.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; and P2P can cover the not =
too
frequent cases,<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; where the router is not in
operation, so the data is backed up<br>
&gt; in<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; other<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; peer residential gateways
(encrypted).<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I guess I just need to have more info =
about
how this would work<br>
&gt; before I<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; will be convinced it is feasible and
trustworthy.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;d to this the conferencing capability coming from p2p
> application
>>      > layer multicast, the SIP e2e control capabilities (for such as
>>      > auto-attendant, agent workstation, etc.) and one has to wonder
> why IT
>>      > networks, public VoIP networks and end users should support
the
> huge
>>      > cost of hand engineering, testing, monitoring, maintaining
> server
>>     based
>>      > VoIP networks. P2P self configuration is nothing less that
> automation
>>      > applied to VoIP, plus the shifting of computing to the
> endpoints,
>>     where
>>      > there is an abundance of unused CPU, storage, bandwidth and
>>     electricity.
>>      >
>>      > Eric Burger also notes IM changes completely the usage for VM
> and may
>>      > make unnecessary to place calls on VM in the first place.
>>
>>     I find this more promising.
>>
>>         =20
>>
>>
>> In overall, are we discussing if P2P systems based VM can work? I
> think
>> it can work.  Just it depends on many things.
>> If it is not super-reliable, should we disregard it? I would say no.
>>
>> On the other hand, do we have to abandon client server based VM and
>> switch to P2P system based VM? It is upto each of us.
>> Client server based VM systems are already there.
>> So why don't we work on P2P based VM now?
>>=20
>> Thanks.
>>
>> Eunsoo
>

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www1.ietf.org/mailman/listinfo/p2psip


------_=_NextPart_001_01C776C7.CE6A1169
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>RE: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage =
scenario</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft
-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:319894744;
	mso-list-type:hybrid;
	mso-list-template-ids:1009410942 -487147662 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Arial;
	mso-fareast-font-family:"Times New Roman";}
@list l1
	{mso-list-id:1298990762;
	mso-list-type:hybrid;
	mso-list-template-ids:1053834342 -46605914 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@ld to this the conferencing capability coming from p2p
> application
>>      > layer multicast, the SIP e2e control capabilities (for such as
>>      > auto-attendant, agent workstation, etc.) and one has to wonder
> why IT
>>      > networks, public VoIP networks and end users should support
the
> huge
>>      > cost of hand engineering, testing, monitoring, maintaining
> server
>>     based
>>      > VoIP networks. P2P self configuration is nothing less that
> automation
>>      > applied to VoIP, plus the shifting of computing to the
> endpoints,
>>     where
>>      > there is an abundance of unused CPU, storage, bandwidth and
>>     electricity.
>>      >
>>      > Eric Burger also notes IM changes completely the usage for VM
> and may
>>      > make unnecessary to place calls on VM in the first place.
>>
>>     I find this more promising.
>>
>>         =20
>>
>>
>> In overall, are we discussing if P2P systems based VM can work? I
> think
>> it can work.  Just it depends on many things.
>> If it is not super-reliable, should we disregard it? I would say no.
>>
>> On the other hand, do we have to abandon client server based VM and
>> switch to P2P system based VM? It is upto each of us.
>> Client server based VM systems are already there.
>> So why don't we work on P2P based VM now?
>>=20
>> Thanks.
>>
>> Eunsoo
>

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www1.ietf.org/mailman/listinfo/p2psip


------_=_NextPart_001_01C776C7.CE6A1169
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>RE: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage =
scenario</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft
-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:319894744;
	mso-list-type:hybrid;
	mso-list-template-ids:1009410942 -487147662 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Arial;
	mso-fareast-font-family:"Times New Roman";}
@list l1
	{mso-list-id:1298990762;
	mso-list-type:hybrid;
	mso-list-template-ids:1053834342 -46605914 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@l Well, 'trustworthy' could be&nbsp; considered in many =
angles.<br>
&gt;&gt; If it is about privacy of the message, a public key based =
encryption<br>
&gt;&gt; would provide acceptable privacy.<br>
&gt;&gt; If it is about reliability of the message delivery, well, a P2P =
based<br>
&gt;&gt; asynchronous message delivery (like VM) is most likely less =
reliable<br>
&gt;&gt; than a well managed server based system.<br>
&gt;&gt; However, my experience with Skype's asynchronous message =
delivery was<br>
&gt;&gt; not bad. Actually I don't see any significant difference =
between it<br>
&gt; and<br>
&gt;&gt; my cellular service provider's VM service. :-)<br>
&gt;&gt; Reliability is always a challenge for P2P, for sure. But, I =
believe it<br>
&gt;<br>
&gt;&gt; is feasible to build a P2P system for VM acceptable for =
many<br>
&gt; scenarios.<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; - In mobile networks: The VM =
can
reside in quite stable peers<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; inside the<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; wireless base station =
network. The
peers in the base station<br>
&gt; network<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; need no configuration, =
etc.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I don't understand. I guess that could =
be true
if the peers are<br>
&gt; willing<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; to store an arbitrary amount of VM
indefinitely for anybody. Is<br>
&gt; that<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; believable?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; It depends.<br>
&gt;&gt; In a very nice environment where all the peers are willing =
to<br>
&gt; cooperate<br>
&gt;&gt; at their best, the peers will store as much as they can. In a =
tough<br>
&gt;&gt; environment, the situation will be different.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; This seems to translate to a model =
where it is
assumed that those<br>
&gt; nodes<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; that are on most of the time will be =
willing
to provide VM storage<br>
&gt; for<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; those nodes that aren't on most of the =
time.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; This is again related to reliability of P2P systems or topics =
like<br>
&gt; free<br>
&gt;&gt; riders and reputation.<br>
&gt;&gt; A P2P system is a community or society. To be simple, if many =
of the<br>
&gt;&gt; members are bad, the community won't work well. If the majority =
of the<br>
&gt;<br>
&gt;&gt; members are good, the community will work well or =
reasonably.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Add to this the conferencing
capability coming from p2p<br>
&gt; application<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; layer multicast, the SIP e2e
control capabilities (for such as<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; auto-attendant, agent =
workstation,
etc.) and one has to wonder<br>
&gt; why IT<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; networks, public VoIP =
networks and
end users should support the<br>
&gt; huge<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; cost of hand engineering, =
testing,
monitoring, maintaining<br>
&gt; server<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; based<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; VoIP networks. P2P self
configuration is nothing less that<br>
&gt; automation<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; applied to VoIP, plus the =
shifting
of computing to the<br>
&gt; endpoints,<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; where<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; there is an abundance of =
unused
CPU, storage, bandwidth and<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; electricity.<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Eric Bu<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>er
also notes IM changes completely the usage for VM<br>
&gt; and may<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; make unnecessary to place =
calls on
VM in the first place.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I find this more promising.<br>
&gist l1:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:Arial;
	color:navy;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Colin, =
Paul,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks for raising the valid issue =
about
service assurance. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>As engineers, we know the service
assurance is more than a piece of legal paper and must be based on the
following:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Adequate
bandwidth,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Geographic
diversity,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Simplicity;
so things can be managed,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Security
that <u>can be audited</u>,<o:p></o:p></span></font></p>

<p class=3DMsoist l1:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:Arial;
	color:navy;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Colin, =
Paul,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks for raising the valid issue =
about
service assurance. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>As engineers, we know the service
assurance is more than a piece of legal paper and must be based on the
following:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Adequate
bandwidth,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Geographic
diversity,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Simplicity;
so things can be managed,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Security
that <u>can be audited</u>,<o:p></o:p></span></font></p>

<p class=3DMsot;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; In overall, are we discussing if P2P systems based VM can work? =
I<br>
&gt; think<br>
&gt;&gt; it can work.&nbsp; Just it depends on many things.<br>
&gt;&gt; If it is not super-reliable, should we disregard it? I would =
say no.<br>
&gt;&gt;<br>
&gt;&gt; On the other hand, do we have to abandon client server based VM =
and<br>
&gt;&gt; switch to P2P system based VM? It is upto each of us.<br>
&gt;&gt; Client server based VM systems are already there.<br>
&gt;&gt; So why don't we work on P2P based VM now?<br>
&gt;&gt;&nbsp;<br>
&gt;&gt; Thanks.<br>
&gt;&gt;<br>
&gt;&gt; Eunsoo<br>
&gt;<br>
<br>
_______________________________________________<br>
P2PSIP mailing list<br>
P2PSIP@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName><br>
<a =
href=3D"https://www1.ietf.org/mailman/listinfo/p2psip">https://www1.ietf.=
org/mailman/listinfo/p2psip</a></span></font><o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01C776C7.CE6A1169--


--===============1723679838==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1723679838==--



From sipping-bounces@ietf.org Thu Apr 05 08:05:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZQgD-0006lT-Vd; Thu, 05 Apr 2007 08:03:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzyv-0003Af-2p; Wed, 04 Apr 2007 03:32:37 -0400
Received: from smtp-vbr9.xs4all.nl ([194.109.24.29])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYzyt-0007gL-QF; Wed, 04 Apr 2007 03:32:37 -0400
Received: from [192.168.0.6] (mit.xs4all.nl [213.84.95.205])
	by smtp-vbr9.xs4all.nl (8.13.8/8.13.8) with ESMTP id l347WGjb017787;
	Wed, 4 Apr 2007 09:32:21 +0200 (CEST)
	(envelope-from ag@ag-projects.com)
In-Reply-To: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
References: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
Mime-Version: 1.0 (Apple Message framework v752.2)
Message-Id: <1D065707-A33E-48CC-887B-0C5D6F0708CF@ag-projects.com>
From: Adrian Georgescu <ag@ag-projects.com>
Subject: Re: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Wed, 4 Apr 2007 09:32:13 +0200
To: "<colin.pons@kpn.com>" <colin.pons@kpn.com>
X-Mailer: Apple Mail (2.752.2)
X-Virus-Scanned: by XS4ALL Virus Scanner
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 9b281509fec590bb711c36d4c3ba4f74
X-Mailman-Approved-At: Thu, 05 Apr 2007 08:03:04 -0400
Cc: p2psip@ietf.org, mhammer@cisco.com, pkyzivat@cisco.com, oran@cisco.com,
	p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0170658415=="
Errors-To: sipping-bounces@ietf.org


--===============0170658415==
Content-Type: multipart/alternative; boundary=Apple-Mail-10--203761590


--Apple-Mail-10--203761590
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Colin,

With the right P2P software, the devices need no configuration at  
all, the configuration data can be derived from the "hardware id" and  
a preloadedNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Safe data
retention: Replication and the geographic diversity of peer nodes of the
overlay,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Economy
of scale: All peers have software with identical =
behavior,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>No
configuration is required or possible. The customer just plugs in the =
gateway
box. This is real service automation.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Cost
containment: P2P self configuration is unbeatable. Count all the savings =
in
CAPEX and OPEX by not having any network based VoIP infrastructure. Save =
all
that electricity and real estate in the data =
centers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Flexibility
for new applications: The API between SIP and the DHT =
overlay,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>No
lock-in from single source: The applications are in the endpoints. Buy =
them
from anyNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Safe data
retention: Replication and the geographic diversity of peer nodes of the
overlay,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Economy
of scale: All peers have software with identical =
behavior,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>No
configuration is required or possible. The customer just plugs in the =
gateway
box. This is real service automation.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Cost
containment: P2P self configuration is unbeatable. Count all the savings =
in
CAPEX and OPEX by not having any network based VoIP infrastructure. Save =
all
that electricity and real estate in the data =
centers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Flexibility
for new applications: The API between SIP and the DHT =
overlay,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>No
lock-in from single source: The applications are in the endpoints. Buy =
them
from any X509 certificate while the mapping between services and  
the hardware can be done centralized and allow the business model the  
operator wishes with minimal opex.

Adrian

On Apr 4, 2007, at 7:37 AM, <colin.pons@kpn.com> <colin.pons@kpn.com>  
wrote:

> Henry,
>
> I like your idea of deploying sip peers in edge devices. However,  
> as an employee of a carrier I would like to see how a carrier is  
> able to provide service asurance to be able to provide compliant  
> handling. Many of our customers do not understand how to install  
> these gateways themselves, let alone how to troubleshoot.
>
> This is even more important for enterprises, which often  insist on  
> SLAs which include troubleshoot resolution limits.
>
> -----Original Message-----
> From: "Paul Kyzivat" <pkyzivat@cisco.com>
> To: "Henry Sinnreich" <hsinnrei@adobe.com>
> Cc: "P2PSIP Mailing List" <p2psip@ietf.org>; "Michael Hammer  
> (mhammer)" <mhammer@cisco.com>; "David R Oran" <oran@cisco.com>;  
> "p2prg@ietf.org" <p2prg@ietf.org>; "sipping@ietf.org"  
> <sipping@ietf.org>
> Sent: 3-4-07 01:11
> Subject: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
>
>
>
> Henry Sinnreich wrote:
> > Paul,
> >
> >> I more or less agree with the final conclusion below.
> >
> > This is good starting point to discuss some usage scenarios.
> >
> > Putting on my former hat as an employee for a carrier, I cannot  
> overlook
> > the following:
> >
> > P2P SIP implemented correctly in the residential access box or cable
> > set-top box indeed is a good or better replacement for the entire  
> VoIP
> > network infrastructure (cost, operations, new services, etc).
> > Integrated access devices for the enterprise can probably play a  
> similar
> > role, not to mention existing P2P PBX products (please refer to  
> all the
> > advantages of P2P that need not repeated here).
> >
> > What do people think of these three usage scenarios for P2P SIP:
> > - SIP peer in the DSL access device,
> > - SIP peer in the cable access device,
>
> These seem quite reasonable, assuming that a device connected at this
> point is able to function properly as a peer. (I haven't been  
> following
> what the assumptions are about required network capabilities of  
> peers.)
>
> > - SIP peer in enterprise network integrated access device (IAD).
>
> I think this depends greatly on what expectations / contractual
> guarantees the enterprise has. Its unclear to me what guarantees  
> can be
> made about a P2PSIP network will be able to make, and its unclear what
> kind of infrastructure would be installed by/for someone willing to  
> make
> guarantees.
>
>         Paul
>
> > Note that these examples imply very low churn for the peers and  
> add the
> > data retention resilience of P2P (geographic diversity is native and
> > mobile, etc.). Incidentally, NAT traversal may also not be a  
> problem, or
> > at least an easier problem.
> >
> > What do you all think?
> >
> > I have taken the liberty to copy the P2P SIP list, since the low  
> churn
> > scenarios are of interest for the DHT selection. Or just pick the  
> same
> > DHT for all scenarios anyway? I don't think so.
> >
> > Thanks, Henry
> >
> >
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: Friday, March 30, 2007 6:31 PM
> > To: Eunsoo Shim
> > Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
> > p2prg@ietf.org; sipping@ietf.org; zhuxian
> > Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
> >
> > I more or less agree with the final conclusion below.
> >
> > My main point here is that P2P and C/S need not be enemies. Nor is a
> > total C/S system necessarily evil. What is most evil is  
> *bundling* of
> > services that prevents freedom of choice.
> >
> > I think I would be quite happy with a SP that provides a  
> registrar/proxy
> >
> > and allows me to provide all other features as I see fit - by taking
> > them ala carte from the SP, or subscribing to them from one or more
> > other SPs, or by providing them myself via appliances I own. If that
> > regiswhere.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Automatic
updates from the application provider: This is current PC SW state of =
the art
and works for both the (1) P2P software in the access device and (2) for =
the
application software, such as presence, IM, voice, multimedia, etc. No =
or
minimal is staff required.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Last but
not least, besides SIP enabled communications, the overlay can also =
serve for many
other applications for your users: Content distribution, application =
layer
multicast for conferences, directory search, IM+A/V chat rooms, name =
services, etc.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>All of the above can be easily =
implemented
by porting well documented open source software into the residential =
access box
or in the integrated access device (IAD) for enterprises. Just check out =
<a
href=3D"http://opendht.org/">http://opendht.org/</a> and other similar =
sites.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Please don&#8217;t take my word for =
it,
just make for yourself a comparison table for your network. If you =
can&#8217;t
share the comparison with the list, can you share it with me in private? =
</span></font><font
size=3D2 color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:
Wingdings;color:navy'>J</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:
Wingdings;color:navy'><span style=3D'mso-list:Ignore'>&Oslash;<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2><span
style=3D'font-size:10.0pt'>as an employee of a =
carrier<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>I worked most of my career for carriers, so that&#82where.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Automatic
updates from the application provider: This is current PC SW state of =
the art
and works for both the (1) P2P software in the access device and (2) for =
the
application software, such as presence, IM, voice, multimedia, etc. No =
or
minimal is staff required.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><span style=3D'mso-list:Ignore'>-<font size=3D1 =
face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Last but
not least, besides SIP enabled communications, the overlay can also =
serve for many
other applications for your users: Content distribution, application =
layer
multicast for conferences, directory search, IM+A/V chat rooms, name =
services, etc.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>All of the above can be easily =
implemented
by porting well documented open source software into the residential =
access box
or in the integrated access device (IAD) for enterprises. Just check out =
<a
href=3D"http://opendht.org/">http://opendht.org/</a> and other similar =
sites.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Please don&#8217;t take my word for =
it,
just make for yourself a comparison table for your network. If you =
can&#8217;t
share the comparison with the list, can you share it with me in private? =
</span></font><font
size=3D2 color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:
Wingdings;color:navy'>J</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:
Wingdings;color:navy'><span style=3D'mso-list:Ignore'>&Oslash;<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2><span
style=3D'font-size:10.0pt'>as an employee of a =
carrier<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>I worked most of my career for carriers, so that&#82trar/proxy was replaced by a P2P sip community, the  
> differences, if
> >
> > any, would hopefully be more a function of the implementation and  
> the
> > business models of those involved than the architecture.
> >
> > (I gather the general assumption is that a P2P setup will be  
> *free*. But
> >
> > I have a hard time believing that. If most of the usage is by mobile
> > devices that can't be peers, then somebody will have to pay for  
> enough
> > peers to support them. If it isn't free, then how is it better  
> than a
> > well engineered C/S system?)
> >
> > So I think the key thing here is that some features will require  
> getting
> >
> > some help from another node. There ought to be the option to pick a
> > different source for each helper you require, and an ability for  
> it all
> > to play together.
> >
> >       Paul
> >
> > Eunsoo Shim wrote:
> >> Please see my inline comment.
> >>
> >> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com
> >> <mailto:pkyzivat@cisco.com>> wrote:
> >>
> >>
> >>
> >>     Henry Sinnreich wrote:
> >>      > David Oran wrote (with regard to voice mail):
> >>      >
> >>      >> I'm not saying this can't be made to work, only that it  
> isn't
> >>      > immediately >obvious that it has advantages over a classic
> >>     application
> >>      > server >approach.
> >>      >
> >>      > The answer for VM is "it depends":
> >>      >
> >>
> >>
> >> I agree. It really depends. Certainly there are tradeoffs.
> >>
> >>      > There are several commercial P2P IP PBX solutions without  
> any
> >>     server for
> >>      > VM or anything else. No doubt the IT organization  
> appreciates
> > just
> >>      > having to plug in the IP phones and GWY to the PSTN  
> without any
> >>      > configuration ever for VM or any other PBX feature.
> >>
> >>     I don't understand. Are you saying they don't have VM, or that
> > they
> >>     don't have a *server* for VM?
> >>
> >>
> >> I guess they don't have a  *server* for  VM.
> >>
> >>      > For public P2P SIP networks there are two more scenarios  
> where
> > VM can
> >>      > reside (and without ever spending one cent on VM servers  
> + IT
> >>     systems):
> >>      >
> >>      > - In Cable and DSL service provider networks: The  
> residential
> >>     router can
> >>      > act as a voice recorder
> >>
> >>     That is simply an example of the user having an appliance of  
> his
> > own
> >>     that provides VM service.
> >>
> >>      > and P2P can cover the not too frequent cases,
> >>      > where the router is not in operation, so the data is  
> backed up
> > in
> >>     other
> >>      > peer residential gateways (encrypted).
> >>
> >>     I guess I just need to have more info about how this would work
> > before I
> >>     will be convinced it is feasible and trustworthy.
> >>
> >>
> >> Well, 'trustworthy' could be  considered in many angles.
> >> If it is about privacy of the message, a public key based  
> encryption
> >> would provide acceptable privacy.
> >> If it is about reliability of the message delivery, well, a P2P  
> based
> >> asynchronous message delivery (like VM) is most likely less  
> reliable
> >> than a well managed server based system.
> >> However, my experience with Skype's asynchronous message  
> delivery was
> >> not bad. Actually I don't see any significant difference between it
> > and
> >> my cellular service provider's VM service. :-)
> >> Reliability is always a challenge for P2P, for sure. But, I  
> believe it
> >
> >> is feasible to build a P2P system for VM acceptable for many
> > scenarios.
> >>      > - In mobile networks: The VM can reside in quite stable  
> peers
> >>     inside the
> >>      > wireless base station network. The peers in the base station
> > network
> >>      > need no configuration, etc.
> >>
> >>     I don't understand. I guess that could be true if the peers are
> > willing
> >>     to store an arbitrary amount of VM indefinitely for anybody. Is
> > that
> >>     believable?
> >>
> >>
> >> It depends.
> >> In a very nice environment where all the peers are willing 17;s what =
prompted
the above considerations.</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, =
Henry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
colin.pons@kpn.com [mailto:colin.pons@kpn.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, April =
04, 2007
12:38 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> pkyzivat@cisco.com; =
Henry
Sinnreich<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
p2psip@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; mhammer@cisco.com; oran@cisco.com; =
<st1:PersonName
w:st=3D"on">p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>; <st1:PersonName =
w:st=3D"on">sipping@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] Re: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>Henry,<br>
<br>
I like your idea of deploying sip peers in edge devices. However, as an
employee of a carrier I would like to see how a carrier is able to =
provide
service asurance to be able to provide compliant handling. Many of our
customers do not understand how to install these gateways themselves, =
let alone
how to troubleshoot.<br>
<br>
This is even more important for enterprises, which often&nbsp; insist on =
SLAs
which include troubleshoot resolution limits.<br>
<br>
-----Original Message-----<br>
From: &quot;<st1:PersonName w:st=3D"on">Paul =
Kyzivat</st1:PersonName>&quot;
&lt;pkyzivat@cisco.com&gt;<br>
To: &quot;Henry Sinnreich&quot; &lt;hsinnrei@adobe.com&gt;<br>
Cc: &quot;<st1:PersonName w:st=3D"on">P2PSIP Mailing =
List</st1:PersonName>&quot;
&lt;p2psip@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName>&gt;; =
&quot;<st1:PersonName
w:st=3D"on">Michael Hammer</st1:PersonName> (mhammer)&quot;
&lt;mhammer@cisco.com&gt;; &quot;<st1:PersonName w:st=3D"on">David R =
<st1:City
 w:st=3D"on"><st1:place =
w:st=3D"on">Oran</st1:place></st1:City></st1:PersonName>&quot;
&lt;oran@cisco.com&gt;; &quot;<st1:PersonName =
w:st=3D"on">p2p<st1:PersonName
 w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&quot;
&lt;<st1:PersonName w:st=3D"on">p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>&gt;; =
&quot;<st1:PersonName
w:st=3D"on">sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&quot;
&lt;<st1:PersonName w:st=3D"on">sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&gt;<br>
Sent: 3-4-07 01:11<br>
Subject: [P2PSIP] Re: [P2P<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>] RE:
[Sipping] Simple SIP usage scenario<br>
<br>
<br>
<br>
Henry 17;s what =
prompted
the above considerations.</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, =
Henry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
colin.pons@kpn.com [mailto:colin.pons@kpn.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, April =
04, 2007
12:38 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> pkyzivat@cisco.com; =
Henry
Sinnreich<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
p2psip@ietf.o<st1:PersonName
w:st=3D"on">rg</st1:PersonName>; mhammer@cisco.com; oran@cisco.com; =
<st1:PersonName
w:st=3D"on">p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>; <st1:PersonName =
w:st=3D"on">sipping@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [P2PSIP] Re: =
[P2P<st1:PersonName
w:st=3D"on">rg</st1:PersonName>] RE: [Sipping] Simple SIP usage =
scenario</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>Henry,<br>
<br>
I like your idea of deploying sip peers in edge devices. However, as an
employee of a carrier I would like to see how a carrier is able to =
provide
service asurance to be able to provide compliant handling. Many of our
customers do not understand how to install these gateways themselves, =
let alone
how to troubleshoot.<br>
<br>
This is even more important for enterprises, which often&nbsp; insist on =
SLAs
which include troubleshoot resolution limits.<br>
<br>
-----Original Message-----<br>
From: &quot;<st1:PersonName w:st=3D"on">Paul =
Kyzivat</st1:PersonName>&quot;
&lt;pkyzivat@cisco.com&gt;<br>
To: &quot;Henry Sinnreich&quot; &lt;hsinnrei@adobe.com&gt;<br>
Cc: &quot;<st1:PersonName w:st=3D"on">P2PSIP Mailing =
List</st1:PersonName>&quot;
&lt;p2psip@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName>&gt;; =
&quot;<st1:PersonName
w:st=3D"on">Michael Hammer</st1:PersonName> (mhammer)&quot;
&lt;mhammer@cisco.com&gt;; &quot;<st1:PersonName w:st=3D"on">David R =
<st1:City
 w:st=3D"on"><st1:place =
w:st=3D"on">Oran</st1:place></st1:City></st1:PersonName>&quot;
&lt;oran@cisco.com&gt;; &quot;<st1:PersonName =
w:st=3D"on">p2p<st1:PersonName
 w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&quot;
&lt;<st1:PersonName w:st=3D"on">p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>&gt;; =
&quot;<st1:PersonName
w:st=3D"on">sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&quot;
&lt;<st1:PersonName w:st=3D"on">sipping@ietf.o<st1:PersonName =
w:st=3D"on">rg</st1:PersonName></st1:PersonName>&gt;<br>
Sent: 3-4-07 01:11<br>
Subject: [P2PSIP] Re: [P2P<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>] RE:
[Sipping] Simple SIP usage scenario<br>
<br>
<br>
<br>
Henry to
> > cooperate
> >> at their best, the peers will store as much as they can. In a tough
> >> environment, the situation will be different.
> >>
> >>     This seems to translate to a model where it is assumed that  
> those
> > nodes
> >>     that are on most of the time will be willing to provide VM  
> storage
> > for
> >>     those nodes that aren't on most of the time.
> >>
> >>
> >> This is again related to reliability of P2P systems or topics like
> > free
> >> riders and reputation.
> >> A P2P system is a community or society. To be simple, if many of  
> the
> >> members are bad, the community won't work well. If the majority  
> of the
> >
> >> members are good, the community will work well or reasonably.
> >>
> >>      > Add to this the conferencing capability coming from p2p
> > application
> >>      > layer multicast, the SIP e2e control capabilities (for  
> such as
> >>      > auto-attendant, agent workstation, etc.) and one has to  
> wonder
> > why IT
> >>      > networks, public VoIP networks and end users should  
> support the
> > huge
> >>      > cost of hand engineering, testing, monitoring, maintaining
> > server
> >>     based
> >>      > VoIP networks. P2P self configuration is nothing less that
> > automation
> >>      > applied to VoIP, plus the shifting of computing to the
> > endpoints,
> >>     where
> >>      > there is an abundance of unused CPU, storage, bandwidth and
> >>     electricity.
> >>      >
> >>      > Eric Burger also notes IM changes completely the usage  
> for VM
> > and may
> >>      > make unnecessary to place calls on VM in the first place.
> >>
> >>     I find this more promising.
> >>
> >>
> >>
> >>
> >> In overall, are we discussing if P2P systems based VM can work? I
> > think
> >> it can work.  Just it depends on many things.
> >> If it is not super-reliable, should we disregard it? I would say  
> no.
> >>
> >> On the other hand, do we have to abandon client server based VM and
> >> switch to P2P system based VM? It is upto each of us.
> >> Client server based VM systems are already there.
> >> So why don't we work on P2P based VM now?
> >>
> >> Thanks.
> >>
> >> Eunsoo
> >
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip


--Apple-Mail-10--203761590
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Colin,<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>With the right P2P =
software, the devices need no configuration at all, the configuration =
data can be derived from the "hardware id" and a preloaded X509 =
certificate while the mapping between services and the hardware can be =
done centralized and allow the business model the operator wishes with =
minimal opex.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Adrian</DIV><DIV><BR><DIV><DI=
V>On Apr 4, 2007, at 7:37 AM, &lt;<A =
href=3D"mailto:colin.pons@kpn.com">colin.pons@kpn.com</A>&gt; &lt;<A =
href=3D"mailto:colin.pons@kpn.com">colin.pons@kpn.com</A>&gt; =
wrote:</DIV><BR class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><P><FONT size=3D"2">Henry,<BR> <BR> I like your idea of =
deploying sip peers in edge devices. However, as an employee of a =
carrier I would like to see how a carrier is able to provide service =
asurance to be able to provide compliant handling. Many of our customers =
do not understand how to install these gateways themselves, let alone =
how to troubleshoot.<BR> <BR> This is even more important for =
enterprises, which often=A0 insist on SLAs which include troubleshoot =
resolution limits.<BR> <BR> -----Original Message-----<BR> From: "Paul =
Kyzivat" &lt;<A =
href=3D"mailto:pkyzivat@cisco.com">pkyzivat@cisco.com</A>&gt;<BR> To: =
"Henry Sinnreich" &lt;<A =
href=3D"mailto:hsinnrSinnreich wrote:<br>
&gt; Paul,<br>
&gt;<br>
&gt;&gt; I more or less agree with the final conclusion below.<br>
&gt;<br>
&gt; This is good starting point to discuss some usage scenarios.<br>
&gt;<br>
&gt; Putting on my former hat as an employee for a carrier, I cannot =
overlook<br>
&gt; the following:<br>
&gt;<br>
&gt; P2P SIP implemented correctly in the residential access box or =
cable<br>
&gt; set-top box indeed is a good or better replacement for the entire =
VoIP<br>
&gt; network infrastructure (cost, operations, new services, etc).<br>
&gt; Integrated access devices for the enterprise can probably play a =
similar<br>
&gt; role, not to mention existing P2P PBX products (please refer to all =
the<br>
&gt; advantages of P2P that need not repeated here).<br>
&gt;<br>
&gt; What do people think of these three usage scenarios for P2P =
SIP:<br>
&gt; - SIP peer in the DSL access device,<br>
&gt; - SIP peer in the cable access device,<br>
<br>
These seem quite reasonable, assuming that a device connected at =
this<br>
point is able to function properly as a peer. (I haven't been =
following<br>
what the assumptions are about required network capabilities of =
peers.)<br>
<br>
&gt; - SIP peer in enterprise network integrated access device =
(IAD).<br>
<br>
I think this depends greatly on what expectations / contractual<br>
guarantees the enterprise has. Its unclear to me what guarantees can =
be<br>
made about a P2PSIP network will be able to make, and its unclear =
what<br>
kind of infrastructure would be installed by/for someone willing to =
make<br>
guarantees.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Paul<br>
<br>
&gt; Note that these examples imply very low churn for the peers and add =
the<br>
&gt; data retention resilience of P2P (geographic diversity is native =
and<br>
&gt; mobile, etc.). Incidentally, NAT traversal may also not be a =
problem, or<br>
&gt; at least an easier problem.<br>
&gt;<br>
&gt; What do you all think?<br>
&gt;<br>
&gt; I have taken the liberty to copy the P2P SIP list, since the low =
churn<br>
&gt; scenarios are of interest for the DHT selection. Or just pick the =
same<br>
&gt; DHT for all scenarios anyway? I don't think so.<br>
&gt;<br>
&gt; Thanks, Henry<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: <st1:PersonName w:st=3D"on">Paul Kyzivat</st1:PersonName> [<a
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</a>]<br>
&gt; Sent: Friday, March 30, 2007 6:31 PM<br>
&gt; To: <st1:PersonName w:st=3D"on">Eunsoo Shim</st1:PersonName><br>
&gt; Cc: Henry Sinnreich; <st1:PersonName w:st=3D"on">Michael =
Hammer</st1:PersonName>
(mhammer); <st1:PersonName w:st=3D"on">David R =
Oran</st1:PersonName>;<br>
&gt; <st1:PersonName w:st=3D"on">p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>; <st1:PersonName =
w:st=3D"on">sipping@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>; zhuxian<br>
&gt; Subject: Re: [P2P<st1:PersonName w:st=3D"on">rg</st1:PersonName>] =
RE:
[Sipping] Simple SIP usage scenario<br>
&gt;<br>
&gt; I more or less agree with the final conclusion below.<br>
&gt;<br>
&gt; My main point here is that P2P and C/S need not be enemies. Nor is =
a<br>
&gt; total C/S system necessarily evil. What is most evil is *bundling* =
of<br>
&gt; services that prevents freedom of choice.<br>
&gt;<br>
&gt; I think I would be quite happy with a SP that provides a =
registrar/proxy<br>
&gt;<br>
&gt; and allows me to provide all other features as I see fit - by =
taking<br>
&gt; them ala carte from the SP, or subscribing to them from one or =
more<br>
&gt; other SPs, or by providing them myself via appliances I own. If =
that<br>
&gt; registrar/proxy was replaced by a P2P sip community, the =
differences, if<br>
&gt;<br>
&gt; any, would hopefully be more a function of the implementation and =
the<br>
&gt; business models of those involved than the architecture.<br>
&gt;<br>
&gt; (I gather the general assumption is that a P2P setup will be =
*free*. But<br>
&gt;<br>
&Sinnreich wrote:<br>
&gt; Paul,<br>
&gt;<br>
&gt;&gt; I more or less agree with the final conclusion below.<br>
&gt;<br>
&gt; This is good starting point to discuss some usage scenarios.<br>
&gt;<br>
&gt; Putting on my former hat as an employee for a carrier, I cannot =
overlook<br>
&gt; the following:<br>
&gt;<br>
&gt; P2P SIP implemented correctly in the residential access box or =
cable<br>
&gt; set-top box indeed is a good or better replacement for the entire =
VoIP<br>
&gt; network infrastructure (cost, operations, new services, etc).<br>
&gt; Integrated access devices for the enterprise can probably play a =
similar<br>
&gt; role, not to mention existing P2P PBX products (please refer to all =
the<br>
&gt; advantages of P2P that need not repeated here).<br>
&gt;<br>
&gt; What do people think of these three usage scenarios for P2P =
SIP:<br>
&gt; - SIP peer in the DSL access device,<br>
&gt; - SIP peer in the cable access device,<br>
<br>
These seem quite reasonable, assuming that a device connected at =
this<br>
point is able to function properly as a peer. (I haven't been =
following<br>
what the assumptions are about required network capabilities of =
peers.)<br>
<br>
&gt; - SIP peer in enterprise network integrated access device =
(IAD).<br>
<br>
I think this depends greatly on what expectations / contractual<br>
guarantees the enterprise has. Its unclear to me what guarantees can =
be<br>
made about a P2PSIP network will be able to make, and its unclear =
what<br>
kind of infrastructure would be installed by/for someone willing to =
make<br>
guarantees.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Paul<br>
<br>
&gt; Note that these examples imply very low churn for the peers and add =
the<br>
&gt; data retention resilience of P2P (geographic diversity is native =
and<br>
&gt; mobile, etc.). Incidentally, NAT traversal may also not be a =
problem, or<br>
&gt; at least an easier problem.<br>
&gt;<br>
&gt; What do you all think?<br>
&gt;<br>
&gt; I have taken the liberty to copy the P2P SIP list, since the low =
churn<br>
&gt; scenarios are of interest for the DHT selection. Or just pick the =
same<br>
&gt; DHT for all scenarios anyway? I don't think so.<br>
&gt;<br>
&gt; Thanks, Henry<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: <st1:PersonName w:st=3D"on">Paul Kyzivat</st1:PersonName> [<a
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</a>]<br>
&gt; Sent: Friday, March 30, 2007 6:31 PM<br>
&gt; To: <st1:PersonName w:st=3D"on">Eunsoo Shim</st1:PersonName><br>
&gt; Cc: Henry Sinnreich; <st1:PersonName w:st=3D"on">Michael =
Hammer</st1:PersonName>
(mhammer); <st1:PersonName w:st=3D"on">David R =
Oran</st1:PersonName>;<br>
&gt; <st1:PersonName w:st=3D"on">p2p<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>; <st1:PersonName =
w:st=3D"on">sipping@ietf.o<st1:PersonName
 w:st=3D"on">rg</st1:PersonName></st1:PersonName>; zhuxian<br>
&gt; Subject: Re: [P2P<st1:PersonName w:st=3D"on">rg</st1:PersonName>] =
RE:
[Sipping] Simple SIP usage scenario<br>
&gt;<br>
&gt; I more or less agree with the final conclusion below.<br>
&gt;<br>
&gt; My main point here is that P2P and C/S need not be enemies. Nor is =
a<br>
&gt; total C/S system necessarily evil. What is most evil is *bundling* =
of<br>
&gt; services that prevents freedom of choice.<br>
&gt;<br>
&gt; I think I would be quite happy with a SP that provides a =
registrar/proxy<br>
&gt;<br>
&gt; and allows me to provide all other features as I see fit - by =
taking<br>
&gt; them ala carte from the SP, or subscribing to them from one or =
more<br>
&gt; other SPs, or by providing them myself via appliances I own. If =
that<br>
&gt; registrar/proxy was replaced by a P2P sip community, the =
differences, if<br>
&gt;<br>
&gt; any, would hopefully be more a function of the implementation and =
the<br>
&gt; business models of those involved than the architecture.<br>
&gt;<br>
&gt; (I gather the general assumption is that a P2P setup will be =
*free*. But<br>
&gt;<br>
&ei@adobe.com">hsinnrei@adobe.com</A>&gt;<BR> Cc: =
"P2PSIP Mailing List" &lt;<A =
href=3D"mailto:p2psip@ietf.org">p2psip@ietf.org</A>&gt;; "Michael Hammer =
(mhammer)" &lt;<A =
href=3D"mailto:mhammer@cisco.com">mhammer@cisco.com</A>&gt;; "David R =
Oran" &lt;<A href=3D"mailto:oran@cisco.com">oran@cisco.com</A>&gt;; "<A =
href=3D"mailto:p2prg@ietf.org">p2prg@ietf.org</A>" &lt;<A =
href=3D"mailto:p2prg@ietf.org">p2prg@ietf.org</A>&gt;; "<A =
href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A>" &lt;<A =
href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A>&gt;<BR> Sent: =
3-4-07 01:11<BR> Subject: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP =
usage scenario<BR> <BR> <BR> <BR> Henry Sinnreich wrote:<BR> &gt; =
Paul,<BR> &gt;<BR> &gt;&gt; I more or less agree with the final =
conclusion below.<BR> &gt;<BR> &gt; This is good starting point to =
discuss some usage scenarios.<BR> &gt;<BR> &gt; Putting on my former hat =
as an employee for a carrier, I cannot overlook<BR> &gt; the =
following:<BR> &gt;<BR> &gt; P2P SIP implemented correctly in the =
residential access box or cable<BR> &gt; set-top box indeed is a good or =
better replacement for the entire VoIP<BR> &gt; network infrastructure =
(cost, operations, new services, etc).<BR> &gt; Integrated access =
devices for the enterprise can probably play a similar<BR> &gt; role, =
not to mention existing P2P PBX products (please refer to all the<BR> =
&gt; advantages of P2P that need not repeated here).<BR> &gt;<BR> &gt; =
What do people think of these three usage scenarios for P2P SIP:<BR> =
&gt; - SIP peer in the DSL access device,<BR> &gt; - SIP peer in the =
cable access device,<BR> <BR> These seem quite reasonable, assuming that =
a device connected at this<BR> point is able to function properly as a =
peer. (I haven't been following<BR> what the assumptions are about =
required network capabilities of peers.)<BR> <BR> &gt; - SIP peer in =
enterprise network integrated access device (IAD).<BR> <BR> I think this =
depends greatly on what expectations / contractual<BR> guarantees the =
enterprise has. Its unclear to me what guarantees can be<BR> made about =
a P2PSIP network will be able to make, and its unclear what<BR> kind of =
infrastructure would be installed by/for someone willing to make<BR> =
guarantees.<BR> <BR> =A0=A0=A0=A0=A0=A0=A0 Paul<BR> <BR> &gt; Note that =
these examples imply very low churn for the peers and add the<BR> &gt; =
data retention resilience of P2P (geographic diversity is native and<BR> =
&gt; mobile, etc.). Incidentally, NAT traversal may also not be a =
problem, or<BR> &gt; at least an easier problem.<BR> &gt;<BR> &gt; What =
do you all think?<BR> &gt;<BR> &gt; I have taken the liberty to copy the =
P2P SIP list, since the low churn<BR> &gt; scenarios are of interest for =
the DHT selection. Or just pick the same<BR> &gt; DHT for all scenarios =
anyway? I don't think so.<BR> &gt;<BR> &gt; Thanks, Henry<BR> &gt;<BR> =
&gt;<BR> &gt; -----Original Message-----<BR> &gt; From: Paul Kyzivat [<A =
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</A>]<BR> =
&gt; Sent: Friday, March 30, 2007 6:31 PM<BR> &gt; To: Eunsoo Shim<BR> =
&gt; Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;<BR> =
&gt; <A href=3D"mailto:p2prg@ietf.org">p2prg@ietf.org</A>; <A =
href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A>; zhuxian<BR> &gt; =
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario<BR> =
&gt;<BR> &gt; I more or less agree with the final conclusion below.<BR> =
&gt;<BR> &gt; My main point here is that P2P and C/S need not be =
enemies. Nor is a<BR> &gt; total C/S system necessarily evil. What is =
most evil is *bundling* of<BR> &gt; services that prevents freedom of =
choice.<BR> &gt;<BR> &gt; I think I would be quite happy with a SP that =
provides a registrar/proxy<BR> &gt;<BR> &gt; and allows me to provide =
all other features as I see fit - by taking<BR> &gt; them ala carte from =
the SP, or subscribing to them from one or more<BR> &gt; other SPs, or =
by providing them myself via appliances I own. If that<BR> &gt; =
reggt; I have a hard time believing that. If most of the usage is by =
mobile<br>
&gt; devices that can't be peers, then somebody will have to pay for =
enough<br>
&gt; peers to support them. If it isn't free, then how is it better than =
a<br>
&gt; well engineered C/S system?)<br>
&gt;<br>
&gt; So I think the key thing here is that some features will require =
getting<br>
&gt;<br>
&gt; some help from another node. There ought to be the option to pick =
a<br>
&gt; different source for each helper you require, and an ability for it =
all<br>
&gt; to play together.<br>
&gt;<br>
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Paul<br>
&gt;<br>
&gt; <st1:PersonName w:st=3D"on">Eunsoo Shim</st1:PersonName> wrote:<br>
&gt;&gt; Please see my inline comment.<br>
&gt;&gt;<br>
&gt;&gt; On 3/30/07, *<st1:PersonName w:st=3D"on">Paul =
Kyzivat</st1:PersonName>*
&lt;pkyzivat@cisco.com<br>
&gt;&gt; &lt;<a =
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</a>&gt;&gt;
wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; Henry Sinnreich wrote:<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; David Oran wrote (with =
regard to
voice mail):<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;&gt; I'm not saying this =
can't be
made to work, only that it isn't<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; immediately &gt;obvious that =
it has
advantages over a classic<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; application<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; server &gt;approach.<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; The answer for VM is =
&quot;it
depends&quot;:<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; I agree. It really depends. Certainly there are tradeoffs.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; There are several commercial =
P2P IP
PBX solutions without any<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; server for<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; VM or anything else. No =
doubt the
IT o<st1:PersonName w:st=3D"on">rg</st1:PersonName>anization =
appreciates<br>
&gt; just<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; having to plug in the IP =
phones and
GWY to the PSTN without any<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; configuration ever for VM or =
any
other PBX feature.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I don't understand. Are you saying they =
don't
have VM, or that<br>
&gt; they<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; don't have a *server* for VM?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; I guess they don't have a&nbsp; *server* for&nbsp; VM.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; For public P2P SIP networks =
there
are two more scenarios where<br>
&gt; VM can<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; reside (and without ever =
spending
one cent on VM servers + IT<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; systems):<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; - In Cable and DSL service =
provider
networks: The residential<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; router can<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; act as a voice recorder<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; That is simply an example of the user =
having
an appliance of his<br>
&gt; own<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; that provides VM service.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; and P2P can cover the not =
too
frequent cases,<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; where the router is not in
operation, so the data is backed up<br>
&gt; in<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; other<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; peer residential gateways
(encrypted).<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I guess I just need to have more info =
about
how this would work<br>
&gt; before I<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; will be convinced it is feasible and
trustworthy.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;gt; I have a hard time believing that. If most of the usage is by =
mobile<br>
&gt; devices that can't be peers, then somebody will have to pay for =
enough<br>
&gt; peers to support them. If it isn't free, then how is it better than =
a<br>
&gt; well engineered C/S system?)<br>
&gt;<br>
&gt; So I think the key thing here is that some features will require =
getting<br>
&gt;<br>
&gt; some help from another node. There ought to be the option to pick =
a<br>
&gt; different source for each helper you require, and an ability for it =
all<br>
&gt; to play together.<br>
&gt;<br>
&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Paul<br>
&gt;<br>
&gt; <st1:PersonName w:st=3D"on">Eunsoo Shim</st1:PersonName> wrote:<br>
&gt;&gt; Please see my inline comment.<br>
&gt;&gt;<br>
&gt;&gt; On 3/30/07, *<st1:PersonName w:st=3D"on">Paul =
Kyzivat</st1:PersonName>*
&lt;pkyzivat@cisco.com<br>
&gt;&gt; &lt;<a =
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</a>&gt;&gt;
wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; Henry Sinnreich wrote:<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; David Oran wrote (with =
regard to
voice mail):<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;&gt; I'm not saying this =
can't be
made to work, only that it isn't<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; immediately &gt;obvious that =
it has
advantages over a classic<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; application<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; server &gt;approach.<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; The answer for VM is =
&quot;it
depends&quot;:<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; I agree. It really depends. Certainly there are tradeoffs.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; There are several commercial =
P2P IP
PBX solutions without any<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; server for<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; VM or anything else. No =
doubt the
IT o<st1:PersonName w:st=3D"on">rg</st1:PersonName>anization =
appreciates<br>
&gt; just<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; having to plug in the IP =
phones and
GWY to the PSTN without any<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; configuration ever for VM or =
any
other PBX feature.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I don't understand. Are you saying they =
don't
have VM, or that<br>
&gt; they<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; don't have a *server* for VM?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; I guess they don't have a&nbsp; *server* for&nbsp; VM.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; For public P2P SIP networks =
there
are two more scenarios where<br>
&gt; VM can<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; reside (and without ever =
spending
one cent on VM servers + IT<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; systems):<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; - In Cable and DSL service =
provider
networks: The residential<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; router can<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; act as a voice recorder<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; That is simply an example of the user =
having
an appliance of his<br>
&gt; own<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; that provides VM service.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; and P2P can cover the not =
too
frequent cases,<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; where the router is not in
operation, so the data is backed up<br>
&gt; in<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; other<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; peer residential gateways
(encrypted).<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I guess I just need to have more info =
about
how this would work<br>
&gt; before I<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; will be convinced it is feasible and
trustworthy.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;istrar/proxy was replaced by a P2P sip community, the differences, =
if<BR> &gt;<BR> &gt; any, would hopefully be more a function of the =
implementation and the<BR> &gt; business models of those involved than =
the architecture.<BR> &gt;<BR> &gt; (I gather the general assumption is =
that a P2P setup will be *free*. But<BR> &gt;<BR> &gt; I have a hard =
time believing that. If most of the usage is by mobile<BR> &gt; devices =
that can't be peers, then somebody will have to pay for enough<BR> &gt; =
peers to support them. If it isn't free, then how is it better than =
a<BR> &gt; well engineered C/S system?)<BR> &gt;<BR> &gt; So I think the =
key thing here is that some features will require getting<BR> &gt;<BR> =
&gt; some help from another node. There ought to be the option to pick =
a<BR> &gt; different source for each helper you require, and an ability =
for it all<BR> &gt; to play together.<BR> &gt;<BR> &gt; =A0=A0=A0=A0=A0 =
Paul<BR> &gt;<BR> &gt; Eunsoo Shim wrote:<BR> &gt;&gt; Please see my =
inline comment.<BR> &gt;&gt;<BR> &gt;&gt; On 3/30/07, *Paul Kyzivat* =
&lt;<A href=3D"mailto:pkyzivat@cisco.com">pkyzivat@cisco.com</A><BR> =
&gt;&gt; &lt;<A =
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</A>&gt;&gt; =
wrote:<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 =
Henry Sinnreich wrote:<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; David Oran wrote =
(with regard to voice mail):<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt;&gt; I'm not saying this can't be made to =
work, only that it isn't<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; immediately =
&gt;obvious that it has advantages over a classic<BR> &gt;&gt;=A0=A0=A0=A0=
 application<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; server &gt;approach.<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; The answer =
for VM is "it depends":<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> =
&gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt; I agree. It really depends. Certainly =
there are tradeoffs.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; There =
are several commercial P2P IP PBX solutions without any<BR> &gt;&gt;=A0=A0=
=A0=A0 server for<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; VM or anything else. =
No doubt the IT organization appreciates<BR> &gt; just<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt; having to plug in the IP phones and GWY to the PSTN without =
any<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; configuration ever for VM or any =
other PBX feature.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 I don't =
understand. Are you saying they don't have VM, or that<BR> &gt; they<BR> =
&gt;&gt;=A0=A0=A0=A0 don't have a *server* for VM?<BR> &gt;&gt;<BR> =
&gt;&gt;<BR> &gt;&gt; I guess they don't have a=A0 *server* for=A0 =
VM.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; For public P2P SIP =
networks there are two more scenarios where<BR> &gt; VM can<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt; reside (and without ever spending one cent =
on VM servers + IT<BR> &gt;&gt;=A0=A0=A0=A0 systems):<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; - In Cable and DSL service =
provider networks: The residential<BR> &gt;&gt;=A0=A0=A0=A0 router =
can<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; act as a voice recorder<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 That is simply an example of the user =
having an appliance of his<BR> &gt; own<BR> &gt;&gt;=A0=A0=A0=A0 that =
provides VM service.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; and =
P2P can cover the not too frequent cases,<BR> &gt;&gt;=A0=A0=A0=A0=A0 =
&gt; where the router is not in operation, so the data is backed up<BR> =
&gt; in<BR> &gt;&gt;=A0=A0=A0=A0 other<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; =
peer residential gateways (encrypted).<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=
 I guess I just need to have more info about how this would work<BR> =
&gt; before I<BR> &gt;&gt;=A0=A0=A0=A0 will be convinced it is feasible =
and trustworthy.<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt; Well, =
'trustworthy' could be=A0 considered in many angles.<BR> &gt;&gt; If it =
is about privacy of the message, a public key based encryption<BR> =
&gt;&gt; would provide acce Well, 'trustworthy' could be&nbsp; considered in many =
angles.<br>
&gt;&gt; If it is about privacy of the message, a public key based =
encryption<br>
&gt;&gt; would provide acceptable privacy.<br>
&gt;&gt; If it is about reliability of the message delivery, well, a P2P =
based<br>
&gt;&gt; asynchronous message delivery (like VM) is most likely less =
reliable<br>
&gt;&gt; than a well managed server based system.<br>
&gt;&gt; However, my experience with Skype's asynchronous message =
delivery was<br>
&gt;&gt; not bad. Actually I don't see any significant difference =
between it<br>
&gt; and<br>
&gt;&gt; my cellular service provider's VM service. :-)<br>
&gt;&gt; Reliability is always a challenge for P2P, for sure. But, I =
believe it<br>
&gt;<br>
&gt;&gt; is feasible to build a P2P system for VM acceptable for =
many<br>
&gt; scenarios.<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; - In mobile networks: The VM =
can
reside in quite stable peers<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; inside the<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; wireless base station =
network. The
peers in the base station<br>
&gt; network<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; need no configuration, =
etc.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I don't understand. I guess that could =
be true
if the peers are<br>
&gt; willing<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; to store an arbitrary amount of VM
indefinitely for anybody. Is<br>
&gt; that<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; believable?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; It depends.<br>
&gt;&gt; In a very nice environment where all the peers are willing =
to<br>
&gt; cooperate<br>
&gt;&gt; at their best, the peers will store as much as they can. In a =
tough<br>
&gt;&gt; environment, the situation will be different.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; This seems to translate to a model =
where it is
assumed that those<br>
&gt; nodes<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; that are on most of the time will be =
willing
to provide VM storage<br>
&gt; for<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; those nodes that aren't on most of the =
time.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; This is again related to reliability of P2P systems or topics =
like<br>
&gt; free<br>
&gt;&gt; riders and reputation.<br>
&gt;&gt; A P2P system is a community or society. To be simple, if many =
of the<br>
&gt;&gt; members are bad, the community won't work well. If the majority =
of the<br>
&gt;<br>
&gt;&gt; members are good, the community will work well or =
reasonably.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Add to this the conferencing
capability coming from p2p<br>
&gt; application<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; layer multicast, the SIP e2e
control capabilities (for such as<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; auto-attendant, agent =
workstation,
etc.) and one has to wonder<br>
&gt; why IT<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; networks, public VoIP =
networks and
end users should support the<br>
&gt; huge<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; cost of hand engineering, =
testing,
monitoring, maintaining<br>
&gt; server<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; based<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; VoIP networks. P2P self
configuration is nothing less that<br>
&gt; automation<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; applied to VoIP, plus the =
shifting
of computing to the<br>
&gt; endpoints,<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; where<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; there is an abundance of =
unused
CPU, storage, bandwidth and<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; electricity.<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Eric Bu<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>er
also notes IM changes completely the usage for VM<br>
&gt; and may<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; make unnecessary to place =
calls on
VM in the first place.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I find this more promising.<br>
&g Well, 'trustworthy' could be&nbsp; considered in many =
angles.<br>
&gt;&gt; If it is about privacy of the message, a public key based =
encryption<br>
&gt;&gt; would provide acceptable privacy.<br>
&gt;&gt; If it is about reliability of the message delivery, well, a P2P =
based<br>
&gt;&gt; asynchronous message delivery (like VM) is most likely less =
reliable<br>
&gt;&gt; than a well managed server based system.<br>
&gt;&gt; However, my experience with Skype's asynchronous message =
delivery was<br>
&gt;&gt; not bad. Actually I don't see any significant difference =
between it<br>
&gt; and<br>
&gt;&gt; my cellular service provider's VM service. :-)<br>
&gt;&gt; Reliability is always a challenge for P2P, for sure. But, I =
believe it<br>
&gt;<br>
&gt;&gt; is feasible to build a P2P system for VM acceptable for =
many<br>
&gt; scenarios.<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; - In mobile networks: The VM =
can
reside in quite stable peers<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; inside the<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; wireless base station =
network. The
peers in the base station<br>
&gt; network<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; need no configuration, =
etc.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I don't understand. I guess that could =
be true
if the peers are<br>
&gt; willing<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; to store an arbitrary amount of VM
indefinitely for anybody. Is<br>
&gt; that<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; believable?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; It depends.<br>
&gt;&gt; In a very nice environment where all the peers are willing =
to<br>
&gt; cooperate<br>
&gt;&gt; at their best, the peers will store as much as they can. In a =
tough<br>
&gt;&gt; environment, the situation will be different.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; This seems to translate to a model =
where it is
assumed that those<br>
&gt; nodes<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; that are on most of the time will be =
willing
to provide VM storage<br>
&gt; for<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; those nodes that aren't on most of the =
time.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; This is again related to reliability of P2P systems or topics =
like<br>
&gt; free<br>
&gt;&gt; riders and reputation.<br>
&gt;&gt; A P2P system is a community or society. To be simple, if many =
of the<br>
&gt;&gt; members are bad, the community won't work well. If the majority =
of the<br>
&gt;<br>
&gt;&gt; members are good, the community will work well or =
reasonably.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Add to this the conferencing
capability coming from p2p<br>
&gt; application<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; layer multicast, the SIP e2e
control capabilities (for such as<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; auto-attendant, agent =
workstation,
etc.) and one has to wonder<br>
&gt; why IT<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; networks, public VoIP =
networks and
end users should support the<br>
&gt; huge<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; cost of hand engineering, =
testing,
monitoring, maintaining<br>
&gt; server<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; based<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; VoIP networks. P2P self
configuration is nothing less that<br>
&gt; automation<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; applied to VoIP, plus the =
shifting
of computing to the<br>
&gt; endpoints,<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; where<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; there is an abundance of =
unused
CPU, storage, bandwidth and<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; electricity.<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Eric Bu<st1:PersonName =
w:st=3D"on">rg</st1:PersonName>er
also notes IM changes completely the usage for VM<br>
&gt; and may<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &gt; make unnecessary to place =
calls on
VM in the first place.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; I find this more promising.<br>
&gptable privacy.<BR> &gt;&gt; If it is about =
reliability of the message delivery, well, a P2P based<BR> &gt;&gt; =
asynchronous message delivery (like VM) is most likely less reliable<BR> =
&gt;&gt; than a well managed server based system.<BR> &gt;&gt; However, =
my experience with Skype's asynchronous message delivery was<BR> =
&gt;&gt; not bad. Actually I don't see any significant difference =
between it<BR> &gt; and<BR> &gt;&gt; my cellular service provider's VM =
service. :-)<BR> &gt;&gt; Reliability is always a challenge for P2P, for =
sure. But, I believe it<BR> &gt;<BR> &gt;&gt; is feasible to build a P2P =
system for VM acceptable for many<BR> &gt; scenarios.<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt; - In mobile networks: The VM can reside in quite stable =
peers<BR> &gt;&gt;=A0=A0=A0=A0 inside the<BR> &gt;&gt;=A0=A0=A0=A0=A0 =
&gt; wireless base station network. The peers in the base station<BR> =
&gt; network<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; need no configuration, =
etc.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 I don't understand. I guess =
that could be true if the peers are<BR> &gt; willing<BR> &gt;&gt;=A0=A0=A0=
=A0 to store an arbitrary amount of VM indefinitely for anybody. Is<BR> =
&gt; that<BR> &gt;&gt;=A0=A0=A0=A0 believable?<BR> &gt;&gt;<BR> =
&gt;&gt;<BR> &gt;&gt; It depends.<BR> &gt;&gt; In a very nice =
environment where all the peers are willing to<BR> &gt; cooperate<BR> =
&gt;&gt; at their best, the peers will store as much as they can. In a =
tough<BR> &gt;&gt; environment, the situation will be different.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 This seems to translate to a model =
where it is assumed that those<BR> &gt; nodes<BR> &gt;&gt;=A0=A0=A0=A0 =
that are on most of the time will be willing to provide VM storage<BR> =
&gt; for<BR> &gt;&gt;=A0=A0=A0=A0 those nodes that aren't on most of the =
time.<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt; This is again related to =
reliability of P2P systems or topics like<BR> &gt; free<BR> &gt;&gt; =
riders and reputation.<BR> &gt;&gt; A P2P system is a community or =
society. To be simple, if many of the<BR> &gt;&gt; members are bad, the =
community won't work well. If the majority of the<BR> &gt;<BR> &gt;&gt; =
members are good, the community will work well or reasonably.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; Add to this the conferencing =
capability coming from p2p<BR> &gt; application<BR> &gt;&gt;=A0=A0=A0=A0=A0=
 &gt; layer multicast, the SIP e2e control capabilities (for such as<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt; auto-attendant, agent workstation, etc.) =
and one has to wonder<BR> &gt; why IT<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; =
networks, public VoIP networks and end users should support the<BR> &gt; =
huge<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; cost of hand engineering, testing, =
monitoring, maintaining<BR> &gt; server<BR> &gt;&gt;=A0=A0=A0=A0 =
based<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; VoIP networks. P2P self =
configuration is nothing less that<BR> &gt; automation<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt; applied to VoIP, plus the shifting of computing to the<BR> =
&gt; endpoints,<BR> &gt;&gt;=A0=A0=A0=A0 where<BR> &gt;&gt;=A0=A0=A0=A0=A0=
 &gt; there is an abundance of unused CPU, storage, bandwidth and<BR> =
&gt;&gt;=A0=A0=A0=A0 electricity.<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt; Eric Burger also notes IM changes =
completely the usage for VM<BR> &gt; and may<BR> &gt;&gt;=A0=A0=A0=A0=A0 =
&gt; make unnecessary to place calls on VM in the first place.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 I find this more promising.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0<BR> &gt;&gt;<BR> =
&gt;&gt;<BR> &gt;&gt; In overall, are we discussing if P2P systems based =
VM can work? I<BR> &gt; think<BR> &gt;&gt; it can work.=A0 Just it =
depends on many things.<BR> &gt;&gt; If it is not super-reliable, should =
we disregard it? I would say no.<BR> &gt;&gt;<BR> &gt;&gt; On the other =
hand, do we have to abandon client server based VM and<BR> &gt;&gt; =
switch to P2P system based VM? It is upto each of us.<BR> &gt;&gt; =
Client server baset;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; In overall, are we discussing if P2P systems based VM can work? =
I<br>
&gt; think<br>
&gt;&gt; it can work.&nbsp; Just it depends on many things.<br>
&gt;&gt; If it is not super-reliable, should we disregard it? I would =
say no.<br>
&gt;&gt;<br>
&gt;&gt; On the other hand, do we have to abandon client server based VM =
and<br>
&gt;&gt; switch to P2P system based VM? It is upto each of us.<br>
&gt;&gt; Client server based VM systems are already there.<br>
&gt;&gt; So why don't we work on P2P based VM now?<br>
&gt;&gt;&nbsp;<br>
&gt;&gt; Thanks.<br>
&gt;&gt;<br>
&gt;&gt; Eunsoo<br>
&gt;<br>
<br>
_______________________________________________<br>
P2PSIP mailing list<br>
P2PSIP@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName><br>
<a =
href=3D"https://www1.ietf.org/mailman/listinfo/p2psip">https://www1.ietf.=
org/mailman/listinfo/p2psip</a></span></font><o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01C776C7.CE6A1169--


--===============1723679838==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1723679838==--



From sipping-bounces@ietf.org Thu Apr 05 08:05:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZQgD-0006lT-Vd; Thu, 05 Apr 2007 08:03:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzyv-0003Af-2p; Wed, 04 Apr 2007 03:32:37 -0400
Received: from smtp-vbr9.xs4all.nl ([194.109.24.29])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYzyt-0007gL-QF; Wed, 04 Apr 2007 03:32:37 -0400
Received: from [192.168.0.6] (mit.xs4all.nl [213.84.95.205])
	by smtp-vbr9.xs4all.nl (8.13.8/8.13.8) with ESMTP id l347WGjb017787;
	Wed, 4 Apr 2007 09:32:21 +0200 (CEST)
	(envelope-from ag@ag-projects.com)
In-Reply-To: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
References: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
Mime-Version: 1.0 (Apple Message framework v752.2)
Message-Id: <1D065707-A33E-48CC-887B-0C5D6F0708CF@ag-projects.com>
From: Adrian Georgescu <ag@ag-projects.com>
Subject: Re: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Wed, 4 Apr 2007 09:32:13 +0200
To: "<colin.pons@kpn.com>" <colin.pons@kpn.com>
X-Mailer: Apple Mail (2.752.2)
X-Virus-Scanned: by XS4ALL Virus Scanner
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 9b281509fec590bb711c36d4c3ba4f74
X-Mailman-Approved-At: Thu, 05 Apr 2007 08:03:04 -0400
Cc: p2psip@ietf.org, mhammer@cisco.com, pkyzivat@cisco.com, oran@cisco.com,
	p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0170658415=="
Errors-To: sipping-bounces@ietf.org


--===============0170658415==
Content-Type: multipart/alternative; boundary=Apple-Mail-10--203761590


--Apple-Mail-10--203761590
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Colin,

With the right P2P software, the devices need no configuration at  
all, the configuration data can be derived from the "hardware id" and  
a preloadedt;&gt;<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; In overall, are we discussing if P2P systems based VM can work? =
I<br>
&gt; think<br>
&gt;&gt; it can work.&nbsp; Just it depends on many things.<br>
&gt;&gt; If it is not super-reliable, should we disregard it? I would =
say no.<br>
&gt;&gt;<br>
&gt;&gt; On the other hand, do we have to abandon client server based VM =
and<br>
&gt;&gt; switch to P2P system based VM? It is upto each of us.<br>
&gt;&gt; Client server based VM systems are already there.<br>
&gt;&gt; So why don't we work on P2P based VM now?<br>
&gt;&gt;&nbsp;<br>
&gt;&gt; Thanks.<br>
&gt;&gt;<br>
&gt;&gt; Eunsoo<br>
&gt;<br>
<br>
_______________________________________________<br>
P2PSIP mailing list<br>
P2PSIP@ietf.o<st1:PersonName w:st=3D"on">rg</st1:PersonName><br>
<a =
href=3D"https://www1.ietf.org/mailman/listinfo/p2psip">https://www1.ietf.=
org/mailman/listinfo/p2psip</a></span></font><o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01C776C7.CE6A1169--


--===============1723679838==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1723679838==--



From sipping-bounces@ietf.org Thu Apr 05 08:05:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZQgD-0006lT-Vd; Thu, 05 Apr 2007 08:03:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYzyv-0003Af-2p; Wed, 04 Apr 2007 03:32:37 -0400
Received: from smtp-vbr9.xs4all.nl ([194.109.24.29])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYzyt-0007gL-QF; Wed, 04 Apr 2007 03:32:37 -0400
Received: from [192.168.0.6] (mit.xs4all.nl [213.84.95.205])
	by smtp-vbr9.xs4all.nl (8.13.8/8.13.8) with ESMTP id l347WGjb017787;
	Wed, 4 Apr 2007 09:32:21 +0200 (CEST)
	(envelope-from ag@ag-projects.com)
In-Reply-To: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
References: <D3BA17190818B44CA969FB72EB43418D01832BBB@KKWNLEX181.kpnnl.local>
Mime-Version: 1.0 (Apple Message framework v752.2)
Message-Id: <1D065707-A33E-48CC-887B-0C5D6F0708CF@ag-projects.com>
From: Adrian Georgescu <ag@ag-projects.com>
Subject: Re: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
Date: Wed, 4 Apr 2007 09:32:13 +0200
To: "<colin.pons@kpn.com>" <colin.pons@kpn.com>
X-Mailer: Apple Mail (2.752.2)
X-Virus-Scanned: by XS4ALL Virus Scanner
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 9b281509fec590bb711c36d4c3ba4f74
X-Mailman-Approved-At: Thu, 05 Apr 2007 08:03:04 -0400
Cc: p2psip@ietf.org, mhammer@cisco.com, pkyzivat@cisco.com, oran@cisco.com,
	p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0170658415=="
Errors-To: sipping-bounces@ietf.org


--===============0170658415==
Content-Type: multipart/alternative; boundary=Apple-Mail-10--203761590


--Apple-Mail-10--203761590
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Colin,

With the right P2P software, the devices need no configuration at  
all, the configuration data can be derived from the "hardware id" and  
a preloadedd VM systems are already there.<BR> &gt;&gt; So why =
don't we work on P2P based VM now?<BR> &gt;&gt;=A0<BR> &gt;&gt; =
Thanks.<BR> &gt;&gt;<BR> &gt;&gt; Eunsoo<BR> &gt;<BR> <BR> =
_______________________________________________<BR> P2PSIP mailing =
list<BR> <A href=3D"mailto:P2PSIP@ietf.org">P2PSIP@ietf.org</A><BR> <A =
href=3D"https://www1.ietf.org/mailman/listinfo/p2psip">https://www1.ietf.o=
rg/mailman/listinfo/p2psip</A><BR> </FONT> </P><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">P2PSIP mailing list</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"mailto:P2PSIP@ietf.org">P2PSIP@ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/p2psip">https://www1.ietf.o=
rg/mailman/listinfo/p2psip</A></DIV> =
</BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-10--203761590--


--===============0170658415==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0170658415==--






 X509 certificate while the mapping between services and  
the hardware can be done centralized and allow the business model the  
operator wishes with minimal opex.

Adrian

On Apr 4, 2007, at 7:37 AM, <colin.pons@kpn.com> <colin.pons@kpn.com>  
wrote:

> Henry,
>
> I like your idea of deploying sip peers in edge devices. However,  
> as an employee of a carrier I would like to see how a carrier is  
> able to provide service asurance to be able to provide compliant  
> handling. Many of our customers do not understand how to install  
> these gateways themselves, let alone how to troubleshoot.
>
> This is even more important for enterprises, which often  insist on  
> SLAs which include troubleshoot resolution limits.
>
> -----Original Message-----
> From: "Paul Kyzivat" <pkyzivat@cisco.com>
> To: "Henry Sinnreich" <hsinnrei@adobe.com>
> Cc: "P2PSIP Mailing List" <p2psip@ietf.org>; "Michael Hammer  
> (mhammer)" <mhammer@cisco.com>; "David R Oran" <oran@cisco.com>;  
> "p2prg@ietf.org" <p2prg@ietf.org>; "sipping@ietf.org"  
> <sipping@ietf.org>
> Sent: 3-4-07 01:11
> Subject: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
>
>
>
> Henry Sinnreich wrote:
> > Paul,
> >
> >> I more or less agree with the final conclusion below.
> >
> > This is good starting point to discuss some usage scenarios.
> >
> > Putting on my former hat as an employee for a carrier, I cannot  
> overlook
> > the following:
> >
> > P2P SIP implemented correctly in the residential access box or cable
> > set-top box indeed is a good or better replacement for the entire  
> VoIP
> > network infrastructure (cost, operations, new services, etc).
> > Integrated access devices for the enterprise can probably play a  
> similar
> > role, not to mention existing P2P PBX products (please refer to  
> all the
> > advantages of P2P that need not repeated here).
> >
> > What do people think of these three usage scenarios for P2P SIP:
> > - SIP peer in the DSL access device,
> > - SIP peer in the cable access device,
>
> These seem quite reasonable, assuming that a device connected at this
> point is able to function properly as a peer. (I haven't been  
> following
> what the assumptions are about required network capabilities of  
> peers.)
>
> > - SIP peer in enterprise network integrated access device (IAD).
>
> I think this depends greatly on what expectations / contractual
> guarantees the enterprise has. Its unclear to me what guarantees  
> can be
> made about a P2PSIP network will be able to make, and its unclear what
> kind of infrastructure would be installed by/for someone willing to  
> make
> guarantees.
>
>         Paul
>
> > Note that these examples imply very low churn for the peers and  
> add the
> > data retention resilience of P2P (geographic diversity is native and
> > mobile, etc.). Incidentally, NAT traversal may also not be a  
> problem, or
> > at least an easier problem.
> >
> > What do you all think?
> >
> > I have taken the liberty to copy the P2P SIP list, since the low  
> churn
> > scenarios are of interest for the DHT selection. Or just pick the  
> same
> > DHT for all scenarios anyway? I don't think so.
> >
> > Thanks, Henry
> >
> >
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: Friday, March 30, 2007 6:31 PM
> > To: Eunsoo Shim
> > Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
> > p2prg@ietf.org; sipping@ietf.org; zhuxian
> > Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
> >
> > I more or less agree with the final conclusion below.
> >
> > My main point here is that P2P and C/S need not be enemies. Nor is a
> > total C/S system necessarily evil. What is most evil is  
> *bundling* of
> > services that prevents freedom of choice.
> >
> > I think I would be quite happy with a SP that provides a  
> registrar/proxy
> >
> > and allows me to provide all other features as I see fit - by taking
> > them ala carte from the SP, or subscribing to them from one or more
> > other SPs, or by providing them myself via appliances I own. If that
> > regis X509 certificate while the mapping between services and  
the hardware can be done centralized and allow the business model the  
operator wishes with minimal opex.

Adrian

On Apr 4, 2007, at 7:37 AM, <colin.pons@kpn.com> <colin.pons@kpn.com>  
wrote:

> Henry,
>
> I like your idea of deploying sip peers in edge devices. However,  
> as an employee of a carrier I would like to see how a carrier is  
> able to provide service asurance to be able to provide compliant  
> handling. Many of our customers do not understand how to install  
> these gateways themselves, let alone how to troubleshoot.
>
> This is even more important for enterprises, which often  insist on  
> SLAs which include troubleshoot resolution limits.
>
> -----Original Message-----
> From: "Paul Kyzivat" <pkyzivat@cisco.com>
> To: "Henry Sinnreich" <hsinnrei@adobe.com>
> Cc: "P2PSIP Mailing List" <p2psip@ietf.org>; "Michael Hammer  
> (mhammer)" <mhammer@cisco.com>; "David R Oran" <oran@cisco.com>;  
> "p2prg@ietf.org" <p2prg@ietf.org>; "sipping@ietf.org"  
> <sipping@ietf.org>
> Sent: 3-4-07 01:11
> Subject: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
>
>
>
> Henry Sinnreich wrote:
> > Paul,
> >
> >> I more or less agree with the final conclusion below.
> >
> > This is good starting point to discuss some usage scenarios.
> >
> > Putting on my former hat as an employee for a carrier, I cannot  
> overlook
> > the following:
> >
> > P2P SIP implemented correctly in the residential access box or cable
> > set-top box indeed is a good or better replacement for the entire  
> VoIP
> > network infrastructure (cost, operations, new services, etc).
> > Integrated access devices for the enterprise can probably play a  
> similar
> > role, not to mention existing P2P PBX products (please refer to  
> all the
> > advantages of P2P that need not repeated here).
> >
> > What do people think of these three usage scenarios for P2P SIP:
> > - SIP peer in the DSL access device,
> > - SIP peer in the cable access device,
>
> These seem quite reasonable, assuming that a device connected at this
> point is able to function properly as a peer. (I haven't been  
> following
> what the assumptions are about required network capabilities of  
> peers.)
>
> > - SIP peer in enterprise network integrated access device (IAD).
>
> I think this depends greatly on what expectations / contractual
> guarantees the enterprise has. Its unclear to me what guarantees  
> can be
> made about a P2PSIP network will be able to make, and its unclear what
> kind of infrastructure would be installed by/for someone willing to  
> make
> guarantees.
>
>         Paul
>
> > Note that these examples imply very low churn for the peers and  
> add the
> > data retention resilience of P2P (geographic diversity is native and
> > mobile, etc.). Incidentally, NAT traversal may also not be a  
> problem, or
> > at least an easier problem.
> >
> > What do you all think?
> >
> > I have taken the liberty to copy the P2P SIP list, since the low  
> churn
> > scenarios are of interest for the DHT selection. Or just pick the  
> same
> > DHT for all scenarios anyway? I don't think so.
> >
> > Thanks, Henry
> >
> >
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: Friday, March 30, 2007 6:31 PM
> > To: Eunsoo Shim
> > Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;
> > p2prg@ietf.org; sipping@ietf.org; zhuxian
> > Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario
> >
> > I more or less agree with the final conclusion below.
> >
> > My main point here is that P2P and C/S need not be enemies. Nor is a
> > total C/S system necessarily evil. What is most evil is  
> *bundling* of
> > services that prevents freedom of choice.
> >
> > I think I would be quite happy with a SP that provides a  
> registrar/proxy
> >
> > and allows me to provide all other features as I see fit - by taking
> > them ala carte from the SP, or subscribing to them from one or more
> > other SPs, or by providing them myself via appliances I own. If that
> > registrar/proxy was replaced by a P2P sip community, the  
> differences, if
> >
> > any, would hopefully be more a function of the implementation and  
> the
> > business models of those involved than the architecture.
> >
> > (I gather the general assumption is that a P2P setup will be  
> *free*. But
> >
> > I have a hard time believing that. If most of the usage is by mobile
> > devices that can't be peers, then somebody will have to pay for  
> enough
> > peers to support them. If it isn't free, then how is it better  
> than a
> > well engineered C/S system?)
> >
> > So I think the key thing here is that some features will require  
> getting
> >
> > some help from another node. There ought to be the option to pick a
> > different source for each helper you require, and an ability for  
> it all
> > to play together.
> >
> >       Paul
> >
> > Eunsoo Shim wrote:
> >> Please see my inline comment.
> >>
> >> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com
> >> <mailto:pkyzivat@cisco.com>> wrote:
> >>
> >>
> >>
> >>     Henry Sinnreich wrote:
> >>      > David Oran wrote (with regard to voice mail):
> >>      >
> >>      >> I'm not saying this can't be made to work, only that it  
> isn't
> >>      > immediately >obvious that it has advantages over a classic
> >>     application
> >>      > server >approach.
> >>      >
> >>      > The answer for VM is "it depends":
> >>      >
> >>
> >>
> >> I agree. It really depends. Certainly there are tradeoffs.
> >>
> >>      > There are several commercial P2P IP PBX solutions without  
> any
> >>     server for
> >>      > VM or anything else. No doubt the IT organization  
> appreciates
> > just
> >>      > having to plug in the IP phones and GWY to the PSTN  
> without any
> >>      > configuration ever for VM or any other PBX feature.
> >>
> >>     I don't understand. Are you saying they don't have VM, or that
> > they
> >>     don't have a *server* for VM?
> >>
> >>
> >> I guess they don't have a  *server* for  VM.
> >>
> >>      > For public P2P SIP networks there are two more scenarios  
> where
> > VM can
> >>      > reside (and without ever spending one cent on VM servers  
> + IT
> >>     systems):
> >>      >
> >>      > - In Cable and DSL service provider networks: The  
> residential
> >>     router can
> >>      > act as a voice recorder
> >>
> >>     That is simply an example of the user having an appliance of  
> his
> > own
> >>     that provides VM service.
> >>
> >>      > and P2P can cover the not too frequent cases,
> >>      > where the router is not in operation, so the data is  
> backed up
> > in
> >>     other
> >>      > peer residential gateways (encrypted).
> >>
> >>     I guess I just need to have more info about how this would work
> > before I
> >>     will be convinced it is feasible and trustworthy.
> >>
> >>
> >> Well, 'trustworthy' could be  considered in many angles.
> >> If it is about privacy of the message, a public key based  
> encryption
> >> would provide acceptable privacy.
> >> If it is about reliability of the message delivery, well, a P2P  
> based
> >> asynchronous message delivery (like VM) is most likely less  
> reliable
> >> than a well managed server based system.
> >> However, my experience with Skype's asynchronous message  
> delivery was
> >> not bad. Actually I don't see any significant difference between it
> > and
> >> my cellular service provider's VM service. :-)
> >> Reliability is always a challenge for P2P, for sure. But, I  
> believe it
> >
> >> is feasible to build a P2P system for VM acceptable for many
> > scenarios.
> >>      > - In mobile networks: The VM can reside in quite stable  
> peers
> >>     inside the
> >>      > wireless base station network. The peers in the base station
> > network
> >>      > need no configuration, etc.
> >>
> >>     I don't understand. I guess that could be true if the peers are
> > willing
> >>     to store an arbitrary amount of VM indefinitely for anybody. Is
> > that
> >>     believable?
> >>
> >>
> >> It depends.
> >> In a very nice environment where all the peers are willing trar/proxy was replaced by a P2P sip community, the  
> differences, if
> >
> > any, would hopefully be more a function of the implementation and  
> the
> > business models of those involved than the architecture.
> >
> > (I gather the general assumption is that a P2P setup will be  
> *free*. But
> >
> > I have a hard time believing that. If most of the usage is by mobile
> > devices that can't be peers, then somebody will have to pay for  
> enough
> > peers to support them. If it isn't free, then how is it better  
> than a
> > well engineered C/S system?)
> >
> > So I think the key thing here is that some features will require  
> getting
> >
> > some help from another node. There ought to be the option to pick a
> > different source for each helper you require, and an ability for  
> it all
> > to play together.
> >
> >       Paul
> >
> > Eunsoo Shim wrote:
> >> Please see my inline comment.
> >>
> >> On 3/30/07, *Paul Kyzivat* <pkyzivat@cisco.com
> >> <mailto:pkyzivat@cisco.com>> wrote:
> >>
> >>
> >>
> >>     Henry Sinnreich wrote:
> >>      > David Oran wrote (with regard to voice mail):
> >>      >
> >>      >> I'm not saying this can't be made to work, only that it  
> isn't
> >>      > immediately >obvious that it has advantages over a classic
> >>     application
> >>      > server >approach.
> >>      >
> >>      > The answer for VM is "it depends":
> >>      >
> >>
> >>
> >> I agree. It really depends. Certainly there are tradeoffs.
> >>
> >>      > There are several commercial P2P IP PBX solutions without  
> any
> >>     server for
> >>      > VM or anything else. No doubt the IT organization  
> appreciates
> > just
> >>      > having to plug in the IP phones and GWY to the PSTN  
> without any
> >>      > configuration ever for VM or any other PBX feature.
> >>
> >>     I don't understand. Are you saying they don't have VM, or that
> > they
> >>     don't have a *server* for VM?
> >>
> >>
> >> I guess they don't have a  *server* for  VM.
> >>
> >>      > For public P2P SIP networks there are two more scenarios  
> where
> > VM can
> >>      > reside (and without ever spending one cent on VM servers  
> + IT
> >>     systems):
> >>      >
> >>      > - In Cable and DSL service provider networks: The  
> residential
> >>     router can
> >>      > act as a voice recorder
> >>
> >>     That is simply an example of the user having an appliance of  
> his
> > own
> >>     that provides VM service.
> >>
> >>      > and P2P can cover the not too frequent cases,
> >>      > where the router is not in operation, so the data is  
> backed up
> > in
> >>     other
> >>      > peer residential gateways (encrypted).
> >>
> >>     I guess I just need to have more info about how this would work
> > before I
> >>     will be convinced it is feasible and trustworthy.
> >>
> >>
> >> Well, 'trustworthy' could be  considered in many angles.
> >> If it is about privacy of the message, a public key based  
> encryption
> >> would provide acceptable privacy.
> >> If it is about reliability of the message delivery, well, a P2P  
> based
> >> asynchronous message delivery (like VM) is most likely less  
> reliable
> >> than a well managed server based system.
> >> However, my experience with Skype's asynchronous message  
> delivery was
> >> not bad. Actually I don't see any significant difference between it
> > and
> >> my cellular service provider's VM service. :-)
> >> Reliability is always a challenge for P2P, for sure. But, I  
> believe it
> >
> >> is feasible to build a P2P system for VM acceptable for many
> > scenarios.
> >>      > - In mobile networks: The VM can reside in quite stable  
> peers
> >>     inside the
> >>      > wireless base station network. The peers in the base station
> > network
> >>      > need no configuration, etc.
> >>
> >>     I don't understand. I guess that could be true if the peers are
> > willing
> >>     to store an arbitrary amount of VM indefinitely for anybody. Is
> > that
> >>     believable?
> >>
> >>
> >> It depends.
> >> In a very nice environment where all the peers are willing to
> > cooperate
> >> at their best, the peers will store as much as they can. In a tough
> >> environment, the situation will be different.
> >>
> >>     This seems to translate to a model where it is assumed that  
> those
> > nodes
> >>     that are on most of the time will be willing to provide VM  
> storage
> > for
> >>     those nodes that aren't on most of the time.
> >>
> >>
> >> This is again related to reliability of P2P systems or topics like
> > free
> >> riders and reputation.
> >> A P2P system is a community or society. To be simple, if many of  
> the
> >> members are bad, the community won't work well. If the majority  
> of the
> >
> >> members are good, the community will work well or reasonably.
> >>
> >>      > Add to this the conferencing capability coming from p2p
> > application
> >>      > layer multicast, the SIP e2e control capabilities (for  
> such as
> >>      > auto-attendant, agent workstation, etc.) and one has to  
> wonder
> > why IT
> >>      > networks, public VoIP networks and end users should  
> support the
> > huge
> >>      > cost of hand engineering, testing, monitoring, maintaining
> > server
> >>     based
> >>      > VoIP networks. P2P self configuration is nothing less that
> > automation
> >>      > applied to VoIP, plus the shifting of computing to the
> > endpoints,
> >>     where
> >>      > there is an abundance of unused CPU, storage, bandwidth and
> >>     electricity.
> >>      >
> >>      > Eric Burger also notes IM changes completely the usage  
> for VM
> > and may
> >>      > make unnecessary to place calls on VM in the first place.
> >>
> >>     I find this more promising.
> >>
> >>
> >>
> >>
> >> In overall, are we discussing if P2P systems based VM can work? I
> > think
> >> it can work.  Just it depends on many things.
> >> If it is not super-reliable, should we disregard it? I would say  
> no.
> >>
> >> On the other hand, do we have to abandon client server based VM and
> >> switch to P2P system based VM? It is upto each of us.
> >> Client server based VM systems are already there.
> >> So why don't we work on P2P based VM now?
> >>
> >> Thanks.
> >>
> >> Eunsoo
> >
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip


--Apple-Mail-10--203761590
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Colin,<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>With the right P2P =
software, the devices need no configuration at all, the configuration =
data can be derived from the "hardware id" and a preloaded X509 =
certificate while the mapping between services and the hardware can be =
done centralized and allow the business model the operator wishes with =
minimal opex.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Adrian</DIV><DIV><BR><DIV><DI=
V>On Apr 4, 2007, at 7:37 AM, &lt;<A =
href=3D"mailto:colin.pons@kpn.com">colin.pons@kpn.com</A>&gt; &lt;<A =
href=3D"mailto:colin.pons@kpn.com">colin.pons@kpn.com</A>&gt; =
wrote:</DIV><BR class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><P><FONT size=3D"2">Henry,<BR> <BR> I like your idea of =
deploying sip peers in edge devices. However, as an employee of a =
carrier I would like to see how a carrier is able to provide service =
asurance to be able to provide compliant handling. Many of our customers =
do not understand how to install these gateways themselves, let alone =
how to troubleshoot.<BR> <BR> This is even more important for =
enterprises, which often=A0 insist on SLAs which include troubleshoot =
resolution limits.<BR> <BR> -----Original Message-----<BR> From: "Paul =
Kyzivat" &lt;<A =
href=3D"mailto:pkyzivat@cisco.com">pkyzivat@cisco.com</A>&gt;<BR> To: =
"Henry Sinnreich" &lt;<A =
href=3D"mailto:hsinnrto
> > cooperate
> >> at their best, the peers will store as much as they can. In a tough
> >> environment, the situation will be different.
> >>
> >>     This seems to translate to a model where it is assumed that  
> those
> > nodes
> >>     that are on most of the time will be willing to provide VM  
> storage
> > for
> >>     those nodes that aren't on most of the time.
> >>
> >>
> >> This is again related to reliability of P2P systems or topics like
> > free
> >> riders and reputation.
> >> A P2P system is a community or society. To be simple, if many of  
> the
> >> members are bad, the community won't work well. If the majority  
> of the
> >
> >> members are good, the community will work well or reasonably.
> >>
> >>      > Add to this the conferencing capability coming from p2p
> > application
> >>      > layer multicast, the SIP e2e control capabilities (for  
> such as
> >>      > auto-attendant, agent workstation, etc.) and one has to  
> wonder
> > why IT
> >>      > networks, public VoIP networks and end users should  
> support the
> > huge
> >>      > cost of hand engineering, testing, monitoring, maintaining
> > server
> >>     based
> >>      > VoIP networks. P2P self configuration is nothing less that
> > automation
> >>      > applied to VoIP, plus the shifting of computing to the
> > endpoints,
> >>     where
> >>      > there is an abundance of unused CPU, storage, bandwidth and
> >>     electricity.
> >>      >
> >>      > Eric Burger also notes IM changes completely the usage  
> for VM
> > and may
> >>      > make unnecessary to place calls on VM in the first place.
> >>
> >>     I find this more promising.
> >>
> >>
> >>
> >>
> >> In overall, are we discussing if P2P systems based VM can work? I
> > think
> >> it can work.  Just it depends on many things.
> >> If it is not super-reliable, should we disregard it? I would say  
> no.
> >>
> >> On the other hand, do we have to abandon client server based VM and
> >> switch to P2P system based VM? It is upto each of us.
> >> Client server based VM systems are already there.
> >> So why don't we work on P2P based VM now?
> >>
> >> Thanks.
> >>
> >> Eunsoo
> >
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www1.ietf.org/mailman/listinfo/p2psip


--Apple-Mail-10--203761590
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Colin,<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>With the right P2P =
software, the devices need no configuration at all, the configuration =
data can be derived from the "hardware id" and a preloaded X509 =
certificate while the mapping between services and the hardware can be =
done centralized and allow the business model the operator wishes with =
minimal opex.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Adrian</DIV><DIV><BR><DIV><DI=
V>On Apr 4, 2007, at 7:37 AM, &lt;<A =
href=3D"mailto:colin.pons@kpn.com">colin.pons@kpn.com</A>&gt; &lt;<A =
href=3D"mailto:colin.pons@kpn.com">colin.pons@kpn.com</A>&gt; =
wrote:</DIV><BR class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><P><FONT size=3D"2">Henry,<BR> <BR> I like your idea of =
deploying sip peers in edge devices. However, as an employee of a =
carrier I would like to see how a carrier is able to provide service =
asurance to be able to provide compliant handling. Many of our customers =
do not understand how to install these gateways themselves, let alone =
how to troubleshoot.<BR> <BR> This is even more important for =
enterprises, which often=A0 insist on SLAs which include troubleshoot =
resolution limits.<BR> <BR> -----Original Message-----<BR> From: "Paul =
Kyzivat" &lt;<A =
href=3D"mailto:pkyzivat@cisco.com">pkyzivat@cisco.com</A>&gt;<BR> To: =
"Henry Sinnreich" &lt;<A =
href=3D"mailto:hsinnrei@adobe.com">hsinnrei@adobe.com</A>&gt;<BR> Cc: =
"P2PSIP Mailing List" &lt;<A =
href=3D"mailto:p2psip@ietf.org">p2psip@ietf.org</A>&gt;; "Michael Hammer =
(mhammer)" &lt;<A =
href=3D"mailto:mhammer@cisco.com">mhammer@cisco.com</A>&gt;; "David R =
Oran" &lt;<A href=3D"mailto:oran@cisco.com">oran@cisco.com</A>&gt;; "<A =
href=3D"mailto:p2prg@ietf.org">p2prg@ietf.org</A>" &lt;<A =
href=3D"mailto:p2prg@ietf.org">p2prg@ietf.org</A>&gt;; "<A =
href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A>" &lt;<A =
href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A>&gt;<BR> Sent: =
3-4-07 01:11<BR> Subject: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP =
usage scenario<BR> <BR> <BR> <BR> Henry Sinnreich wrote:<BR> &gt; =
Paul,<BR> &gt;<BR> &gt;&gt; I more or less agree with the final =
conclusion below.<BR> &gt;<BR> &gt; This is good starting point to =
discuss some usage scenarios.<BR> &gt;<BR> &gt; Putting on my former hat =
as an employee for a carrier, I cannot overlook<BR> &gt; the =
following:<BR> &gt;<BR> &gt; P2P SIP implemented correctly in the =
residential access box or cable<BR> &gt; set-top box indeed is a good or =
better replacement for the entire VoIP<BR> &gt; network infrastructure =
(cost, operations, new services, etc).<BR> &gt; Integrated access =
devices for the enterprise can probably play a similar<BR> &gt; role, =
not to mention existing P2P PBX products (please refer to all the<BR> =
&gt; advantages of P2P that need not repeated here).<BR> &gt;<BR> &gt; =
What do people think of these three usage scenarios for P2P SIP:<BR> =
&gt; - SIP peer in the DSL access device,<BR> &gt; - SIP peer in the =
cable access device,<BR> <BR> These seem quite reasonable, assuming that =
a device connected at this<BR> point is able to function properly as a =
peer. (I haven't been following<BR> what the assumptions are about =
required network capabilities of peers.)<BR> <BR> &gt; - SIP peer in =
enterprise network integrated access device (IAD).<BR> <BR> I think this =
depends greatly on what expectations / contractual<BR> guarantees the =
enterprise has. Its unclear to me what guarantees can be<BR> made about =
a P2PSIP network will be able to make, and its unclear what<BR> kind of =
infrastructure would be installed by/for someone willing to make<BR> =
guarantees.<BR> <BR> =A0=A0=A0=A0=A0=A0=A0 Paul<BR> <BR> &gt; Note that =
these examples imply very low churn for the peers and add the<BR> &gt; =
data retention resilience of P2P (geographic diversity is native and<BR> =
&gt; mobile, etc.). Incidentally, NAT traversal may also not be a =
problem, or<BR> &gt; at least an easier problem.<BR> &gt;<BR> &gt; What =
do you all think?<BR> &gt;<BR> &gt; I have taken the liberty to copy the =
P2P SIP list, since the low churn<BR> &gt; scenarios are of interest for =
the DHT selection. Or just pick the same<BR> &gt; DHT for all scenarios =
anyway? I don't think so.<BR> &gt;<BR> &gt; Thanks, Henry<BR> &gt;<BR> =
&gt;<BR> &gt; -----Original Message-----<BR> &gt; From: Paul Kyzivat [<A =
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</A>]<BR> =
&gt; Sent: Friday, March 30, 2007 6:31 PM<BR> &gt; To: Eunsoo Shim<BR> =
&gt; Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;<BR> =
&gt; <A href=3D"mailto:p2prg@ietf.org">p2prg@ietf.org</A>; <A =
href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A>; zhuxian<BR> &gt; =
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario<BR> =
&gt;<BR> &gt; I more or less agree with the final conclusion below.<BR> =
&gt;<BR> &gt; My main point here is that P2P and C/S need not be =
enemies. Nor is a<BR> &gt; total C/S system necessarily evil. What is =
most evil is *bundling* of<BR> &gt; services that prevents freedom of =
choice.<BR> &gt;<BR> &gt; I think I would be quite happy with a SP that =
provides a registrar/proxy<BR> &gt;<BR> &gt; and allows me to provide =
all other features as I see fit - by taking<BR> &gt; them ala carte from =
the SP, or subscribing to them from one or more<BR> &gt; other SPs, or =
by providing them myself via appliances I own. If that<BR> &gt; =
regei@adobe.com">hsinnrei@adobe.com</A>&gt;<BR> Cc: =
"P2PSIP Mailing List" &lt;<A =
href=3D"mailto:p2psip@ietf.org">p2psip@ietf.org</A>&gt;; "Michael Hammer =
(mhammer)" &lt;<A =
href=3D"mailto:mhammer@cisco.com">mhammer@cisco.com</A>&gt;; "David R =
Oran" &lt;<A href=3D"mailto:oran@cisco.com">oran@cisco.com</A>&gt;; "<A =
href=3D"mailto:p2prg@ietf.org">p2prg@ietf.org</A>" &lt;<A =
href=3D"mailto:p2prg@ietf.org">p2prg@ietf.org</A>&gt;; "<A =
href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A>" &lt;<A =
href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A>&gt;<BR> Sent: =
3-4-07 01:11<BR> Subject: [P2PSIP] Re: [P2Prg] RE: [Sipping] Simple SIP =
usage scenario<BR> <BR> <BR> <BR> Henry Sinnreich wrote:<BR> &gt; =
Paul,<BR> &gt;<BR> &gt;&gt; I more or less agree with the final =
conclusion below.<BR> &gt;<BR> &gt; This is good starting point to =
discuss some usage scenarios.<BR> &gt;<BR> &gt; Putting on my former hat =
as an employee for a carrier, I cannot overlook<BR> &gt; the =
following:<BR> &gt;<BR> &gt; P2P SIP implemented correctly in the =
residential access box or cable<BR> &gt; set-top box indeed is a good or =
better replacement for the entire VoIP<BR> &gt; network infrastructure =
(cost, operations, new services, etc).<BR> &gt; Integrated access =
devices for the enterprise can probably play a similar<BR> &gt; role, =
not to mention existing P2P PBX products (please refer to all the<BR> =
&gt; advantages of P2P that need not repeated here).<BR> &gt;<BR> &gt; =
What do people think of these three usage scenarios for P2P SIP:<BR> =
&gt; - SIP peer in the DSL access device,<BR> &gt; - SIP peer in the =
cable access device,<BR> <BR> These seem quite reasonable, assuming that =
a device connected at this<BR> point is able to function properly as a =
peer. (I haven't been following<BR> what the assumptions are about =
required network capabilities of peers.)<BR> <BR> &gt; - SIP peer in =
enterprise network integrated access device (IAD).<BR> <BR> I think this =
depends greatly on what expectations / contractual<BR> guarantees the =
enterprise has. Its unclear to me what guarantees can be<BR> made about =
a P2PSIP network will be able to make, and its unclear what<BR> kind of =
infrastructure would be installed by/for someone willing to make<BR> =
guarantees.<BR> <BR> =A0=A0=A0=A0=A0=A0=A0 Paul<BR> <BR> &gt; Note that =
these examples imply very low churn for the peers and add the<BR> &gt; =
data retention resilience of P2P (geographic diversity is native and<BR> =
&gt; mobile, etc.). Incidentally, NAT traversal may also not be a =
problem, or<BR> &gt; at least an easier problem.<BR> &gt;<BR> &gt; What =
do you all think?<BR> &gt;<BR> &gt; I have taken the liberty to copy the =
P2P SIP list, since the low churn<BR> &gt; scenarios are of interest for =
the DHT selection. Or just pick the same<BR> &gt; DHT for all scenarios =
anyway? I don't think so.<BR> &gt;<BR> &gt; Thanks, Henry<BR> &gt;<BR> =
&gt;<BR> &gt; -----Original Message-----<BR> &gt; From: Paul Kyzivat [<A =
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</A>]<BR> =
&gt; Sent: Friday, March 30, 2007 6:31 PM<BR> &gt; To: Eunsoo Shim<BR> =
&gt; Cc: Henry Sinnreich; Michael Hammer (mhammer); David R Oran;<BR> =
&gt; <A href=3D"mailto:p2prg@ietf.org">p2prg@ietf.org</A>; <A =
href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A>; zhuxian<BR> &gt; =
Subject: Re: [P2Prg] RE: [Sipping] Simple SIP usage scenario<BR> =
&gt;<BR> &gt; I more or less agree with the final conclusion below.<BR> =
&gt;<BR> &gt; My main point here is that P2P and C/S need not be =
enemies. Nor is a<BR> &gt; total C/S system necessarily evil. What is =
most evil is *bundling* of<BR> &gt; services that prevents freedom of =
choice.<BR> &gt;<BR> &gt; I think I would be quite happy with a SP that =
provides a registrar/proxy<BR> &gt;<BR> &gt; and allows me to provide =
all other features as I see fit - by taking<BR> &gt; them ala carte from =
the SP, or subscribing to them from one or more<BR> &gt; other SPs, or =
by providing them myself via appliances I own. If that<BR> &gt; =
registrar/proxy was replaced by a P2P sip community, the differences, =
if<BR> &gt;<BR> &gt; any, would hopefully be more a function of the =
implementation and the<BR> &gt; business models of those involved than =
the architecture.<BR> &gt;<BR> &gt; (I gather the general assumption is =
that a P2P setup will be *free*. But<BR> &gt;<BR> &gt; I have a hard =
time believing that. If most of the usage is by mobile<BR> &gt; devices =
that can't be peers, then somebody will have to pay for enough<BR> &gt; =
peers to support them. If it isn't free, then how is it better than =
a<BR> &gt; well engineered C/S system?)<BR> &gt;<BR> &gt; So I think the =
key thing here is that some features will require getting<BR> &gt;<BR> =
&gt; some help from another node. There ought to be the option to pick =
a<BR> &gt; different source for each helper you require, and an ability =
for it all<BR> &gt; to play together.<BR> &gt;<BR> &gt; =A0=A0=A0=A0=A0 =
Paul<BR> &gt;<BR> &gt; Eunsoo Shim wrote:<BR> &gt;&gt; Please see my =
inline comment.<BR> &gt;&gt;<BR> &gt;&gt; On 3/30/07, *Paul Kyzivat* =
&lt;<A href=3D"mailto:pkyzivat@cisco.com">pkyzivat@cisco.com</A><BR> =
&gt;&gt; &lt;<A =
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</A>&gt;&gt; =
wrote:<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 =
Henry Sinnreich wrote:<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; David Oran wrote =
(with regard to voice mail):<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt;&gt; I'm not saying this can't be made to =
work, only that it isn't<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; immediately =
&gt;obvious that it has advantages over a classic<BR> &gt;&gt;=A0=A0=A0=A0=
 application<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; server &gt;approach.<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; The answer =
for VM is "it depends":<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> =
&gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt; I agree. It really depends. Certainly =
there are tradeoffs.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; There =
are several commercial P2P IP PBX solutions without any<BR> &gt;&gt;=A0=A0=
=A0=A0 server for<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; VM or anything else. =
No doubt the IT organization appreciates<BR> &gt; just<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt; having to plug in the IP phones and GWY to the PSTN without =
any<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; configuration ever for VM or any =
other PBX feature.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 I don't =
understand. Are you saying they don't have VM, or that<BR> &gt; they<BR> =
&gt;&gt;=A0=A0=A0=A0 don't have a *server* for VM?<BR> &gt;&gt;<BR> =
&gt;&gt;<BR> &gt;&gt; I guess they don't have a=A0 *server* for=A0 =
VM.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; For public P2P SIP =
networks there are two more scenarios where<BR> &gt; VM can<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt; reside (and without ever spending one cent =
on VM servers + IT<BR> &gt;&gt;=A0=A0=A0=A0 systems):<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; - In Cable and DSL service =
provider networks: The residential<BR> &gt;&gt;=A0=A0=A0=A0 router =
can<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; act as a voice recorder<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 That is simply an example of the user =
having an appliance of his<BR> &gt; own<BR> &gt;&gt;=A0=A0=A0=A0 that =
provides VM service.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; and =
P2P can cover the not too frequent cases,<BR> &gt;&gt;=A0=A0=A0=A0=A0 =
&gt; where the router is not in operation, so the data is backed up<BR> =
&gt; in<BR> &gt;&gt;=A0=A0=A0=A0 other<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; =
peer residential gateways (encrypted).<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=
 I guess I just need to have more info about how this would work<BR> =
&gt; before I<BR> &gt;&gt;=A0=A0=A0=A0 will be convinced it is feasible =
and trustworthy.<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt; Well, =
'trustworthy' could be=A0 considered in many angles.<BR> &gt;&gt; If it =
is about privacy of the message, a public key based encryption<BR> =
&gt;&gt; would provide acceistrar/proxy was replaced by a P2P sip community, the differences, =
if<BR> &gt;<BR> &gt; any, would hopefully be more a function of the =
implementation and the<BR> &gt; business models of those involved than =
the architecture.<BR> &gt;<BR> &gt; (I gather the general assumption is =
that a P2P setup will be *free*. But<BR> &gt;<BR> &gt; I have a hard =
time believing that. If most of the usage is by mobile<BR> &gt; devices =
that can't be peers, then somebody will have to pay for enough<BR> &gt; =
peers to support them. If it isn't free, then how is it better than =
a<BR> &gt; well engineered C/S system?)<BR> &gt;<BR> &gt; So I think the =
key thing here is that some features will require getting<BR> &gt;<BR> =
&gt; some help from another node. There ought to be the option to pick =
a<BR> &gt; different source for each helper you require, and an ability =
for it all<BR> &gt; to play together.<BR> &gt;<BR> &gt; =A0=A0=A0=A0=A0 =
Paul<BR> &gt;<BR> &gt; Eunsoo Shim wrote:<BR> &gt;&gt; Please see my =
inline comment.<BR> &gt;&gt;<BR> &gt;&gt; On 3/30/07, *Paul Kyzivat* =
&lt;<A href=3D"mailto:pkyzivat@cisco.com">pkyzivat@cisco.com</A><BR> =
&gt;&gt; &lt;<A =
href=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</A>&gt;&gt; =
wrote:<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 =
Henry Sinnreich wrote:<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; David Oran wrote =
(with regard to voice mail):<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt;&gt; I'm not saying this can't be made to =
work, only that it isn't<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; immediately =
&gt;obvious that it has advantages over a classic<BR> &gt;&gt;=A0=A0=A0=A0=
 application<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; server &gt;approach.<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; The answer =
for VM is "it depends":<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> =
&gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt; I agree. It really depends. Certainly =
there are tradeoffs.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; There =
are several commercial P2P IP PBX solutions without any<BR> &gt;&gt;=A0=A0=
=A0=A0 server for<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; VM or anything else. =
No doubt the IT organization appreciates<BR> &gt; just<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt; having to plug in the IP phones and GWY to the PSTN without =
any<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; configuration ever for VM or any =
other PBX feature.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 I don't =
understand. Are you saying they don't have VM, or that<BR> &gt; they<BR> =
&gt;&gt;=A0=A0=A0=A0 don't have a *server* for VM?<BR> &gt;&gt;<BR> =
&gt;&gt;<BR> &gt;&gt; I guess they don't have a=A0 *server* for=A0 =
VM.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; For public P2P SIP =
networks there are two more scenarios where<BR> &gt; VM can<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt; reside (and without ever spending one cent =
on VM servers + IT<BR> &gt;&gt;=A0=A0=A0=A0 systems):<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; - In Cable and DSL service =
provider networks: The residential<BR> &gt;&gt;=A0=A0=A0=A0 router =
can<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; act as a voice recorder<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 That is simply an example of the user =
having an appliance of his<BR> &gt; own<BR> &gt;&gt;=A0=A0=A0=A0 that =
provides VM service.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; and =
P2P can cover the not too frequent cases,<BR> &gt;&gt;=A0=A0=A0=A0=A0 =
&gt; where the router is not in operation, so the data is backed up<BR> =
&gt; in<BR> &gt;&gt;=A0=A0=A0=A0 other<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; =
peer residential gateways (encrypted).<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=
 I guess I just need to have more info about how this would work<BR> =
&gt; before I<BR> &gt;&gt;=A0=A0=A0=A0 will be convinced it is feasible =
and trustworthy.<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt; Well, =
'trustworthy' could be=A0 considered in many angles.<BR> &gt;&gt; If it =
is about privacy of the message, a public key based encryption<BR> =
&gt;&gt; would provide acceptable privacy.<BR> &gt;&gt; If it is about =
reliability of the message delivery, well, a P2P based<BR> &gt;&gt; =
asynchronous message delivery (like VM) is most likely less reliable<BR> =
&gt;&gt; than a well managed server based system.<BR> &gt;&gt; However, =
my experience with Skype's asynchronous message delivery was<BR> =
&gt;&gt; not bad. Actually I don't see any significant difference =
between it<BR> &gt; and<BR> &gt;&gt; my cellular service provider's VM =
service. :-)<BR> &gt;&gt; Reliability is always a challenge for P2P, for =
sure. But, I believe it<BR> &gt;<BR> &gt;&gt; is feasible to build a P2P =
system for VM acceptable for many<BR> &gt; scenarios.<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt; - In mobile networks: The VM can reside in quite stable =
peers<BR> &gt;&gt;=A0=A0=A0=A0 inside the<BR> &gt;&gt;=A0=A0=A0=A0=A0 =
&gt; wireless base station network. The peers in the base station<BR> =
&gt; network<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; need no configuration, =
etc.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 I don't understand. I guess =
that could be true if the peers are<BR> &gt; willing<BR> &gt;&gt;=A0=A0=A0=
=A0 to store an arbitrary amount of VM indefinitely for anybody. Is<BR> =
&gt; that<BR> &gt;&gt;=A0=A0=A0=A0 believable?<BR> &gt;&gt;<BR> =
&gt;&gt;<BR> &gt;&gt; It depends.<BR> &gt;&gt; In a very nice =
environment where all the peers are willing to<BR> &gt; cooperate<BR> =
&gt;&gt; at their best, the peers will store as much as they can. In a =
tough<BR> &gt;&gt; environment, the situation will be different.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 This seems to translate to a model =
where it is assumed that those<BR> &gt; nodes<BR> &gt;&gt;=A0=A0=A0=A0 =
that are on most of the time will be willing to provide VM storage<BR> =
&gt; for<BR> &gt;&gt;=A0=A0=A0=A0 those nodes that aren't on most of the =
time.<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt; This is again related to =
reliability of P2P systems or topics like<BR> &gt; free<BR> &gt;&gt; =
riders and reputation.<BR> &gt;&gt; A P2P system is a community or =
society. To be simple, if many of the<BR> &gt;&gt; members are bad, the =
community won't work well. If the majority of the<BR> &gt;<BR> &gt;&gt; =
members are good, the community will work well or reasonably.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; Add to this the conferencing =
capability coming from p2p<BR> &gt; application<BR> &gt;&gt;=A0=A0=A0=A0=A0=
 &gt; layer multicast, the SIP e2e control capabilities (for such as<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt; auto-attendant, agent workstation, etc.) =
and one has to wonder<BR> &gt; why IT<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; =
networks, public VoIP networks and end users should support the<BR> &gt; =
huge<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; cost of hand engineering, testing, =
monitoring, maintaining<BR> &gt; server<BR> &gt;&gt;=A0=A0=A0=A0 =
based<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; VoIP networks. P2P self =
configuration is nothing less that<BR> &gt; automation<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt; applied to VoIP, plus the shifting of computing to the<BR> =
&gt; endpoints,<BR> &gt;&gt;=A0=A0=A0=A0 where<BR> &gt;&gt;=A0=A0=A0=A0=A0=
 &gt; there is an abundance of unused CPU, storage, bandwidth and<BR> =
&gt;&gt;=A0=A0=A0=A0 electricity.<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt; Eric Burger also notes IM changes =
completely the usage for VM<BR> &gt; and may<BR> &gt;&gt;=A0=A0=A0=A0=A0 =
&gt; make unnecessary to place calls on VM in the first place.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 I find this more promising.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0<BR> &gt;&gt;<BR> =
&gt;&gt;<BR> &gt;&gt; In overall, are we discussing if P2P systems based =
VM can work? I<BR> &gt; think<BR> &gt;&gt; it can work.=A0 Just it =
depends on many things.<BR> &gt;&gt; If it is not super-reliable, should =
we disregard it? I would say no.<BR> &gt;&gt;<BR> &gt;&gt; On the other =
hand, do we have to abandon client server based VM and<BR> &gt;&gt; =
switch to P2P system based VM? It is upto each of us.<BR> &gt;&gt; =
Client server baseptable privacy.<BR> &gt;&gt; If it is about =
reliability of the message delivery, well, a P2P based<BR> &gt;&gt; =
asynchronous message delivery (like VM) is most likely less reliable<BR> =
&gt;&gt; than a well managed server based system.<BR> &gt;&gt; However, =
my experience with Skype's asynchronous message delivery was<BR> =
&gt;&gt; not bad. Actually I don't see any significant difference =
between it<BR> &gt; and<BR> &gt;&gt; my cellular service provider's VM =
service. :-)<BR> &gt;&gt; Reliability is always a challenge for P2P, for =
sure. But, I believe it<BR> &gt;<BR> &gt;&gt; is feasible to build a P2P =
system for VM acceptable for many<BR> &gt; scenarios.<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt; - In mobile networks: The VM can reside in quite stable =
peers<BR> &gt;&gt;=A0=A0=A0=A0 inside the<BR> &gt;&gt;=A0=A0=A0=A0=A0 =
&gt; wireless base station network. The peers in the base station<BR> =
&gt; network<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; need no configuration, =
etc.<BR> &gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 I don't understand. I guess =
that could be true if the peers are<BR> &gt; willing<BR> &gt;&gt;=A0=A0=A0=
=A0 to store an arbitrary amount of VM indefinitely for anybody. Is<BR> =
&gt; that<BR> &gt;&gt;=A0=A0=A0=A0 believable?<BR> &gt;&gt;<BR> =
&gt;&gt;<BR> &gt;&gt; It depends.<BR> &gt;&gt; In a very nice =
environment where all the peers are willing to<BR> &gt; cooperate<BR> =
&gt;&gt; at their best, the peers will store as much as they can. In a =
tough<BR> &gt;&gt; environment, the situation will be different.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 This seems to translate to a model =
where it is assumed that those<BR> &gt; nodes<BR> &gt;&gt;=A0=A0=A0=A0 =
that are on most of the time will be willing to provide VM storage<BR> =
&gt; for<BR> &gt;&gt;=A0=A0=A0=A0 those nodes that aren't on most of the =
time.<BR> &gt;&gt;<BR> &gt;&gt;<BR> &gt;&gt; This is again related to =
reliability of P2P systems or topics like<BR> &gt; free<BR> &gt;&gt; =
riders and reputation.<BR> &gt;&gt; A P2P system is a community or =
society. To be simple, if many of the<BR> &gt;&gt; members are bad, the =
community won't work well. If the majority of the<BR> &gt;<BR> &gt;&gt; =
members are good, the community will work well or reasonably.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; Add to this the conferencing =
capability coming from p2p<BR> &gt; application<BR> &gt;&gt;=A0=A0=A0=A0=A0=
 &gt; layer multicast, the SIP e2e control capabilities (for such as<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt; auto-attendant, agent workstation, etc.) =
and one has to wonder<BR> &gt; why IT<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; =
networks, public VoIP networks and end users should support the<BR> &gt; =
huge<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; cost of hand engineering, testing, =
monitoring, maintaining<BR> &gt; server<BR> &gt;&gt;=A0=A0=A0=A0 =
based<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt; VoIP networks. P2P self =
configuration is nothing less that<BR> &gt; automation<BR> &gt;&gt;=A0=A0=A0=
=A0=A0 &gt; applied to VoIP, plus the shifting of computing to the<BR> =
&gt; endpoints,<BR> &gt;&gt;=A0=A0=A0=A0 where<BR> &gt;&gt;=A0=A0=A0=A0=A0=
 &gt; there is an abundance of unused CPU, storage, bandwidth and<BR> =
&gt;&gt;=A0=A0=A0=A0 electricity.<BR> &gt;&gt;=A0=A0=A0=A0=A0 &gt;<BR> =
&gt;&gt;=A0=A0=A0=A0=A0 &gt; Eric Burger also notes IM changes =
completely the usage for VM<BR> &gt; and may<BR> &gt;&gt;=A0=A0=A0=A0=A0 =
&gt; make unnecessary to place calls on VM in the first place.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0 I find this more promising.<BR> =
&gt;&gt;<BR> &gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0<BR> &gt;&gt;<BR> =
&gt;&gt;<BR> &gt;&gt; In overall, are we discussing if P2P systems based =
VM can work? I<BR> &gt; think<BR> &gt;&gt; it can work.=A0 Just it =
depends on many things.<BR> &gt;&gt; If it is not super-reliable, should =
we disregard it? I would say no.<BR> &gt;&gt;<BR> &gt;&gt; On the other =
hand, do we have to abandon client server based VM and<BR> &gt;&gt; =
switch to P2P system based VM? It is upto each of us.<BR> &gt;&gt; =
Client server based VM systems are already there.<BR> &gt;&gt; So why =
don't we work on P2P based VM now?<BR> &gt;&gt;=A0<BR> &gt;&gt; =
Thanks.<BR> &gt;&gt;<BR> &gt;&gt; Eunsoo<BR> &gt;<BR> <BR> =
_______________________________________________<BR> P2PSIP mailing =
list<BR> <A href=3D"mailto:P2PSIP@ietf.org">P2PSIP@ietf.org</A><BR> <A =
href=3D"https://www1.ietf.org/mailman/listinfo/p2psip">https://www1.ietf.o=
rg/mailman/listinfo/p2psip</A><BR> </FONT> </P><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">P2PSIP mailing list</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"mailto:P2PSIP@ietf.org">P2PSIP@ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/p2psip">https://www1.ietf.o=
rg/mailman/listinfo/p2psip</A></DIV> =
</BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-10--203761590--


--===============0170658415==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0170658415==--






d VM systems are already there.<BR> &gt;&gt; So why =
don't we work on P2P based VM now?<BR> &gt;&gt;=A0<BR> &gt;&gt; =
Thanks.<BR> &gt;&gt;<BR> &gt;&gt; Eunsoo<BR> &gt;<BR> <BR> =
_______________________________________________<BR> P2PSIP mailing =
list<BR> <A href=3D"mailto:P2PSIP@ietf.org">P2PSIP@ietf.org</A><BR> <A =
href=3D"https://www1.ietf.org/mailman/listinfo/p2psip">https://www1.ietf.o=
rg/mailman/listinfo/p2psip</A><BR> </FONT> </P><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">P2PSIP mailing list</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"mailto:P2PSIP@ietf.org">P2PSIP@ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/p2psip">https://www1.ietf.o=
rg/mailman/listinfo/p2psip</A></DIV> =
</BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-10--203761590--


--===============0170658415==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0170658415==--






From sipping-bounces@ietf.org Thu Apr 05 15:10:52 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZXLh-0003zD-Pc; Thu, 05 Apr 2007 15:10:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZXLf-0003z3-Ko
	for sipping@ietf.org; Thu, 05 Apr 2007 15:10:19 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZXLe-0005zs-G5
	for sipping@ietf.org; Thu, 05 Apr 2007 15:10:19 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l35JAEkY036559
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <sipping@ietf.org>; Thu, 5 Apr 2007 14:10:17 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <46154996.50305@nostrum.com>
Date: Thu, 05 Apr 2007 14:10:14 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: SIPPING WG <sipping@ietf.org>
Content-Type: multipart/mixed; boundary="------------050904090609050107010304"
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea2fecb570ff0fcea6acb63c501a031d
Subject: [Sipping] Call Completion: In Defense of Explicit Operations
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.
--------------050904090609050107010304
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Despite what appeared to be early agreement in the working group (and on 
the MIG mailing list) that we wanted to discourage the use of SUBSCRIBE 
and NOTIFY as general purpose RPC mechanisms. This is the primary 
objection that I have raised to draft-poetzl-sipping-call-completion, 
which uses SUBSCRIBE and NOTIFY to manipulate call queue state.

In the spirit of sending text, I described an alternate set of 
mechanisms in draft-roach-sipping-callcomp-bfcp, which performs the same 
task without having implied side effects from the creation of a 
subscription.

I'll further note that the use of SUBSCRIBE to both create a 
subscription and manipulate a call queue falls under the category of 
"one operation with two separate effects." We have a very poor 
institutional memory indeed if we cannot recall why operations of this 
nature are Really Bad Ideas (cf. REFER creating a subscription; REGISTER 
with call processing upload; and BYE with an "Also" header field).

All of this notwithstanding, in Prague, there seemed to be a curious 
indifference to pursuing the path laden with such Really Bad Ideas. I 
suspect that this indifference is a result of the arguments raised so 
far against the mechanism I have proposed, which I have done little to 
refute so far (largely because I believed that the merits of a system 
with explicit operations were self-evident enough that the objections 
would seem trifling in comparison).

As far as I can tell, the objections raised so far have fallen into 
three primary categories:

   1. "The use of BFCP is troubling because, in a decomposed gateway,
      the BFCP goes to the Media Gateway, while the signaling goes to
      the Media Gateway Controller."

      This objection, raised on one of the slides during the SIPPING
      meeting on March 23rd as the official reason TISPAN rejected the
      approach, is based on a simple misconception.

      The BFCP goes wherever the SDP says the BFCP goes. In the case of
      a decomposed gateway, this could be the Media Gateway, the Media
      Gateway Controller, or any other random network-connected server
      that the Media Gateway Controller wants. I agree that it probably
      is most sensible to send it to the Media Gateway Controller, and
      this is trivial to achieve.

   2. "In the case of PSTN interwork, there is no way to guarantee that
      the ISUP (or other) signaling from the PSTN side lands on the same
      gateway that the client has a BFCP connection to."

      This is true, and it is a relatively difficult problem to solve
      (not impossible, though; I proposed several potential solutions in
      San Diego). It is meaningless to raise it in objection to an
      alternate proposal, since it exists in almost precisely the same
      form in draft-poetzl-sipping-call-completion; and any solution
      that can be applied to one solution can be applied to the other.

   3. "We don't want to add another protocol."

      I suspect this argument is the one that is receiving the most
      traction, probably because most of the people involved in the
      discussion are not familiar with BFCP. The protocol itself is very
      straightforward and extremely easy to implement. In fact,
      exclusively for the purpose of answering this email (and
      demonstrating this very point), I threw together a BFCP
      implementation sufficient for implementation of the Call
      Completion service described in draft-roach-sipping-callcomp-bfcp.
      It took me two hours, and compiles down to less than 4 kb of
      object code on an intel processor. It's attached to this message
      to help the participants in the conversation understand just how
      very little is being added to applications by this use of BFCP.

So, is that it? The first two objections are simply red herrings, and 
the third is based on a misconception regarding the level of effort 
required to implement BFCP. Are we really going to down the path of 
doing things incorrectly over what amount to misunderstandings?

/a



P.S. In case anyone wants a more full-featured BFCP stack, I'll point to 
the confiance project on SourceForge, available under the Academic 
Freedom License, which is compatible with commercial development. See 
http://confiance.sourceforge.net/

--------------050904090609050107010304
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
 name="bfcp.h"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="bfcp.h"

#include <sys/types.h>

/* Primitives */
#define BFCP_PRIM_FLOOR_REQUEST           1    /*  P -> S            */
#define BFCP_PRIM_FLOOR_RELEASE           2    /*  P -> S            */
#define BFCP_PRIM_FLOOR_REQUEST_QUERY     3    /*  P -> S ; Ch -> S  */
#define BFCP_PRIM_FLOOR_REQUEST_STATUS    4    /*  P <- S ; Ch <- S  */
#define BFCP_PRIM_USER_QUERY              5    /*  P -> S ; Ch -> S  */
#define BFCP_PRIM_USER_STATUS             6    /*  P <- S ; Ch <- S  */
#define BFCP_PRIM_FLOOR_QUERY             7    /*  P -> S ; Ch -> S  */
#define BFCP_PRIM_FLOOR_STATUS            8    /*  P <- S ; Ch <- S  */
#define BFCP_PRIM_CHAIR_ACTION            9    /*  Ch -> S           */
#define BFCP_PRIM_CHAIR_ACTION_ACK        10   /*  Ch <- S           */
#define BFCP_PRIM_HELLO                   11   /*  P -> S ; Ch -> S  */
#define BFCP_PRIM_HELLO_ACK               12   /*  P <- S ; Ch <- S  */
#define BFCP_PRIM_ERROR                   13   /*  P <- S ; Ch <- S  */
#define BFCP_PRIM_FLOOR_REQUEST_PAUSE     20   /*  P -> S            */
#define BFCP_PRIM_FLOOR_REQUEST_RESUME    21   /*  P -> S            */

/* Attributes */
#define BFCP_ATT_BENEFICIARY_ID                1   /*  Unsigned16     */
#define BFCP_ATT_FLOOR_ID                      2   /*  Unsigned16     */
#define BFCP_ATT_FLOOR_REQUEST_ID              3   /*  Unsigned16     */
#define BFCP_ATT_PRIORITY                      4   /*  OctetString16  */
#define BFCP_ATT_REQUEST_STATUS                5   /*  OctetString16  */
#define BFCP_ATT_ERROR_CODE                    6   /*  OctetString    */
#define BFCP_ATT_ERROR_INFO                    7   /*  OctetString    */
#define BFCP_ATT_PARTICIPANT_PROVIDED_INFO     8   /*  OctetString    */
#define BFCP_ATT_STATUS_INFO                   9   /*  OctetString    */
#define BFCP_ATT_SUPPORTED_ATTRIBUTES         10   /*  OctetString    */
#define BFCP_ATT_SUPPORTED_PRIMITIVES         11   /*  OctetString    */
#define BFCP_ATT_USER_DISPLAY_NAME            12   /*  OctetString    */
#define BFCP_ATT_USER_URI                     13   /*  OctetString    */
#define BFCP_ATT_BENEFICIARY_INFORMATION      14   /*  Grouped        */
#define BFCP_ATT_FLOOR_REQUEST_INFORMATION    15   /*  Grouped        */
#define BFCP_ATT_REQUESTED_BY_INFORMATION     16   /*  Grouped        */
#define BFCP_ATT_FLOOR_REQUEST_STATUS         17   /*  Grouped        */
#define BFCP_ATT_OVERALL_REQUEST_STATUS       18   /*  Grouped        */

/* Request Status Codes */
#define BFCP_STATUS_PENDING    1
#define BFCP_STATUS_ACCEPTED   2
#define BFCP_STATUS_GRANTED    3
#define BFCP_STATUS_DENIED     4
#define BFCP_STATUS_CANCELLED  5
#define BFCP_STATUS_RELEASED   6
#define BFCP_STATUS_REVOKED    7
#define BFCP_STATUS_PAUSED     8

/* Message output functions */

ssize_t bfcp_send_floor_request(int socket,
                                int flags,
                                uint32_t conference_id,
                                uint16_t transaction_id, 
                                uint16_t user_id,
                                uint16_t floor_id);

ssize_t bfcp_send_floor_release(int socket,
                                int flags,
                                uint32_t conference_id,
                                uint16_t transaction_id, 
                                uint16_t user_id,
                                uint16_t floor_request_id);

ssize_t bfcp_send_floor_pause(int socket, 
                              int flags,
                              uint32_t conference_id, 
                              uint16_t transaction_id, 
                              uint16_t user_id, 
                              uint16_t floor_request_id);

ssize_t bfcp_send_floor_resume(int socket, 
                               int flags,
                               uint32_t conference_id, 
                               uint16_t transaction_id, 
                               uint16_t user_id, 
                               uint16_t floor_request_id);

ssize_t bfcp_send_floor_request_status(int socket, 
                                       int flags,
                                       uint32_t conference_id, 
                                       uint16_t transaction_id, 
                                       uint16_t user_id,
                                       uint16_t floor_request_id,
                                       uint16_t floor_id,
                                       uint8_t  request_status,
                                       uint8_t  queue_position);

ssize_t bfcp_send_error(int socket, 
                        int flags,
                        uint32_t conference_id, 
                        uint16_t transaction_id, 
                        uint16_t user_id, 
                        uint8_t  error_code,
                        uint16_t detail_length,
                        uint8_t *details);

/* Message input functions */

void bfcp_init_message_for_reading(void *message, size_t max_size);

ssize_t bfcp_read_message(int socket,
                          int flags,
                          void *message,
                          size_t max_size);

uint8_t  bfcp_get_message_primitive(void *message);

/* Functions to get attributes */

void *bfcp_get_attribute(void *message, uint8_t tag);
void *bfcp_get_subattribute(void *attribute, uint8_t tag);

/* Functions to examine attributes */

uint16_t bfcp_get_attribute_length(void *attribute);
uint8_t *bfcp_get_attribute_value(void *attribute);
uint16_t bfcp_get_attribute_value_16(void *attribute);
uint16_t bfcp_get_grouped_attribute_header_value(void *attribute);

--------------050904090609050107010304
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
 name="bfcp.c"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="bfcp.c"

#include "bfcp.h"

#include <string.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/socket.h>

/*
  Encodes an arbitrary BFCP attribute.

  @param type      The attribute type.
  @param mandatory Flag indicating whether the attribute is mandatory
                   to understand.
  @param length    The length of the parameter value
  @param value     The value of the parameter to encode
  @param encoded   Buffer into which the encoded attribute is to be written

  @returns         The total length of the encoded attribute

  @note The buffer that "encoded" points to must be at least (length + 5)
        bytes long.
*/
int
bfcp_encode_attribute(uint8_t type,
                      int mandatory,
                      uint16_t length,
                      uint8_t *value, 
                      uint8_t *encoded)
{
  encoded[0] = (type << 1) | (mandatory?1:0);
  encoded[1] = length + 2;
  memmove(encoded + 2, value, length);

  /* ensure the attribute is word aligned */
  length += 2;
  while (length % 4)
  {
    encoded[length] = 0;
    length++;
  }
  return length;
}

/*
  Encodes a groupd BFCP attribute.

  @param type         The attribute type.
  @param mandatory    Flag indicating whether the attribute is mandatory
                      to understand.
  @param header_value The 16-bit value encoded in the grouped attribute header
  @param length       The length of the grouped parameters -- must be
                      an even multiple of 4.
  @param value        The (already encoded) grouped parameters
  @param encoded      Buffer into which the encoded attribute is to be written

  @returns            The total length of the encoded attribute

  @note The buffer that "encoded" points to must be at least (length + 4)
        bytes long.
*/
int
bfcp_encode_attribute_grouped(uint8_t type,
                              int mandatory,
                              uint16_t header_value,
                              uint16_t length,
                              uint8_t *value, 
                              uint8_t *encoded)
{
  encoded[0] = (type << 1) | (mandatory?1:0);
  encoded[1] = length + 2;
  encoded[2] = (header_value >> 8) & 0xff;
  encoded[3] = header_value & 0xff;

  memmove(encoded + 4, value, length);
  return length + 4;
}

/**
  Encodes a 16-bit BFCP attribute.

  @param type      The attribute type.
  @param mandatory Flag indicating whether the attribute is mandatory
                   to understand.
  @param value     The value of the parameter to encode
  @param encoded   Buffer into which the encoded attribute is to be written

  @returns         The total length of the encoded attribute

  @note The buffer that "encoded" points to must be at least 4 bytes long.
*/
int
bfcp_encode_attribute_16(uint8_t type,
                         int mandatory,
                         uint16_t value, 
                         uint8_t *encoded)
{
  encoded[0] = (type << 1) | (mandatory?1:0);
  encoded[1] = 4;
  encoded[2] = (value >> 8) & 0xff;
  encoded[3] = value & 0xff;

  return 4;
}

/**
  Encodes a complete BFCP message.

  @param primitive        The type of BFCP message to send
  @param conference_id    The conference ID for the message
  @param transaction_id   The transaction ID for the message
  @param user_id          The user ID for the message
  @param attribute_length The length of the attributes for this message
  @param attributes       The (already encoded) attributes for this message
  @param encoded          The buffer into which the encoded message is to
                          be written

  @returns                The total length of the BFCP message

  @note The buffer that "encoded" points to must be at least
        (attribute_length + 12) bytes long.
*/
int bfcp_encode_message(uint8_t primitive,
                        uint32_t conference_id,
                        uint16_t transaction_id,
                        uint16_t user_id,
                        uint16_t attribute_length,
                        uint8_t *attributes,
                        uint8_t *encoded)
{
  uint16_t word_length = attribute_length / 4;
  encoded[0] = 0x20; /* BFCP Version 1 */
  encoded[1] = primitive;

  encoded[2] = (word_length >> 8) & 0xff;
  encoded[3] = word_length & 0xff;

  encoded[4] = (conference_id >> 24) & 0xff;
  encoded[5] = (conference_id >> 16) & 0xff;
  encoded[6] = (conference_id >> 8) & 0xff;
  encoded[7] = conference_id & 0xff;

  encoded[8] = (transaction_id >> 8) & 0xff;
  encoded[9] = transaction_id & 0xff;

  encoded[10] = (user_id >> 8) & 0xff;
  encoded[11] = user_id & 0xff;

  memmove(encoded + 12, attributes, attribute_length);

  return attribute_length + 12;
}

/**
  Sends a FloorRequest message.

  @param socket          System-level socket to use to send the message.
  @param flags           Flags passed to send(); see send() documentation.
  @param conference_id   Conference ID for message header
  @param transaction_id  Transaction ID for message header
  @param user_id         User ID for message header
  @param floor_id        Floor ID for floor being requested

  @returns the number of uint8_tacters sent, or -1 if an error occurred.
*/
ssize_t bfcp_send_floor_request(int socket, int flags,
                                uint32_t conference_id,
                                uint16_t transaction_id,
                                uint16_t user_id,
                                uint16_t floor_id)
{
  uint8_t attributes[4];
  uint8_t message[16];
  int length;

  length = bfcp_encode_attribute_16(BFCP_ATT_FLOOR_ID, 0, floor_id, attributes);

  length = bfcp_encode_message(BFCP_PRIM_FLOOR_REQUEST, conference_id,
                      transaction_id, user_id, length, attributes, message);

  return send(socket, message, length, flags);
}

/**
  Sends a FloorRequestRelease message.

  @param socket           System-level socket to use to send the message.
  @param flags            Flags passed to send(); see send() documentation.
  @param conference_id    Conference ID for message header
  @param transaction_id   Transaction ID for message header
  @param user_id          User ID for message header
  @param floor_request_id Floor Request ID for floor being released

  @returns the number of uint8_tacters sent, or -1 if an error occurred.
*/
ssize_t bfcp_send_floor_release(int socket, int flags,
                                uint32_t conference_id,
                                uint16_t transaction_id,
                                uint16_t user_id,
                                uint16_t floor_request_id)
{
  uint8_t attributes[4];
  uint8_t message[16];
  int length;

  length = bfcp_encode_attribute_16(BFCP_ATT_FLOOR_REQUEST_ID, 0, 
                                     floor_request_id, attributes);

  length = bfcp_encode_message(BFCP_PRIM_FLOOR_RELEASE, conference_id,
                      transaction_id, user_id, length, attributes, message);

  return send(socket, message, length, flags);
}

/**
  Sends a FloorRequestPause message.

  @param socket           System-level socket to use to send the message.
  @param flags            Flags passed to send(); see send() documentation.
  @param conference_id    Conference ID for message header
  @param transaction_id   Transaction ID for message header
  @param user_id          User ID for message header
  @param floor_request_id Floor Request ID for floor request being paused

  @returns the number of uint8_tacters sent, or -1 if an error occurred.
*/
ssize_t bfcp_send_floor_pause(int socket, int flags,
                              uint32_t conference_id,
                              uint16_t transaction_id,
                              uint16_t user_id,
                              uint16_t floor_request_id)
{
  uint8_t attributes[4];
  uint8_t message[16];
  int length;

  length = bfcp_encode_attribute_16(BFCP_ATT_FLOOR_REQUEST_ID, 0, 
                                     floor_request_id, attributes);

  length = bfcp_encode_message(BFCP_PRIM_FLOOR_REQUEST_PAUSE, conference_id,
                      transaction_id, user_id, length, attributes, message);

  return send(socket, message, length, flags);
}

/**
  Sends a FloorRequestResume message.

  @param socket           System-level socket to use to send the message.
  @param flags            Flags passed to send(); see send() documentation.
  @param conference_id    Conference ID for message header
  @param transaction_id   Transaction ID for message header
  @param user_id          User ID for message header
  @param floor_request_id Floor Request ID for floor request being resumed

  @returns the number of uint8_tacters sent, or -1 if an error occurred.
*/
ssize_t bfcp_send_floor_resume(int socket, int flags,
                               uint32_t conference_id,
                               uint16_t transaction_id,
                               uint16_t user_id,
                               uint16_t floor_request_id)
{
  uint8_t attributes[4];
  uint8_t message[16];
  int length;

  length = bfcp_encode_attribute_16(BFCP_ATT_FLOOR_REQUEST_ID, 0, 
                                     floor_request_id, attributes);

  length = bfcp_encode_message(BFCP_PRIM_FLOOR_REQUEST_RESUME, conference_id,
                      transaction_id, user_id, length, attributes, message);

  return send(socket, message, length, flags);
}

/**
  Sends a FloorRequestStatus message.

  @param socket           System-level socket to use to send the message.
  @param flags            Flags passed to send(); see send() documentation.
  @param conference_id    Conference ID for message header
  @param transaction_id   Transaction ID for message header
  @param user_id          User ID for message header
  @param floor_request_id Floor Request ID for floor request
  @param floor_id         Floor ID for floor request
  @param request_status   Floor request status
  @param queue_position   Position of request in queue

  @returns the number of uint8_tacters sent, or -1 if an error occurred.
*/
ssize_t bfcp_send_floor_request_status(int socket, int flags,
                                       uint32_t conference_id,
                                       uint16_t transaction_id,
                                       uint16_t user_id,
                                       uint16_t floor_request_id,
                                       uint16_t floor_id,
                                       uint8_t  request_status,
                                       uint8_t  queue_position)
{
  /*
  The attributes for this message are nested as follows:

    FLOOR-REQUEST-INFORMATION (floor-request-id)
      FLOOR-REQUEST-STATUS (floor-id)
        REQUEST-STATUS (status, queue position)
  */

  uint8_t request_status_attribute[4];
  uint8_t floor_request_status_attribute[8];
  uint8_t attributes[12];
  uint8_t message[32];
  int length;

  length = bfcp_encode_attribute_16(BFCP_ATT_REQUEST_STATUS, 0, 
                                    (floor_id << 8) | queue_position,
                                    request_status_attribute);

  length = bfcp_encode_attribute_grouped(BFCP_ATT_FLOOR_REQUEST_STATUS, 0,
                                         floor_id, length,
                                         request_status_attribute,
                                         floor_request_status_attribute);

  length = bfcp_encode_attribute_grouped(BFCP_ATT_FLOOR_REQUEST_INFORMATION, 0,
                                         floor_request_id, length,
                                         floor_request_status_attribute,
                                         attributes);

  length = bfcp_encode_message(BFCP_PRIM_FLOOR_REQUEST_RESUME, conference_id,
                      transaction_id, user_id, length, attributes, message);

  return send(socket, message, length, flags);
}

/**
  Sends an Error message.

  @param socket           System-level socket to use to send the message.
  @param flags            Flags passed to send(); see send() documentation.
  @param conference_id    Conference ID for message header
  @param transaction_id   Transaction ID for message header
  @param user_id          User ID for message header
  @param error_code       Error code indicating what happened
  @param detail_length    Length of error details (often 0)
  @param details          error details

  @returns the number of uint8_tacters sent, or -1 if an error occurred.
*/
ssize_t bfcp_send_error(int socket, int flags,
                        uint32_t conference_id,
                        uint16_t transaction_id,
                        uint16_t user_id,
                        uint8_t error_code,
                        uint16_t detail_length,
                        uint8_t *details)
{
  uint8_t attributes[4];
  uint8_t message[16];
  int length;

  uint8_t *attribute_value;
  uint8_t *detail_attributes;
  uint8_t *detail_message;
  ssize_t status;

  /* Special case for less-common "error with details" case */
  if (detail_length != 0)
  {
    attribute_value = malloc(1 + detail_length);
    attribute_value[0] = error_code;
    memmove(attribute_value + 1, details, detail_length);

    detail_attributes = malloc(1 + detail_length + 5);

    length = bfcp_encode_attribute(BFCP_ATT_ERROR_CODE, 0, 
                                   1, attribute_value, detail_attributes);
    free(attribute_value);

    detail_message = malloc(1 + detail_length + 5 + 20);

    length = bfcp_encode_message(BFCP_PRIM_ERROR, conference_id, transaction_id,
                                 user_id, length, 
                                 detail_attributes, detail_message);

    free(detail_attributes);

    status = send(socket, detail_message, length, flags);
    free(detail_message);
    return status;
  }

  length = bfcp_encode_attribute(BFCP_ATT_ERROR_CODE, 0, 
                                 1, &error_code, attributes);

  length = bfcp_encode_message(BFCP_PRIM_ERROR, conference_id, transaction_id,
                               user_id, length, attributes, message);

  return send(socket, message, length, flags);
}

/**
  Initializes a message buffer so it can be read into. Buffers must be
  initialized for every message read into them.

  @param message  Buffer into which message will be read
  @param max_size Size of message buffer
*/
void bfcp_init_message_for_reading(void *message, size_t max_size)
{
  int *bytes_read = (int *)message;
  if (max_size < 12 + sizeof(int))
  {
    return;
  }
  *bytes_read = 0;
}

/**
  Reads a BFCP message from a socket.

  @param socket   System-level socket used to read the message
  @param flags    Flags passed to recv(); see recv() documentation
  @param message  Buffer into which message is to be read
  @param max_size Size of message buffer

  @returns The size of the message actually read

  @retval -1  An error has occured
  @retval 0   There is not enough data to form a complete message.
              The caller is required to call bfcp_read_message
              again WITH THE SAME MESSAGE BUFFER when the descriptor
              is ready for reading.
*/

ssize_t bfcp_read_message(int socket,
                          int flags,
                          void *message,
                          size_t max_size)
{
  int *bytes_read = (int *)message;
  uint8_t *buffer = (uint8_t *) message;
  uint16_t attribute_length;

  buffer += sizeof(int);

  /* We need enough space to read in at least a message header */
  if (max_size < 12 + sizeof(int))
  {
    return -1;
  }

  /* Read in the header */
  if (*bytes_read < 12)
  {
    *bytes_read += recv(socket, buffer, 12 - (*bytes_read), flags);
  }

  if (*bytes_read < 12)
  {
    return 0;
  }

  /* Check for a valid version number */
  if (buffer[1] & 0xE0 != 0x20)
  {
    return -1;
  }

  attribute_length = ((buffer[2]<<8) | buffer[3]) * 4;

  /* Check that there is enough room in the buffer */
  if (attribute_length + 12 + sizeof(int) > max_size)
  {
    return -1;
  }

  /* Read in the remainder of the message */
  *bytes_read += recv(socket, buffer, attribute_length - (*bytes_read) - 12,
                      flags);

  if (*bytes_read < attribute_length + 12)
  {
    return 0;
  }

  return (*bytes_read);
}

/**
  Reads the primitive from a BFCP message

  @param message The BFCP message to get the primive from

  @returns       The primitive of the BFCP message
*/
uint8_t bfcp_get_message_primitive(void *message)
{
  uint8_t *buffer = (uint8_t *) message;
  buffer += sizeof(int);

  return buffer[1];
}


/**
  Private function used to find an attribute in a block of
  attributes.

  @param buffer    Buffer to find the attribute in
  @param size      Size of the buffer
  @param tag       Tag indicating which attribute to find

  @returns pointer to the attribute, NULL if not found.
*/
void *bfcp_private_find_attribute (void *buffer, size_t size, uint8_t tag)
{
  uint8_t *attributes = (uint8_t *)buffer;
  size_t i = 0;
  tag <<= 1;

  while (i < size)
  {
    if (attributes[i] & 0xFE == tag)
    {
      return attributes + i;
    }

    if (i + 1 < size)
    {
      i += attributes[i+1];
    }
    else
    {
      return NULL;
    }
  }

  return NULL;
}

/**
  Finds the specified attribute in a message.

  @param message  The message to find the attribute in
  @param tag      The tag for the attribute to find

  @returns pointer to the attribute, NULL if not found.
*/
void *bfcp_get_attribute(void *message, uint8_t tag)
{
  uint8_t *buffer = (uint8_t *) message;
  unsigned int attribute_length;
  buffer += sizeof(int);
  attribute_length = ((buffer[2]<<8) | buffer[3]) * 4;

  return bfcp_private_find_attribute(buffer + 12, attribute_length, tag);
}

/**
  Finds the specified subattribute in a grouped attribute.

  @param attribute  The grouped attribute to find the subattribute in
  @param tag        The tag for the attribute to find

  @returns pointer to the attribute, NULL if not found.
*/
void *bfcp_get_subattribute(void *attribute, uint8_t tag)
{
  uint8_t *buffer = (uint8_t *) attribute;
  uint8_t attribute_length;

  attribute_length = buffer[1];

  if (attribute_length < 4)
  {
    return NULL;
  }

  return bfcp_private_find_attribute(buffer + 4, attribute_length - 4, tag);
}

/**
  Gets the length of an attribute

  @param attribute  Pointer to the attribute

  @returns Length of the attribute
*/
uint16_t bfcp_get_attribute_length(void *attribute)
{
  uint8_t *buffer = (uint8_t *) attribute;
  uint8_t attribute_length;

  attribute_length = buffer[1];
  if (attribute_length < 2)
  {
    return 0;
  }
  return (attribute_length - 2);
}

/**
  Gets the value of an arbitrary attribute

  @param attribute  Pointer to the attribute

  @returns 16-bit value for the indicated attribute; NULL if attribute
           has no value.
*/

uint8_t *bfcp_get_attribute_value(void* attribute)
{
  uint8_t *buffer = (uint8_t *) attribute;
  if (bfcp_get_attribute_length(attribute) == 0)
  {
    return NULL;
  }
  return buffer + 2;
}

/**
  Gets the value of a 16-bit attribute

  @param attribute  Pointer to the attribute

  @returns 16-bit value for the indicated attribute
*/
uint16_t bfcp_get_attribute_value_16(void* attribute)
{
  uint8_t *buffer = (uint8_t *) attribute;
  if (bfcp_get_attribute_length(attribute) < 2)
  {
    return 0;
  }
  return (buffer[2] << 8) | buffer[3];
}

/**
  Gets the 16-bit value from a grouped attribute header

  @param attribute

  @returns the 16-bit value from the grouped attribute header
*/

uint16_t bfcp_get_grouped_attribute_header_value(void* attribute)
{
  return bfcp_get_attribute_value_16(attribute);
}

--------------050904090609050107010304
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--------------050904090609050107010304--




From sipping-bounces@ietf.org Thu Apr 05 18:20:23 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZaIE-0004CC-VE; Thu, 05 Apr 2007 18:18:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZaID-0004AB-3q
	for sipping@ietf.org; Thu, 05 Apr 2007 18:18:57 -0400
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZaIB-0004Xz-N0
	for sipping@ietf.org; Thu, 05 Apr 2007 18:18:57 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l35MIch05626; Thu, 5 Apr 2007 22:18:38 GMT
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
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Thu, 5 Apr 2007 17:18:20 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0FEA6575@zrc2hxm0.corp.nortel.com>
In-Reply-To: <46154996.50305@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
thread-index: Acd3tjNQA+j4DVEJQt+DFt65y+A5FQAFzr2A
References: <46154996.50305@nostrum.com>
From: "Francois Audet" <audet@nortel.com>
To: "Adam Roach" <adam@nostrum.com>, "SIPPING WG" <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Wouldn't it be possible to do this CCBS/CCNR stuff with a simple
dialog package, and ditch this "queue management" mechanism?

This seems to me to be a classic case of Engineers-gone-wild.

I see this in the poetzl draft:

    Completion of Calls on no Reply (CCNR) provides the caller with the=20
    ability to complete a requested call to a callee without having to=20
    make a new call attempt when the callee becomes not busy after=20
    having initiated an activity.  The CCNR service description is=20
    defined in ETSI EN 301 134 [6].=20

    The call completion services provide the capability to queue=20
    several CCBS/CCNR requests to the same callee on a FIFO basis. It=20
    therefore requires functionalities like notifying changes of queue=20
    states and managing queues. =20

In other words, we are defining this really complex stuff just because
it
used to work like this in some ETSI standard for PSTN.

Is there a better justification than that? What am I missing?

Couldn't we handle some basic level of queueing at the endpoints
themselves,
and use a simple dialog package, and avoid all this stuff that creates
all
the complexity?

This CCBS/CCNR feature is one of the feature that has the most variation

in implementations in PSTN that I know of. To me, picking a really
complicated
variant and replicating it in SIP (either by bastardizing the protocol,
or
by using an entirely different protocol altogether) is not a good idea.
My take is
that there will be such a small uptake in implementation that it will
effectively
useful only in a few confined environments where the it can be mandated
by law.

I'd must rather have a simpler easier to implement version of the
service.

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]=20
> Sent: Thursday, April 05, 2007 12:10
> To: SIPPING WG
> Subject: [Sipping] Call Completion: In Defense of Explicit Operations
>=20
> Despite what appeared to be early agreement in the working=20
> group (and on the MIG mailing list) that we wanted to=20
> discourage the use of SUBSCRIBE and NOTIFY as general purpose=20
> RPC mechanisms. This is the primary objection that I have=20
> raised to draft-poetzl-sipping-call-completion,
> which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
>=20
> In the spirit of sending text, I described an alternate set=20
> of mechanisms in draft-roach-sipping-callcomp-bfcp, which=20
> performs the same task without having implied side effects=20
> from the creation of a subscription.
>=20
> I'll further note that the use of SUBSCRIBE to both create a=20
> subscription and manipulate a call queue falls under the=20
> category of "one operation with two separate effects." We=20
> have a very poor institutional memory indeed if we cannot=20
> recall why operations of this nature are Really Bad Ideas=20
> (cf. REFER creating a subscription; REGISTER with call=20
> processing upload; and BYE with an "Also" header field).
>=20
> All of this notwithstanding, in Prague, there seemed to be a=20
> curious indifference to pursuing the path laden with such=20
> Really Bad Ideas. I suspect that this indifference is a=20
> result of the arguments raised so far against the mechanism I=20
> have proposed, which I have done little to refute so far=20
> (largely because I believed that the merits of a system with=20
> explicit operations were self-evident enough that the=20
> objections would seem trifling in comparison).
>=20
> As far as I can tell, the objections raised so far have=20
> fallen into three primary categories:
>=20
>    1. "The use of BFCP is troubling because, in a decomposed gateway,
>       the BFCP goes to the Media Gateway, while the signaling goes to
>       the Media Gateway Controller."
>=20
>       This objection, raised on one of the slides during the SIPPING
>       meeting on March 23rd as the official reason TISPAN rejected the
>       approach, is based on a simple misconception.
>=20
>       The BFCP goes wherever the SDP says the BFCP goes. In=20
> the case of
>       a decomposed gateway, this could be the Media Gateway, the Media
>       Gateway Controller, or any other random network-connected server
>       that the Media Gateway Controller wants. I agree that=20
> it probably
>       is most sensible to send it to the Media Gateway Controller, and
>       this is trivial to achieve.
>=20
>    2. "In the case of PSTN interwork, there is no way to=20
> guarantee that
>       the ISUP (or other) signaling from the PSTN side lands=20
> on the same
>       gateway that the client has a BFCP connection to."
>=20
>       This is true, and it is a relatively difficult problem to solve
>       (not impossible, though; I proposed several potential=20
> solutions in
>       San Diego). It is meaningless to raise it in objection to an
>       alternate proposal, since it exists in almost precisely the same
>       form in draft-poetzl-sipping-call-completion; and any solution
>       that can be applied to one solution can be applied to the other.
>=20
>    3. "We don't want to add another protocol."
>=20
>       I suspect this argument is the one that is receiving the most
>       traction, probably because most of the people involved in the
>       discussion are not familiar with BFCP. The protocol=20
> itself is very
>       straightforward and extremely easy to implement. In fact,
>       exclusively for the purpose of answering this email (and
>       demonstrating this very point), I threw together a BFCP
>       implementation sufficient for implementation of the Call
>       Completion service described in=20
> draft-roach-sipping-callcomp-bfcp.
>       It took me two hours, and compiles down to less than 4 kb of
>       object code on an intel processor. It's attached to this message
>       to help the participants in the conversation understand just how
>       very little is being added to applications by this use of BFCP.
>=20
> So, is that it? The first two objections are simply red=20
> herrings, and the third is based on a misconception regarding=20
> the level of effort required to implement BFCP. Are we really=20
> going to down the path of doing things incorrectly over what=20
> amount to misunderstandings?
>=20
> /a
>=20
>=20
>=20
> P.S. In case anyone wants a more full-featured BFCP stack,=20
> I'll point to=20
> the confiance project on SourceForge, available under the Academic=20
> Freedom License, which is compatible with commercial development. See=20
> http://confiance.sourceforge.net/
>=20

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 05 19:03:32 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZayY-0006FF-1D; Thu, 05 Apr 2007 19:02:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZayW-0006F5-BW
	for sipping@ietf.org; Thu, 05 Apr 2007 19:02:40 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZayV-0001Ln-2j
	for sipping@ietf.org; Thu, 05 Apr 2007 19:02:40 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 05 Apr 2007 19:02:39 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l35N2cOu032227
	for <sipping@ietf.org>; Thu, 5 Apr 2007 19:02:38 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l35N2clG017806
	for <sipping@ietf.org>; Thu, 5 Apr 2007 23:02:38 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Apr 2007 19:02:38 -0400
Received: from [161.44.174.244] ([161.44.174.244]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Apr 2007 19:02:38 -0400
Message-ID: <4615800F.2030706@cisco.com>
Date: Thu, 05 Apr 2007 19:02:39 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Apr 2007 23:02:38.0460 (UTC)
	FILETIME=[819CEBC0:01C777D6]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2018; t=1175814158;
	x=1176678158; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20draft-poetzl-sipping-call-completion-02
	|Sender:=20 |To:=20sipping=20<sipping@ietf.org>;
	bh=5Lt6ZeNP2bcDYdAwZ2FaNsIRixTTAhV0Her3Pq+do94=;
	b=eShommvRSEnbXEtx+MigXkZPiSGYuXDavsckHW3CJhnatHLL0YCRBCZI7fM+M58l1OuT1j1B
	of+hJmzRd7BTBDsubg/iwgXp740qyV2HBI0TXYI8WmNfdr/bIPbC/rju;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: [Sipping] Re: draft-poetzl-sipping-call-completion-02
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Adam's post just jogged me - I had started to write up some comments on 
the latest version of this draft before the meeting, but I never got 
around to sending them. Here they are (updated based on Adam's comments):

1) I concur with Adam that using SUBSCRIBE to add an entry to the queue, 
and unSUBSCRIBE to remove an entry from the que is wrong. He has given a 
lengthly explanation that I don't need to repeat.

2) It is a little unclear to me whether the UAS that rejects the initial 
call is also the one to host the queue, or whether some other server is 
expected to host the queue. There is mention that no state agents are 
used, and the examples show the same UAS doing both jobs, but I question 
whether this is realistic. In a practical sense I expect it will often 
be a separate server for this, with selective routing by the home proxy 
sending the SUBSCRIBE to the required server. This is practically a 
necessity if there is more than one UA registered for the same AOR, 
because otherwise there is no guarantee that the SUBSCRIBE will get to 
the correct UA.

If there will ever be a separate server managing the queue then using 
Allow-Event in the response to invite to indicate that this capability 
is available is inappropriate.

3) While the implementation does require a queue, it doesn't appear that 
the subscription is really to the status of the queue, since there is no 
visibility to the queue itself. Instead, each subscription seems to be 
to a unique resource - a queue *entry* - that is created by the 
subscription. But there is no name for this resource. This might make it 
impossible to establish a new subscription to the queue entry if the old 
one expires.

4) Section 3 talks about two queues (A-queue and B-queue) but this is 
never mentioned again. If this is intended then the concept should be 
further expanded.

5) The message examples following Figure 1 are not consistent with the 
flow shown in the figure.

	Thanks,
	Paul

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 05 21:47:41 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZdX6-0001Yt-Vt; Thu, 05 Apr 2007 21:46:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZdX5-0001Vp-8w
	for sipping@ietf.org; Thu, 05 Apr 2007 21:46:31 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZdX3-0008G7-Nk
	for sipping@ietf.org; Thu, 05 Apr 2007 21:46:31 -0400
Received: from [192.168.0.102] (ppp-70-244-81-252.dsl.rcsntx.swbell.net
	[70.244.81.252]) (authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l361kRxk053973
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 5 Apr 2007 20:46:28 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4615A5C2.5030607@nostrum.com>
Date: Thu, 05 Apr 2007 20:43:30 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.8 (X11/20061107)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com>
	<1ECE0EB50388174790F9694F77522CCF0FEA6575@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF0FEA6575@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.244.81.252 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Francois:

You are correct that the specific inclusion of a requirement for strict 
call queuing to handle the once-in-a-lifetime situation in which two 
people attempt to perform call completion against the same destination 
is at the root of the complexity. Without this requirement, call 
completion services could be implemented using already-defined mechanisms.

Not only do I agree with your analysis; it's exactly what I was trying 
to convey at the Dallas meeting. If I recall, the pushback took the form 
of, "TISPAN has defined these requirements, and none of them are 
negotiable."

It would be nice if we could get some kind of liaison statement from 
TISPAN confirming that the use of strict queuing is considered a 
sufficiently critical requirement to warrant the relatively ridiculous 
complexity it introduces. (Relative, that is, to the impact on user 
experience.)

/a

Francois Audet wrote:
> Wouldn't it be possible to do this CCBS/CCNR stuff with a simple
> dialog package, and ditch this "queue management" mechanism?
>
> This seems to me to be a classic case of Engineers-gone-wild.
>
> I see this in the poetzl draft:
>
>     Completion of Calls on no Reply (CCNR) provides the caller with the 
>     ability to complete a requested call to a callee without having to 
>     make a new call attempt when the callee becomes not busy after 
>     having initiated an activity.  The CCNR service description is 
>     defined in ETSI EN 301 134 [6]. 
>
>     The call completion services provide the capability to queue 
>     several CCBS/CCNR requests to the same callee on a FIFO basis. It 
>     therefore requires functionalities like notifying changes of queue 
>     states and managing queues.  
>
> In other words, we are defining this really complex stuff just because
> it
> used to work like this in some ETSI standard for PSTN.
>
> Is there a better justification than that? What am I missing?
>
> Couldn't we handle some basic level of queueing at the endpoints
> themselves,
> and use a simple dialog package, and avoid all this stuff that creates
> all
> the complexity?
>
> This CCBS/CCNR feature is one of the feature that has the most variation
>
> in implementations in PSTN that I know of. To me, picking a really
> complicated
> variant and replicating it in SIP (either by bastardizing the protocol,
> or
> by using an entirely different protocol altogether) is not a good idea.
> My take is
> that there will be such a small uptake in implementation that it will
> effectively
> useful only in a few confined environments where the it can be mandated
> by law.
>
> I'd must rather have a simpler easier to implement version of the
> service.
>
>   
>> -----Original Message-----
>> From: Adam Roach [mailto:adam@nostrum.com] 
>> Sent: Thursday, April 05, 2007 12:10
>> To: SIPPING WG
>> Subject: [Sipping] Call Completion: In Defense of Explicit Operations
>>
>> Despite what appeared to be early agreement in the working 
>> group (and on the MIG mailing list) that we wanted to 
>> discourage the use of SUBSCRIBE and NOTIFY as general purpose 
>> RPC mechanisms. This is the primary objection that I have 
>> raised to draft-poetzl-sipping-call-completion,
>> which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
>>
>> In the spirit of sending text, I described an alternate set 
>> of mechanisms in draft-roach-sipping-callcomp-bfcp, which 
>> performs the same task without having implied side effects 
>> from the creation of a subscription.
>>
>> I'll further note that the use of SUBSCRIBE to both create a 
>> subscription and manipulate a call queue falls under the 
>> category of "one operation with two separate effects." We 
>> have a very poor institutional memory indeed if we cannot 
>> recall why operations of this nature are Really Bad Ideas 
>> (cf. REFER creating a subscription; REGISTER with call 
>> processing upload; and BYE with an "Also" header field).
>>
>> All of this notwithstanding, in Prague, there seemed to be a 
>> curious indifference to pursuing the path laden with such 
>> Really Bad Ideas. I suspect that this indifference is a 
>> result of the arguments raised so far against the mechanism I 
>> have proposed, which I have done little to refute so far 
>> (largely because I believed that the merits of a system with 
>> explicit operations were self-evident enough that the 
>> objections would seem trifling in comparison).
>>
>> As far as I can tell, the objections raised so far have 
>> fallen into three primary categories:
>>
>>    1. "The use of BFCP is troubling because, in a decomposed gateway,
>>       the BFCP goes to the Media Gateway, while the signaling goes to
>>       the Media Gateway Controller."
>>
>>       This objection, raised on one of the slides during the SIPPING
>>       meeting on March 23rd as the official reason TISPAN rejected the
>>       approach, is based on a simple misconception.
>>
>>       The BFCP goes wherever the SDP says the BFCP goes. In 
>> the case of
>>       a decomposed gateway, this could be the Media Gateway, the Media
>>       Gateway Controller, or any other random network-connected server
>>       that the Media Gateway Controller wants. I agree that 
>> it probably
>>       is most sensible to send it to the Media Gateway Controller, and
>>       this is trivial to achieve.
>>
>>    2. "In the case of PSTN interwork, there is no way to 
>> guarantee that
>>       the ISUP (or other) signaling from the PSTN side lands 
>> on the same
>>       gateway that the client has a BFCP connection to."
>>
>>       This is true, and it is a relatively difficult problem to solve
>>       (not impossible, though; I proposed several potential 
>> solutions in
>>       San Diego). It is meaningless to raise it in objection to an
>>       alternate proposal, since it exists in almost precisely the same
>>       form in draft-poetzl-sipping-call-completion; and any solution
>>       that can be applied to one solution can be applied to the other.
>>
>>    3. "We don't want to add another protocol."
>>
>>       I suspect this argument is the one that is receiving the most
>>       traction, probably because most of the people involved in the
>>       discussion are not familiar with BFCP. The protocol 
>> itself is very
>>       straightforward and extremely easy to implement. In fact,
>>       exclusively for the purpose of answering this email (and
>>       demonstrating this very point), I threw together a BFCP
>>       implementation sufficient for implementation of the Call
>>       Completion service described in 
>> draft-roach-sipping-callcomp-bfcp.
>>       It took me two hours, and compiles down to less than 4 kb of
>>       object code on an intel processor. It's attached to this message
>>       to help the participants in the conversation understand just how
>>       very little is being added to applications by this use of BFCP.
>>
>> So, is that it? The first two objections are simply red 
>> herrings, and the third is based on a misconception regarding 
>> the level of effort required to implement BFCP. Are we really 
>> going to down the path of doing things incorrectly over what 
>> amount to misunderstandings?
>>
>> /a
>>
>>
>>
>> P.S. In case anyone wants a more full-featured BFCP stack, 
>> I'll point to 
>> the confiance project on SourceForge, available under the Academic 
>> Freedom License, which is compatible with commercial development. See 
>> http://confiance.sourceforge.net/
>>
>>     


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 05 22:13:08 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZdwd-0008H0-Tl; Thu, 05 Apr 2007 22:12:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZdwc-0008Gn-6y
	for sipping@ietf.org; Thu, 05 Apr 2007 22:12:54 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZdwa-0005Oq-TF
	for sipping@ietf.org; Thu, 05 Apr 2007 22:12:54 -0400
Received: from [192.168.0.102] (ppp-70-244-81-252.dsl.rcsntx.swbell.net
	[70.244.81.252]) (authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l362Cobq055176
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 5 Apr 2007 21:12:51 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4615ABF3.70604@nostrum.com>
Date: Thu, 05 Apr 2007 21:09:55 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.8 (X11/20061107)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping] Re: draft-poetzl-sipping-call-completion-02
References: <4615800F.2030706@cisco.com>
In-Reply-To: <4615800F.2030706@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.244.81.252 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Paul Kyzivat wrote:
> 2) It is a little unclear to me whether the UAS that rejects the 
> initial call is also the one to host the queue, or whether some other 
> server is expected to host the queue. There is mention that no state 
> agents are used, and the examples show the same UAS doing both jobs, 
> but I question whether this is realistic. In a practical sense I 
> expect it will often be a separate server for this, with selective 
> routing by the home proxy sending the SUBSCRIBE to the required 
> server. This is practically a necessity if there is more than one UA 
> registered for the same AOR, because otherwise there is no guarantee 
> that the SUBSCRIBE will get to the correct UA.
>
> If there will ever be a separate server managing the queue then using 
> Allow-Event in the response to invite to indicate that this capability 
> is available is inappropriate.

This was another objection I raised to the mechanism in draft-poetzl -- 
it is designed and described almost exclusively in the context of PSTN 
interoperation. Its application to pure SIP networks is difficult to 
deduce from the current document, and it suffers from a number of 
shortcomings (such as the one you describe above). *If* we decide to 
take the mechanism down the path proposed in draft-poetzl, it will need 
a fairly radical re-write so that it describes the mechanism in terms of 
a pure SIP network (with discussion of how it applies to PSTN interwork) 
instead of being written as if it were primarily a PSTN interworking 
document.

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 06 05:24:13 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZkeJ-0006Je-Ba; Fri, 06 Apr 2007 05:22:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZkeH-0006CZ-3H
	for sipping@ietf.org; Fri, 06 Apr 2007 05:22:25 -0400
Received: from an-out-0708.google.com ([209.85.132.243])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HZkeF-0006Aj-NM
	for sipping@ietf.org; Fri, 06 Apr 2007 05:22:25 -0400
Received: by an-out-0708.google.com with SMTP id d30so1019492and
	for <sipping@ietf.org>; Fri, 06 Apr 2007 02:22:23 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=fs73sbZifP6Tcks9Fmrg6YonnvdZHOpvUXOfm+CXwVUu3FgE+R6CYsOmkU1hutQpP7yA/bpGj7PXr+QUfyphdE6lHPZecQmuKwXpgvm8QA3obN8ER/9bn4OKXPi1BlAwxdOU5DhH89kmYY7JzVu/XrlsCJCZ1iQP2NPeSlHJONg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=ge+aXPF4zrsUoZ2v3+Ab0qRPz6yYModybivHYDAxVwSn8PgHZNgIZm4phYuS0WPvk4hLE7InhLr4taaFPQtAAFctBRq/VgZk037JEoVehz0cqnTGQX61mqwdVszVFUIqiSEjQUAMcx5ceLSOXtp22CPu/hLC3gjBAI9VOiTZaCw=
Received: by 10.100.178.7 with SMTP id a7mr1957301anf.1175851343114;
	Fri, 06 Apr 2007 02:22:23 -0700 (PDT)
Received: by 10.100.189.14 with HTTP; Fri, 6 Apr 2007 02:22:23 -0700 (PDT)
Message-ID: <458913680704060222p6a4aeab3n85cbdb998999f5a6@mail.gmail.com>
Date: Fri, 6 Apr 2007 11:22:23 +0200
From: "Xavier Marjou" <xavier.marjou@orange-ftgroup.com>
To: alan@sipstation.com, sipping@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Google-Sender-Auth: f2418e22223fb4ca
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc: 
Subject: [Sipping] Comments on draft-ietf-sipping-cc-framework-07
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Section 2.3
- Among the advantages of the peer-to-peer approach (ie: REFER msg)
over the 3pcc approach (ie: RFC3725), I would somehow underline that
the peer-to-peer approach allows the creation of a single SIP dialog
directly between the peers. On the contrary, with the 3pcc approach,
there are 2 SIP dialogs connected together by a SIP intermediary, the
controller. This intermediary thus affects, and may even limit, the
communication between the 2 peers. For example, if the controller does
not support a given SIP extension (eg: UPDATE message) whereas the 2
peers support it, the peers won't be able to use this SIP extension.
Similarly, if the controller supports a given SIP extension and only
one of the 2 peers support it, the SIP extension will be used in one
dialog but not in the other dialog, which means that the controller
will need to implement a complex behavior to mitigate this. (For this
later case, the use of OPTIONS before 3pcc could help, but this is
something I haven't seen being implemented.)

Section 2.7.1
- Elaborate on "calendar reminder": is it "just" a type of network
announcement service?

Section 2.7.2
- Replace
  advantage of the fact that the standard SIP URI has a user part.
  Most services may be thought of as user automatons that participate
  in SIP sessions.  It naturally follows that the user address, or the
  left-hand-side of the URI, should be utilized as a service indicator.
with:
  advantage of the fact that the standard the left-hand-side of the
  SIP URI is a user part. Most services may be thought of as user
  automatons that participate in SIP sessions.  It naturally follows
  that the user part should be utilized as a service indicator.

Section 2.7.2
- Replace
 "represents people. However, the URI can also represent services,"
with
 "represents a person. However, the URI can also represent a service,"

Section 3.1
- Rename "3.1. Early Dialog Actions" into "3.1. Remote Call Control
Actions on Early Dialog"

Section 3.2
- Rename "3.2. Single Dialog Actions" into "3.2. Remote Call Control
Actions on Single Dialog"

Section 3.2.
- What does CRM stand for?

Section 3.2.2.
- Replace "be conceptually be" with "conceptually be"

Section 3.2.2.
- It is currently written that "There is no way to distinguish between
the desire to go on or off hold." Reading sip-remote-cc-05, I
understand that placing on-hold or off-old is possible, but that it is
not possible to do it at a "per" media level.

Section 3.3.1
- In case user-A is a "secretary", and user-C is a "boss", it may be
that the SIP URI of user-C must not be revealed to any user-B. This is
something inherent to 3pcc. It should therefore be mentionned that
"the 3pcc helps if privacy is needed for C".

Section 3.3.3
- It's not easy to read the following text:
  "A
  could send the following requests: REFER B Refer-To: conference-URI
  INVITE conference-URI BYE B To add a party to a conference: REFER C
  Refer-To: conference-URI or REFER conference-URI Refer-To: C Using
  the 3pcc approach to transition to centrally mixed, the controller
  would send: INVITE mixer leg 1 (w/SDP of A) INVITE mixer leg 2 (w/SDP
  of B) INVITE C (late SDP) reINVITE A (w/SDP of mixer leg 1) reINVITE
  B (w/SDP of mixer leg 2) INVITE mixer leg3 (w/SDP of C) To add a
  party to a SIP conference: INVITE C (late SDP) INVITE conference-URI
  (w/SDP of C) Features enabled: - standard conference feature - call
  recording - answering-machine style screening (screening)"
Maybe rewrite it with
  "A could send the following requests:
  =B0 REFER B Refer-To: conference-URI
  =B0 INVITE conference-URI
  =B0 BYE B
 To add a party to a conference:
  =B0 REFER C Refer-To: conference-URI
  =B0 or REFER conference-URI Refer-To: C
  Using the 3pcc approach to transition to centrally mixed, the
controller would send:
  =B0 INVITE mixer leg 1 (w/SDP of A)
  =B0 INVITE mixer leg 2 (w/SDP of B)
  =B0 INVITE C (late SDP)
  =B0 reINVITE A (w/SDP of mixer leg 1)
  =B0 reINVITE B (w/SDP of mixer leg 2)
  =B0  INVITE mixer leg3 (w/SDP of C)
  To add a party to a SIP conference:
  =B0 INVITE C (late SDP)
  =B0 INVITE conference-URI (w/SDP of C)
Features enabled: - standard conference feature - call recording -
answering-machine style screening (screening)"

Section 3.3.4
- Replace "5.3) For" by "5.3).  For"
- There is no Section 5.3

Section 6
- I suggest to list example features by alphabetical order in section
6, 6.1, 6.1.1. ... otherwise it's difficulte to look for a given
feature among the different sections.

Section 6.1
- Update references for [service-examples], [conf-models],
[cc-transfer], [cc-framework], [sip-answer-mode] with [6], .... [28]

Section 6.1.4
- Replace "dialog state" with "dialog event package" ? If yes, add a
reference to [11], RFC 4235

Section 6.1.13
- Replace "Voice Portal Takes" with "Voice Portal takes"

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 06 13:12:07 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZrxl-00084d-37; Fri, 06 Apr 2007 13:11:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZrxj-00084Y-IN
	for sipping@ietf.org; Fri, 06 Apr 2007 13:10:59 -0400
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZrxi-00033v-Aa
	for sipping@ietf.org; Fri, 06 Apr 2007 13:10:59 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l36HAlu01129; Fri, 6 Apr 2007 17:10:48 GMT
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
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Fri, 6 Apr 2007 12:10:41 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0FEA6B61@zrc2hxm0.corp.nortel.com>
In-Reply-To: <4615A5C2.5030607@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
thread-index: Acd37WqX74KC8Z7WSkC83gdBoPaooAAdrwPw
References: <46154996.50305@nostrum.com>
	<1ECE0EB50388174790F9694F77522CCF0FEA6575@zrc2hxm0.corp.nortel.com>
	<4615A5C2.5030607@nostrum.com>
From: "Francois Audet" <audet@nortel.com>
To: "Adam Roach" <adam@nostrum.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Thanks, it's good to see I'm not the only one puzzled by this.

I think what would be useful is a document that explains how to do
CCBS/CCNR using standard existing mechanisms (i.e., a subscription to
the dialog package), combine with recommendations on how to handle
basic queuing at the endpoint.=20

That is probably very simple, and something that is easily implementable
by
clients.=20

Then we can think of "is it worth it to ADD queue management to this by
either=20
mucking around with SUBSCRIBE (like the poetzl draft) or by using BFCP".

TISPAN will have to think about the tradeoffs:
- I really believe that the vast majority of implementations will not
  do this queue management stuff. It will be confined to places where
  it is somehow mandatory (if there are such places).
- The reality of the market is that the simple version will then be
  widely supported, and the complicated one will not.

So again, I'd advocate doing the simple basic stuff as the baseline, and
then
decice if it needs to be expanded with optional enhancements specific
for TISPAN.



> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]=20
> Sent: Thursday, April 05, 2007 18:44
> To: Audet, Francois (SC100:3055)
> Cc: SIPPING WG
> Subject: Re: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
> Francois:
>=20
> You are correct that the specific inclusion of a requirement=20
> for strict call queuing to handle the once-in-a-lifetime=20
> situation in which two people attempt to perform call=20
> completion against the same destination is at the root of the=20
> complexity. Without this requirement, call completion=20
> services could be implemented using already-defined mechanisms.
>=20
> Not only do I agree with your analysis; it's exactly what I=20
> was trying to convey at the Dallas meeting. If I recall, the=20
> pushback took the form of, "TISPAN has defined these=20
> requirements, and none of them are negotiable."
>=20
> It would be nice if we could get some kind of liaison=20
> statement from TISPAN confirming that the use of strict=20
> queuing is considered a sufficiently critical requirement to=20
> warrant the relatively ridiculous complexity it introduces.=20
> (Relative, that is, to the impact on user
> experience.)
>=20
> /a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 06 15:39:25 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZuFw-0003VX-61; Fri, 06 Apr 2007 15:37:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZuFu-0003SM-SZ
	for sipping@ietf.org; Fri, 06 Apr 2007 15:37:54 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZuFs-0001l2-8o
	for sipping@ietf.org; Fri, 06 Apr 2007 15:37:54 -0400
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l36JbjoF016052
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 6 Apr 2007 12:37:46 -0700
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l36JbjAU018582;
	Fri, 6 Apr 2007 12:37:45 -0700 (PDT)
Received: from NAEX07.na.qualcomm.com ([129.46.133.195]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Apr 2007 12:37:45 -0700
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: Fri, 6 Apr 2007 12:37:43 -0700
Message-ID: <90D469E18343DE47961207F6851040B30188A91C@NAEX07.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-sipping-ipv6-torture-tests-01.txt
Thread-Index: Acd4gwvcenSXGALXSBa4xkH9OPRe0A==
From: "Mahendran, AC" <mahendra@qualcomm.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 06 Apr 2007 19:37:45.0319 (UTC)
	FILETIME=[0CBE3770:01C77883]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: ac@qualcomm.com, mary.barnes@nortel.com
Subject: [Sipping] Comments on draft-ietf-sipping-ipv6-torture-tests-01.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


Hi Vijay,

Here are my comments on draft-ietf-sipping-ipv6-torture-tests-01.txt.=20

1) In section 3, text: "This document does not, however, address these
issues.  Instead, a companion document [ID.sip-trans] provides more
guidance on these."

It would good to complete the sentence by appending "issues" to the end
of the sentence.

2) In 4.3, text: "Consider the REGISTER request below.  The sender of
the request intended to specify a port number (5070) to contact a
server, but inadvertently, put the port number inside the closing "]" of
the IPv6 reference. "

s/put/puts (or inserts)

3) Sections 4.3/4.4 mention about the (un)/ambiguous ports in
Request-URI. This, however, applies to other headers (e.g., Via header
[in sent-by production rule], and the Contact header) as well. If
possible, can we mention that in the description?

4) General comment (applies to the entire doc): Intent of "Message
Details" is not clear. It would be good include a small description on
the intent of "Message Details" field. It is descriptive in some
examples (e.g., "ipv6-good", "ipv6-bad" etc), whereas, it does not mean
much in others (e.g., "param1", "param2" etc).

Note: I see it being used in RFC 4475, but there is no description in
that document too.

5) In Section 4.4, text: "Message Details: port-umabiguous"=20

s/umabiguous/unambiguous

Also, the spelling needs to be fixed in the title of the section as
well.

6) In section 4.6,=20

Text:

     o=3Dassistant 971731711378798081 0 IN IP6 2001:db8::20
     s=3DLive video feed for today's meeting
     c=3DIN IP6 2001:db8::1

Is there are reason why you made the IPv6 address in the "o=3D" line
different from the "c=3D" line? If not, it'd be better to make them the
same.

7) In section 4.5,=20

Text:

     OPTIONS sip:[2001:db8::10] SIP/2.0
     To: sip:user@example.com
     From: sip:user@example.com;tag=3D81x2
     <allOneLine>
     Via: SIP/2.0/UDP [2001:db8::9:1];received=3D2001:db8::9:255;
     branch=3Dz9hG4bKas3
     </allOneLine>
     Call-ID: SSG95523997077@hlau_4100
     Max-Forwards: 70
     Contact: "Caller" <sip:caller@[2001:db8::1]>
     CSeq: 921 OPTIONS
     Content-Length: 0

The IPv6 address in the "Contact" header is different from the address
in the "Via" header e.g., "9" is missing from the address in the Contact
header. If this intentional, it would be good to note it in the
description.

The same comment applies to the examples in sections 4.6 and 4.8.

8) In section 4.7,

Text:

     BYE sip:user@host.example.com SIP/2.0
     Via: SIP/2.0/UDP [2001:db8::9:1]:6050;branch=3Dz9hG4bKas3-111
     Via: SIP/2.0/UDP 192.0.2.1;branch=3Dz9hG4bKjhja8781hjuaij65144
     <allOneLine>
     Via: SIP/2.0/TCP [2001:db8::9:255];branch=3Dz9hG4bK451jj;
     received=3D192.0.2.200
     </allOneLine>
     Call-ID: 997077@lau_4100
     Max-Forwards: 70
     CSeq: 89187 BYE
     To: sip:user@example.net;tag=3D9817--94
     From: sip:user@example.com;tag=3D81x2
     Content-Length: 0


The "To" header contains the domain "example.net" but the Request-URI
contains "example.com". While this is possible, I think it'd be better
to make both these domains the same (e.g., example.net).


Thanks,
AC




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sat Apr 07 14:30:07 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaFf0-0005Ia-4G; Sat, 07 Apr 2007 14:29:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaFey-0005IO-Qr
	for sipping@ietf.org; Sat, 07 Apr 2007 14:29:12 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaFeu-00028w-NT
	for sipping@ietf.org; Sat, 07 Apr 2007 14:29:12 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JG500C8N4O3Q8@siemenscomms.co.uk> for sipping@ietf.org;
	Sat, 07 Apr 2007 19:28:51 +0100 (BST)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VC0JTL>; Sat, 07 Apr 2007 19:28:55 +0100
Content-return: allowed
Date: Sat, 07 Apr 2007 19:28:47 +0100
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
To: Francois Audet <audet@nortel.com>, Adam Roach <adam@nostrum.com>,
	SIPPING WG <sipping@ietf.org>
Message-id: <50B1CBA96870A34799A506B2313F26670B7D7823@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97c820c82c68af374c4e382a80dc5017
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I know this feature is quite popular in the PSTN residential market in
various countries in Europe, particularly Germany and also the UK to some
extent. Customers seem prepared to spend a few euro cents for the
convenience it gives in a presence-less environment. So I think the
operators of those networks want to make sure they don't lose this when they
evolve to SIP. Given that in SIP you could do things differently and
hopefully better, PSTN interworking would appear to be the essential driver
behind the TISPAN requirements, but presumably an important driver in the
eyes of the carriers concerned. For the enterprise market I just don't see
it as important. We used to have it on PBXs right back in the 70s and 80s
and it was popular then, but voicemail has pretty well taken over in the
enterprise. I hope this sheds some light.

John

> -----Original Message-----
> From: Francois Audet [mailto:audet@nortel.com] 
> Sent: 05 April 2007 23:18
> To: Adam Roach; SIPPING WG
> Subject: RE: [Sipping] Call Completion: In Defense of 
> Explicit Operations
> 
> Wouldn't it be possible to do this CCBS/CCNR stuff with a simple
> dialog package, and ditch this "queue management" mechanism?
> 
> This seems to me to be a classic case of Engineers-gone-wild.
> 
> I see this in the poetzl draft:
> 
>     Completion of Calls on no Reply (CCNR) provides the 
> caller with the 
>     ability to complete a requested call to a callee without 
> having to 
>     make a new call attempt when the callee becomes not busy after 
>     having initiated an activity.  The CCNR service description is 
>     defined in ETSI EN 301 134 [6]. 
> 
>     The call completion services provide the capability to queue 
>     several CCBS/CCNR requests to the same callee on a FIFO basis. It 
>     therefore requires functionalities like notifying changes 
> of queue 
>     states and managing queues.  
> 
> In other words, we are defining this really complex stuff just because
> it
> used to work like this in some ETSI standard for PSTN.
> 
> Is there a better justification than that? What am I missing?
> 
> Couldn't we handle some basic level of queueing at the endpoints
> themselves,
> and use a simple dialog package, and avoid all this stuff that creates
> all
> the complexity?
> 
> This CCBS/CCNR feature is one of the feature that has the 
> most variation
> 
> in implementations in PSTN that I know of. To me, picking a really
> complicated
> variant and replicating it in SIP (either by bastardizing the 
> protocol,
> or
> by using an entirely different protocol altogether) is not a 
> good idea.
> My take is
> that there will be such a small uptake in implementation that it will
> effectively
> useful only in a few confined environments where the it can 
> be mandated
> by law.
> 
> I'd must rather have a simpler easier to implement version of the
> service.
> 
> > -----Original Message-----
> > From: Adam Roach [mailto:adam@nostrum.com] 
> > Sent: Thursday, April 05, 2007 12:10
> > To: SIPPING WG
> > Subject: [Sipping] Call Completion: In Defense of Explicit 
> Operations
> > 
> > Despite what appeared to be early agreement in the working 
> > group (and on the MIG mailing list) that we wanted to 
> > discourage the use of SUBSCRIBE and NOTIFY as general purpose 
> > RPC mechanisms. This is the primary objection that I have 
> > raised to draft-poetzl-sipping-call-completion,
> > which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
> > 
> > In the spirit of sending text, I described an alternate set 
> > of mechanisms in draft-roach-sipping-callcomp-bfcp, which 
> > performs the same task without having implied side effects 
> > from the creation of a subscription.
> > 
> > I'll further note that the use of SUBSCRIBE to both create a 
> > subscription and manipulate a call queue falls under the 
> > category of "one operation with two separate effects." We 
> > have a very poor institutional memory indeed if we cannot 
> > recall why operations of this nature are Really Bad Ideas 
> > (cf. REFER creating a subscription; REGISTER with call 
> > processing upload; and BYE with an "Also" header field).
> > 
> > All of this notwithstanding, in Prague, there seemed to be a 
> > curious indifference to pursuing the path laden with such 
> > Really Bad Ideas. I suspect that this indifference is a 
> > result of the arguments raised so far against the mechanism I 
> > have proposed, which I have done little to refute so far 
> > (largely because I believed that the merits of a system with 
> > explicit operations were self-evident enough that the 
> > objections would seem trifling in comparison).
> > 
> > As far as I can tell, the objections raised so far have 
> > fallen into three primary categories:
> > 
> >    1. "The use of BFCP is troubling because, in a 
> decomposed gateway,
> >       the BFCP goes to the Media Gateway, while the 
> signaling goes to
> >       the Media Gateway Controller."
> > 
> >       This objection, raised on one of the slides during the SIPPING
> >       meeting on March 23rd as the official reason TISPAN 
> rejected the
> >       approach, is based on a simple misconception.
> > 
> >       The BFCP goes wherever the SDP says the BFCP goes. In 
> > the case of
> >       a decomposed gateway, this could be the Media 
> Gateway, the Media
> >       Gateway Controller, or any other random 
> network-connected server
> >       that the Media Gateway Controller wants. I agree that 
> > it probably
> >       is most sensible to send it to the Media Gateway 
> Controller, and
> >       this is trivial to achieve.
> > 
> >    2. "In the case of PSTN interwork, there is no way to 
> > guarantee that
> >       the ISUP (or other) signaling from the PSTN side lands 
> > on the same
> >       gateway that the client has a BFCP connection to."
> > 
> >       This is true, and it is a relatively difficult 
> problem to solve
> >       (not impossible, though; I proposed several potential 
> > solutions in
> >       San Diego). It is meaningless to raise it in objection to an
> >       alternate proposal, since it exists in almost 
> precisely the same
> >       form in draft-poetzl-sipping-call-completion; and any solution
> >       that can be applied to one solution can be applied to 
> the other.
> > 
> >    3. "We don't want to add another protocol."
> > 
> >       I suspect this argument is the one that is receiving the most
> >       traction, probably because most of the people involved in the
> >       discussion are not familiar with BFCP. The protocol 
> > itself is very
> >       straightforward and extremely easy to implement. In fact,
> >       exclusively for the purpose of answering this email (and
> >       demonstrating this very point), I threw together a BFCP
> >       implementation sufficient for implementation of the Call
> >       Completion service described in 
> > draft-roach-sipping-callcomp-bfcp.
> >       It took me two hours, and compiles down to less than 4 kb of
> >       object code on an intel processor. It's attached to 
> this message
> >       to help the participants in the conversation 
> understand just how
> >       very little is being added to applications by this 
> use of BFCP.
> > 
> > So, is that it? The first two objections are simply red 
> > herrings, and the third is based on a misconception regarding 
> > the level of effort required to implement BFCP. Are we really 
> > going to down the path of doing things incorrectly over what 
> > amount to misunderstandings?
> > 
> > /a
> > 
> > 
> > 
> > P.S. In case anyone wants a more full-featured BFCP stack, 
> > I'll point to 
> > the confiance project on SourceForge, available under the Academic 
> > Freedom License, which is compatible with commercial 
> development. See 
> > http://confiance.sourceforge.net/
> > 
> 
> _______________________________________________
> Sipping mailing list  https://www1.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
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sat Apr 07 14:39:13 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaFoZ-0002US-Fw; Sat, 07 Apr 2007 14:39:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaFoY-0002Rv-DG
	for sipping@ietf.org; Sat, 07 Apr 2007 14:39:06 -0400
Received: from jalapeno.cc.columbia.edu ([128.59.29.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaFoV-0005Mq-U3
	for sipping@ietf.org; Sat, 07 Apr 2007 14:39:06 -0400
Received: from [192.168.0.41] (pool-70-21-193-163.nwrk.east.verizon.net
	[70.21.193.163]) (user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id
	l37IcvJf013813
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sat, 7 Apr 2007 14:38:58 -0400 (EDT)
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B7D7823@ntht201e.siemenscomms.co.uk>
References: <50B1CBA96870A34799A506B2313F26670B7D7823@ntht201e.siemenscomms.co.uk>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <260AFF3D-EA06-4F12-95DD-5E81DE4D2B11@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Sat, 7 Apr 2007 14:38:59 -0400
To: "Elwell, John" <john.elwell@siemens.com>
X-Mailer: Apple Mail (2.752.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bcd240e64c427d3d3617cfc704e7fd7f
Cc: SIPPING WG <sipping@ietf.org>, Francois Audet <audet@nortel.com>,
	Adam Roach <adam@nostrum.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

This seems like a special case of a call log handler, which might be  
useful beyond CCNR. Why not simply subscribe to a call log event  
package (to be defined) and let the UA manage the call backs? That  
way, you can do call backs for calls placed from other devices or  
even previously completed calls, just like people routinely dial from  
their "recent calls" list.

I don't know if Francois was referring to the same thing as "a simple  
dialog package".

Henning

On Apr 7, 2007, at 2:28 PM, Elwell, John wrote:

> I know this feature is quite popular in the PSTN residential market in
> various countries in Europe, particularly Germany and also the UK  
> to some
> extent. Customers seem prepared to spend a few euro cents for the
> convenience it gives in a presence-less environment. So I think the
> operators of those networks want to make sure they don't lose this  
> when they
> evolve to SIP. Given that in SIP you could do things differently and
> hopefully better, PSTN interworking would appear to be the  
> essential driver
> behind the TISPAN requirements, but presumably an important driver  
> in the
> eyes of the carriers concerned. For the enterprise market I just  
> don't see
> it as important. We used to have it on PBXs right back in the 70s  
> and 80s
> and it was popular then, but voicemail has pretty well taken over  
> in the
> enterprise. I hope this sheds some light.
>
> John
>
>> -----Original Message-----
>> From: Francois Audet [mailto:audet@nortel.com]
>> Sent: 05 April 2007 23:18
>> To: Adam Roach; SIPPING WG
>> Subject: RE: [Sipping] Call Completion: In Defense of
>> Explicit Operations
>>
>> Wouldn't it be possible to do this CCBS/CCNR stuff with a simple
>> dialog package, and ditch this "queue management" mechanism?
>>
>> This seems to me to be a cFrom sipping-bounces@ietf.org Sat Apr 07 14:39:13 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaFoZ-0002US-Fw; Sat, 07 Apr 2007 14:39:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaFoY-0002Rv-DG
	for sipping@ietf.org; Sat, 07 Apr 2007 14:39:06 -0400
Received: from jalapeno.cc.columbia.edu ([128.59.29.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaFoV-0005Mq-U3
	for sipping@ietf.org; Sat, 07 Apr 2007 14:39:06 -0400
Received: from [192.168.0.41] (pool-70-21-193-163.nwrk.east.verizon.net
	[70.21.193.163]) (user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id
	l37IcvJf013813
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sat, 7 Apr 2007 14:38:58 -0400 (EDT)
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B7D7823@ntht201e.siemenscomms.co.uk>
References: <50B1CBA96870A34799A506B2313F26670B7D7823@ntht201e.siemenscomms.co.uk>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <260AFF3D-EA06-4F12-95DD-5E81DE4D2B11@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Sat, 7 Apr 2007 14:38:59 -0400
To: "Elwell, John" <john.elwell@siemens.com>
X-Mailer: Apple Mail (2.752.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bcd240e64c427d3d3617cfc704e7fd7f
Cc: SIPPING WG <sipping@ietf.org>, Francois Audet <audet@nortel.com>,
	Adam Roach <adam@nostrum.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

This seems like a special case of a call log handler, which might be  
useful beyond CCNR. Why not simply subscribe to a call log event  
package (to be defined) and let the UA manage the call backs? That  
way, you can do call backs for calls placed from other devices or  
even previously completed calls, just like people routinely dial from  
their "recent calls" list.

I don't know if Francois was referring to the same thing as "a simple  
dialog package".

Henning

On Apr 7, 2007, at 2:28 PM, Elwell, John wrote:

> I know this feature is quite popular in the PSTN residential market in
> various countries in Europe, particularly Germany and also the UK  
> to some
> extent. Customers seem prepared to spend a few euro cents for the
> convenience it gives in a presence-less environment. So I think the
> operators of those networks want to make sure they don't lose this  
> when they
> evolve to SIP. Given that in SIP you could do things differently and
> hopefully better, PSTN interworking would appear to be the  
> essential driver
> behind the TISPAN requirements, but presumably an important driver  
> in the
> eyes of the carriers concerned. For the enterprise market I just  
> don't see
> it as important. We used to have it on PBXs right back in the 70s  
> and 80s
> and it was popular then, but voicemail has pretty well taken over  
> in the
> enterprise. I hope this sheds some light.
>
> John
>
>> -----Original Message-----
>> From: Francois Audet [mailto:audet@nortel.com]
>> Sent: 05 April 2007 23:18
>> To: Adam Roach; SIPPING WG
>> Subject: RE: [Sipping] Call Completion: In Defense of
>> Explicit Operations
>>
>> Wouldn't it be possible to do this CCBS/CCNR stuff with a simple
>> dialog package, and ditch this "queue management" mechanism?
>>
>> This seems to me to be a classic case of Engineers-gone-wild.
>>
>> I see this in the poetzl draft:
>>
>>     Completion of Calls on no Reply (CCNR) provides the
>> caller with the
>>     ability to complete a requested call to a callee without
>> having to
>>     make a new call attempt when the callee becomes not busy after
>>     having initiated an activity.  The CCNR service description is
>>     defined in ETSI EN 301 134 [6].
>>
>>     The call completion services provide the capability to queue
>>     several CCBS/CCNR requests to the same callee on a FIFO basis. It
>>     therefore requires functionalities like notifying changes
>> of queue
>>     states and managing queues.
>>
>> In other words, we are defining this really complex stuff just  
>> because
>> it
>> used to work like this in some ETSI standard for PSTN.
>>
>> Is there a better justification than that? What am I missing?
>>
>> Couldn't we handle some basic level of queueing at the endpoints
>> themselves,
>> and use a simple dialog package, and avoid all this stuff that  
>> creates
>> all
>> the complexity?
>>
>> This CCBS/CCNR feature is one of the feature that has the
>> most variation
>>
>> in implementations in PSTN that I know of. To me, picking a really
>> complicated
>> variant and replicating it in SIP (either by bastardizing the
>> protocol,
>> or
>> by using an entirely different protocol altogether) is not a
>> good idea.
>> My take is
>> that there will be such a small uptake in implementation that it will
>> effectively
>> useful only in a few confined environments where the it can
>> be mandated
>> by law.
>>
>> I'd must rather have a simpler easier to implement version of the
>> service.
>>
>>> -----Original Message-----
>>> From: Adam Roach [mailto:adam@nostrum.com]
>>> Sent: Thursday, April 05, 2007 12:10
>>> To: SIPPING WG
>>> Subject: [Sipping] Call Completion: In Defense of Explicit
>> Operations
>>>
>>> Despite what appeared to be early agreement in the working
>>> group (and on the MIG mailing list) that we wanted to
>>> discourage the use of SUBSCRIBE and NOTIFY as general purpose
>>> RPC mechanisms. This is the primary objection that I have
>>> raised to draft-poetzl-sipping-call-completion,
>>> which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
>>>
>>> In the spirit of sending text, I described an alternate set
>>> of mechanisms in draft-roach-sipping-callcomp-bfcp, which
>>> performs the same task without having implied side effects
>>> from the creation of a subscription.
>>>
>>> I'll further note that the use of SUBSCRIBE to both create a
>>> subscription and manipulate a call queue falls under the
>>> category of "one operation with two separate effects." We
>>> have a very poor institutional memory indeed if we cannot
>>> recall why operations of this nature are Really Bad Ideas
>>> (cf. REFER creating a subscription; REGISTER with call
>>> processing upload; and BYE with an "Also" header field).
>>>
>>> All of this notwithstanding, in Prague, there seemed to be a
>>> curious indifference to pursuing the path laden with such
>>> Really Bad Ideas. I suspect that this indifference is a
>>> result of the arguments raised so far against the mechanism I
>>> have proposed, which I have done little to refute so far
>>> (largely because I believed that the merits of a system with
>>> explicit operations were self-evident enough that the
>>> objections would seem trifling in comparison).
>>>
>>> As far as I can tell, the objections raised so far have
>>> fallen into three primary categories:
>>>
>>>    1. "The use of BFCP is troubling because, in a
>> decomposed gateway,
>>>       the BFCP goes to the Media Gateway, while the
>> signaling goes to
>>>       the Media Gateway Controller."
>>>
>>>       This objection, raised on one of the slides during the SIPPING
>>>       meeting on March 23rd as the official reason TISPAN
>> rejected the
>>>       approach, is based on a simple misconception.
>>>
>>>       The BFCP goes wherever the SDP says the BFCP goes. In
>>> the case of
>>>       a decomposed gateway, this could be the Media
>> Gatewlassic case of Engineers-gone-wild.
>>
>> I see this in the poetzl draft:
>>
>>     Completion of Calls on no Reply (CCNR) provides the
>> caller with the
>>     ability to complete a requested call to a callee without
>> having to
>>     make a new call attempt when the callee becomes not busy after
>>     having initiated an activity.  The CCNR service description is
>>     defined in ETSI EN 301 134 [6].
>>
>>     The call completion services provide the capability to queue
>>     several CCBS/CCNR requests to the same callee on a FIFO basis. It
>>     therefore requires functionalities like notifying changes
>> of queue
>>     states and managing queues.
>>
>> In other words, we are defining this really complex stuff just  
>> because
>> it
>> used to work like this in some ETSI standard for PSTN.
>>
>> Is there a better justification than that? What am I missing?
>>
>> Couldn't we handle some basic level of queueing at the endpoints
>> themselves,
>> and use a simple dialog package, and avoid all this stuff that  
>> creates
>> all
>> the complexity?
>>
>> This CCBS/CCNR feature is one of the feature that has the
>> most variation
>>
>> in implementations in PSTN that I know of. To me, picking a really
>> complicated
>> variant and replicating it in SIP (either by bastardizing the
>> protocol,
>> or
>> by using an entirely different protocol altogether) is not a
>> good idea.
>> My take is
>> that there will be such a small uptake in implementation that it will
>> effectively
>> useful only in a few confined environments where the it can
>> be mandated
>> by law.
>>
>> I'd must rather have a simpler easier to implement version of the
>> service.
>>
>>> -----Original Message-----
>>> From: Adam Roach [mailto:adam@nostrum.com]
>>> Sent: Thursday, April 05, 2007 12:10
>>> To: SIPPING WG
>>> Subject: [Sipping] Call Completion: In Defense of Explicit
>> Operations
>>>
>>> Despite what appeared to be early agreement in the working
>>> group (and on the MIG mailing list) that we wanted to
>>> discourage the use of SUBSCRIBE and NOTIFY as general purpose
>>> RPC mechanisms. This is the primary objection that I have
>>> raised to draft-poetzl-sipping-call-completion,
>>> which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
>>>
>>> In the spirit of sending text, I described an alternate set
>>> of mechanisms in draft-roach-sipping-callcomp-bfcp, which
>>> performs the same task without having implied side effects
>>> from the creation of a subscription.
>>>
>>> I'll further note that the use of SUBSCRIBE to both create a
>>> subscription and manipulate a call queue falls under the
>>> category of "one operation with two separate effects." We
>>> have a very poor institutional memory indeed if we cannot
>>> recall why operations of this nature are Really Bad Ideas
>>> (cf. REFER creating a subscription; REGISTER with call
>>> processing upload; and BYE with an "Also" header field).
>>>
>>> All of this notwithstanding, in Prague, there seemed to be a
>>> curious indifference to pursuing the path laden with such
>>> Really Bad Ideas. I suspect that this indifference is a
>>> result of the arguments raised so far against the mechanism I
>>> have proposed, which I have done little to refute so far
>>> (largely because I believed that the merits of a system with
>>> explicit operations were self-evident enough that the
>>> objections would seem trifling in comparison).
>>>
>>> As far as I can tell, the objections raised so far have
>>> fallen into three primary categories:
>>>
>>>    1. "The use of BFCP is troubling because, in a
>> decomposed gateway,
>>>       the BFCP goes to the Media Gateway, while the
>> signaling goes to
>>>       the Media Gateway Controller."
>>>
>>>       This objection, raised on one of the slides during the SIPPING
>>>       meeting on March 23rd as the official reason TISPAN
>> rejected the
>>>       approach, is based on a simple misconception.
>>>
>>>       The BFCP goes wherever the SDP says the BFCP goes. In
>>> the case of
>>>       a decomposed gateway, this could be the Media
>> Gateway, the Media
>>>       Gateway Controller, or any other random
>> network-connected server
>>>       that the Media Gateway Controller wants. I agree that
>>> it probably
>>>       is most sensible to send it to the Media Gateway
>> Controller, and
>>>       this is trivial to achieve.
>>>
>>>    2. "In the case of PSTN interwork, there is no way to
>>> guarantee that
>>>       the ISUP (or other) signaling from the PSTN side lands
>>> on the same
>>>       gateway that the client has a BFCP connection to."
>>>
>>>       This is true, and it is a relatively difficult
>> problem to solve
>>>       (not impossible, though; I proposed several potential
>>> solutions in
>>>       San Diego). It is meaningless to raise it in objection to an
>>>       alternate proposal, since it exists in almost
>> precisely the same
>>>       form in draft-poetzl-sipping-call-completion; and any solution
>>>       that can be applied to one solution can be applied to
>> the other.
>>>
>>>    3. "We don't want to add another protocol."
>>>
>>>       I suspect this argument is the one that is receiving the most
>>>       traction, probably because most of the people involved in the
>>>       discussion are not familiar with BFCP. The protocol
>>> itself is very
>>>       straightforward and extremely easy to implement. In fact,
>>>       exclusively for the purpose of answering this email (and
>>>       demonstrating this very point), I threw together a BFCP
>>>       implementation sufficient for implementation of the Call
>>>       Completion service described in
>>> draft-roach-sipping-callcomp-bfcp.
>>>       It took me two hours, and compiles down to less than 4 kb of
>>>       object code on an intel processor. It's attached to
>> this message
>>>       to help the participants in the conversation
>> understand just how
>>>       very little is being added to applications by this
>> use of BFCP.
>>>
>>> So, is that it? The first two objections are simply red
>>> herrings, and the third is based on a misconception regarding
>>> the level of effort required to implement BFCP. Are we really
>>> going to down the path of doing things incorrectly over what
>>> amount to misunderstandings?
>>>
>>> /a
>>>
>>>
>>>
>>> P.S. In case anyone wants a more full-featured BFCP stack,
>>> I'll point to
>>> the confiance project on SourceForge, available under the Academic
>>> Freedom License, which is compatible with commercial
>> development. See
>>> http://confiance.sourceforge.net/
>>>
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.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
>>
>
> _______________________________________________
> Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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

From sipping-bounces@ietf.org Sat Apr 07 14:39:13 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaFoU-0002PV-KT; Sat, 07 Apr 2007 14:39:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaFoT-0002PL-VX
	for sipping@ietf.org; Sat, 07 Apr 2007 14:39:01 -0400
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaFoS-0005Mj-E8
	for sipping@ietf.org; Sat, 07 Apr 2007 14:39:01 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71]ay, the Media
>>>       Gateway Controller, or any other random
>> network-connected server
>>>       that the Media Gateway Controller wants. I agree that
>>> it probably
>>>       is most sensible to send it to the Media Gateway
>> Controller, and
>>>       this is trivial to achieve.
>>>
>>>    2. "In the case of PSTN interwork, there is no way to
>>> guarantee that
>>>       the ISUP (or other) signaling from the PSTN side lands
>>> on the same
>>>       gateway that the client has a BFCP connection to."
>>>
>>>       This is true, and it is a relatively difficult
>> problem to solve
>>>       (not impossible, though; I proposed several potential
>>> solutions in
>>>       San Diego). It is meaningless to raise it in objection to an
>>>       alternate proposal, since it exists in almost
>> precisely the same
>>>       form in draft-poetzl-sipping-call-completion; and any solution
>>>       that can be applied to one solution can be applied to
>> the other.
>>>
>>>    3. "We don't want to add another protocol."
>>>
>>>       I suspect this argument is the one that is receiving the most
>>>       traction, probably because most of the people involved in the
>>>       discussion are not familiar with BFCP. The protocol
>>> itself is very
>>>       straightforward and extremely easy to implement. In fact,
>>>       exclusively for the purpose of answering this email (and
>>>       demonstrating this very point), I threw together a BFCP
>>>       implementation sufficient for implementation of the Call
>>>       Completion service described in
>>> draft-roach-sipping-callcomp-bfcp.
>>>       It took me two hours, and compiles down to less than 4 kb of
>>>       object code on an intel processor. It's attached to
>> this message
>>>       to help the participants in the conversation
>> understand just how
>>>       very little is being added to applications by this
>> use of BFCP.
>>>
>>> So, is that it? The first two objections are simply red
>>> herrings, and the third is based on a misconception regarding
>>> the level of effort required to implement BFCP. Are we really
>>> going to down the path of doing things incorrectly over what
>>> amount to misunderstandings?
>>>
>>> /a
>>>
>>>
>>>
>>> P.S. In case anyone wants a more full-featured BFCP stack,
>>> I'll point to
>>> the confiance project on SourceForge, available under the Academic
>>> Freedom License, which is compatible with commercial
>> development. See
>>> http://confiance.sourceforge.net/
>>>
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.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
>>
>
> _______________________________________________
> Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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

From sipping-bounces@ietf.org Sat Apr 07 14:39:13 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaFoU-0002PV-KT; Sat, 07 Apr 2007 14:39:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaFoT-0002PL-VX
	for sipping@ietf.org; Sat, 07 Apr 2007 14:39:01 -0400
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaFoS-0005Mj-E8
	for sipping@ietf.org; Sat, 07 Apr 2007 14:39:01 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l37IcnF18853; Sat, 7 Apr 2007 18:38:49 GMT
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
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Sat, 7 Apr 2007 13:38:47 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0FEFCEB3@zrc2hxm0.corp.nortel.com>
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B7D7823@ntht201e.siemenscomms.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
thread-index: Acd5Qp2oxmURjIgMRduEGnBlXL00IgAAOLJQ
References: <50B1CBA96870A34799A506B2313F26670B7D7823@ntht201e.siemenscomms.co.uk>
From: "Francois Audet" <audet@nortel.com>
To: "Elwell, John" <john.elwell@siemens.com>, "Adam Roach" <adam@nostrum.com>, 
	"SIPPING WG" <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi John,

Do you think that this implementing this feature in
the way Adam and I were alluding to, i.e., where queuing
is handled by the clients but without some of the more
complex "queue management" feature would be acceptable
in those countries?

That would allow us to have a very simple implemenation
without compromising the semantics of SUBSCRIBE or=20
using a separate protocol (BFCP).


> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens.com]=20
> Sent: Saturday, April 07, 2007 11:29
> To: Audet, Francois (SC100:3055); Adam Roach; SIPPING WG
> Subject: RE: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
> I know this feature is quite popular in the PSTN residential=20
> market in various countries in Europe, particularly Germany=20
> and also the UK to some extent. Customers seem prepared to=20
> spend a few euro cents for the convenience it gives in a=20
> presence-less environment. So I think the operators of those=20
> networks want to make sure they don't lose this when they=20
> evolve to SIP. Given that in SIP you could do things=20
> differently and hopefully better, PSTN interworking would=20
> appear to be the essential driver behind the TISPAN=20
> requirements, but presumably an important driver in the eyes=20
> of the carriers concerned. For the enterprise market I just=20
> don't see it as important. We used to have it on PBXs right=20
> back in the 70s and 80s and it was popular then, but=20
> voicemail has pretty well taken over in the enterprise. I=20
> hope this sheds some light.
>=20
> John
>=20
> > -----Original Message-----
> > From: Francois Audet [mailto:audet@nortel.com]
> > Sent: 05 April 2007 23:18
> > To: Adam Roach; SIPPING WG
> > Subject: RE: [Sipping] Call Completion: In Defense of Explicit=20
> > Operations
> >=20
> > Wouldn't it be possible to do this CCBS/CCNR stuff with a simple=20
> > dialog package, and ditch this "queue management" mechanism?
> >=20
> > This seems to me to be a classic case of Engineers-gone-wild.
> >=20
> > I see this in the poetzl draft:
> >=20
> >     Completion of Calls on no Reply (CCNR) provides the caller with=20
> > the
> >     ability to complete a requested call to a callee=20
> without having to
> >     make a new call attempt when the callee becomes not busy after=20
> >     having initiated an activity.  The CCNR service description is=20
> >     defined in ETSI EN 301 134 [6].=20
> >=20
> >     The call completion services provide the capabil)
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l37IcnF18853; Sat, 7 Apr 2007 18:38:49 GMT
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
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Sat, 7 Apr 2007 13:38:47 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0FEFCEB3@zrc2hxm0.corp.nortel.com>
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B7D7823@ntht201e.siemenscomms.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
thread-index: Acd5Qp2oxmURjIgMRduEGnBlXL00IgAAOLJQ
References: <50B1CBA96870A34799A506B2313F26670B7D7823@ntht201e.siemenscomms.co.uk>
From: "Francois Audet" <audet@nortel.com>
To: "Elwell, John" <john.elwell@siemens.com>, "Adam Roach" <adam@nostrum.com>, 
	"SIPPING WG" <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi John,

Do you think that this implementing this feature in
the way Adam and I were alluding to, i.e., where queuing
is handled by the clients but without some of the more
complex "queue management" feature would be acceptable
in those countries?

That would allow us to have a very simple implemenation
without compromising the semantics of SUBSCRIBE or=20
using a separate protocol (BFCP).


> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens.com]=20
> Sent: Saturday, April 07, 2007 11:29
> To: Audet, Francois (SC100:3055); Adam Roach; SIPPING WG
> Subject: RE: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
> I know this feature is quite popular in the PSTN residential=20
> market in various countries in Europe, particularly Germany=20
> and also the UK to some extent. Customers seem prepared to=20
> spend a few euro cents for the convenience it gives in a=20
> presence-less environment. So I think the operators of those=20
> networks want to make sure they don't lose this when they=20
> evolve to SIP. Given that in SIP you could do things=20
> differently and hopefully better, PSTN interworking would=20
> appear to be the essential driver behind the TISPAN=20
> requirements, but presumably an important driver in the eyes=20
> of the carriers concerned. For the enterprise market I just=20
> don't see it as important. We used to have it on PBXs right=20
> back in the 70s and 80s and it was popular then, but=20
> voicemail has pretty well taken over in the enterprise. I=20
> hope this sheds some light.
>=20
> John
>=20
> > -----Original Message-----
> > From: Francois Audet [mailto:audet@nortel.com]
> > Sent: 05 April 2007 23:18
> > To: Adam Roach; SIPPING WG
> > Subject: RE: [Sipping] Call Completion: In Defense of Explicit=20
> > Operations
> >=20
> > Wouldn't it be possible to do this CCBS/CCNR stuff with a simple=20
> > dialog package, and ditch this "queue management" mechanism?
> >=20
> > This seems to me to be a classic case of Engineers-gone-wild.
> >=20
> > I see this in the poetzl draft:
> >=20
> >     Completion of Calls on no Reply (CCNR) provides the caller with=20
> > the
> >     ability to complete a requested call to a callee=20
> without having to
> >     make a new call attempt when the callee becomes not busy after=20
> >     having initiated an activity.  The CCNR service description is=20
> >     defined in ETSI EN 301 134 [6].=20
> >=20
> >     The call completion services provide the capability to queue=20
> >     several CCBS/CCNR requests to the same callee on a FIFO=20
> basis. It=20
> >     therefore requires functionalities like notifying=20
> changes of queue
> >     states and managing queues. =20
> >=20
> > In other words, we are defining this really complex stuff=20
> just because=20
> > it used to work like this in some ETSI standard for PSTN.
> >=20
> > Is there a better justification than that? What am I missing?
> >=20
> > Couldn't we handle some basic level of queueing at the endpoints=20
> > themselves, and use a simple dialog package, and avoid all=20
> this stuff=20
> > that creates all the complexity?
> >=20
> > This CCBS/CCNR feature is one of the feature that has the most=20
> > variation
> >=20
> > in implementations in PSTN that I know of. To me, picking a really=20
> > complicated variant and replicating it in SIP (either by=20
> bastardizing=20
> > the protocol, or by using an entirely different protocol=20
> altogether)=20
> > is not a good idea.
> > My take is
> > that there will be such a small uptake in implementation=20
> that it will=20
> > effectively useful only in a few confined environments where the it=20
> > can be mandated by law.
> >=20
> > I'd must rather have a simpler easier to implement version of the=20
> > service.
> >=20
> > > -----Original Message-----
> > > From: Adam Roach [mailto:adam@nostrum.com]
> > > Sent: Thursday, April 05, 2007 12:10
> > > To: SIPPING WG
> > > Subject: [Sipping] Call Completion: In Defense of Explicit
> > Operations
> > >=20
> > > Despite what appeared to be early agreement in the working group=20
> > > (and on the MIG mailing list) that we wanted to=20
> discourage the use=20
> > > of SUBSCRIBE and NOTIFY as general purpose RPC=20
> mechanisms. This is=20
> > > the primary objection that I have raised to=20
> > > draft-poetzl-sipping-call-completion,
> > > which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
> > >=20
> > > In the spirit of sending text, I described an alternate set of=20
> > > mechanisms in draft-roach-sipping-callcomp-bfcp, which=20
> performs the=20
> > > same task without having implied side effects from the=20
> creation of a=20
> > > subscription.
> > >=20
> > > I'll further note that the use of SUBSCRIBE to both create a=20
> > > subscription and manipulate a call queue falls under the=20
> category of=20
> > > "one operation with two separate effects." We have a very poor=20
> > > institutional memory indeed if we cannot recall why operations of=20
> > > this nature are Really Bad Ideas (cf. REFER creating a=20
> subscription;=20
> > > REGISTER with call processing upload; and BYE with an=20
> "Also" header=20
> > > field).
> > >=20
> > > All of this notwithstanding, in Prague, there seemed to=20
> be a curious=20
> > > indifference to pursuing the path laden with such Really=20
> Bad Ideas.=20
> > > I suspect that this indifference is a result of the=20
> arguments raised=20
> > > so far against the mechanism I have proposed, which I have done=20
> > > little to refute so far (largely because I believed that=20
> the merits=20
> > > of a system with explicit operations were self-evident=20
> enough that=20
> > > the objections would seem trifling in comparison).
> > >=20
> > > As far as I can tell, the objections raised so far have=20
> fallen into=20
> > > three primary categories:
> > >=20
> > >    1. "The use of BFCP is troubling because, in a
> > decomposed gateway,
> > >       the BFCP goes to the Media Gateway, while the
> > signaling goes to
> > >       the Media Gateway Controller."
> > >=20
> > >       This objection, raised on one of the slides during=20
> the SIPPING
> > >       meeting on March 23rd as the official reason TISPAN
> > rejected the
> > >       approach, is based on a simple misconception.
> > >=20
> > >       The BFCP goes wherever the SDP says the BFCP goes.=20
> In the case=20
> > > of
> > >       a decomposed gateway, this could be the Media
> > Gateway, the Media
> > >       Gateway Controller, or any other random
> > network-connected server
> > >       that the Media Gity to queue=20
> >     several CCBS/CCNR requests to the same callee on a FIFO=20
> basis. It=20
> >     therefore requires functionalities like notifying=20
> changes of queue
> >     states and managing queues. =20
> >=20
> > In other words, we are defining this really complex stuff=20
> just because=20
> > it used to work like this in some ETSI standard for PSTN.
> >=20
> > Is there a better justification than that? What am I missing?
> >=20
> > Couldn't we handle some basic level of queueing at the endpoints=20
> > themselves, and use a simple dialog package, and avoid all=20
> this stuff=20
> > that creates all the complexity?
> >=20
> > This CCBS/CCNR feature is one of the feature that has the most=20
> > variation
> >=20
> > in implementations in PSTN that I know of. To me, picking a really=20
> > complicated variant and replicating it in SIP (either by=20
> bastardizing=20
> > the protocol, or by using an entirely different protocol=20
> altogether)=20
> > is not a good idea.
> > My take is
> > that there will be such a small uptake in implementation=20
> that it will=20
> > effectively useful only in a few confined environments where the it=20
> > can be mandated by law.
> >=20
> > I'd must rather have a simpler easier to implement version of the=20
> > service.
> >=20
> > > -----Original Message-----
> > > From: Adam Roach [mailto:adam@nostrum.com]
> > > Sent: Thursday, April 05, 2007 12:10
> > > To: SIPPING WG
> > > Subject: [Sipping] Call Completion: In Defense of Explicit
> > Operations
> > >=20
> > > Despite what appeared to be early agreement in the working group=20
> > > (and on the MIG mailing list) that we wanted to=20
> discourage the use=20
> > > of SUBSCRIBE and NOTIFY as general purpose RPC=20
> mechanisms. This is=20
> > > the primary objection that I have raised to=20
> > > draft-poetzl-sipping-call-completion,
> > > which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
> > >=20
> > > In the spirit of sending text, I described an alternate set of=20
> > > mechanisms in draft-roach-sipping-callcomp-bfcp, which=20
> performs the=20
> > > same task without having implied side effects from the=20
> creation of a=20
> > > subscription.
> > >=20
> > > I'll further note that the use of SUBSCRIBE to both create a=20
> > > subscription and manipulate a call queue falls under the=20
> category of=20
> > > "one operation with two separate effects." We have a very poor=20
> > > institutional memory indeed if we cannot recall why operations of=20
> > > this nature are Really Bad Ideas (cf. REFER creating a=20
> subscription;=20
> > > REGISTER with call processing upload; and BYE with an=20
> "Also" header=20
> > > field).
> > >=20
> > > All of this notwithstanding, in Prague, there seemed to=20
> be a curious=20
> > > indifference to pursuing the path laden with such Really=20
> Bad Ideas.=20
> > > I suspect that this indifference is a result of the=20
> arguments raised=20
> > > so far against the mechanism I have proposed, which I have done=20
> > > little to refute so far (largely because I believed that=20
> the merits=20
> > > of a system with explicit operations were self-evident=20
> enough that=20
> > > the objections would seem trifling in comparison).
> > >=20
> > > As far as I can tell, the objections raised so far have=20
> fallen into=20
> > > three primary categories:
> > >=20
> > >    1. "The use of BFCP is troubling because, in a
> > decomposed gateway,
> > >       the BFCP goes to the Media Gateway, while the
> > signaling goes to
> > >       the Media Gateway Controller."
> > >=20
> > >       This objection, raised on one of the slides during=20
> the SIPPING
> > >       meeting on March 23rd as the official reason TISPAN
> > rejected the
> > >       approach, is based on a simple misconception.
> > >=20
> > >       The BFCP goes wherever the SDP says the BFCP goes.=20
> In the case=20
> > > of
> > >       a decomposed gateway, this could be the Media
> > Gateway, the Media
> > >       Gateway Controller, or any other random
> > network-connected server
> > >       that the Media Gateway Controller wants. I agree that it=20
> > > probably
> > >       is most sensible to send it to the Media Gateway
> > Controller, and
> > >       this is trivial to achieve.
> > >=20
> > >    2. "In the case of PSTN interwork, there is no way to=20
> guarantee=20
> > > that
> > >       the ISUP (or other) signaling from the PSTN side=20
> lands on the=20
> > > same
> > >       gateway that the client has a BFCP connection to."
> > >=20
> > >       This is true, and it is a relatively difficult
> > problem to solve
> > >       (not impossible, though; I proposed several potential=20
> > > solutions in
> > >       San Diego). It is meaningless to raise it in objection to an
> > >       alternate proposal, since it exists in almost
> > precisely the same
> > >       form in draft-poetzl-sipping-call-completion; and=20
> any solution
> > >       that can be applied to one solution can be applied to
> > the other.
> > >=20
> > >    3. "We don't want to add another protocol."
> > >=20
> > >       I suspect this argument is the one that is=20
> receiving the most
> > >       traction, probably because most of the people=20
> involved in the
> > >       discussion are not familiar with BFCP. The protocol=20
> itself is=20
> > > very
> > >       straightforward and extremely easy to implement. In fact,
> > >       exclusively for the purpose of answering this email (and
> > >       demonstrating this very point), I threw together a BFCP
> > >       implementation sufficient for implementation of the Call
> > >       Completion service described in=20
> > > draft-roach-sipping-callcomp-bfcp.
> > >       It took me two hours, and compiles down to less than 4 kb of
> > >       object code on an intel processor. It's attached to
> > this message
> > >       to help the participants in the conversation
> > understand just how
> > >       very little is being added to applications by this
> > use of BFCP.
> > >=20
> > > So, is that it? The first two objections are simply red herrings,=20
> > > and the third is based on a misconception regarding the level of=20
> > > effort required to implement BFCP. Are we really going to=20
> down the=20
> > > path of doing things incorrectly over what amount to=20
> > > misunderstandings?
> > >=20
> > > /a
> > >=20
> > >=20
> > >=20
> > > P.S. In case anyone wants a more full-featured BFCP stack, I'll=20
> > > point to the confiance project on SourceForge, available=20
> under the=20
> > > Academic Freedom License, which is compatible with commercial
> > development. See
> > > http://confiance.sourceforge.net/
> > >=20
> >=20
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
> >=20
>=20

_______________________________________________
Sipping mailing list  https://www1.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





ateway Controller wants. I agree that it=20
> > > probably
> > >       is most sensible to send it to the Media Gateway
> > Controller, and
> > >       this is trivial to achieve.
> > >=20
> > >    2. "In the case of PSTN interwork, there is no way to=20
> guarantee=20
> > > that
> > >       the ISUP (or other) signaling from the PSTN side=20
> lands on the=20
> > > same
> > >       gateway that the client has a BFCP connection to."
> > >=20
> > >       This is true, and it is a relatively difficult
> > problem to solve
> > >       (not impossible, though; I proposed several potential=20
> > > solutions in
> > >       San Diego). It is meaningless to raise it in objection to an
> > >       alternate proposal, since it exists in almost
> > precisely the same
> > >       form in draft-poetzl-sipping-call-completion; and=20
> any solution
> > >       that can be applied to one solution can be applied to
> > the other.
> > >=20
> > >    3. "We don't want to add another protocol."
> > >=20
> > >       I suspect this argument is the one that is=20
> receiving the most
> > >       traction, probably because most of the people=20
> involved in the
> > >       discussion are not familiar with BFCP. The protocol=20
> itself is=20
> > > very
> > >       straightforward and extremely easy to implement. In fact,
> > >       exclusively for the purpose of answering this email (and
> > >       demonstrating this very point), I threw together a BFCP
> > >       implementation sufficient for implementation of the Call
> > >       Completion service described in=20
> > > draft-roach-sipping-callcomp-bfcp.
> > >       It took me two hours, and compiles down to less than 4 kb of
> > >       object code on an intel processor. It's attached to
> > this message
> > >       to help the participants in the conversation
> > understand just how
> > >       very little is being added to applications by this
> > use of BFCP.
> > >=20
> > > So, is that it? The first two objections are simply red herrings,=20
> > > and the third is based on a misconception regarding the level of=20
> > > effort required to implement BFCP. Are we really going to=20
> down the=20
> > > path of doing things incorrectly over what amount to=20
> > > misunderstandings?
> > >=20
> > > /a
> > >=20
> > >=20
> > >=20
> > > P.S. In case anyone wants a more full-featured BFCP stack, I'll=20
> > > point to the confiance project on SourceForge, available=20
> under the=20
> > > Academic Freedom License, which is compatible with commercial
> > development. See
> > > http://confiance.sourceforge.net/
> > >=20
> >=20
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
> >=20
>=20

_______________________________________________
Sipping mailing list  https://www1.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





From sipping-bounces@ietf.org Sat Apr 07 15:15:27 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaGNB-0006wB-V9; Sat, 07 Apr 2007 15:14:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaGNB-0006us-CY
	for sipping@ietf.org; Sat, 07 Apr 2007 15:14:53 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaGN9-0007Li-Oy
	for sipping@ietf.org; Sat, 07 Apr 2007 15:14:53 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JG50025D6SI1T@siemenscomms.co.uk> for sipping@ietf.org;
	Sat, 07 Apr 2007 20:14:42 +0100 (BST)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VC0JVM>; Sat, 07 Apr 2007 20:14:46 +0100
Content-return: allowed
Date: Sat, 07 Apr 2007 20:14:41 +0100
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
To: Francois Audet <audet@nortel.com>, Adam Roach <adam@nostrum.com>,
	SIPPING WG <sipping@ietf.org>
Message-id: <50B1CBA96870A34799A506B2313F26670B7D7824@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ba0d4c5f57f7c289496fce758bbf4798
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Francois,

Clearly the TISPAN people want more than that.

John 

> -----Original Message-----
> From: Francois Audet [mailto:audet@nortel.com] 
> Sent: 07 April 2007 19:39
> To: Elwell, John; Adam Roach; SIPPING WG
> Subject: RE: [Sipping] Call Completion: In Defense of 
> Explicit Operations
> 
> Hi John,
> 
> Do you think that this implementing this feature in
> the way Adam and I were alluding to, i.e., where queuing
> is handled by the clients but without some of the more
> complex "queue management" feature would be acceptable
> in those countries?
> 
> That would allow us to have a very simple implemenation
> without compromising the semantics of SUBSCRIBE or 
> using a separate protocol (BFCP).
> 
> 
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens.com] 
> > Sent: Saturday, April 07, 2007 11:29
> > To: Audet, Francois (SC100:3055); Adam Roach; SIPPING WG
> > Subject: RE: [Sipping] Call Completion: In Defense of 
> > Explicit Operations
> > 
> > I know this feature is quite popular in the PSTN residential 
> > market in various countries in Europe, particularly Germany 
> > and also the UK to some extent. Customers seem prepared to 
> > spend a few euro cents for the convenience it gives in a 
> > presence-less environment. So I think the operators of those 
> > networks want to make sure they don't lose this when they 
> > evolve to SIP. Given that in SIP you could do things 
> > differently and hopefully better, PSTN interworking would 
> > appear to be the essential driver behind the TISPAN 
> > requirements, but presumably an important driver in the eyes 
> > of the carriers concerned. For the enterprise market I just 
> > don't see it as important. We used to have it on PBXs right 
> > back in the 70s and 80s and it was popular then, but 
> > voicemail has pretty well taken over in the enterprise. I 
> > hope this sheds some light.
> > 
> > John
> > 
> > > -----Original Message-----
> > > From: Francois Audet [mailto:audet@nortel.com]
> > > Sent: 05 April 2007 23:18
> > > To: Adam Roach; SIPPING WG
> > > Subject: RE: [Sipping] Call Completion: In Defense of Explicit 
> > > Operations
> > > 
> > > Wouldn't it be possible to do this CCBS/CCNR stuff with a simple 
> > > dialog package, and ditch this "queue management" mechanism?
> > > 
> > > This seems to me to be a classic case of Engineers-gone-wild.
> > > 
> > > I see this in the poetzl draft:
> > > 
> > >     Completion of Calls on no Reply (CCNR) provides the 
> caller with 
> > > the
> > >     ability to complete a requested call to a callee 
> > without having to
> > >     make a new call attempt when the callee becomes not 
> busy after 
> > >     having initiated an activity.  The CCNR service 
> description is 
> > >     defined in ETSI EN 301 134 [6]. 
> > > 
> > >     The call completion services provide the capability to queue 
> > >     several CCBS/CCNR requests to the same callee on a FIFO 
> > basis. It 
> > >     therefore requires functionalities like notifying 
> > changes of queue
> > >     states and managing queues.  
> > > 
> > > In other words, we are defining this really complex stuff 
> > just because 
> > > it used to work like this in some ETSI standard for PSTN.
> > > 
> > > Is there a better justification than that? What am I missing?
> > > 
> > > Couldn't we handle some basic level of queueing at the endpoints 
> > > themselves, and use a simple dialog package, and avoid all 
> > this stuff 
> > > that creates all the complexity?
> > > 
> > > This CCBS/CCNR feature is one of the feature that has the most 
> > > variation
> > > 
> > > in implementations in PSTN that I know of. To me, picking 
> a really 
> > > complicated variant and replicating it in SIP (either by 
> > bastardizing 
> > > the protocol, or by using an entirely different protocol 
> > altogether) 
> > > is not a good idea.
> > > My take is
> > > that there will be such a small uptake in implementation 
> > that it will 
> > > effectively useful only in a few confined environments 
> where the it 
> > > can be mandated by law.
> > > 
> > > I'd must rather have a simpler easier to implement version of the 
> > > service.
> > > 
> > > > -----Original Message-----
> > > > From: Adam Roach [mailto:adam@nostrum.com]
> > > > Sent: Thursday, April 05, 2007 12:10
> > > > To: SIPPING WG
> > > > Subject: [Sipping] Call Completion: In Defense of Explicit
> > > Operations
> > > > 
> > > > Despite what appeared to be early agreement in the 
> working group 
> > > > (and on the MIG mailing list) that we wanted to 
> > discourage the use 
> > > > of SUBSCRIBE and NOTIFY as general purpose RPC 
> > mechanisms. This is 
> > > > the primary objection that I have raised to 
> > > > draft-poetzl-sipping-call-completion,
> > > > which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
> > > > 
> > > > In the spirit of sending text, I described an alternate set of 
> > > > mechanisms in draft-roach-sipping-callcomp-bfcp, which 
> > performs the 
> > > > same task without having implied side effects from the 
> > creation of a 
> > > > subscription.
> > > > 
> > > > I'll further note that the use of SUBSCRIBE to both create a 
> > > > subscription and manipulate a call queue falls under the 
> > category of 
> > > > "one operation with two separate effects." We have a very poor 
> > > > institutional memory indeed if we cannot recall why 
> operations of 
> > > > this nature are Really Bad Ideas (cf. REFER creating a 
> > subscription; 
> > > > REGISTER with call processing upload; and BYE with an 
> > "Also" header 
> > > > field).
> > > > 
> > > > All of this notwithstanding, in Prague, there seemed to 
> > be a curious 
> > > > indifference to pursuing the path laden with such Really 
> > Bad Ideas. 
> > > > I suspect that this indifference is a result of the 
> > arguments raised 
> > > > so far against the mechanism I have proposed, which I have done 
> > > > little to refute so far (largely because I believed that 
> > the merits 
> > > > of a system with explicit operations were self-evident 
> > enough that 
> > > > the objections would seem trifling in comparison).
> > > > 
> > > > As far as I can tell, the objections raised so far have 
> > fallen into 
> > > > three primary categories:
> > > > 
> > > >    1. "The use of BFCP is troubling because, in a
> > > decomposed gateway,
> > > >       the BFCP goes to the Media Gateway, while the
> > > signaling goes to
> > > >       the Media Gateway Controller."
> > > > 
> > > >       This objection, raised on one of the slides during 
> > the SIPPING
> > > >       meeting on March 23rd as the official reason TISPAN
> > > rejected the
> > > >       approach, is based on a simple misconception.
> > > > 
> > > >       The BFCP goes wherever the SDP says the BFCP goes. 
> > In the case 
> > > > of
> > > >       a decomposed gateway, this could be the Media
> > > Gateway, the Media
> > > >       Gateway Controller, or any other random
> > > network-connected server
> > > >       that the Media Gateway Controller wants. I agree that it 
> > > > probably
> > > >       is most sensible to send it to the Media Gateway
> > > Controller, and
> > > >       this is trivial to achieve.
> > > > 
> > > >    2. "In the case of PSTN interwork, there is no way to 
> > guarantee 
> > > > that
> > > >       the ISUP (or other) signaling from the PSTN side 
> > lands on the 
> > > > same
> > > >       gateway that the client has a BFCP connection to."
> > > > 
> > > >       This is true, and it is a relatively difficult
> > > problem to solve
> > > >       (not impossible, though; I proposed several potential 
> > > > solutions in
> > > >       San Diego). It is meaningless to raise it in 
> objection to an
> > > >       alternate proposal, since it exists in almost
> > > precisely the same
> > > >       form in draft-poetzl-sipping-call-completion; and 
> > any solution
> > > >       that can be applied to one solution can be applied to
> > > the other.
> > > > 
> > > >    3. "We don't want to add another protocol."
> > > > 
> > > >       I suspect this argument is the one that is 
> > receiving the most
> > > >       traction, probably because most of the people 
> > involved in the
> > > >       discussion are not familiar with BFCP. The protocol 
> > itself is 
> > > > very
> > > >       straightforward and extremely easy to implement. In fact,
> > > >       exclusively for the purpose of answering this email (and
> > > >       demonstrating this very point), I threw together a BFCP
> > > >       implementation sufficient for implementation of the Call
> > > >       Completion service described in 
> > > > draft-roach-sipping-callcomp-bfcp.
> > > >       It took me two hours, and compiles down to less 
> than 4 kb of
> > > >       object code on an intel processor. It's attached to
> > > this message
> > > >       to help the participants in the conversation
> > > understand just how
> > > >       very little is being added to applications by this
> > > use of BFCP.
> > > > 
> > > > So, is that it? The first two objections are simply red 
> herrings, 
> > > > and the third is based on a misconception regarding the 
> level of 
> > > > effort required to implement BFCP. Are we really going to 
> > down the 
> > > > path of doing things incorrectly over what amount to 
> > > > misunderstandings?
> > > > 
> > > > /a
> > > > 
> > > > 
> > > > 
> > > > P.S. In case anyone wants a more full-featured BFCP stack, I'll 
> > > > point to the confiance project on SourceForge, available 
> > under the 
> > > > Academic Freedom License, which is compatible with commercial
> > > development. See
> > > > http://confiance.sourceforge.net/
> > > > 
> > > 
> > > _______________________________________________
> > > Sipping mailing list  
> https://www1.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
> > > 
> > 
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sat Apr 07 15:24:43 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaGW0-0004kH-Va; Sat, 07 Apr 2007 15:24:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaGVz-0004hI-O1
	for sipping@ietf.org; Sat, 07 Apr 2007 15:23:59 -0400
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaGVz-00007K-8k
	for sipping@ietf.org; Sat, 07 Apr 2007 15:23:59 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l37JNnF19941; Sat, 7 Apr 2007 19:23:49 GMT
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
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Sat, 7 Apr 2007 14:23:32 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0FEFCEB6@zrc2hxm0.corp.nortel.com>
In-Reply-To: <260AFF3D-EA06-4F12-95DD-5E81DE4D2B11@cs.columbia.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
thread-index: Acd5RAf/SMutgEplQICbfeUiverWJwABW7rQ
References: <50B1CBA96870A34799A506B2313F26670B7D7823@ntht201e.siemenscomms.co.uk>
	<260AFF3D-EA06-4F12-95DD-5E81DE4D2B11@cs.columbia.edu>
From: "Francois Audet" <audet@nortel.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>,
	"Elwell, John" <john.elwell@siemens.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 83e9494d829b08cc3f644ef6ac1b9bd4
Cc: SIPPING WG <sipping@ietf.org>, Adam Roach <adam@nostrum.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

That was not really what I was thinking of, but it does
seems like a reasonable idea.

A simple implemenation would use a dialog package, and
for the people who need this queuing (i.e., TISPAN), then
we could add this call log.

I think Henning might be on to something. If this mechanism
is more useful than just the TISPAN queue management feature,
then people may actually implement it.=20

> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]=20
> Sent: Saturday, April 07, 2007 11:39
> To: Elwell, John
> Cc: Audet, Francois (SC100:3055); Adam Roach; SIPPING WG
> Subject: Re: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
> This seems like a special case of a call log handler, which=20
> might be useful beyond CCNR. Why not simply subscribe to a=20
> call log event package (to be defined) and let the UA manage=20
> the call backs? That way, you can do call backs for calls=20
> placed from other devices or even previously completed calls,=20
> just like people routinely dial from their "recent calls" list.
>=20
> I don't know if Francois was referring to the same thing as=20
> "a simple dialog package".
>=20
> Henning
>=20
> On Apr 7, 2007, at 2:28 PM, Elwell, John wrote:
>=20
> > I know this feature is quite popular in the PSTN=20
> residential market in=20
> > various countries in Europe, particularly Germany and also=20
> the UK to=20
> > some extent. Customers seem prepared to spend a few euro=20
> cents for the=20
> > convenience it gives in a presence-less environment. So I think the=20
> > operators of those networks want to make sure they don't lose this=20
> > when they evolve to SIP. Given that in SIP you could do things=20
> > differently and hopefully better, PSTN interworking would=20
> appear to be=20
> > the essential driver behind the TISPAN requirements, but=20
> presumably an=20
> > important driver in the eyes of the carriers concerned. For the=20
> > enterprise market I just don't see it as important. We used=20
> to have it=20
> > on PBXs right back in the 70s and 80s and it was popular then, but=20
> > voicemail has pretty well taken over in the enterprise. I hope this=20
> > sheds some light.
> >
> > John
> >
> >> -----Original Message-----
> >> From: Francois Audet [mailto:audet@nortel.com]
> >> Sent: 05 April 2007 23:18
> >> To: Adam Roach; SIPPING WG
> >> Subject: RE: [Sipping] Call Completion: In Defense of Explicit=20
> >> Operations
> >>
> >> Wouldn't it be possible to do this CCBS/CCNR stuff with a simple=20
> >> dialog package, and ditch this "queue management" mechanism?
> >>
> >> This seems to me to be a classic case of Engineers-gone-wild.
> >>
> >> I see this in the poetzl draft:
> >>
> >>     Completion of Calls on no Reply (CCNR) provides the=20
> caller with=20
> >> the
> >>     ability to complete a requested call to a callee=20
> without having=20
> >> to
> >>     make a new call attempt when the callee becomes not busy after
> >>     having initiated an activity.  The CCNR service description is
> >>     defined in ETSI EN 301 134 [6].
> >>
> >>     The call completion services provide the capability to queue
> >>     several CCBS/CCNR requests to the same callee on a=20
> FIFO basis. It
> >>     therefore requires functionalities like notifying changes of=20
> >> queue
> >>     states and managing queues.
> >>
> >> In other words, we are defining this really complex stuff just=20
> >> because it used to work like this in some ETSI standard for PSTN.
> >>
> >> Is there a better justification than that? What am I missing?
> >>
> >> Couldn't we handle some basic level of queueing at the endpoints=20
> >> themselves, and use a simple dialog package, and avoid all=20
> this stuff=20
> >> that creates all the complexity?
> >>
> >> This CCBS/CCNR feature is one of the feature that has the most=20
> >> variation
> >>
> >> in implementations in PSTN that I know of. To me, picking a really=20
> >> complicated variant and replicating it in SIP (either by=20
> bastardizing=20
> >> the protocol, or by using an entirely different protocol=20
> altogether)=20
> >> is not a good idea.
> >> My take is
> >> that there will be such a small uptake in implementation=20
> that it will=20
> >> effectively useful only in a few confined environments=20
> where the it=20
> >> can be mandated by law.
> >>
> >> I'd must rather have a simpler easier to implement version of the=20
> >> service.
> >>
> >>> -----Original Message-----
> >>> From: Adam Roach [mailto:adam@nostrum.com]
> >>> Sent: Thursday, April 05, 2007 12:10
> >>> To: SIPPING WG
> >>> Subject: [Sipping] Call Completion: In Defense of Explicit
> >> Operations
> >>>
> >>> Despite what appeared to be early agreement in the working group=20
> >>> (and on the MIG mailing list) that we wanted to=20
> discourage the use=20
> >>> of SUBSCRIBE and NOTIFY as general purpose RPC=20
> mechanisms. This is=20
> >>> the primary objection that I have raised to=20
> >>> draft-poetzl-sipping-call-completion,
> >>> which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
> >>>
> >>> In the spirit of sending text, I described an alternate set of=20
> >>> mechanisms in draft-roach-sipping-callcomp-bfcp, which=20
> performs the=20
> >>> same task without having implied side effects from the=20
> creation of a=20
> >>> subscription.
> >>>
> >>> I'll further note that the use of SUBSCRIBE to both create a=20
> >>> subscription and manipulate a call queue falls under the=20
> category of=20
> >>> "one operation with two separate effects." We have a very poor=20
> >>> institutional memory indeed if we cannot recall why operations of=20
> >>> this nature are Really Bad Ideas (cf. REFER creating a=20
> subscription;=20
> >>> REGISTER with call processing upload; and BYE with an=20
> "Also" header=20
> >>> field).
> >>>
> >>> All of this notwithstanding, in Prague, there seemed to=20
> be a curious=20
> >>> indifference to pursuing the path laden with such Really=20
> Bad Ideas.=20
> >>> I suspect that this indifference is a result of the=20
> arguments raised=20
> >>> so far against the mechanism I have proposed, which I have done=20
> >>> little to refute so far (largely because I believed that=20
> the merits=20
> >>> of a system with explicit operations were self-evident=20
> enough that=20
> >>> the objections would seem trifling in comparison).
> >>>
> >>> As far as I can tell, the objections raised so far have=20
> fallen into=20
> >>> three primary categories:
> >>>
> >>>    1. "The use of BFCP is troubling because, in a
> >> decomposed gateway,
> >>>       the BFCP goes to the Media Gateway, while the
> >> signaling goes to
> >>>       the Media Gateway Controller."
> >>>
> >>>       This objection, raised on one of the slides during=20
> the SIPPING
> >>>       meeting on March 23rd as the official reason TISPAN
> >> rejected the
> >>>       approach, is based on a simple misconception.
> >>>
> >>>       The BFCP goes wherever the SDP says the BFCP goes.=20
> In the case=20
> >>> of
> >>>       a decomposed gateway, this could be the Media
> >> Gateway, the Media
> >>>       Gateway Controller, or any other random
> >> network-connected server
> >>>       that the Media Gateway Controller wants. I agree that it=20
> >>> probably
> >>>       is most sensible to send it to the Media Gateway
> >> Controller, and
> >>>       this is trivial to achieve.
> >>>
> >>>    2. "In the case of PSTN interwork, there is no way to=20
> guarantee=20
> >>> that
> >>>       the ISUP (or other) signaling from the PSTN side=20
> lands on the=20
> >>> same
> >>>       gateway that the client has a BFCP connection to."
> >>>
> >>>       This is true, and it is a relatively difficult
> >> problem to solve
> >>>       (not impossible, though; I proposed several potential=20
> >>> solutions in
> >>>       San Diego). It is meaningless to raise it in objection to an
> >>>       alternate proposal, since it exists in almost
> >> precisely the same
> >>>       form in draft-poetzl-sipping-call-completion; and=20
> any solution
> >>>       that can be applied to one solution can be applied to
> >> the other.
> >>>
> >>>    3. "We don't want to add another protocol."
> >>>
> >>>       I suspect this argument is the one that is=20
> receiving the most
> >>>       traction, probably because most of the people=20
> involved in the
> >>>       discussion are not familiar with BFCP. The protocol=20
> itself is=20
> >>> very
> >>>       straightforward and extremely easy to implement. In fact,
> >>>       exclusively for the purpose of answering this email (and
> >>>       demonstrating this very point), I threw together a BFCP
> >>>       implementation sufficient for implementation of the Call
> >>>       Completion service described in=20
> >>> draft-roach-sipping-callcomp-bfcp.
> >>>       It took me two hours, and compiles down to less than 4 kb of
> >>>       object code on an intel processor. It's attached to
> >> this message
> >>>       to help the participants in the conversation
> >> understand just how
> >>>       very little is being added to applications by this
> >> use of BFCP.
> >>>
> >>> So, is that it? The first two objections are simply red herrings,=20
> >>> and the third is based on a misconception regarding the level of=20
> >>> effort required to implement BFCP. Are we really going to=20
> down the=20
> >>> path of doing things incorrectly over what amount to=20
> >>> misunderstandings?
> >>>
> >>> /a
> >>>
> >>>
> >>>
> >>> P.S. In case anyone wants a more full-featured BFCP stack, I'll=20
> >>> point to the confiance project on SourceForge, available=20
> under the=20
> >>> Academic Freedom License, which is compatible with commercial
> >> development. See
> >>> http://confiance.sourceforge.net/
> >>>
> >>
> >> _______________________________________________
> >> Sipping mailing list =20
> https://www1.ietf.org/mailman/listinfo/sipping
> >> This list is for NEW development of the application of SIP Use=20
> >> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> >> sip@ietf.org for new developments of core SIP
> >>
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
>=20
>=20

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sat Apr 07 15:36:19 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaGhG-00032e-83; Sat, 07 Apr 2007 15:35:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaGhF-00032Z-IU
	for sipping@ietf.org; Sat, 07 Apr 2007 15:35:37 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaGhE-0001Vm-VP
	for sipping@ietf.org; Sat, 07 Apr 2007 15:35:37 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JG500A1V7QZDE@siemenscomms.co.uk> for sipping@ietf.org;
	Sat, 07 Apr 2007 20:35:23 +0100 (BST)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VC0JWS>; Sat, 07 Apr 2007 20:35:27 +0100
Content-return: allowed
Date: Sat, 07 Apr 2007 20:35:21 +0100
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Message-id: <50B1CBA96870A34799A506B2313F26670B7D7825@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c2e58d9873012c90703822e287241385
Cc: SIPPING WG <sipping@ietf.org>, Francois Audet <audet@nortel.com>,
	Adam Roach <adam@nostrum.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Henning,

I am not sure what you have in mind or how it caters for the so-called
queueing requirement from TISPAN.

John 

> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu] 
> Sent: 07 April 2007 19:39
> To: Elwell, John
> Cc: Francois Audet; Adam Roach; SIPPING WG
> Subject: Re: [Sipping] Call Completion: In Defense of 
> Explicit Operations
> 
> This seems like a special case of a call log handler, which might be  
> useful beyond CCNR. Why not simply subscribe to a call log event  
> package (to be defined) and let the UA manage the call backs? That  
> way, you can do call backs for calls placed from other devices or  
> even previously completed calls, just like people routinely 
> dial from  
> their "recent calls" list.
> 
> I don't know if Francois was referring to the same thing as 
> "a simple  
> dialog package".
> 
> Henning
> 
> On Apr 7, 2007, at 2:28 PM, Elwell, John wrote:
> 
> > I know this feature is quite popular in the PSTN 
> residential market in
> > various countries in Europe, particularly Germany and also the UK  
> > to some
> > extent. Customers seem prepared to spend a few euro cents for the
> > convenience it gives in a presence-less environment. So I think the
> > operators of those networks want to make sure they don't lose this  
> > when they
> > evolve to SIP. Given that in SIP you could do things differently and
> > hopefully better, PSTN interworking would appear to be the  
> > essential driver
> > behind the TISPAN requirements, but presumably an important driver  
> > in the
> > eyes of the carriers concerned. For the enterprise market I just  
> > don't see
> > it as important. We used to have it on PBXs right back in the 70s  
> > and 80s
> > and it was popular then, but voicemail has pretty well taken over  
> > in the
> > enterprise. I hope this sheds some light.
> >
> > John
> >
> >> -----Original Message-----
> >> From: Francois Audet [mailto:audet@nortel.com]
> >> Sent: 05 April 2007 23:18
> >> To: Adam Roach; SIPPING WG
> >> Subject: RE: [Sipping] Call Completion: In Defense of
> >> Explicit Operations
> >>
> >> Wouldn't it be possible to do this CCBS/CCNR stuff with a simple
> >> dialog package, and ditch this "queue management" mechanism?
> >>
> >> This seems to me to be a classic case of Engineers-gone-wild.
> >>
> >> I see this in the poetzl draft:
> >>
> >>     Completion of Calls on no Reply (CCNR) provides the
> >> caller with the
> >>     ability to complete a requested call to a callee without
> >> having to
> >>     make a new call attempt when the callee becomes not busy after
> >>     having initiated an activity.  The CCNR service description is
> >>     defined in ETSI EN 301 134 [6].
> >>
> >>     The call completion services provide the capability to queue
> >>     several CCBS/CCNR requests to the same callee on a 
> FIFO basis. It
> >>     therefore requires functionalities like notifying changes
> >> of queue
> >>     states and managing queues.
> >>
> >> In other words, we are defining this really complex stuff just  
> >> because
> >> it
> >> used to work like this in some ETSI standard for PSTN.
> >>
> >> Is there a better justification than that? What am I missing?
> >>
> >> Couldn't we handle some basic level of queueing at the endpoints
> >> themselves,
> >> and use a simple dialog package, and avoid all this stuff that  
> >> creates
> >> all
> >> the complexity?
> >>
> >> This CCBS/CCNR feature is one of the feature that has the
> >> most variation
> >>
> >> in implementations in PSTN that I know of. To me, picking a really
> >> complicated
> >> variant and replicating it in SIP (either by bastardizing the
> >> protocol,
> >> or
> >> by using an entirely different protocol altogether) is not a
> >> good idea.
> >> My take is
> >> that there will be such a small uptake in implementation 
> that it will
> >> effectively
> >> useful only in a few confined environments where the it can
> >> be mandated
> >> by law.
> >>
> >> I'd must rather have a simpler easier to implement version of the
> >> service.
> >>
> >>> -----Original Message-----
> >>> From: Adam Roach [mailto:adam@nostrum.com]
> >>> Sent: Thursday, April 05, 2007 12:10
> >>> To: SIPPING WG
> >>> Subject: [Sipping] Call Completion: In Defense of Explicit
> >> Operations
> >>>
> >>> Despite what appeared to be early agreement in the working
> >>> group (and on the MIG mailing list) that we wanted to
> >>> discourage the use of SUBSCRIBE and NOTIFY as general purpose
> >>> RPC mechanisms. This is the primary objection that I have
> >>> raised to draft-poetzl-sipping-call-completion,
> >>> which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
> >>>
> >>> In the spirit of sending text, I described an alternate set
> >>> of mechanisms in draft-roach-sipping-callcomp-bfcp, which
> >>> performs the same task without having implied side effects
> >>> from the creation of a subscription.
> >>>
> >>> I'll further note that the use of SUBSCRIBE to both create a
> >>> subscription and manipulate a call queue falls under the
> >>> category of "one operation with two separate effects." We
> >>> have a very poor institutional memory indeed if we cannot
> >>> recall why operations of this nature are Really Bad Ideas
> >>> (cf. REFER creating a subscription; REGISTER with call
> >>> processing upload; and BYE with an "Also" header field).
> >>>
> >>> All of this notwithstanding, in Prague, there seemed to be a
> >>> curious indifference to pursuing the path laden with such
> >>> Really Bad Ideas. I suspect that this indifference is a
> >>> result of the arguments raised so far against the mechanism I
> >>> have proposed, which I have done little to refute so far
> >>> (largely because I believed that the merits of a system with
> >>> explicit operations were self-evident enough that the
> >>> objections would seem trifling in comparison).
> >>>
> >>> As far as I can tell, the objections raised so far have
> >>> fallen into three primary categories:
> >>>
> >>>    1. "The use of BFCP is troubling because, in a
> >> decomposed gateway,
> >>>       the BFCP goes to the Media Gateway, while the
> >> signaling goes to
> >>>       the Media Gateway Controller."
> >>>
> >>>       This objection, raised on one of the slides during 
> the SIPPING
> >>>       meeting on March 23rd as the official reason TISPAN
> >> rejected the
> >>>       approach, is based on a simple misconception.
> >>>
> >>>       The BFCP goes wherever the SDP says the BFCP goes. In
> >>> the case of
> >>>       a decomposed gateway, this could be the Media
> >> Gateway, the Media
> >>>       Gateway Controller, or any other random
> >> network-connected server
> >>>       that the Media Gateway Controller wants. I agree that
> >>> it probably
> >>>       is most sensible to send it to the Media Gateway
> >> Controller, and
> >>>       this is trivial to achieve.
> >>>
> >>>    2. "In the case of PSTN interwork, there is no way to
> >>> guarantee that
> >>>       the ISUP (or other) signaling from the PSTN side lands
> >>> on the same
> >>>       gateway that the client has a BFCP connection to."
> >>>
> >>>       This is true, and it is a relatively difficult
> >> problem to solve
> >>>       (not impossible, though; I proposed several potential
> >>> solutions in
> >>>       San Diego). It is meaningless to raise it in objection to an
> >>>       alternate proposal, since it exists in almost
> >> precisely the same
> >>>       form in draft-poetzl-sipping-call-completion; and 
> any solution
> >>>       that can be applied to one solution can be applied to
> >> the other.
> >>>
> >>>    3. "We don't want to add another protocol."
> >>>
> >>>       I suspect this argument is the one that is 
> receiving the most
> >>>       traction, probably because most of the people 
> involved in the
> >>>       discussion are not familiar with BFCP. The protocol
> >>> itself is very
> >>>       straightforward and extremely easy to implement. In fact,
> >>>       exclusively for the purpose of answering this email (and
> >>>       demonstrating this very point), I threw together a BFCP
> >>>       implementation sufficient for implementation of the Call
> >>>       Completion service described in
> >>> draft-roach-sipping-callcomp-bfcp.
> >>>       It took me two hours, and compiles down to less than 4 kb of
> >>>       object code on an intel processor. It's attached to
> >> this message
> >>>       to help the participants in the conversation
> >> understand just how
> >>>       very little is being added to applications by this
> >> use of BFCP.
> >>>
> >>> So, is that it? The first two objections are simply red
> >>> herrings, and the third is based on a misconception regarding
> >>> the level of effort required to implement BFCP. Are we really
> >>> going to down the path of doing things incorrectly over what
> >>> amount to misunderstandings?
> >>>
> >>> /a
> >>>
> >>>
> >>>
> >>> P.S. In case anyone wants a more full-featured BFCP stack,
> >>> I'll point to
> >>> the confiance project on SourceForge, available under the Academic
> >>> Freedom License, which is compatible with commercial
> >> development. See
> >>> http://confiance.sourceforge.net/
> >>>
> >>
> >> _______________________________________________
> >> Sipping mailing list  
> https://www1.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
> >>
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.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
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sat Apr 07 18:01:03 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaIvw-000789-Bk; Sat, 07 Apr 2007 17:58:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaIvs-00075r-HI
	for sipping@ietf.org; Sat, 07 Apr 2007 17:58:54 -0400
Received: from exprod6og54.obsmtp.com ([64.18.1.189])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HaIvq-0004Tr-Vx
	for sipping@ietf.org; Sat, 07 Apr 2007 17:58:52 -0400
Received: from source ([192.150.20.142]) by exprod6ob54.postini.com
	([64.18.5.12]) with SMTP; Sat, 07 Apr 2007 14:58:47 PDT
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l37LwhSd001230; Sat, 7 Apr 2007 14:58:44 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	l37Lwc0k008899; Sat, 7 Apr 2007 14:58:43 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 7 Apr 2007 14:58:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Comments on draft-ietf-sipping-cc-framework-07
Date: Sat, 7 Apr 2007 14:58:42 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223ADF7B@namail5.corp.adobe.com>
In-Reply-To: <458913680704060222p6a4aeab3n85cbdb998999f5a6@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Comments on draft-ietf-sipping-cc-framework-07
Thread-Index: Acd4LZ16EqRDn1tGTTqbzNj3Tm48oQBMHDwg
References: <458913680704060222p6a4aeab3n85cbdb998999f5a6@mail.gmail.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Xavier Marjou" <xavier.marjou@orange-ftgroup.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 07 Apr 2007 21:58:41.0994 (UTC)
	FILETIME=[E7BA2AA0:01C7795F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Xavier,

I believe you are right about 3pcc 'as is' not being compatible with P2P =
SIP.

Alan, what do you think?

Henry

-----Original Message-----
From: Xavier Marjou [mailto:xavier.marjou@orange-ftgroup.com]=20
Sent: Friday, April 06, 2007 4:22 AM
To: alan@sipstation.com; sipping@ietf.org
Subject: [Sipping] Comments on draft-ietf-sipping-cc-framework-07

Section 2.3
- Among the advantages of the peer-to-peer approach (ie: REFER msg)
over the 3pcc approach (ie: RFC3725), I would somehow underline that
the peer-to-peer approach allows the creation of a single SIP dialog
directly between the peers. On the contrary, with the 3pcc approach,
there are 2 SIP dialogs connected together by a SIP intermediary, the
controller. This intermediary thus affects, and may even limit, the
communication between the 2 peers. For example, if the controller does
not support a given SIP extension (eg: UPDATE message) whereas the 2
peers support it, the peers won't be able to use this SIP extension.
Similarly, if the controller supports a given SIP extension and only
one of the 2 peers support it, the SIP extension will be used in one
dialog but not in the other dialog, which means that the controller
will need to implement a complex behavior to mitigate this. (For this
later case, the use of OPTIONS before 3pcc could help, but this is
something I haven't seen being implemented.)

Section 2.7.1
- Elaborate on "calendar reminder": is it "just" a type of network
announcement service?

Section 2.7.2
- Replace
  advantage of the fact that the standard SIP URI has a user part.
  Most services may be thought of as user automatons that participate
  in SIP sessions.  It naturally follows that the user address, or the
  left-hand-side of the URI, should be utilized as a service indicator.
with:
  advantage of the fact that the standard the left-hand-side of the
  SIP URI is a user part. Most services may be thought of as user
  automatons that participate in SIP sessions.  It naturally follows
  that the user part should be utilized as a service indicator.

Section 2.7.2
- Replace
 "represents people. However, the URI can also represent services,"
with
 "represents a person. However, the URI can also represent a service,"

Section 3.1
- Rename "3.1. Early Dialog Actions" into "3.1. Remote Call Control
Actions on Early Dialog"

Section 3.2
- Rename "3.2. Single Dialog Actions" into "3.2. Remote Call Control
Actions on Single Dialog"

Section 3.2.
- What does CRM stand for?

Section 3.2.2.
- Replace "be conceptually be" with "conceptually be"

Section 3.2.2.
- It is currently written that "There is no way to distinguish between
the desire to go on or off hold." Reading sip-remote-cc-05, I
understand that placing on-hold or off-old is possible, but that it is
not possible to do it at a "per" media level.

Section 3.3.1
- In case user-A is a "secretary", and user-C is a "boss", it may be
that the SIP URI of user-C must not be revealed to any user-B. This is
something inherent to 3pcc. It should therefore be mentionned that
"the 3pcc helps if privacy is needed for C".

Section 3.3.3
- It's not easy to read the following text:
  "A
  could send the following requests: REFER B Refer-To: conference-URI
  INVITE conference-URI BYE B To add a party to a conference: REFER C
  Refer-To: conference-URI or REFER conference-URI Refer-To: C Using
  the 3pcc approach to transition to centrally mixed, the controller
  would send: INVITE mixer leg 1 (w/SDP of A) INVITE mixer leg 2 (w/SDP
  of B) INVITE C (late SDP) reINVITE A (w/SDP of mixer leg 1) reINVITE
  B (w/SDP of mixer leg 2) INVITE mixer leg3 (w/SDP of C) To add a
  party to a SIP conference: INVITE C (late SDP) INVITE conference-URI
  (w/SDP of C) Features enabled: - standard conference feature - call
  recording - answering-machine style screening (screening)"
Maybe rewrite it with
  "A could send the following requests:
  =B0 REFER B Refer-To: conference-URI
  =B0 INVITE conference-URI
  =B0 BYE B
 To add a party to a conference:
  =B0 REFER C Refer-To: conference-URI
  =B0 or REFER conference-URI Refer-To: C
  Using the 3pcc approach to transition to centrally mixed, the
controller would send:
  =B0 INVITE mixer leg 1 (w/SDP of A)
  =B0 INVITE mixer leg 2 (w/SDP of B)
  =B0 INVITE C (late SDP)
  =B0 reINVITE A (w/SDP of mixer leg 1)
  =B0 reINVITE B (w/SDP of mixer leg 2)
  =B0  INVITE mixer leg3 (w/SDP of C)
  To add a party to a SIP conference:
  =B0 INVITE C (late SDP)
  =B0 INVITE conference-URI (w/SDP of C)
Features enabled: - standard conference feature - call recording -
answering-machine style screening (screening)"

Section 3.3.4
- Replace "5.3) For" by "5.3).  For"
- There is no Section 5.3

Section 6
- I suggest to list example features by alphabetical order in section
6, 6.1, 6.1.1. ... otherwise it's difficulte to look for a given
feature among the different sections.

Section 6.1
- Update references for [service-examples], [conf-models],
[cc-transfer], [cc-framework], [sip-answer-mode] with [6], .... [28]

Section 6.1.4
- Replace "dialog state" with "dialog event package" ? If yes, add a
reference to [11], RFC 4235

Section 6.1.13
- Replace "Voice Portal Takes" with "Voice Portal takes"

_______________________________________________
Sipping mailing list  https://www1.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

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sat Apr 07 18:08:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaJ5T-00054F-WF; Sat, 07 Apr 2007 18:08:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaJ5S-00053r-1V
	for sipping@ietf.org; Sat, 07 Apr 2007 18:08:46 -0400
Received: from brinza.cc.columbia.edu ([128.59.29.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaJ5Q-0007Xv-Pr
	for sipping@ietf.org; Sat, 07 Apr 2007 18:08:46 -0400
Received: from [192.168.0.41] (pool-70-21-193-163.nwrk.east.verizon.net
	[70.21.193.163]) (user=hgs10 mech=PLAIN bits=0)
	by brinza.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id l37M8e9N019696
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sat, 7 Apr 2007 18:08:41 -0400 (EDT)
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B7D7825@ntht201e.siemenscomms.co.uk>
References: <50B1CBA96870A34799A506B2313F26670B7D7825@ntht201e.siemenscomms.co.uk>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <AE1496AB-EC74-4C7B-88B0-99129CF193CA@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Sat, 7 Apr 2007 18:08:32 -0400
To: "Elwell, John" <john.elwell@siemens.com>
X-Mailer: Apple Mail (2.752.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.8
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Francois Audet <audet@nortel.com>, SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

John,

I can't say I fully understand all the requirements, but here's what  
I had in mind:

Each UA subscribes to the call log for its AOR, presumably via  
incremental updates and maybe with some time limit ("I'm just back  
from vacation. Only give me calls that arrived earlier today, not  
three weeks ago."). Each time-stamped call is marked with its  
completion status, such as 'no response', 'busy', 'outgoing', etc.,  
just like you'd find on most cell phones today. When a UA becomes  
available again, e.g., after busy or being out of the office, the UA  
can easily reconstruct the "queue" of missed calls and dial any one  
of them, in whatever order it chooses. Since it has the complete  
list, it can easily determine whether some other UA for the same AOR  
has already returned a call. There doesn't seem to be a need to  
manage the queue on the proxy.

Being able to return calls from other devices seems to be a nice  
feature; naturally, web call logs do most of that today, but they are  
a bit harder to manage.

Henning

On Apr 7, 2007, at 3:35 PM, Elwell, John wrote:

> Henning,
>
> I am not sure what you have in mind or how it caters for the so-called
> queueing requirement from TISPAN.
>
> John
>


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 08 11:35:44 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaZNV-00023a-Oo; Sun, 08 Apr 2007 11:32:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaZNV-00023V-3I
	for sipping@ietf.org; Sun, 08 Apr 2007 11:32:29 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaZNU-0007ub-EQ
	for sipping@ietf.org; Sun, 08 Apr 2007 11:32:29 -0400
Received: from [192.168.0.102] (ppp-70-244-81-252.dsl.rcsntx.swbell.net
	[70.244.81.252]) (authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l38FWNIp041962
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sun, 8 Apr 2007 10:32:26 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <46190A56.4060206@nostrum.com>
Date: Sun, 08 Apr 2007 10:29:26 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.8 (X11/20061107)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <50B1CBA96870A34799A506B2313F26670B7D7824@ntht201e.siemenscomms.co.uk>
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B7D7824@ntht201e.siemenscomms.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.244.81.252 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4ec58ef3f343ebf5ac40a04538f9a6fc
Cc: Francois Audet <audet@nortel.com>, SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Elwell, John wrote:
> Francois,
>
> Clearly the TISPAN people want more than that.
>
>   

I think we understand that they *want* it to behave that way. What I 
believe is getting lost is the cost imposed by the requirements as 
written. In particular, there appears to be no dialog, only a 
unidirectional declaration of requirements without listening for any 
feedback.

To use an analogy: let's imagine that I wanted to buy a car. I could 
write down the list of features I wanted and then send a representative 
to the car dealer with that list. Now, imagine if the car dealer 
explained that they have something on the lot that has all of my 
features for $25,000, *except* it's not a stick shift -- and that, in 
fact, a model with those features *and* a stick shift would be such an 
odd special order that it would add $400,000 to the price of the car 
because of the need to re-tool the assembly line.

A sensible representative would take this information back to me and ask 
whether the additional cost was warranted. Of course, I would probably 
say, "no."

An insane representative would, without contacting me, raise a stink 
about the ridiculous cost for this feature and attempt to stand their 
ground, eventually imposing an additional $400,000 cost on me.

What I'd like to know for certain is that TISPAN *understands* the 
difficulty required to implement this one very small and rarely-used 
aspect of the feature, and that they have explicitly stated that it is 
important enough to justify the additional cost it imposes on the solution.

/a

>   
>> -----Original Message-----
>> From: Francois Audet [mailto:audet@nortel.com] 
>> Sent: 07 April 2007 19:39
>> To: Elwell, John; Adam Roach; SIPPING WG
>> Subject: RE: [Sipping] Call Completion: In Defense of 
>> Explicit Operations
>>
>> Hi John,
>>
>> Do you think that this implementing this feature in
>> the way Adam and I were alluding to, i.e., where queuing
>> is handled by the clients but without some of the more
>> complex "queue management" feature would be acceptable
>> in those countries?
>>
>> That would allow us to have a very simple implemenation
>> without compromising the semantics of SUBSCRIBE or 
>> using a separate protocol (BFCP).
>>
>>
>>     
>>> -----Original Message-----
>>> From: Elwell, John [mailto:john.elwell@siemens.com] 
>>> Sent: Saturday, April 07, 2007 11:29
>>> To: Audet, Francois (SC100:3055); Adam Roach; SIPPING WG
>>> Subject: RE: [Sipping] Call Completion: In Defense of 
>>> Explicit Operations
>>>
>>> I know this feature is quite popular in the PSTN residential 
>>> market in various countries in Europe, particularly Germany 
>>> and also the UK to some extent. Customers seem prepared to 
>>> spend a few euro cents for the convenience it gives in a 
>>> presence-less environment. So I think the operators of those 
>>> networks want to make sure they don't lose this when they 
>>> evolve to SIP. Given that in SIP you could do things 
>>> differently and hopefully better, PSTN interworking would 
>>> appear to be the essential driver behind the TISPAN 
>>> requirements, but presumably an important driver in the eyes 
>>> of the carriers concerned. For the enterprise market I just 
>>> don't see it as important. We used to have it on PBXs right 
>>> back in the 70s and 80s and it was popular then, but 
>>> voicemail has pretty well taken over in the enterprise. I 
>>> hope this sheds some light.
>>>
>>> John
>>>
>>>       
>>>> -----Original Message-----
>>>> From: Francois Audet [mailto:audet@nortel.com]
>>>> Sent: 05 April 2007 23:18
>>>> To: Adam Roach; SIPPING WG
>>>> Subject: RE: [Sipping] Call Completion: In Defense of Explicit 
>>>> Operations
>>>>
>>>> Wouldn't it be possible to do this CCBS/CCNR stuff with a simple 
>>>> dialog package, and ditch this "queue management" mechanism?
>>>>
>>>> This seems to me to be a classic case of Engineers-gone-wild.
>>>>
>>>> I see this in the poetzl draft:
>>>>
>>>>     Completion of Calls on no Reply (CCNR) provides the 
>>>>         
>> caller with 
>>     
>>>> the
>>>>     ability to complete a requested call to a callee 
>>>>         
>>> without having to
>>>       
>>>>     make a new call attempt when the callee becomes not 
>>>>         
>> busy after 
>>     
>>>>     having initiated an activity.  The CCNR service 
>>>>         
>> description is 
>>     
>>>>     defined in ETSI EN 301 134 [6]. 
>>>>
>>>>     The call completion services provide the capability to queue 
>>>>     several CCBS/CCNR requests to the same callee on a FIFO 
>>>>         
>>> basis. It 
>>>       
>>>>     therefore requires functionalities like notifying 
>>>>         
>>> changes of queue
>>>       
>>>>     states and managing queues.  
>>>>
>>>> In other words, we are defining this really complex stuff 
>>>>         
>>> just because 
>>>       
>>>> it used to work like this in some ETSI standard for PSTN.
>>>>
>>>> Is there a better justification than that? What am I missing?
>>>>
>>>> Couldn't we handle some basic level of queueing at the endpoints 
>>>> themselves, and use a simple dialog package, and avoid all 
>>>>         
>>> this stuff 
>>>       
>>>> that creates all the complexity?
>>>>
>>>> This CCBS/CCNR feature is one of the feature that has the most 
>>>> variation
>>>>
>>>> in implementations in PSTN that I know of. To me, picking 
>>>>         
>> a really 
>>     
>>>> complicated variant and replicating it in SIP (either by 
>>>>         
>>> bastardizing 
>>>       
>>>> the protocol, or by using an entirely different protocol 
>>>>         
>>> altogether) 
>>>       
>>>> is not a good idea.
>>>> My take is
>>>> that there will be such a small uptake in implementation 
>>>>         
>>> that it will 
>>>       
>>>> effectively useful only in a few confined environments 
>>>>         
>> where the it 
>>     
>>>> can be mandated by law.
>>>>
>>>> I'd must rather have a simpler easier to implement version of the 
>>>> service.
>>>>
>>>>         
>>>>> -----Original Message-----
>>>>> From: Adam Roach [mailto:adam@nostrum.com]
>>>>> Sent: Thursday, April 05, 2007 12:10
>>>>> To: SIPPING WG
>>>>> Subject: [Sipping] Call Completion: In Defense of Explicit
>>>>>           
>>>> Operations
>>>>         
>>>>> Despite what appeared to be early agreement in the 
>>>>>           
>> working group 
>>     
>>>>> (and on the MIG mailing list) that we wanted to 
>>>>>           
>>> discourage the use 
>>>       
>>>>> of SUBSCRIBE and NOTIFY as general purpose RPC 
>>>>>           
>>> mechanisms. This is 
>>>       
>>>>> the primary objection that I have raised to 
>>>>> draft-poetzl-sipping-call-completion,
>>>>> which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
>>>>>
>>>>> In the spirit of sending text, I described an alternate set of 
>>>>> mechanisms in draft-roach-sipping-callcomp-bfcp, which 
>>>>>           
>>> performs the 
>>>       
>>>>> same task without having implied side effects from the 
>>>>>           
>>> creation of a 
>>>       
>>>>> subscription.
>>>>>
>>>>> I'll further note that the use of SUBSCRIBE to both create a 
>>>>> subscription and manipulate a call queue falls under the 
>>>>>           
>>> category of 
>>>       
>>>>> "one operation with two separate effects." We have a very poor 
>>>>> institutional memory indeed if we cannot recall why 
>>>>>           
>> operations of 
>>     
>>>>> this nature are Really Bad Ideas (cf. REFER creating a 
>>>>>           
>>> subscription; 
>>>       
>>>>> REGISTER with call processing upload; and BYE with an 
>>>>>           
>>> "Also" header 
>>>       
>>>>> field).
>>>>>
>>>>> All of this notwithstanding, in Prague, there seemed to 
>>>>>           
>>> be a curious 
>>>       
>>>>> indifference to pursuing the path laden with such Really 
>>>>>           
>>> Bad Ideas. 
>>>       
>>>>> I suspect that this indifference is a result of the 
>>>>>           
>>> arguments raised 
>>>       
>>>>> so far against the mechanism I have proposed, which I have done 
>>>>> little to refute so far (largely because I believed that 
>>>>>           
>>> the merits 
>>>       
>>>>> of a system with explicit operations were self-evident 
>>>>>           
>>> enough that 
>>>       
>>>>> the objections would seem trifling in comparison).
>>>>>
>>>>> As far as I can tell, the objections raised so far have 
>>>>>           
>>> fallen into 
>>>       
>>>>> three primary categories:
>>>>>
>>>>>    1. "The use of BFCP is troubling because, in a
>>>>>           
>>>> decomposed gateway,
>>>>         
>>>>>       the BFCP goes to the Media Gateway, while the
>>>>>           
>>>> signaling goes to
>>>>         
>>>>>       the Media Gateway Controller."
>>>>>
>>>>>       This objection, raised on one of the slides during 
>>>>>           
>>> the SIPPING
>>>       
>>>>>       meeting on March 23rd as the official reason TISPAN
>>>>>           
>>>> rejected the
>>>>         
>>>>>       approach, is based on a simple misconception.
>>>>>
>>>>>       The BFCP goes wherever the SDP says the BFCP goes. 
>>>>>           
>>> In the case 
>>>       
>>>>> of
>>>>>       a decomposed gateway, this could be the Media
>>>>>           
>>>> Gateway, the Media
>>>>         
>>>>>       Gateway Controller, or any other random
>>>>>           
>>>> network-connected server
>>>>         
>>>>>       that the Media Gateway Controller wants. I agree that it 
>>>>> probably
>>>>>       is most sensible to send it to the Media Gateway
>>>>>           
>>>> Controller, and
>>>>         
>>>>>       this is trivial to achieve.
>>>>>
>>>>>    2. "In the case of PSTN interwork, there is no way to 
>>>>>           
>>> guarantee 
>>>       
>>>>> that
>>>>>       the ISUP (or other) signaling from the PSTN side 
>>>>>           
>>> lands on the 
>>>       
>>>>> same
>>>>>       gateway that the client has a BFCP connection to."
>>>>>
>>>>>       This is true, and it is a relatively difficult
>>>>>           
>>>> problem to solve
>>>>         
>>>>>       (not impossible, though; I proposed several potential 
>>>>> solutions in
>>>>>       San Diego). It is meaningless to raise it in 
>>>>>           
>> objection to an
>>     
>>>>>       alternate proposal, since it exists in almost
>>>>>           
>>>> precisely the same
>>>>         
>>>>>       form in draft-poetzl-sipping-call-completion; and 
>>>>>           
>>> any solution
>>>       
>>>>>       that can be applied to one solution can be applied to
>>>>>           
>>>> the other.
>>>>         
>>>>>    3. "We don't want to add another protocol."
>>>>>
>>>>>       I suspect this argument is the one that is 
>>>>>           
>>> receiving the most
>>>       
>>>>>       traction, probably because most of the people 
>>>>>           
>>> involved in the
>>>       
>>>>>       discussion are not familiar with BFCP. The protocol 
>>>>>           
>>> itself is 
>>>       
>>>>> very
>>>>>       straightforward and extremely easy to implement. In fact,
>>>>>       exclusively for the purpose of answering this email (and
>>>>>       demonstrating this very point), I threw together a BFCP
>>>>>       implementation sufficient for implementation of the Call
>>>>>       Completion service described in 
>>>>> draft-roach-sipping-callcomp-bfcp.
>>>>>       It took me two hours, and compiles down to less 
>>>>>           
>> than 4 kb of
>>     
>>>>>       object code on an intel processor. It's attached to
>>>>>           
>>>> this message
>>>>         
>>>>>       to help the participants in the conversation
>>>>>           
>>>> understand just how
>>>>         
>>>>>       very little is being added to applications by this
>>>>>           
>>>> use of BFCP.
>>>>         
>>>>> So, is that it? The first two objections are simply red 
>>>>>           
>> herrings, 
>>     
>>>>> and the third is based on a misconception regarding the 
>>>>>           
>> level of 
>>     
>>>>> effort required to implement BFCP. Are we really going to 
>>>>>           
>>> down the 
>>>       
>>>>> path of doing things incorrectly over what amount to 
>>>>> misunderstandings?
>>>>>
>>>>> /a
>>>>>
>>>>>
>>>>>
>>>>> P.S. In case anyone wants a more full-featured BFCP stack, I'll 
>>>>> point to the confiance project on SourceForge, available 
>>>>>           
>>> under the 
>>>       
>>>>> Academic Freedom License, which is compatible with commercial
>>>>>           
>>>> development. See
>>>>         
>>>>> http://confiance.sourceforge.net/
>>>>>
>>>>>           
>>>> _______________________________________________
>>>> Sipping mailing list  
>>>>         
>> https://www1.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
>>>>
>>>>         


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 08 17:55:09 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HafKS-0003fu-6x; Sun, 08 Apr 2007 17:53:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HafKR-0003fj-07
	for sipping@ietf.org; Sun, 08 Apr 2007 17:53:43 -0400
Received: from rwcrmhc15.comcast.net ([216.148.227.155])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HafKP-00047N-Lu
	for sipping@ietf.org; Sun, 08 Apr 2007 17:53:42 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc15) with ESMTP
	id <20070408215340m15007g6j9e>; Sun, 8 Apr 2007 21:53:40 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l38LrdLv010844
	for <sipping@ietf.org>; Sun, 8 Apr 2007 17:53:39 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l38Lrdj0010840;
	Sun, 8 Apr 2007 17:53:39 -0400
Date: Sun, 8 Apr 2007 17:53:39 -0400
Message-Id: <200704082153.l38Lrdj0010840@dragon.ariadne.com>
To: sipping@ietf.org
In-reply-to: <46190A56.4060206@nostrum.com> (adam@nostrum.com)
Subject: Re: [Sipping] Call Completion: Various issues
References: <50B1CBA96870A34799A506B2313F26670B7D7824@ntht201e.siemenscomms.co.uk>
	<46190A56.4060206@nostrum.com>
From: Dale.Worley@comcast.net
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I've finally caught up on the Call Completion thread.  Here are a
bunch of issues that occurred to me, most of which apply to both
current proposals nearly equally.  I admit I've not mastered all of
the discussion, so I may have overlooked some answers to these issues.
I've omitted implementation details that it's clear can be solved once
the overall architecture is in order.  Issues regarding "explicit
operations" I'm putting in a separate message because they are deep
enough to require a long message.

- A good editing is in order.  I have the feeling that all authors
read the TISPAN documents first, and have been using it as a starting
point without realizing it.  E.g., the fundamental architectural
structure is not stated anywhere.  (That CC is managed by a server
that is integral to, or in tight coordination with, the destination
UA.)  Multiple terms are used for the same objects and operations,
some terms are defined without being used, and some are used without
being defined.  There is no overview up front of the complete sequence
of operations of a CC action.

- Time-outs and race conditions.  Other than that the SUBSCRIBE method
shows how a CC caller loses its place in the queue, there's not much
information on time-outs and race conditions.  E.g., in the BFCP
method, how does a calling UA that becomes non-functional lose its
place in the queue?  Once the queue controller permits a calling UA to
make a CC attempt, how is that UAs permission withdrawn if it does not
respond quickly enough?  These need to be enumerated and defined
carefully, since if they are not, implementors will make incompatible
guesses (or forget to consider them at all), and rare conditions will
cause complete feature failure.

- If setting up TCP connections for BFCP has excessive overhead, how
about encapsulating BFCP requests and responses in MESSAGE or INFO
transactions?

- The matter of correlating CC calls seems to need more work.  When
the queue manager decides to admit one particular CC retry call, how
is it to filter all incoming calls to enforce that?  It seems that the
queue manager must pass a secret token to the UA, and the UA must
attach it to the CC retry call.  (Or vice-versa.)

- Forking.  SIP forking has semantics that occur nowhere in the PSTN,
and so when a feature is imported from the PSTN, we must examine how
it interacts with forking.  It seems that the PSTN CC feature uses a
callee DN as the stored destination for future CC calls.  E.g., if
that DN has two appearances on two instruments, the CC call will ring
both of them.  But consider Cullen's example, a user that has three
instruments that are forked to by his AOR.  What is the right
destination URI for a CC call?  It may be the GRUU for the instrument
that returned busy, but it might be the AOR at the immediately
upstream forking of the call.  As it is a destination user preference
and/or an architectural feature of the destination network, only the
destination UAs/proxies can know, and we may need an explicit way to
transmit this information to the UAC.

In addition, a forked call can have several return statuses -- E.g.,
one early dialog returns busy and two return ring-no-answer.  (There
should be a separate ring-no-answer status in SIP but the status that
is seen will probably be 487 when the upstream proxy cancels the
fork.)  Only some of this information is returned to the caller.  What
sort of user interface is presented to the caller to invoke CC on such
a call?

- Is queue management really necessary?  I suspect the answer is "yes"
because the CC retry call is user-visible, even if it fails.  E.g.,
users A and B are waiting for user C to become not-busy.  C becomes
not-busy.  Without queue management, the CC feature rings both A and
B.  A's CC retry call rings C, but B's CC call returns busy.  This
will be uncommon, and isn't particularly harmful, but it's likely to
be really annoying to user B.

Dale

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 08 19:53:15 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HahAP-0004bN-3M; Sun, 08 Apr 2007 19:51:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HahAO-0004Xv-6R
	for sipping@ietf.org; Sun, 08 Apr 2007 19:51:28 -0400
Received: from sccrmhc14.comcast.net ([204.127.200.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HahAM-0006x8-V6
	for sipping@ietf.org; Sun, 08 Apr 2007 19:51:28 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (sccrmhc14) with ESMTP
	id <2007040823512601400281boe>; Sun, 8 Apr 2007 23:51:26 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l38NpQLv019395
	for <sipping@ietf.org>; Sun, 8 Apr 2007 19:51:26 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l38NpPNT019391;
	Sun, 8 Apr 2007 19:51:25 -0400
Date: Sun, 8 Apr 2007 19:51:25 -0400
Message-Id: <200704082351.l38NpPNT019391@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <46154996.50305@nostrum.com> (adam@nostrum.com)
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

There's more to this issue than meets the eye.

First, what is the objection?

The semantic model presented in RFC 3265 is fairly simple:  There is a
"resource" whose state is a time-changing document.  UACs subscribe to
the resource to track the contents of the state document.  From this
follows various features, including (1) the state is logically prior
to the subscriptions, so the presence or absence of subscriptions does
not affect the state, (2) all subscribers see the same information,
and (3) if the machinery of a subscription (at either end) becomes
disrupted, that UA can terminate the subscription and either establish
a new one (if it is the subscriber), or force the subscriber to
establish a new one (if it is the notifier), with only momentary
interruption in functionality.  (Of course, this is a simplification.)

Other than the matter of conceptual coherence of the design of SIP, we
could ignore this if it weren't for the fact that implementations
implicitly incorporate the semantic models of the features they
implement.  E.g., in the sipX code base, there is an event server
system whose purpose is to handle all the machinery of being a
notifier.  The "application" delivers to the event server revisions to
the state documents for the resources it supports, and the event
server handles notifying the appropriate subscribers.  But this
architecture demands properties (1) and (2) above.

Another possibility is that of a proxy-like service that aggregates
and caches subscriptions, so that it can be a notifier for several
subscribers to the same resource, but it needs to make only one
subscription to the "real" notifier for the resource.  This behavior
requires (2), and may require (3) as part of its strategy for
recovering from failures.

At this point I will note that most event package definitions violate
(2) in that they incorporate a sequence number *of the NOTIFYs
delivered within a subscription* into an XML document which is
otherwise common state information.  This has turned out to add
substantial complexity and difficulty to the sipX event server.  This
is another example of why maintaining simple and consistent semantic
models is important for good software.

However, there are some escapes from these limitations by using clever
design.  For instance, subscriptions are allowed to carry attributes
that filter the information seen.  Clever definitions of filters may
be used to avoid limitation (2).

Similarly, careful design of the event package may make (2) less of a
problem than appears.  For instance, if we wish to report to each of
several UAs where it appears in a queue, without revealing to each UA
where the others are in the queue, we can represent each UA's place in
the queue by a hash of the dialog identifiers of its subscription.
Generally, each UA will be able to recognize the hash that represents
it, but it will not be able to identify the UAs represented by the
other hashes.

Dale

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 01:58:40 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hamsc-0000ag-FD; Mon, 09 Apr 2007 01:57:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hamsa-0000YK-VV; Mon, 09 Apr 2007 01:57:28 -0400
Received: from fw21above.mobilkom.at ([194.48.128.75]
	helo=srvmxtreme1.mobilkom.at)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HamsZ-0008Jo-AC; Mon, 09 Apr 2007 01:57:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 9 Apr 2007 07:57:24 +0200
Message-ID: <03972E773D99AF4680D5DD84E6E2ABB00FE72786@ntxms01.ms.mobilkom.at>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Location Presence Event Package
Thread-Index: Acd6a/HMn5cHW6ybTY6l4vF+LYIT6Q==
From: "Pailer Rudolf" <r.pailer@mobilkom.at>
To: <sipping@ietf.org>, <geopriv@ietf.org>
Received-SPF: none
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Cc: 
Subject: [Sipping] Location Presence Event Package
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0932771088=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0932771088==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C77A6B.F1EBCE94"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C77A6B.F1EBCE94
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello!

I would like to notify you about the the Internet Draft "A Location
Presence Event Package for the Session Initiation Protocol (SIP)".
http://www.ietf.org/internet-drafts/draft-pailer-locpres-00.txt

The draft describes the usage of the Session Initiation Protocol (SIP)
for subscriptions and notifications of location presence. Location
presence is information about the geographical position of a user.
Subscriptions and notifications of location presence are supported by
defining an event package within the general SIP event notification
framework.

The concept of a SIP based location enabler that is the core of the
proposed draft was published on several occasions:
*) A Terminal-Based Location Service Enabler for the IP Multimedia
Subsystem, R. Pailer, S. Bessler, F. Wegscheider, IEEE Wireless
Communications and Networking Conference April 2006 (WCNC06), Las Vegas,
USA
*) Terminal-Centric Location Services for the IP Multimedia Subsystem,
J. Fabini, M. Happenhofer, R. Pailer, IEEE 63rd Vehicular Technology
Conference, May 2006, Melbourne, Australia
*) Implementing a Native IMS Location Service Enabler over a
Prototypical IMS Core Network Testbed, P. Reichl, S. Bessler, J. Fabini,
R. Pailer, J. Zeiss,The Third IEEE International Workshop on Mobile
Commerce and Wireless Services (WMCS'06) June 26, 2006, San Francisco,
USA
*) Practical Experiences with an IMS-Aware Location Service Enabler on
Top of an Experimental Open Source IMS Core Implementation, P. Reichl,
S. Bessler, J. Fabini, R. Pailer, A. Poropatich, N. Jordan, R. Huber, H.
Weisgrab, C. Brandner, I. Gojmerac, M. Ries, F. Wegscheider, Journal of
Mobile Multimedia, Rinton Press, Fall 2006
*) Lecture Notes in Geoinformation and Cartography, Location Based
Services an TeleCartography, G. Gartner, W. Cartwright, M. P. Peterson
(Eds.), Springer, 2007

I can provide above documents in PDF format, if needed.

Feedback from the IETF Working Groups GEOPRIV and SIPPING would be
appreciated very much indeed.

greetings
Rudolf


------_=_NextPart_001_01C77A6B.F1EBCE94
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">
<TITLE>Location Presence Event Package</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Hello!</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">I would like to notify you about the =
the Internet Draft &quot;A Location Presence Event Package for the =
Session Initiation Protocol (SIP)&quot;.</FONT></P>

<P><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-pailer-locpres-00.txt">=
<U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Tahoma">http://www.ietf.org/internet-drafts/draft-pailer-locpres-=
00.txt</FONT></U></A>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">The draft describes the usage of the =
Session Initiation Protocol (SIP) for subscriptions and notifications of =
location presence. Location presence is information about the =
geographical position of a user.&nbsp; Subscriptions and notifications =
of location presence are supported by defining an event package within =
the general SIP event notification framework.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">The concept of a SIP based location =
enabler that is the core of the proposed draft was published on several =
occasions:</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Tahoma">*) A Terminal-Based Location Service =
Enabler for the IP Multimedia Subsystem, R. Pailer, S. Bessler, F. =
Wegscheider, IEEE Wireless Communications and Networking Conference =
April 2006 (WCNC06), Las Vegas, USA</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">*) Terminal-Centric Location Services =
for the IP Multimedia Subsystem, J. Fabini, M. Happenhofer, R. Pailer, =
IEEE 63rd Vehicular Technology Conference, May 2006, Melbourne, =
Australia</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">*) Implementing a Native IMS Location =
Service Enabler over a Prototypical IMS Core Network Testbed, P. Reichl, =
S. Bessler, J. Fabini, R. Pailer, J. Zeiss,The Third IEEE International =
Workshop on Mobile Commerce and Wireless Services (WMCS'06) June 26, =
2006, San Francisco, USA</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">*) Practical Experiences with an =
IMS-Aware Location Service Enabler on Top of an Experimental Open Source =
IMS Core Implementation, P. Reichl, S. Bessler, J. Fabini, R. Pailer, A. =
Poropatich, N. Jordan, R. Huber, H. Weisgrab, C. Brandner, I. Gojmerac, =
M. Ries, F. Wegscheider, Journal of Mobile Multimedia, Rinton Press, =
Fall 2006</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">*) Lecture Notes in Geoinformation and =
Cartography, Location Based Services an TeleCartography, G. Gartner, W. =
Cartwright, M. P. Peterson (Eds.), Springer, 2007</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">I can provide above documents in PDF =
format, if needed.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Feedback from the IETF Working Groups =
GEOPRIV and SIPPING would be appreciated very much indeed.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">greetings</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Tahoma">Rudolf</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C77A6B.F1EBCE94--


--===============0932771088==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0932771088==--




From sipping-bounces@ietf.org Mon Apr 09 07:36:19 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Has9K-0006Dh-4I; Mon, 09 Apr 2007 07:35:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Has9I-0006DK-Vy; Mon, 09 Apr 2007 07:35:04 -0400
Received: from ebru.winwebhosting.com ([74.52.236.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Has9G-0002Eo-CG; Mon, 09 Apr 2007 07:35:04 -0400
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROSENLT40xp)
	by ebru.winwebhosting.com with esmtpa (Exim 4.63)
	(envelope-from <br@brianrosen.net>)
	id 1Has7m-0005Xg-Be; Mon, 09 Apr 2007 06:33:31 -0500
From: "Brian Rosen" <br@brianrosen.net>
To: "'Pailer Rudolf'" <r.pailer@mobilkom.at>, <sipping@ietf.org>,
	<geopriv@ietf.org>
Date: Mon, 9 Apr 2007 07:34:56 -0400
Message-ID: <050401c77a9b$1c122820$640fa8c0@cis.neustar.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <03972E773D99AF4680D5DD84E6E2ABB00FE72786@ntxms01.ms.mobilkom.at>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
thread-index: Acd6a/HMn5cHW6ybTY6l4vF+LYIT6QAKy53g
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4bb0e9e1ca9d18125bc841b2d8d77e24
Cc: 
Subject: [Sipping] RE: [Geopriv] Location Presence Event Package
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0491369725=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0491369725==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0505_01C77A79.95008820"

This is a multi-part message in MIME format.

------=_NextPart_000_0505_01C77A79.95008820
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I've read this, and I don't really understand why real presence (with the
filter package) doesn't provide the same service.

Can you give an example where presence+filter is significantly different
from this package, with the filter inclusion?   It seems to me that you get
roughly the same number of messages, with roughly the same content.

 

Brian

 

  _____  

From: Pailer Rudolf [mailto:r.pailer@mobilkom.at] 
Sent: Monday, April 09, 2007 1:57 AM
To: sipping@ietf.org; geopriv@ietf.org
Subject: [Geopriv] Location Presence Event Package

 

Hello! 

I would like to notify you about the the Internet Draft "A Location Presence
Event Package for the Session Initiation Protocol (SIP)".

 <http://www.ietf.org/internet-drafts/draft-pailer-locpres-00.txt>
http://www.ietf.org/internet-drafts/draft-pailer-locpres-00.txt 

The draft describes the usage of the Session Initiation Protocol (SIP) for
subscriptions and notifications of location presence. Location presence is
information about the geographical position of a user.  Subscriptions and
notifications of location presence are supported by defining an event
package within the general SIP event notification framework.

The concept of a SIP based location enabler that is the core of the proposed
draft was published on several occasions: 
*) A Terminal-Based Location Service Enabler for the IP Multimedia
Subsystem, R. Pailer, S. Bessler, F. Wegscheider, IEEE Wireless
Communications and Networking Conference April 2006 (WCNC06), Las Vegas, USA

*) Terminal-Centric Location Services for the IP Multimedia Subsystem, J.
Fabini, M. Happenhofer, R. Pailer, IEEE 63rd Vehicular Technology
Conference, May 2006, Melbourne, Australia

*) Implementing a Native IMS Location Service Enabler over a Prototypical
IMS Core Network Testbed, P. Reichl, S. Bessler, J. Fabini, R. Pailer, J.
Zeiss,The Third IEEE International Workshop on Mobile Commerce and Wireless
Services (WMCS'06) June 26, 2006, San Francisco, USA

*) Practical Experiences with an IMS-Aware Location Service Enabler on Top
of an Experimental Open Source IMS Core Implementation, P. Reichl, S.
Bessler, J. Fabini, R. Pailer, A. Poropatich, N. Jordan, R. Huber, H.
Weisgrab, C. Brandner, I. Gojmerac, M. Ries, F. Wegscheider, Journal of
Mobile Multimedia, Rinton Press, Fall 2006

*) Lecture Notes in Geoinformation and Cartography, Location Based Services
an TeleCartography, G. Gartner, W. Cartwright, M. P. Peterson (Eds.),
Springer, 2007

I can provide above documents in PDF format, if needed. 

Feedback from the IETF Working Groups GEOPRIV and SIPPING would be
appreciated very much indeed. 

greetings 
Rudolf 


------=_NextPart_000_0505_01C77A79.95008820
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Location Presence Event Package</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I&#8217;ve read this, and I =
don&#8217;t
really understand why real presence (with the filter package) =
doesn&#8217;t
provide the same service.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Can you give an example where
presence+filter is significantly different from this package, with the =
filter
inclusion?&nbsp; &nbsp;It seems to me that you get roughly the same =
number of
messages, with roughly the same content.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Brian<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Pailer Rudolf
[mailto:r.pailer@mobilkom.at] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, April 09, =
2007 1:57
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> sipping@ietf.org;
geopriv@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Geopriv] =
Location
Presence Event Package</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>Hello!</span></font>
<o:p></o:p></p>

<p><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>I
would like to notify you about the the Internet Draft &quot;A Location =
Presence
Event Package for the Session Initiation Protocol =
(SIP)&quot;.</span></font><o:p></o:p></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'><a
href=3D"http://www.ietf.org/internet-drafts/draft-pailer-locpres-00.txt">=
<font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>http://www.ietf.org/interne=
t-drafts/draft-pailer-locpres-00.txt</span></font></a>
<o:p></o:p></span></font></p>

<p><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>The
draft describes the usage of the Session Initiation Protocol (SIP) for
subscriptions and notifications of location presence. Location presence =
is
information about the geographical position of a user.&nbsp; =
Subscriptions and
notifications of location presence are supported by defining an event =
package
within the general SIP event notification =
framework.</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>The
concept of a SIP based location enabler that is the core of the proposed =
draft
was published on several occasions:</span></font> <br>
<font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>*) A
Terminal-Based Location Service Enabler for the IP Multimedia Subsystem, =
R.
Pailer, S. Bessler, F. Wegscheider, IEEE Wireless Communications and =
Networking
Conference April 2006 (WCNC06), Las Vegas, =
USA</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>*)
Terminal-Centric Location Services for the IP Multimedia Subsystem, J. =
Fabini,
M. Happenhofer, R. Pailer, IEEE 63rd Vehicular Technology Conference, =
May 2006,
Melbourne, Australia</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>*)
Implementing a Native IMS Location Service Enabler over a Prototypical =
IMS Core
Network Testbed, P. Reichl, S. Bessler, J. Fabini, R. Pailer, J. =
Zeiss,The
Third IEEE International Workshop on Mobile Commerce and Wireless =
Services
(WMCS'06) June 26, 2006, San Francisco, USA</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>*)
Practical Experiences with an IMS-Aware Location Service Enabler on Top =
of an
Experimental Open Source IMS Core Implementation, P. Reichl, S. Bessler, =
J.
Fabini, R. Pailer, A. Poropatich, N. Jordan, R. Huber, H. Weisgrab, C.
Brandner, I. Gojmerac, M. Ries, F. Wegscheider, Journal of Mobile =
Multimedia,
Rinton Press, Fall 2006</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>*)
Lecture Notes in Geoinformation and Cartography, Location Based Services =
an
TeleCartography, G. Gartner, W. Cartwright, M. P. Peterson (Eds.), =
Springer,
2007</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>I
can provide above documents in PDF format, if needed.</span></font> =
<o:p></o:p></p>

<p><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>Feedback
from the IETF Working Groups GEOPRIV and SIPPING would be appreciated =
very much
indeed.</span></font> <o:p></o:p></p>

<p><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>greetings</span></font>
<br>
<font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>Rudolf</span></font>
<o:p></o:p></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_0505_01C77A79.95008820--



--===============0491369725==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0491369725==--





From sipping-bounces@ietf.org Mon Apr 09 08:55:53 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HatP7-00066k-Fg; Mon, 09 Apr 2007 08:55:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HatP5-00064i-EI
	for sipping@ietf.org; Mon, 09 Apr 2007 08:55:27 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HatP2-0008UI-1j
	for sipping@ietf.org; Mon, 09 Apr 2007 08:55:27 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 09 Apr 2007 08:55:23 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l39CtNbu026999; 
	Mon, 9 Apr 2007 08:55:23 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l39CtFGj029327; 
	Mon, 9 Apr 2007 12:55:23 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 08:55:15 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 08:55:14 -0400
Message-ID: <461A37B2.1040502@cisco.com>
Date: Mon, 09 Apr 2007 08:55:14 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <50B1CBA96870A34799A506B2313F26670B7D7825@ntht201e.siemenscomms.co.uk>
	<AE1496AB-EC74-4C7B-88B0-99129CF193CA@cs.columbia.edu>
In-Reply-To: <AE1496AB-EC74-4C7B-88B0-99129CF193CA@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Apr 2007 12:55:14.0700 (UTC)
	FILETIME=[511774C0:01C77AA6]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3368; t=1176123323;
	x=1176987323; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defense=20of=
	20Explicit=20Operations |Sender:=20
	|To:=20Henning=20Schulzrinne=20<hgs@cs.columbia.edu>;
	bh=nQvtpZk0hNMxutWluYlvKt5cPutx/iZJwA4fT04TNDs=;
	b=S5dbJkohMid6Pp0tHkcIrZiQ7CizLAAHFO0cGIN0Z3k+aVmJxYfoOyeTpaKE//ZSQXe+Vb3d
	w1+sQEdusCkLZ7lc+ua9GyQyR9zoKnBxmtWcIY4nJk3zUYOJDtiNyNLo;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: SIPPING WG <sipping@ietf.org>, Francois Audet <audet@nortel.com>, "Elwell,
	John" <john.elwell@siemens.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Henning,

I really like the kind of service you are suggesting. I'd like to see it 
be available. Its the kind of thing that can make a sip-based service be 
better than a traditional service.

Of course it is not an *exact* replacement for the traditional call 
completion service(s), or even a very close one. Whether that is 
important will depend on the customers involved. For someone buying a 
replacement system, the need to avoid retraining a bunch of users may be 
important. (But probably not as important as the people making the 
buying decision think it is.)

My impression is that a key requirement is for interop with a pstn 
service that contains an implementation with queuing. That constrains 
the set of solutions.

IMO the big but unconsidered issue is providing some reasonable user 
experience for the caller regardless of the capabilities of the callee. 
No matter what is decided here, not all callees will support it. As much 
as IMS might like to think they will have a closed system, they won't. 
Calls will be made to callees on the PSTN in different countries that 
follow various standards, to cell phones from various providers, to an 
assortment of PBXs, gateways to sip systems, to Skype, etc. If I have 
trouble getting through with a call, and want help completing it, I want 
that help regardless of who I am trying to call. A really simple 
solution, such as one that simply repeatedly redials, will be better 
than a queuing system if it works for more callees. A system that 
separates caller support from callee support, and is capable of using 
any of a variety of techniques based on what the callee supports, would 
be even better.

	Paul

Henning Schulzrinne wrote:
> John,
> 
> I can't say I fully understand all the requirements, but here's what I 
> had in mind:
> 
> Each UA subscribes to the call log for its AOR, presumably via 
> incremental updates and maybe with some time limit ("I'm just back from 
> vacation. Only give me calls that arrived earlier today, not three weeks 
> ago."). Each time-stamped call is marked with its completion status, 
> such as 'no response', 'busy', 'outgoing', etc., just like you'd find on 
> most cell phones today. When a UA becomes available again, e.g., after 
> busy or being out of the office, the UA can easily reconstruct the 
> "queue" of missed calls and dial any one of them, in whatever order it 
> chooses. Since it has the complete list, it can easily determine whether 
> some other UA for the same AOR has already returned a call. There 
> doesn't seem to be a need to manage the queue on the proxy.
> 
> Being able to return calls from other devices seems to be a nice 
> feature; naturally, web call logs do most of that today, but they are a 
> bit harder to manage.
> 
> Henning
> 
> On Apr 7, 2007, at 3:35 PM, Elwell, John wrote:
> 
>> Henning,
>>
>> I am not sure what you have in mind or how it caters for the so-called
>> queueing requirement from TISPAN.
>>
>> John
>>
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.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
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 08:56:07 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HatPj-0006LW-OC; Mon, 09 Apr 2007 08:56:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HatPi-0006Hg-Bg
	for sipping@ietf.org; Mon, 09 Apr 2007 08:56:06 -0400
Received: from 18-116.252-81.static-ip.oleane.fr ([81.252.116.18]
	helo=mail.softdom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HatPg-00008W-VU
	for sipping@ietf.org; Mon, 09 Apr 2007 08:56:06 -0400
Received: from ([156.154.16.145])
	by mail.softdom.com (Merak 8.9.1) with SMTP id OQO01615
	for <sipping@ietf.org>; Mon, 09 Apr 2007 14:57:15 +0200
Date: Mon, 09 Apr 2007 14:57:15 +0200
From: Francois.plagnard <francois.plagnard@netbricks.net>
To: <sipping@ietf.org>
Message-Id: <914978599@mail.softdom.com>
Content-Type: text/plain; charset="utf-8"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: [Sipping] Re: Sipping Digest, Vol 36, Issue 23
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I'm out office until April 15th.

Best regards,

Francois Plagnard.


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 09:07:02 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hata9-0004Ly-Fe; Mon, 09 Apr 2007 09:06:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hata8-0004Lt-1x
	for sipping@ietf.org; Mon, 09 Apr 2007 09:06:52 -0400
Received: from jalapeno.cc.columbia.edu ([128.59.29.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hata6-00025y-Qk
	for sipping@ietf.org; Mon, 09 Apr 2007 09:06:52 -0400
Received: from [192.168.0.41] (pool-70-21-193-163.nwrk.east.verizon.net
	[70.21.193.163]) (user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id
	l39D6Z0H018878
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 9 Apr 2007 09:06:40 -0400 (EDT)
In-Reply-To: <461A37B2.1040502@cisco.com>
References: <50B1CBA96870A34799A506B2313F26670B7D7825@ntht201e.siemenscomms.co.uk>
	<AE1496AB-EC74-4C7B-88B0-99129CF193CA@cs.columbia.edu>
	<461A37B2.1040502@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6429ADF8-A408-4AFA-B1AC-00854CFB3E80@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Mon, 9 Apr 2007 09:06:43 -0400
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: SIPPING WG <sipping@ietf.org>, Francois Audet <audet@nortel.com>, "Elwell,
	John" <john.elwell@siemens.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 9, 2007, at 8:55 AM, Paul Kyzivat wrote:

> Henning,
>
> Of course it is not an *exact* replacement for the traditional call  
> completion service(s), or even a very close one. Whether that is  
> important will depend on the customers involved. For someone buying  
> a replacement system, the need to avoid retraining a bunch of users  
> may be important. (But probably not as important as the people  
> making the buying decision think it is.)

Ignoring the part of where this is implemented, I'm curious (simply  
because I have never experienced the original service...) as to how  
the user experience would differ. I'm envisioning an automated mode  
that emulates the call-back style mode CCNR seems to imply, not  
necessarily an explicit call log listing with "click to dial"  
functionality.

In addition to the basic call log, there would need to be an  
indicator (caller preference?) to be called back, which can be easily  
reflected into the call log.

A separable issue is whether a "network"-based solution will lead to  
more widespread availability.

>
> My impression is that a key requirement is for interop with a pstn  
> service that contains an implementation with queuing. That  
> constrains the set of solutions.
>
> IMO the big but unconsidered issue is providing some reasonable  
> user experience for the caller regardless of the capabilities of  
> the callee. No matter what is decided here, not all callees will  
> support it. As much as IMS might like to think they will have a  
> closed system, they won't. Calls will be made to callees on the  
> PSTN in different countries that follow various standards, to cell  
> phones from various providers, to an assortment of PBXs, gateways  
> to sip systems, to Skype, etc. If I have trouble getting through  
> with a call, and want help completing it, I want that help  
> regardless of who I am trying to call. A really simple solution,  
> such as one that simply repeatedly redials, will be better than a  
> queuing system if it works for more callees. A system that  
> separates caller support from callee support, and is capable of  
> using any of a variety of techniques based on what the callee  
> supports, would be even better.
>
> 	Paul
>
> H

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 09:35:46 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hau1t-0003R2-Cc; Mon, 09 Apr 2007 09:35:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hau1r-0003OG-IC; Mon, 09 Apr 2007 09:35:31 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hau1q-0006u9-6S; Mon, 09 Apr 2007 09:35:31 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 09 Apr 2007 09:35:31 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l39DZTop013358; 
	Mon, 9 Apr 2007 09:35:29 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l39DZIH1010597; 
	Mon, 9 Apr 2007 13:35:21 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 09:35:18 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 09:35:18 -0400
Message-ID: <461A4115.6000201@cisco.com>
Date: Mon, 09 Apr 2007 09:35:17 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Brian Rosen <br@brianrosen.net>
Subject: Re: [Sipping] RE: [Geopriv] Location Presence Event Package
References: <050401c77a9b$1c122820$640fa8c0@cis.neustar.com>
In-Reply-To: <050401c77a9b$1c122820$640fa8c0@cis.neustar.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 09 Apr 2007 13:35:18.0258 (UTC)
	FILETIME=[E9B94D20:01C77AAB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4057; t=1176125730;
	x=1176989730; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20RE=3A=20[Geopriv]=20Location=20Presence=2
	0Event=20Package |Sender:=20
	|To:=20Brian=20Rosen=20<br@brianrosen.net>;
	bh=5FmAT+2GMCqtZ42xQw6Jebo7FpiR4BUWQGtX7O7Ll/8=;
	b=d/is+SlSBwme9clrs0e00r3D7aSl1qjDvW0RwRs4d2W00ApeQ1hfJhMcnZetxk0TZ7jbPlZC
	uBQjoK6Xm1lT0WXdht2KeM68u8B6VNqP0Kkt+mobhUjotqjU0gIIkkzK;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: geopriv@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Like Brian I think this seems so close to existing presence that you 
need to work harder to make the case for something different, and to 
show how the two packages would be coordinated.

It appears to me that a major goal you have is to avoid sending out 
messages as a result of movement when there are no watchers that are 
interested in that movement. While I can see how that could be helpful 
in some cases, it needs to be reconciled with the resulting need to 
manage subscriptions from what could be a large number of watchers.

In any case, I think what you suggest could be achieved by introducing 
some special filters for geoloc information into standard presence. At 
least that would work when there is no separate presence aggregator.

	Paul

Brian Rosen wrote:
> I’ve read this, and I don’t really understand why real presence (with 
> the filter package) doesn’t provide the same service.
> 
> Can you give an example where presence+filter is significantly different 
> from this package, with the filter inclusion?   It seems to me that you 
> get roughly the same number of messages, with roughly the same content.
> 
>  
> 
> Brian
> 
>  
> 
> ------------------------------------------------------------------------
> 
> *From:* Pailer Rudolf [mailto:r.pailer@mobilkom.at]
> *Sent:* Monday, April 09, 2007 1:57 AM
> *To:* sipping@ietf.org; geopriv@ietf.org
> *Subject:* [Geopriv] Location Presence Event Package
> 
>  
> 
> Hello!
> 
> I would like to notify you about the the Internet Draft "A Location 
> Presence Event Package for the Session Initiation Protocol (SIP)".
> 
> http://www.ietf.org/internet-drafts/draft-pailer-locpres-00.txt
> 
> The draft describes the usage of the Session Initiation Protocol (SIP) 
> for subscriptions and notifications of location presence. Location 
> presence is information about the geographical position of a user.  
> Subscriptions and notifications of location presence are supported by 
> defining an event package within the general SIP event notification 
> framework.
> 
> The concept of a SIP based location enabler that is the core of the 
> proposed draft was published on several occasions:
> *) A Terminal-Based Location Service Enabler for the IP Multimedia 
> Subsystem, R. Pailer, S. Bessler, F. Wegscheider, IEEE Wireless 
> Communications and Networking Conference April 2006 (WCNC06), Las Vegas, USA
> 
> *) Terminal-Centric Location Services for the IP Multimedia Subsystem, 
> J. Fabini, M. Happenhofer, R. Pailer, IEEE 63rd Vehicular Technology 
> Conference, May 2006, Melbourne, Australia
> 
> *) Implementing a Native IMS Location Service Enabler over a 
> Prototypical IMS Core Network Testbed, P. Reichl, S. Bessler, J. Fabini, 
> R. Pailer, J. Zeiss,The Third IEEE International Workshop on Mobile 
> Commerce and Wireless Services (WMCS'06) June 26, 2006, San Francisco, USA
> 
> *) Practical Experiences with an IMS-Aware Location Service Enabler on 
> Top of an Experimental Open Source IMS Core Implementation, P. Reichl, 
> S. Bessler, J. Fabini, R. Pailer, A. Poropatich, N. Jordan, R. Huber, H. 
> Weisgrab, C. Brandner, I. Gojmerac, M. Ries, F. Wegscheider, Journal of 
> Mobile Multimedia, Rinton Press, Fall 2006
> 
> *) Lecture Notes in Geoinformation and Cartography, Location Based 
> Services an TeleCartography, G. Gartner, W. Cartwright, M. P. Peterson 
> (Eds.), Springer, 2007
> 
> I can provide above documents in PDF format, if needed.
> 
> Feedback from the IETF Working Groups GEOPRIV and SIPPING would be 
> appreciated very much indeed.
> 
> greetings
> Rudolf
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Sipping mailing list  https://www1.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

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 09:45:17 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HauBJ-0002QU-4k; Mon, 09 Apr 2007 09:45:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HauBH-0002Lj-Kc
	for sipping@ietf.org; Mon, 09 Apr 2007 09:45:15 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HauBG-0008JN-8c
	for sipping@ietf.org; Mon, 09 Apr 2007 09:45:15 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 09 Apr 2007 09:45:15 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l39DjEu4010768; 
	Mon, 9 Apr 2007 09:45:14 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l39Dj1lM025872; 
	Mon, 9 Apr 2007 13:45:13 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 09:45:05 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 09:45:04 -0400
Message-ID: <461A4360.7070607@cisco.com>
Date: Mon, 09 Apr 2007 09:45:04 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <50B1CBA96870A34799A506B2313F26670B7D7825@ntht201e.siemenscomms.co.uk>
	<AE1496AB-EC74-4C7B-88B0-99129CF193CA@cs.columbia.edu>
	<461A37B2.1040502@cisco.com>
	<6429ADF8-A408-4AFA-B1AC-00854CFB3E80@cs.columbia.edu>
In-Reply-To: <6429ADF8-A408-4AFA-B1AC-00854CFB3E80@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Apr 2007 13:45:04.0950 (UTC)
	FILETIME=[476B6560:01C77AAD]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3084; t=1176126314;
	x=1176990314; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defense=20of=
	20Explicit=20Operations |Sender:=20
	|To:=20Henning=20Schulzrinne=20<hgs@cs.columbia.edu>;
	bh=qQ1a4x9aCZ3ppTka8lekGqtYF2GbbUwWiW+qHr1fJRM=;
	b=SpV59I/TzcEs3vzhiy+xSBz3EPuIVfxf/gPdxbSnmLcdDfbbRF99arUdsjZA4kDgHWMAg7N0
	BJiEQ+OvTb6di37EomwMdHa3EFzAYSJ3qaGLClWJioHHL44Glmr/npGd;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: SIPPING WG <sipping@ietf.org>, Francois Audet <audet@nortel.com>, "Elwell,
	John" <john.elwell@siemens.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Henning Schulzrinne wrote:
> 
> On Apr 9, 2007, at 8:55 AM, Paul Kyzivat wrote:
> 
>> Henning,
>>
>> Of course it is not an *exact* replacement for the traditional call 
>> completion service(s), or even a very close one. Whether that is 
>> important will depend on the customers involved. For someone buying a 
>> replacement system, the need to avoid retraining a bunch of users may 
>> be important. (But probably not as important as the people making the 
>> buying decision think it is.)
> 
> Ignoring the part of where this is implemented, I'm curious (simply 
> because I have never experienced the original service...) as to how the 
> user experience would differ. I'm envisioning an automated mode that 
> emulates the call-back style mode CCNR seems to imply, not necessarily 
> an explicit call log listing with "click to dial" functionality.

If I understood what you were proposing, it would be the *callee* that 
would initiate the callback, based on the call log, whereas CCNR has the 
*caller* initiate the callback.

There are several differences in user experience here:
- with ccnr, the caller is alerted first. If not present,
   the attempt won't occur. With a callee initiation based
   on the call log, the callback will probably happen without
   knowledge of availability of the caller. So it may go
   unanswered.
- if the caller has restrictions on who he can call,
   the callback attempt may be blocked. This wouldn't
   happen if the caller did the initiation.
- the caller probably gets the bill for the call.

	Paul

> In addition to the basic call log, there would need to be an indicator 
> (caller preference?) to be called back, which can be easily reflected 
> into the call log.
> 
> A separable issue is whether a "network"-based solution will lead to 
> more widespread availability.
> 
>>
>> My impression is that a key requirement is for interop with a pstn 
>> service that contains an implementation with queuing. That constrains 
>> the set of solutions.
>>
>> IMO the big but unconsidered issue is providing some reasonable user 
>> experience for the caller regardless of the capabilities of the 
>> callee. No matter what is decided here, not all callees will support 
>> it. As much as IMS might like to think they will have a closed system, 
>> they won't. Calls will be made to callees on the PSTN in different 
>> countries that follow various standards, to cell phones from various 
>> providers, to an assortment of PBXs, gateways to sip systems, to 
>> Skype, etc. If I have trouble getting through with a call, and want 
>> help completing it, I want that help regardless of who I am trying to 
>> call. A really simple solution, such as one that simply repeatedly 
>> redials, will be better than a queuing system if it works for more 
>> callees. A system that separates caller support from callee support, 
>> and is capable of using any of a variety of techniques based on what 
>> the callee supports, would be even better.
>>
>>     Paul
>>
>> H
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 10:23:52 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Haum1-00045a-C4; Mon, 09 Apr 2007 10:23:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Haum0-00042U-31
	for sipping@ietf.org; Mon, 09 Apr 2007 10:23:12 -0400
Received: from jalapeno.cc.columbia.edu ([128.59.29.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Haulx-00087g-Rl
	for sipping@ietf.org; Mon, 09 Apr 2007 10:23:12 -0400
Received: from [128.59.23.102] (macmini1.cs.columbia.edu [128.59.23.102])
	(user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id
	l39EMsKK007441
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 9 Apr 2007 10:22:58 -0400 (EDT)
In-Reply-To: <461A4360.7070607@cisco.com>
References: <50B1CBA96870A34799A506B2313F26670B7D7825@ntht201e.siemenscomms.co.uk>
	<AE1496AB-EC74-4C7B-88B0-99129CF193CA@cs.columbia.edu>
	<461A37B2.1040502@cisco.com>
	<6429ADF8-A408-4AFA-B1AC-00854CFB3E80@cs.columbia.edu>
	<461A4360.7070607@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BEB8A01D-D216-4257-AD73-C38D2AF09D62@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Mon, 9 Apr 2007 10:23:52 -0400
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: SIPPING WG <sipping@ietf.org>, Francois Audet <audet@nortel.com>, "Elwell,
	John" <john.elwell@siemens.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 9, 2007, at 9:45 AM, Paul Kyzivat wrote:

>
>
> Henning Schulzrinne wrote:
>> On Apr 9, 2007, at 8:55 AM, Paul Kyzivat wrote:
>>> Henning,
>>>
>>> Of course it is not an *exact* replacement for the traditional  
>>> call completion service(s), or even a very close one. Whether  
>>> that is important will depend on the customers involved. For  
>>> someone buying a replacement system, the need to avoid retraining  
>>> a bunch of users may be important. (But probably not as important  
>>> as the people making the buying decision think it is.)
>> Ignoring the part of where this is implemented, I'm curious  
>> (simply because I have never experienced the original service...)  
>> as to how the user experience would differ. I'm envisioning an  
>> automated mode that emulates the call-back style mode CCNR seems  
>> to imply, not necessarily an explicit call log listing with "click  
>> to dial" functionality.
>
> If I understood what you were proposing, it would be the *callee*  
> that would initiate the callback, based on the call log, whereas  
> CCNR has the *caller* initiate the callback.
>
> There are several differences in user experience here:
> - with ccnr, the caller is alerted first. If not present,
>   the attempt won't occur. With a callee initiation based
>   on the call log, the callback will probably happen without
>   knowledge of availability of the caller. So it may go
>   unanswered.

This sounds like presence, possibly staged in some "queued" order.  
Does the caller get to choose "dial now or abandon"?



> - if the caller has restrictions on who he can call,
>   the callback attempt may be blocked. This wouldn't
>   happen if the caller did the initiation.
> - the caller probably gets the bill for the call.


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 11:18:40 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HavdF-0001je-3f; Mon, 09 Apr 2007 11:18:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HavdD-0001jZ-Nz
	for sipping@ietf.org; Mon, 09 Apr 2007 11:18:11 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HavdB-0003TC-Ef
	for sipping@ietf.org; Mon, 09 Apr 2007 11:18:11 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 09 Apr 2007 11:18:09 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l39FI7ND027800; 
	Mon, 9 Apr 2007 11:18:07 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l39FHjH9013584; 
	Mon, 9 Apr 2007 15:18:07 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 11:18:03 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 11:18:02 -0400
Message-ID: <461A592C.4010908@cisco.com>
Date: Mon, 09 Apr 2007 11:18:04 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <50B1CBA96870A34799A506B2313F26670B7D7825@ntht201e.siemenscomms.co.uk>
	<AE1496AB-EC74-4C7B-88B0-99129CF193CA@cs.columbia.edu>
	<461A37B2.1040502@cisco.com>
	<6429ADF8-A408-4AFA-B1AC-00854CFB3E80@cs.columbia.edu>
	<461A4360.7070607@cisco.com>
	<BEB8A01D-D216-4257-AD73-C38D2AF09D62@cs.columbia.edu>
In-Reply-To: <BEB8A01D-D216-4257-AD73-C38D2AF09D62@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Apr 2007 15:18:02.0930 (UTC)
	FILETIME=[44279920:01C77ABA]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2063; t=1176131887;
	x=1176995887; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defense=20of=
	20Explicit=20Operations |Sender:=20
	|To:=20Henning=20Schulzrinne=20<hgs@cs.columbia.edu>;
	bh=Zk9x1fb6kEm8IlHYORmbsX8T4WFf+O1p9qM6PskUgqk=;
	b=RnIzFFH9U87xhxQfnKve43azqIhW5kdAbJQWxl3lEZ7ceMD7T76YN1fe1asL6mikKdH9KGLT
	vbtpE5C+4ZLW/PfCMsvHwbubZACxZuaI3ZYccy08XT+4RlSy0Mw0X5MP;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: SIPPING WG <sipping@ietf.org>, Francois Audet <audet@nortel.com>, "Elwell,
	John" <john.elwell@siemens.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Henning Schulzrinne wrote:
> 
> On Apr 9, 2007, at 9:45 AM, Paul Kyzivat wrote:
> 
>>
>>
>> Henning Schulzrinne wrote:
>>> On Apr 9, 2007, at 8:55 AM, Paul Kyzivat wrote:
>>>> Henning,
>>>>
>>>> Of course it is not an *exact* replacement for the traditional call 
>>>> completion service(s), or even a very close one. Whether that is 
>>>> important will depend on the customers involved. For someone buying 
>>>> a replacement system, the need to avoid retraining a bunch of users 
>>>> may be important. (But probably not as important as the people 
>>>> making the buying decision think it is.)
>>> Ignoring the part of where this is implemented, I'm curious (simply 
>>> because I have never experienced the original service...) as to how 
>>> the user experience would differ. I'm envisioning an automated mode 
>>> that emulates the call-back style mode CCNR seems to imply, not 
>>> necessarily an explicit call log listing with "click to dial" 
>>> functionality.
>>
>> If I understood what you were proposing, it would be the *callee* that 
>> would initiate the callback, based on the call log, whereas CCNR has 
>> the *caller* initiate the callback.
>>
>> There are several differences in user experience here:
>> - with ccnr, the caller is alerted first. If not present,
>>   the attempt won't occur. With a callee initiation based
>>   on the call log, the callback will probably happen without
>>   knowledge of availability of the caller. So it may go
>>   unanswered.
> 
> This sounds like presence, possibly staged in some "queued" order. Does 
> the caller get to choose "dial now or abandon"?

There is a small aspect of presence involved, in a very loose sense.

What happens is that when the target becomes free the top caller in the 
queue gets alerted. If that is answered quickly enough, another call 
attempt is made. If not, then I think that caller is removed from the 
queue - hence an abandon.

At least that is how I remember the telcordia version of the feature 
working.

	Paul

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 11:30:52 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Havoy-0001Ai-WC; Mon, 09 Apr 2007 11:30:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Havox-0001AX-0x
	for sipping@ietf.org; Mon, 09 Apr 2007 11:30:19 -0400
Received: from jalapeno.cc.columbia.edu ([128.59.29.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Havos-0005ll-LH
	for sipping@ietf.org; Mon, 09 Apr 2007 11:30:19 -0400
Received: from [160.39.252.245] (dyn-160-39-252-245.dyn.columbia.edu
	[160.39.252.245]) (user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id
	l39FTqAm025784
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 9 Apr 2007 11:29:57 -0400 (EDT)
In-Reply-To: <461A592C.4010908@cisco.com>
References: <50B1CBA96870A34799A506B2313F26670B7D7825@ntht201e.siemenscomms.co.uk>
	<AE1496AB-EC74-4C7B-88B0-99129CF193CA@cs.columbia.edu>
	<461A37B2.1040502@cisco.com>
	<6429ADF8-A408-4AFA-B1AC-00854CFB3E80@cs.columbia.edu>
	<461A4360.7070607@cisco.com>
	<BEB8A01D-D216-4257-AD73-C38D2AF09D62@cs.columbia.edu>
	<461A592C.4010908@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7DE9E082-8C70-48C7-AF45-AB3EBC7E6385@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Mon, 9 Apr 2007 12:29:57 -0400
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: SIPPING WG <sipping@ietf.org>, Francois Audet <audet@nortel.com>, "Elwell,
	John" <john.elwell@siemens.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

>
> There is a small aspect of presence involved, in a very loose sense.
>
> What happens is that when the target becomes free the top caller in  
> the queue gets alerted. If that is answered quickly enough, another  
> call attempt is made. If not, then I think that caller is removed  
> from the queue - hence an abandon.
>

This sounds like regular presence, except that NOTIFYs are staged in  
queue order and have a short validity period. If no call arrives, the  
proxy just sends the next NOTIFY.

> At least that is how I remember the telcordia version of the  
> feature working.
>
> 	Paul


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 11:30:52 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HavpA-0001OX-58; Mon, 09 Apr 2007 11:30:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Havp9-0001Ma-4H
	for sipping@ietf.org; Mon, 09 Apr 2007 11:30:31 -0400
Received: from 18-116.252-81.static-ip.oleane.fr ([81.252.116.18]
	helo=mail.softdom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Havp7-0005nN-OM
	for sipping@ietf.org; Mon, 09 Apr 2007 11:30:31 -0400
Received: from ([156.154.16.145])
	by mail.softdom.com (Merak 8.9.1) with SMTP id OTO93843
	for <sipping@ietf.org>; Mon, 09 Apr 2007 17:31:43 +0200
Date: Mon, 09 Apr 2007 17:31:43 +0200
From: Francois.plagnard <francois.plagnard@netbricks.net>
To: <sipping@ietf.org>
Message-Id: <914983925@mail.softdom.com>
Content-Type: text/plain; charset="utf-8"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: [Sipping] Re: Sipping Digest, Vol 36, Issue 24
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I'm out office until April 15th.

Best regards,

Francois Plagnard.


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 11:42:13 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HavzS-0007Vm-5A; Mon, 09 Apr 2007 11:41:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HavzR-0007Vd-00
	for sipping@ietf.org; Mon, 09 Apr 2007 11:41:09 -0400
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HavzO-0007Yl-DW
	for sipping@ietf.org; Mon, 09 Apr 2007 11:41:08 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l39FeiJ03226; Mon, 9 Apr 2007 15:40:44 GMT
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
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Mon, 9 Apr 2007 10:40:42 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0FEFD424@zrc2hxm0.corp.nortel.com>
In-Reply-To: <46190A56.4060206@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
thread-index: Acd585SysIAKXuANQeqEBdjX6UfxRQAyc2Yg
References: <50B1CBA96870A34799A506B2313F26670B7D7824@ntht201e.siemenscomms.co.uk>
	<46190A56.4060206@nostrum.com>
From: "Francois Audet" <audet@nortel.com>
To: "Adam Roach" <adam@nostrum.com>, "Elwell, John" <john.elwell@siemens.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 75ac86d24bd0a3cd8a26e327ae61143e
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Thanks Adam. That's exactly my feeling.

=20

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]=20
> Sent: Sunday, April 08, 2007 08:29
> To: Elwell, John
> Cc: Audet, Francois (SC100:3055); SIPPING WG
> Subject: Re: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
> Elwell, John wrote:
> > Francois,
> >
> > Clearly the TISPAN people want more than that.
> >
> >  =20
>=20
> I think we understand that they *want* it to behave that way.=20
> What I believe is getting lost is the cost imposed by the=20
> requirements as written. In particular, there appears to be=20
> no dialog, only a unidirectional declaration of requirements=20
> without listening for any feedback.
>=20
> To use an analogy: let's imagine that I wanted to buy a car.=20
> I could write down the list of features I wanted and then=20
> send a representative to the car dealer with that list. Now,=20
> imagine if the car dealer explained that they have something=20
> on the lot that has all of my features for $25,000, *except*=20
> it's not a stick shift -- and that, in fact, a model with=20
> those features *and* a stick shift would be such an odd=20
> special order that it would add $400,000 to the price of the=20
> car because of the need to re-tool the assembly line.
>=20
> A sensible representative would take this information back to=20
> me and ask whether the additional cost was warranted. Of=20
> course, I would probably say, "no."
>=20
> An insane representative would, without contacting me, raise=20
> a stink about the ridiculous cost for this feature and=20
> attempt to stand their ground, eventually imposing an=20
> additional $400,000 cost on me.
>=20
> What I'd like to know for certain is that TISPAN=20
> *understands* the difficulty required to implement this one=20
> very small and rarely-used aspect of the feature, and that=20
> they have explicitly stated that it is important enough to=20
> justify the additional cost it imposes on the solution.
>=20
> /a
>=20
> >  =20
> >> -----Original Message-----
> >> From: Francois Audet [mailto:audet@nortel.com]=20
> >> Sent: 07 April 2007 19:39
> >> To: Elwell, John; Adam Roach; SIPPING WG
> >> Subject: RE: [Sipping] Call Completion: In Defense of=20
> >> Explicit Operations
> >>
> >> Hi John,
> >>
> >> Do you think that this implementing this feature in
> >> the way Adam and I were alluding to, i.e., where queuing
> >> is handled by the clients but without some of the more
> >> complex "queue management" feature would be acceptable
> >> in those countries?
> >>
> >> That would allow us to have a very simple implemenation
> >> without compromising the semantics of SUBSCRIBE or=20
> >> using a separate protocol (BFCP).
> >>
> >>
> >>    =20
> >>> -----Original Message-----
> >>> From: Elwell, John [mailto:john.elwell@siemens.com]=20
> >>> Sent: Saturday, April 07, 2007 11:29
> >>> To: Audet, Francois (SC100:3055); Adam Roach; SIPPING WG
> >>> Subject: RE: [Sipping] Call Completion: In Defense of=20
> >>> Explicit Operations
> >>>
> >>> I know this feature is quite popular in the PSTN residential=20
> >>> market in various countries in Europe, particularly Germany=20
> >>> and also the UK to some extent. Customers seem prepared to=20
> >>> spend a few euro cents for the convenience it gives in a=20
> >>> presence-less environment. So I think the operators of those=20
> >>> networks want to make sure they don't lose this when they=20
> >>> evolve to SIP. Given that in SIP you could do things=20
> >>> differently and hopefully better, PSTN interworking would=20
> >>> appear to be the essential driver behind the TISPAN=20
> >>> requirements, but presumably an important driver in the eyes=20
> >>> of the carriers concerned. For the enterprise market I just=20
> >>> don't see it as important. We used to have it on PBXs right=20
> >>> back in the 70s and 80s and it was popular then, but=20
> >>> voicemail has pretty well taken over in the enterprise. I=20
> >>> hope this sheds some light.
> >>>
> >>> John
> >>>
> >>>      =20
> >>>> -----Original Message-----
> >>>> From: Francois Audet [mailto:audet@nortel.com]
> >>>> Sent: 05 April 2007 23:18
> >>>> To: Adam Roach; SIPPING WG
> >>>> Subject: RE: [Sipping] Call Completion: In Defense of Explicit=20
> >>>> Operations
> >>>>
> >>>> Wouldn't it be possible to do this CCBS/CCNR stuff with a simple=20
> >>>> dialog package, and ditch this "queue management" mechanism?
> >>>>
> >>>> This seems to me to be a classic case of Engineers-gone-wild.
> >>>>
> >>>> I see this in the poetzl draft:
> >>>>
> >>>>     Completion of Calls on no Reply (CCNR) provides the=20
> >>>>        =20
> >> caller with=20
> >>    =20
> >>>> the
> >>>>     ability to complete a requested call to a callee=20
> >>>>        =20
> >>> without having to
> >>>      =20
> >>>>     make a new call attempt when the callee becomes not=20
> >>>>        =20
> >> busy after=20
> >>    =20
> >>>>     having initiated an activity.  The CCNR service=20
> >>>>        =20
> >> description is=20
> >>    =20
> >>>>     defined in ETSI EN 301 134 [6].=20
> >>>>
> >>>>     The call completion services provide the capability to queue=20
> >>>>     several CCBS/CCNR requests to the same callee on a FIFO=20
> >>>>        =20
> >>> basis. It=20
> >>>      =20
> >>>>     therefore requires functionalities like notifying=20
> >>>>        =20
> >>> changes of queue
> >>>      =20
> >>>>     states and managing queues. =20
> >>>>
> >>>> In other words, we are defining this really complex stuff=20
> >>>>        =20
> >>> just because=20
> >>>      =20
> >>>> it used to work like this in some ETSI standard for PSTN.
> >>>>
> >>>> Is there a better justification than that? What am I missing?
> >>>>
> >>>> Couldn't we handle some basic level of queueing at the endpoints=20
> >>>> themselves, and use a simple dialog package, and avoid all=20
> >>>>        =20
> >>> this stuff=20
> >>>      =20
> >>>> that creates all the complexity?
> >>>>
> >>>> This CCBS/CCNR feature is one of the feature that has the most=20
> >>>> variation
> >>>>
> >>>> in implementations in PSTN that I know of. To me, picking=20
> >>>>        =20
> >> a really=20
> >>    =20
> >>>> complicated variant and replicating it in SIP (either by=20
> >>>>        =20
> >>> bastardizing=20
> >>>      =20
> >>>> the protocol, or by using an entirely different protocol=20
> >>>>        =20
> >>> altogether)=20
> >>>      =20
> >>>> is not a good idea.
> >>>> My take is
> >>>> that there will be such a small uptake in implementation=20
> >>>>        =20
> >>> that it will=20
> >>>      =20
> >>>> effectively useful only in a few confined environments=20
> >>>>        =20
> >> where the it=20
> >>    =20
> >>>> can be mandated by law.
> >>>>
> >>>> I'd must rather have a simpler easier to implement=20
> version of the=20
> >>>> service.
> >>>>
> >>>>        =20
> >>>>> -----Original Message-----
> >>>>> From: Adam Roach [mailto:adam@nostrum.com]
> >>>>> Sent: Thursday, April 05, 2007 12:10
> >>>>> To: SIPPING WG
> >>>>> Subject: [Sipping] Call Completion: In Defense of Explicit
> >>>>>          =20
> >>>> Operations
> >>>>        =20
> >>>>> Despite what appeared to be early agreement in the=20
> >>>>>          =20
> >> working group=20
> >>    =20
> >>>>> (and on the MIG mailing list) that we wanted to=20
> >>>>>          =20
> >>> discourage the use=20
> >>>      =20
> >>>>> of SUBSCRIBE and NOTIFY as general purpose RPC=20
> >>>>>          =20
> >>> mechanisms. This is=20
> >>>      =20
> >>>>> the primary objection that I have raised to=20
> >>>>> draft-poetzl-sipping-call-completion,
> >>>>> which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
> >>>>>
> >>>>> In the spirit of sending text, I described an alternate set of=20
> >>>>> mechanisms in draft-roach-sipping-callcomp-bfcp, which=20
> >>>>>          =20
> >>> performs the=20
> >>>      =20
> >>>>> same task without having implied side effects from the=20
> >>>>>          =20
> >>> creation of a=20
> >>>      =20
> >>>>> subscription.
> >>>>>
> >>>>> I'll further note that the use of SUBSCRIBE to both create a=20
> >>>>> subscription and manipulate a call queue falls under the=20
> >>>>>          =20
> >>> category of=20
> >>>      =20
> >>>>> "one operation with two separate effects." We have a very poor=20
> >>>>> institutional memory indeed if we cannot recall why=20
> >>>>>          =20
> >> operations of=20
> >>    =20
> >>>>> this nature are Really Bad Ideas (cf. REFER creating a=20
> >>>>>          =20
> >>> subscription;=20
> >>>      =20
> >>>>> REGISTER with call processing upload; and BYE with an=20
> >>>>>          =20
> >>> "Also" header=20
> >>>      =20
> >>>>> field).
> >>>>>
> >>>>> All of this notwithstanding, in Prague, there seemed to=20
> >>>>>          =20
> >>> be a curious=20
> >>>      =20
> >>>>> indifference to pursuing the path laden with such Really=20
> >>>>>          =20
> >>> Bad Ideas.=20
> >>>      =20
> >>>>> I suspect that this indifference is a result of the=20
> >>>>>          =20
> >>> arguments raised=20
> >>>      =20
> >>>>> so far against the mechanism I have proposed, which I have done=20
> >>>>> little to refute so far (largely because I believed that=20
> >>>>>          =20
> >>> the merits=20
> >>>      =20
> >>>>> of a system with explicit operations were self-evident=20
> >>>>>          =20
> >>> enough that=20
> >>>      =20
> >>>>> the objections would seem trifling in comparison).
> >>>>>
> >>>>> As far as I can tell, the objections raised so far have=20
> >>>>>          =20
> >>> fallen into=20
> >>>      =20
> >>>>> three primary categories:
> >>>>>
> >>>>>    1. "The use of BFCP is troubling because, in a
> >>>>>          =20
> >>>> decomposed gateway,
> >>>>        =20
> >>>>>       the BFCP goes to the Media Gateway, while the
> >>>>>          =20
> >>>> signaling goes to
> >>>>        =20
> >>>>>       the Media Gateway Controller."
> >>>>>
> >>>>>       This objection, raised on one of the slides during=20
> >>>>>          =20
> >>> the SIPPING
> >>>      =20
> >>>>>       meeting on March 23rd as the official reason TISPAN
> >>>>>          =20
> >>>> rejected the
> >>>>        =20
> >>>>>       approach, is based on a simple misconception.
> >>>>>
> >>>>>       The BFCP goes wherever the SDP says the BFCP goes.=20
> >>>>>          =20
> >>> In the case=20
> >>>      =20
> >>>>> of
> >>>>>       a decomposed gateway, this could be the Media
> >>>>>          =20
> >>>> Gateway, the Media
> >>>>        =20
> >>>>>       Gateway Controller, or any other random
> >>>>>          =20
> >>>> network-connected server
> >>>>        =20
> >>>>>       that the Media Gateway Controller wants. I agree that it=20
> >>>>> probably
> >>>>>       is most sensible to send it to the Media Gateway
> >>>>>          =20
> >>>> Controller, and
> >>>>        =20
> >>>>>       this is trivial to achieve.
> >>>>>
> >>>>>    2. "In the case of PSTN interwork, there is no way to=20
> >>>>>          =20
> >>> guarantee=20
> >>>      =20
> >>>>> that
> >>>>>       the ISUP (or other) signaling from the PSTN side=20
> >>>>>          =20
> >>> lands on the=20
> >>>      =20
> >>>>> same
> >>>>>       gateway that the client has a BFCP connection to."
> >>>>>
> >>>>>       This is true, and it is a relatively difficult
> >>>>>          =20
> >>>> problem to solve
> >>>>        =20
> >>>>>       (not impossible, though; I proposed several potential=20
> >>>>> solutions in
> >>>>>       San Diego). It is meaningless to raise it in=20
> >>>>>          =20
> >> objection to an
> >>    =20
> >>>>>       alternate proposal, since it exists in almost
> >>>>>          =20
> >>>> precisely the same
> >>>>        =20
> >>>>>       form in draft-poetzl-sipping-call-completion; and=20
> >>>>>          =20
> >>> any solution
> >>>      =20
> >>>>>       that can be applied to one solution can be applied to
> >>>>>          =20
> >>>> the other.
> >>>>        =20
> >>>>>    3. "We don't want to add another protocol."
> >>>>>
> >>>>>       I suspect this argument is the one that is=20
> >>>>>          =20
> >>> receiving the most
> >>>      =20
> >>>>>       traction, probably because most of the people=20
> >>>>>          =20
> >>> involved in the
> >>>      =20
> >>>>>       discussion are not familiar with BFCP. The protocol=20
> >>>>>          =20
> >>> itself is=20
> >>>      =20
> >>>>> very
> >>>>>       straightforward and extremely easy to implement. In fact,
> >>>>>       exclusively for the purpose of answering this email (and
> >>>>>       demonstrating this very point), I threw together a BFCP
> >>>>>       implementation sufficient for implementation of the Call
> >>>>>       Completion service described in=20
> >>>>> draft-roach-sipping-callcomp-bfcp.
> >>>>>       It took me two hours, and compiles down to less=20
> >>>>>          =20
> >> than 4 kb of
> >>    =20
> >>>>>       object code on an intel processor. It's attached to
> >>>>>          =20
> >>>> this message
> >>>>        =20
> >>>>>       to help the participants in the conversation
> >>>>>          =20
> >>>> understand just how
> >>>>        =20
> >>>>>       very little is being added to applications by this
> >>>>>          =20
> >>>> use of BFCP.
> >>>>        =20
> >>>>> So, is that it? The first two objections are simply red=20
> >>>>>          =20
> >> herrings,=20
> >>    =20
> >>>>> and the third is based on a misconception regarding the=20
> >>>>>          =20
> >> level of=20
> >>    =20
> >>>>> effort required to implement BFCP. Are we really going to=20
> >>>>>          =20
> >>> down the=20
> >>>      =20
> >>>>> path of doing things incorrectly over what amount to=20
> >>>>> misunderstandings?
> >>>>>
> >>>>> /a
> >>>>>
> >>>>>
> >>>>>
> >>>>> P.S. In case anyone wants a more full-featured BFCP stack, I'll=20
> >>>>> point to the confiance project on SourceForge, available=20
> >>>>>          =20
> >>> under the=20
> >>>      =20
> >>>>> Academic Freedom License, which is compatible with commercial
> >>>>>          =20
> >>>> development. See
> >>>>        =20
> >>>>> http://confiance.sourceforge.net/
> >>>>>
> >>>>>          =20
> >>>> _______________________________________________
> >>>> Sipping mailing list =20
> >>>>        =20
> >> https://www1.ietf.org/mailman/listinfo/sipping
> >>    =20
> >>>> This list is for NEW development of the application of SIP Use=20
> >>>> sip-implementors@cs.columbia.edu for questions on=20
> current sip Use=20
> >>>> sip@ietf.org for new developments of core SIP
> >>>>
> >>>>        =20
>=20
>=20

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 12:01:23 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HawI5-0000Uj-0x; Mon, 09 Apr 2007 12:00:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HawI3-0000SQ-CA
	for sipping@ietf.org; Mon, 09 Apr 2007 12:00:23 -0400
Received: from 18-116.252-81.static-ip.oleane.fr ([81.252.116.18]
	helo=mail.softdom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HawI0-0002wL-F9
	for sipping@ietf.org; Mon, 09 Apr 2007 12:00:23 -0400
Received: from ([156.154.16.145])
	by mail.softdom.com (Merak 8.9.1) with SMTP id OUK84434
	for <sipping@ietf.org>; Mon, 09 Apr 2007 18:01:34 +0200
Date: Mon, 09 Apr 2007 18:01:34 +0200
From: Francois.plagnard <francois.plagnard@netbricks.net>
To: <sipping@ietf.org>
Message-Id: <914985009@mail.softdom.com>
Content-Type: text/plain; charset="utf-8"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: [Sipping] Re: Sipping Digest, Vol 36, Issue 25
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I'm out office until April 15th.

Best regards,

Francois Plagnard.


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 13:56:17 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hay5J-0006ne-Py; Mon, 09 Apr 2007 13:55:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hay5I-0006mh-9x
	for sipping@ietf.org; Mon, 09 Apr 2007 13:55:20 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hay5G-0004uq-TU
	for sipping@ietf.org; Mon, 09 Apr 2007 13:55:20 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 09 Apr 2007 13:55:20 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l39HtIQA009176; 
	Mon, 9 Apr 2007 13:55:18 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l39HshlQ014015; 
	Mon, 9 Apr 2007 17:55:14 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 13:55:12 -0400
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
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Mon, 9 Apr 2007 13:55:07 -0400
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E302DB35A0@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <46154996.50305@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
Thread-Index: Acd3tjKkl07dgjfaS4qxHAiuLtrMgQDGHGUA
References: <46154996.50305@nostrum.com>
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Adam Roach" <adam@nostrum.com>, "SIPPING WG" <sipping@ietf.org>
X-OriginalArrivalTime: 09 Apr 2007 17:55:12.0076 (UTC)
	FILETIME=[385D18C0:01C77AD0]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=6153; t=1176141318;
	x=1177005318; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mhammer@cisco.com;
	z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defense=20of=
	20Explicit=20Operations |Sender:=20
	|To:=20=22Adam=20Roach=22=20<adam@nostrum.com>,
	=20=22SIPPING=20WG=22=20<s ipping@ietf.org>;
	bh=XHtPJ61pvX9JBtEhsi+c3rwkOShZ4FXUTtR1wd57vXo=;
	b=CmStRF2C85ZP8x4TzBuV9Z6A7mA23ooFaj0vDYAaFf6yqufk9qHe0GJjn69nT3EPuzzxAb3H
	Oq7PLVrsteq5nc44JLYibeOeejmi0C6v4M5CZeqwEx1q2WjCpE9fQGFJ;
Authentication-Results: rtp-dkim-2; header.From=mhammer@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Adam,

I am confused about the disconnect between the true state of the call in
the solution you proprose.  In the case of CCBS or CCNR, in fact no call
is in progress.  The initial call has failed and the service is all
about state of a queue for managing priority of the next call attempt
that should be made with the targetted party.  Your reference to a "call
queue" is off the mark.  Only one call is in progress, the one that
caused the target to be busy.  (Or none if NR)  The other callers are
free to call elsewhere or not.  Their lines are not busy with the caller
"hanging on".  That is the whole point of the feature.

Also, I thought binary floor control was about manage sessions/media
*after* a call is completed.  In this way, it seems to be tainted by the
dual operational effects you assert for a subscription-based mechanism.
If floor control for failed as well as completed calls?

And yes, interworking with the TDM version of the feature is important.

To me the Subscription model was exactly called for since this is all
about learning the state of the priority order or not only who called,
but who called and wanted to be notified in order to call again.

Mike


> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]=20
> Sent: Thursday, April 05, 2007 3:10 PM
> To: SIPPING WG
> Subject: [Sipping] Call Completion: In Defense of Explicit Operations
>=20
> Despite what appeared to be early agreement in the working=20
> group (and on the MIG mailing list) that we wanted to=20
> discourage the use of SUBSCRIBE and NOTIFY as general purpose=20
> RPC mechanisms. This is the primary objection that I have=20
> raised to draft-poetzl-sipping-call-completion,
> which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
>=20
> In the spirit of sending text, I described an alternate set=20
> of mechanisms in draft-roach-sipping-callcomp-bfcp, which=20
> performs the same task without having implied side effects=20
> from the creation of a subscription.
>=20
> I'll further note that the use of SUBSCRIBE to both create a=20
> subscription and manipulate a call queue falls under the=20
> category of "one operation with two separate effects." We=20
> have a very poor institutional memory indeed if we cannot=20
> recall why operations of this nature are Really Bad Ideas=20
> (cf. REFER creating a subscription; REGISTER with call=20
> processing upload; and BYE with an "Also" header field).
>=20
> All of this notwithstanding, in Prague, there seemed to be a=20
> curious indifference to pursuing the path laden with such=20
> Really Bad Ideas. I suspect that this indifference is a=20
> result of the arguments raised so far against the mechanism I=20
> have proposed, which I have done little to refute so far=20
> (largely because I believed that the merits of a system with=20
> explicit operations were self-evident enough that the=20
> objections would seem trifling in comparison).
>=20
> As far as I can tell, the objections raised so far have=20
> fallen into three primary categories:
>=20
>    1. "The use of BFCP is troubling because, in a decomposed gateway,
>       the BFCP goes to the Media Gateway, while the signaling goes to
>       the Media Gateway Controller."
>=20
>       This objection, raised on one of the slides during the SIPPING
>       meeting on March 23rd as the official reason TISPAN rejected the
>       approach, is based on a simple misconception.
>=20
>       The BFCP goes wherever the SDP says the BFCP goes. In=20
> the case of
>       a decomposed gateway, this could be the Media Gateway, the Media
>       Gateway Controller, or any other random network-connected server
>       that the Media Gateway Controller wants. I agree that=20
> it probably
>       is most sensible to send it to the Media Gateway Controller, and
>       this is trivial to achieve.
>=20
>    2. "In the case of PSTN interwork, there is no way to=20
> guarantee that
>       the ISUP (or other) signaling from the PSTN side lands=20
> on the same
>       gateway that the client has a BFCP connection to."
>=20
>       This is true, and it is a relatively difficult problem to solve
>       (not impossible, though; I proposed several potential=20
> solutions in
>       San Diego). It is meaningless to raise it in objection to an
>       alternate proposal, since it exists in almost precisely the same
>       form in draft-poetzl-sipping-call-completion; and any solution
>       that can be applied to one solution can be applied to the other.
>=20
>    3. "We don't want to add another protocol."
>=20
>       I suspect this argument is the one that is receiving the most
>       traction, probably because most of the people involved in the
>       discussion are not familiar with BFCP. The protocol=20
> itself is very
>       straightforward and extremely easy to implement. In fact,
>       exclusively for the purpose of answering this email (and
>       demonstrating this very point), I threw together a BFCP
>       implementation sufficient for implementation of the Call
>       Completion service described in=20
> draft-roach-sipping-callcomp-bfcp.
>       It took me two hours, and compiles down to less than 4 kb of
>       object code on an intel processor. It's attached to this message
>       to help the participants in the conversation understand just how
>       very little is being added to applications by this use of BFCP.
>=20
> So, is that it? The first two objections are simply red=20
> herrings, and the third is based on a misconception regarding=20
> the level of effort required to implement BFCP. Are we really=20
> going to down the path of doing things incorrectly over what=20
> amount to misunderstandings?
>=20
> /a
>=20
>=20
>=20
> P.S. In case anyone wants a more full-featured BFCP stack,=20
> I'll point to=20
> the confiance project on SourceForge, available under the Academic=20
> Freedom License, which is compatible with commercial development. See=20
> http://confiance.sourceforge.net/
>=20

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 14:05:37 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HayF0-0005FR-LG; Mon, 09 Apr 2007 14:05:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HayEy-00057J-SA
	for sipping@ietf.org; Mon, 09 Apr 2007 14:05:20 -0400
Received: from panorama.covad.com ([66.134.72.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HayEx-0006xA-Bo
	for sipping@ietf.org; Mon, 09 Apr 2007 14:05:20 -0400
Received: from zanxmb00a.cc-ntd1.covad.com (zanxmb00a.corp.covad.com
	[172.16.2.75])
	by panorama.Covad.COM (8.9.3/8.8.7) with ESMTP id BAA03359;
	Tue, 10 Apr 2007 01:05:16 +0700 (GMT)
Received: from ZANEVS03.cc-ntd1.covad.com ([172.16.2.83]) by
	zanxmb00a.cc-ntd1.covad.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 11:05:16 -0700
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
Subject: RE: [Sipping] Session Establishment Efficiency Rate
Date: Mon, 9 Apr 2007 11:05:15 -0700
Message-ID: <3BC5D44AB71A754FAE3CA68A7597EABEB7BB25@ZANEVS03.cc-ntd1.covad.com>
In-Reply-To: <97F2AD7AA4EAD948827639B06CF2745FC4D462@esealmw106.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Session Establishment Efficiency Rate
Thread-Index: AcdXYkku4CAgr+eHTe2Vtg4MEn4t7AH1mCVwBKfN+4AAR6J0cAC1rfJgALddljA=
From: "Fardid, Reza" <RFardid@Covad.COM>
To: "Marian Delkinov \(LN/EAB\)" <marian.delkinov@ericsson.com>,
	"Daryl Malas" <daryl@level3.net>
X-OriginalArrivalTime: 09 Apr 2007 18:05:16.0236 (UTC)
	FILETIME=[A07898C0:01C77AD1]
X-TM-AS-Product-Ver: SMEX-7.0.0.1345-3.6.1039-15106.000
X-TM-AS-Result: No--16.251000-0.000000-31
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Mario,

IMO, if the objective is to eliminate called party behavior from ASR
(and SER), minimally the following response codes need to be excluded:
User Busy		~480
RNA			~486
Busy Everywhere	~600

I fail to see how exclusion of 3xx, other 4xx, and 6xx codes (with the
possible exception of 603) will serve this objective. =20

It appears that the metric you are proposing has a much broader scope.
Perhaps, the confusion is caused by the inclusion of "user agent"
behavior in the definition of SEER, which should only exclude the
effects of "called party" behavior.

Regards,
-Reza

	=09





-----Original Message-----
From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]=20
Sent: Tuesday, April 03, 2007 3:28 AM
To: Fardid, Reza; Daryl Malas
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Reza,=20

Exactly because of the analogy with NER and the meaning it has as
telephony metric I wanted to make clear the right counters, including
for release codes, are used to achieve the same meaning in SIP. I didn't
understand for when you foresee the implementation?

Best regards!
Mario.

-----Original Message-----
From: Fardid, Reza [mailto:RFardid@Covad.COM]=20
Sent: Friday, 30 March, 2007 22:02
To: Marian Delkinov (LN/EAB); Daryl Malas
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Mario,

What I had in mind when I proposed inclusion of SEER in this draft was a
SIP performance metric analogous to NER in the PSTN, within the
framework defined by Daryl:

Telephony Metric/Standard (ITU-T, BellCore, etc.) =3D=3D> SIP ETE Metric

Clearly some SIP metrics defined in this draft do not have a telephony
counterpart.  For the rest, IMO, it is good to stay within the above
framework and leave exclusion/inclusion of specific release codes from
defined metrics to implementation.

Regards,
Reza Fardid
Covad Communications


-----Original Message-----
From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
Sent: Thursday, March 29, 2007 1:07 AM
To: Daryl Malas
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Hi Daryl,

I haven't got your opinion about my comments on the SEER definition.
Have you considered them?=20
Would also be interested to know when a finalized document on the
performance metrics can be released.=20

Thanks!

Best regards!
Mario.

-----Original Message-----
From: Marian Delkinov (LN/EAB)
Sent: Monday, 05 March, 2007 17:06
To: 'Daryl Malas'
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Hi Daryl,

In principle, I agree with you in case we considered this from a user
perspective - then 3xx is not final. However my idea behind including
the 3xx codes was based on the involvement of "#Invite" in the formula.
If a 3xx code would result in sending a new Invite, then it sounds
logical to me to add the 3xx codes in the numerator. (NB: RFC3261
defines 3xx responses as "final" for the SIP transaction, ref. to page
21, Final Response).

Best regards!
Mario.

=20

-----Original Message-----
From: Daryl Malas [mailto:daryl@level3.net]
Sent: Friday, 23 February, 2007 17:00
To: Marian Delkinov (LN/EAB)
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

I don't think 3xx codes should be included, since they would not be
considered a "Final" release cause code.  --Daryl

On Fri, 2007-02-23 at 12:22 +0100, Marian Delkinov (LN/EAB) wrote:
> Hi,
>=20
> If the Network Efficiency Rate is designed to express the ability of=20
> the network to deliver calls (in SIP terms one should perhaps say=20
> "establish sessions"), I think that it might be reasonable to include=20
> few more cases (cause codes) in the numerator: e.g. all redirection=20
> 3xx codes, all 4xx except 408 codes and all 6xx codes. (If you agree=20
> that those are the ones that exclude network failures, congestion and=20
> any other network malfunction).
>=20
> Actually it sounds fair to me if it's the opposite of the Ineffective=20
> Session Attempts (ISA):
> SEER% =3D
> 	   Total # of Invite Requests - # of ISA
> ---------------------------------------------------- x 100
> 	   Total # of Invite Requests
>=20
> What do you think?
>=20
> Best regards!
> Mario.
>=20
> -----Original Message-----
> From: Daryl Malas [mailto:daryl@level3.net]
> Sent: Friday, 23 February, 2007 01:14
> To: sipping@ietf.org
> Subject: [Sipping] Session Establishment Efficiency Rate
>=20
> A couple more people have expressed to me that this adaptation of the=20
> ITU-T E.411 Network Efficiency Rate metric is very valuable.  The=20
> snapshot of the metric from the draft is:
>=20
> "This metric is similar to Session Establishment Rate, but it is=20
> intended to exclude the effects of customer behavior and user agent=20
> behavior.  Essentially, the attempts resulting with a final cause code

> of 480, 486, and 600 would be added to the SER numerator."
>=20
> Does anyone else want to see this metric in the draft?  I personally=20
> think it is an interesting metric.
>=20
> Thanks...
>=20
> --Daryl
>=20
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use=20
> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.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

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 14:18:52 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HayRd-0001CL-G8; Mon, 09 Apr 2007 14:18:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HayRc-0001CG-HU
	for sipping@ietf.org; Mon, 09 Apr 2007 14:18:24 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HayRb-0001DT-8G
	for sipping@ietf.org; Mon, 09 Apr 2007 14:18:24 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l39IIFnv003876
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 9 Apr 2007 13:18:17 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <461A8367.1000700@nostrum.com>
Date: Mon, 09 Apr 2007 13:18:15 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: "Michael Hammer (mhammer)" <mhammer@cisco.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB35A0@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E302DB35A0@xmb-rtp-20b.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Michael Hammer (mhammer) wrote:
> I am confused about the disconnect between the true state of the call in
> the solution you proprose.  In the case of CCBS or CCNR, in fact no call
> is in progress.  The initial call has failed and the service is all
> about state of a queue for managing priority of the next call attempt
> that should be made with the targetted party.  Your reference to a "call
> queue" is off the mark.

I was being imprecise, and I apologize. Anywhere I used that term, you 
can interpret it to mean "queue of pending but not ongoing calls."

> Only one call is in progress, the one that
> caused the target to be busy.  (Or none if NR)  The other callers are
> free to call elsewhere or not.  Their lines are not busy with the caller
> "hanging on".  That is the whole point of the feature.
>   

That was exactly my understanding, and I think this fact is relatively 
well represented in the current document.

> Also, I thought binary floor control was about manage sessions/media
> *after* a call is completed.  In this way, it seems to be tainted by the
> dual operational effects you assert for a subscription-based mechanism.
> If floor control for failed as well as completed calls?
>   

I believe you misunderstand what I was saying. The issue isn't that it's 
a single operation that can mean different things when used in different 
contexts -- that's okay if it's designed correctly. The place where we 
get into trouble is where we have a single instance of an operation -- 
one transaction, as it were -- that does two things simultaneously.


> And yes, interworking with the TDM version of the feature is important.
>   

I took great pains in my proposal to preserve this quality. The problem 
could be solved in a far simpler fashion otherwise.

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 15:29:17 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HazX5-0000kC-Kn; Mon, 09 Apr 2007 15:28:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HazX4-0000k6-Jx
	for sipping@ietf.org; Mon, 09 Apr 2007 15:28:06 -0400
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HazWx-00013Z-2d
	for sipping@ietf.org; Mon, 09 Apr 2007 15:28:06 -0400
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l39JRu6f009844; 
	Mon, 9 Apr 2007 14:27:56 -0500 (CDT)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90])
	by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l39JRtA12657; Mon, 9 Apr 2007 14:27:55 -0500 (CDT)
Message-ID: <461A93BB.6040106@alcatel-lucent.com>
Date: Mon, 09 Apr 2007 14:27:55 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Mahendran, AC" <mahendra@qualcomm.com>
References: <90D469E18343DE47961207F6851040B30188A91C@NAEX07.na.qualcomm.com>
In-Reply-To: <90D469E18343DE47961207F6851040B30188A91C@NAEX07.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ac@qualcomm.com, sipping@ietf.org, mary.barnes@nortel.com
Subject: [Sipping] Re: Comments on
	draft-ietf-sipping-ipv6-torture-tests-01.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Mahendran, AC wrote:
> Hi Vijay,
> 
> Here are my comments on draft-ietf-sipping-ipv6-torture-tests-01.txt. 

AC: Thanks for the review.

I went through your comments; all of them appear reasonable and
I do not see any reason not to include them in the next revision.
I don't have anything to clarify; so please make sure that your
comments are addressed in the next revision.

The document will be revised based on the two WGLC comments received
to date.  If anyone has any additional feedback, please post.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 15:32:52 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hazbf-0003dJ-Qm; Mon, 09 Apr 2007 15:32:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hazbe-0003dD-5U
	for sipping@ietf.org; Mon, 09 Apr 2007 15:32:50 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hazbb-0002Ky-S3
	for sipping@ietf.org; Mon, 09 Apr 2007 15:32:50 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 09 Apr 2007 15:32:47 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l39JWlZ6028191; 
	Mon, 9 Apr 2007 15:32:47 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l39JWlGd002767; 
	Mon, 9 Apr 2007 19:32:47 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 15:32:44 -0400
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
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Mon, 9 Apr 2007 15:32:41 -0400
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E302DB3651@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <461A8367.1000700@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
Thread-Index: Acd603gr+OybjisJRKG4OD2OyNyiRQACHYpw
References: <46154996.50305@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB35A0@xmb-rtp-20b.amer.cisco.com>
	<461A8367.1000700@nostrum.com>
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Adam Roach" <adam@nostrum.com>
X-OriginalArrivalTime: 09 Apr 2007 19:32:44.0168 (UTC)
	FILETIME=[D87B7880:01C77ADD]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3386; t=1176147167;
	x=1177011167; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mhammer@cisco.com;
	z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defense=20of=
	20Explicit=20Operations |Sender:=20
	|To:=20=22Adam=20Roach=22=20<adam@nostrum.com>;
	bh=f2b9AGxGwnBxuRNGs3byWUCUJ/wumT8FHpnmSqO+zhI=;
	b=LMlbSxK609mf3p+VRZ3ji36NuKA2s/ahLP6XoC1EF2IvIUkifNUq6QBWKZeuZ5uJP9ZnZ/4o
	LEjmYgkzbCstHy7yOkNgOafa13gCeYyz9DAK1U9R0NrKrce+7UC284f6;
Authentication-Results: rtp-dkim-2; header.From=mhammer@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Adam,

My intent is not to advocate the solution as exactly like the poetzl
draft proposes, but to suggest that the SUB/NOT approach is not
inherently wrong.  The problem with the existing draft is that it tries
to treat the Subscribe like an ISUP message.

I was thinking that the set of subscriptions is state.
The in arrival order of that state is a queue.
Reaching the top of the queue (and still being able to make the call) is
an Event.
Events can be Notified.

How does the application managing the subscriptions and queue know the
caller is able to make the call? =20
That could be Presence state learned through the called application
subscribing to those callers who subscribed to the CCBS/NR Top of queue
Event.

Yes, it is reciprocal.  But, in such a case SUB/NOT operates exactly as
proscribed.

The tricky part about matching the TDM CCBS is the ability to suspend
and resume without losing place in line.  The algorithm for deciding who
is next at top of queue and when to cancel the subscription would be
straight forward.

Mike
=20

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]=20
> Sent: Monday, April 09, 2007 2:18 PM
> To: Michael Hammer (mhammer)
> Cc: SIPPING WG
> Subject: Re: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
> Michael Hammer (mhammer) wrote:
> > I am confused about the disconnect between the true state=20
> of the call=20
> > in the solution you proprose.  In the case of CCBS or CCNR,=20
> in fact no=20
> > call is in progress.  The initial call has failed and the=20
> service is=20
> > all about state of a queue for managing priority of the next call=20
> > attempt that should be made with the targetted party.  Your=20
> reference=20
> > to a "call queue" is off the mark.
>=20
> I was being imprecise, and I apologize. Anywhere I used that=20
> term, you can interpret it to mean "queue of pending but not=20
> ongoing calls."
>=20
> > Only one call is in progress, the one that caused the target to be=20
> > busy.  (Or none if NR)  The other callers are free to call=20
> elsewhere=20
> > or not.  Their lines are not busy with the caller "hanging=20
> on".  That=20
> > is the whole point of the feature.
> >  =20
>=20
> That was exactly my understanding, and I think this fact is=20
> relatively well represented in the current document.
>=20
> > Also, I thought binary floor control was about manage sessions/media
> > *after* a call is completed.  In this way, it seems to be=20
> tainted by=20
> > the dual operational effects you assert for a=20
> subscription-based mechanism.
> > If floor control for failed as well as completed calls?
> >  =20
>=20
> I believe you misunderstand what I was saying. The issue=20
> isn't that it's a single operation that can mean different=20
> things when used in different contexts -- that's okay if it's=20
> designed correctly. The place where we get into trouble is=20
> where we have a single instance of an operation -- one=20
> transaction, as it were -- that does two things simultaneously.
>=20
>=20
> > And yes, interworking with the TDM version of the feature=20
> is important.
> >  =20
>=20
> I took great pains in my proposal to preserve this quality.=20
> The problem could be solved in a far simpler fashion otherwise.
>=20
> /a
>=20

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 15:33:20 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hazc8-0003pY-QX; Mon, 09 Apr 2007 15:33:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hazc7-0003nD-An
	for sipping@ietf.org; Mon, 09 Apr 2007 15:33:19 -0400
Received: from 18-116.252-81.static-ip.oleane.fr ([81.252.116.18]
	helo=mail.softdom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hazc4-0002Pf-Ox
	for sipping@ietf.org; Mon, 09 Apr 2007 15:33:19 -0400
Received: from ([156.154.16.145])
	by mail.softdom.com (Merak 8.9.1) with SMTP id OXR34430
	for <sipping@ietf.org>; Mon, 09 Apr 2007 21:34:30 +0200
Date: Mon, 09 Apr 2007 21:34:30 +0200
From: Francois.plagnard <francois.plagnard@netbricks.net>
To: <sipping@ietf.org>
Message-Id: <914992207@mail.softdom.com>
Content-Type: text/plain; charset="utf-8"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: [Sipping] Re: Sipping Digest, Vol 36, Issue 26
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I'm out office until April 15th.

Best regards,

Francois Plagnard.


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 15:54:58 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hazx3-00007D-Io; Mon, 09 Apr 2007 15:54:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hazx2-00006x-K4
	for sipping@ietf.org; Mon, 09 Apr 2007 15:54:56 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hazwn-0000q4-V8
	for sipping@ietf.org; Mon, 09 Apr 2007 15:54:56 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l39JsWMY008519
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 9 Apr 2007 14:54:32 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <461A99F8.3050408@nostrum.com>
Date: Mon, 09 Apr 2007 14:54:32 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: "Michael Hammer (mhammer)" <mhammer@cisco.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB35A0@xmb-rtp-20b.amer.cisco.com>
	<461A8367.1000700@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB3651@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E302DB3651@xmb-rtp-20b.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Michael Hammer (mhammer) wrote:
> My intent is not to advocate the solution as exactly like the poetzl
> draft proposes, but to suggest that the SUB/NOT approach is not
> inherently wrong.  The problem with the existing draft is that it tries
> to treat the Subscribe like an ISUP message.
>
> I was thinking that the set of subscriptions is state.
> The in arrival order of that state is a queue.
> Reaching the top of the queue (and still being able to make the call) is
> an Event.
> Events can be Notified.
>   

That's an interesting way of looking at it -- but I'm pretty sure that 
what you're describing would require two subscriptions from each caller 
to make things work.

So, basically, the caller would subscribe to the callee (or their agent) 
for some event package -- perhaps presence, perhaps dialog state, 
perhaps something else. For the sake of discussion, we'll call this 
event package "foo" for the time being.

Then, for this service, we would define a new template event package 
that deals with the relative order of subscribers' subscriptions to a 
resource. Let's call this template event package ".queue".

Then, to activate the service, your proposal basically boils down to the 
caller first subscribing to foo (which may usefully provide the calling 
party some kind of progress information about the called party -- as 
would be the case with the two example event packages I name above.) 
After this subscription succeeds, the caller would additionally 
subscribe to the event package "foo.queue", which would allow the caller 
to find out about the order in which these subscriptions... umm... 
occurred? expire? refresh? I have to admit that I get a bit lost here 
when you talk about "reaching the top of the queue is an event," since 
it's not clear where this queue comes from. It's not something that's 
inherently part of a subscription, as far as I can tell.

In any case, I concede that they might be a solution down this path, but 
you'd need to identify something that's inherently part of a 
subscription's state that has the queuing properties you want. I'm not 
convinced that such a thing exists.

And here's the crux of the matter: adding such a property to an event 
package inherently means that you're now taking "SUBSCRIBE" from meaning 
"create a subscription" to meaning "create a subscription *and* insert 
my user into a queue;" these need to be separate, explicit operations 
that succeed or fail independently.

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 16:15:34 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hb0GL-0003k8-3u; Mon, 09 Apr 2007 16:14:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hb0GJ-0003jt-Qf
	for sipping@ietf.org; Mon, 09 Apr 2007 16:14:51 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hb0GB-00053a-ID
	for sipping@ietf.org; Mon, 09 Apr 2007 16:14:51 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l39JwU3i008870
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 9 Apr 2007 14:58:31 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <461A9AE7.1030802@nostrum.com>
Date: Mon, 09 Apr 2007 14:58:31 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: "Michael Hammer (mhammer)" <mhammer@cisco.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB35A0@xmb-rtp-20b.amer.cisco.com>
	<461A8367.1000700@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB3651@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E302DB3651@xmb-rtp-20b.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Michael:

Since we're having this discussion, and you seem to be one of the 
parties that has a distinctly different opinion on
the topic than I, I'd like you to comment on whether my note at the 
beginning of this thread accurately described the objections that have 
been raised to my BFCP-based proposal -- and whether my explanations 
regarding why I believe such objections are invalid contains any obvious 
fallacies.

Thanks.

/a

Michael Hammer (mhammer) wrote:
> Adam,
>
> My intent is not to advocate the solution as exactly like the poetzl
> draft proposes, but to suggest that the SUB/NOT approach is not
> inherently wrong.  The problem with the existing draft is that it tries
> to treat the Subscribe like an ISUP message.
>
> I was thinking that the set of subscriptions is state.
> The in arrival order of that state is a queue.
> Reaching the top of the queue (and still being able to make the call) is
> an Event.
> Events can be Notified.
>
> How does the application managing the subscriptions and queue know the
> caller is able to make the call?  
> That could be Presence state learned through the called application
> subscribing to those callers who subscribed to the CCBS/NR Top of queue
> Event.
>
> Yes, it is reciprocal.  But, in such a case SUB/NOT operates exactly as
> proscribed.
>
> The tricky part about matching the TDM CCBS is the ability to suspend
> and resume without losing place in line.  The algorithm for deciding who
> is next at top of queue and when to cancel the subscription would be
> straight forward.
>
> Mike
>  
>
>   
>> -----Original Message-----
>> From: Adam Roach [mailto:adam@nostrum.com] 
>> Sent: Monday, April 09, 2007 2:18 PM
>> To: Michael Hammer (mhammer)
>> Cc: SIPPING WG
>> Subject: Re: [Sipping] Call Completion: In Defense of 
>> Explicit Operations
>>
>> Michael Hammer (mhammer) wrote:
>>     
>>> I am confused about the disconnect between the true state 
>>>       
>> of the call 
>>     
>>> in the solution you proprose.  In the case of CCBS or CCNR, 
>>>       
>> in fact no 
>>     
>>> call is in progress.  The initial call has failed and the 
>>>       
>> service is 
>>     
>>> all about state of a queue for managing priority of the next call 
>>> attempt that should be made with the targetted party.  Your 
>>>       
>> reference 
>>     
>>> to a "call queue" is off the mark.
>>>       
>> I was being imprecise, and I apologize. Anywhere I used that 
>> term, you can interpret it to mean "queue of pending but not 
>> ongoing calls."
>>
>>     
>>> Only one call is in progress, the one that caused the target to be 
>>> busy.  (Or none if NR)  The other callers are free to call 
>>>       
>> elsewhere 
>>     
>>> or not.  Their lines are not busy with the caller "hanging 
>>>       
>> on".  That 
>>     
>>> is the whole point of the feature.
>>>   
>>>       
>> That was exactly my understanding, and I think this fact is 
>> relatively well represented in the current document.
>>
>>     
>>> Also, I thought binary floor control was about manage sessions/media
>>> *after* a call is completed.  In this way, it seems to be 
>>>       
>> tainted by 
>>     
>>> the dual operational effects you assert for a 
>>>       
>> subscription-based mechanism.
>>     
>>> If floor control for failed as well as completed calls?
>>>   
>>>       
>> I believe you misunderstand what I was saying. The issue 
>> isn't that it's a single operation that can mean different 
>> things when used in different contexts -- that's okay if it's 
>> designed correctly. The place where we get into trouble is 
>> where we have a single instance of an operation -- one 
>> transaction, as it were -- that does two things simultaneously.
>>
>>
>>     
>>> And yes, interworking with the TDM version of the feature 
>>>       
>> is important.
>>     
>>>   
>>>       
>> I took great pains in my proposal to preserve this quality. 
>> The problem could be solved in a far simpler fashion otherwise.
>>
>> /a
>>
>>     


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 16:49:42 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hb0mW-00066J-MA; Mon, 09 Apr 2007 16:48:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hb0mU-00066E-Qk
	for sipping@ietf.org; Mon, 09 Apr 2007 16:48:06 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hb0mO-0003vD-Rz
	for sipping@ietf.org; Mon, 09 Apr 2007 16:48:06 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 09 Apr 2007 16:48:01 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l39Km0cj010150; 
	Mon, 9 Apr 2007 16:48:00 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l39KlqlS007257; 
	Mon, 9 Apr 2007 20:48:00 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 16:47:54 -0400
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
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Mon, 9 Apr 2007 16:47:52 -0400
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E302DB36C3@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <461A9AE7.1030802@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
Thread-Index: Acd64XTfEo0tQpqER9WZwMLeM2g5nwABT5ow
References: <46154996.50305@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB35A0@xmb-rtp-20b.amer.cisco.com>
	<461A8367.1000700@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB3651@xmb-rtp-20b.amer.cisco.com>
	<461A9AE7.1030802@nostrum.com>
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Adam Roach" <adam@nostrum.com>
X-OriginalArrivalTime: 09 Apr 2007 20:47:54.0369 (UTC)
	FILETIME=[58C58710:01C77AE8]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5897; t=1176151680;
	x=1177015680; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mhammer@cisco.com;
	z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defense=20of=
	20Explicit=20Operations |Sender:=20
	|To:=20=22Adam=20Roach=22=20<adam@nostrum.com>;
	bh=xGGdQvSycubwBI/nr7KfNh86uQE24UoLgwW67J9VIpg=;
	b=L+6CsuCJs5NQQSvPL3I6f454jKt7nxmABSCIei4r64WDPf0F+mNjXj3N6804R9+on7+fm4p/
	ZeUHgAfVkcqk7IJt7YHxuOugbNdqcHKaYyyxgbmIFlugHOfNZLraBfeD;
Authentication-Results: rtp-dkim-1; header.From=mhammer@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Adam,

One potential weakness in your arguments is a possible assumption that
there are no intermediate boxes that have to handle the SDP and the
subsequent BFCP.  Having the additional protocol may mean additional
programming for the SBCs and other things that like to muck with the
signaling. :(  In a purer SIP world this might not be so bad.  Every new
protocol probably means asking a host of vendors:  "Do you handle
protocol X too?"

While we are at it, when I read the draft my impression was that you
never sent a 486 to end the call as busy, but kept all callers on as
early dialogs.  Did I read that right?  In some situations a client may
be able to only make one call at a time due to interface constraints.

Also, it seemed very strange to me that an INVITE would set up a session
(the BFCP) that did not end with the final response to the INVITE (a
486).  Did I read that correctly?  If so, some middleboxes would likley
shut down such connections when the INVITE gets non-success response.

Mike


> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]=20
> Sent: Monday, April 09, 2007 3:59 PM
> To: Michael Hammer (mhammer)
> Cc: SIPPING WG
> Subject: Re: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
> Michael:
>=20
> Since we're having this discussion, and you seem to be one of=20
> the parties that has a distinctly different opinion on the=20
> topic than I, I'd like you to comment on whether my note at=20
> the beginning of this thread accurately described the=20
> objections that have been raised to my BFCP-based proposal --=20
> and whether my explanations regarding why I believe such=20
> objections are invalid contains any obvious fallacies.
>=20
> Thanks.
>=20
> /a
>=20
> Michael Hammer (mhammer) wrote:
> > Adam,
> >
> > My intent is not to advocate the solution as exactly like=20
> the poetzl=20
> > draft proposes, but to suggest that the SUB/NOT approach is not=20
> > inherently wrong.  The problem with the existing draft is that it=20
> > tries to treat the Subscribe like an ISUP message.
> >
> > I was thinking that the set of subscriptions is state.
> > The in arrival order of that state is a queue.
> > Reaching the top of the queue (and still being able to make=20
> the call)=20
> > is an Event.
> > Events can be Notified.
> >
> > How does the application managing the subscriptions and=20
> queue know the=20
> > caller is able to make the call?
> > That could be Presence state learned through the called application=20
> > subscribing to those callers who subscribed to the CCBS/NR Top of=20
> > queue Event.
> >
> > Yes, it is reciprocal.  But, in such a case SUB/NOT=20
> operates exactly=20
> > as proscribed.
> >
> > The tricky part about matching the TDM CCBS is the ability=20
> to suspend=20
> > and resume without losing place in line.  The algorithm for=20
> deciding=20
> > who is next at top of queue and when to cancel the=20
> subscription would=20
> > be straight forward.
> >
> > Mike
> > =20
> >
> >  =20
> >> -----Original Message-----
> >> From: Adam Roach [mailto:adam@nostrum.com]
> >> Sent: Monday, April 09, 2007 2:18 PM
> >> To: Michael Hammer (mhammer)
> >> Cc: SIPPING WG
> >> Subject: Re: [Sipping] Call Completion: In Defense of Explicit=20
> >> Operations
> >>
> >> Michael Hammer (mhammer) wrote:
> >>    =20
> >>> I am confused about the disconnect between the true state
> >>>      =20
> >> of the call
> >>    =20
> >>> in the solution you proprose.  In the case of CCBS or CCNR,
> >>>      =20
> >> in fact no
> >>    =20
> >>> call is in progress.  The initial call has failed and the
> >>>      =20
> >> service is
> >>    =20
> >>> all about state of a queue for managing priority of the next call=20
> >>> attempt that should be made with the targetted party.  Your
> >>>      =20
> >> reference
> >>    =20
> >>> to a "call queue" is off the mark.
> >>>      =20
> >> I was being imprecise, and I apologize. Anywhere I used that term,=20
> >> you can interpret it to mean "queue of pending but not ongoing=20
> >> calls."
> >>
> >>    =20
> >>> Only one call is in progress, the one that caused the=20
> target to be=20
> >>> busy.  (Or none if NR)  The other callers are free to call
> >>>      =20
> >> elsewhere
> >>    =20
> >>> or not.  Their lines are not busy with the caller "hanging
> >>>      =20
> >> on".  That
> >>    =20
> >>> is the whole point of the feature.
> >>>  =20
> >>>      =20
> >> That was exactly my understanding, and I think this fact is=20
> >> relatively well represented in the current document.
> >>
> >>    =20
> >>> Also, I thought binary floor control was about manage=20
> sessions/media
> >>> *after* a call is completed.  In this way, it seems to be
> >>>      =20
> >> tainted by
> >>    =20
> >>> the dual operational effects you assert for a
> >>>      =20
> >> subscription-based mechanism.
> >>    =20
> >>> If floor control for failed as well as completed calls?
> >>>  =20
> >>>      =20
> >> I believe you misunderstand what I was saying. The issue=20
> isn't that=20
> >> it's a single operation that can mean different things=20
> when used in=20
> >> different contexts -- that's okay if it's designed correctly. The=20
> >> place where we get into trouble is where we have a single=20
> instance of=20
> >> an operation -- one transaction, as it were -- that does=20
> two things=20
> >> simultaneously.
> >>
> >>
> >>    =20
> >>> And yes, interworking with the TDM version of the feature
> >>>      =20
> >> is important.
> >>    =20
> >>>  =20
> >>>      =20
> >> I took great pains in my proposal to preserve this quality.=20
> >> The problem could be solved in a far simpler fashion otherwise.
> >>
> >> /a
> >>
> >>    =20
>=20

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 16:49:42 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hb0ng-0006UX-W6; Mon, 09 Apr 2007 16:49:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hb0nf-0006UM-Hk
	for sipping@ietf.org; Mon, 09 Apr 2007 16:49:19 -0400
Received: from alnrmhc11.comcast.net ([204.127.225.91])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hb0ne-0004A0-2u
	for sipping@ietf.org; Mon, 09 Apr 2007 16:49:19 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (alnrmhc11) with ESMTP
	id <20070409204917b1100kcpuie>; Mon, 9 Apr 2007 20:49:17 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l39KnGLv014771
	for <sipping@ietf.org>; Mon, 9 Apr 2007 16:49:16 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l39KnG1p014767;
	Mon, 9 Apr 2007 16:49:16 -0400
Date: Mon, 9 Apr 2007 16:49:16 -0400
Message-Id: <200704092049.l39KnG1p014767@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <7374777208BDC7449D5620EF9423256702B78623@esealmw113.eemea.ericsson.se>
	(christer.holmberg@ericsson.com)
Subject: Re: [Sipping] Re: draft-holmberg-sipping-199-00.txt
References: <7374777208BDC7449D5620EF9423256702B78623@esealmw113.eemea.ericsson.se>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>

   Because, in some cases 199 may be useful to peopleeven if they don't
   know whe IP source information etc for a stream associated with the
   early dialog. "Resource" may have different meaning for different
   applications, access types and network architectures.

Well, off the top of my head, I don't see any real usefulness of 199
unless the UAC can use it to terminate consideration of a media
stream.  So to make it worth moving forward, we either need to find
another reason that it's useful, or work out the media stream
correlation.

Dale

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 17:00:12 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hb0y0-0000dZ-Ef; Mon, 09 Apr 2007 17:00:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hb0xz-0000dU-Ar
	for sipping@ietf.org; Mon, 09 Apr 2007 16:59:59 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hb0xw-0006Uh-VL
	for sipping@ietf.org; Mon, 09 Apr 2007 16:59:59 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l39KxpVD012000
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 9 Apr 2007 15:59:51 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <461AA948.2090906@nostrum.com>
Date: Mon, 09 Apr 2007 15:59:52 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: "Michael Hammer (mhammer)" <mhammer@cisco.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB35A0@xmb-rtp-20b.amer.cisco.com>
	<461A8367.1000700@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB3651@xmb-rtp-20b.amer.cisco.com>
	<461A9AE7.1030802@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB36C3@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E302DB36C3@xmb-rtp-20b.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Michael Hammer (mhammer) wrote:
> One potential weakness in your arguments is a possible assumption that
> there are no intermediate boxes that have to handle the SDP and the
> subsequent BFCP.  Having the additional protocol may mean additional
> programming for the SBCs and other things that like to muck with the
> signaling. :(  In a purer SIP world this might not be so bad.  Every new
> protocol probably means asking a host of vendors:  "Do you handle
> protocol X too?"
>   

An interesting point; however, such middleboxes typically need 
modification to handle *any* new service semantics (including, most 
probably, the SUB/NOT proposal in draft-poetzl), so I don't think it's 
that much of a differentiator.

> While we are at it, when I read the draft my impression was that you
> never sent a 486 to end the call as busy, but kept all callers on as
> early dialogs.  Did I read that right?

No; the original (failed) call attempt is terminated with a 486 in this 
case. A *new* dialog is set up for the queue management.

> Also, it seemed very strange to me that an INVITE would set up a session
> (the BFCP) that did not end with the final response to the INVITE (a
> 486).  Did I read that correctly?

The BFCP dialog is established normally with a 200, and ends normally 
with a BYE.

For both of these cases, look at section 8.1 -- messages 1 through 6 are 
a normal failed call attempt due to a called-party-busy situation 
(INVITE/180/PRACK/200/486/ACK). Messages 7 though 9 are a normal session 
establishment for a BFCP-only session (INVITE/200/ACK). Messages 15 
through 20 are the call re-attempt, which establishes a normal voice 
call (INVITE/180/PRACK/200/200/ACK). Messages 22 and 23 tear down the 
BFCP-only session (BYE/200).

Does that make the proposed mechanism clearer?

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 17:13:43 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hb1BC-0005Se-Qj; Mon, 09 Apr 2007 17:13:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hb1BB-0005SY-Lw
	for sipping@ietf.org; Mon, 09 Apr 2007 17:13:37 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hb1BA-0001ba-Cq
	for sipping@ietf.org; Mon, 09 Apr 2007 17:13:37 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 09 Apr 2007 17:13:34 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l39LDYgo016083; 
	Mon, 9 Apr 2007 17:13:34 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l39LDXGd003233; 
	Mon, 9 Apr 2007 21:13:34 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Apr 2007 17:13:33 -0400
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
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Mon, 9 Apr 2007 17:13:36 -0400
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E302DB36E9@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <461AA948.2090906@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
Thread-Index: Acd66g59TlEqfk0uRgmYL+PGX4uEUQAAWrWQ
References: <46154996.50305@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB35A0@xmb-rtp-20b.amer.cisco.com>
	<461A8367.1000700@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB3651@xmb-rtp-20b.amer.cisco.com>
	<461A9AE7.1030802@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB36C3@xmb-rtp-20b.amer.cisco.com>
	<461AA948.2090906@nostrum.com>
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Adam Roach" <adam@nostrum.com>
X-OriginalArrivalTime: 09 Apr 2007 21:13:33.0968 (UTC)
	FILETIME=[EE71B100:01C77AEB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2467; t=1176153214;
	x=1177017214; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mhammer@cisco.com;
	z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defense=20of=
	20Explicit=20Operations |Sender:=20
	|To:=20=22Adam=20Roach=22=20<adam@nostrum.com>;
	bh=QOUJn1fBrV6NZ8XmwQ8izozJu70trqh7evkSASfzxBk=;
	b=UYWG3RyOIGH7NoY4gzpk7RjqugJnEIAlpQkJwKSVnYoKYFk/pj1JAqL/lqVUE+2qA4OyUjaO
	eRYGH0uyC1UyW3l77+R4PCJa9UkAsvMHbSF6aJ8XYs4S5yjfdEpkkVzG;
Authentication-Results: rtp-dkim-2; header.From=mhammer@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Ok, that makes things clearer.

BTW, do you release the floor before you finish the call that got
through because of the floor request?

Mike
=20

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]=20
> Sent: Monday, April 09, 2007 5:00 PM
> To: Michael Hammer (mhammer)
> Cc: SIPPING WG
> Subject: Re: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
> Michael Hammer (mhammer) wrote:
> > One potential weakness in your arguments is a possible=20
> assumption that=20
> > there are no intermediate boxes that have to handle the SDP and the=20
> > subsequent BFCP.  Having the additional protocol may mean=20
> additional=20
> > programming for the SBCs and other things that like to muck=20
> with the=20
> > signaling. :(  In a purer SIP world this might not be so=20
> bad.  Every=20
> > new protocol probably means asking a host of vendors:  "Do=20
> you handle=20
> > protocol X too?"
> >  =20
>=20
> An interesting point; however, such middleboxes typically=20
> need modification to handle *any* new service semantics=20
> (including, most probably, the SUB/NOT proposal in=20
> draft-poetzl), so I don't think it's that much of a differentiator.
>=20
> > While we are at it, when I read the draft my impression was=20
> that you=20
> > never sent a 486 to end the call as busy, but kept all=20
> callers on as=20
> > early dialogs.  Did I read that right?
>=20
> No; the original (failed) call attempt is terminated with a=20
> 486 in this case. A *new* dialog is set up for the queue management.
>=20
> > Also, it seemed very strange to me that an INVITE would set up a=20
> > session (the BFCP) that did not end with the final response to the=20
> > INVITE (a 486).  Did I read that correctly?
>=20
> The BFCP dialog is established normally with a 200, and ends=20
> normally with a BYE.
>=20
> For both of these cases, look at section 8.1 -- messages 1=20
> through 6 are a normal failed call attempt due to a=20
> called-party-busy situation (INVITE/180/PRACK/200/486/ACK).=20
> Messages 7 though 9 are a normal session establishment for a=20
> BFCP-only session (INVITE/200/ACK). Messages 15 through 20=20
> are the call re-attempt, which establishes a normal voice=20
> call (INVITE/180/PRACK/200/200/ACK). Messages 22 and 23 tear=20
> down the BFCP-only session (BYE/200).
>=20
> Does that make the proposed mechanism clearer?
>=20
> /a
>=20

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 17:13:56 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hb1BU-0005hN-Ag; Mon, 09 Apr 2007 17:13:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hb1BS-0005gu-QB
	for sipping@ietf.org; Mon, 09 Apr 2007 17:13:54 -0400
Received: from 18-116.252-81.static-ip.oleane.fr ([81.252.116.18]
	helo=mail.softdom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hb1BN-0001cU-KJ
	for sipping@ietf.org; Mon, 09 Apr 2007 17:13:54 -0400
Received: from ([156.154.16.145])
	by mail.softdom.com (Merak 8.9.1) with SMTP id OZY90702
	for <sipping@ietf.org>; Mon, 09 Apr 2007 23:15:02 +0200
Date: Mon, 09 Apr 2007 23:15:02 +0200
From: Francois.plagnard <francois.plagnard@netbricks.net>
To: <sipping@ietf.org>
Message-Id: <914995681@mail.softdom.com>
Content-Type: text/plain; charset="utf-8"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: [Sipping] Re: Sipping Digest, Vol 36, Issue 27
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I'm out office until April 15th.

Best regards,

Francois Plagnard.


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 09 17:20:39 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hb1HV-0007cY-Sl; Mon, 09 Apr 2007 17:20:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hb1HU-0007cT-OK
	for sipping@ietf.org; Mon, 09 Apr 2007 17:20:08 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hb1HT-0002v3-EF
	for sipping@ietf.org; Mon, 09 Apr 2007 17:20:08 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l39LK620013146
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 9 Apr 2007 16:20:06 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <461AAE06.2000708@nostrum.com>
Date: Mon, 09 Apr 2007 16:20:06 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: "Michael Hammer (mhammer)" <mhammer@cisco.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB35A0@xmb-rtp-20b.amer.cisco.com>
	<461A8367.1000700@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB3651@xmb-rtp-20b.amer.cisco.com>
	<461A9AE7.1030802@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB36C3@xmb-rtp-20b.amer.cisco.com>
	<461AA948.2090906@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB36E9@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E302DB36E9@xmb-rtp-20b.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Michael Hammer (mhammer) wrote:
> Ok, that makes things clearer.
>
> BTW, do you release the floor before you finish the call that got
> through because of the floor request?
>   

That's an interesting question. Currently, the document shows the floor 
being released by the caller as soon as the call re-attempt succeeds. It 
would probably be more semantically correct to have the caller hold the 
floor until the call is concluded. In practice, this strikes me as a 
fairly minor detail that can be ironed out later (and I believe one can 
make reasonable arguments both ways).

/a


> Mike
>  
>
>   
>> -----Original Message-----
>> From: Adam Roach [mailto:adam@nostrum.com] 
>> Sent: Monday, April 09, 2007 5:00 PM
>> To: Michael Hammer (mhammer)
>> Cc: SIPPING WG
>> Subject: Re: [Sipping] Call Completion: In Defense of 
>> Explicit Operations
>>
>> Michael Hammer (mhammer) wrote:
>>     
>>> One potential weakness in your arguments is a possible 
>>>       
>> assumption that 
>>     
>>> there are no intermediate boxes that have to handle the SDP and the 
>>> subsequent BFCP.  Having the additional protocol may mean 
>>>       
>> additional 
>>     
>>> programming for the SBCs and other things that like to muck 
>>>       
>> with the 
>>     
>>> signaling. :(  In a purer SIP world this might not be so 
>>>       
>> bad.  Every 
>>     
>>> new protocol probably means asking a host of vendors:  "Do 
>>>       
>> you handle 
>>     
>>> protocol X too?"
>>>   
>>>       
>> An interesting point; however, such middleboxes typically 
>> need modification to handle *any* new service semantics 
>> (including, most probably, the SUB/NOT proposal in 
>> draft-poetzl), so I don't think it's that much of a differentiator.
>>
>>     
>>> While we are at it, when I read the draft my impression was 
>>>       
>> that you 
>>     
>>> never sent a 486 to end the call as busy, but kept all 
>>>       
>> callers on as 
>>     
>>> early dialogs.  Did I read that right?
>>>       
>> No; the original (failed) call attempt is terminated with a 
>> 486 in this case. A *new* dialog is set up for the queue management.
>>
>>     
>>> Also, it seemed very strange to me that an INVITE would set up a 
>>> session (the BFCP) that did not end with the final response to the 
>>> INVITE (a 486).  Did I read that correctly?
>>>       
>> The BFCP dialog is established normally with a 200, and ends 
>> normally with a BYE.
>>
>> For both of these cases, look at section 8.1 -- messages 1 
>> through 6 are a normal failed call attempt due to a 
>> called-party-busy situation (INVITE/180/PRACK/200/486/ACK). 
>> Messages 7 though 9 are a normal session establishment for a 
>> BFCP-only session (INVITE/200/ACK). Messages 15 through 20 
>> are the call re-attempt, which establishes a normal voice 
>> call (INVITE/180/PRACK/200/200/ACK). Messages 22 and 23 tear 
>> down the BFCP-only session (BYE/200).
>>
>> Does that make the proposed mechanism clearer?
>>
>> /a
>>
>>     


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 03:54:20 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbB8x-00010G-AF; Tue, 10 Apr 2007 03:51:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbB8w-000108-72
	for sipping@ietf.org; Tue, 10 Apr 2007 03:51:58 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbB8q-0004UT-LU
	for sipping@ietf.org; Tue, 10 Apr 2007 03:51:58 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	F0FC6213AC; Tue, 10 Apr 2007 09:51:43 +0200 (CEST)
X-AuditID: c1b4fb3e-ad1e9bb0000061ca-b9-461b420f8793 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E2478213D7; Tue, 10 Apr 2007 09:51:43 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 10 Apr 2007 09:51:43 +0200
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
Subject: RE: [Sipping] Re: draft-holmberg-sipping-199-00.txt
Date: Tue, 10 Apr 2007 09:51:43 +0200
Message-ID: <7374777208BDC7449D5620EF94232567033AD311@esealmw113.eemea.ericsson.se>
In-Reply-To: <200704092049.l39KnG1p014767@dragon.ariadne.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Re: draft-holmberg-sipping-199-00.txt
Thread-Index: Acd66KxgdE7n8l6RSxOZasxCVza1VAAWv61A
From: "Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
To: <Dale.Worley@comcast.net>,
	<sipping@ietf.org>
X-OriginalArrivalTime: 10 Apr 2007 07:51:43.0833 (UTC)
	FILETIME=[14FB6C90:01C77B45]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


Hi,

>>Because, in some cases 199 may be useful to peopleeven if=20
>>they don't know whe IP source information etc for a stream associated
with the
>>early dialog. "Resource" may have different meaning for different
applications, access types and network architectures.
>=20
>Well, off the top of my head, I don't see any real usefulness=20
>of 199 unless the UAC can use it to terminate consideration=20
>of a media stream.  So to make it worth moving forward, we=20
>either need to find another reason that it's useful, or work=20
>out the media stream correlation.

You may be able to free stream related resources even if you are not
able to associate the stream with the dialog. For example, if you have
reserved codec X only for the stream that is terminated, you know that
you can free the resources associated with that codec.

Another use-case is pre-conditions. When the dialog is terminated, you
can terminate any procedures related to pre-conditions for that dialog.

Another use-case is in-band security negotiation, which you can
terminate when the dialog is terminated. Yes, in this case you need to
be able to associate the dialog with the media.

Another use-case is where the P-Early-Media header is used. A UA may
trigger different actions depending on whether the header has been used
for a specific dialog.

During the early media discussions in Prague it was indicated that we
need to start working on a mechanism to associate dialogs with media,
and I strongly support that initiative. But, again, I would like to
handle it as a separate item, because it's not only related to 199.

Regards,

Christer

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 09:10:13 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbG5m-0005M8-Js; Tue, 10 Apr 2007 09:09:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbG5l-0005M3-QW
	for sipping@ietf.org; Tue, 10 Apr 2007 09:09:01 -0400
Received: from an-out-0708.google.com ([209.85.132.241])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbG5k-0005aj-JT
	for sipping@ietf.org; Tue, 10 Apr 2007 09:09:01 -0400
Received: by an-out-0708.google.com with SMTP id d30so2083185and
	for <sipping@ietf.org>; Tue, 10 Apr 2007 06:09:00 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=l3+4hV3vLRrnVqBBXXmUQZtZqbSNWPcfZIJA/RNZ4z14B1/XSulmFw1ybKhiJdHvQZ2QLf+QfqRx37CsqQK0hte/9G0ebXGWGCmEGXZNOh8Axvb4mtOrB5+gwCpjtlFImPPPhUX3Y5ddpGp6pteuBkdFYk/iCocbcYZXp8pW6NQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=pZTyY08nRto7gu4I2IVQXFFGCVYnZXzLURA9p5rF9ByUVz0eMeIkPLmZGfo6GrlzLmlrBDAiXdkC/EXi1roSf+vjK7V1RT9IhZgI5SKEys6fJplHOX3UB33ohtU69Sxi8+JewTxHkpaCmttsrvEO63PQtUcdvdqZ+EEz20rok7w=
Received: by 10.100.10.20 with SMTP id 20mr4848676anj.1176210540181;
	Tue, 10 Apr 2007 06:09:00 -0700 (PDT)
Received: by 10.100.189.14 with HTTP; Tue, 10 Apr 2007 06:08:59 -0700 (PDT)
Message-ID: <458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>
Date: Tue, 10 Apr 2007 15:08:59 +0200
From: "Xavier Marjou" <xavier.marjou@orange-ftgroup.com>
To: "Adam Roach" <adam@nostrum.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
In-Reply-To: <46154996.50305@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46154996.50305@nostrum.com>
X-Google-Sender-Auth: 8a955b2533ca35f3
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

>    3. "We don't want to add another protocol."

Although I understand motivations to re-use BFCP, I am in favor of a
SIP-only solution, based on the following considerations:

- First, as some people raised it, there's also some analogy between
CCBS and Presence. Should Presence have been integrated into a media
stream (eg: XMPP stream negotiated by SIP) or based on SIP signalling
only? This was debatable as the 2 choices seem technically feasible.
Nevertheless, the situation is that Presence is definitely possible
with SIP signalling only. Now, can we blame a CCBS solution based on a
similar approach?

- BFCP used as a media stream makes sense to control media streams.
Using a media stream (BFCP) to implement CCBS, the media stream would
control SIP signalling actions. I'm not sure wether we want to go in
that direction. You already gave 2 issues that have been raised.
Though I have no other example coming to my mind, we may encounter
more interaction issues of this kind by dispatching controlling
between SIP and a media stream.

- With a SIP only approach, we can hope for a single draft. With a
BFCP approach, we will probably need drafts in XCON, MMUSIC, and
perhaps also in SIPPING and MEDIACTRL, which means a lot of time and
efforts before having a solution for this nice feature.

Xavier

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 09:26:45 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbGMJ-0001ku-Pq; Tue, 10 Apr 2007 09:26:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbGMI-0001kl-7W
	for sipping@ietf.org; Tue, 10 Apr 2007 09:26:06 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbGMG-0000Gm-Ta
	for sipping@ietf.org; Tue, 10 Apr 2007 09:26:06 -0400
Received: from [192.168.0.102] (ppp-70-244-81-252.dsl.rcsntx.swbell.net
	[70.244.81.252]) (authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3ADQ2x0058803
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 10 Apr 2007 08:26:03 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461B8FB7.3000903@nostrum.com>
Date: Tue, 10 Apr 2007 08:23:03 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.8 (X11/20061107)
MIME-Version: 1.0
To: Xavier Marjou <xavier.marjou@orange-ftgroup.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com>
	<458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>
In-Reply-To: <458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.244.81.252 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Xavier Marjou wrote:
>>    3. "We don't want to add another protocol."
>
> Although I understand motivations to re-use BFCP, I am in favor of a
> SIP-only solution, based on the following considerations:
>
> - First, as some people raised it, there's also some analogy between
> CCBS and Presence.

Inasmuch as a system that properly utilizes presence doesn't need a call 
completion service, this is true. That's where the analogy lies, and one 
shouldn't read too much into it in terms of what a solution might look 
like that implements call completion *without* presence information.

> Should Presence have been integrated into a media
> stream (eg: XMPP stream negotiated by SIP) or based on SIP signalling
> only? This was debatable as the 2 choices seem technically feasible.
> Nevertheless, the situation is that Presence is definitely possible
> with SIP signalling only.

Yes, and we did so by adding a set of methods -- because none of the 
existing SIP methods had appropriate semantics for subscriptions.

> Now, can we blame a CCBS solution based on a
> similar approach?

Yes, we can. In early conversations on the call completion service, I 
clearly pointed out that adding a new method (or set of methods) to SIP 
for queue manipulation would be a potential solution to the problem.

The key point being that none of the existing SIP methods have 
appropriate semantics for queue manipulation. If you want to do this in 
SIP, you'll need to add one or more new methods.

> - BFCP used as a media stream makes sense to control media streams.
> Using a media stream (BFCP) to implement CCBS, the media stream would
> control SIP signalling actions. I'm not sure wether we want to go in
> that direction. You already gave 2 issues that have been raised.

I gave two _misconceptions_ that have been voiced and corrected. They 
are not valid objections.

> Though I have no other example coming to my mind, we may encounter
> more interaction issues of this kind by dispatching controlling
> between SIP and a media stream.

And we know for a *fact* that implicit side effects and crafting single 
operations with multiple, disjoint effects *does* cause problems, with a 
track record of exactly how. (I cited these in my initial mail on this 
thread; you can go back to read them there).


> - With a SIP only approach, we can hope for a single draft. With a
> BFCP approach, we will probably need drafts in XCON, MMUSIC, and
> perhaps also in SIPPING and MEDIACTRL, which means a lot of time and
> efforts before having a solution for this nice feature.


XCON: probably not. I'll talk to the XCON chairs about whether this 
would fall under their charter. :)  BFCP isn't limited to XCON for 
extensions; this could (and probably would) be done in SIPPING.

MMUSIC: True.

SIPPING: True.

MEDIACTRL: Um.... no.

So, yes, we do end up adding one more working group to the mix -- but 
that hardly seems a valid reason to head down a path that we know is 
technically wrong.

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 09:58:03 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbGqb-0004Nl-Gf; Tue, 10 Apr 2007 09:57:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbGqY-0004NJ-GU
	for sipping@ietf.org; Tue, 10 Apr 2007 09:57:22 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbGqR-0007lf-OM
	for sipping@ietf.org; Tue, 10 Apr 2007 09:57:22 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	360832057A; Tue, 10 Apr 2007 15:57:13 +0200 (CEST)
X-AuditID: c1b4fb3c-a9cedbb0000073d5-99-461b97b9e681 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	13555203D1; Tue, 10 Apr 2007 15:57:13 +0200 (CEST)
Received: from esealmw106.eemea.ericsson.se ([153.88.200.69]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 10 Apr 2007 15:57:12 +0200
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
Subject: RE: [Sipping] Session Establishment Efficiency Rate
Date: Tue, 10 Apr 2007 15:57:11 +0200
Message-ID: <97F2AD7AA4EAD948827639B06CF2745FCC6640@esealmw106.eemea.ericsson.se>
In-Reply-To: <3BC5D44AB71A754FAE3CA68A7597EABEB7BB25@ZANEVS03.cc-ntd1.covad.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Session Establishment Efficiency Rate
thread-index: AcdXYkku4CAgr+eHTe2Vtg4MEn4t7AH1mCVwBKfN+4AAR6J0cAC1rfJgALddljAAsnOOIA==
From: "Marian Delkinov \(LN/EAB\)" <marian.delkinov@ericsson.com>
To: "Fardid, Reza" <RFardid@Covad.COM>,
	"Daryl Malas" <daryl@level3.net>
X-OriginalArrivalTime: 10 Apr 2007 13:57:12.0986 (UTC)
	FILETIME=[23C69FA0:01C77B78]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Reza,

As far as I know the standard telephony - it functions a bit
differently. For instance if a user activates a service as "Call
Diversion" (similar to redirect in SIP), it's the network that handles
that hidden for the calling party, i.e. the caller does not need to dial
another number. And when such case occurs, in terms of PSTN for  the
calling party it's 1 call (1 seizure produced) only. Or in NER formula
you will have:

(1 answer, or RNA, or BUSY etc)/ 1 call =3D 100% NER

If we try to apply same to SIP. When redirect is received, the UA has to
send another INVITE, right? (Tell me if I'm wrong). And if we count the
300 code as network failure, and assume the second INVITE is successful,
then we have:

1 OK /2 #INVITE =3D 50% SEER, which IMO isn't correct. Do you agree, or
please explain.

Best regards!
Mario.

-----Original Message-----
From: Fardid, Reza [mailto:RFardid@Covad.COM]=20
Sent: Monday, 09 April, 2007 20:05
To: Marian Delkinov (LN/EAB); Daryl Malas
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Mario,

IMO, if the objective is to eliminate called party behavior from ASR
(and SER), minimally the following response codes need to be excluded:
User Busy		~480
RNA			~486
Busy Everywhere	~600

I fail to see how exclusion of 3xx, other 4xx, and 6xx codes (with the
possible exception of 603) will serve this objective. =20

It appears that the metric you are proposing has a much broader scope.
Perhaps, the confusion is caused by the inclusion of "user agent"
behavior in the definition of SEER, which should only exclude the
effects of "called party" behavior.

Regards,
-Reza

	=09





-----Original Message-----
From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
Sent: Tuesday, April 03, 2007 3:28 AM
To: Fardid, Reza; Daryl Malas
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Reza,=20

Exactly because of the analogy with NER and the meaning it has as
telephony metric I wanted to make clear the right counters, including
for release codes, are used to achieve the same meaning in SIP. I didn't
understand for when you foresee the implementation?

Best regards!
Mario.

-----Original Message-----
From: Fardid, Reza [mailto:RFardid@Covad.COM]
Sent: Friday, 30 March, 2007 22:02
To: Marian Delkinov (LN/EAB); Daryl Malas
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Mario,

What I had in mind when I proposed inclusion of SEER in this draft was a
SIP performance metric analogous to NER in the PSTN, within the
framework defined by Daryl:

Telephony Metric/Standard (ITU-T, BellCore, etc.) =3D=3D> SIP ETE Metric

Clearly some SIP metrics defined in this draft do not have a telephony
counterpart.  For the rest, IMO, it is good to stay within the above
framework and leave exclusion/inclusion of specific release codes from
defined metrics to implementation.

Regards,
Reza Fardid
Covad Communications


-----Original Message-----
From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
Sent: Thursday, March 29, 2007 1:07 AM
To: Daryl Malas
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Hi Daryl,

I haven't got your opinion about my comments on the SEER definition.
Have you considered them?=20
Would also be interested to know when a finalized document on the
performance metrics can be released.=20

Thanks!

Best regards!
Mario.

-----Original Message-----
From: Marian Delkinov (LN/EAB)
Sent: Monday, 05 March, 2007 17:06
To: 'Daryl Malas'
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Hi Daryl,

In principle, I agree with you in case we considered this from a user
perspective - then 3xx is not final. However my idea behind including
the 3xx codes was based on the involvement of "#Invite" in the formula.
If a 3xx code would result in sending a new Invite, then it sounds
logical to me to add the 3xx codes in the numerator. (NB: RFC3261
defines 3xx responses as "final" for the SIP transaction, ref. to page
21, Final Response).

Best regards!
Mario.

=20

-----Original Message-----
From: Daryl Malas [mailto:daryl@level3.net]
Sent: Friday, 23 February, 2007 17:00
To: Marian Delkinov (LN/EAB)
Cc: sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

I don't think 3xx codes should be included, since they would not be
considered a "Final" release cause code.  --Daryl

On Fri, 2007-02-23 at 12:22 +0100, Marian Delkinov (LN/EAB) wrote:
> Hi,
>=20
> If the Network Efficiency Rate is designed to express the ability of=20
> the network to deliver calls (in SIP terms one should perhaps say=20
> "establish sessions"), I think that it might be reasonable to include=20
> few more cases (cause codes) in the numerator: e.g. all redirection=20
> 3xx codes, all 4xx except 408 codes and all 6xx codes. (If you agree=20
> that those are the ones that exclude network failures, congestion and=20
> any other network malfunction).
>=20
> Actually it sounds fair to me if it's the opposite of the Ineffective=20
> Session Attempts (ISA):
> SEER% =3D
> 	   Total # of Invite Requests - # of ISA
> ---------------------------------------------------- x 100
> 	   Total # of Invite Requests
>=20
> What do you think?
>=20
> Best regards!
> Mario.
>=20
> -----Original Message-----
> From: Daryl Malas [mailto:daryl@level3.net]
> Sent: Friday, 23 February, 2007 01:14
> To: sipping@ietf.org
> Subject: [Sipping] Session Establishment Efficiency Rate
>=20
> A couple more people have expressed to me that this adaptation of the=20
> ITU-T E.411 Network Efficiency Rate metric is very valuable.  The=20
> snapshot of the metric from the draft is:
>=20
> "This metric is similar to Session Establishment Rate, but it is=20
> intended to exclude the effects of customer behavior and user agent=20
> behavior.  Essentially, the attempts resulting with a final cause code

> of 480, 486, and 600 would be added to the SER numerator."
>=20
> Does anyone else want to see this metric in the draft?  I personally=20
> think it is an interesting metric.
>=20
> Thanks...
>=20
> --Daryl
>=20
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use=20
> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.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

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 10:08:13 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbH0e-0008VC-FK; Tue, 10 Apr 2007 10:07:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbH0c-0008V6-CX
	for sipping@ietf.org; Tue, 10 Apr 2007 10:07:46 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbH0a-0002bg-Tr
	for sipping@ietf.org; Tue, 10 Apr 2007 10:07:46 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 10 Apr 2007 10:07:45 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3AE7img007120; 
	Tue, 10 Apr 2007 10:07:44 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l3AE7ilG003342; 
	Tue, 10 Apr 2007 14:07:44 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 10 Apr 2007 10:07:34 -0400
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
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Tue, 10 Apr 2007 10:07:29 -0400
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <461B8FB7.3000903@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
Thread-Index: Acd7c/feixiTz2y8TxGdWcT9a6Tg7wABJpgg
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>
	<461B8FB7.3000903@nostrum.com>
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Adam Roach" <adam@nostrum.com>,
	"Xavier Marjou" <xavier.marjou@orange-ftgroup.com>
X-OriginalArrivalTime: 10 Apr 2007 14:07:34.0213 (UTC)
	FILETIME=[960E5750:01C77B79]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4378; t=1176214064;
	x=1177078064; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mhammer@cisco.com;
	z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com>
	|Subject:=20RE=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defense=20of=
	20Explicit=20Operations |Sender:=20
	|To:=20=22Adam=20Roach=22=20<adam@nostrum.com>,
	=0A=20=20=20=20=20=20=20=2
	0=22Xavier=20Marjou=22=20<xavier.marjou@orange-ftgroup.com>;
	bh=YawJ65HoKuxcOPmXTk8XpVvJyPmVwpKYAateTTuVrK4=;
	b=eThgiPeCrvzpf0vFVZs7bJDE142s28TCS3+8PH+nIWTdMMQvqIQGU6SarzAcoQI9xaDt3Fgu
	H+DuUrUhNMc2eR/iASRWZDGxMSa7S5+oLocIkMzHOhtNsJLfRBmGLHeX;
Authentication-Results: rtp-dkim-1; header.From=mhammer@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Adam,

One final comment from me.  I originally went with presence because when
you step back and look at what the CCBS or CCNR features are all about
it is about the presence of the caller and called parties and the
ability to accept a call.  Although you have shown that media control
can be used to achieve the same effect, I think that there has not been
sufficient thought put into a presence-based approach.

Mike


> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]=20
> Sent: Tuesday, April 10, 2007 9:23 AM
> To: Xavier Marjou
> Cc: SIPPING WG
> Subject: Re: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
> Xavier Marjou wrote:
> >>    3. "We don't want to add another protocol."
> >
> > Although I understand motivations to re-use BFCP, I am in=20
> favor of a=20
> > SIP-only solution, based on the following considerations:
> >
> > - First, as some people raised it, there's also some=20
> analogy between=20
> > CCBS and Presence.
>=20
> Inasmuch as a system that properly utilizes presence doesn't=20
> need a call completion service, this is true. That's where=20
> the analogy lies, and one shouldn't read too much into it in=20
> terms of what a solution might look like that implements call=20
> completion *without* presence information.
>=20
> > Should Presence have been integrated into a media stream (eg: XMPP=20
> > stream negotiated by SIP) or based on SIP signalling only? This was=20
> > debatable as the 2 choices seem technically feasible.
> > Nevertheless, the situation is that Presence is definitely possible=20
> > with SIP signalling only.
>=20
> Yes, and we did so by adding a set of methods -- because none=20
> of the existing SIP methods had appropriate semantics for=20
> subscriptions.
>=20
> > Now, can we blame a CCBS solution based on a similar approach?
>=20
> Yes, we can. In early conversations on the call completion=20
> service, I clearly pointed out that adding a new method (or=20
> set of methods) to SIP for queue manipulation would be a=20
> potential solution to the problem.
>=20
> The key point being that none of the existing SIP methods=20
> have appropriate semantics for queue manipulation. If you=20
> want to do this in SIP, you'll need to add one or more new methods.
>=20
> > - BFCP used as a media stream makes sense to control media streams.
> > Using a media stream (BFCP) to implement CCBS, the media=20
> stream would=20
> > control SIP signalling actions. I'm not sure wether we want=20
> to go in=20
> > that direction. You already gave 2 issues that have been raised.
>=20
> I gave two _misconceptions_ that have been voiced and=20
> corrected. They are not valid objections.
>=20
> > Though I have no other example coming to my mind, we may encounter=20
> > more interaction issues of this kind by dispatching controlling=20
> > between SIP and a media stream.
>=20
> And we know for a *fact* that implicit side effects and=20
> crafting single operations with multiple, disjoint effects=20
> *does* cause problems, with a track record of exactly how. (I=20
> cited these in my initial mail on this thread; you can go=20
> back to read them there).
>=20
>=20
> > - With a SIP only approach, we can hope for a single draft. With a=20
> > BFCP approach, we will probably need drafts in XCON, MMUSIC, and=20
> > perhaps also in SIPPING and MEDIACTRL, which means a lot of=20
> time and=20
> > efforts before having a solution for this nice feature.
>=20
>=20
> XCON: probably not. I'll talk to the XCON chairs about=20
> whether this would fall under their charter. :)  BFCP isn't=20
> limited to XCON for extensions; this could (and probably=20
> would) be done in SIPPING.
>=20
> MMUSIC: True.
>=20
> SIPPING: True.
>=20
> MEDIACTRL: Um.... no.
>=20
> So, yes, we do end up adding one more working group to the=20
> mix -- but that hardly seems a valid reason to head down a=20
> path that we know is technically wrong.
>=20
> /a
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP=20
> Use sip-implementors@cs.columbia.edu for questions on current=20
> sip Use sip@ietf.org for new developments of core SIP
>=20

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 11:49:59 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbIaZ-00018L-Do; Tue, 10 Apr 2007 11:48:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbIaX-00018D-Hp
	for sipping@ietf.org; Tue, 10 Apr 2007 11:48:57 -0400
Received: from sccrmhc14.comcast.net ([63.240.77.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbIaW-0006xm-AW
	for sipping@ietf.org; Tue, 10 Apr 2007 11:48:57 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (sccrmhc14) with ESMTP
	id <200704101548550140025j31e>; Tue, 10 Apr 2007 15:48:55 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l3AFmtLv005705
	for <sipping@ietf.org>; Tue, 10 Apr 2007 11:48:55 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l3AFmtHT005701;
	Tue, 10 Apr 2007 11:48:55 -0400
Date: Tue, 10 Apr 2007 11:48:55 -0400
Message-Id: <200704101548.l3AFmtHT005701@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <461B8FB7.3000903@nostrum.com> (adam@nostrum.com)
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com>
	<458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>
	<461B8FB7.3000903@nostrum.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: Adam Roach <adam@nostrum.com>

   And we know for a *fact* that implicit side effects and crafting single 
   operations with multiple, disjoint effects *does* cause problems, with a 
   track record of exactly how. (I cited these in my initial mail on this 
   thread; you can go back to read them there).

Worse, we're talking about adding side effects to a method that
previously did not have them.  That pretty much guarantees that any
generic implementation of SUBSCRIBE/NOTIFY will have to be changed.

Dale

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 12:55:55 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbJcd-0003le-Nk; Tue, 10 Apr 2007 12:55:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbJcc-0003lZ-MU
	for sipping@ietf.org; Tue, 10 Apr 2007 12:55:10 -0400
Received: from hme1.july.broomfield1.level3.net ([209.245.18.8]
	helo=f4bb49-05.idc1.level3.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbJcc-0004GH-7J
	for sipping@ietf.org; Tue, 10 Apr 2007 12:55:10 -0400
Received: from montag.eng.level3.com (montag.eng.l3.com [10.1.68.57])
	by f4bb49-05.idc1.level3.com (8.12.10/8.12.10) with ESMTP id
	l3AGt3oK007180; Tue, 10 Apr 2007 16:55:03 GMT
Subject: RE: [Sipping] Session Establishment Efficiency Rate
From: Daryl Malas <daryl@level3.net>
To: "Marian Delkinov (LN/EAB)" <marian.delkinov@ericsson.com>
In-Reply-To: <97F2AD7AA4EAD948827639B06CF2745FCC6640@esealmw106.eemea.ericsson.se>
References: <97F2AD7AA4EAD948827639B06CF2745FCC6640@esealmw106.eemea.ericsson.se>
Content-Type: text/plain
Date: Tue, 10 Apr 2007 11:07:54 -0600
Message-Id: <1176224874.17141.115.camel@montag.eng.level3.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.0 (2.6.0-1) 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c
Cc: "Fardid, Reza" <RFardid@Covad.COM>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

It sends a new INVITE, but the call id doesn't change.  This allows
tools to identify it as the same call or 1 OK/ 1 INVITE = 100% SER.

--Daryl

On Tue, 2007-04-10 at 15:57 +0200, Marian Delkinov (LN/EAB) wrote:
> Reza,
> 
> As far as I know the standard telephony - it functions a bit
> differently. For instance if a user activates a service as "Call
> Diversion" (similar to redirect in SIP), it's the network that handles
> that hidden for the calling party, i.e. the caller does not need to dial
> another number. And when such case occurs, in terms of PSTN for  the
> calling party it's 1 call (1 seizure produced) only. Or in NER formula
> you will have:
> 
> (1 answer, or RNA, or BUSY etc)/ 1 call = 100% NER
> 
> If we try to apply same to SIP. When redirect is received, the UA has to
> send another INVITE, right? (Tell me if I'm wrong). And if we count the
> 300 code as network failure, and assume the second INVITE is successful,
> then we have:
> 
> 1 OK /2 #INVITE = 50% SEER, which IMO isn't correct. Do you agree, or
> please explain.
> 
> Best regards!
> Mario.
> 
> -----Original Message-----
> From: Fardid, Reza [mailto:RFardid@Covad.COM] 
> Sent: Monday, 09 April, 2007 20:05
> To: Marian Delkinov (LN/EAB); Daryl Malas
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
> 
> Mario,
> 
> IMO, if the objective is to eliminate called party behavior from ASR
> (and SER), minimally the following response codes need to be excluded:
> User Busy		~480
> RNA			~486
> Busy Everywhere	~600
> 
> I fail to see how exclusion of 3xx, other 4xx, and 6xx codes (with the
> possible exception of 603) will serve this objective.  
> 
> It appears that the metric you are proposing has a much broader scope.
> Perhaps, the confusion is caused by the inclusion of "user agent"
> behavior in the definition of SEER, which should only exclude the
> effects of "called party" behavior.
> 
> Regards,
> -Reza
> 
> 		
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> Sent: Tuesday, April 03, 2007 3:28 AM
> To: Fardid, Reza; Daryl Malas
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
> 
> Reza, 
> 
> Exactly because of the analogy with NER and the meaning it has as
> telephony metric I wanted to make clear the right counters, including
> for release codes, are used to achieve the same meaning in SIP. I didn't
> understand for when you foresee the implementation?
> 
> Best regards!
> Mario.
> 
> -----Original Message-----
> From: Fardid, Reza [mailto:RFardid@Covad.COM]
> Sent: Friday, 30 March, 2007 22:02
> To: Marian Delkinov (LN/EAB); Daryl Malas
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
> 
> Mario,
> 
> What I had in mind when I proposed inclusion of SEER in this draft was a
> SIP performance metric analogous to NER in the PSTN, within the
> framework defined by Daryl:
> 
> Telephony Metric/Standard (ITU-T, BellCore, etc.) ==> SIP ETE Metric
> 
> Clearly some SIP metrics defined in this draft do not have a telephony
> counterpart.  For the rest, IMO, it is good to stay within the above
> framework and leave exclusion/inclusion of specific release codes from
> defined metrics to implementation.
> 
> Regards,
> Reza Fardid
> Covad Communications
> 
> 
> -----Original Message-----
> From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> Sent: Thursday, March 29, 2007 1:07 AM
> To: Daryl Malas
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
> 
> Hi Daryl,
> 
> I haven't got your opinion about my comments on the SEER definition.
> Have you considered them? 
> Would also be interested to know when a finalized document on the
> performance metrics can be released. 
> 
> Thanks!
> 
> Best regards!
> Mario.
> 
> -----Original Message-----
> From: Marian Delkinov (LN/EAB)
> Sent: Monday, 05 March, 2007 17:06
> To: 'Daryl Malas'
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
> 
> Hi Daryl,
> 
> In principle, I agree with you in case we considered this from a user
> perspective - then 3xx is not final. However my idea behind including
> the 3xx codes was based on the involvement of "#Invite" in the formula.
> If a 3xx code would result in sending a new Invite, then it sounds
> logical to me to add the 3xx codes in the numerator. (NB: RFC3261
> defines 3xx responses as "final" for the SIP transaction, ref. to page
> 21, Final Response).
> 
> Best regards!
> Mario.
> 
>  
> 
> -----Original Message-----
> From: Daryl Malas [mailto:daryl@level3.net]
> Sent: Friday, 23 February, 2007 17:00
> To: Marian Delkinov (LN/EAB)
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
> 
> I don't think 3xx codes should be included, since they would not be
> considered a "Final" release cause code.  --Daryl
> 
> On Fri, 2007-02-23 at 12:22 +0100, Marian Delkinov (LN/EAB) wrote:
> > Hi,
> > 
> > If the Network Efficiency Rate is designed to express the ability of 
> > the network to deliver calls (in SIP terms one should perhaps say 
> > "establish sessions"), I think that it might be reasonable to include 
> > few more cases (cause codes) in the numerator: e.g. all redirection 
> > 3xx codes, all 4xx except 408 codes and all 6xx codes. (If you agree 
> > that those are the ones that exclude network failures, congestion and 
> > any other network malfunction).
> > 
> > Actually it sounds fair to me if it's the opposite of the Ineffective 
> > Session Attempts (ISA):
> > SEER% =
> > 	   Total # of Invite Requests - # of ISA
> > ---------------------------------------------------- x 100
> > 	   Total # of Invite Requests
> > 
> > What do you think?
> > 
> > Best regards!
> > Mario.
> > 
> > -----Original Message-----
> > From: Daryl Malas [mailto:daryl@level3.net]
> > Sent: Friday, 23 February, 2007 01:14
> > To: sipping@ietf.org
> > Subject: [Sipping] Session Establishment Efficiency Rate
> > 
> > A couple more people have expressed to me that this adaptation of the 
> > ITU-T E.411 Network Efficiency Rate metric is very valuable.  The 
> > snapshot of the metric from the draft is:
> > 
> > "This metric is similar to Session Establishment Rate, but it is 
> > intended to exclude the effects of customer behavior and user agent 
> > behavior.  Essentially, the attempts resulting with a final cause code
> 
> > of 480, 486, and 600 would be added to the SER numerator."
> > 
> > Does anyone else want to see this metric in the draft?  I personally 
> > think it is an interesting metric.
> > 
> > Thanks...
> > 
> > --Daryl
> > 
> > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.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
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 13:01:02 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbJiF-0007yT-MC; Tue, 10 Apr 2007 13:00:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbJiE-0007yA-4Y
	for sipping@ietf.org; Tue, 10 Apr 2007 13:00:58 -0400
Received: from hme1.july.broomfield1.level3.net ([209.245.18.8]
	helo=f4bb49-05.idc1.level3.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbJiC-0005l9-RD
	for sipping@ietf.org; Tue, 10 Apr 2007 13:00:58 -0400
Received: from montag.eng.level3.com (montag.eng.l3.com [10.1.68.57])
	by f4bb49-05.idc1.level3.com (8.12.10/8.12.10) with ESMTP id
	l3AH0uoK008178 for <sipping@ietf.org>; Tue, 10 Apr 2007 17:00:56 GMT
Subject: [Sipping] Performance metrics for media
From: Daryl Malas <daryl@level3.net>
To: sipping@ietf.org
Content-Type: text/plain
Date: Tue, 10 Apr 2007 11:13:46 -0600
Message-Id: <1176225227.17141.122.camel@montag.eng.level3.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.0 (2.6.0-1) 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I have heard several comments regarding the value of understanding how
long it takes from the time a 200 OK (w/ SDP) is received from the UAS
to the time bi-direction (or even uni-directional) media is actually
flowing between the two UA's.  I have specifically focused my draft on
the signaling only, excluding all media correlations.  Because SIP
signaling can occur successfully in many different manners without ever
requesting an RTP session to be established, I am having a hard time
understanding the value of doing this.  It doesn't mean a company/vendor
can't do this, but should it be incorporated into this draft.  I am
already hearing grumblings that there are too many metrics in the
current draft.

Also, adding a "media" metric, I believe, will simply open a big can of
worms.

--Daryl


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 13:35:55 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbKFV-0002Cj-8i; Tue, 10 Apr 2007 13:35:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbKFT-0002Ce-TM
	for sipping@ietf.org; Tue, 10 Apr 2007 13:35:19 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbKFS-0004XE-KM
	for sipping@ietf.org; Tue, 10 Apr 2007 13:35:19 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3AHZGjX070847
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 10 Apr 2007 12:35:16 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461BCAD7.1020001@nostrum.com>
Date: Tue, 10 Apr 2007 12:35:19 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: "Michael Hammer (mhammer)" <mhammer@cisco.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>
	<461B8FB7.3000903@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: SIPPING WG <sipping@ietf.org>,
	Xavier Marjou <xavier.marjou@orange-ftgroup.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Michael Hammer (mhammer) wrote:
> Adam,
>
> One final comment from me.  I originally went with presence because when
> you step back and look at what the CCBS or CCNR features are all about
> it is about the presence of the caller and called parties and the
> ability to accept a call.

I agree wholeheartedly. If there were a way to reliably subscribe to the 
presence state of a PSTN user, that would be the incontestable, obvious 
way to implement this. While my TCAP knowledge is rusty, I don't think 
there's a way to do this directly.

>   Although you have shown that media control
> can be used to achieve the same effect, I think that there has not been
> sufficient thought put into a presence-based approach.
>   

As Francois and I discussed earlier, it would be a rather 
straightforward exercise to define this service using existing tools, 
*except* for the queue management aspect of the service. That's why I've 
been making arguments that an alternate way to clear the logjam would be 
removal of the queueing requirement.

If we can't do that, we need some mechanism to handle the queueing -- 
and SUBSCRIBE/NOTIFY aren't queue management methods.

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 13:43:55 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbKNG-0006Yf-0y; Tue, 10 Apr 2007 13:43:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbKNF-0006YV-0u
	for sipping@ietf.org; Tue, 10 Apr 2007 13:43:21 -0400
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbKND-0006YZ-OR
	for sipping@ietf.org; Tue, 10 Apr 2007 13:43:21 -0400
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l3AHhJiw014535; 
	Tue, 10 Apr 2007 12:43:19 -0500 (CDT)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90])
	by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l3AHhIA04730; Tue, 10 Apr 2007 12:43:19 -0500 (CDT)
Message-ID: <461BCCB6.6090009@alcatel-lucent.com>
Date: Tue, 10 Apr 2007 12:43:18 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>	<461B8FB7.3000903@nostrum.com>	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>
	<461BCAD7.1020001@nostrum.com>
In-Reply-To: <461BCAD7.1020001@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Adam Roach wrote:
> I agree wholeheartedly. If there were a way to reliably subscribe to the 
> presence state of a PSTN user, that would be the incontestable, obvious 
> way to implement this. While my TCAP knowledge is rusty, I don't think 
> there's a way to do this directly.

There was work done in the SPIRITS WG that enabled presence
state of a PSTN user using SUBS/NOT event packages in rfc3910.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 14:00:09 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbKcX-0006ie-A7; Tue, 10 Apr 2007 13:59:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbKcW-0006iZ-0C
	for sipping@ietf.org; Tue, 10 Apr 2007 13:59:08 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbKcU-0001gV-Lm
	for sipping@ietf.org; Tue, 10 Apr 2007 13:59:07 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3AHx23e072070
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 10 Apr 2007 12:59:04 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461BD069.8050702@nostrum.com>
Date: Tue, 10 Apr 2007 12:59:05 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>	<461B8FB7.3000903@nostrum.com>	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>
	<461BCAD7.1020001@nostrum.com>
	<461BCCB6.6090009@alcatel-lucent.com>
In-Reply-To: <461BCCB6.6090009@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Vijay K. Gurbani wrote:
> Adam Roach wrote:
>> I agree wholeheartedly. If there were a way to reliably subscribe to 
>> the presence state of a PSTN user, that would be the incontestable, 
>> obvious way to implement this. While my TCAP knowledge is rusty, I 
>> don't think there's a way to do this directly.
>
> There was work done in the SPIRITS WG that enabled presence
> state of a PSTN user using SUBS/NOT event packages in rfc3910.
>

Ah, yes. By hooking into an SCP, it would certainly be possible to 
determine this information. Somehow I doubt that such a solution would 
be acceptable to TISPAN, since it requires significant software upgrades 
of the called-party end office equipment (even assuming it already has 
generic IN capabilities). Of course, we *could* ask our TISPAN or ETSI 
liaison whether this approach would meet their requirements -- except 
that we don't seem to have one.

  http://www.ietf.org/liaisonActivities.html

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 14:40:29 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbLGF-0003qn-ID; Tue, 10 Apr 2007 14:40:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbLGD-0003qe-IW
	for sipping@ietf.org; Tue, 10 Apr 2007 14:40:09 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbLG7-0002bq-Ln
	for sipping@ietf.org; Tue, 10 Apr 2007 14:40:09 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	10D4D21153; Tue, 10 Apr 2007 20:40:03 +0200 (CEST)
X-AuditID: c1b4fb3e-ae9ecbb0000061ca-ca-461bda02c124 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	DF8BD21042; Tue, 10 Apr 2007 20:40:02 +0200 (CEST)
Received: from esealmw106.eemea.ericsson.se ([153.88.200.69]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 10 Apr 2007 20:40:02 +0200
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
Subject: RE: [Sipping] Session Establishment Efficiency Rate
Date: Tue, 10 Apr 2007 20:39:59 +0200
Message-ID: <97F2AD7AA4EAD948827639B06CF2745FCC6787@esealmw106.eemea.ericsson.se>
In-Reply-To: <1176224874.17141.115.camel@montag.eng.level3.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Session Establishment Efficiency Rate
thread-index: Acd7kP360ozBkDrkSC2easx94joh7gAAiwjQ
From: "Marian Delkinov \(LN/EAB\)" <marian.delkinov@ericsson.com>
To: "Daryl Malas" <daryl@level3.net>
X-OriginalArrivalTime: 10 Apr 2007 18:40:02.0832 (UTC)
	FILETIME=[A697A100:01C77B9F]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 223e3c753032a50d5dc4443c921c3fcd
Cc: "Fardid, Reza" <RFardid@Covad.COM>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Daryl,

I understand what you mean and with the condition about the same Call
ID, I agree with it. The reason for my comments as  I wrote you earlier,
was the inclusion of #INVITE in the formula. What you are talking about
should perhaps be described as #Call Attempts. Because if we consider
all INVITEs with same Call ID as 1 call attempt and put that in the
formula, then everything fits on place.

In that case the definition would look:

SEER =3D (#Invite w/200 OK + #480 + #486 + #600)/# Total Call Attempts

(with note e.g: #Total Call Attempts =3D # distinct(Call_IDs)

What worries me yet is how we handle the forking.=20

Best regards!
Mario.
=20

-----Original Message-----
From: Daryl Malas [mailto:daryl@level3.net]=20
Sent: Tuesday, 10 April, 2007 19:08
To: Marian Delkinov (LN/EAB)
Cc: Fardid, Reza; sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

It sends a new INVITE, but the call id doesn't change.  This allows
tools to identify it as the same call or 1 OK/ 1 INVITE =3D 100% SER.

--Daryl

On Tue, 2007-04-10 at 15:57 +0200, Marian Delkinov (LN/EAB) wrote:
> Reza,
>=20
> As far as I know the standard telephony - it functions a bit=20
> differently. For instance if a user activates a service as "Call=20
> Diversion" (similar to redirect in SIP), it's the network that handles

> that hidden for the calling party, i.e. the caller does not need to=20
> dial another number. And when such case occurs, in terms of PSTN for =20
> the calling party it's 1 call (1 seizure produced) only. Or in NER=20
> formula you will have:
>=20
> (1 answer, or RNA, or BUSY etc)/ 1 call =3D 100% NER
>=20
> If we try to apply same to SIP. When redirect is received, the UA has=20
> to send another INVITE, right? (Tell me if I'm wrong). And if we count

> the 300 code as network failure, and assume the second INVITE is=20
> successful, then we have:
>=20
> 1 OK /2 #INVITE =3D 50% SEER, which IMO isn't correct. Do you agree, =
or=20
> please explain.
>=20
> Best regards!
> Mario.
>=20
> -----Original Message-----
> From: Fardid, Reza [mailto:RFardid@Covad.COM]
> Sent: Monday, 09 April, 2007 20:05
> To: Marian Delkinov (LN/EAB); Daryl Malas
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
>=20
> Mario,
>=20
> IMO, if the objective is to eliminate called party behavior from ASR=20
> (and SER), minimally the following response codes need to be excluded:
> User Busy		~480
> RNA			~486
> Busy Everywhere	~600
>=20
> I fail to see how exclusion of 3xx, other 4xx, and 6xx codes (with the

> possible exception of 603) will serve this objective.
>=20
> It appears that the metric you are proposing has a much broader scope.
> Perhaps, the confusion is caused by the inclusion of "user agent"
> behavior in the definition of SEER, which should only exclude the=20
> effects of "called party" behavior.
>=20
> Regards,
> -Reza
>=20
> 	=09
>=20
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> Sent: Tuesday, April 03, 2007 3:28 AM
> To: Fardid, Reza; Daryl Malas
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
>=20
> Reza,
>=20
> Exactly because of the analogy with NER and the meaning it has as=20
> telephony metric I wanted to make clear the right counters, including=20
> for release codes, are used to achieve the same meaning in SIP. I=20
> didn't understand for when you foresee the implementation?
>=20
> Best regards!
> Mario.
>=20
> -----Original Message-----
> From: Fardid, Reza [mailto:RFardid@Covad.COM]
> Sent: Friday, 30 March, 2007 22:02
> To: Marian Delkinov (LN/EAB); Daryl Malas
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
>=20
> Mario,
>=20
> What I had in mind when I proposed inclusion of SEER in this draft was

> a SIP performance metric analogous to NER in the PSTN, within the=20
> framework defined by Daryl:
>=20
> Telephony Metric/Standard (ITU-T, BellCore, etc.) =3D=3D> SIP ETE =
Metric
>=20
> Clearly some SIP metrics defined in this draft do not have a telephony

> counterpart.  For the rest, IMO, it is good to stay within the above=20
> framework and leave exclusion/inclusion of specific release codes from

> defined metrics to implementation.
>=20
> Regards,
> Reza Fardid
> Covad Communications
>=20
>=20
> -----Original Message-----
> From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> Sent: Thursday, March 29, 2007 1:07 AM
> To: Daryl Malas
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
>=20
> Hi Daryl,
>=20
> I haven't got your opinion about my comments on the SEER definition.
> Have you considered them?=20
> Would also be interested to know when a finalized document on the=20
> performance metrics can be released.
>=20
> Thanks!
>=20
> Best regards!
> Mario.
>=20
> -----Original Message-----
> From: Marian Delkinov (LN/EAB)
> Sent: Monday, 05 March, 2007 17:06
> To: 'Daryl Malas'
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
>=20
> Hi Daryl,
>=20
> In principle, I agree with you in case we considered this from a user=20
> perspective - then 3xx is not final. However my idea behind including=20
> the 3xx codes was based on the involvement of "#Invite" in the
formula.
> If a 3xx code would result in sending a new Invite, then it sounds=20
> logical to me to add the 3xx codes in the numerator. (NB: RFC3261=20
> defines 3xx responses as "final" for the SIP transaction, ref. to page

> 21, Final Response).
>=20
> Best regards!
> Mario.
>=20
> =20
>=20
> -----Original Message-----
> From: Daryl Malas [mailto:daryl@level3.net]
> Sent: Friday, 23 February, 2007 17:00
> To: Marian Delkinov (LN/EAB)
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
>=20
> I don't think 3xx codes should be included, since they would not be=20
> considered a "Final" release cause code.  --Daryl
>=20
> On Fri, 2007-02-23 at 12:22 +0100, Marian Delkinov (LN/EAB) wrote:
> > Hi,
> >=20
> > If the Network Efficiency Rate is designed to express the ability of

> > the network to deliver calls (in SIP terms one should perhaps say=20
> > "establish sessions"), I think that it might be reasonable to=20
> > include few more cases (cause codes) in the numerator: e.g. all=20
> > redirection 3xx codes, all 4xx except 408 codes and all 6xx codes.=20
> > (If you agree that those are the ones that exclude network failures,

> > congestion and any other network malfunction).
> >=20
> > Actually it sounds fair to me if it's the opposite of the=20
> > Ineffective Session Attempts (ISA):
> > SEER% =3D
> > 	   Total # of Invite Requests - # of ISA
> > ---------------------------------------------------- x 100
> > 	   Total # of Invite Requests
> >=20
> > What do you think?
> >=20
> > Best regards!
> > Mario.
> >=20
> > -----Original Message-----
> > From: Daryl Malas [mailto:daryl@level3.net]
> > Sent: Friday, 23 February, 2007 01:14
> > To: sipping@ietf.org
> > Subject: [Sipping] Session Establishment Efficiency Rate
> >=20
> > A couple more people have expressed to me that this adaptation of=20
> > the ITU-T E.411 Network Efficiency Rate metric is very valuable. =20
> > The snapshot of the metric from the draft is:
> >=20
> > "This metric is similar to Session Establishment Rate, but it is=20
> > intended to exclude the effects of customer behavior and user agent=20
> > behavior.  Essentially, the attempts resulting with a final cause=20
> > code
>=20
> > of 480, 486, and 600 would be added to the SER numerator."
> >=20
> > Does anyone else want to see this metric in the draft?  I personally

> > think it is an interesting metric.
> >=20
> > Thanks...
> >=20
> > --Daryl
> >=20
> >=20
> >=20
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use=20
> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 14:41:11 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbLHD-0004B5-2P; Tue, 10 Apr 2007 14:41:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbLHC-0004AM-86
	for sipping@ietf.org; Tue, 10 Apr 2007 14:41:10 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbLHA-0002nW-U6
	for sipping@ietf.org; Tue, 10 Apr 2007 14:41:10 -0400
Received: from [64.101.173.113] ([64.101.173.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3AHlhgM023049
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 10 Apr 2007 12:47:44 -0500
In-Reply-To: <461BCAD7.1020001@nostrum.com>
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>
	<461B8FB7.3000903@nostrum.com>
	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>
	<461BCAD7.1020001@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <34668222-C8B1-41FE-9519-530FDFE92BFA@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Tue, 10 Apr 2007 13:40:55 -0500
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: Xavier Marjou <xavier.marjou@orange-ftgroup.com>,
	SIPPING WG <sipping@ietf.org>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 10, 2007, at 12:35 PM, Adam Roach wrote:


>
> If we can't do that, we need some mechanism to handle the queueing  
> -- and SUBSCRIBE/NOTIFY aren't queue management methods.
>

I've been pondering that assertion, and can't see why the queue  
modeled as a document with filtering on what part of the document is  
visible isn't a reasonable approach to an event package.

--
Dean


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 15:02:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbLbV-00077H-30; Tue, 10 Apr 2007 15:02:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbLbT-00075k-Jp
	for sipping@ietf.org; Tue, 10 Apr 2007 15:02:07 -0400
Received: from hme1.july.broomfield1.level3.net ([209.245.18.8]
	helo=f4bb49-05.idc1.level3.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbLbT-0002O5-3A
	for sipping@ietf.org; Tue, 10 Apr 2007 15:02:07 -0400
Received: from montag.eng.level3.com (montag.eng.l3.com [10.1.68.57])
	by f4bb49-05.idc1.level3.com (8.12.10/8.12.10) with ESMTP id
	l3AJ1soK003980; Tue, 10 Apr 2007 19:01:54 GMT
Subject: RE: [Sipping] Session Establishment Efficiency Rate
From: Daryl Malas <daryl@level3.net>
To: "Marian Delkinov (LN/EAB)" <marian.delkinov@ericsson.com>
In-Reply-To: <97F2AD7AA4EAD948827639B06CF2745FCC6787@esealmw106.eemea.ericsson.se>
References: <97F2AD7AA4EAD948827639B06CF2745FCC6787@esealmw106.eemea.ericsson.se>
Content-Type: text/plain
Date: Tue, 10 Apr 2007 13:14:45 -0600
Message-Id: <1176232485.17141.133.camel@montag.eng.level3.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.0 (2.6.0-1) 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
Cc: "Fardid, Reza" <RFardid@Covad.COM>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Okay...I think I understand your point.  The denominator needs to be
clarified in Section 3.6 and then relative to SEER.  It needs to make
sure it does not include INVITE's that are redirected or similar, as
this will skew the data.  Is this what you are referring to?

--Daryl

On Tue, 2007-04-10 at 20:39 +0200, Marian Delkinov (LN/EAB) wrote:
> Daryl,
> 
> I understand what you mean and with the condition about the same Call
> ID, I agree with it. The reason for my comments as  I wrote you earlier,
> was the inclusion of #INVITE in the formula. What you are talking about
> should perhaps be described as #Call Attempts. Because if we consider
> all INVITEs with same Call ID as 1 call attempt and put that in the
> formula, then everything fits on place.
> 
> In that case the definition would look:
> 
> SEER = (#Invite w/200 OK + #480 + #486 + #600)/# Total Call Attempts
> 
> (with note e.g: #Total Call Attempts = # distinct(Call_IDs)
> 
> What worries me yet is how we handle the forking. 
> 
> Best regards!
> Mario.
>  
> 
> -----Original Message-----
> From: Daryl Malas [mailto:daryl@level3.net] 
> Sent: Tuesday, 10 April, 2007 19:08
> To: Marian Delkinov (LN/EAB)
> Cc: Fardid, Reza; sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
> 
> It sends a new INVITE, but the call id doesn't change.  This allows
> tools to identify it as the same call or 1 OK/ 1 INVITE = 100% SER.
> 
> --Daryl
> 
> On Tue, 2007-04-10 at 15:57 +0200, Marian Delkinov (LN/EAB) wrote:
> > Reza,
> > 
> > As far as I know the standard telephony - it functions a bit 
> > differently. For instance if a user activates a service as "Call 
> > Diversion" (similar to redirect in SIP), it's the network that handles
> 
> > that hidden for the calling party, i.e. the caller does not need to 
> > dial another number. And when such case occurs, in terms of PSTN for  
> > the calling party it's 1 call (1 seizure produced) only. Or in NER 
> > formula you will have:
> > 
> > (1 answer, or RNA, or BUSY etc)/ 1 call = 100% NER
> > 
> > If we try to apply same to SIP. When redirect is received, the UA has 
> > to send another INVITE, right? (Tell me if I'm wrong). And if we count
> 
> > the 300 code as network failure, and assume the second INVITE is 
> > successful, then we have:
> > 
> > 1 OK /2 #INVITE = 50% SEER, which IMO isn't correct. Do you agree, or 
> > please explain.
> > 
> > Best regards!
> > Mario.
> > 
> > -----Original Message-----
> > From: Fardid, Reza [mailto:RFardid@Covad.COM]
> > Sent: Monday, 09 April, 2007 20:05
> > To: Marian Delkinov (LN/EAB); Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > 
> > Mario,
> > 
> > IMO, if the objective is to eliminate called party behavior from ASR 
> > (and SER), minimally the following response codes need to be excluded:
> > User Busy		~480
> > RNA			~486
> > Busy Everywhere	~600
> > 
> > I fail to see how exclusion of 3xx, other 4xx, and 6xx codes (with the
> 
> > possible exception of 603) will serve this objective.
> > 
> > It appears that the metric you are proposing has a much broader scope.
> > Perhaps, the confusion is caused by the inclusion of "user agent"
> > behavior in the definition of SEER, which should only exclude the 
> > effects of "called party" behavior.
> > 
> > Regards,
> > -Reza
> > 
> > 		
> > 
> > 
> > 
> > 
> > 
> > -----Original Message-----
> > From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> > Sent: Tuesday, April 03, 2007 3:28 AM
> > To: Fardid, Reza; Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > 
> > Reza,
> > 
> > Exactly because of the analogy with NER and the meaning it has as 
> > telephony metric I wanted to make clear the right counters, including 
> > for release codes, are used to achieve the same meaning in SIP. I 
> > didn't understand for when you foresee the implementation?
> > 
> > Best regards!
> > Mario.
> > 
> > -----Original Message-----
> > From: Fardid, Reza [mailto:RFardid@Covad.COM]
> > Sent: Friday, 30 March, 2007 22:02
> > To: Marian Delkinov (LN/EAB); Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > 
> > Mario,
> > 
> > What I had in mind when I proposed inclusion of SEER in this draft was
> 
> > a SIP performance metric analogous to NER in the PSTN, within the 
> > framework defined by Daryl:
> > 
> > Telephony Metric/Standard (ITU-T, BellCore, etc.) ==> SIP ETE Metric
> > 
> > Clearly some SIP metrics defined in this draft do not have a telephony
> 
> > counterpart.  For the rest, IMO, it is good to stay within the above 
> > framework and leave exclusion/inclusion of specific release codes from
> 
> > defined metrics to implementation.
> > 
> > Regards,
> > Reza Fardid
> > Covad Communications
> > 
> > 
> > -----Original Message-----
> > From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> > Sent: Thursday, March 29, 2007 1:07 AM
> > To: Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > 
> > Hi Daryl,
> > 
> > I haven't got your opinion about my comments on the SEER definition.
> > Have you considered them? 
> > Would also be interested to know when a finalized document on the 
> > performance metrics can be released.
> > 
> > Thanks!
> > 
> > Best regards!
> > Mario.
> > 
> > -----Original Message-----
> > From: Marian Delkinov (LN/EAB)
> > Sent: Monday, 05 March, 2007 17:06
> > To: 'Daryl Malas'
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > 
> > Hi Daryl,
> > 
> > In principle, I agree with you in case we considered this from a user 
> > perspective - then 3xx is not final. However my idea behind including 
> > the 3xx codes was based on the involvement of "#Invite" in the
> formula.
> > If a 3xx code would result in sending a new Invite, then it sounds 
> > logical to me to add the 3xx codes in the numerator. (NB: RFC3261 
> > defines 3xx responses as "final" for the SIP transaction, ref. to page
> 
> > 21, Final Response).
> > 
> > Best regards!
> > Mario.
> > 
> >  
> > 
> > -----Original Message-----
> > From: Daryl Malas [mailto:daryl@level3.net]
> > Sent: Friday, 23 February, 2007 17:00
> > To: Marian Delkinov (LN/EAB)
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > 
> > I don't think 3xx codes should be included, since they would not be 
> > considered a "Final" release cause code.  --Daryl
> > 
> > On Fri, 2007-02-23 at 12:22 +0100, Marian Delkinov (LN/EAB) wrote:
> > > Hi,
> > > 
> > > If the Network Efficiency Rate is designed to express the ability of
> 
> > > the network to deliver calls (in SIP terms one should perhaps say 
> > > "establish sessions"), I think that it might be reasonable to 
> > > include few more cases (cause codes) in the numerator: e.g. all 
> > > redirection 3xx codes, all 4xx except 408 codes and all 6xx codes. 
> > > (If you agree that those are the ones that exclude network failures,
> 
> > > congestion and any other network malfunction).
> > > 
> > > Actually it sounds fair to me if it's the opposite of the 
> > > Ineffective Session Attempts (ISA):
> > > SEER% =
> > > 	   Total # of Invite Requests - # of ISA
> > > ---------------------------------------------------- x 100
> > > 	   Total # of Invite Requests
> > > 
> > > What do you think?
> > > 
> > > Best regards!
> > > Mario.
> > > 
> > > -----Original Message-----
> > > From: Daryl Malas [mailto:daryl@level3.net]
> > > Sent: Friday, 23 February, 2007 01:14
> > > To: sipping@ietf.org
> > > Subject: [Sipping] Session Establishment Efficiency Rate
> > > 
> > > A couple more people have expressed to me that this adaptation of 
> > > the ITU-T E.411 Network Efficiency Rate metric is very valuable.  
> > > The snapshot of the metric from the draft is:
> > > 
> > > "This metric is similar to Session Establishment Rate, but it is 
> > > intended to exclude the effects of customer behavior and user agent 
> > > behavior.  Essentially, the attempts resulting with a final cause 
> > > code
> > 
> > > of 480, 486, and 600 would be added to the SER numerator."
> > > 
> > > Does anyone else want to see this metric in the draft?  I personally
> 
> > > think it is an interesting metric.
> > > 
> > > Thanks...
> > > 
> > > --Daryl
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Sipping mailing list  https://www1.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
> > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 15:09:02 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbLiA-0003ju-9Q; Tue, 10 Apr 2007 15:09:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbLi9-0003jp-1A
	for sipping@ietf.org; Tue, 10 Apr 2007 15:09:01 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbLi7-0004Lz-Nn
	for sipping@ietf.org; Tue, 10 Apr 2007 15:09:01 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3AJ8vUo075698
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 10 Apr 2007 14:08:57 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461BE0CC.8010403@nostrum.com>
Date: Tue, 10 Apr 2007 14:09:00 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>	<461B8FB7.3000903@nostrum.com>	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>	<461BCAD7.1020001@nostrum.com>
	<34668222-C8B1-41FE-9519-530FDFE92BFA@softarmor.com>
In-Reply-To: <34668222-C8B1-41FE-9519-530FDFE92BFA@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: SIPPING WG <sipping@ietf.org>,
	Xavier Marjou <xavier.marjou@orange-ftgroup.com>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dean Willis wrote:
>> If we can't do that, we need some mechanism to handle the queueing -- 
>> and SUBSCRIBE/NOTIFY aren't queue management methods.
>>
>
>
> I've been pondering that assertion, and can't see why the queue 
> modeled as a document with filtering on what part of the document is 
> visible isn't a reasonable approach to an event package.

Interesting. Continue.

No, really -- what state is the user subscribing to? What changes this 
state? How is the filter being specified? How does a user's position in 
the queue get suspended? Resumed?

I'm not 100% convinced that it can't be done, but I've spent hours 
trying to figure out some way of doing this without having implicit 
operations invoked. It's gonna take someone smarter than I to figure out 
how to make this work in a way that is consistent with the defined 
semantics of SUBSCRIBE and NOTIFY -- so maybe your proposal makes sense; 
but, without more detail, it's not clear how.

Because, on the surface, the problem seems intractable without new 
operations for queue management.

/a


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 15:32:52 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbM4w-0007Ba-Ah; Tue, 10 Apr 2007 15:32:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbM4u-0007BN-FX; Tue, 10 Apr 2007 15:32:32 -0400
Received: from repmmg02.bea.com ([66.248.192.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HbM4r-0003Vy-Ke; Tue, 10 Apr 2007 15:32:32 -0400
Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71])
	by repmmg02.bea.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l3AJWPOQ028581; Tue, 10 Apr 2007 12:32:25 -0700
Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98])
	by repmmr01.bea.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l3AJWHSG009272; Tue, 10 Apr 2007 12:32:23 -0700
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: 7bit
Subject: RE: [Sipping] Simple SIP usage scenario
Date: Tue, 10 Apr 2007 12:32:21 -0700
Message-ID: <E2839307E942954A846FD1125BE33A1A03A6C0C4@repbex01.amer.bea.com>
In-Reply-To: <D3BA17190818B44CA969FB72EB43418D017A82E5@KKWNLEX181.kpnnl.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Simple SIP usage scenario
Thread-Index: AcdrlBcWVWbSgNeHEduLXAAWy4mm/wBFL8FgAB/BGMcAm+1PsAL7qBvg
References: <072C5B76F7CEAB488172C6F64B30B5E302C88E16@xmb-rtp-20b.amer.cisco.com>
	<C2290C52.4329%eburger@bea.com>
	<D3BA17190818B44CA969FB72EB43418D017A82E5@KKWNLEX181.kpnnl.local>
From: "Eric Burger" <eburger@bea.com>
To: <colin.pons@kpn.com>
x-BEA-PMX-Instructions: AV
x-BEA-MM: Internal-To-External
X-Spam-Score: 0.0 (/)
X-Scan-Signature: be922d419820e291bde1362184dc32fd
Cc: p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

The whole point is the caller gets to chose.  It doesn't matter what the
target user has or subscribes to.  If the target happens to have a voice
message service, great, I can leave a message if I chose.  If the target
doesn't, or I feel like sending an e-mail, I can just do it.  No need
for whacky protocols, architectures, inter-carrier agreements, service
identifiers, etc. 

-----Original Message-----
From: colin.pons@kpn.com [mailto:colin.pons@kpn.com] 
Sent: Monday, March 26, 2007 7:34 AM
To: Eric Burger; mhammer@cisco.com; pkyzivat@cisco.com;
hsinnrei@adobe.com
Cc: p2prg@ietf.org; sipping@ietf.org
Subject: RE: [Sipping] Simple SIP usage scenario


How would this work? If the callee (or his agent in IM style) are
off-line he is not able to inform the caller. 

The VM concept Works is based on asynchronous transaction, where both
the callee and the caller are in control; the callee is in control by
subscribing to a VM service or implementing a voicemail Application and
the caller is in control by choosing to leave a voicemail.

I agree that the VM experience can be improved where both the caller and
the calle gets to choose how to deliver the message. But my point is how
does the caller know from which options to choose if the callee did not
(or could not because of being off line) inform the caller of the
options? Otherwise I have a system the leaves control solely to the
caller.

Colin Pons
Senior Architect
WSO Innovation Management

-----Oorspronkelijk bericht-----
Van: Eric Burger [mailto:eburger@bea.com]
Verzonden: vrijdag 23 maart 2007 9:47
Aan: Michael Hammer (mhammer); Paul Kyzivat; Henry Sinnreich
CC: p2prg@ietf.org; sipping@ietf.org
Onderwerp: Re: [Sipping] Simple SIP usage scenario

Missing the point:

The called party gets to CHOOSE whether the caller is allowed to send
them an e-mail.  The called party does this by publishing their e-mail
address.
That is like a classic subscription to voice mail.  However, it is
BETTER than classic voice mail, in that if the called party does not
CHOOSE to offer voice mail, there is still the possibility for an
asynchronous IM-style transaction.

Best of all, the caller (you) gets to CHOOSE how to deliver the message.
Note I say CHOOSE, and not "the network does weird stuff that I don't
understand and has a ton of hidden feature interactions that pop out
when I and the called party least expect it."  If I chose to go the
e-mail route, then I know to expect the message to be delivered in a
timely manner, especially if "message-context: voice-message" is set.
Moreover, if I CHOOSE to go the asynchronous route, then my expectation
is appropriately set.

Also, it is important to note that the IM-style method does not
necessarily mean when *I* am on-line.  It can mean when my *agent* is on
line.


On 3/22/07 6:41 PM, "Michael Hammer (mhammer)" <mhammer@cisco.com>
wrote:

> Note that doing that (Skype P2P) delays the deliver of the message to 
> when the caller is back online versus when the sender intended the 
> message to be sent and stored, i.e. before the called party is online.
> 
> What if I need to leave an important message before hopping a plane,
and
> the receiver getting it when the plane lands hours later will be after

> the meeting for which the message was intended?
> 
> Not good.  Not the same service as VM.  The whole point is dijoint 
> asynchronous delivery.
> 
> Mike
> 
> 
>> -----Original Message-----
>> From: Eric Burger [mailto:eburger@bea.com]
>> Sent: Wednesday, March 21, 2007 4:37 AM
>> To: Paul Kyzivat (pkyzivat); Henry Sinnreich
>> Cc: p2prg@ietf.org; sipping@ietf.org
>> Subject: Re: [Sipping] Simple SIP usage scenario
>> 
>> I would offer the concept of putting the responsibility for "sending"

>> the message on the caller IS EXCELLENT.
>> 
>> It totally removes a ton of hard stuff that VM systems have to do, 
>> like absolutely, positively, delivering the message once the caller 
>> thinks the message was recorded.  Why is this so?  The CALLER knows 
>> if his device is up, down, or sideways.
>>  If he knows the device is not on line or broke, then he has NO 
>> expectations of the message being delivered.
>> 
>> Think of how Skype and Yahoo!IM does delayed delivery: they wait 
>> until both parties are back on-line before sending the message.  Thus

>> this paradigm is NOT going to be foreign to a p2p SIP user.
>> 
>> 
>> On 3/20/07 11:57 AM, "Paul Kyzivat" <pkyzivat@cisco.com> wrote:
>> 
>>> 
>>> 
>>> Henry Sinnreich wrote:
>>>> Paul,
>>>> 
>>>> This is a good question regarding VM in P2P SIP. It is discussed 
>>>> along with other telephony services in more detail in:
>>>> 
>>>> 
>> http://www1.cs.columbia.edu/~library/TR-repository/reports/reports-20
>>>> 04/
>>>> cucs-044-04.pdf
>>> 
>>> Loots to me that this could use a lot more discussion.
>>> 
>>> It seems that there is one fundamental decision to be made:
>> When the
>>> callee is not available, is it the responsibility of the
>> caller or the
>>> callee to capture a message? Then there are secondary
>> questions of how
>>> the message is stored, and how it is conveyed to the recipient.
>>> 
>>> Clearly the current world view is that it is the
>> responsibility of the
>>> callee to handle the capture of the message. If the goal is
>> to change
>>> that assumption, then there will need to be some compatibility 
>>> mechanism put in place for callers that don't do it. To the extent 
>>> that it is the callee that would like to have the message, it may 
>>> always need to be a responsibility of the callee.
>>> 
>>> If it is decided that it is the callee that must provide this, then 
>>> either it is done by the P2P framework or it is not. If not we can 
>>> perhaps ignore it as just another UA, though it might actually be 
>>> provided by a multiuser VM service provider.
>>> 
>>> If this is to be provided by the p2p framework, then it has
>> become a
>>> "network service".
>>> 
>>> Personally, I rather like the idea of making this a
>> requirement of the
>>> caller, and having them email the message. (If the callee wants to 
>>> receive a message it could return a 3xx with email url.)
>> But I don't
>>> know how we get to where we can count on callers doing it.
>>> 
>>> Paul
>>> 
>>>> Henry
>>>> 
>>>> -----Original Message-----
>>>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
>>>> Sent: Tuesday, March 20, 2007 10:35 AM
>>>> To: Henry Sinnreich
>>>> Cc: Dale.Worley@comcast.net; sipping@ietf.org; p2prg@ietf.org
>>>> Subject: Re: [Sipping] Simple SIP usage scenario
>>>> 
>>>> Henry,
>>>> 
>>>> Your comments below seem to assume that I must have a UA
>> attached any
>>>> time I might what to send a call to VM. But if all I have
>> are mobile
>>>> devices then that won't be the case. I need a way to have
>> *something*
>>>> that acts for me when I have none of my own devices attached.
>>>> 
>>>> I could satisfy this by contracting for service from something to 
>>>> register on my behalf at all times. If I want that, where
>> does that
>>>> service fit into the p2p framework? Is it internal to it,
>> or external?
>>>> 
>>>> Paul
>>>> 
>>>> Henry Sinnreich wrote:
>>>>>> It seems like it would be hard to associate a voicemail
>> server with
>>>>>> a mobile handset without a proxy/registrar somewhere.
>>>>> This is a good _editorial_ catch.
>>>>> 
>>>>> 1. In the case of a VM server no extensions to RFC 3261
>> are required
>>>> for
>>>>> simple VM. The called UA can redirect the call to VM
>> after a timeout.
>>>>> This must be made clear in the text.
>>>>> 
>>>>> 2. In the case of P2P SIP, the DHT can serve for voice
>> mail storage.
>>>>> 
>>>>> Maybe I am missing something?
>>>>> 
>>>>> Thanks for noting it,
>>>>> 
>>>>> Henry
>>>>> 
>>>>> -----Original Message-----
>>>>> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]
>>>>> Sent: Tuesday, March 20, 2007 1:59 AM
>>>>> To: p2prg@ietf.org; sipping@ietf.org
>>>>> Subject: Re: [Sipping] Simple SIP usage scenario
>>>>> 
>>>>>    From: Paul Kyzivat <pkyzivat@cisco.com>
>>>>> 
>>>>>    It could be functionally equivalent - registering with my AOR.
>>>>> 
>>>>> This strikes me as a central issue.  Especially if the real UA is 
>>>>> mobile, you need a high-accessibility "fixed" server to
>> anchor the
>>>>> AOR.  SIP has the machinery to do that well, yes, but
>> that machinery
>>>>> *is* a proxy/registrar.  At that point, I don't see how
>> the "Simple
>>>>> SIP scenario" differs from a PBX, though possibly a PBX with one 
>>>>> extension.
>>>>> 
>>>>> It seems like it would be hard to associate a voicemail
>> server with
>>>>> a mobile handset without a proxy/registrar somewhere.
>>>>> 
>>>>> Dale
>>>>> 
>>>>> _______________________________________________
>>>>> Sipping mailing list
>> https://www1.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
>>>>> 
>>>>> _______________________________________________
>>>>> Sipping mailing list
>> https://www1.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
>>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> Sipping mailing list  https://www1.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
>> 
>> ______________________________________________________________
>> _________
>> Notice:  This email message, together with any attachments, may 
>> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  
>> affiliated entities,  that may be confidential,  proprietary,  
>> copyrighted  and/or legally privileged, and is intended solely for 
>> the use of the individual or entity named in this message. If you are

>> not the intended recipient, and have received this message in error, 
>> please immediately return this by email and then delete it.
>> 
>> _______________________________________________
>> Sipping mailing list  https://www1.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
>> 
> 



Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

_______________________________________________
Sipping mailing list  https://www1.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

Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 17:04:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbNV2-00023O-Ba; Tue, 10 Apr 2007 17:03:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbNV0-00022x-5D
	for sipping@ietf.org; Tue, 10 Apr 2007 17:03:34 -0400
Received: from alnrmhc13.comcast.net ([206.18.177.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbNUy-0000Ry-Ux
	for sipping@ietf.org; Tue, 10 Apr 2007 17:03:34 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (alnrmhc13) with ESMTP
	id <20070410210332b1300jo60se>; Tue, 10 Apr 2007 21:03:32 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l3AL3VLv028697
	for <sipping@ietf.org>; Tue, 10 Apr 2007 17:03:31 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l3AL3VqL028693;
	Tue, 10 Apr 2007 17:03:31 -0400
Date: Tue, 10 Apr 2007 17:03:31 -0400
Message-Id: <200704102103.l3AL3VqL028693@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <7374777208BDC7449D5620EF94232567033AD311@esealmw113.eemea.ericsson.se>
	(christer.holmberg@ericsson.com)
Subject: Re: [Sipping] Re: draft-holmberg-sipping-199-00.txt
References: <7374777208BDC7449D5620EF94232567033AD311@esealmw113.eemea.ericsson.se>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>

   For example, if you have reserved codec X only for the stream that
   is terminated, you know that you can free the resources associated
   with that codec. [2 further examples delete]

OK, you've convinced me.

Dale

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 10 18:26:05 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbOlG-0008Co-2F; Tue, 10 Apr 2007 18:24:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbOlE-0008Cf-8I
	for sipping@ietf.org; Tue, 10 Apr 2007 18:24:24 -0400
Received: from smtp1.versatel.nl ([62.58.50.88])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbOlC-0008E0-8l
	for sipping@ietf.org; Tue, 10 Apr 2007 18:24:24 -0400
Received: (qmail 3630 invoked by uid 0); 10 Apr 2007 22:25:33 -0000
Received: from ip198-11-212-87.adsl2.versatel.nl (HELO BEMBUSTER)
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp1.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 10 Apr 2007 22:25:33 -0000
Message-ID: <00e101c77bbe$d9edc6f0$0601a8c0@BEMBUSTER>
From: "Jeroen van Bemmel" <jbemmel@zonnet.nl>
To: "Eric Burger" <eburger@bea.com>,
	<colin.pons@kpn.com>
References: <072C5B76F7CEAB488172C6F64B30B5E302C88E16@xmb-rtp-20b.amer.cisco.com><C2290C52.4329%eburger@bea.com><D3BA17190818B44CA969FB72EB43418D017A82E5@KKWNLEX181.kpnnl.local>
	<E2839307E942954A846FD1125BE33A1A03A6C0C4@repbex01.amer.bea.com>
Subject: Re: [Sipping] Simple SIP usage scenario
Date: Wed, 11 Apr 2007 00:23:23 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d9ae72af46718088458d214998cc683
Cc: p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Eric,

What you describe below is already (and always has been) possible. Note that 
in todays world also e-mail has inter-provider agreements, and 
architectures, and wacky protocols, and well-known ports (the UDP/TCP 
equivalent of one aspect of a service identifier).

Voice mail, as it is currently commonly used and known, is a service that 
may kick in when A calls B and B has a voice mail service. One could imagine 
a "straight to voice mail" service controlled by the caller, but usually the 
callee determines when voice mail is offered. When offered, the caller can 
then choose to leave a message "after the beep", or not. Whatever the caller 
does after/besides this (e.g. send e-mail) is irrelevant for the VM service.

My point here is: voice mail works the way it does. It provides the caller 
an extra option to deliver a message, under certain conditions, and provides 
a certain user experience with associated expectations. In no way does it 
(or the architecture or what have you) limit the choices of either the 
caller or the callee with regards to using other means of communication.

One can change (hoping to "improve", subjective) the user experience 
provided by voice mail, but you soon end up with something which is 
essentially a _different_ service. To avoid confusion, it should then no 
longer be called "voice mail"

So: are we really talking about a "voice mail" service for P2P SIP here?

Regards,
Jeroen

Eric Burger wrote:
> The whole point is the caller gets to chose.  It doesn't matter what
> the
> target user has or subscribes to.  If the target happens to have a
> voice
> message service, great, I can leave a message if I chose.  If the
> target
> doesn't, or I feel like sending an e-mail, I can just do it.  No need
> for whacky protocols, architectures, inter-carrier agreements, service
> identifiers, etc.
>
> -----Original Message-----
> From: colin.pons@kpn.com [mailto:colin.pons@kpn.com]
> Sent: Monday, March 26, 2007 7:34 AM
> To: Eric Burger; mhammer@cisco.com; pkyzivat@cisco.com;
> hsinnrei@adobe.com
> Cc: p2prg@ietf.org; sipping@ietf.org
> Subject: RE: [Sipping] Simple SIP usage scenario
>
>
> How would this work? If the callee (or his agent in IM style) are
> off-line he is not able to inform the caller.
>
> The VM concept Works is based on asynchronous transaction, where both
> the callee and the caller are in control; the callee is in control by
> subscribing to a VM service or implementing a voicemail Application
> and
> the caller is in control by choosing to leave a voicemail.
>
> I agree that the VM experience can be improved where both the caller
> and
> the calle gets to choose how to deliver the message. But my point is
> how
> does the caller know from which options to choose if the callee did
> not (or could not because of being off line) inform the caller of the
> options? Otherwise I have a system the leaves control solely to the
> caller.
>
> Colin Pons
> Senior Architect
> WSO Innovation Management
>
> -----Oorspronkelijk bericht-----
> Van: Eric Burger [mailto:eburger@bea.com]
> Verzonden: vrijdag 23 maart 2007 9:47
> Aan: Michael Hammer (mhammer); Paul Kyzivat; Henry Sinnreich
> CC: p2prg@ietf.org; sipping@ietf.org
> Onderwerp: Re: [Sipping] Simple SIP usage scenario
>
> Missing the point:
>
> The called party gets to CHOOSE whether the caller is allowed to send
> them an e-mail.  The called party does this by publishing their e-mail
> address.
> That is like a classic subscription to voice mail.  However, it is
> BETTER than classic voice mail, in that if the called party does not
> CHOOSE to offer voice mail, there is still the possibility for an
> asynchronous IM-style transaction.
>
> Best of all, the caller (you) gets to CHOOSE how to deliver the
> message.
> Note I say CHOOSE, and not "the network does weird stuff that I don't
> understand and has a ton of hidden feature interactions that pop out
> when I and the called party least expect it."  If I chose to go the
> e-mail route, then I know to expect the message to be delivered in a
> timely manner, especially if "message-context: voice-message" is set.
> Moreover, if I CHOOSE to go the asynchronous route, then my
> expectation
> is appropriately set.
>
> Also, it is important to note that the IM-style method does not
> necessarily mean when *I* am on-line.  It can mean when my *agent* is
> on
> line.
>
>
> On 3/22/07 6:41 PM, "Michael Hammer (mhammer)" <mhammer@cisco.com>
> wrote:
>
>> Note that doing that (Skype P2P) delays the deliver of the message to
>> when the caller is back online versus when the sender intended the
>> message to be sent and stored, i.e. before the called party is
>> online.
>>
>> What if I need to leave an important message before hopping a plane,
> and
>> the receiver getting it when the plane lands hours later will be
>> after
>
>> the meeting for which the message was intended?
>>
>> Not good.  Not the same service as VM.  The whole point is dijoint
>> asynchronous delivery.
>>
>> Mike
>>
>>
>>> -----Original Message-----
>>> From: Eric Burger [mailto:eburger@bea.com]
>>> Sent: Wednesday, March 21, 2007 4:37 AM
>>> To: Paul Kyzivat (pkyzivat); Henry Sinnreich
>>> Cc: p2prg@ietf.org; sipping@ietf.org
>>> Subject: Re: [Sipping] Simple SIP usage scenario
>>>
>>> I would offer the concept of putting the responsibility for
>>> "sending"
>
>>> the message on the caller IS EXCELLENT.
>>>
>>> It totally removes a ton of hard stuff that VM systems have to do,
>>> like absolutely, positively, delivering the message once the caller
>>> thinks the message was recorded.  Why is this so?  The CALLER knows
>>> if his device is up, down, or sideways.
>>>  If he knows the device is not on line or broke, then he has NO
>>> expectations of the message being delivered.
>>>
>>> Think of how Skype and Yahoo!IM does delayed delivery: they wait
>>> until both parties are back on-line before sending the message.
>>> Thus
>
>>> this paradigm is NOT going to be foreign to a p2p SIP user.
>>>
>>>
>>> On 3/20/07 11:57 AM, "Paul Kyzivat" <pkyzivat@cisco.com> wrote:
>>>
>>>>
>>>>
>>>> Henry Sinnreich wrote:
>>>>> Paul,
>>>>>
>>>>> This is a good question regarding VM in P2P SIP. It is discussed
>>>>> along with other telephony services in more detail in:
>>>>>
>>>>>
>>> http://www1.cs.columbia.edu/~library/TR-repository/reports/reports-20
>>>>> 04/
>>>>> cucs-044-04.pdf
>>>>
>>>> Loots to me that this could use a lot more discussion.
>>>>
>>>> It seems that there is one fundamental decision to be made:
>>> When the
>>>> callee is not available, is it the responsibility of the
>>> caller or the
>>>> callee to capture a message? Then there are secondary
>>> questions of how
>>>> the message is stored, and how it is conveyed to the recipient.
>>>>
>>>> Clearly the current world view is that it is the
>>> responsibility of the
>>>> callee to handle the capture of the message. If the goal is
>>> to change
>>>> that assumption, then there will need to be some compatibility
>>>> mechanism put in place for callers that don't do it. To the extent
>>>> that it is the callee that would like to have the message, it may
>>>> always need to be a responsibility of the callee.
>>>>
>>>> If it is decided that it is the callee that must provide this, then
>>>> either it is done by the P2P framework or it is not. If not we can
>>>> perhaps ignore it as just another UA, though it might actually be
>>>> provided by a multiuser VM service provider.
>>>>
>>>> If this is to be provided by the p2p framework, then it has
>>> become a
>>>> "network service".
>>>>
>>>> Personally, I rather like the idea of making this a
>>> requirement of the
>>>> caller, and having them email the message. (If the callee wants to
>>>> receive a message it could return a 3xx with email url.)
>>> But I don't
>>>> know how we get to where we can count on callers doing it.
>>>>
>>>> Paul
>>>>
>>>>> Henry
>>>>>
>>>>> -----Original Message-----
>>>>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
>>>>> Sent: Tuesday, March 20, 2007 10:35 AM
>>>>> To: Henry Sinnreich
>>>>> Cc: Dale.Worley@comcast.net; sipping@ietf.org; p2prg@ietf.org
>>>>> Subject: Re: [Sipping] Simple SIP usage scenario
>>>>>
>>>>> Henry,
>>>>>
>>>>> Your comments below seem to assume that I must have a UA
>>> attached any
>>>>> time I might what to send a call to VM. But if all I have
>>> are mobile
>>>>> devices then that won't be the case. I need a way to have
>>> *something*
>>>>> that acts for me when I have none of my own devices attached.
>>>>>
>>>>> I could satisfy this by contracting for service from something to
>>>>> register on my behalf at all times. If I want that, where
>>> does that
>>>>> service fit into the p2p framework? Is it internal to it,
>>> or external?
>>>>>
>>>>> Paul
>>>>>
>>>>> Henry Sinnreich wrote:
>>>>>>> It seems like it would be hard to associate a voicemail
>>> server with
>>>>>>> a mobile handset without a proxy/registrar somewhere.
>>>>>> This is a good _editorial_ catch.
>>>>>>
>>>>>> 1. In the case of a VM server no extensions to RFC 3261 are
>>>>>> required for simple VM. The called UA can redirect the call to VM
>>> after a timeout.
>>>>>> This must be made clear in the text.
>>>>>>
>>>>>> 2. In the case of P2P SIP, the DHT can serve for voice
>>> mail storage.
>>>>>>
>>>>>> Maybe I am missing something?
>>>>>>
>>>>>> Thanks for noting it,
>>>>>>
>>>>>> Henry
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]
>>>>>> Sent: Tuesday, March 20, 2007 1:59 AM
>>>>>> To: p2prg@ietf.org; sipping@ietf.org
>>>>>> Subject: Re: [Sipping] Simple SIP usage scenario
>>>>>>
>>>>>>    From: Paul Kyzivat <pkyzivat@cisco.com>
>>>>>>
>>>>>>    It could be functionally equivalent - registering with my AOR.
>>>>>>
>>>>>> This strikes me as a central issue.  Especially if the real UA is
>>>>>> mobile, you need a high-accessibility "fixed" server to
>>> anchor the
>>>>>> AOR.  SIP has the machinery to do that well, yes, but
>>> that machinery
>>>>>> *is* a proxy/registrar.  At that point, I don't see how
>>> the "Simple
>>>>>> SIP scenario" differs from a PBX, though possibly a PBX with one
>>>>>> extension.
>>>>>>
>>>>>> It seems like it would be hard to associate a voicemail
>>> server with
>>>>>> a mobile handset without a proxy/registrar somewhere.
>>>>>>
>>>>>> Dale
>>>>>>
>>>>>> _______________________________________________
>>>>>> Sipping mailing list
>>> https://www1.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
>>>>>>
>>>>>> _______________________________________________
>>>>>> Sipping mailing list
>>> https://www1.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
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Sipping mailing list
>>>> https://www1.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
>>>
>>> ______________________________________________________________
>>> _________
>>> Notice:  This email message, together with any attachments, may
>>> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and
>>> affiliated entities,  that may be confidential,  proprietary,
>>> copyrighted  and/or legally privileged, and is intended solely for
>>> the use of the individual or entity named in this message. If you
>>> are
>
>>> not the intended recipient, and have received this message in error,
>>> please immediately return this by email and then delete it.
>>>
>>> _______________________________________________
>>> Sipping mailing list  https://www1.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
>>>
>>
>
>
>
> Notice:  This email message, together with any attachments, may
> contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and
> affiliated
> entities,  that may be confidential,  proprietary,  copyrighted
> and/or
> legally privileged, and is intended solely for the use of the
> individual
> or entity named in this message. If you are not the intended
> recipient,
> and have received this message in error, please immediately return
> this
> by email and then delete it.
>
> _______________________________________________
> Sipping mailing list  https://www1.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
>
> Notice:  This email message, together with any attachments, may
> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and
> affiliated entities,  that may be confidential,  proprietary,
> copyrighted  and/or legally privileged, and is intended solely for
> the use of the individual or entity named in this message. If you are
> not the intended recipient, and have received this message in error,
> please immediately return this by email and then delete it.
>
> _______________________________________________
> Sipping mailing list  https://www1.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 


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 02:50:55 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbWd7-00015K-Nj; Wed, 11 Apr 2007 02:48:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbWd6-00015F-LT
	for sipping@ietf.org; Wed, 11 Apr 2007 02:48:32 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbWd3-0002hD-U5
	for sipping@ietf.org; Wed, 11 Apr 2007 02:48:32 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JGB0037TMW4BA@siemenscomms.co.uk> for sipping@ietf.org;
	Wed, 11 Apr 2007 07:48:04 +0100 (BST)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VDAFT8>; Wed, 11 Apr 2007 07:48:08 +0100
Content-return: allowed
Date: Wed, 11 Apr 2007 07:48:08 +0100
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
To: Adam Roach <adam@nostrum.com>
Message-id: <50B1CBA96870A34799A506B2313F26670B862057@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 916029c14bdb340aa234d3ec4cd24f52
Cc: Francois Audet <audet@nortel.com>, SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Well, this can work both ways. In my case I  happen to think the BFCP
solution will cost more so my sane way of looking at it is to make do with
the event package method. I have never been convinced that that is broken.

John 

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com] 
> Sent: 08 April 2007 16:29
> To: Elwell, John
> Cc: Francois Audet; SIPPING WG
> Subject: Re: [Sipping] Call Completion: In Defense of 
> Explicit Operations
> 
> Elwell, John wrote:
> > Francois,
> >
> > Clearly the TISPAN people want more than that.
> >
> >   
> 
> I think we understand that they *want* it to behave that way. What I 
> believe is getting lost is the cost imposed by the requirements as 
> written. In particular, there appears to be no dialog, only a 
> unidirectional declaration of requirements without listening for any 
> feedback.
> 
> To use an analogy: let's imagine that I wanted to buy a car. I could 
> write down the list of features I wanted and then send a 
> representative 
> to the car dealer with that list. Now, imagine if the car dealer 
> explained that they have something on the lot that has all of my 
> features for $25,000, *except* it's not a stick shift -- and that, in 
> fact, a model with those features *and* a stick shift would 
> be such an 
> odd special order that it would add $400,000 to the price of the car 
> because of the need to re-tool the assembly line.
> 
> A sensible representative would take this information back to 
> me and ask 
> whether the additional cost was warranted. Of course, I would 
> probably 
> say, "no."
> 
> An insane representative would, without contacting me, raise a stink 
> about the ridiculous cost for this feature and attempt to stand their 
> ground, eventually imposing an additional $400,000 cost on me.
> 
> What I'd like to know for certain is that TISPAN *understands* the 
> difficulty required to implement this one very small and rarely-used 
> aspect of the feature, and that they have explicitly stated 
> that it is 
> important enough to justify the additional cost it imposes on 
> the solution.
> 
> /a
> 
> >   
> >> -----Original Message-----
> >> From: Francois Audet [mailto:audet@nortel.com] 
> >> Sent: 07 April 2007 19:39
> >> To: Elwell, John; Adam Roach; SIPPING WG
> >> Subject: RE: [Sipping] Call Completion: In Defense of 
> >> Explicit Operations
> >>
> >> Hi John,
> >>
> >> Do you think that this implementing this feature in
> >> the way Adam and I were alluding to, i.e., where queuing
> >> is handled by the clients but without some of the more
> >> complex "queue management" feature would be acceptable
> >> in those countries?
> >>
> >> That would allow us to have a very simple implemenation
> >> without compromising the semantics of SUBSCRIBE or 
> >> using a separate protocol (BFCP).
> >>
> >>
> >>     
> >>> -----Original Message-----
> >>> From: Elwell, John [mailto:john.elwell@siemens.com] 
> >>> Sent: Saturday, April 07, 2007 11:29
> >>> To: Audet, Francois (SC100:3055); Adam Roach; SIPPING WG
> >>> Subject: RE: [Sipping] Call Completion: In Defense of 
> >>> Explicit Operations
> >>>
> >>> I know this feature is quite popular in the PSTN residential 
> >>> market in various countries in Europe, particularly Germany 
> >>> and also the UK to some extent. Customers seem prepared to 
> >>> spend a few euro cents for the convenience it gives in a 
> >>> presence-less environment. So I think the operators of those 
> >>> networks want to make sure they don't lose this when they 
> >>> evolve to SIP. Given that in SIP you could do things 
> >>> differently and hopefully better, PSTN interworking would 
> >>> appear to be the essential driver behind the TISPAN 
> >>> requirements, but presumably an important driver in the eyes 
> >>> of the carriers concerned. For the enterprise market I just 
> >>> don't see it as important. We used to have it on PBXs right 
> >>> back in the 70s and 80s and it was popular then, but 
> >>> voicemail has pretty well taken over in the enterprise. I 
> >>> hope this sheds some light.
> >>>
> >>> John
> >>>
> >>>       
> >>>> -----Original Message-----
> >>>> From: Francois Audet [mailto:audet@nortel.com]
> >>>> Sent: 05 April 2007 23:18
> >>>> To: Adam Roach; SIPPING WG
> >>>> Subject: RE: [Sipping] Call Completion: In Defense of Explicit 
> >>>> Operations
> >>>>
> >>>> Wouldn't it be possible to do this CCBS/CCNR stuff with a simple 
> >>>> dialog package, and ditch this "queue management" mechanism?
> >>>>
> >>>> This seems to me to be a classic case of Engineers-gone-wild.
> >>>>
> >>>> I see this in the poetzl draft:
> >>>>
> >>>>     Completion of Calls on no Reply (CCNR) provides the 
> >>>>         
> >> caller with 
> >>     
> >>>> the
> >>>>     ability to complete a requested call to a callee 
> >>>>         
> >>> without having to
> >>>       
> >>>>     make a new call attempt when the callee becomes not 
> >>>>         
> >> busy after 
> >>     
> >>>>     having initiated an activity.  The CCNR service 
> >>>>         
> >> description is 
> >>     
> >>>>     defined in ETSI EN 301 134 [6]. 
> >>>>
> >>>>     The call completion services provide the capability to queue 
> >>>>     several CCBS/CCNR requests to the same callee on a FIFO 
> >>>>         
> >>> basis. It 
> >>>       
> >>>>     therefore requires functionalities like notifying 
> >>>>         
> >>> changes of queue
> >>>       
> >>>>     states and managing queues.  
> >>>>
> >>>> In other words, we are defining this really complex stuff 
> >>>>         
> >>> just because 
> >>>       
> >>>> it used to work like this in some ETSI standard for PSTN.
> >>>>
> >>>> Is there a better justification than that? What am I missing?
> >>>>
> >>>> Couldn't we handle some basic level of queueing at the endpoints 
> >>>> themselves, and use a simple dialog package, and avoid all 
> >>>>         
> >>> this stuff 
> >>>       
> >>>> that creates all the complexity?
> >>>>
> >>>> This CCBS/CCNR feature is one of the feature that has the most 
> >>>> variation
> >>>>
> >>>> in implementations in PSTN that I know of. To me, picking 
> >>>>         
> >> a really 
> >>     
> >>>> complicated variant and replicating it in SIP (either by 
> >>>>         
> >>> bastardizing 
> >>>       
> >>>> the protocol, or by using an entirely different protocol 
> >>>>         
> >>> altogether) 
> >>>       
> >>>> is not a good idea.
> >>>> My take is
> >>>> that there will be such a small uptake in implementation 
> >>>>         
> >>> that it will 
> >>>       
> >>>> effectively useful only in a few confined environments 
> >>>>         
> >> where the it 
> >>     
> >>>> can be mandated by law.
> >>>>
> >>>> I'd must rather have a simpler easier to implement 
> version of the 
> >>>> service.
> >>>>
> >>>>         
> >>>>> -----Original Message-----
> >>>>> From: Adam Roach [mailto:adam@nostrum.com]
> >>>>> Sent: Thursday, April 05, 2007 12:10
> >>>>> To: SIPPING WG
> >>>>> Subject: [Sipping] Call Completion: In Defense of Explicit
> >>>>>           
> >>>> Operations
> >>>>         
> >>>>> Despite what appeared to be early agreement in the 
> >>>>>           
> >> working group 
> >>     
> >>>>> (and on the MIG mailing list) that we wanted to 
> >>>>>           
> >>> discourage the use 
> >>>       
> >>>>> of SUBSCRIBE and NOTIFY as general purpose RPC 
> >>>>>           
> >>> mechanisms. This is 
> >>>       
> >>>>> the primary objection that I have raised to 
> >>>>> draft-poetzl-sipping-call-completion,
> >>>>> which uses SUBSCRIBE and NOTIFY to manipulate call queue state.
> >>>>>
> >>>>> In the spirit of sending text, I described an alternate set of 
> >>>>> mechanisms in draft-roach-sipping-callcomp-bfcp, which 
> >>>>>           
> >>> performs the 
> >>>       
> >>>>> same task without having implied side effects from the 
> >>>>>           
> >>> creation of a 
> >>>       
> >>>>> subscription.
> >>>>>
> >>>>> I'll further note that the use of SUBSCRIBE to both create a 
> >>>>> subscription and manipulate a call queue falls under the 
> >>>>>           
> >>> category of 
> >>>       
> >>>>> "one operation with two separate effects." We have a very poor 
> >>>>> institutional memory indeed if we cannot recall why 
> >>>>>           
> >> operations of 
> >>     
> >>>>> this nature are Really Bad Ideas (cf. REFER creating a 
> >>>>>           
> >>> subscription; 
> >>>       
> >>>>> REGISTER with call processing upload; and BYE with an 
> >>>>>           
> >>> "Also" header 
> >>>       
> >>>>> field).
> >>>>>
> >>>>> All of this notwithstanding, in Prague, there seemed to 
> >>>>>           
> >>> be a curious 
> >>>       
> >>>>> indifference to pursuing the path laden with such Really 
> >>>>>           
> >>> Bad Ideas. 
> >>>       
> >>>>> I suspect that this indifference is a result of the 
> >>>>>           
> >>> arguments raised 
> >>>       
> >>>>> so far against the mechanism I have proposed, which I have done 
> >>>>> little to refute so far (largely because I believed that 
> >>>>>           
> >>> the merits 
> >>>       
> >>>>> of a system with explicit operations were self-evident 
> >>>>>           
> >>> enough that 
> >>>       
> >>>>> the objections would seem trifling in comparison).
> >>>>>
> >>>>> As far as I can tell, the objections raised so far have 
> >>>>>           
> >>> fallen into 
> >>>       
> >>>>> three primary categories:
> >>>>>
> >>>>>    1. "The use of BFCP is troubling because, in a
> >>>>>           
> >>>> decomposed gateway,
> >>>>         
> >>>>>       the BFCP goes to the Media Gateway, while the
> >>>>>           
> >>>> signaling goes to
> >>>>         
> >>>>>       the Media Gateway Controller."
> >>>>>
> >>>>>       This objection, raised on one of the slides during 
> >>>>>           
> >>> the SIPPING
> >>>       
> >>>>>       meeting on March 23rd as the official reason TISPAN
> >>>>>           
> >>>> rejected the
> >>>>         
> >>>>>       approach, is based on a simple misconception.
> >>>>>
> >>>>>       The BFCP goes wherever the SDP says the BFCP goes. 
> >>>>>           
> >>> In the case 
> >>>       
> >>>>> of
> >>>>>       a decomposed gateway, this could be the Media
> >>>>>           
> >>>> Gateway, the Media
> >>>>         
> >>>>>       Gateway Controller, or any other random
> >>>>>           
> >>>> network-connected server
> >>>>         
> >>>>>       that the Media Gateway Controller wants. I agree that it 
> >>>>> probably
> >>>>>       is most sensible to send it to the Media Gateway
> >>>>>           
> >>>> Controller, and
> >>>>         
> >>>>>       this is trivial to achieve.
> >>>>>
> >>>>>    2. "In the case of PSTN interwork, there is no way to 
> >>>>>           
> >>> guarantee 
> >>>       
> >>>>> that
> >>>>>       the ISUP (or other) signaling from the PSTN side 
> >>>>>           
> >>> lands on the 
> >>>       
> >>>>> same
> >>>>>       gateway that the client has a BFCP connection to."
> >>>>>
> >>>>>       This is true, and it is a relatively difficult
> >>>>>           
> >>>> problem to solve
> >>>>         
> >>>>>       (not impossible, though; I proposed several potential 
> >>>>> solutions in
> >>>>>       San Diego). It is meaningless to raise it in 
> >>>>>           
> >> objection to an
> >>     
> >>>>>       alternate proposal, since it exists in almost
> >>>>>           
> >>>> precisely the same
> >>>>         
> >>>>>       form in draft-poetzl-sipping-call-completion; and 
> >>>>>           
> >>> any solution
> >>>       
> >>>>>       that can be applied to one solution can be applied to
> >>>>>           
> >>>> the other.
> >>>>         
> >>>>>    3. "We don't want to add another protocol."
> >>>>>
> >>>>>       I suspect this argument is the one that is 
> >>>>>           
> >>> receiving the most
> >>>       
> >>>>>       traction, probably because most of the people 
> >>>>>           
> >>> involved in the
> >>>       
> >>>>>       discussion are not familiar with BFCP. The protocol 
> >>>>>           
> >>> itself is 
> >>>       
> >>>>> very
> >>>>>       straightforward and extremely easy to implement. In fact,
> >>>>>       exclusively for the purpose of answering this email (and
> >>>>>       demonstrating this very point), I threw together a BFCP
> >>>>>       implementation sufficient for implementation of the Call
> >>>>>       Completion service described in 
> >>>>> draft-roach-sipping-callcomp-bfcp.
> >>>>>       It took me two hours, and compiles down to less 
> >>>>>           
> >> than 4 kb of
> >>     
> >>>>>       object code on an intel processor. It's attached to
> >>>>>           
> >>>> this message
> >>>>         
> >>>>>       to help the participants in the conversation
> >>>>>           
> >>>> understand just how
> >>>>         
> >>>>>       very little is being added to applications by this
> >>>>>           
> >>>> use of BFCP.
> >>>>         
> >>>>> So, is that it? The first two objections are simply red 
> >>>>>           
> >> herrings, 
> >>     
> >>>>> and the third is based on a misconception regarding the 
> >>>>>           
> >> level of 
> >>     
> >>>>> effort required to implement BFCP. Are we really going to 
> >>>>>           
> >>> down the 
> >>>       
> >>>>> path of doing things incorrectly over what amount to 
> >>>>> misunderstandings?
> >>>>>
> >>>>> /a
> >>>>>
> >>>>>
> >>>>>
> >>>>> P.S. In case anyone wants a more full-featured BFCP stack, I'll 
> >>>>> point to the confiance project on SourceForge, available 
> >>>>>           
> >>> under the 
> >>>       
> >>>>> Academic Freedom License, which is compatible with commercial
> >>>>>           
> >>>> development. See
> >>>>         
> >>>>> http://confiance.sourceforge.net/
> >>>>>
> >>>>>           
> >>>> _______________________________________________
> >>>> Sipping mailing list  
> >>>>         
> >> https://www1.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
> >>>>
> >>>>         
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 05:48:23 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbZPt-0005k2-RO; Wed, 11 Apr 2007 05:47:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbZPs-0005ex-LR
	for sipping@ietf.org; Wed, 11 Apr 2007 05:47:04 -0400
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbZPr-0000tK-5x
	for sipping@ietf.org; Wed, 11 Apr 2007 05:47:04 -0400
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de
	[10.125.177.122]) by tcmail21.telekom.de with ESMTP;
	Wed, 11 Apr 2007 11:46:51 +0200
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Apr 2007 11:46:48 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: [Sipping] Call Completion: In Defense of Explicit Operations
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 11 Apr 2007 11:46:47 +0200
Message-Id: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <461BE0CC.8010403@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
Thread-Index: Acd7o7YVSBiOK++5S/eAeat0v/9wAQAc7oCw
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <adam@nostrum.com>,
    <sipping@ietf.org>
X-OriginalArrivalTime: 11 Apr 2007 09:46:48.0267 (UTC)
	FILETIME=[52C231B0:01C77C1E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I think the part of the solution where are no doubts is that we can use =
SUB/NOT to inform the user about his call-completion state (queued, or =
he is the one who shall start the recall). IF we decide for a SIP =
solution, which I think we should do if there are no technical reasons =
against, because BFCP seem to be easy to implement with the necassary =
knowledge, but it is still another protocol.=20

The question is, when SUBSCRIBEs are used anyway, why can't we reuse =
them for queue manipulation actions? Why put another RFC into the =
terminal, when RFC 3265 would be enough. The simpler those terminals =
are, the cheaper they will be, and the more people will use them.=20

Yes, using the SUBSCRIBE also for queue manipulations would be one =
operation with two effects, but where is the harm? There is a similar =
use in the policy package, which submits an SDP in the SUBSCRIBE request =
and gets back a policy for that SDP in the NOTIFY request.


Adam, you are of course the expert for RFC 3265, and if you say such a =
usage breaks SUB/NOT because of certain reasons, then we certainly have =
to look for another solution. But if SUB/NOT was not intended for such a =
use, but it can be done, I think we can keep things simpler if we =
consider the solution of the Poetzl draft.



Regards, Martin





> -----Urspr=FCngliche Nachricht-----
> Von: Adam Roach [mailto:adam@nostrum.com]=20
> Gesendet: Dienstag, 10. April 2007 21:09
> An: Dean Willis
> Cc: SIPPING WG; Xavier Marjou; Michael Hammer (mhammer)
> Betreff: Re: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
>=20
> Dean Willis wrote:
> >> If we can't do that, we need some mechanism to handle the=20
> queueing --=20
> >> and SUBSCRIBE/NOTIFY aren't queue management methods.
> >>
> >
> >
> > I've been pondering that assertion, and can't see why the queue=20
> > modeled as a document with filtering on what part of the=20
> document is=20
> > visible isn't a reasonable approach to an event package.
>=20
> Interesting. Continue.
>=20
> No, really -- what state is the user subscribing to? What=20
> changes this=20
> state? How is the filter being specified? How does a user's=20
> position in=20
> the queue get suspended? Resumed?
>=20
> I'm not 100% convinced that it can't be done, but I've spent hours=20
> trying to figure out some way of doing this without having implicit=20
> operations invoked. It's gonna take someone smarter than I to=20
> figure out=20
> how to make this work in a way that is consistent with the defined=20
> semantics of SUBSCRIBE and NOTIFY -- so maybe your proposal=20
> makes sense;=20
> but, without more detail, it's not clear how.
>=20
> Because, on the surface, the problem seems intractable without new=20
> operations for queue management.
>=20
> /a
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.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
>=20

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 06:56:36 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbaTn-0005ma-4T; Wed, 11 Apr 2007 06:55:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbaTl-0005YE-J2
	for sipping@ietf.org; Wed, 11 Apr 2007 06:55:09 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbaTe-0006wA-Gf
	for sipping@ietf.org; Wed, 11 Apr 2007 06:55:09 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	DAA14204F4; Wed, 11 Apr 2007 12:54:57 +0200 (CEST)
X-AuditID: c1b4fb3c-aa4eebb0000073d5-ff-461cbe818792 
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B612A2072E; Wed, 11 Apr 2007 12:54:57 +0200 (CEST)
Received: from esealmw106.eemea.ericsson.se ([153.88.200.69]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Apr 2007 12:54:57 +0200
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
Subject: RE: [Sipping] Session Establishment Efficiency Rate
Date: Wed, 11 Apr 2007 12:54:53 +0200
Message-ID: <97F2AD7AA4EAD948827639B06CF2745FD05740@esealmw106.eemea.ericsson.se>
In-Reply-To: <1176232485.17141.133.camel@montag.eng.level3.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Session Establishment Efficiency Rate
thread-index: Acd7ornco3eIaTU2RqKNmzyJ2d4zhgAhL19A
From: "Marian Delkinov \(LN/EAB\)" <marian.delkinov@ericsson.com>
To: "Daryl Malas" <daryl@level3.net>
X-OriginalArrivalTime: 11 Apr 2007 10:54:57.0235 (UTC)
	FILETIME=[D7F93230:01C77C27]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a4bcf8f67063cac573319207fe3db35
Cc: "Fardid, Reza" <RFardid@Covad.COM>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi Daryl,

Precisely!=20

Best regards!
Mario.

-----Original Message-----
From: Daryl Malas [mailto:daryl@level3.net]=20
Sent: Tuesday, 10 April, 2007 21:15
To: Marian Delkinov (LN/EAB)
Cc: Fardid, Reza; sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Okay...I think I understand your point.  The denominator needs to be
clarified in Section 3.6 and then relative to SEER.  It needs to make
sure it does not include INVITE's that are redirected or similar, as
this will skew the data.  Is this what you are referring to?

--Daryl

On Tue, 2007-04-10 at 20:39 +0200, Marian Delkinov (LN/EAB) wrote:
> Daryl,
>=20
> I understand what you mean and with the condition about the same Call=20
> ID, I agree with it. The reason for my comments as  I wrote you=20
> earlier, was the inclusion of #INVITE in the formula. What you are=20
> talking about should perhaps be described as #Call Attempts. Because=20
> if we consider all INVITEs with same Call ID as 1 call attempt and put

> that in the formula, then everything fits on place.
>=20
> In that case the definition would look:
>=20
> SEER =3D (#Invite w/200 OK + #480 + #486 + #600)/# Total Call Attempts
>=20
> (with note e.g: #Total Call Attempts =3D # distinct(Call_IDs)
>=20
> What worries me yet is how we handle the forking.=20
>=20
> Best regards!
> Mario.
> =20
>=20
> -----Original Message-----
> From: Daryl Malas [mailto:daryl@level3.net]
> Sent: Tuesday, 10 April, 2007 19:08
> To: Marian Delkinov (LN/EAB)
> Cc: Fardid, Reza; sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
>=20
> It sends a new INVITE, but the call id doesn't change.  This allows=20
> tools to identify it as the same call or 1 OK/ 1 INVITE =3D 100% SER.
>=20
> --Daryl
>=20
> On Tue, 2007-04-10 at 15:57 +0200, Marian Delkinov (LN/EAB) wrote:
> > Reza,
> >=20
> > As far as I know the standard telephony - it functions a bit=20
> > differently. For instance if a user activates a service as "Call=20
> > Diversion" (similar to redirect in SIP), it's the network that=20
> > handles
>=20
> > that hidden for the calling party, i.e. the caller does not need to=20
> > dial another number. And when such case occurs, in terms of PSTN for

> > the calling party it's 1 call (1 seizure produced) only. Or in NER=20
> > formula you will have:
> >=20
> > (1 answer, or RNA, or BUSY etc)/ 1 call =3D 100% NER
> >=20
> > If we try to apply same to SIP. When redirect is received, the UA=20
> > has to send another INVITE, right? (Tell me if I'm wrong). And if we

> > count
>=20
> > the 300 code as network failure, and assume the second INVITE is=20
> > successful, then we have:
> >=20
> > 1 OK /2 #INVITE =3D 50% SEER, which IMO isn't correct. Do you agree, =

> > or please explain.
> >=20
> > Best regards!
> > Mario.
> >=20
> > -----Original Message-----
> > From: Fardid, Reza [mailto:RFardid@Covad.COM]
> > Sent: Monday, 09 April, 2007 20:05
> > To: Marian Delkinov (LN/EAB); Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > Mario,
> >=20
> > IMO, if the objective is to eliminate called party behavior from ASR

> > (and SER), minimally the following response codes need to be
excluded:
> > User Busy		~480
> > RNA			~486
> > Busy Everywhere	~600
> >=20
> > I fail to see how exclusion of 3xx, other 4xx, and 6xx codes (with=20
> > the
>=20
> > possible exception of 603) will serve this objective.
> >=20
> > It appears that the metric you are proposing has a much broader
scope.
> > Perhaps, the confusion is caused by the inclusion of "user agent"
> > behavior in the definition of SEER, which should only exclude the=20
> > effects of "called party" behavior.
> >=20
> > Regards,
> > -Reza
> >=20
> > 	=09
> >=20
> >=20
> >=20
> >=20
> >=20
> > -----Original Message-----
> > From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> > Sent: Tuesday, April 03, 2007 3:28 AM
> > To: Fardid, Reza; Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > Reza,
> >=20
> > Exactly because of the analogy with NER and the meaning it has as=20
> > telephony metric I wanted to make clear the right counters,=20
> > including for release codes, are used to achieve the same meaning in

> > SIP. I didn't understand for when you foresee the implementation?
> >=20
> > Best regards!
> > Mario.
> >=20
> > -----Original Message-----
> > From: Fardid, Reza [mailto:RFardid@Covad.COM]
> > Sent: Friday, 30 March, 2007 22:02
> > To: Marian Delkinov (LN/EAB); Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > Mario,
> >=20
> > What I had in mind when I proposed inclusion of SEER in this draft=20
> > was
>=20
> > a SIP performance metric analogous to NER in the PSTN, within the=20
> > framework defined by Daryl:
> >=20
> > Telephony Metric/Standard (ITU-T, BellCore, etc.) =3D=3D> SIP ETE =
Metric
> >=20
> > Clearly some SIP metrics defined in this draft do not have a=20
> > telephony
>=20
> > counterpart.  For the rest, IMO, it is good to stay within the above

> > framework and leave exclusion/inclusion of specific release codes=20
> > from
>=20
> > defined metrics to implementation.
> >=20
> > Regards,
> > Reza Fardid
> > Covad Communications
> >=20
> >=20
> > -----Original Message-----
> > From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> > Sent: Thursday, March 29, 2007 1:07 AM
> > To: Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > Hi Daryl,
> >=20
> > I haven't got your opinion about my comments on the SEER definition.
> > Have you considered them?=20
> > Would also be interested to know when a finalized document on the=20
> > performance metrics can be released.
> >=20
> > Thanks!
> >=20
> > Best regards!
> > Mario.
> >=20
> > -----Original Message-----
> > From: Marian Delkinov (LN/EAB)
> > Sent: Monday, 05 March, 2007 17:06
> > To: 'Daryl Malas'
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > Hi Daryl,
> >=20
> > In principle, I agree with you in case we considered this from a=20
> > user perspective - then 3xx is not final. However my idea behind=20
> > including the 3xx codes was based on the involvement of "#Invite" in

> > the
> formula.
> > If a 3xx code would result in sending a new Invite, then it sounds=20
> > logical to me to add the 3xx codes in the numerator. (NB: RFC3261=20
> > defines 3xx responses as "final" for the SIP transaction, ref. to=20
> > page
>=20
> > 21, Final Response).
> >=20
> > Best regards!
> > Mario.
> >=20
> > =20
> >=20
> > -----Original Message-----
> > From: Daryl Malas [mailto:daryl@level3.net]
> > Sent: Friday, 23 February, 2007 17:00
> > To: Marian Delkinov (LN/EAB)
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > I don't think 3xx codes should be included, since they would not be=20
> > considered a "Final" release cause code.  --Daryl
> >=20
> > On Fri, 2007-02-23 at 12:22 +0100, Marian Delkinov (LN/EAB) wrote:
> > > Hi,
> > >=20
> > > If the Network Efficiency Rate is designed to express the ability=20
> > > of
>=20
> > > the network to deliver calls (in SIP terms one should perhaps say=20
> > > "establish sessions"), I think that it might be reasonable to=20
> > > include few more cases (cause codes) in the numerator: e.g. all=20
> > > redirection 3xx codes, all 4xx except 408 codes and all 6xx codes.
> > > (If you agree that those are the ones that exclude network=20
> > > failures,
>=20
> > > congestion and any other network malfunction).
> > >=20
> > > Actually it sounds fair to me if it's the opposite of the=20
> > > Ineffective Session Attempts (ISA):
> > > SEER% =3D
> > > 	   Total # of Invite Requests - # of ISA
> > > ---------------------------------------------------- x 100
> > > 	   Total # of Invite Requests
> > >=20
> > > What do you think?
> > >=20
> > > Best regards!
> > > Mario.
> > >=20
> > > -----Original Message-----
> > > From: Daryl Malas [mailto:daryl@level3.net]
> > > Sent: Friday, 23 February, 2007 01:14
> > > To: sipping@ietf.org
> > > Subject: [Sipping] Session Establishment Efficiency Rate
> > >=20
> > > A couple more people have expressed to me that this adaptation of=20
> > > the ITU-T E.411 Network Efficiency Rate metric is very valuable.
> > > The snapshot of the metric from the draft is:
> > >=20
> > > "This metric is similar to Session Establishment Rate, but it is=20
> > > intended to exclude the effects of customer behavior and user=20
> > > agent behavior.  Essentially, the attempts resulting with a final=20
> > > cause code
> >=20
> > > of 480, 486, and 600 would be added to the SER numerator."
> > >=20
> > > Does anyone else want to see this metric in the draft?  I=20
> > > personally
>=20
> > > think it is an interesting metric.
> > >=20
> > > Thanks...
> > >=20
> > > --Daryl
> > >=20
> > >=20
> > >=20
> > > _______________________________________________
> > > Sipping mailing list =20
> > > https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP Use=20
> > > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > > sip@ietf.org for new developments of core SIP
> >=20
> >=20
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 09:10:59 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbcaU-0000lU-4u; Wed, 11 Apr 2007 09:10:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbcaS-0000lG-Gw; Wed, 11 Apr 2007 09:10:12 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HbcaQ-00089p-PA; Wed, 11 Apr 2007 09:10:12 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 11 Apr 2007 09:10:11 -0400
X-IronPort-AV: i="4.14,395,1170651600"; 
	d="scan'208"; a="118218632:sNHT79028026"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3BDAAk0018800; 
	Wed, 11 Apr 2007 09:10:10 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l3BDA1lM001875; 
	Wed, 11 Apr 2007 13:10:01 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Apr 2007 09:09:55 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Apr 2007 09:09:55 -0400
Message-ID: <461CDE23.4070105@cisco.com>
Date: Wed, 11 Apr 2007 09:09:55 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Jeroen van Bemmel <jbemmel@zonnet.nl>
Subject: Re: [Sipping] Simple SIP usage scenario
References: <072C5B76F7CEAB488172C6F64B30B5E302C88E16@xmb-rtp-20b.amer.cisco.com><C2290C52.4329%eburger@bea.com><D3BA17190818B44CA969FB72EB43418D017A82E5@KKWNLEX181.kpnnl.local>	<E2839307E942954A846FD1125BE33A1A03A6C0C4@repbex01.amer.bea.com>
	<00e101c77bbe$d9edc6f0$0601a8c0@BEMBUSTER>
In-Reply-To: <00e101c77bbe$d9edc6f0$0601a8c0@BEMBUSTER>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Apr 2007 13:09:55.0637 (UTC)
	FILETIME=[B2FF4650:01C77C3A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=16005; t=1176297010;
	x=1177161010; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Simple=20SIP=20usage=20scenario
	|Sender:=20 |To:=20Jeroen=20van=20Bemmel=20<jbemmel@zonnet.nl>;
	bh=ZF6eB3ywx4yI2Ax9qDOoVJqg59pSnT30Mgf5TecpIUA=;
	b=XnYp3dDMqemeskCkgM2Bu7OVK1Gyyl3TBZMiFez7v/NRlaysZFPrxsI92BJaSHtLLl6Y/CaB
	/UcgZU0d1vo7TNtq8aLXJvljElYqHHo5qVsjcvOavhGBuON8FZtRXh4m;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d437399464e10b52abe9a34ed7e712d0
Cc: p2prg@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Jeroen van Bemmel wrote:
> Eric,
> 
> What you describe below is already (and always has been) possible. Note 
> that in todays world also e-mail has inter-provider agreements, and 
> architectures, and wacky protocols, and well-known ports (the UDP/TCP 
> equivalent of one aspect of a service identifier).
> 
> Voice mail, as it is currently commonly used and known, is a service 
> that may kick in when A calls B and B has a voice mail service. One 
> could imagine a "straight to voice mail" service controlled by the 
> caller, but usually the callee determines when voice mail is offered. 
> When offered, the caller can then choose to leave a message "after the 
> beep", or not. Whatever the caller does after/besides this (e.g. send 
> e-mail) is irrelevant for the VM service.
> 
> My point here is: voice mail works the way it does. It provides the 
> caller an extra option to deliver a message, under certain conditions, 
> and provides a certain user experience with associated expectations. In 
> no way does it (or the architecture or what have you) limit the choices 
> of either the caller or the callee with regards to using other means of 
> communication.

Well, it does work the way it does. :-)

But it does limit other options of both caller and callee. Some examples:

- when caller is an automaton, and doesn't care to leave a message,
   it provides little option. Calling systems use various heuristics
   to figure out if they are talking to VM, but those are unreliable.

- If Alice calls Bob, and Bob is not present, then Bob may wish to
   try forwarding the call to Charlie, and then if Charlie doesn't
   answer route the call to Bob's VM. But this may not work if
   Charlie isn't present but has his own VM system.
   (I know some VM systems try to get around this by selecting the
   VM mailbox of the original target, but that also isn't reliable.
   It only works if both share the same mail server.)

Callerprefs-usecases (RFC 4596) attempted to address some of these 
cases. But that only works if the VM server *registers* with its 
capabilities.

> One can change (hoping to "improve", subjective) the user experience 
> provided by voice mail, but you soon end up with something which is 
> essentially a _different_ service. To avoid confusion, it should then no 
> longer be called "voice mail"
> 
> So: are we really talking about a "voice mail" service for P2P SIP here?

I think that the implementations of VM are sufficiently diverse that we 
can't assume too much in any case.

	Paul

> Regards,
> Jeroen
> 
> Eric Burger wrote:
>> The whole point is the caller gets to chose.  It doesn't matter what
>> the
>> target user has or subscribes to.  If the target happens to have a
>> voice
>> message service, great, I can leave a message if I chose.  If the
>> target
>> doesn't, or I feel like sending an e-mail, I can just do it.  No need
>> for whacky protocols, architectures, inter-carrier agreements, service
>> identifiers, etc.
>>
>> -----Original Message-----
>> From: colin.pons@kpn.com [mailto:colin.pons@kpn.com]
>> Sent: Monday, March 26, 2007 7:34 AM
>> To: Eric Burger; mhammer@cisco.com; pkyzivat@cisco.com;
>> hsinnrei@adobe.com
>> Cc: p2prg@ietf.org; sipping@ietf.org
>> Subject: RE: [Sipping] Simple SIP usage scenario
>>
>>
>> How would this work? If the callee (or his agent in IM style) are
>> off-line he is not able to inform the caller.
>>
>> The VM concept Works is based on asynchronous transaction, where both
>> the callee and the caller are in control; the callee is in control by
>> subscribing to a VM service or implementing a voicemail Application
>> and
>> the caller is in control by choosing to leave a voicemail.
>>
>> I agree that the VM experience can be improved where both the caller
>> and
>> the calle gets to choose how to deliver the message. But my point is
>> how
>> does the caller know from which options to choose if the callee did
>> not (or could not because of being off line) inform the caller of the
>> options? Otherwise I have a system the leaves control solely to the
>> caller.
>>
>> Colin Pons
>> Senior Architect
>> WSO Innovation Management
>>
>> -----Oorspronkelijk bericht-----
>> Van: Eric Burger [mailto:eburger@bea.com]
>> Verzonden: vrijdag 23 maart 2007 9:47
>> Aan: Michael Hammer (mhammer); Paul Kyzivat; Henry Sinnreich
>> CC: p2prg@ietf.org; sipping@ietf.org
>> Onderwerp: Re: [Sipping] Simple SIP usage scenario
>>
>> Missing the point:
>>
>> The called party gets to CHOOSE whether the caller is allowed to send
>> them an e-mail.  The called party does this by publishing their e-mail
>> address.
>> That is like a classic subscription to voice mail.  However, it is
>> BETTER than classic voice mail, in that if the called party does not
>> CHOOSE to offer voice mail, there is still the possibility for an
>> asynchronous IM-style transaction.
>>
>> Best of all, the caller (you) gets to CHOOSE how to deliver the
>> message.
>> Note I say CHOOSE, and not "the network does weird stuff that I don't
>> understand and has a ton of hidden feature interactions that pop out
>> when I and the called party least expect it."  If I chose to go the
>> e-mail route, then I know to expect the message to be delivered in a
>> timely manner, especially if "message-context: voice-message" is set.
>> Moreover, if I CHOOSE to go the asynchronous route, then my
>> expectation
>> is appropriately set.
>>
>> Also, it is important to note that the IM-style method does not
>> necessarily mean when *I* am on-line.  It can mean when my *agent* is
>> on
>> line.
>>
>>
>> On 3/22/07 6:41 PM, "Michael Hammer (mhammer)" <mhammer@cisco.com>
>> wrote:
>>
>>> Note that doing that (Skype P2P) delays the deliver of the message to
>>> when the caller is back online versus when the sender intended the
>>> message to be sent and stored, i.e. before the called party is
>>> online.
>>>
>>> What if I need to leave an important message before hopping a plane,
>> and
>>> the receiver getting it when the plane lands hours later will be
>>> after
>>
>>> the meeting for which the message was intended?
>>>
>>> Not good.  Not the same service as VM.  The whole point is dijoint
>>> asynchronous delivery.
>>>
>>> Mike
>>>
>>>
>>>> -----Original Message-----
>>>> From: Eric Burger [mailto:eburger@bea.com]
>>>> Sent: Wednesday, March 21, 2007 4:37 AM
>>>> To: Paul Kyzivat (pkyzivat); Henry Sinnreich
>>>> Cc: p2prg@ietf.org; sipping@ietf.org
>>>> Subject: Re: [Sipping] Simple SIP usage scenario
>>>>
>>>> I would offer the concept of putting the responsibility for
>>>> "sending"
>>
>>>> the message on the caller IS EXCELLENT.
>>>>
>>>> It totally removes a ton of hard stuff that VM systems have to do,
>>>> like absolutely, positively, delivering the message once the caller
>>>> thinks the message was recorded.  Why is this so?  The CALLER knows
>>>> if his device is up, down, or sideways.
>>>>  If he knows the device is not on line or broke, then he has NO
>>>> expectations of the message being delivered.
>>>>
>>>> Think of how Skype and Yahoo!IM does delayed delivery: they wait
>>>> until both parties are back on-line before sending the message.
>>>> Thus
>>
>>>> this paradigm is NOT going to be foreign to a p2p SIP user.
>>>>
>>>>
>>>> On 3/20/07 11:57 AM, "Paul Kyzivat" <pkyzivat@cisco.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> Henry Sinnreich wrote:
>>>>>> Paul,
>>>>>>
>>>>>> This is a good question regarding VM in P2P SIP. It is discussed
>>>>>> along with other telephony services in more detail in:
>>>>>>
>>>>>>
>>>> http://www1.cs.columbia.edu/~library/TR-repository/reports/reports-20
>>>>>> 04/
>>>>>> cucs-044-04.pdf
>>>>>
>>>>> Loots to me that this could use a lot more discussion.
>>>>>
>>>>> It seems that there is one fundamental decision to be made:
>>>> When the
>>>>> callee is not available, is it the responsibility of the
>>>> caller or the
>>>>> callee to capture a message? Then there are secondary
>>>> questions of how
>>>>> the message is stored, and how it is conveyed to the recipient.
>>>>>
>>>>> Clearly the current world view is that it is the
>>>> responsibility of the
>>>>> callee to handle the capture of the message. If the goal is
>>>> to change
>>>>> that assumption, then there will need to be some compatibility
>>>>> mechanism put in place for callers that don't do it. To the extent
>>>>> that it is the callee that would like to have the message, it may
>>>>> always need to be a responsibility of the callee.
>>>>>
>>>>> If it is decided that it is the callee that must provide this, then
>>>>> either it is done by the P2P framework or it is not. If not we can
>>>>> perhaps ignore it as just another UA, though it might actually be
>>>>> provided by a multiuser VM service provider.
>>>>>
>>>>> If this is to be provided by the p2p framework, then it has
>>>> become a
>>>>> "network service".
>>>>>
>>>>> Personally, I rather like the idea of making this a
>>>> requirement of the
>>>>> caller, and having them email the message. (If the callee wants to
>>>>> receive a message it could return a 3xx with email url.)
>>>> But I don't
>>>>> know how we get to where we can count on callers doing it.
>>>>>
>>>>> Paul
>>>>>
>>>>>> Henry
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
>>>>>> Sent: Tuesday, March 20, 2007 10:35 AM
>>>>>> To: Henry Sinnreich
>>>>>> Cc: Dale.Worley@comcast.net; sipping@ietf.org; p2prg@ietf.org
>>>>>> Subject: Re: [Sipping] Simple SIP usage scenario
>>>>>>
>>>>>> Henry,
>>>>>>
>>>>>> Your comments below seem to assume that I must have a UA
>>>> attached any
>>>>>> time I might what to send a call to VM. But if all I have
>>>> are mobile
>>>>>> devices then that won't be the case. I need a way to have
>>>> *something*
>>>>>> that acts for me when I have none of my own devices attached.
>>>>>>
>>>>>> I could satisfy this by contracting for service from something to
>>>>>> register on my behalf at all times. If I want that, where
>>>> does that
>>>>>> service fit into the p2p framework? Is it internal to it,
>>>> or external?
>>>>>>
>>>>>> Paul
>>>>>>
>>>>>> Henry Sinnreich wrote:
>>>>>>>> It seems like it would be hard to associate a voicemail
>>>> server with
>>>>>>>> a mobile handset without a proxy/registrar somewhere.
>>>>>>> This is a good _editorial_ catch.
>>>>>>>
>>>>>>> 1. In the case of a VM server no extensions to RFC 3261 are
>>>>>>> required for simple VM. The called UA can redirect the call to VM
>>>> after a timeout.
>>>>>>> This must be made clear in the text.
>>>>>>>
>>>>>>> 2. In the case of P2P SIP, the DHT can serve for voice
>>>> mail storage.
>>>>>>>
>>>>>>> Maybe I am missing something?
>>>>>>>
>>>>>>> Thanks for noting it,
>>>>>>>
>>>>>>> Henry
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]
>>>>>>> Sent: Tuesday, March 20, 2007 1:59 AM
>>>>>>> To: p2prg@ietf.org; sipping@ietf.org
>>>>>>> Subject: Re: [Sipping] Simple SIP usage scenario
>>>>>>>
>>>>>>>    From: Paul Kyzivat <pkyzivat@cisco.com>
>>>>>>>
>>>>>>>    It could be functionally equivalent - registering with my AOR.
>>>>>>>
>>>>>>> This strikes me as a central issue.  Especially if the real UA is
>>>>>>> mobile, you need a high-accessibility "fixed" server to
>>>> anchor the
>>>>>>> AOR.  SIP has the machinery to do that well, yes, but
>>>> that machinery
>>>>>>> *is* a proxy/registrar.  At that point, I don't see how
>>>> the "Simple
>>>>>>> SIP scenario" differs from a PBX, though possibly a PBX with one
>>>>>>> extension.
>>>>>>>
>>>>>>> It seems like it would be hard to associate a voicemail
>>>> server with
>>>>>>> a mobile handset without a proxy/registrar somewhere.
>>>>>>>
>>>>>>> Dale
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Sipping mailing list
>>>> https://www1.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
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Sipping mailing list
>>>> https://www1.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
>>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Sipping mailing list
>>>>> https://www1.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
>>>>
>>>> ______________________________________________________________
>>>> _________
>>>> Notice:  This email message, together with any attachments, may
>>>> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and
>>>> affiliated entities,  that may be confidential,  proprietary,
>>>> copyrighted  and/or legally privileged, and is intended solely for
>>>> the use of the individual or entity named in this message. If you
>>>> are
>>
>>>> not the intended recipient, and have received this message in error,
>>>> please immediately return this by email and then delete it.
>>>>
>>>> _______________________________________________
>>>> Sipping mailing list  https://www1.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
>>>>
>>>
>>
>>
>>
>> Notice:  This email message, together with any attachments, may
>> contain
>> information  of  BEA Systems,  Inc.,  its subsidiaries  and
>> affiliated
>> entities,  that may be confidential,  proprietary,  copyrighted
>> and/or
>> legally privileged, and is intended solely for the use of the
>> individual
>> or entity named in this message. If you are not the intended
>> recipient,
>> and have received this message in error, please immediately return
>> this
>> by email and then delete it.
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.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
>>
>> Notice:  This email message, together with any attachments, may
>> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and
>> affiliated entities,  that may be confidential,  proprietary,
>> copyrighted  and/or legally privileged, and is intended solely for
>> the use of the individual or entity named in this message. If you are
>> not the intended recipient, and have received this message in error,
>> please immediately return this by email and then delete it.
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.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 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.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
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 09:16:52 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hbcgn-0003qZ-8A; Wed, 11 Apr 2007 09:16:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hbcgl-0003pK-Ua
	for sipping@ietf.org; Wed, 11 Apr 2007 09:16:43 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hbcgj-0001W1-Kk
	for sipping@ietf.org; Wed, 11 Apr 2007 09:16:43 -0400
Received: from [192.168.0.102] (ppp-70-244-81-252.dsl.rcsntx.swbell.net
	[70.244.81.252]) (authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3BDGbkk029666
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 11 Apr 2007 08:16:39 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461CDF02.2020705@nostrum.com>
Date: Wed, 11 Apr 2007 08:13:38 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.8 (X11/20061107)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <50B1CBA96870A34799A506B2313F26670B862057@ntht201e.siemenscomms.co.uk>
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B862057@ntht201e.siemenscomms.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.244.81.252 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: Francois Audet <audet@nortel.com>, SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Elwell, John wrote:
> Well, this can work both ways. In my case I  happen to think the BFCP
> solution will cost more so my sane way of looking at it is to make do with
> the event package method. 

You're arguing over the shape of the knob on the stick shift, not 
whether it is there in the first place. My point is that we would need 
neither approach without the strict queuing requirement.

/a

> I have never been convinced that that is broken.
>
> John 
>
>   
>> -----Original Message-----
>> From: Adam Roach [mailto:adam@nostrum.com] 
>> Sent: 08 April 2007 16:29
>> To: Elwell, John
>> Cc: Francois Audet; SIPPING WG
>> Subject: Re: [Sipping] Call Completion: In Defense of 
>> Explicit Operations
>>
>> Elwell, John wrote:
>>     
>>> Francois,
>>>
>>> Clearly the TISPAN people want more than that.
>>>
>>>   
>>>       
>> I think we understand that they *want* it to behave that way. What I 
>> believe is getting lost is the cost imposed by the requirements as 
>> written. In particular, there appears to be no dialog, only a 
>> unidirectional declaration of requirements without listening for any 
>> feedback.
>>
>> To use an analogy: let's imagine that I wanted to buy a car. I could 
>> write down the list of features I wanted and then send a 
>> representative 
>> to the car dealer with that list. Now, imagine if the car dealer 
>> explained that they have something on the lot that has all of my 
>> features for $25,000, *except* it's not a stick shift -- and that, in 
>> fact, a model with those features *and* a stick shift would 
>> be such an 
>> odd special order that it would add $400,000 to the price of the car 
>> because of the need to re-tool the assembly line.
>>
>> A sensible representative would take this information back to 
>> me and ask 
>> whether the additional cost was warranted. Of course, I would 
>> probably 
>> say, "no."
>>
>> An insane representative would, without contacting me, raise a stink 
>> about the ridiculous cost for this feature and attempt to stand their 
>> ground, eventually imposing an additional $400,000 cost on me.
>>
>> What I'd like to know for certain is that TISPAN *understands* the 
>> difficulty required to implement this one very small and rarely-used 
>> aspect of the feature, and that they have explicitly stated 
>> that it is 
>> important enough to justify the additional cost it imposes on 
>> the solution.
>>
>> /a
>>     


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 10:08:30 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbdU9-0005UL-8C; Wed, 11 Apr 2007 10:07:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbdU7-0005U8-2C
	for sipping@ietf.org; Wed, 11 Apr 2007 10:07:43 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HbdU4-0004Cq-Ki
	for sipping@ietf.org; Wed, 11 Apr 2007 10:07:42 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JGC004AQ78IZ2@siemenscomms.co.uk> for sipping@ietf.org;
	Wed, 11 Apr 2007 15:07:30 +0100 (BST)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VDAQ3K>; Wed, 11 Apr 2007 15:07:35 +0100
Content-return: allowed
Date: Wed, 11 Apr 2007 15:07:32 +0100
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
To: Adam Roach <adam@nostrum.com>
Message-id: <50B1CBA96870A34799A506B2313F26670B8625C4@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: Francois Audet <audet@nortel.com>, SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Adam,

OK, I agree with you there. Given that we have these requirements from
TISPAN that can't be satisfied by traditional SIP means such as dialog
package, presence, etc., then they are likely to be "expensive" to meet.

John

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com] 
> Sent: 11 April 2007 14:14
> To: Elwell, John
> Cc: Francois Audet; SIPPING WG
> Subject: Re: [Sipping] Call Completion: In Defense of 
> Explicit Operations
> 
> Elwell, John wrote:
> > Well, this can work both ways. In my case I  happen to 
> think the BFCP
> > solution will cost more so my sane way of looking at it is 
> to make do with
> > the event package method. 
> 
> You're arguing over the shape of the knob on the stick shift, not 
> whether it is there in the first place. My point is that we 
> would need 
> neither approach without the strict queuing requirement.
> 
> /a
> 
> > I have never been convinced that that is broken.
> >
> > John 
> >
> >   
> >> -----Original Message-----
> >> From: Adam Roach [mailto:adam@nostrum.com] 
> >> Sent: 08 April 2007 16:29
> >> To: Elwell, John
> >> Cc: Francois Audet; SIPPING WG
> >> Subject: Re: [Sipping] Call Completion: In Defense of 
> >> Explicit Operations
> >>
> >> Elwell, John wrote:
> >>     
> >>> Francois,
> >>>
> >>> Clearly the TISPAN people want more than that.
> >>>
> >>>   
> >>>       
> >> I think we understand that they *want* it to behave that 
> way. What I 
> >> believe is getting lost is the cost imposed by the requirements as 
> >> written. In particular, there appears to be no dialog, only a 
> >> unidirectional declaration of requirements without 
> listening for any 
> >> feedback.
> >>
> >> To use an analogy: let's imagine that I wanted to buy a 
> car. I could 
> >> write down the list of features I wanted and then send a 
> >> representative 
> >> to the car dealer with that list. Now, imagine if the car dealer 
> >> explained that they have something on the lot that has all of my 
> >> features for $25,000, *except* it's not a stick shift -- 
> and that, in 
> >> fact, a model with those features *and* a stick shift would 
> >> be such an 
> >> odd special order that it would add $400,000 to the price 
> of the car 
> >> because of the need to re-tool the assembly line.
> >>
> >> A sensible representative would take this information back to 
> >> me and ask 
> >> whether the additional cost was warranted. Of course, I would 
> >> probably 
> >> say, "no."
> >>
> >> An insane representative would, without contacting me, 
> raise a stink 
> >> about the ridiculous cost for this feature and attempt to 
> stand their 
> >> ground, eventually imposing an additional $400,000 cost on me.
> >>
> >> What I'd like to know for certain is that TISPAN *understands* the 
> >> difficulty required to implement this one very small and 
> rarely-used 
> >> aspect of the feature, and that they have explicitly stated 
> >> that it is 
> >> important enough to justify the additional cost it imposes on 
> >> the solution.
> >>
> >> /a
> >>     
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 10:16:32 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbdcK-0000mf-8r; Wed, 11 Apr 2007 10:16:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbdcI-0000mU-Hq
	for sipping@ietf.org; Wed, 11 Apr 2007 10:16:10 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbdcE-0004UO-5L
	for sipping@ietf.org; Wed, 11 Apr 2007 10:16:10 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 11 Apr 2007 10:16:06 -0400
X-IronPort-AV: i="4.14,395,1170651600"; 
	d="scan'208"; a="118225953:sNHT75477192"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3BEG54Y019292; 
	Wed, 11 Apr 2007 10:16:05 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l3BEFZli020650; 
	Wed, 11 Apr 2007 14:16:05 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Apr 2007 10:15:44 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Apr 2007 10:15:43 -0400
Message-ID: <461CED8F.60501@cisco.com>
Date: Wed, 11 Apr 2007 10:15:43 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Apr 2007 14:15:44.0024 (UTC)
	FILETIME=[E46B5180:01C77C43]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3953; t=1176300965;
	x=1177164965; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defen
	se=20of=20Explicit=20Operations |Sender:=20
	|To:=20=22Huelsemann,=20Martin=22=20<Martin.Huelsemann@t-com.net>;
	bh=mQvyT9AzXTRf+tog5F5jPxcsiXpLPY4QX96Zx3dY2Bk=;
	b=D3KnpokexdOa2kw7R9ZSkPNS01mXDA3YnyjAYN3uXY/iMzLBSZt+ksZrkK++WVtMU8CmMNf6
	fzUgnxSqOoLtxkJYwqmWkBIV9MiZvxi9kSfUhYHb9AJZ7TDuNjaInHMm;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: sipping@ietf.org, adam@nostrum.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Huelsemann, Martin wrote:
> I think the part of the solution where are no doubts is that we can use SUB/NOT to inform the user about his call-completion state (queued, or he is the one who shall start the recall). IF we decide for a SIP solution, which I think we should do if there are no technical reasons against, because BFCP seem to be easy to implement with the necassary knowledge, but it is still another protocol. 
> 
> The question is, when SUBSCRIBEs are used anyway, why can't we reuse them for queue manipulation actions? Why put another RFC into the terminal, when RFC 3265 would be enough. The simpler those terminals are, the cheaper they will be, and the more people will use them. 
> 
> Yes, using the SUBSCRIBE also for queue manipulations would be one operation with two effects, but where is the harm? There is a similar use in the policy package, which submits an SDP in the SUBSCRIBE request and gets back a policy for that SDP in the NOTIFY request.

Lets go through this again:

Suppose it does work that way. Then conceptually what is the event state 
that is being subscribed to? Apparently it is the queue of potential 
callers. In principle, every time this state changes there should be a 
notification sent to *all* the subscribers.

Now it could be that policy is used to restrict how much visibility 
subscribers have to the event state. So the views of some may be such 
that they can't see the change, and so get no notification of it. But 
arranging things that way requires structuring the state very carefully. 
For instance, the policy might state that a subscriber can only see 
entries that refer to them. But this wouldn't be very interesting unless 
their entry included "position in queue". That would result in getting a 
notification each time your entry advanced in the queue. If that is 
annoying there could be a filter that says to only display entries that 
are "first in queue".

None of that says anything about queue manipulation - just using sub/not 
to observer a queue in a useful way for this purpose.

Note that we do have an example where the act of subscribing creates 
state that can itself be subscribed to. It is watcherinfo. But in that 
case there are two event packages in use - e.g. presence and 
presence.watcherinfo. Subscribing to presence creates watcher state that 
can be observed by subscribing to presence.watcherinfo. Having a 
SUBSCRIBE modify the state of the event being subscribed to introduces a 
sort of Heisenberg Uncertainty Principle - you can't observe the event 
without affecting it.

Specifically, it becomes impossible to observe the queue without 
becoming one of the requesters. For instance, suppose the queue was 
managed on a server separate from the UAs that receive calls to the 
target AOR. They may want to observe the queue themselves. But 
attempting to do so would seem to cause them to become candidates to 
call themself. This could be mitigated by requesting that the entry be 
suspended, but the point remains.

Further manipulation of the queue, such as suspend and resume, also 
doesn't seem to fit the sub/not model very well. If its done as part of 
the body (as the current draft specifies) then it should be considered a 
filter, but filters don't change state of the event - only the view of 
it. There isn't any good place to specify this kind of action in a 
subscribe request, for the obvious reason that SUBSCRIBE isn't intended 
to be used in that way.

I have seen reference to the policy event package as precedent for using 
bodies to create the state being subscribed to. I think that case is 
less of a problem because it does fall into a suitable conceptual model 
as a filter. In theory one is subscribing to all policies. Supplying a 
body can be viewed as simply a filter restricting notifications to ones 
pertaining to a particular set of media, etc.

	Paul

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 10:25:26 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbdkT-0006dl-Pu; Wed, 11 Apr 2007 10:24:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbdkS-0006cz-J0
	for sipping@ietf.org; Wed, 11 Apr 2007 10:24:36 -0400
Received: from sccrmhc12.comcast.net ([63.240.77.82])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbdkR-0006iw-DF
	for sipping@ietf.org; Wed, 11 Apr 2007 10:24:36 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (sccrmhc12) with ESMTP
	id <200704111424300120067u4te>; Wed, 11 Apr 2007 14:24:30 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l3BEOULv007585
	for <sipping@ietf.org>; Wed, 11 Apr 2007 10:24:30 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l3BEOU0R007581;
	Wed, 11 Apr 2007 10:24:30 -0400
Date: Wed, 11 Apr 2007 10:24:30 -0400
Message-Id: <200704111424.l3BEOU0R007581@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <50B1CBA96870A34799A506B2313F26670B8625C4@ntht201e.siemenscomms.co.uk>
	(john.elwell@siemens.com)
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <50B1CBA96870A34799A506B2313F26670B8625C4@ntht201e.siemenscomms.co.uk>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Elwell, John" <john.elwell@siemens.com>

   OK, I agree with you there. Given that we have these requirements from
   TISPAN that can't be satisfied by traditional SIP means such as dialog
   package, presence, etc., then they are likely to be "expensive" to meet.

Correction:  TISPAN has these requirements, and *we* are considering
whether we want to implement to them.

Unless we have established a consensus that we *will* implement what
TISPAN says it needs...

Dale

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 10:55:59 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbeEH-0005FJ-89; Wed, 11 Apr 2007 10:55:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbeEF-0005F8-JG
	for sipping@ietf.org; Wed, 11 Apr 2007 10:55:23 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbeED-0004c5-7f
	for sipping@ietf.org; Wed, 11 Apr 2007 10:55:23 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3BEtCPc034673
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 11 Apr 2007 09:55:19 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461CF6D6.4020809@nostrum.com>
Date: Wed, 11 Apr 2007 09:55:18 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
	<461CED8F.60501@cisco.com>
In-Reply-To: <461CED8F.60501@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Thank you, Paul. You've summarized the key points in a very coherent 
fashion.

/a

Paul Kyzivat wrote:
>
>
> Huelsemann, Martin wrote:
>> I think the part of the solution where are no doubts is that we can 
>> use SUB/NOT to inform the user about his call-completion state 
>> (queued, or he is the one who shall start the recall). IF we decide 
>> for a SIP solution, which I think we should do if there are no 
>> technical reasons against, because BFCP seem to be easy to implement 
>> with the necassary knowledge, but it is still another protocol.
>> The question is, when SUBSCRIBEs are used anyway, why can't we reuse 
>> them for queue manipulation actions? Why put another RFC into the 
>> terminal, when RFC 3265 would be enough. The simpler those terminals 
>> are, the cheaper they will be, and the more people will use them.
>> Yes, using the SUBSCRIBE also for queue manipulations would be one 
>> operation with two effects, but where is the harm? There is a similar 
>> use in the policy package, which submits an SDP in the SUBSCRIBE 
>> request and gets back a policy for that SDP in the NOTIFY request.
>
> Lets go through this again:
>
> Suppose it does work that way. Then conceptually what is the event 
> state that is being subscribed to? Apparently it is the queue of 
> potential callers. In principle, every time this state changes there 
> should be a notification sent to *all* the subscribers.
>
> Now it could be that policy is used to restrict how much visibility 
> subscribers have to the event state. So the views of some may be such 
> that they can't see the change, and so get no notification of it. But 
> arranging things that way requires structuring the state very 
> carefully. For instance, the policy might state that a subscriber can 
> only see entries that refer to them. But this wouldn't be very 
> interesting unless their entry included "position in queue". That 
> would result in getting a notification each time your entry advanced 
> in the queue. If that is annoying there could be a filter that says to 
> only display entries that are "first in queue".
>
> None of that says anything about queue manipulation - just using 
> sub/not to observer a queue in a useful way for this purpose.
>
> Note that we do have an example where the act of subscribing creates 
> state that can itself be subscribed to. It is watcherinfo. But in that 
> case there are two event packages in use - e.g. presence and 
> presence.watcherinfo. Subscribing to presence creates watcher state 
> that can be observed by subscribing to presence.watcherinfo. Having a 
> SUBSCRIBE modify the state of the event being subscribed to introduces 
> a sort of Heisenberg Uncertainty Principle - you can't observe the 
> event without affecting it.
>
> Specifically, it becomes impossible to observe the queue without 
> becoming one of the requesters. For instance, suppose the queue was 
> managed on a server separate from the UAs that receive calls to the 
> target AOR. They may want to observe the queue themselves. But 
> attempting to do so would seem to cause them to become candidates to 
> call themself. This could be mitigated by requesting that the entry be 
> suspended, but the point remains.
>
> Further manipulation of the queue, such as suspend and resume, also 
> doesn't seem to fit the sub/not model very well. If its done as part 
> of the body (as the current draft specifies) then it should be 
> considered a filter, but filters don't change state of the event - 
> only the view of it. There isn't any good place to specify this kind 
> of action in a subscribe request, for the obvious reason that 
> SUBSCRIBE isn't intended to be used in that way.
>
> I have seen reference to the policy event package as precedent for 
> using bodies to create the state being subscribed to. I think that 
> case is less of a problem because it does fall into a suitable 
> conceptual model as a filter. In theory one is subscribing to all 
> policies. Supplying a body can be viewed as simply a filter 
> restricting notifications to ones pertaining to a particular set of 
> media, etc.
>
>     Paul


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 12:21:24 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbfXX-0005mB-A0; Wed, 11 Apr 2007 12:19:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbfXW-0005m1-I6
	for sipping@ietf.org; Wed, 11 Apr 2007 12:19:22 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbfXV-00083D-6R
	for sipping@ietf.org; Wed, 11 Apr 2007 12:19:22 -0400
Received: from [206.176.144.212] (rcdn4-dmznat-gw1-nat-27.cisco.com
	[12.5.186.27]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3BFPdjo028679
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 11 Apr 2007 10:25:40 -0500
In-Reply-To: <461BE0CC.8010403@nostrum.com>
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>	<461B8FB7.3000903@nostrum.com>	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>	<461BCAD7.1020001@nostrum.com>
	<34668222-C8B1-41FE-9519-530FDFE92BFA@softarmor.com>
	<461BE0CC.8010403@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4B7406B6-B323-43B1-B7BB-2843CD105F65@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Wed, 11 Apr 2007 11:18:52 -0500
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: SIPPING WG <sipping@ietf.org>,
	Xavier Marjou <xavier.marjou@orange-ftgroup.com>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 10, 2007, at 2:09 PM, Adam Roach wrote:

> Dean Willis wrote:
>>> If we can't do that, we need some mechanism to handle the  
>>> queueing -- and SUBSCRIBE/NOTIFY aren't queue management methods.
>>>
>>
>>
>> I've been pondering that assertion, and can't see why the queue  
>> modeled as a document with filtering on what part of the document  
>> is visible isn't a reasonable approach to an event package.
>
> Interesting. Continue.
>
> No, really -- what state is the user subscribing to? What changes  
> this state? How is the filter being specified? How does a user's  
> position in the queue get suspended? Resumed?
>

It's not all that different from sip config.

The state is the content of a document describing the queue, which  
could certainly be modeled in XML, versioned with etag, and so on.

The document is modified by the queue manager, for example by adding  
a queue element, changing the pointer to the "current" queue element,  
or deleting a queue element. It might contain explicit ordering or  
priority rankings.

One can envision that the queue manager's operations on the document  
would be driven by events outside of subscriptions to the queue  
state, just as changes in sip-config documents or resource lists are  
driven by events outside of subscriptions to those documents.

Filtering is the tricky question. Let's step back and see what the  
requirements are:

1) The watcher needs to know when they're the "current" element and  
should make a call.

2) We MAY have a requirement to give the watcher some sense of  
position in the queue, as in "There are currently 487 callers ahead  
of you".

3) We MUST NOT disclose the identity of other pending callers.

4) We need to be able to change the state of the queue to "suspended"  
when the queue target is busy, either in dealing with a queued call  
or an outside call.

5) We probably have a need to correlate incoming calls against the  
queue set, so that callers who are not currently pending can be  
enqueued instead of preempting the queue.

So let's take a simplistic approach for initial analysis: the queue  
consists of an ordered set of elements (a vector), each of which  
represents either one pending call or the "suspended" state. The  
first element is the "active" element. If a watcher of this document  
sees that the first element corresponds to them, they launch a new  
INVITE, using some component of the element as a parameter so that  
the queue manager can match them up. If the queue is in a suspended  
state, the first element is one which encodes "suspended".

This seems to satisfy requirements 1,2,4, and 5 above.

Let's play a bit with #4 -- disclosing of identity of pending call  
sources.

One possibility is to use an opaque token per caller (which might be  
the same token that is used in the call setup). Alice calls into Bob,  
gets a response containing a queue URI and a token for her position.  
She watches the queue until her token comes up to the top, then calls  
in.

The above works just fine, but raises the possibility of "queue  
jumping" -- an aggressive watcher might just take whatever token is  
currently at the top and use it.

We could offset this by adding a filter. One approach might be for  
the queue-watching subscription to include the token-of-interest,  
which would be applied by the queue manager (which is serving as the  
event source). On a per-subscription basis, the queue manager would  
"mask" tokens other than the "token of interest" for that  
subscription with a dummy value.

So Alice, who is subscribed to the callback queue for Bob, might  
receive a NOTIFY containing a queue document with a "suspended"  
element, three "dummy" elements, an element containing her token, and  
two more "dummy" elements. From this she would know that the queue is  
currently blocked, there are three callers ahead of her, and two  
callers behind her. Moments later, she might see a new NOTIFY without  
the "suspended" element at its head, and deduce that the last caller  
is now off the line and a new one likely to be calling in. Eventually  
she receives a NOTIFY with a queue document with her token at the  
head, and calls in.

Myriad other queue representations and filtration strategies seem  
feasible depending on what constraints one wishes to adopt.

The important thing is to keep in mind that the queue is a document  
being edited by an application whose operation is driven by  
information (perhaps other subscriptions, such as presence) that is  
EXTERNAL to the queue itself.

I think this fits into the basic SUBSCRIBE/NOTIFY framework.

--
Dean

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 12:29:41 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbfhU-0002gj-T9; Wed, 11 Apr 2007 12:29:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbfhT-0002gQ-BD
	for sipping@ietf.org; Wed, 11 Apr 2007 12:29:39 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbfhQ-0001gs-Uj
	for sipping@ietf.org; Wed, 11 Apr 2007 12:29:39 -0400
Received: from [206.176.144.212] (rcdn4-dmznat-gw1-nat-27.cisco.com
	[12.5.186.27]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3BFa8tc028747
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 11 Apr 2007 10:36:09 -0500
In-Reply-To: <461CED8F.60501@cisco.com>
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
	<461CED8F.60501@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Wed, 11 Apr 2007 11:29:21 -0500
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: adam@nostrum.com, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 11, 2007, at 9:15 AM, Paul Kyzivat wrote:

>
>
> Huelsemann, Martin wrote:
>> I think the part of the solution where are no doubts is that we  
>> can use SUB/NOT to inform the user about his call-completion state  
>> (queued, or he is the one who shall start the recall). IF we  
>> decide for a SIP solution, which I think we should do if there are  
>> no technical reasons against, because BFCP seem to be easy to  
>> implement with the necassary knowledge, but it is still another  
>> protocol. The question is, when SUBSCRIBEs are used anyway, why  
>> can't we reuse them for queue manipulation actions? Why put  
>> another RFC into the terminal, when RFC 3265 would be enough. The  
>> simpler those terminals are, the cheaper they will be, and the  
>> more people will use them. Yes, using the SUBSCRIBE also for queue  
>> manipulations would be one operation with two effects, but where  
>> is the harm? There is a similar use in the policy package, which  
>> submits an SDP in the SUBSCRIBE request and gets back a policy for  
>> that SDP in the NOTIFY request.
>
> Lets go through this again:
>
> Suppose it does work that way. Then conceptually what is the event  
> state that is being subscribed to? Apparently it is the queue of  
> potential callers. In principle, every time this state changes  
> there should be a notification sent to *all* the subscribers.
>
> Now it could be that policy is used to restrict how much visibility  
> subscribers have to the event state. So the views of some may be  
> such that they can't see the change, and so get no notification of  
> it. But arranging things that way requires structuring the state  
> very carefully. For instance, the policy might state that a  
> subscriber can only see entries that refer to them. But this  
> wouldn't be very interesting unless their entry included "position  
> in queue". That would result in getting a notification each time  
> your entry advanced in the queue. If that is annoying there could  
> be a filter that says to only display entries that are "first in  
> queue".
>
> None of that says anything about queue manipulation - just using  
> sub/not to observer a queue in a useful way for this purpose.
>

Yes, that's the model my previous post expanded on.

> Note that we do have an example where the act of subscribing  
> creates state that can itself be subscribed to. It is watcherinfo.  
> But in that case there are two event packages in use - e.g.  
> presence and presence.watcherinfo. Subscribing to presence creates  
> watcher state that can be observed by subscribing to  
> presence.watcherinfo. Having a SUBSCRIBE modify the state of the  
> event being subscribed to introduces a sort of Heisenberg  
> Uncertainty Principle - you can't observe the event without  
> affecting it.
>

So the open question is how does one get into the queue without  
having that insertion be a side-effect of the subscription itself?

Two options:

1) Automatically enqueue all callers when there is a queue.

2) Redirect (or indirect via a new header field) callers to a queue  
factory when there is a queue. If they follow the indirection, they  
get enqueued.


> Specifically, it becomes impossible to observe the queue without  
> becoming one of the requesters. For instance, suppose the queue was  
> managed on a server separate from the UAs that receive calls to the  
> target AOR. They may want to observe the queue themselves. But  
> attempting to do so would seem to cause them to become candidates  
> to call themself. This could be mitigated by requesting that the  
> entry be suspended, but the point remains.

I concur that insertion into the queue and subscription to the queue  
must be different things. That seems obvious, so I must have missed  
the idea that they were intertwingled (or dismissed it as just silly).

>
> Further manipulation of the queue, such as suspend and resume, also  
> doesn't seem to fit the sub/not model very well. If its done as  
> part of the body (as the current draft specifies) then it should be  
> considered a filter, but filters don't change state of the event -  
> only the view of it. There isn't any good place to specify this  
> kind of action in a subscribe request, for the obvious reason that  
> SUBSCRIBE isn't intended to be used in that way.
>

Operations on the queue data itself are clearly outside of the  
"watcher" package. If the queue notification is handled on a node  
that is different from the node with the data that drives the queue,  
then we have XCAP to manipulate the queue document and make  
insertions, etc.

--
Dean




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 12:34:00 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbflY-0004H6-38; Wed, 11 Apr 2007 12:33:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbflW-0004Gr-HG
	for sipping@ietf.org; Wed, 11 Apr 2007 12:33:50 -0400
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbflU-0002wq-0P
	for sipping@ietf.org; Wed, 11 Apr 2007 12:33:50 -0400
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de
	[10.125.177.122]) by tcmail21.telekom.de with ESMTP;
	Wed, 11 Apr 2007 18:33:47 +0200
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Apr 2007 18:33:46 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: AW: AW: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Wed, 11 Apr 2007 18:33:46 +0200
Message-Id: <CCA850DCD3FBE2479D5076C5C18732220168AA39@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <461CED8F.60501@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AW: [Sipping] Call Completion: In Defense of Explicit Operations
Thread-Index: Acd8RCblvWHlQtRwQXCLCJa9v/Q+2gAEgnyQ
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <pkyzivat@cisco.com>
X-OriginalArrivalTime: 11 Apr 2007 16:33:46.0711 (UTC)
	FILETIME=[2D490E70:01C77C57]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: sipping@ietf.org, adam@nostrum.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


So what is really meant by (and explained really badly in) the Poetzl =
draft is that a user subscribes to his own call-completion state, and =
the events he is informed of are the transition of his state from any =
state to the 'queued' state and from any state to the 'start the recall' =
state.
The notifier has to derive this state from the state of the =
call-completion queue. The nature of the queue and how the =
call-completion state for a user is derived from the queue are not =
explained, but it is assumed that the queue and the notifier are =
collocated and can interact. A FIFO queue could be a suitable basis for =
the queue, although other models are not precluded.
=20
True is that the user's subscription also creates the resource, which is =
his own call-completion state. The question is, is that problematical, =
and why?=20

The next question of course would be, is it problematical to transport =
bodies with queue manipulation information within the SUBSCRIBEs.=20
On the other hand, you can interprete suspending and resuming as =
something like a filter, too. Nothing changes, neither the =
call-completion queue, the user's position remains the same, nor the =
resource, the call-completion state of a user remains 'queued'. The user =
just doesn't receive NOTIFYs for a certain time. Only after resuming the =
call-completion state might change, but then because of B has become not =
busy again.


Martin



> -----Urspr=FCngliche Nachricht-----
> Von: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
> Gesendet: Mittwoch, 11. April 2007 16:16
> An: H=FClsemann, Martin
> Cc: adam@nostrum.com; sipping@ietf.org
> Betreff: Re: AW: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
>=20
>=20
>=20
> Huelsemann, Martin wrote:
> > I think the part of the solution where are no doubts is=20
> that we can use SUB/NOT to inform the user about his=20
> call-completion state (queued, or he is the one who shall=20
> start the recall). IF we decide for a SIP solution, which I=20
> think we should do if there are no technical reasons against,=20
> because BFCP seem to be easy to implement with the necassary=20
> knowledge, but it is still another protocol.=20
> >=20
> > The question is, when SUBSCRIBEs are used anyway, why can't=20
> we reuse them for queue manipulation actions? Why put another=20
> RFC into the terminal, when RFC 3265 would be enough. The=20
> simpler those terminals are, the cheaper they will be, and=20
> the more people will use them.=20
> >=20
> > Yes, using the SUBSCRIBE also for queue manipulations would=20
> be one operation with two effects, but where is the harm?=20
> There is a similar use in the policy package, which submits=20
> an SDP in the SUBSCRIBE request and gets back a policy for=20
> that SDP in the NOTIFY request.
>=20
> Lets go through this again:
>=20
> Suppose it does work that way. Then conceptually what is the=20
> event state=20
> that is being subscribed to? Apparently it is the queue of potential=20
> callers. In principle, every time this state changes there=20
> should be a=20
> notification sent to *all* the subscribers.
>=20
> Now it could be that policy is used to restrict how much visibility=20
> subscribers have to the event state. So the views of some may be such=20
> that they can't see the change, and so get no notification of it. But=20
> arranging things that way requires structuring the state very=20
> carefully.=20
> For instance, the policy might state that a subscriber can only see=20
> entries that refer to them. But this wouldn't be very=20
> interesting unless=20
> their entry included "position in queue". That would result=20
> in getting a=20
> notification each time your entry advanced in the queue. If that is=20
> annoying there could be a filter that says to only display=20
> entries that=20
> are "first in queue".
>=20
> None of that says anything about queue manipulation - just=20
> using sub/not=20
> to observer a queue in a useful way for this purpose.
>=20
> Note that we do have an example where the act of subscribing creates=20
> state that can itself be subscribed to. It is watcherinfo.=20
> But in that=20
> case there are two event packages in use - e.g. presence and=20
> presence.watcherinfo. Subscribing to presence creates watcher=20
> state that=20
> can be observed by subscribing to presence.watcherinfo. Having a=20
> SUBSCRIBE modify the state of the event being subscribed to=20
> introduces a=20
> sort of Heisenberg Uncertainty Principle - you can't observe=20
> the event=20
> without affecting it.
>=20
> Specifically, it becomes impossible to observe the queue without=20
> becoming one of the requesters. For instance, suppose the queue was=20
> managed on a server separate from the UAs that receive calls to the=20
> target AOR. They may want to observe the queue themselves. But=20
> attempting to do so would seem to cause them to become candidates to=20
> call themself. This could be mitigated by requesting that the=20
> entry be=20
> suspended, but the point remains.
>=20
> Further manipulation of the queue, such as suspend and resume, also=20
> doesn't seem to fit the sub/not model very well. If its done=20
> as part of=20
> the body (as the current draft specifies) then it should be=20
> considered a=20
> filter, but filters don't change state of the event - only=20
> the view of=20
> it. There isn't any good place to specify this kind of action in a=20
> subscribe request, for the obvious reason that SUBSCRIBE=20
> isn't intended=20
> to be used in that way.
>=20
> I have seen reference to the policy event package as=20
> precedent for using=20
> bodies to create the state being subscribed to. I think that case is=20
> less of a problem because it does fall into a suitable=20
> conceptual model=20
> as a filter. In theory one is subscribing to all policies.=20
> Supplying a=20
> body can be viewed as simply a filter restricting=20
> notifications to ones=20
> pertaining to a particular set of media, etc.
>=20
> 	Paul
>=20

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 12:52:31 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hbg36-0005YG-Bb; Wed, 11 Apr 2007 12:52:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hbg35-0005YA-AH
	for sipping@ietf.org; Wed, 11 Apr 2007 12:51:59 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hbg33-00073q-Sw
	for sipping@ietf.org; Wed, 11 Apr 2007 12:51:59 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 11 Apr 2007 12:51:59 -0400
X-IronPort-AV: i="4.14,395,1170651600"; 
	d="scan'208"; a="57365462:sNHT60350524"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l3BGpvxd029760; 
	Wed, 11 Apr 2007 12:51:57 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3BGpvGd003421; 
	Wed, 11 Apr 2007 16:51:57 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Apr 2007 12:51:57 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Apr 2007 12:51:56 -0400
Message-ID: <461D122C.3070607@cisco.com>
Date: Wed, 11 Apr 2007 12:51:56 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
Subject: Re: AW: AW: [Sipping] Call Completion: In Defense of Explicit
	Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA39@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <CCA850DCD3FBE2479D5076C5C18732220168AA39@S4DE9JSAAHW.ost.t-com.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 11 Apr 2007 16:51:56.0961 (UTC)
	FILETIME=[B7200110:01C77C59]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=6831; t=1176310317;
	x=1177174317; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In
	=20Defense=20of=20Explicit=20Operations |Sender:=20
	|To:=20=22Huelsemann,=20Martin=22=20<Martin.Huelsemann@t-com.net>;
	bh=7QENLg+hQQmibUtXMTxcyleOQQGErjRUtBBJH/HkGBA=;
	b=alSLyJe7toqj8HXk35bdFNNMXELb3guF0gnyC2m3T9sywYAsWORuPstvc2HvXGGenKMfZlmk
	qtaPWElTeKRi2CRjUJ0ZXHE1QshxgH3lo33/p+FYSYTwRQDdTeVhpKY9;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: sipping@ietf.org, adam@nostrum.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Huelsemann, Martin wrote:
> So what is really meant by (and explained really badly in) the Poetzl draft is that a user subscribes to his own call-completion state, and the events he is informed of are the transition of his state from any state to the 'queued' state and from any state to the 'start the recall' state.
> The notifier has to derive this state from the state of the call-completion queue. The nature of the queue and how the call-completion state for a user is derived from the queue are not explained, but it is assumed that the queue and the notifier are collocated and can interact. A FIFO queue could be a suitable basis for the queue, although other models are not precluded.

Yes, this is one way to look at the proposal. I posted an earlier reply 
with a similar interpretation.

> True is that the user's subscription also creates the resource, which is his own call-completion state. The question is, is that problematical, and why? 

Agreed.

I think it is problematical. For instance, if the subscription gets 
terminated for some reason, position in queue is lost. One may be able 
to establish a new subscription, but then goes to the end of the line. 
This could be a problem for instance with a mobile device that loses 
connectivity for a period of time.

> The next question of course would be, is it problematical to transport bodies with queue manipulation information within the SUBSCRIBEs. 
> On the other hand, you can interprete suspending and resuming as something like a filter, too. Nothing changes, neither the call-completion queue, the user's position remains the same, nor the resource, the call-completion state of a user remains 'queued'. The user just doesn't receive NOTIFYs for a certain time. Only after resuming the call-completion state might change, but then because of B has become not busy again.

Suspending has more of an effect that that. If I understand the intent, 
calls are only to be accepted from the currently selected candidate, 
which is the entry nearest to the top of the queue that is not 
suspended. So suspending has effect on the state of the queue, rather 
than simply being a filter on the subscription.

	Paul

> Martin
> 
> 
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
>> Gesendet: Mittwoch, 11. April 2007 16:16
>> An: Hülsemann, Martin
>> Cc: adam@nostrum.com; sipping@ietf.org
>> Betreff: Re: AW: [Sipping] Call Completion: In Defense of 
>> Explicit Operations
>>
>>
>>
>>
>> Huelsemann, Martin wrote:
>>> I think the part of the solution where are no doubts is 
>> that we can use SUB/NOT to inform the user about his 
>> call-completion state (queued, or he is the one who shall 
>> start the recall). IF we decide for a SIP solution, which I 
>> think we should do if there are no technical reasons against, 
>> because BFCP seem to be easy to implement with the necassary 
>> knowledge, but it is still another protocol. 
>>> The question is, when SUBSCRIBEs are used anyway, why can't 
>> we reuse them for queue manipulation actions? Why put another 
>> RFC into the terminal, when RFC 3265 would be enough. The 
>> simpler those terminals are, the cheaper they will be, and 
>> the more people will use them. 
>>> Yes, using the SUBSCRIBE also for queue manipulations would 
>> be one operation with two effects, but where is the harm? 
>> There is a similar use in the policy package, which submits 
>> an SDP in the SUBSCRIBE request and gets back a policy for 
>> that SDP in the NOTIFY request.
>>
>> Lets go through this again:
>>
>> Suppose it does work that way. Then conceptually what is the 
>> event state 
>> that is being subscribed to? Apparently it is the queue of potential 
>> callers. In principle, every time this state changes there 
>> should be a 
>> notification sent to *all* the subscribers.
>>
>> Now it could be that policy is used to restrict how much visibility 
>> subscribers have to the event state. So the views of some may be such 
>> that they can't see the change, and so get no notification of it. But 
>> arranging things that way requires structuring the state very 
>> carefully. 
>> For instance, the policy might state that a subscriber can only see 
>> entries that refer to them. But this wouldn't be very 
>> interesting unless 
>> their entry included "position in queue". That would result 
>> in getting a 
>> notification each time your entry advanced in the queue. If that is 
>> annoying there could be a filter that says to only display 
>> entries that 
>> are "first in queue".
>>
>> None of that says anything about queue manipulation - just 
>> using sub/not 
>> to observer a queue in a useful way for this purpose.
>>
>> Note that we do have an example where the act of subscribing creates 
>> state that can itself be subscribed to. It is watcherinfo. 
>> But in that 
>> case there are two event packages in use - e.g. presence and 
>> presence.watcherinfo. Subscribing to presence creates watcher 
>> state that 
>> can be observed by subscribing to presence.watcherinfo. Having a 
>> SUBSCRIBE modify the state of the event being subscribed to 
>> introduces a 
>> sort of Heisenberg Uncertainty Principle - you can't observe 
>> the event 
>> without affecting it.
>>
>> Specifically, it becomes impossible to observe the queue without 
>> becoming one of the requesters. For instance, suppose the queue was 
>> managed on a server separate from the UAs that receive calls to the 
>> target AOR. They may want to observe the queue themselves. But 
>> attempting to do so would seem to cause them to become candidates to 
>> call themself. This could be mitigated by requesting that the 
>> entry be 
>> suspended, but the point remains.
>>
>> Further manipulation of the queue, such as suspend and resume, also 
>> doesn't seem to fit the sub/not model very well. If its done 
>> as part of 
>> the body (as the current draft specifies) then it should be 
>> considered a 
>> filter, but filters don't change state of the event - only 
>> the view of 
>> it. There isn't any good place to specify this kind of action in a 
>> subscribe request, for the obvious reason that SUBSCRIBE 
>> isn't intended 
>> to be used in that way.
>>
>> I have seen reference to the policy event package as 
>> precedent for using 
>> bodies to create the state being subscribed to. I think that case is 
>> less of a problem because it does fall into a suitable 
>> conceptual model 
>> as a filter. In theory one is subscribing to all policies. 
>> Supplying a 
>> body can be viewed as simply a filter restricting 
>> notifications to ones 
>> pertaining to a particular set of media, etc.
>>
>> 	Paul
>>
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 13:51:05 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hbgx0-00081P-F2; Wed, 11 Apr 2007 13:49:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hbgwy-00081C-QA
	for sipping@ietf.org; Wed, 11 Apr 2007 13:49:44 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hbgwx-0001By-DW
	for sipping@ietf.org; Wed, 11 Apr 2007 13:49:44 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3BHncXc043080
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 11 Apr 2007 12:49:38 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461D1FB8.2070500@nostrum.com>
Date: Wed, 11 Apr 2007 12:49:44 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>	<461B8FB7.3000903@nostrum.com>	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>	<461BCAD7.1020001@nostrum.com>
	<34668222-C8B1-41FE-9519-530FDFE92BFA@softarmor.com>
	<461BE0CC.8010403@nostrum.com>
	<4B7406B6-B323-43B1-B7BB-2843CD105F65@softarmor.com>
In-Reply-To: <4B7406B6-B323-43B1-B7BB-2843CD105F65@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: SIPPING WG <sipping@ietf.org>,
	Xavier Marjou <xavier.marjou@orange-ftgroup.com>,
	"Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dean:

Yes, yes, yes!

What you say below is absolutely correct. Defining an event package that 
subscribes -- unobtrusively -- to a queue state is a perfectly valid 
**part** of a solution. (It's not what I proposed in my draft because 
such notification would be redundant with BFCP mechanisms -- but if 
there were some other sensible way to manipulate the queue, it would 
have been exactly what I would have proposed).

In particular, you make a point that is precisely congruent with the key 
point that I've been trying to make; to wit:

> The important thing is to keep in mind that the queue is a document 
> being edited by an application whose operation is driven by 
> information (perhaps other subscriptions, such as presence) that is 
> EXTERNAL to the queue itself.

Yes! Absolutely! That is completely and utterly correct! And that is 
what is primarily wrong with draft-poetzl.

/a


Dean Willis wrote:
>
> On Apr 10, 2007, at 2:09 PM, Adam Roach wrote:
>
>> Dean Willis wrote:
>>>> If we can't do that, we need some mechanism to handle the queueing 
>>>> -- and SUBSCRIBE/NOTIFY aren't queue management methods.
>>>>
>>>
>>>
>>> I've been pondering that assertion, and can't see why the queue 
>>> modeled as a document with filtering on what part of the document is 
>>> visible isn't a reasonable approach to an event package.
>>
>> Interesting. Continue.
>>
>> No, really -- what state is the user subscribing to? What changes 
>> this state? How is the filter being specified? How does a user's 
>> position in the queue get suspended? Resumed?
>>
>
> It's not all that different from sip config.
>
> The state is the content of a document describing the queue, which 
> could certainly be modeled in XML, versioned with etag, and so on.
>
> The document is modified by the queue manager, for example by adding a 
> queue element, changing the pointer to the "current" queue element, or 
> deleting a queue element. It might contain explicit ordering or 
> priority rankings.
>
> One can envision that the queue manager's operations on the document 
> would be driven by events outside of subscriptions to the queue state, 
> just as changes in sip-config documents or resource lists are driven 
> by events outside of subscriptions to those documents.
>
> Filtering is the tricky question. Let's step back and see what the 
> requirements are:
>
> 1) The watcher needs to know when they're the "current" element and 
> should make a call.
>
> 2) We MAY have a requirement to give the watcher some sense of 
> position in the queue, as in "There are currently 487 callers ahead of 
> you".
>
> 3) We MUST NOT disclose the identity of other pending callers.
>
> 4) We need to be able to change the state of the queue to "suspended" 
> when the queue target is busy, either in dealing with a queued call or 
> an outside call.
>
> 5) We probably have a need to correlate incoming calls against the 
> queue set, so that callers who are not currently pending can be 
> enqueued instead of preempting the queue.
>
> So let's take a simplistic approach for initial analysis: the queue 
> consists of an ordered set of elements (a vector), each of which 
> represents either one pending call or the "suspended" state. The first 
> element is the "active" element. If a watcher of this document sees 
> that the first element corresponds to them, they launch a new INVITE, 
> using some component of the element as a parameter so that the queue 
> manager can match them up. If the queue is in a suspended state, the 
> first element is one which encodes "suspended".
>
> This seems to satisfy requirements 1,2,4, and 5 above.
>
> Let's play a bit with #4 -- disclosing of identity of pending call 
> sources.
>
> One possibility is to use an opaque token per caller (which might be 
> the same token that is used in the call setup). Alice calls into Bob, 
> gets a response containing a queue URI and a token for her position. 
> She watches the queue until her token comes up to the top, then calls in.
>
> The above works just fine, but raises the possibility of "queue 
> jumping" -- an aggressive watcher might just take whatever token is 
> currently at the top and use it.
>
> We could offset this by adding a filter. One approach might be for the 
> queue-watching subscription to include the token-of-interest, which 
> would be applied by the queue manager (which is serving as the event 
> source). On a per-subscription basis, the queue manager would "mask" 
> tokens other than the "token of interest" for that subscription with a 
> dummy value.
>
> So Alice, who is subscribed to the callback queue for Bob, might 
> receive a NOTIFY containing a queue document with a "suspended" 
> element, three "dummy" elements, an element containing her token, and 
> two more "dummy" elements. From this she would know that the queue is 
> currently blocked, there are three callers ahead of her, and two 
> callers behind her. Moments later, she might see a new NOTIFY without 
> the "suspended" element at its head, and deduce that the last caller 
> is now off the line and a new one likely to be calling in. Eventually 
> she receives a NOTIFY with a queue document with her token at the 
> head, and calls in.
>
> Myriad other queue representations and filtration strategies seem 
> feasible depending on what constraints one wishes to adopt.
>
> The important thing is to keep in mind that the queue is a document 
> being edited by an application whose operation is driven by 
> information (perhaps other subscriptions, such as presence) that is 
> EXTERNAL to the queue itself.
>
> I think this fits into the basic SUBSCRIBE/NOTIFY framework.
>
> -- 
> Dean


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 14:16:52 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbhN0-0003sI-9i; Wed, 11 Apr 2007 14:16:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbhMy-0003sD-K4
	for sipping@ietf.org; Wed, 11 Apr 2007 14:16:36 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbhMx-0000X7-Ak
	for sipping@ietf.org; Wed, 11 Apr 2007 14:16:36 -0400
Received: from [206.176.144.212] (rcdn4-dmznat-gw1-nat-27.cisco.com
	[12.5.186.27]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3BHNCGu029267
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 11 Apr 2007 12:23:13 -0500
In-Reply-To: <461D1FB8.2070500@nostrum.com>
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>	<461B8FB7.3000903@nostrum.com>	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>	<461BCAD7.1020001@nostrum.com>
	<34668222-C8B1-41FE-9519-530FDFE92BFA@softarmor.com>
	<461BE0CC.8010403@nostrum.com>
	<4B7406B6-B323-43B1-B7BB-2843CD105F65@softarmor.com>
	<461D1FB8.2070500@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E4E23388-C9F3-422D-B16E-DAD0114F096B@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Wed, 11 Apr 2007 13:16:24 -0500
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 11, 2007, at 12:49 PM, Adam Roach wrote:

> Dean:
>
> Yes, yes, yes!
>
> What you say below is absolutely correct. Defining an event package  
> that subscribes -- unobtrusively -- to a queue state is a perfectly  
> valid **part** of a solution. (It's not what I proposed in my draft  
> because such notification would be redundant with BFCP mechanisms  
> -- but if there were some other sensible way to manipulate the  
> queue, it would have been exactly what I would have proposed).
>
> In particular, you make a point that is precisely congruent with  
> the key point that I've been trying to make; to wit:
>
>> The important thing is to keep in mind that the queue is a  
>> document being edited by an application whose operation is driven  
>> by information (perhaps other subscriptions, such as presence)  
>> that is EXTERNAL to the queue itself.
>
> Yes! Absolutely! That is completely and utterly correct! And that  
> is what is primarily wrong with draft-poetzl.
>

So it would be reasonable to say that it is not the concept of an  
event package for call completion that bothers you. It's the  
intertwingling of "subscription to the events" and "enrollment in the  
queue" that bothers you. That would bother me too -- I think I simply  
assumed that aspect of the Poetzl draft was a misunderstanding that  
remained to be worked out, because it clearly doesn't work right.

This should be resolvable, because it's relatively straightforward to  
use an INVITE side-effect (aka a "factory") to enqueue. The cleanest  
approach might require an additional 4xx response code, semantic  
"enqueued", along with a new header field for returning the queue  
URI. I suppose one could simply use the new header field along with a  
480 (Temporarily Unavailable) response code as an even lighter solution.

What's the remaining problem? Manipulating the queue itself? Why is  
that a problem?

--
Dean

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 14:29:34 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbhZ0-0001Hz-H3; Wed, 11 Apr 2007 14:29:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbhYz-0001Hs-1n
	for sipping@ietf.org; Wed, 11 Apr 2007 14:29:01 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbhYx-00039A-Oz
	for sipping@ietf.org; Wed, 11 Apr 2007 14:29:01 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3BISulM044971
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 11 Apr 2007 13:28:57 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461D28EE.4070904@nostrum.com>
Date: Wed, 11 Apr 2007 13:29:02 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
	<461CED8F.60501@cisco.com>
	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>
In-Reply-To: <4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: Paul Kyzivat <pkyzivat@cisco.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dean Willis wrote:
> So the open question is how does one get into the queue without having 
> that insertion be a side-effect of the subscription itself?
>
> Two options:
>
> 1) Automatically enqueue all callers when there is a queue.

Interesting approach -- I'm not sure how well it will work in practice, 
because you'll end up having to wait for the queue of missed calls from 
disinterested parties to drain before your position percolates to the 
top of the queue. It's probably solvable, but we'd need to come up with 
something.

> 2) Redirect (or indirect via a new header field) callers to a queue 
> factory when there is a queue. If they follow the indirection, they 
> get enqueued.

Ooh. Run this one by Dave Oran. Perhaps we can get him to give his 
"To-Explode-My-Phone:" speech again.

> I concur that insertion into the queue and subscription to the queue 
> must be different things. That seems obvious, so I must have missed 
> the idea that they were intertwingled (or dismissed it as just silly).

Yes, they must be different things. Yes, this is obvious. Yes, it is 
silly to propose that they be combined into the same operation. Yes, 
this very silly thing is at the core of the draft-poetzl proposal.

> Operations on the queue data itself are clearly outside of the 
> "watcher" package. If the queue notification is handled on a node that 
> is different from the node with the data that drives the queue, then 
> we have XCAP to manipulate the queue document and make insertions, etc.

_That's_ interesting. I hadn't thought of that. So, instead of using 
BFCP (as my current proposal suggests), we could use an event package to 
unobtrusively subscribe to a queue, and XCAP to place ourselves in, 
pause, resume, and remove ourselves from the queue.

That seems quite reasonable. I'd be interested to see what other people 
have to say about it.

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 14:52:00 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hbhu6-0004UR-BM; Wed, 11 Apr 2007 14:50:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hbhu4-0004Pm-P4
	for sipping@ietf.org; Wed, 11 Apr 2007 14:50:48 -0400
Received: from panorama.covad.com ([66.134.72.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hbhu4-0000xJ-5o
	for sipping@ietf.org; Wed, 11 Apr 2007 14:50:48 -0400
Received: from zanxmb00b.cc-ntd1.covad.com (zanxmb00b.corp.covad.com
	[172.16.2.76])
	by panorama.Covad.COM (8.9.3/8.8.7) with ESMTP id BAA06508;
	Thu, 12 Apr 2007 01:50:45 +0700 (GMT)
Received: from ZANEVS03.cc-ntd1.covad.com ([172.16.2.83]) by
	zanxmb00b.cc-ntd1.covad.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Apr 2007 11:50:45 -0700
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
Subject: RE: [Sipping] Session Establishment Efficiency Rate
Date: Wed, 11 Apr 2007 11:50:44 -0700
Message-ID: <3BC5D44AB71A754FAE3CA68A7597EABEB7BB33@ZANEVS03.cc-ntd1.covad.com>
In-Reply-To: <97F2AD7AA4EAD948827639B06CF2745FD05740@esealmw106.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Session Establishment Efficiency Rate
Thread-Index: Acd7ornco3eIaTU2RqKNmzyJ2d4zhgAhL19AAA/WkEA=
From: "Fardid, Reza" <RFardid@Covad.COM>
To: "Marian Delkinov \(LN/EAB\)" <marian.delkinov@ericsson.com>,
	"Daryl Malas" <daryl@level3.net>
X-OriginalArrivalTime: 11 Apr 2007 18:50:45.0555 (UTC)
	FILETIME=[50192030:01C77C6A]
X-TM-AS-Product-Ver: SMEX-7.0.0.1345-3.6.1039-15110.000
X-TM-AS-Result: No--23.088400-0.000000-31
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 16a2b98d831858659c646b3dec9ed22b
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Agreed. This is a good change to both SER and SEER definitions.
There is, however, an implicit assumption that call-legs can be properly
correlated to produce Total Call Attempts.  A note to this effect may be
worth adding to either section 5.1 or 5.3.

Regards,
-Reza



-----Original Message-----
From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]=20
Sent: Wednesday, April 11, 2007 3:55 AM
To: Daryl Malas
Cc: Fardid, Reza; sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Hi Daryl,

Precisely!=20

Best regards!
Mario.

-----Original Message-----
From: Daryl Malas [mailto:daryl@level3.net]=20
Sent: Tuesday, 10 April, 2007 21:15
To: Marian Delkinov (LN/EAB)
Cc: Fardid, Reza; sipping@ietf.org
Subject: RE: [Sipping] Session Establishment Efficiency Rate

Okay...I think I understand your point.  The denominator needs to be
clarified in Section 3.6 and then relative to SEER.  It needs to make
sure it does not include INVITE's that are redirected or similar, as
this will skew the data.  Is this what you are referring to?

--Daryl

On Tue, 2007-04-10 at 20:39 +0200, Marian Delkinov (LN/EAB) wrote:
> Daryl,
>=20
> I understand what you mean and with the condition about the same Call=20
> ID, I agree with it. The reason for my comments as  I wrote you=20
> earlier, was the inclusion of #INVITE in the formula. What you are=20
> talking about should perhaps be described as #Call Attempts. Because=20
> if we consider all INVITEs with same Call ID as 1 call attempt and put

> that in the formula, then everything fits on place.
>=20
> In that case the definition would look:
>=20
> SEER =3D (#Invite w/200 OK + #480 + #486 + #600)/# Total Call Attempts
>=20
> (with note e.g: #Total Call Attempts =3D # distinct(Call_IDs)
>=20
> What worries me yet is how we handle the forking.=20
>=20
> Best regards!
> Mario.
> =20
>=20
> -----Original Message-----
> From: Daryl Malas [mailto:daryl@level3.net]
> Sent: Tuesday, 10 April, 2007 19:08
> To: Marian Delkinov (LN/EAB)
> Cc: Fardid, Reza; sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
>=20
> It sends a new INVITE, but the call id doesn't change.  This allows=20
> tools to identify it as the same call or 1 OK/ 1 INVITE =3D 100% SER.
>=20
> --Daryl
>=20
> On Tue, 2007-04-10 at 15:57 +0200, Marian Delkinov (LN/EAB) wrote:
> > Reza,
> >=20
> > As far as I know the standard telephony - it functions a bit=20
> > differently. For instance if a user activates a service as "Call=20
> > Diversion" (similar to redirect in SIP), it's the network that=20
> > handles
>=20
> > that hidden for the calling party, i.e. the caller does not need to=20
> > dial another number. And when such case occurs, in terms of PSTN for

> > the calling party it's 1 call (1 seizure produced) only. Or in NER=20
> > formula you will have:
> >=20
> > (1 answer, or RNA, or BUSY etc)/ 1 call =3D 100% NER
> >=20
> > If we try to apply same to SIP. When redirect is received, the UA=20
> > has to send another INVITE, right? (Tell me if I'm wrong). And if we

> > count
>=20
> > the 300 code as network failure, and assume the second INVITE is=20
> > successful, then we have:
> >=20
> > 1 OK /2 #INVITE =3D 50% SEER, which IMO isn't correct. Do you agree, =

> > or please explain.
> >=20
> > Best regards!
> > Mario.
> >=20
> > -----Original Message-----
> > From: Fardid, Reza [mailto:RFardid@Covad.COM]
> > Sent: Monday, 09 April, 2007 20:05
> > To: Marian Delkinov (LN/EAB); Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > Mario,
> >=20
> > IMO, if the objective is to eliminate called party behavior from ASR

> > (and SER), minimally the following response codes need to be
excluded:
> > User Busy		~480
> > RNA			~486
> > Busy Everywhere	~600
> >=20
> > I fail to see how exclusion of 3xx, other 4xx, and 6xx codes (with=20
> > the
>=20
> > possible exception of 603) will serve this objective.
> >=20
> > It appears that the metric you are proposing has a much broader
scope.
> > Perhaps, the confusion is caused by the inclusion of "user agent"
> > behavior in the definition of SEER, which should only exclude the=20
> > effects of "called party" behavior.
> >=20
> > Regards,
> > -Reza
> >=20
> > 	=09
> >=20
> >=20
> >=20
> >=20
> >=20
> > -----Original Message-----
> > From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> > Sent: Tuesday, April 03, 2007 3:28 AM
> > To: Fardid, Reza; Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > Reza,
> >=20
> > Exactly because of the analogy with NER and the meaning it has as=20
> > telephony metric I wanted to make clear the right counters,=20
> > including for release codes, are used to achieve the same meaning in

> > SIP. I didn't understand for when you foresee the implementation?
> >=20
> > Best regards!
> > Mario.
> >=20
> > -----Original Message-----
> > From: Fardid, Reza [mailto:RFardid@Covad.COM]
> > Sent: Friday, 30 March, 2007 22:02
> > To: Marian Delkinov (LN/EAB); Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > Mario,
> >=20
> > What I had in mind when I proposed inclusion of SEER in this draft=20
> > was
>=20
> > a SIP performance metric analogous to NER in the PSTN, within the=20
> > framework defined by Daryl:
> >=20
> > Telephony Metric/Standard (ITU-T, BellCore, etc.) =3D=3D> SIP ETE =
Metric
> >=20
> > Clearly some SIP metrics defined in this draft do not have a=20
> > telephony
>=20
> > counterpart.  For the rest, IMO, it is good to stay within the above

> > framework and leave exclusion/inclusion of specific release codes=20
> > from
>=20
> > defined metrics to implementation.
> >=20
> > Regards,
> > Reza Fardid
> > Covad Communications
> >=20
> >=20
> > -----Original Message-----
> > From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> > Sent: Thursday, March 29, 2007 1:07 AM
> > To: Daryl Malas
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > Hi Daryl,
> >=20
> > I haven't got your opinion about my comments on the SEER definition.
> > Have you considered them?=20
> > Would also be interested to know when a finalized document on the=20
> > performance metrics can be released.
> >=20
> > Thanks!
> >=20
> > Best regards!
> > Mario.
> >=20
> > -----Original Message-----
> > From: Marian Delkinov (LN/EAB)
> > Sent: Monday, 05 March, 2007 17:06
> > To: 'Daryl Malas'
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > Hi Daryl,
> >=20
> > In principle, I agree with you in case we considered this from a=20
> > user perspective - then 3xx is not final. However my idea behind=20
> > including the 3xx codes was based on the involvement of "#Invite" in

> > the
> formula.
> > If a 3xx code would result in sending a new Invite, then it sounds=20
> > logical to me to add the 3xx codes in the numerator. (NB: RFC3261=20
> > defines 3xx responses as "final" for the SIP transaction, ref. to=20
> > page
>=20
> > 21, Final Response).
> >=20
> > Best regards!
> > Mario.
> >=20
> > =20
> >=20
> > -----Original Message-----
> > From: Daryl Malas [mailto:daryl@level3.net]
> > Sent: Friday, 23 February, 2007 17:00
> > To: Marian Delkinov (LN/EAB)
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> >=20
> > I don't think 3xx codes should be included, since they would not be=20
> > considered a "Final" release cause code.  --Daryl
> >=20
> > On Fri, 2007-02-23 at 12:22 +0100, Marian Delkinov (LN/EAB) wrote:
> > > Hi,
> > >=20
> > > If the Network Efficiency Rate is designed to express the ability=20
> > > of
>=20
> > > the network to deliver calls (in SIP terms one should perhaps say=20
> > > "establish sessions"), I think that it might be reasonable to=20
> > > include few more cases (cause codes) in the numerator: e.g. all=20
> > > redirection 3xx codes, all 4xx except 408 codes and all 6xx codes.
> > > (If you agree that those are the ones that exclude network=20
> > > failures,
>=20
> > > congestion and any other network malfunction).
> > >=20
> > > Actually it sounds fair to me if it's the opposite of the=20
> > > Ineffective Session Attempts (ISA):
> > > SEER% =3D
> > > 	   Total # of Invite Requests - # of ISA
> > > ---------------------------------------------------- x 100
> > > 	   Total # of Invite Requests
> > >=20
> > > What do you think?
> > >=20
> > > Best regards!
> > > Mario.
> > >=20
> > > -----Original Message-----
> > > From: Daryl Malas [mailto:daryl@level3.net]
> > > Sent: Friday, 23 February, 2007 01:14
> > > To: sipping@ietf.org
> > > Subject: [Sipping] Session Establishment Efficiency Rate
> > >=20
> > > A couple more people have expressed to me that this adaptation of=20
> > > the ITU-T E.411 Network Efficiency Rate metric is very valuable.
> > > The snapshot of the metric from the draft is:
> > >=20
> > > "This metric is similar to Session Establishment Rate, but it is=20
> > > intended to exclude the effects of customer behavior and user=20
> > > agent behavior.  Essentially, the attempts resulting with a final=20
> > > cause code
> >=20
> > > of 480, 486, and 600 would be added to the SER numerator."
> > >=20
> > > Does anyone else want to see this metric in the draft?  I=20
> > > personally
>=20
> > > think it is an interesting metric.
> > >=20
> > > Thanks...
> > >=20
> > > --Daryl
> > >=20
> > >=20
> > >=20
> > > _______________________________________________
> > > Sipping mailing list =20
> > > https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP Use=20
> > > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > > sip@ietf.org for new developments of core SIP
> >=20
> >=20
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 14:56:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbhzO-0007OX-29; Wed, 11 Apr 2007 14:56:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbhzN-0007OK-1Z
	for sipping@ietf.org; Wed, 11 Apr 2007 14:56:17 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbhzL-00028c-Ka
	for sipping@ietf.org; Wed, 11 Apr 2007 14:56:17 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-5.cisco.com with ESMTP; 11 Apr 2007 11:56:13 -0700
X-IronPort-AV: i="4.14,395,1170662400"; 
	d="scan'208"; a="410380944:sNHT51749394"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l3BIuD0s026142; 
	Wed, 11 Apr 2007 11:56:13 -0700
Received: from [10.32.245.157] (stealth-10-32-245-157.cisco.com
	[10.32.245.157])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l3BIu8A8020175;
	Wed, 11 Apr 2007 18:56:12 GMT
In-Reply-To: <461D28EE.4070904@nostrum.com>
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
	<461CED8F.60501@cisco.com>
	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>
	<461D28EE.4070904@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <ECD8E8E9-9DAD-4C7A-9FB1-A4F26F57E994@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Wed, 11 Apr 2007 14:56:01 -0400
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3375; t=1176317773;
	x=1177181773; c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defen
	se=20of=20Explicit=20Operations |Sender:=20;
	bh=Hx03uR9mf4R0sJpACtgR8qZJY75yZYJB+u0bIWeweAo=;
	b=ZcBFqcmynVsNcsiOrZOIM6EOTmudhf12AqjZSVIWBSB8mS/60W9Jy3kvp1t4jMLSYQZN5/3Z
	P2kLb/CQdnAmR65hHUaarURyGhyjmH/gVe2ELPwgnmL6LwqhsSbNVXNk;
Authentication-Results: sj-dkim-6; header.From=oran@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim6002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: Paul Kyzivat <pkyzivat@cisco.com>, sipping@ietf.org,
	Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 11, 2007, at 2:29 PM, Adam Roach wrote:

> Dean Willis wrote:
>> So the open question is how does one get into the queue without  
>> having that insertion be a side-effect of the subscription itself?
>>
>> Two options:
>>
>> 1) Automatically enqueue all callers when there is a queue.
>
> Interesting approach -- I'm not sure how well it will work in  
> practice, because you'll end up having to wait for the queue of  
> missed calls from disinterested parties to drain before your  
> position percolates to the top of the queue. It's probably  
> solvable, but we'd need to come up with something.
>
>> 2) Redirect (or indirect via a new header field) callers to a  
>> queue factory when there is a queue. If they follow the  
>> indirection, they get enqueued.
>
> Ooh. Run this one by Dave Oran. Perhaps we can get him to give his  
> "To-Explode-My-Phone:" speech again.
>
I'm not sure I'd use a 305 redirect. If we had hexadecimal response  
codes, I'd suggest assigning 3-C4.

Seriously though, if we make "holding queues" first-class objects  
(i.e. they have URIs) then one might instead think of this  
analogously to call park, where you can park yourself and get  
notified through the queue/park agent by REFER to try they original  
call again. What does seem common to any SIP-only approach is the  
notion that the caller has an active dialog with *something* until  
such time as he gets to re-try the call to the original callee or  
abandon the operation.

>> I concur that insertion into the queue and subscription to the  
>> queue must be different things. That seems obvious, so I must have  
>> missed the idea that they were intertwingled (or dismissed it as  
>> just silly).
>
> Yes, they must be different things. Yes, this is obvious. Yes, it  
> is silly to propose that they be combined into the same operation.  
> Yes, this very silly thing is at the core of the draft-poetzl  
> proposal.
>
This seems to be one point which is common to the objections to using  
the subscribe/notify machinery. I agree too.

>> Operations on the queue data itself are clearly outside of the  
>> "watcher" package. If the queue notification is handled on a node  
>> that is different from the node with the data that drives the  
>> queue, then we have XCAP to manipulate the queue document and make  
>> insertions, etc.
>
> _That's_ interesting. I hadn't thought of that. So, instead of  
> using BFCP (as my current proposal suggests), we could use an event  
> package to unobtrusively subscribe to a queue, and XCAP to place  
> ourselves in, pause, resume, and remove ourselves from the queue.
>
> That seems quite reasonable. I'd be interested to see what other  
> people have to say about it.
>
If what we want to model is a queue, this makes sense. On the other  
hand, the externally visible behavior does not inherently require a  
queue, in the sense of allowing operations such as head(), tail(),  
count(), enqueue_head(), enqueue_tail(), etc.

> /a
>
> _______________________________________________
> Sipping mailing list  https://www1.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

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 15:49:06 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbioC-0008BH-JN; Wed, 11 Apr 2007 15:48:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbioB-0008BC-Gl
	for sipping@ietf.org; Wed, 11 Apr 2007 15:48:47 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hbio9-0001ss-KE
	for sipping@ietf.org; Wed, 11 Apr 2007 15:48:47 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3BJmD0J048950
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 11 Apr 2007 14:48:36 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461D3B83.7000309@nostrum.com>
Date: Wed, 11 Apr 2007 14:48:19 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>	<461B8FB7.3000903@nostrum.com>	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>	<461BCAD7.1020001@nostrum.com>	<34668222-C8B1-41FE-9519-530FDFE92BFA@softarmor.com>	<461BE0CC.8010403@nostrum.com>	<4B7406B6-B323-43B1-B7BB-2843CD105F65@softarmor.com>	<461D1FB8.2070500@nostrum.com>
	<E4E23388-C9F3-422D-B16E-DAD0114F096B@softarmor.com>
In-Reply-To: <E4E23388-C9F3-422D-B16E-DAD0114F096B@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dean Willis wrote:
> So it would be reasonable to say that it is not the concept of an 
> event package for call completion that bothers you. It's the 
> intertwingling of "subscription to the events" and "enrollment in the 
> queue" that bothers you.

Reasonable and accurate.

> That would bother me too -- I think I simply assumed that aspect of 
> the Poetzl draft was a misunderstanding that remained to be worked 
> out, because it clearly doesn't work right.
>
> This should be resolvable, because it's relatively straightforward to 
> use an INVITE side-effect (aka a "factory") to enqueue. The cleanest 
> approach might require an additional 4xx response code, semantic 
> "enqueued", along with a new header field for returning the queue URI. 
> I suppose one could simply use the new header field along with a 480 
> (Temporarily Unavailable) response code as an even lighter solution.

There's probably a mechanism in that direction -- somehow communicating 
a factory URI for the purpose of enqueueing, using INVITE (open issue: 
to what kind of session? Media-free?) to enqueue, and tearing down the 
session to dequeue.

(The "new header field with a URI for activating a feature" proposal is 
why I invoked Dave Oran, referring to his impassioned speech at the 
London IETF SIP meeting arguing _against_ the use of feature-specific 
header fields containing URIs for activating the corresponding feature. 
The reductio ad absurdum he used was a header field called 
"To-Explode-My-Phone:", containing a request URI, presumably used for 
that purpose. At the time, I thought he had a good point, but I can't 
seem to reconstitute the argument at the moment.)

> What's the remaining problem? Manipulating the queue itself? Why is 
> that a problem?

Your question implies that you think this is a solved problem. Great! In 
that case, it would be no problem for you to answer the following two 
questions:

   1. How does the queued caller pause their position in the queue?
   2. How does the queued caller un-pause their position in the queue?

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 15:54:27 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbisX-0002eA-OW; Wed, 11 Apr 2007 15:53:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbisU-0002co-EH
	for sipping@ietf.org; Wed, 11 Apr 2007 15:53:14 -0400
Received: from hme1.july.broomfield1.level3.net ([209.245.18.8]
	helo=f4bb49-05.idc1.level3.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbisT-0003Jl-S8
	for sipping@ietf.org; Wed, 11 Apr 2007 15:53:14 -0400
Received: from montag.eng.level3.com (montag.eng.l3.com [10.1.68.57])
	by f4bb49-05.idc1.level3.com (8.12.10/8.12.10) with ESMTP id
	l3BJr9oK017072; Wed, 11 Apr 2007 19:53:09 GMT
Subject: RE: [Sipping] Session Establishment Efficiency Rate
From: Daryl Malas <daryl@level3.net>
To: "Fardid, Reza" <RFardid@covad.com>
In-Reply-To: <3BC5D44AB71A754FAE3CA68A7597EABEB7BB33@ZANEVS03.cc-ntd1.covad.com>
References: <3BC5D44AB71A754FAE3CA68A7597EABEB7BB33@ZANEVS03.cc-ntd1.covad.com>
Content-Type: text/plain
Date: Wed, 11 Apr 2007 14:06:04 -0600
Message-Id: <1176321964.17141.142.camel@montag.eng.level3.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.0 (2.6.0-1) 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bd8a74b81c71f965ca7918b90d1c49c0
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Good idea.  I'll add some context to it in those sections.
Thanks...--Daryl

On Wed, 2007-04-11 at 11:50 -0700, Fardid, Reza wrote:
> Agreed. This is a good change to both SER and SEER definitions.
> There is, however, an implicit assumption that call-legs can be properly
> correlated to produce Total Call Attempts.  A note to this effect may be
> worth adding to either section 5.1 or 5.3.
> 
> Regards,
> -Reza
> 
> 
> 
> -----Original Message-----
> From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com] 
> Sent: Wednesday, April 11, 2007 3:55 AM
> To: Daryl Malas
> Cc: Fardid, Reza; sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
> 
> Hi Daryl,
> 
> Precisely! 
> 
> Best regards!
> Mario.
> 
> -----Original Message-----
> From: Daryl Malas [mailto:daryl@level3.net] 
> Sent: Tuesday, 10 April, 2007 21:15
> To: Marian Delkinov (LN/EAB)
> Cc: Fardid, Reza; sipping@ietf.org
> Subject: RE: [Sipping] Session Establishment Efficiency Rate
> 
> Okay...I think I understand your point.  The denominator needs to be
> clarified in Section 3.6 and then relative to SEER.  It needs to make
> sure it does not include INVITE's that are redirected or similar, as
> this will skew the data.  Is this what you are referring to?
> 
> --Daryl
> 
> On Tue, 2007-04-10 at 20:39 +0200, Marian Delkinov (LN/EAB) wrote:
> > Daryl,
> > 
> > I understand what you mean and with the condition about the same Call 
> > ID, I agree with it. The reason for my comments as  I wrote you 
> > earlier, was the inclusion of #INVITE in the formula. What you are 
> > talking about should perhaps be described as #Call Attempts. Because 
> > if we consider all INVITEs with same Call ID as 1 call attempt and put
> 
> > that in the formula, then everything fits on place.
> > 
> > In that case the definition would look:
> > 
> > SEER = (#Invite w/200 OK + #480 + #486 + #600)/# Total Call Attempts
> > 
> > (with note e.g: #Total Call Attempts = # distinct(Call_IDs)
> > 
> > What worries me yet is how we handle the forking. 
> > 
> > Best regards!
> > Mario.
> >  
> > 
> > -----Original Message-----
> > From: Daryl Malas [mailto:daryl@level3.net]
> > Sent: Tuesday, 10 April, 2007 19:08
> > To: Marian Delkinov (LN/EAB)
> > Cc: Fardid, Reza; sipping@ietf.org
> > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > 
> > It sends a new INVITE, but the call id doesn't change.  This allows 
> > tools to identify it as the same call or 1 OK/ 1 INVITE = 100% SER.
> > 
> > --Daryl
> > 
> > On Tue, 2007-04-10 at 15:57 +0200, Marian Delkinov (LN/EAB) wrote:
> > > Reza,
> > > 
> > > As far as I know the standard telephony - it functions a bit 
> > > differently. For instance if a user activates a service as "Call 
> > > Diversion" (similar to redirect in SIP), it's the network that 
> > > handles
> > 
> > > that hidden for the calling party, i.e. the caller does not need to 
> > > dial another number. And when such case occurs, in terms of PSTN for
> 
> > > the calling party it's 1 call (1 seizure produced) only. Or in NER 
> > > formula you will have:
> > > 
> > > (1 answer, or RNA, or BUSY etc)/ 1 call = 100% NER
> > > 
> > > If we try to apply same to SIP. When redirect is received, the UA 
> > > has to send another INVITE, right? (Tell me if I'm wrong). And if we
> 
> > > count
> > 
> > > the 300 code as network failure, and assume the second INVITE is 
> > > successful, then we have:
> > > 
> > > 1 OK /2 #INVITE = 50% SEER, which IMO isn't correct. Do you agree, 
> > > or please explain.
> > > 
> > > Best regards!
> > > Mario.
> > > 
> > > -----Original Message-----
> > > From: Fardid, Reza [mailto:RFardid@Covad.COM]
> > > Sent: Monday, 09 April, 2007 20:05
> > > To: Marian Delkinov (LN/EAB); Daryl Malas
> > > Cc: sipping@ietf.org
> > > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > > 
> > > Mario,
> > > 
> > > IMO, if the objective is to eliminate called party behavior from ASR
> 
> > > (and SER), minimally the following response codes need to be
> excluded:
> > > User Busy		~480
> > > RNA			~486
> > > Busy Everywhere	~600
> > > 
> > > I fail to see how exclusion of 3xx, other 4xx, and 6xx codes (with 
> > > the
> > 
> > > possible exception of 603) will serve this objective.
> > > 
> > > It appears that the metric you are proposing has a much broader
> scope.
> > > Perhaps, the confusion is caused by the inclusion of "user agent"
> > > behavior in the definition of SEER, which should only exclude the 
> > > effects of "called party" behavior.
> > > 
> > > Regards,
> > > -Reza
> > > 
> > > 		
> > > 
> > > 
> > > 
> > > 
> > > 
> > > -----Original Message-----
> > > From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> > > Sent: Tuesday, April 03, 2007 3:28 AM
> > > To: Fardid, Reza; Daryl Malas
> > > Cc: sipping@ietf.org
> > > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > > 
> > > Reza,
> > > 
> > > Exactly because of the analogy with NER and the meaning it has as 
> > > telephony metric I wanted to make clear the right counters, 
> > > including for release codes, are used to achieve the same meaning in
> 
> > > SIP. I didn't understand for when you foresee the implementation?
> > > 
> > > Best regards!
> > > Mario.
> > > 
> > > -----Original Message-----
> > > From: Fardid, Reza [mailto:RFardid@Covad.COM]
> > > Sent: Friday, 30 March, 2007 22:02
> > > To: Marian Delkinov (LN/EAB); Daryl Malas
> > > Cc: sipping@ietf.org
> > > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > > 
> > > Mario,
> > > 
> > > What I had in mind when I proposed inclusion of SEER in this draft 
> > > was
> > 
> > > a SIP performance metric analogous to NER in the PSTN, within the 
> > > framework defined by Daryl:
> > > 
> > > Telephony Metric/Standard (ITU-T, BellCore, etc.) ==> SIP ETE Metric
> > > 
> > > Clearly some SIP metrics defined in this draft do not have a 
> > > telephony
> > 
> > > counterpart.  For the rest, IMO, it is good to stay within the above
> 
> > > framework and leave exclusion/inclusion of specific release codes 
> > > from
> > 
> > > defined metrics to implementation.
> > > 
> > > Regards,
> > > Reza Fardid
> > > Covad Communications
> > > 
> > > 
> > > -----Original Message-----
> > > From: Marian Delkinov (LN/EAB) [mailto:marian.delkinov@ericsson.com]
> > > Sent: Thursday, March 29, 2007 1:07 AM
> > > To: Daryl Malas
> > > Cc: sipping@ietf.org
> > > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > > 
> > > Hi Daryl,
> > > 
> > > I haven't got your opinion about my comments on the SEER definition.
> > > Have you considered them? 
> > > Would also be interested to know when a finalized document on the 
> > > performance metrics can be released.
> > > 
> > > Thanks!
> > > 
> > > Best regards!
> > > Mario.
> > > 
> > > -----Original Message-----
> > > From: Marian Delkinov (LN/EAB)
> > > Sent: Monday, 05 March, 2007 17:06
> > > To: 'Daryl Malas'
> > > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > > 
> > > Hi Daryl,
> > > 
> > > In principle, I agree with you in case we considered this from a 
> > > user perspective - then 3xx is not final. However my idea behind 
> > > including the 3xx codes was based on the involvement of "#Invite" in
> 
> > > the
> > formula.
> > > If a 3xx code would result in sending a new Invite, then it sounds 
> > > logical to me to add the 3xx codes in the numerator. (NB: RFC3261 
> > > defines 3xx responses as "final" for the SIP transaction, ref. to 
> > > page
> > 
> > > 21, Final Response).
> > > 
> > > Best regards!
> > > Mario.
> > > 
> > >  
> > > 
> > > -----Original Message-----
> > > From: Daryl Malas [mailto:daryl@level3.net]
> > > Sent: Friday, 23 February, 2007 17:00
> > > To: Marian Delkinov (LN/EAB)
> > > Cc: sipping@ietf.org
> > > Subject: RE: [Sipping] Session Establishment Efficiency Rate
> > > 
> > > I don't think 3xx codes should be included, since they would not be 
> > > considered a "Final" release cause code.  --Daryl
> > > 
> > > On Fri, 2007-02-23 at 12:22 +0100, Marian Delkinov (LN/EAB) wrote:
> > > > Hi,
> > > > 
> > > > If the Network Efficiency Rate is designed to express the ability 
> > > > of
> > 
> > > > the network to deliver calls (in SIP terms one should perhaps say 
> > > > "establish sessions"), I think that it might be reasonable to 
> > > > include few more cases (cause codes) in the numerator: e.g. all 
> > > > redirection 3xx codes, all 4xx except 408 codes and all 6xx codes.
> > > > (If you agree that those are the ones that exclude network 
> > > > failures,
> > 
> > > > congestion and any other network malfunction).
> > > > 
> > > > Actually it sounds fair to me if it's the opposite of the 
> > > > Ineffective Session Attempts (ISA):
> > > > SEER% =
> > > > 	   Total # of Invite Requests - # of ISA
> > > > ---------------------------------------------------- x 100
> > > > 	   Total # of Invite Requests
> > > > 
> > > > What do you think?
> > > > 
> > > > Best regards!
> > > > Mario.
> > > > 
> > > > -----Original Message-----
> > > > From: Daryl Malas [mailto:daryl@level3.net]
> > > > Sent: Friday, 23 February, 2007 01:14
> > > > To: sipping@ietf.org
> > > > Subject: [Sipping] Session Establishment Efficiency Rate
> > > > 
> > > > A couple more people have expressed to me that this adaptation of 
> > > > the ITU-T E.411 Network Efficiency Rate metric is very valuable.
> > > > The snapshot of the metric from the draft is:
> > > > 
> > > > "This metric is similar to Session Establishment Rate, but it is 
> > > > intended to exclude the effects of customer behavior and user 
> > > > agent behavior.  Essentially, the attempts resulting with a final 
> > > > cause code
> > > 
> > > > of 480, 486, and 600 would be added to the SER numerator."
> > > > 
> > > > Does anyone else want to see this metric in the draft?  I 
> > > > personally
> > 
> > > > think it is an interesting metric.
> > > > 
> > > > Thanks...
> > > > 
> > > > --Daryl
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Sipping mailing list  
> > > > https://www1.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
> > > 
> > > 
> > > _______________________________________________
> > > Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 16:29:56 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbjR7-0000Up-7c; Wed, 11 Apr 2007 16:29:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbjR5-0000Tn-NB
	for sipping@ietf.org; Wed, 11 Apr 2007 16:28:59 -0400
Received: from web31501.mail.mud.yahoo.com ([68.142.198.130])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HbjR4-0004eL-DN
	for sipping@ietf.org; Wed, 11 Apr 2007 16:28:59 -0400
Received: (qmail 25318 invoked by uid 60001); 11 Apr 2007 20:28:54 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=XEsYvoc1Vvfk61G02d4O2YyOO2oiCJEGUsvU63qtdRQxyuYY3dWiYUsbaHxitR1ofnoc8xlmBYtb3IvSqSF6IEiBu4aDmmVg1FKmXKDWhS3Rbz0AhQ5v04BOjkIYtcO3xMciAGQBo9PTkwgn7U7wZgtI5dfrkDV8X9QbuMiDi/s=;
X-YMail-OSG: Jzo.1TUVM1mZQ1NJdCtNGxnSiH47zOoKdJx4vGpzV6PDxEdp7aOtqrWsYLzXsu9e8ssh5JpV74hKI_rBSm2DSPt0ynAIPAsDrK4ZAt0TYoJ9bXSTw94-
Received: from [198.152.12.67] by web31501.mail.mud.yahoo.com via HTTP;
	Wed, 11 Apr 2007 21:28:53 BST
Date: Wed, 11 Apr 2007 21:28:53 +0100 (BST)
From: Kapil Nayar <kapilnayar@yahoo.com>
To: sipping@ietf.org
In-Reply-To: <1176321964.17141.142.camel@montag.eng.level3.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <16151.24886.qm@web31501.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [Sipping] Question on draft-worley-sipping-pickup-03.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi

In section 9 the draft refers to using 302-Moved
Temporarily with contact header containing Replaces
parameter (technique from Dan Petrie). I am looking
for further details on this technique - in the sense
that including multiple contact headers with Replaces
parameters, exactly how legal it is use this technique
etc.

In essence can somebody point me to the draft/ RFC
which explains this technique in more detail?

thanks,
Kapil


      ___________________________________________________________ 
Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for
your free account today http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.html 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 16:50:49 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hbjlw-0003zU-K4; Wed, 11 Apr 2007 16:50:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hbjlv-0003wd-1v
	for sipping@ietf.org; Wed, 11 Apr 2007 16:50:31 -0400
Received: from alnrmhc16.comcast.net ([206.18.177.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hbjlt-0001Ms-R9
	for sipping@ietf.org; Wed, 11 Apr 2007 16:50:31 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (alnrmhc16) with ESMTP
	id <20070411205029b1600hldrse>; Wed, 11 Apr 2007 20:50:29 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l3BKoSLv003683
	for <sipping@ietf.org>; Wed, 11 Apr 2007 16:50:28 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l3BKoS1m003679;
	Wed, 11 Apr 2007 16:50:28 -0400
Date: Wed, 11 Apr 2007 16:50:28 -0400
Message-Id: <200704112050.l3BKoS1m003679@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <16151.24886.qm@web31501.mail.mud.yahoo.com>
	(kapilnayar@yahoo.com)
Subject: Re: [Sipping] Question on draft-worley-sipping-pickup-03.txt
References: <16151.24886.qm@web31501.mail.mud.yahoo.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: Kapil Nayar <kapilnayar@yahoo.com>

   In section 9 the draft refers to using 302-Moved Temporarily with
   contact header containing Replaces parameter (technique from Dan
   Petrie). I am looking for further details on this technique - in
   the sense that including multiple contact headers with Replaces
   parameters, exactly how legal it is use this technique etc.

If you have multiple contact headers with Replaces, it's processed
exactly as you'd expect -- the call forks, and the first successful
contact establishes the dialog.

   In essence can somebody point me to the draft/ RFC which explains
   this technique in more detail?

You know of RFC 3261, of course.  INVITE with Replaces is described in
RFC 3891.  I should probably reference those.

Dale

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 17:22:47 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbkGD-0001mm-HP; Wed, 11 Apr 2007 17:21:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbkGB-0001mg-DI
	for sipping@ietf.org; Wed, 11 Apr 2007 17:21:47 -0400
Received: from alnrmhc15.comcast.net ([204.127.225.95])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbkGA-0006pU-6R
	for sipping@ietf.org; Wed, 11 Apr 2007 17:21:47 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (alnrmhc15) with ESMTP
	id <20070411212145b1500sp133e>; Wed, 11 Apr 2007 21:21:45 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l3BLLiLv005985
	for <sipping@ietf.org>; Wed, 11 Apr 2007 17:21:44 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l3BLLiGp005976;
	Wed, 11 Apr 2007 17:21:44 -0400
Date: Wed, 11 Apr 2007 17:21:44 -0400
Message-Id: <200704112121.l3BLLiGp005976@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <CCA850DCD3FBE2479D5076C5C18732220168AA39@S4DE9JSAAHW.ost.t-com.de>
	(Martin.Huelsemann@t-com.net)
Subject: Re: AW: AW: [Sipping] Call Completion: In Defense of Explicit
	Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA39@S4DE9JSAAHW.ost.t-com.de>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>

   True is that the user's subscription also creates the resource,
   which is his own call-completion state. The question is, is that
   problematical, and why? 

   The next question of course would be, is it problematical to
   transport bodies with queue manipulation information within the
   SUBSCRIBEs. 

Both are problematical in the same way -- The original defintion of
the subscription mechanism makes subscriptions to be passive observers
of the resource; they inherently could not affect the resource
itself.  And this passivity could now be enshrined as an architectural
principle of implementations.  The change is that the existence of
subscriptions (and the event-type parameters and possibly request
bodies) become operations on the resource.

Indeed, we need to split that previous sentence -- the existence of
subscriptions becomes part of the state that is observed, and (even
messier) features of re-SUBSCRIBE messages become operations on the
state.

Dale

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 18:22:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HblBp-0006wP-Qm; Wed, 11 Apr 2007 18:21:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HblBn-0006wH-UH
	for sipping@ietf.org; Wed, 11 Apr 2007 18:21:19 -0400
Received: from exprod6og56.obsmtp.com ([64.18.1.208])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HblBm-0007SL-20
	for sipping@ietf.org; Wed, 11 Apr 2007 18:21:19 -0400
Received: from source ([192.150.20.142]) by exprod6ob56.postini.com
	([64.18.5.12]) with SMTP; Wed, 11 Apr 2007 15:21:12 PDT
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l3BML8Sd002903; Wed, 11 Apr 2007 15:21:08 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	l3BMKt0s019355; Wed, 11 Apr 2007 15:21:08 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Apr 2007 15:21:06 -0700
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
Subject: RE: [Sipping] Simple SIP usage scenario
Date: Wed, 11 Apr 2007 15:21:04 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D226B2A85@namail5.corp.adobe.com>
In-Reply-To: <00e101c77bbe$d9edc6f0$0601a8c0@BEMBUSTER>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Simple SIP usage scenario
Thread-Index: Acd7v30l4Cf/kYKGSi6p5fxMAMu0SQAxMMnQ
References: <072C5B76F7CEAB488172C6F64B30B5E302C88E16@xmb-rtp-20b.amer.cisco.com><C2290C52.4329%eburger@bea.com><D3BA17190818B44CA969FB72EB43418D017A82E5@KKWNLEX181.kpnnl.local><E2839307E942954A846FD1125BE33A1A03A6C0C4@repbex01.amer.bea.com>
	<00e101c77bbe$d9edc6f0$0601a8c0@BEMBUSTER>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Jeroen van Bemmel" <jbemmel@zonnet.nl>, "Eric Burger" <eburger@bea.com>, 
	<colin.pons@kpn.com>
X-OriginalArrivalTime: 11 Apr 2007 22:21:06.0104 (UTC)
	FILETIME=[B2881380:01C77C87]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 85e99493ec37f9acef29c7843dbf2e68
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

> So: are we really talking about a "voice mail" service for P2P SIP
here?

>From the user perspective, what matters is a voice message can be left
for later retrieval by the called party. From this perspective VM is VM
no matter what the technology is or how this capability is enhanced by
"surround stuff" to justify more charges.

Eric makes a valid and critical point that presence may induce the
caller to just not make the call in the first place or send an e-mail or
a deferred IM (as it works in Skype). (The advantages are many: Save
your breath and don't talk to machine, save the called party to retrieve
the VM since texting, IM or email are more accurate and understandable).


It also can be argued that for network enabled people VM is just a bad
habit :-)

But P2P can certainly provide a VM that can be sold as such and this is
all that matters to the marketing folks.

My two cents,

Henry

-----Original Message-----
From: Jeroen van Bemmel [mailto:jbemmel@zonnet.nl]=20
Sent: Tuesday, April 10, 2007 3:23 PM
To: Eric Burger; colin.pons@kpn.com
Cc: p2prg@ietf.org; sipping@ietf.org
Subject: Re: [Sipping] Simple SIP usage scenario

Eric,

What you describe below is already (and always has been) possible. Note
that=20
in todays world also e-mail has inter-provider agreements, and=20
architectures, and wacky protocols, and well-known ports (the UDP/TCP=20
equivalent of one aspect of a service identifier).

Voice mail, as it is currently commonly used and known, is a service
that=20
may kick in when A calls B and B has a voice mail service. One could
imagine=20
a "straight to voice mail" service controlled by the caller, but usually
the=20
callee determines when voice mail is offered. When offered, the caller
can=20
then choose to leave a message "after the beep", or not. Whatever the
caller=20
does after/besides this (e.g. send e-mail) is irrelevant for the VM
service.

My point here is: voice mail works the way it does. It provides the
caller=20
an extra option to deliver a message, under certain conditions, and
provides=20
a certain user experience with associated expectations. In no way does
it=20
(or the architecture or what have you) limit the choices of either the=20
caller or the callee with regards to using other means of communication.

One can change (hoping to "improve", subjective) the user experience=20
provided by voice mail, but you soon end up with something which is=20
essentially a _different_ service. To avoid confusion, it should then no

longer be called "voice mail"

So: are we really talking about a "voice mail" service for P2P SIP here?

Regards,
Jeroen

Eric Burger wrote:
> The whole point is the caller gets to chose.  It doesn't matter what
> the
> target user has or subscribes to.  If the target happens to have a
> voice
> message service, great, I can leave a message if I chose.  If the
> target
> doesn't, or I feel like sending an e-mail, I can just do it.  No need
> for whacky protocols, architectures, inter-carrier agreements, service
> identifiers, etc.
>
> -----Original Message-----
> From: colin.pons@kpn.com [mailto:colin.pons@kpn.com]
> Sent: Monday, March 26, 2007 7:34 AM
> To: Eric Burger; mhammer@cisco.com; pkyzivat@cisco.com;
> hsinnrei@adobe.com
> Cc: p2prg@ietf.org; sipping@ietf.org
> Subject: RE: [Sipping] Simple SIP usage scenario
>
>
> How would this work? If the callee (or his agent in IM style) are
> off-line he is not able to inform the caller.
>
> The VM concept Works is based on asynchronous transaction, where both
> the callee and the caller are in control; the callee is in control by
> subscribing to a VM service or implementing a voicemail Application
> and
> the caller is in control by choosing to leave a voicemail.
>
> I agree that the VM experience can be improved where both the caller
> and
> the calle gets to choose how to deliver the message. But my point is
> how
> does the caller know from which options to choose if the callee did
> not (or could not because of being off line) inform the caller of the
> options? Otherwise I have a system the leaves control solely to the
> caller.
>
> Colin Pons
> Senior Architect
> WSO Innovation Management
>
> -----Oorspronkelijk bericht-----
> Van: Eric Burger [mailto:eburger@bea.com]
> Verzonden: vrijdag 23 maart 2007 9:47
> Aan: Michael Hammer (mhammer); Paul Kyzivat; Henry Sinnreich
> CC: p2prg@ietf.org; sipping@ietf.org
> Onderwerp: Re: [Sipping] Simple SIP usage scenario
>
> Missing the point:
>
> The called party gets to CHOOSE whether the caller is allowed to send
> them an e-mail.  The called party does this by publishing their e-mail
> address.
> That is like a classic subscription to voice mail.  However, it is
> BETTER than classic voice mail, in that if the called party does not
> CHOOSE to offer voice mail, there is still the possibility for an
> asynchronous IM-style transaction.
>
> Best of all, the caller (you) gets to CHOOSE how to deliver the
> message.
> Note I say CHOOSE, and not "the network does weird stuff that I don't
> understand and has a ton of hidden feature interactions that pop out
> when I and the called party least expect it."  If I chose to go the
> e-mail route, then I know to expect the message to be delivered in a
> timely manner, especially if "message-context: voice-message" is set.
> Moreover, if I CHOOSE to go the asynchronous route, then my
> expectation
> is appropriately set.
>
> Also, it is important to note that the IM-style method does not
> necessarily mean when *I* am on-line.  It can mean when my *agent* is
> on
> line.
>
>
> On 3/22/07 6:41 PM, "Michael Hammer (mhammer)" <mhammer@cisco.com>
> wrote:
>
>> Note that doing that (Skype P2P) delays the deliver of the message to
>> when the caller is back online versus when the sender intended the
>> message to be sent and stored, i.e. before the called party is
>> online.
>>
>> What if I need to leave an important message before hopping a plane,
> and
>> the receiver getting it when the plane lands hours later will be
>> after
>
>> the meeting for which the message was intended?
>>
>> Not good.  Not the same service as VM.  The whole point is dijoint
>> asynchronous delivery.
>>
>> Mike
>>
>>
>>> -----Original Message-----
>>> From: Eric Burger [mailto:eburger@bea.com]
>>> Sent: Wednesday, March 21, 2007 4:37 AM
>>> To: Paul Kyzivat (pkyzivat); Henry Sinnreich
>>> Cc: p2prg@ietf.org; sipping@ietf.org
>>> Subject: Re: [Sipping] Simple SIP usage scenario
>>>
>>> I would offer the concept of putting the responsibility for
>>> "sending"
>
>>> the message on the caller IS EXCELLENT.
>>>
>>> It totally removes a ton of hard stuff that VM systems have to do,
>>> like absolutely, positively, delivering the message once the caller
>>> thinks the message was recorded.  Why is this so?  The CALLER knows
>>> if his device is up, down, or sideways.
>>>  If he knows the device is not on line or broke, then he has NO
>>> expectations of the message being delivered.
>>>
>>> Think of how Skype and Yahoo!IM does delayed delivery: they wait
>>> until both parties are back on-line before sending the message.
>>> Thus
>
>>> this paradigm is NOT going to be foreign to a p2p SIP user.
>>>
>>>
>>> On 3/20/07 11:57 AM, "Paul Kyzivat" <pkyzivat@cisco.com> wrote:
>>>
>>>>
>>>>
>>>> Henry Sinnreich wrote:
>>>>> Paul,
>>>>>
>>>>> This is a good question regarding VM in P2P SIP. It is discussed
>>>>> along with other telephony services in more detail in:
>>>>>
>>>>>
>>>
http://www1.cs.columbia.edu/~library/TR-repository/reports/reports-20
>>>>> 04/
>>>>> cucs-044-04.pdf
>>>>
>>>> Loots to me that this could use a lot more discussion.
>>>>
>>>> It seems that there is one fundamental decision to be made:
>>> When the
>>>> callee is not available, is it the responsibility of the
>>> caller or the
>>>> callee to capture a message? Then there are secondary
>>> questions of how
>>>> the message is stored, and how it is conveyed to the recipient.
>>>>
>>>> Clearly the current world view is that it is the
>>> responsibility of the
>>>> callee to handle the capture of the message. If the goal is
>>> to change
>>>> that assumption, then there will need to be some compatibility
>>>> mechanism put in place for callers that don't do it. To the extent
>>>> that it is the callee that would like to have the message, it may
>>>> always need to be a responsibility of the callee.
>>>>
>>>> If it is decided that it is the callee that must provide this, then
>>>> either it is done by the P2P framework or it is not. If not we can
>>>> perhaps ignore it as just another UA, though it might actually be
>>>> provided by a multiuser VM service provider.
>>>>
>>>> If this is to be provided by the p2p framework, then it has
>>> become a
>>>> "network service".
>>>>
>>>> Personally, I rather like the idea of making this a
>>> requirement of the
>>>> caller, and having them email the message. (If the callee wants to
>>>> receive a message it could return a 3xx with email url.)
>>> But I don't
>>>> know how we get to where we can count on callers doing it.
>>>>
>>>> Paul
>>>>
>>>>> Henry
>>>>>
>>>>> -----Original Message-----
>>>>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
>>>>> Sent: Tuesday, March 20, 2007 10:35 AM
>>>>> To: Henry Sinnreich
>>>>> Cc: Dale.Worley@comcast.net; sipping@ietf.org; p2prg@ietf.org
>>>>> Subject: Re: [Sipping] Simple SIP usage scenario
>>>>>
>>>>> Henry,
>>>>>
>>>>> Your comments below seem to assume that I must have a UA
>>> attached any
>>>>> time I might what to send a call to VM. But if all I have
>>> are mobile
>>>>> devices then that won't be the case. I need a way to have
>>> *something*
>>>>> that acts for me when I have none of my own devices attached.
>>>>>
>>>>> I could satisfy this by contracting for service from something to
>>>>> register on my behalf at all times. If I want that, where
>>> does that
>>>>> service fit into the p2p framework? Is it internal to it,
>>> or external?
>>>>>
>>>>> Paul
>>>>>
>>>>> Henry Sinnreich wrote:
>>>>>>> It seems like it would be hard to associate a voicemail
>>> server with
>>>>>>> a mobile handset without a proxy/registrar somewhere.
>>>>>> This is a good _editorial_ catch.
>>>>>>
>>>>>> 1. In the case of a VM server no extensions to RFC 3261 are
>>>>>> required for simple VM. The called UA can redirect the call to VM
>>> after a timeout.
>>>>>> This must be made clear in the text.
>>>>>>
>>>>>> 2. In the case of P2P SIP, the DHT can serve for voice
>>> mail storage.
>>>>>>
>>>>>> Maybe I am missing something?
>>>>>>
>>>>>> Thanks for noting it,
>>>>>>
>>>>>> Henry
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]
>>>>>> Sent: Tuesday, March 20, 2007 1:59 AM
>>>>>> To: p2prg@ietf.org; sipping@ietf.org
>>>>>> Subject: Re: [Sipping] Simple SIP usage scenario
>>>>>>
>>>>>>    From: Paul Kyzivat <pkyzivat@cisco.com>
>>>>>>
>>>>>>    It could be functionally equivalent - registering with my AOR.
>>>>>>
>>>>>> This strikes me as a central issue.  Especially if the real UA is
>>>>>> mobile, you need a high-accessibility "fixed" server to
>>> anchor the
>>>>>> AOR.  SIP has the machinery to do that well, yes, but
>>> that machinery
>>>>>> *is* a proxy/registrar.  At that point, I don't see how
>>> the "Simple
>>>>>> SIP scenario" differs from a PBX, though possibly a PBX with one
>>>>>> extension.
>>>>>>
>>>>>> It seems like it would be hard to associate a voicemail
>>> server with
>>>>>> a mobile handset without a proxy/registrar somewhere.
>>>>>>
>>>>>> Dale
>>>>>>
>>>>>> _______________________________________________
>>>>>> Sipping mailing list
>>> https://www1.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
>>>>>>
>>>>>> _______________________________________________
>>>>>> Sipping mailing list
>>> https://www1.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
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Sipping mailing list
>>>> https://www1.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
>>>
>>> ______________________________________________________________
>>> _________
>>> Notice:  This email message, together with any attachments, may
>>> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and
>>> affiliated entities,  that may be confidential,  proprietary,
>>> copyrighted  and/or legally privileged, and is intended solely for
>>> the use of the individual or entity named in this message. If you
>>> are
>
>>> not the intended recipient, and have received this message in error,
>>> please immediately return this by email and then delete it.
>>>
>>> _______________________________________________
>>> Sipping mailing list  https://www1.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
>>>
>>
>
>
>
> Notice:  This email message, together with any attachments, may
> contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and
> affiliated
> entities,  that may be confidential,  proprietary,  copyrighted
> and/or
> legally privileged, and is intended solely for the use of the
> individual
> or entity named in this message. If you are not the intended
> recipient,
> and have received this message in error, please immediately return
> this
> by email and then delete it.
>
> _______________________________________________
> Sipping mailing list  https://www1.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
>
> Notice:  This email message, together with any attachments, may
> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and
> affiliated entities,  that may be confidential,  proprietary,
> copyrighted  and/or legally privileged, and is intended solely for
> the use of the individual or entity named in this message. If you are
> not the intended recipient, and have received this message in error,
> please immediately return this by email and then delete it.
>
> _______________________________________________
> Sipping mailing list  https://www1.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=20


_______________________________________________
Sipping mailing list  https://www1.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

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 11 20:04:29 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbmnO-00056n-Cn; Wed, 11 Apr 2007 20:04:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbmnM-00056e-1C
	for sipping@ietf.org; Wed, 11 Apr 2007 20:04:12 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbmnK-0001KL-PC
	for sipping@ietf.org; Wed, 11 Apr 2007 20:04:12 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 11 Apr 2007 17:04:10 -0700
X-IronPort-AV: i="4.14,397,1170662400"; 
	d="scan'208"; a="410485130:sNHT126534036"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l3C04Aa1026877; 
	Wed, 11 Apr 2007 17:04:10 -0700
Received: from [10.32.245.157] (stealth-10-32-245-157.cisco.com
	[10.32.245.157])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l3C040A8011883;
	Thu, 12 Apr 2007 00:04:00 GMT
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D226B2A85@namail5.corp.adobe.com>
References: <072C5B76F7CEAB488172C6F64B30B5E302C88E16@xmb-rtp-20b.amer.cisco.com><C2290C52.4329%eburger@bea.com><D3BA17190818B44CA969FB72EB43418D017A82E5@KKWNLEX181.kpnnl.local><E2839307E942954A846FD1125BE33A1A03A6C0C4@repbex01.amer.bea.com>
	<00e101c77bbe$d9edc6f0$0601a8c0@BEMBUSTER>
	<24CCCC428EFEA2469BF046DB3C7A8D226B2A85@namail5.corp.adobe.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <592F38E2-15BD-48B1-B5B5-C6228C8380A4@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] Simple SIP usage scenario
Date: Wed, 11 Apr 2007 20:03:53 -0400
To: Henry Sinnreich <hsinnrei@adobe.com>
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=175; t=1176336250;
	x=1177200250; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Simple=20SIP=20usage=20scenario
	|Sender:=20; bh=mszZEiLRGnoCxH4SlALDyWkbXxSjrK/FJXAc0qnvg+I=;
	b=h7y/EIjGzTJxTYO5bbT0SiDHCJ6tAiFAQOMGdHxVXpzno79NiRxd1Ui+rAgpsT7YRWUCFRmh
	QGHqEMsB+a8AK/yi+3KV2j8KbpAfpvZtoeI9YizEj+gdbbwSpWDax5ab;
Authentication-Results: sj-dkim-7; header.From=oran@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

> It also can be argued that for network enabled people VM is just a bad
> habit :-)
>
Yeah the only VM feature I use is a greeting that tells people to  
send me email.

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 03:30:34 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hbtl6-0006N3-Dc; Thu, 12 Apr 2007 03:30:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hbtl4-0006Mw-N6
	for sipping@ietf.org; Thu, 12 Apr 2007 03:30:18 -0400
Received: from an-out-0708.google.com ([209.85.132.243])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hbtl2-0000tO-ES
	for sipping@ietf.org; Thu, 12 Apr 2007 03:30:18 -0400
Received: by an-out-0708.google.com with SMTP id d30so521484and
	for <sipping@ietf.org>; Thu, 12 Apr 2007 00:30:15 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=IP95WILCMz+SXArcfQg/aZm6aEBNjRRf9r/8/NHCAbxYK+iaaAqtKsnd2OG6d0YUyPPjCrP7L88FZiyQgOyVt4OdF/UTchAvVdqMb64BkFB+fo9d7ZmaPbutfZtGnzWga/dtPDfUjLm/24bSqaqE1SpgGRhmSltESarvGfUz+IY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=BRnmkMdXPLc5mKngbShJzSIatEDqZp0uFFVHMheD3LzYYWZoZ3V1hs7iRkxCJGLtRbsXGOmHP+usMMwnBBCeoOjjwYL+lKQ3O89Mik4AvjLzJhtUjptfsOxv5ka0VW9gSpulG3+CGBgCjuNCv9qsE5vK5xJyQTIRBw4R9CAbSaE=
Received: by 10.100.164.14 with SMTP id m14mr1100120ane.1176363015758;
	Thu, 12 Apr 2007 00:30:15 -0700 (PDT)
Received: by 10.100.189.14 with HTTP; Thu, 12 Apr 2007 00:30:15 -0700 (PDT)
Message-ID: <458913680704120030h1921cd42u9c3caf5b58d6ab52@mail.gmail.com>
Date: Thu, 12 Apr 2007 09:30:15 +0200
From: "Xavier Marjou" <xavier.marjou@orange-ftgroup.com>
To: "Adam Roach" <adam@nostrum.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
In-Reply-To: <461D28EE.4070904@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
	<461CED8F.60501@cisco.com>
	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>
	<461D28EE.4070904@nostrum.com>
X-Google-Sender-Auth: 35126831f8e3adc2
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: Paul Kyzivat <pkyzivat@cisco.com>, sipping@ietf.org,
	Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

> > I concur that insertion into the queue and subscription to the queue
> > must be different things. That seems obvious, so I must have missed
> > the idea that they were intertwingled (or dismissed it as just silly).
>
> Yes, they must be different things. Yes, this is obvious. Yes, it is
> silly to propose that they be combined into the same operation. Yes,
> this very silly thing is at the core of the draft-poetzl proposal.
>

I think the disagreement between people stems from Section 4.4.3 of
RFC3265 that indicates "SUBSCRIBE method bodies [...] will typically
modify, expand, filter, throttle, and/or set thresholds for the class
of events being requested."  Many people understood "modify" as a
"set" operation on the state of the event, whereas the meaning of
"modify" is a "get" operation that can filters - but not modify - the
state parameters being returned to the user. (I admit the analogy with
setters and getters is not perfectly accurate as there are no setters
and getters within our XML documents)


> > Operations on the queue data itself are clearly outside of the
> > "watcher" package. If the queue notification is handled on a node that
> > is different from the node with the data that drives the queue, then
> > we have XCAP to manipulate the queue document and make insertions, etc.
>
> _That's_ interesting. I hadn't thought of that. So, instead of using
> BFCP (as my current proposal suggests), we could use an event package to
> unobtrusively subscribe to a queue, and XCAP to place ourselves in,
> pause, resume, and remove ourselves from the queue.
>
> That seems quite reasonable. I'd be interested to see what other people
> have to say about it.
>

XCAP is for configuration data; typically this data is stored as
received within a file. In our case, if a user removes himself from a
queue, it would not make sense to store this information in a file. To
continue the analogy with Presence, we may also consider another
alternative: A user PUBLISHes its state ("in/out queue") via an
input-queue event package, the server side makes the aggregration of
all existing inputs to build the queue, and any user can perform a
SUBscription to an output-queue event package to be NOTified of its
position within the queue. (I think someone, perhaps Mike, proposed
this some time ago).

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 08:52:20 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbymW-0007Tu-0M; Thu, 12 Apr 2007 08:52:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbymQ-0007Qe-M1
	for sipping@ietf.org; Thu, 12 Apr 2007 08:52:02 -0400
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbymP-0003rj-6p
	for sipping@ietf.org; Thu, 12 Apr 2007 08:52:02 -0400
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de
	[10.125.177.122]) by tcmail21.telekom.de with ESMTP;
	Thu, 12 Apr 2007 14:51:59 +0200
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 14:51:59 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: AW: AW: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Thu, 12 Apr 2007 14:51:59 +0200
Message-Id: <CCA850DCD3FBE2479D5076C5C18732220168AA3E@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <461D28EE.4070904@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AW: [Sipping] Call Completion: In Defense of Explicit Operations
Thread-Index: Acd8Z168JCkqf3iyRtSjf1ik7yrnhAAmTH7g
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <adam@nostrum.com>,
    <dean.willis@softarmor.com>
X-OriginalArrivalTime: 12 Apr 2007 12:51:59.0528 (UTC)
	FILETIME=[5BFFD280:01C77D01]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: pkyzivat@cisco.com, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Would it then look like as follows?


--- Activation and retention

A calls B, B is busy, B has queueing function, A gets provisionally =
queued,
=20
Timer for A's queueing confirmation starts,=20

resource "A's call-completion state" is created (would be instance or =
function of the queue),=20

Allow-events:call-completion is inserted in 486 (this would be the =
cc-possible indication for A),=20

A subscribes to his call-completion state, A gets notification =
cc-state=3Didle,

A uses XCAP to add himself to the queue (queueing is confirmed at B =
queue, confirmation timer stops), A gets notification cc-state=3Dqueued

B becomes not busy, A gets notification cc-state=3Dstart-recall

recall fails for some reasons, retention option is fulfilled, A gets =
notification cc-state=3Dqueued



--- Deactivation

call-completion activated

A uses XCAP to remove himself from the queue, A gets notification =
cc-state=3Didle,

A terminates subscription=20




Are this roughly the procedures you are thinking of?=20



Martin




> -----Urspr=FCngliche Nachricht-----
> Von: Adam Roach [mailto:adam@nostrum.com]=20
> Gesendet: Mittwoch, 11. April 2007 20:29
> An: Dean Willis
> Cc: Paul Kyzivat; H=FClsemann, Martin; sipping@ietf.org
> Betreff: Re: AW: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
>=20
>=20
> Dean Willis wrote:
> > So the open question is how does one get into the queue=20
> without having=20
> > that insertion be a side-effect of the subscription itself?
> >
> > Two options:
> >
> > 1) Automatically enqueue all callers when there is a queue.
>=20
> Interesting approach -- I'm not sure how well it will work in=20
> practice,=20
> because you'll end up having to wait for the queue of missed=20
> calls from=20
> disinterested parties to drain before your position percolates to the=20
> top of the queue. It's probably solvable, but we'd need to=20
> come up with=20
> something.
>=20
> > 2) Redirect (or indirect via a new header field) callers to a queue=20
> > factory when there is a queue. If they follow the indirection, they=20
> > get enqueued.
>=20
> Ooh. Run this one by Dave Oran. Perhaps we can get him to give his=20
> "To-Explode-My-Phone:" speech again.
>=20
> > I concur that insertion into the queue and subscription to=20
> the queue=20
> > must be different things. That seems obvious, so I must have missed=20
> > the idea that they were intertwingled (or dismissed it as=20
> just silly).
>=20
> Yes, they must be different things. Yes, this is obvious. Yes, it is=20
> silly to propose that they be combined into the same operation. Yes,=20
> this very silly thing is at the core of the draft-poetzl proposal.
>=20
> > Operations on the queue data itself are clearly outside of the=20
> > "watcher" package. If the queue notification is handled on=20
> a node that=20
> > is different from the node with the data that drives the=20
> queue, then=20
> > we have XCAP to manipulate the queue document and make=20
> insertions, etc.
>=20
> _That's_ interesting. I hadn't thought of that. So, instead of using=20
> BFCP (as my current proposal suggests), we could use an event=20
> package to=20
> unobtrusively subscribe to a queue, and XCAP to place ourselves in,=20
> pause, resume, and remove ourselves from the queue.
>=20
> That seems quite reasonable. I'd be interested to see what=20
> other people=20
> have to say about it.
>=20
> /a
>=20

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 09:30:51 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbzNx-000657-Sc; Thu, 12 Apr 2007 09:30:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbzNw-00064s-Pz
	for sipping@ietf.org; Thu, 12 Apr 2007 09:30:48 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbzNv-0000Xw-GF
	for sipping@ietf.org; Thu, 12 Apr 2007 09:30:48 -0400
Received: from [206.176.144.210] (206-176-144-210.waymark.net
	[206.176.144.210]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3CCbH4P004543
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 07:37:18 -0500
Message-ID: <461E3486.3050906@softarmor.com>
Date: Thu, 12 Apr 2007 08:30:46 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061206)
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
	<461CED8F.60501@cisco.com>
	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>
	<461D28EE.4070904@nostrum.com>
In-Reply-To: <461D28EE.4070904@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: Paul Kyzivat <pkyzivat@cisco.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Adam Roach wrote:

> 
> _That's_ interesting. I hadn't thought of that. So, instead of using 
> BFCP (as my current proposal suggests), we could use an event package to 
> unobtrusively subscribe to a queue, and XCAP to place ourselves in, 
> pause, resume, and remove ourselves from the queue.
> 
> That seems quite reasonable. I'd be interested to see what other people 
> have to say about it.

I didn't mean to suggest that the caller enqueue themselves with XCAP, 
but that if the queue manager and the event server were on different 
nodes that the queue manager could manipulate the queue state document 
using XCAP.

I still think that being enqueued as a result of an INVITE is a 
reasonable thing.

--
Dean


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 09:35:01 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbzS0-0007xD-DU; Thu, 12 Apr 2007 09:35:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbzRz-0007va-1Y
	for sipping@ietf.org; Thu, 12 Apr 2007 09:34:59 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbzRx-0001hn-Ns
	for sipping@ietf.org; Thu, 12 Apr 2007 09:34:59 -0400
Received: from [206.176.144.210] (206-176-144-210.waymark.net
	[206.176.144.210]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3CCfZpk004567
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 07:41:36 -0500
Message-ID: <461E3588.1050505@softarmor.com>
Date: Thu, 12 Apr 2007 08:35:04 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061206)
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>	<461B8FB7.3000903@nostrum.com>	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>	<461BCAD7.1020001@nostrum.com>	<34668222-C8B1-41FE-9519-530FDFE92BFA@softarmor.com>	<461BE0CC.8010403@nostrum.com>	<4B7406B6-B323-43B1-B7BB-2843CD105F65@softarmor.com>	<461D1FB8.2070500@nostrum.com>	<E4E23388-C9F3-422D-B16E-DAD0114F096B@softarmor.com>
	<461D3B83.7000309@nostrum.com>
In-Reply-To: <461D3B83.7000309@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Adam Roach wrote:

>> What's the remaining problem? Manipulating the queue itself? Why is 
>> that a problem?
> 
> Your question implies that you think this is a solved problem. Great! In 
> that case, it would be no problem for you to answer the following two 
> questions:
> 
>   1. How does the queued caller pause their position in the queue?
>   2. How does the queued caller un-pause their position in the queue?
> 

Ah, so you want the CALLER to manipulate the queue. Not on my original 
list of requirements, which were around the queue manager manipulating it.

But if you're maintaining an INVITE dialog, suspend sounds a lot like hold.


--
Dean

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 10:06:49 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hbzwh-0007yX-SJ; Thu, 12 Apr 2007 10:06:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hbzwg-0007yM-2c
	for sipping@ietf.org; Thu, 12 Apr 2007 10:06:42 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hbzwf-0004j0-PB
	for sipping@ietf.org; Thu, 12 Apr 2007 10:06:42 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 12 Apr 2007 10:06:41 -0400
X-IronPort-AV: i="4.14,403,1170651600"; 
	d="scan'208"; a="57442939:sNHT49272224"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3CE6f0L023330; 
	Thu, 12 Apr 2007 10:06:41 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l3CE6RlG003595; 
	Thu, 12 Apr 2007 14:06:27 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 10:06:27 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 10:06:27 -0400
Message-ID: <461E3CE2.7000009@cisco.com>
Date: Thu, 12 Apr 2007 10:06:26 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
	<461CED8F.60501@cisco.com>
	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>
	<461D28EE.4070904@nostrum.com> <461E3486.3050906@softarmor.com>
In-Reply-To: <461E3486.3050906@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Apr 2007 14:06:27.0261 (UTC)
	FILETIME=[C2F9C6D0:01C77D0B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2277; t=1176386801;
	x=1177250801; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defen
	se=20of=20Explicit=20Operations |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=Ua94lrb84+VipxBXYKkFfUCG65ArTq9KJQkdiFFtFGY=;
	b=RDtHP2JTHBAWGKseKYsZ4Olt7NTIZxs8q1KvI13HosKTPkQ0HtcCJBYiJkWWs2EYGvSKyK8e
	QysNG70K2PWnkGdmZFIH7nycRaDKb541ZrBa/NedCJ6hG3as4AI+f/kk;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: sipping@ietf.org, Adam Roach <adam@nostrum.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Dean Willis wrote:
> Adam Roach wrote:
> 
>>
>> _That's_ interesting. I hadn't thought of that. So, instead of using 
>> BFCP (as my current proposal suggests), we could use an event package 
>> to unobtrusively subscribe to a queue, and XCAP to place ourselves in, 
>> pause, resume, and remove ourselves from the queue.
>>
>> That seems quite reasonable. I'd be interested to see what other 
>> people have to say about it.
> 
> I didn't mean to suggest that the caller enqueue themselves with XCAP, 
> but that if the queue manager and the event server were on different 
> nodes that the queue manager could manipulate the queue state document 
> using XCAP.
> 
> I still think that being enqueued as a result of an INVITE is a 
> reasonable thing.

Dean,

The ultimate goal seems to be to give the potential caller at the top of 
the queue a window of opportunity to attempt a call. During that time, 
you don't want to allow the other pending callers, or new callers, to 
establish a call to the callee.

But if you enroll everybody that attempts a call, without knowing that 
they will use the queue to retry, then you have a problem. You don't 
want to give a window of opportunity to someone who isn't waiting.

I guess you could go ahead and enroll the caller of every failed call, 
but only give a window of opportunity to a candidate that has been 
notified that it is at the head of the queue.

That also suggests a way to handle suspend/resume: to suspend you simply 
cancel your subscription. And to resume you make a new subscription.

That seems somewhat interesting. But it presents a new problem - a 
subscriber needs to know if they even have an entry in the queue. If you 
only get notified when you get to the top, then you could wait forever 
if you aren't in the queue.

I guess that could be handled by having an initial notification report 
your queue entry even if you are not first - perhaps giving position in 
queue. Then a subsequent notifications could be filtered unless the 
entry is first in queue, if it is considered undesirable to notify of 
every change in position. That would take some peculiar language around 
the design of a filter, but seems like it should be possible.

	Paul

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 10:49:42 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc0cG-0001p4-77; Thu, 12 Apr 2007 10:49:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc0cE-0001oe-83
	for sipping@ietf.org; Thu, 12 Apr 2007 10:49:38 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Hc0cC-0003CX-U6
	for sipping@ietf.org; Thu, 12 Apr 2007 10:49:38 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3CEnX5Q005670
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 09:49:35 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461E4705.9020401@nostrum.com>
Date: Thu, 12 Apr 2007 09:49:41 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>	<461B8FB7.3000903@nostrum.com>	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>	<461BCAD7.1020001@nostrum.com>	<34668222-C8B1-41FE-9519-530FDFE92BFA@softarmor.com>	<461BE0CC.8010403@nostrum.com>	<4B7406B6-B323-43B1-B7BB-2843CD105F65@softarmor.com>	<461D1FB8.2070500@nostrum.com>	<E4E23388-C9F3-422D-B16E-DAD0114F096B@softarmor.com>
	<461D3B83.7000309@nostrum.com> <461E3588.1050505@softarmor.com>
In-Reply-To: <461E3588.1050505@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dean Willis wrote:
> Ah, so you want the CALLER to manipulate the queue. Not on my original 
> list of requirements, which were around the queue manager manipulating it.

No, *I* don't want it. TISPAN wants it. *I* think it's silly.

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 11:49:24 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc1Xz-0003Fw-3a; Thu, 12 Apr 2007 11:49:19 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc1Xx-0003Fr-QO
	for sipping@ietf.org; Thu, 12 Apr 2007 11:49:17 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Hc1Xv-00089m-Bv
	for sipping@ietf.org; Thu, 12 Apr 2007 11:49:17 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3CFnEjL008756
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 10:49:14 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461E5502.1090105@nostrum.com>
Date: Thu, 12 Apr 2007 10:49:22 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>	<461B8FB7.3000903@nostrum.com>	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>	<461BCAD7.1020001@nostrum.com>	<34668222-C8B1-41FE-9519-530FDFE92BFA@softarmor.com>	<461BE0CC.8010403@nostrum.com>	<4B7406B6-B323-43B1-B7BB-2843CD105F65@softarmor.com>	<461D1FB8.2070500@nostrum.com>	<E4E23388-C9F3-422D-B16E-DAD0114F096B@softarmor.com>
	<461D3B83.7000309@nostrum.com> <461E3588.1050505@softarmor.com>
In-Reply-To: <461E3588.1050505@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dean Willis wrote:
> But if you're maintaining an INVITE dialog, suspend sounds a lot like 
> hold.

I agree -- but I'm having a hard time understanding what you're 
proposing. From what you've said so far, it sounds like you're thinking 
something like:


       Caller                        Callee
          |(1) INVITE                   |
          |---------------------------->|
          |(2) 486                      |
          |<----------------------------|
          |(3) ACK                      |
          |---------------------------->|
          |                             |
          |Caller activates service     |
          |                             |
          |(4) SUBSCRIBE                |
          |---------------------------->|
          |(5) 200                      |
          |<----------------------------|
          |(6) NOTIFY                   |
          |<----------------------------|
          |(7) 200                      |
          |---------------------------->|
          |(8) INVITE                   |
          |---------------------------->|
          |(9) 200                      |
          |<----------------------------|
          |(10) ACK                     |
          |---------------------------->|
          |                             |
          |Caller pauses position       |
          |                             |
          |(11) INVITE                  |
          |---------------------------->|
          |(12) 200                     |
          |<----------------------------|
          |(13) ACK                     |
          |---------------------------->|
          |(14) NOTIFY                  |
          |<----------------------------|
          |(15) 200                     |
          |---------------------------->|
          |                             |
          |Caller resumes position      |
          |                             |
          |(16) INVITE                  |
          |---------------------------->|
          |(17) 200                     |
          |<----------------------------|
          |(18) ACK                     |
          |---------------------------->|
          |(19) NOTIFY                  |
          |<----------------------------|
          |(20) 200                     |
          |---------------------------->|
          |                             |
          |Callee becomes available     |
          |                             |
          |(21) NOTIFY                  |
          |<----------------------------|
          |(22) 200                     |
          |---------------------------->|
          |(23) BYE                     |
          |---------------------------->|
          |(24) 200                     |
          |<----------------------------|
          |                             |
          |Callee re-initiates call     |
          |                             |
          |(25) INVITE                  |
          |---------------------------->|
          |(26) 180                     |
          |<----------------------------|
          |(27) 200                     |
          |<----------------------------|
          |(28) ACK                     |
          |---------------------------->|


(You may find it easier to follow along using the image at 
<http://www.nostrum.com/~adam/images/callcomp-invite.png>)

Most of this should be self-explanatory. Messages 1 - 3 are the failed 
call setup attempt. Messages 4 - 7, 14, 15, 19, 20, 21, and 22 relate to 
the subscription to queue state. Messages 8 - 10 are the INVITE that the 
caller uses to place themselves in the "pending call" queue.

And that's where things start to get confusing for me. What kind of 
session is being set up here? Specifically, what goes in the SDP for 
messages 8 and 9 (or 9 and 10, if that's how you want to do it)? Are 
there any m= lines? What do they indicate?

Semantically, messages 11 through 13 are a re-invite sequence to put the 
session on hold. Hold is enacted by marking a media stream 
appropriately. There are (as far as I understand things) no media 
streams. How do we indicate hold? (Messages 16 through 18 are similarly 
un-hold, and have an identical series of questions). Again, what does 
the SDP look like?

Don't get me wrong -- this approach seems well positioned to address 
everyone's concerns (explicit operations, semantically correct use of 
SUB/NOT, no introduction of additional protocols) -- I'm just poking 
around the edges to try to figure out whether the details can be worked 
out in a sensible fashion. Right now the bugaboo seems to be that you 
want to set up a session to mark a place in the queue, but that this 
"session" doesn't actually exist, since there isn't any media being 
exchanged. (Remember, in SIP, the SIP protocol construct is a dialog; 
the "session" itself is a stream of media).

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 11:56:56 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc1fL-0008Sf-D7; Thu, 12 Apr 2007 11:56:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc1fJ-0008SQ-MN
	for sipping@ietf.org; Thu, 12 Apr 2007 11:56:53 -0400
Received: from relais-inet.francetelecom.com ([212.234.67.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc1fJ-0000UH-38
	for sipping@ietf.org; Thu, 12 Apr 2007 11:56:53 -0400
Received: from prive-Rline3.com ([192.168.1.32] [192.168.1.32]) by
	Rline3.francetelecom.com with ESMTP; Thu, 12 Apr 2007 17:56:52 +0200
Received: from PMEXCC31.intranet-paris.francetelecom.fr ([10.196.130.32]
	[10.196.130.32]) by Rline3.francetelecom.com with ESMTP;
	Thu, 12 Apr 2007 17:55:52 +0200
Received: from PMEXCB90.intranet-paris.francetelecom.fr ([10.196.130.54]) by
	PMEXCC31.intranet-paris.francetelecom.fr with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 12 Apr 2007 17:55:52 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Thu, 12 Apr 2007 17:55:53 +0200
Message-Id: <406AC648B5523840AE2274F1CBE61FD2512E26@PMEXCB90.intranet-paris.francetelecom.fr>
In-Reply-To: <461E5502.1090105@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
Thread-Index: Acd9GiVASMdCyiXNR86U2Qks8+jWmAAAI6aQ
From: "GARCIN S=?utf-8?B?w6k=?=bastien AERM"
	<sebastien.garcin@orange-ftgroup.com>
To: "Adam Roach" <adam@nostrum.com>, "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 12 Apr 2007 15:55:52.0294 (UTC)
	FILETIME=[0C0A5060:01C77D1B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


A lot of the confusion here comes from the fact that the flows show=
 "caller" and "callee" exchangin SUB/NOT message whereas the call=
 completion service transactions we are talking are to take place between=
 Application Servers serving the caller and callee parties=2E

s=E9bastien



Dean Willis wrote:
> But if you're maintaining an INVITE dialog, suspend sounds a lot like=20
> hold=2E

I agree -- but I'm having a hard time understanding what you're proposing=
=2E From what you've said so far, it sounds like you're thinking something=
 like:


       Caller                        Callee
          |(1) INVITE                   |
          |---------------------------->|
          |(2) 486                      |
          |<----------------------------|
          |(3) ACK                      |
          |---------------------------->|
          |                             |
          |Caller activates service     |
          |                             |
          |(4) SUBSCRIBE                |
          |---------------------------->|
          |(5) 200                      |
          |<----------------------------|
          |(6) NOTIFY                   |
          |<----------------------------|
          |(7) 200                      |
          |---------------------------->|
          |(8) INVITE                   |
          |---------------------------->|
          |(9) 200                      |
          |<----------------------------|
          |(10) ACK                     |
          |---------------------------->|
          |                             |
          |Caller pauses position       |
          |                             |
          |(11) INVITE                  |
          |---------------------------->|
          |(12) 200                     |
          |<----------------------------|
          |(13) ACK                     |
          |---------------------------->|
          |(14) NOTIFY                  |
          |<----------------------------|
          |(15) 200                     |
          |---------------------------->|
          |                             |
          |Caller resumes position      |
          |                             |
          |(16) INVITE                  |
          |---------------------------->|
          |(17) 200                     |
          |<----------------------------|
          |(18) ACK                     |
          |---------------------------->|
          |(19) NOTIFY                  |
          |<----------------------------|
          |(20) 200                     |
          |---------------------------->|
          |                             |
          |Callee becomes available     |
          |                             |
          |(21) NOTIFY                  |
          |<----------------------------|
          |(22) 200                     |
          |---------------------------->|
          |(23) BYE                     |
          |---------------------------->|
          |(24) 200                     |
          |<----------------------------|
          |                             |
          |Callee re-initiates call     |
          |                             |
          |(25) INVITE                  |
          |---------------------------->|
          |(26) 180                     |
          |<----------------------------|
          |(27) 200                     |
          |<----------------------------|
          |(28) ACK                     |
          |---------------------------->|


(You may find it easier to follow along using the image at
<http://www=2Enostrum=2Ecom/~adam/images/callcomp-invite=2Epng>)

Most of this should be self-explanatory=2E Messages 1 - 3 are the failed=
 call setup attempt=2E Messages 4 - 7, 14, 15, 19, 20, 21, and 22 relate to=
 the subscription to queue state=2E Messages 8 - 10 are the INVITE that the=
 caller uses to place themselves in the "pending call" queue=2E

And that's where things start to get confusing for me=2E What kind of=
 session is being set up here? Specifically, what goes in the SDP for=
 messages 8 and 9 (or 9 and 10, if that's how you want to do it)? Are there=
 any m=3D lines? What do they indicate?

Semantically, messages 11 through 13 are a re-invite sequence to put the=
 session on hold=2E Hold is enacted by marking a media stream appropriately=
=2E There are (as far as I understand things) no media streams=2E How do we=
 indicate hold? (Messages 16 through 18 are similarly un-hold, and have an=
 identical series of questions)=2E Again, what does the SDP look like?

Don't get me wrong -- this approach seems well positioned to address=
 everyone's concerns (explicit operations, semantically correct use of=
 SUB/NOT, no introduction of additional protocols) -- I'm just poking=
 around the edges to try to figure out whether the details can be worked=
 out in a sensible fashion=2E Right now the bugaboo seems to be that you=
 want to set up a session to mark a place in the queue, but that this=
 "session" doesn't actually exist, since there isn't any media being=
 exchanged=2E (Remember, in SIP, the SIP protocol construct is a dialog;=
 the "session" itself is a stream of media)=2E

/a

_______________________________________________
Sipping mailing list  https://www1=2Eietf=2Eorg/mailman/listinfo/sipping
This list is for NEW development of the application of SIP Use=
 sip-implementors@cs=2Ecolumbia=2Eedu for questions on current sip Use=
 sip@ietf=2Eorg for new developments of core SIP


*********************************
This message and any attachments (the "message") are confidential and=
 intended solely for the addressees=2E Any unauthorised
use or dissemination is prohibited=2E
Messages are susceptible to alteration=2E France Telecom Group shall not be=
 liable for the message if altered, changed or
falsified=2E
If you are not the intended addressee of this message, please cancel it=
 immediately and inform the sender=2E
********************************

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 11:58:50 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc1hB-0000hU-SX; Thu, 12 Apr 2007 11:58:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc1hA-0000hJ-Km
	for sipping@ietf.org; Thu, 12 Apr 2007 11:58:48 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc1hA-0000iZ-9g
	for sipping@ietf.org; Thu, 12 Apr 2007 11:58:48 -0400
Received: from [64.101.173.120] ([64.101.173.120]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3CF5OtH005269
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 12 Apr 2007 10:05:25 -0500
In-Reply-To: <461E3CE2.7000009@cisco.com>
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
	<461CED8F.60501@cisco.com>
	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>
	<461D28EE.4070904@nostrum.com> <461E3486.3050906@softarmor.com>
	<461E3CE2.7000009@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Thu, 12 Apr 2007 10:58:32 -0500
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: sipping@ietf.org, Adam Roach <adam@nostrum.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 12, 2007, at 9:06 AM, Paul Kyzivat wrote:

>
>
> Dean Willis wrote:
>> Adam Roach wrote:
>>>
>>> _That's_ interesting. I hadn't thought of that. So, instead of  
>>> using BFCP (as my current proposal suggests), we could use an  
>>> event package to unobtrusively subscribe to a queue, and XCAP to  
>>> place ourselves in, pause, resume, and remove ourselves from the  
>>> queue.
>>>
>>> That seems quite reasonable. I'd be interested to see what other  
>>> people have to say about it.
>> I didn't mean to suggest that the caller enqueue themselves with  
>> XCAP, but that if the queue manager and the event server were on  
>> different nodes that the queue manager could manipulate the queue  
>> state document using XCAP.
>> I still think that being enqueued as a result of an INVITE is a  
>> reasonable thing.
>
> Dean,
>
> The ultimate goal seems to be to give the potential caller at the  
> top of the queue a window of opportunity to attempt a call. During  
> that time, you don't want to allow the other pending callers, or  
> new callers, to establish a call to the callee.
>

That's easy. The queue manager uses something like watcherinfo to  
know whether that caller is watching the queue and waiting for his  
turn to come up.

> But if you enroll everybody that attempts a call, without knowing  
> that they will use the queue to retry, then you have a problem. You  
> don't want to give a window of opportunity to someone who isn't  
> waiting.

Those who watch and wait are also served . . .

>
> I guess you could go ahead and enroll the caller of every failed  
> call, but only give a window of opportunity to a candidate that has  
> been notified that it is at the head of the queue.
>

That would work too -- if the NOTIFY times out, expunge. But it does  
add about 32s of latency.

> That also suggests a way to handle suspend/resume: to suspend you  
> simply cancel your subscription. And to resume you make a new  
> subscription.

yeah, that works. The requirement is that the queue-place is not  
purged as a side effect of canceling the subscription. Rather, the  
watcherinfo is used to determine the duration for which that queue- 
place will be held at the top of the queue.

What happens if you "suspend" and your place comes and goes during  
the interval? Sounds like we'd also have to have a little more  
complex queue management to give a recovery window, but it is very  
doable.

>
> That seems somewhat interesting. But it presents a new problem - a  
> subscriber needs to know if they even have an entry in the queue.  
> If you only get notified when you get to the top, then you could  
> wait forever if you aren't in the queue.
>

Right. Would it be reasonable to have a server-side cancel on the  
subscription if your token goes stale?

--
Dean




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 12:00:04 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc1iL-0002Md-PF; Thu, 12 Apr 2007 12:00:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc1iJ-0002LY-JE
	for sipping@ietf.org; Thu, 12 Apr 2007 11:59:59 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc1iI-0000qN-9o
	for sipping@ietf.org; Thu, 12 Apr 2007 11:59:59 -0400
Received: from [64.101.173.120] ([64.101.173.120]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3CF6Zrl005280
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 12 Apr 2007 10:06:36 -0500
In-Reply-To: <461E5502.1090105@nostrum.com>
References: <46154996.50305@nostrum.com><458913680704100608u77bc9f1cl7fcb0cc885d7d96d@mail.gmail.com>	<461B8FB7.3000903@nostrum.com>	<072C5B76F7CEAB488172C6F64B30B5E302DB38C4@xmb-rtp-20b.amer.cisco.com>	<461BCAD7.1020001@nostrum.com>	<34668222-C8B1-41FE-9519-530FDFE92BFA@softarmor.com>	<461BE0CC.8010403@nostrum.com>	<4B7406B6-B323-43B1-B7BB-2843CD105F65@softarmor.com>	<461D1FB8.2070500@nostrum.com>	<E4E23388-C9F3-422D-B16E-DAD0114F096B@softarmor.com>
	<461D3B83.7000309@nostrum.com> <461E3588.1050505@softarmor.com>
	<461E5502.1090105@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C78ED1EF-D728-4CB2-9213-7B27505455BE@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Thu, 12 Apr 2007 10:59:45 -0500
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 12, 2007, at 10:49 AM, Adam Roach wrote:

> Dean Willis wrote:
>> But if you're maintaining an INVITE dialog, suspend sounds a lot  
>> like hold.
>
> I agree -- but I'm having a hard time understanding what you're  
> proposing. From what you've said so far, it sounds like you're  
> thinking something like:

yeah, that's what I was thinking, but I don't like it. I like the  
watcherinfo model as came out of Paul's ideas a lot better.

--
Dean


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 12:01:53 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc1k9-0003iL-Dz; Thu, 12 Apr 2007 12:01:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc1k7-0003i7-Rl
	for sipping@ietf.org; Thu, 12 Apr 2007 12:01:51 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc1k6-0001Q7-I7
	for sipping@ietf.org; Thu, 12 Apr 2007 12:01:51 -0400
Received: from [64.101.173.120] ([64.101.173.120]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3CF8Rse005296
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 12 Apr 2007 10:08:29 -0500
In-Reply-To: <406AC648B5523840AE2274F1CBE61FD2512E26@PMEXCB90.intranet-paris.francetelecom.fr>
References: <406AC648B5523840AE2274F1CBE61FD2512E26@PMEXCB90.intranet-paris.francetelecom.fr>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <3999DA03-578D-4B05-9E23-BC6E42B1B97A@softarmor.com>
Content-Transfer-Encoding: quoted-printable
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Thu, 12 Apr 2007 11:01:37 -0500
To: =?ISO-8859-1?Q?"GARCIN_S=E9bastien_AERM"?=
	<sebastien.garcin@orange-ftgroup.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: SIPPING WG <sipping@ietf.org>, Adam Roach <adam@nostrum.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 12, 2007, at 10:55 AM, GARCIN S=E9bastien AERM wrote:

>
> A lot of the confusion here comes from the fact that the flows show =20=

> "caller" and "callee" exchangin SUB/NOT message whereas the call =20
> completion service transactions we are talking are to take place =20
> between Application Servers serving the caller and callee parties.

Don't try and complicate our world by pretending that B2BUAs are =20
anything but UAs.

We don't care WHERE your user agent is or what kind of bastardized =20
protocol it uses to present a user. =46rom the SIP perspective, it's =20
just a UA.

--
Dean


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 13:50:27 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc3R6-0006W6-V4; Thu, 12 Apr 2007 13:50:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc3R6-0006VW-0A
	for sipping@ietf.org; Thu, 12 Apr 2007 13:50:20 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc3R5-0007kf-5w
	for sipping@ietf.org; Thu, 12 Apr 2007 13:50:19 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3CHoGPD014886
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 12:50:17 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461E7160.7010409@nostrum.com>
Date: Thu, 12 Apr 2007 12:50:24 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
Subject: Re: AW: AW: [Sipping] Call Completion: In Defense of Explicit
	Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA3E@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <CCA850DCD3FBE2479D5076C5C18732220168AA3E@S4DE9JSAAHW.ost.t-com.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by nostrum.com id
	l3CHoGPD014886
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Cc: pkyzivat@cisco.com, sipping@ietf.org, dean.willis@softarmor.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

You're getting close -- but you really don't want resources to be=20
popping in and out of existence ephemerally, if at all possible. What=20
people have been discussing so far is that user A subscribes to user B's=20
"pending queue of calls" state, not user A's own "my call completion stat=
e."

Additionally, the former kind of information has a much broader=20
application (think of, for example, the ability for a supervisor to=20
watch a queue of pending calls for a call center), while the latter is=20
extremely service-specific.

We're still floundering on the queue manipulation bit; it sounds like=20
people don't quite like the XCAP approach.

/a

Huelsemann, Martin wrote:
> Would it then look like as follows?
>
>
> --- Activation and retention
>
> A calls B, B is busy, B has queueing function, A gets provisionally que=
ued,
> =20
> Timer for A's queueing confirmation starts,=20
>
> resource "A's call-completion state" is created (would be instance or f=
unction of the queue),=20
>
> Allow-events:call-completion is inserted in 486 (this would be the cc-p=
ossible indication for A),=20
>
> A subscribes to his call-completion state, A gets notification cc-state=
=3Didle,
>
> A uses XCAP to add himself to the queue (queueing is confirmed at B que=
ue, confirmation timer stops), A gets notification cc-state=3Dqueued
>
> B becomes not busy, A gets notification cc-state=3Dstart-recall
>
> recall fails for some reasons, retention option is fulfilled, A gets no=
tification cc-state=3Dqueued
>
>
>
> --- Deactivation
>
> call-completion activated
>
> A uses XCAP to remove himself from the queue, A gets notification cc-st=
ate=3Didle,
>
> A terminates subscription=20
>
>
>
>
> Are this roughly the procedures you are thinking of?=20
>
>
>
> Martin
>
>
>
>
>  =20
>> -----Urspr=FCngliche Nachricht-----
>> Von: Adam Roach [mailto:adam@nostrum.com]=20
>> Gesendet: Mittwoch, 11. April 2007 20:29
>> An: Dean Willis
>> Cc: Paul Kyzivat; H=FClsemann, Martin; sipping@ietf.org
>> Betreff: Re: AW: [Sipping] Call Completion: In Defense of=20
>> Explicit Operations
>>
>>
>> Dean Willis wrote:
>>    =20
>>> So the open question is how does one get into the queue=20
>>>      =20
>> without having=20
>>    =20
>>> that insertion be a side-effect of the subscription itself?
>>>
>>> Two options:
>>>
>>> 1) Automatically enqueue all callers when there is a queue.
>>>      =20
>> Interesting approach -- I'm not sure how well it will work in=20
>> practice,=20
>> because you'll end up having to wait for the queue of missed=20
>> calls from=20
>> disinterested parties to drain before your position percolates to the=20
>> top of the queue. It's probably solvable, but we'd need to=20
>> come up with=20
>> something.
>>
>>    =20
>>> 2) Redirect (or indirect via a new header field) callers to a queue=20
>>> factory when there is a queue. If they follow the indirection, they=20
>>> get enqueued.
>>>      =20
>> Ooh. Run this one by Dave Oran. Perhaps we can get him to give his=20
>> "To-Explode-My-Phone:" speech again.
>>
>>    =20
>>> I concur that insertion into the queue and subscription to=20
>>>      =20
>> the queue=20
>>    =20
>>> must be different things. That seems obvious, so I must have missed=20
>>> the idea that they were intertwingled (or dismissed it as=20
>>>      =20
>> just silly).
>>
>> Yes, they must be different things. Yes, this is obvious. Yes, it is=20
>> silly to propose that they be combined into the same operation. Yes,=20
>> this very silly thing is at the core of the draft-poetzl proposal.
>>
>>    =20
>>> Operations on the queue data itself are clearly outside of the=20
>>> "watcher" package. If the queue notification is handled on=20
>>>      =20
>> a node that=20
>>    =20
>>> is different from the node with the data that drives the=20
>>>      =20
>> queue, then=20
>>    =20
>>> we have XCAP to manipulate the queue document and make=20
>>>      =20
>> insertions, etc.
>>
>> _That's_ interesting. I hadn't thought of that. So, instead of using=20
>> BFCP (as my current proposal suggests), we could use an event=20
>> package to=20
>> unobtrusively subscribe to a queue, and XCAP to place ourselves in,=20
>> pause, resume, and remove ourselves from the queue.
>>
>> That seems quite reasonable. I'd be interested to see what=20
>> other people=20
>> have to say about it.
>>
>> /a
>>
>>    =20
>
> _______________________________________________
> Sipping mailing list  https://www1.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
>  =20


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 14:14:47 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc3og-0002UC-76; Thu, 12 Apr 2007 14:14:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc3oe-0002RC-N5
	for sipping@ietf.org; Thu, 12 Apr 2007 14:14:40 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc3oP-0005zd-2S
	for sipping@ietf.org; Thu, 12 Apr 2007 14:14:25 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3CIEJFt016971
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 13:14:19 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461E7703.8010709@nostrum.com>
Date: Thu, 12 Apr 2007 13:14:27 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>
	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>
	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
In-Reply-To: <32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: Paul Kyzivat <pkyzivat@cisco.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dean Willis wrote:
>
> On Apr 12, 2007, at 9:06 AM, Paul Kyzivat wrote:
>
>>
>> Dean,
>>
>> The ultimate goal seems to be to give the potential caller at the top 
>> of the queue a window of opportunity to attempt a call. During that 
>> time, you don't want to allow the other pending callers, or new 
>> callers, to establish a call to the callee.
>>
>
> That's easy. The queue manager uses something like watcherinfo to know 
> whether that caller is watching the queue and waiting for his turn to 
> come up.
>
>> But if you enroll everybody that attempts a call, without knowing 
>> that they will use the queue to retry, then you have a problem. You 
>> don't want to give a window of opportunity to someone who isn't waiting.
>
> Those who watch and wait are also served . . .

An interesting approach, to be sure. You're using the subscription 
itself in a similar fashion to the INVITE session from before. You're 
modeling the queue controller as an external third party using stock 
winfo to receive information. I think modeling this as an external 
network element will do a reasonably good job of keeping us out of trouble.

Co-location of the 3265 server and the queue handler would, of course, 
always be possible -- but once we go down a path that *requires* 
co-location, it's pretty clear that we've strayed into dangerous 
territory. This means that subscription to the queue is necessarily 
non-atomic with being added to the queue, and that nothing in the 
subscription itself can modify one's position in the queue.

Great! This defines semantics for putting one's self into the queue, for 
removing one's self from a queue, and for discovering when one is at the 
front of the queue. That's three out of five; so now I have to re-ask my 
two questions:

   1. How does the queued caller pause their position in the queue?
   2. How does the queued caller un-pause their position in the queue?


/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 14:55:04 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc4Rb-0002mM-Lr; Thu, 12 Apr 2007 14:54:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc4Ra-0002mE-47
	for sipping@ietf.org; Thu, 12 Apr 2007 14:54:54 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc4RY-0005kE-Nd
	for sipping@ietf.org; Thu, 12 Apr 2007 14:54:54 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3CIsoiW052253
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 13:54:50 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461E8083.2010606@nostrum.com>
Date: Thu, 12 Apr 2007 13:54:59 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com>
In-Reply-To: <461E7703.8010709@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 1.0 (+)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Cc: Paul Kyzivat <pkyzivat@cisco.com>, sipping@ietf.org,
	Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Adam Roach wrote:
>
> Great! This defines semantics for putting one's self into the queue, 
> for removing one's self from a queue, and for discovering when one is 
> at the front of the queue. That's three out of five; so now I have to 
> re-ask my two questions:
>
>   1. How does the queued caller pause their position in the queue?
>   2. How does the queued caller un-pause their position in the queue?

Whoops. Sorry; I missed your suggestion that the subscription also 
controls whether the entry is held at the top of the queue for an 
allowed callback period or merely discarded. I guess that works, so long 
as the service definition is such that a "paused" entry continues to 
advance in the queue, and is discarded if it reaches the front while paused.

Or I guess the queue controller could take note of the fact that a 
subscription from that user existed at some point in the past, so it 
will freeze advancing it for a reasonable period of time (say, one 
hour), at which point it gets discarded. In fact, I'm not certain the 
queue controller's behavior would even be appropriate for 
standardization here, as long as the caller had a way to learn, upon 
resubscription, whether he still has a position in the queue.

So, what it's shaping up to look like is something like this: the event 
package itself has an underlying state that would look something like this:

    <queue target="sip:zachary@example.name">

      <user name="Bob Smith"
            uri="sip:bob@example.com"
            position="1"
            state="active"
           
    callback="sip:86dacaff-e941-4fb1-86d6-1ef8adee4658@example.name"
            expires="60" />

      <user name="Alice Jones"
            uri="sip:alice@example.org"
            position="2"
            state="pending" />

      <user name="Charlie Farmer"
            uri="sip:charlie@example.net"
            position="3"
            state="void" />

      <user name="Dave Little"
            uri="sip:dave@example.biz"
            position="4"
            state="paused" />

      <user name="Ed Gardner"
            uri="sip:ed@example.info"
            position="5"
            state="pending" />

    </queue>


In theory, there may be users (e.g., administrative assistants, call 
center supervisors) who have access to this complete state document, but 
*most* people will receive an administratively-filtered view of its.

For example, if Ed subscribes to this state, the authorization policy at 
the server might be such that he is filtered from seeing any information 
but his own; meaning that he would receive notification similar to:


    <queue target="sip:zachary@example.name">
      <user name="Ed Gardner"
            uri="sip:ed@example.info"
            position="5"
            state="pending" />
    </queue>



So, Ed knows he is in the queue, and that there are 4 people in front of 
him. He'll be notified whenever he advances in the queue, and (most 
importantly) when he gets to the head of the queue. He'll also get 
another notification when he is removed from the queue. I think that all 
works exactly like we need it to.

Bob, on the other hand, would see only *his* own entry, which contains 
the information he needs to re-attempt his call (i.e., a callback URI, 
along with some indication of how long the URI will remain valid):

    <queue target="sip:zachary@example.name">
      <user name="Bob Smith"
            uri="sip:bob@example.com"
            position="1"
            state="active"
           
    callback="sip:86dacaff-e941-4fb1-86d6-1ef8adee4658@example.name"
            expires="60" />
    </queue>


Dave has apparently unsubscribed from the state. The queue handler 
received notification of this fact (via callqueue.winfo), and 
consequently paused his entry. The queue handler will keep the entry 
paused until it gets a callqueue.winfo notification that Dave has 
subscribed again, or until it reaches its administratively-provisioned 
timeout that sets how long it is willing to hold on to a paused user.

Charlie has never subscribed to the queue state. The queue handler will 
either remove his entry after a implementation-specific timeout or when 
it reaches the top of the queue.

If Fred (not listed above) attempts to subscribe to the queue state, 
he'll find out that he's not in the queue because he won't be in the 
queue...

    <queue target="sip:zachary@example.name" />

I think that covers all the vagaries of getting people in and out of the 
queue, pausing them and unpausing them, and making sure they know 
whether they'll be notified of their chance to call back in the future.

Sound reasonable? Any obvious holes?

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 14:57:10 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc4Tl-0005Ci-C7; Thu, 12 Apr 2007 14:57:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc4Tk-0005Cc-CV
	for sipping@ietf.org; Thu, 12 Apr 2007 14:57:08 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc4Tk-0006wE-00
	for sipping@ietf.org; Thu, 12 Apr 2007 14:57:08 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3CIv6AX052416
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 13:57:06 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461E810A.2020309@nostrum.com>
Date: Thu, 12 Apr 2007 13:57:14 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
In-Reply-To: <461E8083.2010606@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
Cc: Paul Kyzivat <pkyzivat@cisco.com>, sipping@ietf.org,
	Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Responding to myself *yet* *again*...

After a few seconds' more thought, I'm not sure this is what we want -- 
mostly because there's no distinction between "pause my entry in the 
queue" and "remove my entry from the queue."

*sigh*

/a

Adam Roach wrote:
> Adam Roach wrote:
>>
>> Great! This defines semantics for putting one's self into the queue, 
>> for removing one's self from a queue, and for discovering when one is 
>> at the front of the queue. That's three out of five; so now I have to 
>> re-ask my two questions:
>>
>>   1. How does the queued caller pause their position in the queue?
>>   2. How does the queued caller un-pause their position in the queue?
>
> Whoops. Sorry; I missed your suggestion that the subscription also 
> controls whether the entry is held at the top of the queue for an 
> allowed callback period or merely discarded. I guess that works, so 
> long as the service definition is such that a "paused" entry continues 
> to advance in the queue, and is discarded if it reaches the front 
> while paused.
>
> Or I guess the queue controller could take note of the fact that a 
> subscription from that user existed at some point in the past, so it 
> will freeze advancing it for a reasonable period of time (say, one 
> hour), at which point it gets discarded. In fact, I'm not certain the 
> queue controller's behavior would even be appropriate for 
> standardization here, as long as the caller had a way to learn, upon 
> resubscription, whether he still has a position in the queue.
>
> So, what it's shaping up to look like is something like this: the 
> event package itself has an underlying state that would look something 
> like this:
>
>    <queue target="sip:zachary@example.name">
>
>      <user name="Bob Smith"
>            uri="sip:bob@example.com"
>            position="1"
>            state="active"
>              
> callback="sip:86dacaff-e941-4fb1-86d6-1ef8adee4658@example.name"
>            expires="60" />
>
>      <user name="Alice Jones"
>            uri="sip:alice@example.org"
>            position="2"
>            state="pending" />
>
>      <user name="Charlie Farmer"
>            uri="sip:charlie@example.net"
>            position="3"
>            state="void" />
>
>      <user name="Dave Little"
>            uri="sip:dave@example.biz"
>            position="4"
>            state="paused" />
>
>      <user name="Ed Gardner"
>            uri="sip:ed@example.info"
>            position="5"
>            state="pending" />
>
>    </queue>
>
>
> In theory, there may be users (e.g., administrative assistants, call 
> center supervisors) who have access to this complete state document, 
> but *most* people will receive an administratively-filtered view of its.
>
> For example, if Ed subscribes to this state, the authorization policy 
> at the server might be such that he is filtered from seeing any 
> information but his own; meaning that he would receive notification 
> similar to:
>
>
>    <queue target="sip:zachary@example.name">
>      <user name="Ed Gardner"
>            uri="sip:ed@example.info"
>            position="5"
>            state="pending" />
>    </queue>
>
>
>
> So, Ed knows he is in the queue, and that there are 4 people in front 
> of him. He'll be notified whenever he advances in the queue, and (most 
> importantly) when he gets to the head of the queue. He'll also get 
> another notification when he is removed from the queue. I think that 
> all works exactly like we need it to.
>
> Bob, on the other hand, would see only *his* own entry, which contains 
> the information he needs to re-attempt his call (i.e., a callback URI, 
> along with some indication of how long the URI will remain valid):
>
>    <queue target="sip:zachary@example.name">
>      <user name="Bob Smith"
>            uri="sip:bob@example.com"
>            position="1"
>            state="active"
>              
> callback="sip:86dacaff-e941-4fb1-86d6-1ef8adee4658@example.name"
>            expires="60" />
>    </queue>
>
>
> Dave has apparently unsubscribed from the state. The queue handler 
> received notification of this fact (via callqueue.winfo), and 
> consequently paused his entry. The queue handler will keep the entry 
> paused until it gets a callqueue.winfo notification that Dave has 
> subscribed again, or until it reaches its administratively-provisioned 
> timeout that sets how long it is willing to hold on to a paused user.
>
> Charlie has never subscribed to the queue state. The queue handler 
> will either remove his entry after a implementation-specific timeout 
> or when it reaches the top of the queue.
>
> If Fred (not listed above) attempts to subscribe to the queue state, 
> he'll find out that he's not in the queue because he won't be in the 
> queue...
>
>    <queue target="sip:zachary@example.name" />
>
> I think that covers all the vagaries of getting people in and out of 
> the queue, pausing them and unpausing them, and making sure they know 
> whether they'll be notified of their chance to call back in the future.
>
> Sound reasonable? Any obvious holes?
>
> /a


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 17:04:31 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc6Sy-0005Wl-Fl; Thu, 12 Apr 2007 17:04:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc6Sx-0005Wg-8i
	for sipping@ietf.org; Thu, 12 Apr 2007 17:04:27 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc6Sv-0002hf-S3
	for sipping@ietf.org; Thu, 12 Apr 2007 17:04:27 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 12 Apr 2007 17:04:21 -0400
X-IronPort-AV: i="4.14,405,1170651600"; 
	d="scan'208"; a="57492101:sNHT53993988"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l3CL4L4d004928; 
	Thu, 12 Apr 2007 17:04:21 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3CL4LGd004746; 
	Thu, 12 Apr 2007 21:04:21 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 17:04:21 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 17:04:21 -0400
Message-ID: <461E9ED3.2010103@cisco.com>
Date: Thu, 12 Apr 2007 17:04:19 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: sipping@ietf.org
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>
	<461CED8F.60501@cisco.com>
	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>
	<461D28EE.4070904@nostrum.com> <461E3486.3050906@softarmor.com>
	<461E3CE2.7000009@cisco.com>
In-Reply-To: <461E3CE2.7000009@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Apr 2007 21:04:21.0036 (UTC)
	FILETIME=[241C36C0:01C77D46]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4696; t=1176411861;
	x=1177275861; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defen
	se=20of=20Explicit=20Operations |Sender:=20
	|To:=20sipping@ietf.org;
	bh=qp6W350bBb94+sXGNW8CEwvit9qp5uNnlf61qsENBn0=;
	b=myiBIFlHu0hOIjgLHptE/+lILJ2sGFLfoNA5rpTf56x6UEHDrut9LwZh6+OxV13FaB1gBDQX
	vLjIOXe3fPJ5y9s2dAE5Lucs+DQHYPzrxGVTW2YaUN9eZZ+dT9mQCsd0;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: Adam Roach <adam@nostrum.com>, Dean Willis <deawilli@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

My comments below were off the cuff in response to what had been said. 
But what I ended up at seems like an almost complete and workable 
approach. So let me try to explain it again directly:

1) A calls B.
2) B decides to reject the call (say busy)
3) B adds the caller A to the call completion queue
4) B returns a 486 response with some indication that
    the caller has been queued (how is TBD)
5) if A wants to use the call completion feature,
    it subscribes to the event package.
6) B sends an initial notify, with queue status.
    Policy most likely limits the information to
    entries naming the subscriber. (Presumably there
    is only one.) With the entry is a status, which
    can be either "waiting" or "selected". Assume it
    is "waiting" because others are in the queue.
7) When B becomes available for a call, it selects the
    oldest entry in the queue for which there is a watcher.
    It changes the state of that entry to "selected".
    As a result of the change, a notification is sent
    to any watchers that can see the change. That includes
    at least A.
8) Perhaps while that is happening B may receive a call
    from C. B knows what is going on, notes that the caller
    is not the selected caller B, and so rejects the call.
    (Same actions as above.)
9) When A receives the notify, it alerts its user. When
    the user is ready, it places the call to B again.
10) When B receives the call from A, it notes it is the
    selected caller and answers. It also then removes the
    entry for A from the queue. This results in a notify
    to A that there is no entry for it in the queue.
11) When A receives that notify, it cancels its subscription.

If, following (4), A had not bothered to subscribe, its entry would 
remain in the queue for awhile. Entries will age out of the queue 
eventually.

If, following (6), enters a state where it won't be able to complete the 
call to B (e.g. A gets a call from C), then A simply unsubscribes. When 
A is again ready to try, it again subscribes. (Being subscribed or not 
is the means of doing suspend and resume.)

For CCNA (no answer) I think B will have to put the caller into the 
queue any time a call is abandoned by the caller. I think that is ok.

	Paul


Paul Kyzivat wrote:
> 
> 
> Dean Willis wrote:
>> Adam Roach wrote:
>>
>>>
>>> _That's_ interesting. I hadn't thought of that. So, instead of using 
>>> BFCP (as my current proposal suggests), we could use an event package 
>>> to unobtrusively subscribe to a queue, and XCAP to place ourselves 
>>> in, pause, resume, and remove ourselves from the queue.
>>>
>>> That seems quite reasonable. I'd be interested to see what other 
>>> people have to say about it.
>>
>> I didn't mean to suggest that the caller enqueue themselves with XCAP, 
>> but that if the queue manager and the event server were on different 
>> nodes that the queue manager could manipulate the queue state document 
>> using XCAP.
>>
>> I still think that being enqueued as a result of an INVITE is a 
>> reasonable thing.
> 
> Dean,
> 
> The ultimate goal seems to be to give the potential caller at the top of 
> the queue a window of opportunity to attempt a call. During that time, 
> you don't want to allow the other pending callers, or new callers, to 
> establish a call to the callee.
> 
> But if you enroll everybody that attempts a call, without knowing that 
> they will use the queue to retry, then you have a problem. You don't 
> want to give a window of opportunity to someone who isn't waiting.
> 
> I guess you could go ahead and enroll the caller of every failed call, 
> but only give a window of opportunity to a candidate that has been 
> notified that it is at the head of the queue.
> 
> That also suggests a way to handle suspend/resume: to suspend you simply 
> cancel your subscription. And to resume you make a new subscription.
> 
> That seems somewhat interesting. But it presents a new problem - a 
> subscriber needs to know if they even have an entry in the queue. If you 
> only get notified when you get to the top, then you could wait forever 
> if you aren't in the queue.
> 
> I guess that could be handled by having an initial notification report 
> your queue entry even if you are not first - perhaps giving position in 
> queue. Then a subsequent notifications could be filtered unless the 
> entry is first in queue, if it is considered undesirable to notify of 
> every change in position. That would take some peculiar language around 
> the design of a filter, but seems like it should be possible.
> 
>     Paul
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 17:10:41 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc6Yz-0007aj-6A; Thu, 12 Apr 2007 17:10:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc6Yx-0007RW-11
	for sipping@ietf.org; Thu, 12 Apr 2007 17:10:39 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc6Yv-0003ri-OL
	for sipping@ietf.org; Thu, 12 Apr 2007 17:10:39 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3CLAXm5059299
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 16:10:34 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461EA052.5080901@nostrum.com>
Date: Thu, 12 Apr 2007 16:10:42 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>
	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>
	<461E9ED3.2010103@cisco.com>
In-Reply-To: <461E9ED3.2010103@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: sipping@ietf.org, Dean Willis <deawilli@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Paul:

You ended up describing pretty much the same system as I did. Look over 
my earlier mail on the topic, paying close attention to the importance 
of modeling the queue controller as a third party. Any comments on this 
aspect? How about the differentiation between suspend and cancel? It 
might not be important for a pure SIP service, but I can see this 
potentially causing problems in the PSTN interwork case.

One more comment below.

Paul Kyzivat wrote:
> For CCNA (no answer) I think B will have to put the caller into the 
> queue any time a call is abandoned by the caller. I think that is ok.

Yes; it's almost exactly the same solution. The primary difference is a 
matter of a 486 response code versus a 487 response code.


/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 17:17:02 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc6f7-0004zS-LU; Thu, 12 Apr 2007 17:17:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc6f5-0004zL-Ne
	for sipping@ietf.org; Thu, 12 Apr 2007 17:16:59 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc6f5-0005jT-AQ
	for sipping@ietf.org; Thu, 12 Apr 2007 17:16:59 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 12 Apr 2007 17:16:59 -0400
X-IronPort-AV: i="4.14,405,1170651600"; 
	d="scan'208"; a="57494117:sNHT59907132"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3CLGxcc021825; 
	Thu, 12 Apr 2007 17:16:59 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l3CLGblU019171; 
	Thu, 12 Apr 2007 21:16:50 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 17:16:39 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 17:16:39 -0400
Message-ID: <461EA1B6.4010003@cisco.com>
Date: Thu, 12 Apr 2007 17:16:38 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
In-Reply-To: <461E8083.2010606@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Apr 2007 21:16:39.0411 (UTC)
	FILETIME=[DC374C30:01C77D47]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5544; t=1176412619;
	x=1177276619; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defen
	se=20of=20Explicit=20Operations |Sender:=20
	|To:=20Adam=20Roach=20<adam@nostrum.com>;
	bh=wCjIM1O2fzpjolXeDxT11J88J4wKSnQqt5Ac+ArSdm8=;
	b=AVjvGnqHYYiQ/j+Z1J/Hu/MQMMmauedJVtJSuVMRAM9GYgPBfoDm56v9p55Ppz0SqRBs2iK9
	m0C9E4dHyQ42SRPDJe8PuwEnX6bKz0QmdkpNZBOVBlf0kThTDorzyoIe;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
Cc: sipping@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I replied separately before seeing this. My reply describes something 
pretty much equivalent to this.

One nuance of mine (would work with yours too) is that the <state> can 
be sufficient to tell the watcher that it is time for it to call - he 
doesn't have to see the position. The position could be filtered out by 
policy (because the callee doesn't want people to know it), or it could 
be filtered out by a caller-supplied filter (because the caller doesn't 
want to get the extraneous notifications.

	Paul

Adam Roach wrote:
> Adam Roach wrote:
>>
>> Great! This defines semantics for putting one's self into the queue, 
>> for removing one's self from a queue, and for discovering when one is 
>> at the front of the queue. That's three out of five; so now I have to 
>> re-ask my two questions:
>>
>>   1. How does the queued caller pause their position in the queue?
>>   2. How does the queued caller un-pause their position in the queue?
> 
> Whoops. Sorry; I missed your suggestion that the subscription also 
> controls whether the entry is held at the top of the queue for an 
> allowed callback period or merely discarded. I guess that works, so long 
> as the service definition is such that a "paused" entry continues to 
> advance in the queue, and is discarded if it reaches the front while 
> paused.
> 
> Or I guess the queue controller could take note of the fact that a 
> subscription from that user existed at some point in the past, so it 
> will freeze advancing it for a reasonable period of time (say, one 
> hour), at which point it gets discarded. In fact, I'm not certain the 
> queue controller's behavior would even be appropriate for 
> standardization here, as long as the caller had a way to learn, upon 
> resubscription, whether he still has a position in the queue.
> 
> So, what it's shaping up to look like is something like this: the event 
> package itself has an underlying state that would look something like this:
> 
>    <queue target="sip:zachary@example.name">
> 
>      <user name="Bob Smith"
>            uri="sip:bob@example.com"
>            position="1"
>            state="active"
>              
> callback="sip:86dacaff-e941-4fb1-86d6-1ef8adee4658@example.name"
>            expires="60" />
> 
>      <user name="Alice Jones"
>            uri="sip:alice@example.org"
>            position="2"
>            state="pending" />
> 
>      <user name="Charlie Farmer"
>            uri="sip:charlie@example.net"
>            position="3"
>            state="void" />
> 
>      <user name="Dave Little"
>            uri="sip:dave@example.biz"
>            position="4"
>            state="paused" />
> 
>      <user name="Ed Gardner"
>            uri="sip:ed@example.info"
>            position="5"
>            state="pending" />
> 
>    </queue>
> 
> 
> In theory, there may be users (e.g., administrative assistants, call 
> center supervisors) who have access to this complete state document, but 
> *most* people will receive an administratively-filtered view of its.
> 
> For example, if Ed subscribes to this state, the authorization policy at 
> the server might be such that he is filtered from seeing any information 
> but his own; meaning that he would receive notification similar to:
> 
> 
>    <queue target="sip:zachary@example.name">
>      <user name="Ed Gardner"
>            uri="sip:ed@example.info"
>            position="5"
>            state="pending" />
>    </queue>
> 
> 
> 
> So, Ed knows he is in the queue, and that there are 4 people in front of 
> him. He'll be notified whenever he advances in the queue, and (most 
> importantly) when he gets to the head of the queue. He'll also get 
> another notification when he is removed from the queue. I think that all 
> works exactly like we need it to.
> 
> Bob, on the other hand, would see only *his* own entry, which contains 
> the information he needs to re-attempt his call (i.e., a callback URI, 
> along with some indication of how long the URI will remain valid):
> 
>    <queue target="sip:zachary@example.name">
>      <user name="Bob Smith"
>            uri="sip:bob@example.com"
>            position="1"
>            state="active"
>              
> callback="sip:86dacaff-e941-4fb1-86d6-1ef8adee4658@example.name"
>            expires="60" />
>    </queue>
> 
> 
> Dave has apparently unsubscribed from the state. The queue handler 
> received notification of this fact (via callqueue.winfo), and 
> consequently paused his entry. The queue handler will keep the entry 
> paused until it gets a callqueue.winfo notification that Dave has 
> subscribed again, or until it reaches its administratively-provisioned 
> timeout that sets how long it is willing to hold on to a paused user.
> 
> Charlie has never subscribed to the queue state. The queue handler will 
> either remove his entry after a implementation-specific timeout or when 
> it reaches the top of the queue.
> 
> If Fred (not listed above) attempts to subscribe to the queue state, 
> he'll find out that he's not in the queue because he won't be in the 
> queue...
> 
>    <queue target="sip:zachary@example.name" />
> 
> I think that covers all the vagaries of getting people in and out of the 
> queue, pausing them and unpausing them, and making sure they know 
> whether they'll be notified of their chance to call back in the future.
> 
> Sound reasonable? Any obvious holes?
> 
> /a
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 17:18:36 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc6ge-0006vE-Qy; Thu, 12 Apr 2007 17:18:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc6gd-0006v7-7b
	for sipping@ietf.org; Thu, 12 Apr 2007 17:18:35 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc6gc-0006Zh-0B
	for sipping@ietf.org; Thu, 12 Apr 2007 17:18:35 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 12 Apr 2007 17:18:33 -0400
X-IronPort-AV: i="4.14,405,1170651600"; 
	d="scan'208"; a="118374725:sNHT44767848"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l3CLIXgG014067; 
	Thu, 12 Apr 2007 17:18:33 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3CLIXGd010418; 
	Thu, 12 Apr 2007 21:18:33 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 17:18:33 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 17:18:33 -0400
Message-ID: <461EA227.1080401@cisco.com>
Date: Thu, 12 Apr 2007 17:18:31 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
	<461E810A.2020309@nostrum.com>
In-Reply-To: <461E810A.2020309@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Apr 2007 21:18:33.0160 (UTC)
	FILETIME=[20040480:01C77D48]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=503; t=1176412713;
	x=1177276713; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defen
	se=20of=20Explicit=20Operations |Sender:=20
	|To:=20Adam=20Roach=20<adam@nostrum.com>;
	bh=t4/mdvc+uMCFv2JQKWBwc7HbFEpsgXBNNlYk4IH/tos=;
	b=qZ49KThduPngtvPfiq+5VZSbJd14wIANBEFQplbT8ua6aeckOHRIL3PVll7wLph/9+eARZ9w
	fgBAfHC61q29kMeQjSxwqwi5tm/n8y9d3lEBpplOMszNH44Jqs79F4ly;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: sipping@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Adam Roach wrote:
> Responding to myself *yet* *again*...
> 
> After a few seconds' more thought, I'm not sure this is what we want -- 
> mostly because there's no distinction between "pause my entry in the 
> queue" and "remove my entry from the queue."

Why does it matter? As long as it is paused it won't bother other 
people, and it will eventually age out of the queue. Its no worse that 
the people who are added and have no intention of ever requesting call 
completion.

	Paul

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 17:20:21 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc6iK-00008O-8h; Thu, 12 Apr 2007 17:20:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc6iI-00008J-Fz
	for sipping@ietf.org; Thu, 12 Apr 2007 17:20:18 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc6iH-0007PW-6z
	for sipping@ietf.org; Thu, 12 Apr 2007 17:20:18 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3CLKFrY060880
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 16:20:15 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461EA298.4020704@nostrum.com>
Date: Thu, 12 Apr 2007 16:20:24 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
	<461EA1B6.4010003@cisco.com>
In-Reply-To: <461EA1B6.4010003@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: sipping@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Paul Kyzivat wrote:
> I replied separately before seeing this. My reply describes something 
> pretty much equivalent to this.
>
> One nuance of mine (would work with yours too) is that the <state> can 
> be sufficient to tell the watcher that it is time for it to call

That's what I meant state="active" to mean. The position attribute 
could, indeed, be optional.

     <user name="Bob Smith"
           uri="sip:bob@example.com"
           position="1"
-------->  state="active"
             
callback="sip:86dacaff-e941-4fb1-86d6-1ef8adee4658@example.name"
           expires="60" />

/a


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 17:21:38 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc6jZ-0000it-QN; Thu, 12 Apr 2007 17:21:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc6jY-0000il-TC
	for sipping@ietf.org; Thu, 12 Apr 2007 17:21:36 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc6jX-0007bI-LK
	for sipping@ietf.org; Thu, 12 Apr 2007 17:21:36 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3CLLY1l060944
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 16:21:34 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461EA2E7.3000508@nostrum.com>
Date: Thu, 12 Apr 2007 16:21:43 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
	<461E810A.2020309@nostrum.com> <461EA227.1080401@cisco.com>
In-Reply-To: <461EA227.1080401@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: sipping@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Paul Kyzivat wrote:
>
>
> Adam Roach wrote:
>> Responding to myself *yet* *again*...
>>
>> After a few seconds' more thought, I'm not sure this is what we want 
>> -- mostly because there's no distinction between "pause my entry in 
>> the queue" and "remove my entry from the queue."
>
> Why does it matter? As long as it is paused it won't bother other 
> people, and it will eventually age out of the queue. Its no worse that 
> the people who are added and have no intention of ever requesting call 
> completion.

My concern here is PSTN interop. I believe that you *do* tie up very 
real and limited resources in that case. I could be mistaken.

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 18:32:35 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc7q8-0002A6-J6; Thu, 12 Apr 2007 18:32:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc7q7-00029s-EP
	for sipping@ietf.org; Thu, 12 Apr 2007 18:32:27 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc7q6-00044H-9L
	for sipping@ietf.org; Thu, 12 Apr 2007 18:32:27 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 12 Apr 2007 18:32:21 -0400
X-IronPort-AV: i="4.14,405,1170651600"; 
	d="scan'208"; a="57504286:sNHT46460692"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3CMWKlD030802; 
	Thu, 12 Apr 2007 18:32:20 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3CMWDGd007736; 
	Thu, 12 Apr 2007 22:32:13 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 18:32:13 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 18:32:13 -0400
Message-ID: <461EB36B.2090609@cisco.com>
Date: Thu, 12 Apr 2007 18:32:11 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
	<461E810A.2020309@nostrum.com> <461EA227.1080401@cisco.com>
	<461EA2E7.3000508@nostrum.com>
In-Reply-To: <461EA2E7.3000508@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Apr 2007 22:32:13.0148 (UTC)
	FILETIME=[6A88A9C0:01C77D52]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=988; t=1176417140;
	x=1177281140; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defen
	se=20of=20Explicit=20Operations |Sender:=20
	|To:=20Adam=20Roach=20<adam@nostrum.com>;
	bh=e5xjcg/P3KjhuoPKPONaYd6pvT1h9RSrXXE1FbZT7zI=;
	b=AFZZS3bkbeMK1TEJdlM8idAJE2e5Wy8gRRzfsieC0tq8JbEcoXJHia4Z48dAh8WNMOyS1NTY
	0ZLn7XeNMnLJF9YL+Cb8l027frAZJlzkx0ckcr43fluRbjL2NGd/lqCU;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: sipping@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Adam Roach wrote:
> Paul Kyzivat wrote:
>>
>>
>> Adam Roach wrote:
>>> Responding to myself *yet* *again*...
>>>
>>> After a few seconds' more thought, I'm not sure this is what we want 
>>> -- mostly because there's no distinction between "pause my entry in 
>>> the queue" and "remove my entry from the queue."
>>
>> Why does it matter? As long as it is paused it won't bother other 
>> people, and it will eventually age out of the queue. Its no worse that 
>> the people who are added and have no intention of ever requesting call 
>> completion.
> 
> My concern here is PSTN interop. I believe that you *do* tie up very 
> real and limited resources in that case. I could be mistaken.


Perhaps that is a problem. But if so then I think the whole scheme is 
kaput, since it currently has callers being added with no overt action 
on their part. If we need an overt action to cause addition to the queue 
then we are back to the same old problem.

	Paul

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 18:43:50 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc817-00014Y-8I; Thu, 12 Apr 2007 18:43:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc816-00014T-AA
	for sipping@ietf.org; Thu, 12 Apr 2007 18:43:48 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc814-0007o8-W4
	for sipping@ietf.org; Thu, 12 Apr 2007 18:43:48 -0400
Received: from [64.101.173.120] ([64.101.173.120]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3CLoOxi007266
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 12 Apr 2007 16:50:25 -0500
In-Reply-To: <461E810A.2020309@nostrum.com>
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
	<461E810A.2020309@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E1367ED5-7AEB-4E37-A2D1-5C7D09CE7607@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Thu, 12 Apr 2007 17:43:33 -0500
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Paul Kyzivat <pkyzivat@cisco.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 12, 2007, at 1:57 PM, Adam Roach wrote:

> After a few seconds' more thought, I'm not sure this is what we  
> want -- mostly because there's no distinction between "pause my  
> entry in the queue" and "remove my entry from the queue."

Do we need one?

The question is whether a position in the queue to which no one is  
going to listen is different from not being in the queue at all.

While this is something like "If a tree falls where there is nobody  
to hear, does it still make a sound?", there is one subtle  
difference. The queue state uses up a resource. Is this resource  
costly enough that waiting a reasonable period with no watcher (which  
could be locally tuned) before discarding it would be too expensive?

For example, I might make a DOS attack by enqueueing calls as fast as  
I can send INVITEs.

Of course, a reasonable queue manager could probably defend itself  
from this as well as it could defend itself against an INVITE flood  
DOS, and using the same mechanisms, so why worry?

--
Dean


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 18:53:49 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc8Am-0000YL-Uz; Thu, 12 Apr 2007 18:53:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc8Al-0000Xv-AS
	for sipping@ietf.org; Thu, 12 Apr 2007 18:53:47 -0400
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc8Ak-0002qf-0Y
	for sipping@ietf.org; Thu, 12 Apr 2007 18:53:47 -0400
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l3CMriK6065525
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 17:53:44 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <461EB881.1040605@nostrum.com>
Date: Thu, 12 Apr 2007 17:53:53 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
	<461E810A.2020309@nostrum.com>
	<E1367ED5-7AEB-4E37-A2D1-5C7D09CE7607@softarmor.com>
In-Reply-To: <E1367ED5-7AEB-4E37-A2D1-5C7D09CE7607@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: Paul Kyzivat <pkyzivat@cisco.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dean Willis wrote:
>
> On Apr 12, 2007, at 1:57 PM, Adam Roach wrote:
>
>> After a few seconds' more thought, I'm not sure this is what we want 
>> -- mostly because there's no distinction between "pause my entry in 
>> the queue" and "remove my entry from the queue."
>
> Do we need one?
>
> The question is whether a position in the queue to which no one is 
> going to listen is different from not being in the queue at all.
>
> While this is something like "If a tree falls where there is nobody to 
> hear, does it still make a sound?", there is one subtle difference. 
> The queue state uses up a resource. Is this resource costly enough 
> that waiting a reasonable period with no watcher (which could be 
> locally tuned) before discarding it would be too expensive?
>
> For example, I might make a DOS attack by enqueueing calls as fast as 
> I can send INVITEs.
>
> Of course, a reasonable queue manager could probably defend itself 
> from this as well as it could defend itself against an INVITE flood 
> DOS, and using the same mechanisms, so why worry?


Because there are TCAP operations and PSTN resources tied up for these 
abandoned (but not explicitly deleted) queue positions.

/a

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 19:31:31 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc8lE-0000Hr-4E; Thu, 12 Apr 2007 19:31:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc8lC-0000Hm-Jy
	for sipping@ietf.org; Thu, 12 Apr 2007 19:31:26 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc8lB-0007id-Bt
	for sipping@ietf.org; Thu, 12 Apr 2007 19:31:26 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 12 Apr 2007 19:31:26 -0400
X-IronPort-AV: i="4.14,405,1170651600"; 
	d="scan'208"; a="57510983:sNHT48065544"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l3CNVPEP017110; 
	Thu, 12 Apr 2007 19:31:25 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3CNVKGd027003; 
	Thu, 12 Apr 2007 23:31:20 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 19:31:20 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 19:31:20 -0400
Message-ID: <461EC146.6010606@cisco.com>
Date: Thu, 12 Apr 2007 19:31:18 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
	<461E810A.2020309@nostrum.com> <461EA227.1080401@cisco.com>
	<461EA2E7.3000508@nostrum.com> <461EB36B.2090609@cisco.com>
In-Reply-To: <461EB36B.2090609@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Apr 2007 23:31:20.0319 (UTC)
	FILETIME=[ACD000F0:01C77D5A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1356; t=1176420685;
	x=1177284685; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defen
	se=20of=20Explicit=20Operations |Sender:=20
	|To:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>;
	bh=akcn8bLEhDeiiQkAA7M6la/G2PtusURgCLbNcI+U5jQ=;
	b=MRoqv0eleTOXtollpMeLSrCR4YuP1juNRKldUr9lP9cybC4ghUA7w43xe0LQa5Tdhniv8ctR
	+vofRPknJg6WoFipibgtSc9IQg2gA4K2XyeLqRSm5q+Kp/fZdy+M0L8c;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: sipping@ietf.org, Adam Roach <adam@nostrum.com>,
	Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Replying to myself. :-(

Paul Kyzivat wrote:
> Adam Roach wrote:

>> My concern here is PSTN interop. I believe that you *do* tie up very 
>> real and limited resources in that case. I could be mistaken.
> 
> Perhaps that is a problem. But if so then I think the whole scheme is 
> kaput, since it currently has callers being added with no overt action 
> on their part. If we need an overt action to cause addition to the queue 
> then we are back to the same old problem.

Maybe these aren't the same problem.

One problem is the caller who never subscribes. The other problem is the 
caller who subscribes and then changes his mind wants to be entirely 
dequeued.

If we automatically queue callers whenever their call attempt fails, 
then the the first kind is likely to be a substantially worse problem 
than the second kind. I'd venture a guess that overt cancellations are 
very rare, since it is an extra action that provides no benefit to the 
caller.

In a pure sip environment I don't think we care much about either kind. 
Its the PSTN case that seems a potential problem. When the queue is 
being managed on behalf of a PSTN gateway, it seems like the TCAP action 
could be deferred until a subscription is first received for a queue 
entry. And then I propose that the second problem simply be ignored.

	Paul

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 19:42:55 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc8wG-000687-5l; Thu, 12 Apr 2007 19:42:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc8wE-00067z-Dm
	for sipping@ietf.org; Thu, 12 Apr 2007 19:42:50 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc8wD-00065l-5E
	for sipping@ietf.org; Thu, 12 Apr 2007 19:42:50 -0400
Received: from [64.101.173.120] ([64.101.173.120]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3CMnQVw007484
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 12 Apr 2007 17:49:27 -0500
In-Reply-To: <461EB881.1040605@nostrum.com>
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
	<461E810A.2020309@nostrum.com>
	<E1367ED5-7AEB-4E37-A2D1-5C7D09CE7607@softarmor.com>
	<461EB881.1040605@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5C4EB515-8738-4182-9038-2A9E87FD1D23@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Thu, 12 Apr 2007 18:42:35 -0500
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Paul Kyzivat <pkyzivat@cisco.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 12, 2007, at 5:53 PM, Adam Roach wrote:

> Dean Willis wrote:
>>
>> On Apr 12, 2007, at 1:57 PM, Adam Roach wrote:
>>
>>> After a few seconds' more thought, I'm not sure this is what we  
>>> want -- mostly because there's no distinction between "pause my  
>>> entry in the queue" and "remove my entry from the queue."
>>
>> Do we need one?
>
> Because there are TCAP operations and PSTN resources tied up for  
> these abandoned (but not explicitly deleted) queue positions.
>

I don't see that. The TCAP/PSTN resources don't get pulled back into  
play until the caller reaches the top of the queue.


If you're thinking about a TCAP based WATCHER losing resources, if  
the TCAP side knows that the caller has abandoned, it abandons its  
subscription so the only resource cost is at the queue manager and  
the event server (And possibly depending on filtering, at the other  
watchers).

--
Dean


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 12 20:04:38 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc9HJ-0003dX-4C; Thu, 12 Apr 2007 20:04:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc9HI-0003dS-1A
	for sipping@ietf.org; Thu, 12 Apr 2007 20:04:36 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc9HF-0008KE-Oy
	for sipping@ietf.org; Thu, 12 Apr 2007 20:04:36 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 12 Apr 2007 20:04:34 -0400
X-IronPort-AV: i="4.14,405,1170651600"; 
	d="scan'208"; a="118393615:sNHT52825420"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3D04XZK005370; 
	Thu, 12 Apr 2007 20:04:33 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3D04TGd004915; 
	Fri, 13 Apr 2007 00:04:29 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 20:04:29 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 20:04:28 -0400
Message-ID: <461EC90C.4080709@cisco.com>
Date: Thu, 12 Apr 2007 20:04:28 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
	<461E810A.2020309@nostrum.com>
	<E1367ED5-7AEB-4E37-A2D1-5C7D09CE7607@softarmor.com>
	<461EB881.1040605@nostrum.com>
	<5C4EB515-8738-4182-9038-2A9E87FD1D23@softarmor.com>
In-Reply-To: <5C4EB515-8738-4182-9038-2A9E87FD1D23@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Apr 2007 00:04:28.0978 (UTC)
	FILETIME=[4E254920:01C77D5F]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1294; t=1176422673;
	x=1177286673; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defen
	se=20of=20Explicit=20Operations |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=MWHwMEnBCKFmYXSn9EVOgkWv759hw25uljg0L5x/tfs=;
	b=gZ+9OAktRnJJAWRS5cnKTJPZx+vJCfOx39pGszFBDQGa1vaCr1AEF/Y3u44pNUST5QL5uY4d
	+vJMlDzk8Q3z6OD0dyVDCNGomntiwbsIsJLXn3CjQUI11CQT7FwSPXQS;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: sipping@ietf.org, Adam Roach <adam@nostrum.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Dean Willis wrote:
> 
> On Apr 12, 2007, at 5:53 PM, Adam Roach wrote:
> 
>> Dean Willis wrote:
>>>
>>> On Apr 12, 2007, at 1:57 PM, Adam Roach wrote:
>>>
>>>> After a few seconds' more thought, I'm not sure this is what we want 
>>>> -- mostly because there's no distinction between "pause my entry in 
>>>> the queue" and "remove my entry from the queue."
>>>
>>> Do we need one?
>>
>> Because there are TCAP operations and PSTN resources tied up for these 
>> abandoned (but not explicitly deleted) queue positions.
>>
> 
> I don't see that. The TCAP/PSTN resources don't get pulled back into 
> play until the caller reaches the top of the queue.

I think that if the callee is in the PSTN, and supports the TCAP version 
of this service, then the gateway will need to allow the queuing to use 
the TCAP mechanism and fake it to the sip caller. If the queuing is only 
done on the sip side then it will only be for the sip callers.

	Paul

> If you're thinking about a TCAP based WATCHER losing resources, if the 
> TCAP side knows that the caller has abandoned, it abandons its 
> subscription so the only resource cost is at the queue manager and the 
> event server (And possibly depending on filtering, at the other watchers).
> 
> -- 
> Dean
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 13 00:17:29 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcDDr-0002rr-8c; Fri, 13 Apr 2007 00:17:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcDDp-0002ri-FR
	for sipping@ietf.org; Fri, 13 Apr 2007 00:17:17 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcDDp-0005QT-6J
	for sipping@ietf.org; Fri, 13 Apr 2007 00:17:17 -0400
Received: from [192.168.2.116] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3D3Nt0K008310
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 12 Apr 2007 22:23:56 -0500
Message-ID: <461F0449.4050207@softarmor.com>
Date: Thu, 12 Apr 2007 23:17:13 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
	<461E810A.2020309@nostrum.com>
	<E1367ED5-7AEB-4E37-A2D1-5C7D09CE7607@softarmor.com>
	<461EB881.1040605@nostrum.com>
	<5C4EB515-8738-4182-9038-2A9E87FD1D23@softarmor.com>
	<461EC90C.4080709@cisco.com>
In-Reply-To: <461EC90C.4080709@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: sipping@ietf.org, Adam Roach <adam@nostrum.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


> I think that if the callee is in the PSTN, and supports the TCAP 
> version of this service, then the gateway will need to allow the 
> queuing to use the TCAP mechanism and fake it to the sip caller. If 
> the queuing is only done on the sip side then it will only be for the 
> sip callers.
>
Well, clearly I was thinking of the use case in the other direction.


But then, I don't understand the user experience in the PSTN. If you 
call into a line that is queuing, how do you indicate whether you wish 
to camp on it? Wouldn't exercise of this mechanism determine whether the 
caller was expecting to watch the queue or not?

IIRC correctly, one dials a number, gets a "busy", and then enters a 
digit sequence to activate call-back to that target. This "digit sequence"
 is the analog of  both inserting into the queue AND subscribing to 
notifications on that queue. If it happens, then we allocate resources 
in the PSTN gateway to make it happen. If it doesn't, we don't. So in 
any case, the resources are only allocated when there really is a watcher.

The proposed SIP model breaks the process into two discrete steps -- 1) 
inserting into the queue, and 2) subscribing to events on the queue.

You're positing that if a SIP  to PSTN call completes step 1 but doesn't 
go to step 2 that resources are wasted "watching" the TCAP changes in 
order to send an event that will never be sent. But as we've already 
described, the queue manager is fully able to make some reasonable 
time-out decision, like "It's been ten seconds since I offered callback 
and I haven't had a subscription, so I'll assume this guy wasn't serious 
about callback and drop him".

And in any case, this seems like a good fit for "If it hurts, don't do 
it!". That is, don't engage the resources on the TCP side until both the 
insertion and at least one subscription have occurred.

--
Dean




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 13 03:14:15 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcFyr-0004a7-JV; Fri, 13 Apr 2007 03:14:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcFyp-0004Zw-JZ
	for sipping@ietf.org; Fri, 13 Apr 2007 03:13:59 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcFyn-0008Kd-1G
	for sipping@ietf.org; Fri, 13 Apr 2007 03:13:59 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JGF00HC6DF3W6@siemenscomms.co.uk> for sipping@ietf.org;
	Fri, 13 Apr 2007 08:13:51 +0100 (BST)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VDBQP3>; Fri, 13 Apr 2007 08:13:55 +0100
Content-return: allowed
Date: Fri, 13 Apr 2007 08:13:51 +0100
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: AW: [Sipping] Call Completion: In Defense of Explicit Operati	ons
To: Paul Kyzivat <pkyzivat@cisco.com>, sipping@ietf.org
Message-id: <50B1CBA96870A34799A506B2313F26670B8C2A26@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: Adam Roach <adam@nostrum.com>, Dean Willis <deawilli@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I think this is heading in the right direction. I noted some subsequent
postings discussing matters to do with tying up resources in the PSTN when
interworking, and I think this still needs some attention. For the present,
let's confine ourselves to the case where the callee is in the PSTN and is
busy.

Case 1: The caller never subscribes. I see two solutions. With the first,
the gateway automatically issues a TCAP request for queueing at the same
time as sending the 486 response to the caller. If the gateway does not
receive a SUBSCRIBE request within a certain period it then sends a TCAP
request to cancel queueing. With the second, the gateway starts its own
"queue" but takes no TCAP action. When it detects that there is a watcher
(i.e., the caller has subscribed) it issues a TCAP request for queueing. My
concern with the first one is that the PSTN might issue a charge as soon as
the TCAP request for queueing is received. Perhaps Martin can shed light on
that. This may force us into the second approach.

Case 2. The caller cancels the subscription. This is likely to be relatively
rare, as already noted, because why would the caller bother? But if he does,
then the gateway can either determine that there are no watchers and send a
TCAP request to cancel queueing or can simply take no action. However, see
also case 3.

Case 3. Pause and resume. If the caller just cancels the subscription, the
gateway will have to take account of the fact that this could be due to
either pause or cancel. Therefore on detection of the fact that there is no
longer a watcher it probably has to assume pause and send a TCAP pause
request. On detection of the fact that there is a watcher again later, it
has to send a TCAP resume request.

John

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: 12 April 2007 22:04
> To: sipping@ietf.org
> Cc: Adam Roach; Dean Willis
> Subject: Re: AW: [Sipping] Call Completion: In Defense of 
> Explicit Operations
> 
> My comments below were off the cuff in response to what had 
> been said. 
> But what I ended up at seems like an almost complete and workable 
> approach. So let me try to explain it again directly:
> 
> 1) A calls B.
> 2) B decides to reject the call (say busy)
> 3) B adds the caller A to the call completion queue
> 4) B returns a 486 response with some indication that
>     the caller has been queued (how is TBD)
> 5) if A wants to use the call completion feature,
>     it subscribes to the event package.
> 6) B sends an initial notify, with queue status.
>     Policy most likely limits the information to
>     entries naming the subscriber. (Presumably there
>     is only one.) With the entry is a status, which
>     can be either "waiting" or "selected". Assume it
>     is "waiting" because others are in the queue.
> 7) When B becomes available for a call, it selects the
>     oldest entry in the queue for which there is a watcher.
>     It changes the state of that entry to "selected".
>     As a result of the change, a notification is sent
>     to any watchers that can see the change. That includes
>     at least A.
> 8) Perhaps while that is happening B may receive a call
>     from C. B knows what is going on, notes that the caller
>     is not the selected caller B, and so rejects the call.
>     (Same actions as above.)
> 9) When A receives the notify, it alerts its user. When
>     the user is ready, it places the call to B again.
> 10) When B receives the call from A, it notes it is the
>     selected caller and answers. It also then removes the
>     entry for A from the queue. This results in a notify
>     to A that there is no entry for it in the queue.
> 11) When A receives that notify, it cancels its subscription.
> 
> If, following (4), A had not bothered to subscribe, its entry would 
> remain in the queue for awhile. Entries will age out of the queue 
> eventually.
> 
> If, following (6), enters a state where it won't be able to 
> complete the 
> call to B (e.g. A gets a call from C), then A simply 
> unsubscribes. When 
> A is again ready to try, it again subscribes. (Being 
> subscribed or not 
> is the means of doing suspend and resume.)
> 
> For CCNA (no answer) I think B will have to put the caller into the 
> queue any time a call is abandoned by the caller. I think that is ok.
> 
> 	Paul
> 
> 
> Paul Kyzivat wrote:
> > 
> > 
> > Dean Willis wrote:
> >> Adam Roach wrote:
> >>
> >>>
> >>> _That's_ interesting. I hadn't thought of that. So, 
> instead of using 
> >>> BFCP (as my current proposal suggests), we could use an 
> event package 
> >>> to unobtrusively subscribe to a queue, and XCAP to place 
> ourselves 
> >>> in, pause, resume, and remove ourselves from the queue.
> >>>
> >>> That seems quite reasonable. I'd be interested to see what other 
> >>> people have to say about it.
> >>
> >> I didn't mean to suggest that the caller enqueue 
> themselves with XCAP, 
> >> but that if the queue manager and the event server were on 
> different 
> >> nodes that the queue manager could manipulate the queue 
> state document 
> >> using XCAP.
> >>
> >> I still think that being enqueued as a result of an INVITE is a 
> >> reasonable thing.
> > 
> > Dean,
> > 
> > The ultimate goal seems to be to give the potential caller 
> at the top of 
> > the queue a window of opportunity to attempt a call. During 
> that time, 
> > you don't want to allow the other pending callers, or new 
> callers, to 
> > establish a call to the callee.
> > 
> > But if you enroll everybody that attempts a call, without 
> knowing that 
> > they will use the queue to retry, then you have a problem. 
> You don't 
> > want to give a window of opportunity to someone who isn't waiting.
> > 
> > I guess you could go ahead and enroll the caller of every 
> failed call, 
> > but only give a window of opportunity to a candidate that has been 
> > notified that it is at the head of the queue.
> > 
> > That also suggests a way to handle suspend/resume: to 
> suspend you simply 
> > cancel your subscription. And to resume you make a new subscription.
> > 
> > That seems somewhat interesting. But it presents a new problem - a 
> > subscriber needs to know if they even have an entry in the 
> queue. If you 
> > only get notified when you get to the top, then you could 
> wait forever 
> > if you aren't in the queue.
> > 
> > I guess that could be handled by having an initial 
> notification report 
> > your queue entry even if you are not first - perhaps giving 
> position in 
> > queue. Then a subsequent notifications could be filtered unless the 
> > entry is first in queue, if it is considered undesirable to 
> notify of 
> > every change in position. That would take some peculiar 
> language around 
> > the design of a filter, but seems like it should be possible.
> > 
> >     Paul
> > 
> 
> _______________________________________________
> Sipping mailing list  https://www1.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
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 13 03:50:38 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcGYD-0008Sx-Vk; Fri, 13 Apr 2007 03:50:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcGY8-0008Qn-Nl
	for sipping@ietf.org; Fri, 13 Apr 2007 03:50:28 -0400
Received: from relais-inet-sc.francetelecom.com ([212.234.67.5]
	helo=relais-inet.francetelecom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcGTl-00088d-Qt
	for sipping@ietf.org; Fri, 13 Apr 2007 03:45:59 -0400
Received: from prive-Rline1.com ([192.168.1.12] [192.168.1.12]) by
	Rline1.francetelecom.com with ESMTP; Fri, 13 Apr 2007 09:45:54 +0200
Received: from PMEXCC11.intranet-paris.francetelecom.fr ([10.196.130.4]
	[10.196.130.4]) by Rline1.francetelecom.com with ESMTP;
	Fri, 13 Apr 2007 09:45:54 +0200
Received: from PMEXCB90.intranet-paris.francetelecom.fr ([10.196.130.54]) by
	PMEXCC11.intranet-paris.francetelecom.fr with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 13 Apr 2007 09:45:53 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Fri, 13 Apr 2007 09:45:53 +0200
Message-Id: <406AC648B5523840AE2274F1CBE61FD2512E48@PMEXCB90.intranet-paris.francetelecom.fr>
In-Reply-To: <3999DA03-578D-4B05-9E23-BC6E42B1B97A@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
Thread-Index: Acd9HAthDubKmrSFT5eLnDx5xXMgSgAg4e5Q
From: "GARCIN S=?utf-8?B?w6k=?=bastien AERM"
	<sebastien.garcin@orange-ftgroup.com>
To: "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 13 Apr 2007 07:45:53.0975 (UTC)
	FILETIME=[C3B09470:01C77D9F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: SIPPING WG <sipping@ietf.org>, Adam Roach <adam@nostrum.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


As matter of fact the "bastardized protocol" that we have in mind is "SIP",=
 and I wasn't pretending anything=2E=20

s=E9bastien  =20

-----Message d'origine-----
De : Dean Willis [mailto:dean=2Ewillis@softarmor=2Ecom]=20
Envoy=E9 : jeudi 12 avril 2007 18:02
=C0 : GARCIN S=E9bastien AERM
Cc : Adam Roach; SIPPING WG
Objet : Re: [Sipping] Call Completion: In Defense of Explicit Operations


On Apr 12, 2007, at 10:55 AM, GARCIN S=E9bastien AERM wrote:

>
> A lot of the confusion here comes from the fact that the flows show=20
> "caller" and "callee" exchangin SUB/NOT message whereas the call=20
> completion service transactions we are talking are to take place=20
> between Application Servers serving the caller and callee parties=2E

Don't try and complicate our world by pretending that B2BUAs are anything=
 but UAs=2E

We don't care WHERE your user agent is or what kind of bastardized protocol=
 it uses to present a user=2E From the SIP perspective, it's just a UA=2E

--
Dean


*********************************
This message and any attachments (the "message") are confidential and=
 intended solely for the addressees=2E Any unauthorised
use or dissemination is prohibited=2E
Messages are susceptible to alteration=2E France Telecom Group shall not be=
 liable for the message if altered, changed or
falsified=2E
If you are not the intended addressee of this message, please cancel it=
 immediately and inform the sender=2E
********************************

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 13 07:24:35 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcJtF-0007ro-Tf; Fri, 13 Apr 2007 07:24:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcJtE-0007rh-Jy
	for sipping@ietf.org; Fri, 13 Apr 2007 07:24:28 -0400
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcJtD-0004K0-7a
	for sipping@ietf.org; Fri, 13 Apr 2007 07:24:28 -0400
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de
	[10.125.177.122]) by tcmail21.telekom.de with ESMTP;
	Fri, 13 Apr 2007 13:24:24 +0200
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Apr 2007 13:24:23 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: AW: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Fri, 13 Apr 2007 13:24:23 +0200
Message-Id: <CCA850DCD3FBE2479D5076C5C18732220168AA4F@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B8C2A26@ntht201e.siemenscomms.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Call Completion: In Defense of Explicit Operations
Thread-Index: Acd9m1zPtSGbA+YJQiKZMAVJJO9CDQAH8Opw
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <john.elwell@siemens.com>, <pkyzivat@cisco.com>, <deawilli@cisco.com>,
	<adam@nostrum.com>
X-OriginalArrivalTime: 13 Apr 2007 11:24:23.0880 (UTC)
	FILETIME=[49CD5480:01C77DBE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi all,

thanks for this very productive discussion. Just as a reminder of what =
are the basic requirements for at least TISPAN in this issue: as this =
all shall end up in a feature for user A who encounters a busy user B,=20

- it shall be possible to inform A that he has the possibility to =
receive a notification when he can start a recall (as there could be =
several users which encounter the busy condition at B, of course that =
means that he would be added to a queue, the first user who orders this =
notification should be the first who receives it),=20

- A shall be able to decide if he wants to receive this notification ,

- A shall be informed when it is possible to start a recall (surely one =
but not the only condition for this is that he has reached the top of =
the queue), and

- A shall be able to pause this notifications without loosing his =
position in the queue (he just wouldn't receive a recall notification =
although he might be at the top of the queue, in this case the second =
queue entry would receive a recall notification).

So, this would be what we need.


Regards, Martin


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 13 09:24:42 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcLlU-0001jk-I7; Fri, 13 Apr 2007 09:24:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcLlT-0001iX-JJ
	for sipping@ietf.org; Fri, 13 Apr 2007 09:24:35 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcLlT-0003OG-Aa
	for sipping@ietf.org; Fri, 13 Apr 2007 09:24:35 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 13 Apr 2007 09:24:36 -0400
X-IronPort-AV: i="4.14,408,1170651600"; 
	d="scan'208"; a="57560908:sNHT48699860"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3DDOZ4N031975; 
	Fri, 13 Apr 2007 09:24:35 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l3DDOWlG007862; 
	Fri, 13 Apr 2007 13:24:32 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Apr 2007 09:24:32 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Apr 2007 09:24:32 -0400
Message-ID: <461F848F.80107@cisco.com>
Date: Fri, 13 Apr 2007 09:24:31 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA33@S4DE9JSAAHW.ost.t-com.de>	<461CED8F.60501@cisco.com>	<4F7E1C16-F9BD-46BA-B6A8-678051FD4628@softarmor.com>	<461D28EE.4070904@nostrum.com>	<461E3486.3050906@softarmor.com>	<461E3CE2.7000009@cisco.com>	<32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
	<461E7703.8010709@nostrum.com> <461E8083.2010606@nostrum.com>
	<461E810A.2020309@nostrum.com>
	<E1367ED5-7AEB-4E37-A2D1-5C7D09CE7607@softarmor.com>
	<461EB881.1040605@nostrum.com>
	<5C4EB515-8738-4182-9038-2A9E87FD1D23@softarmor.com>
	<461EC90C.4080709@cisco.com> <461F0449.4050207@softarmor.com>
In-Reply-To: <461F0449.4050207@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Apr 2007 13:24:32.0181 (UTC)
	FILETIME=[1248C650:01C77DCF]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2103; t=1176470675;
	x=1177334675; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defen
	se=20of=20Explicit=20Operations |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=+5NMLCxZA45iwg11/65Z3sVjIWE3Qz00I2dxO9o3P3c=;
	b=I6K04J2APReh5fvrQnn4MA2FVZn6zRaAhAq/fxpYqQqXVmzFK39hxPo8GHbLq1771aGuH0WU
	nQ2A5roDLyOGmXShs5BYERr2Pl2PfRzhIuSBfZwkgZMTtwpL4I5CA+QK;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: sipping@ietf.org, Adam Roach <adam@nostrum.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Dean Willis wrote:
> 
>> I think that if the callee is in the PSTN, and supports the TCAP 
>> version of this service, then the gateway will need to allow the 
>> queuing to use the TCAP mechanism and fake it to the sip caller. If 
>> the queuing is only done on the sip side then it will only be for the 
>> sip callers.
>>
> Well, clearly I was thinking of the use case in the other direction.
> 
> 
> But then, I don't understand the user experience in the PSTN. If you 
> call into a line that is queuing, how do you indicate whether you wish 
> to camp on it? Wouldn't exercise of this mechanism determine whether the 
> caller was expecting to watch the queue or not?
> 
> IIRC correctly, one dials a number, gets a "busy", and then enters a 
> digit sequence to activate call-back to that target. This "digit sequence"
> is the analog of  both inserting into the queue AND subscribing to 
> notifications on that queue.

Yes, that is my understanding too.

> If it happens, then we allocate resources 
> in the PSTN gateway to make it happen. If it doesn't, we don't. So in 
> any case, the resources are only allocated when there really is a watcher.

> The proposed SIP model breaks the process into two discrete steps -- 1) 
> inserting into the queue, and 2) subscribing to events on the queue.
> 
> You're positing that if a SIP  to PSTN call completes step 1 but doesn't 
> go to step 2 that resources are wasted "watching" the TCAP changes in 
> order to send an event that will never be sent. But as we've already 
> described, the queue manager is fully able to make some reasonable 
> time-out decision, like "It's been ten seconds since I offered callback 
> and I haven't had a subscription, so I'll assume this guy wasn't serious 
> about callback and drop him".
> 
> And in any case, this seems like a good fit for "If it hurts, don't do 
> it!". That is, don't engage the resources on the TCP side until both the 
> insertion and at least one subscription have occurred.

I proposed something similar in a separate response.

	Paul

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 13 09:38:50 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcLzE-00020I-BZ; Fri, 13 Apr 2007 09:38:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcLzC-0001zF-U7
	for sipping@ietf.org; Fri, 13 Apr 2007 09:38:46 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcLxM-0008KC-Em
	for sipping@ietf.org; Fri, 13 Apr 2007 09:36:52 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 13 Apr 2007 09:36:47 -0400
X-IronPort-AV: i="4.14,408,1170651600"; 
	d="scan'208"; a="118436699:sNHT1463485730"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3DDal9l005133; 
	Fri, 13 Apr 2007 09:36:47 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3DDaVHH003054; 
	Fri, 13 Apr 2007 13:36:47 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Apr 2007 09:36:46 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Apr 2007 09:36:45 -0400
Message-ID: <461F876E.3040007@cisco.com>
Date: Fri, 13 Apr 2007 09:36:46 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
Subject: Re: AW: [Sipping] Call Completion: In Defense of Explicit Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA4F@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <CCA850DCD3FBE2479D5076C5C18732220168AA4F@S4DE9JSAAHW.ost.t-com.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Apr 2007 13:36:45.0455 (UTC)
	FILETIME=[C75981F0:01C77DD0]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1646; t=1176471407;
	x=1177335407; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In=20Defen
	se=20of=20Explicit=20Operations |Sender:=20
	|To:=20=22Huelsemann,=20Martin=22=20<Martin.Huelsemann@t-com.net>;
	bh=CelMaKr8xE85mNWkrfGWjbNWQZilj21tag5owaHZp7M=;
	b=lUwKYBWfixfABzx9Hq8UAPyecqO2f/7OTwSy9afQsbHyQVP/U/gABSJHgIRTnTQkt8lwZUw2
	y8kdLueIhVUXSt3+94KxaM4Zdbg/6aW1Iw86/hoFioYvGr58wiououPg;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: adam@nostrum.com, sipping@ietf.org, john.elwell@siemens.com,
	deawilli@cisco.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Huelsemann, Martin wrote:
> Hi all,
> 
> thanks for this very productive discussion. Just as a reminder of what are the basic requirements for at least TISPAN in this issue: as this all shall end up in a feature for user A who encounters a busy user B, 
> 
> - it shall be possible to inform A that he has the possibility to receive a notification when he can start a recall (as there could be several users which encounter the busy condition at B, of course that means that he would be added to a queue, the first user who orders this notification should be the first who receives it), 

This still needs some work. The current draft proposes using 
"Allow-Events" for this. That makes sense if the UAS returning this will 
always be the one that services the subscribe. I suspect a reasonable 
case will be where a phone returns the error response but a separate 
server will handle the queue and the subscription. In that case I think 
the use of Allow-Events is debatable.

> - A shall be able to decide if he wants to receive this notification ,
> 
> - A shall be informed when it is possible to start a recall (surely one but not the only condition for this is that he has reached the top of the queue), and
> 
> - A shall be able to pause this notifications without loosing his position in the queue (he just wouldn't receive a recall notification although he might be at the top of the queue, in this case the second queue entry would receive a recall notification).

I think what Adam and I have been converging on addresses the rest.

	Paul

> So, this would be what we need.
> 
> 
> Regards, Martin
> 

_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 13 14:24:00 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcQR8-0007Gn-FO; Fri, 13 Apr 2007 14:23:54 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HcQR7-0007Gi-96 for sipping-confirm+ok@megatron.ietf.org;
	Fri, 13 Apr 2007 14:23:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcQR6-0007Ga-Vu
	for sipping@ietf.org; Fri, 13 Apr 2007 14:23:52 -0400
Received: from web31512.mail.mud.yahoo.com ([68.142.198.141])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HcQR6-00088h-LZ
	for sipping@ietf.org; Fri, 13 Apr 2007 14:23:52 -0400
Received: (qmail 56746 invoked by uid 60001); 13 Apr 2007 18:23:52 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=M4ARbCNMel+skfjcBmJsTMs3PjnPv0CMi1eIqmubbDrN18mx1RXhOcvZqw2jcvtUujekb+9VBq3sVVAG0Hc1THv75CoCVgViFa0V9kOSe9U/DipCK5AOKrFv13YeyYC16Lvv7D/OQar1aJEg96HG8h7sTOV7zvVxuuD0r9rwaIA=;
X-YMail-OSG: x8ayRg8VM1nAHF50AiCsJcZF5RKJo0hmUOJvXuvV3z7g3IHuH1_QA4ry5lxj5QV52ZfSEOBBiHcVz0_OIrQ5m7E8tO_IISUbopQHvVD_W6yKM5sNWvtKzkKSEfWNnQ--
Received: from [198.152.12.67] by web31512.mail.mud.yahoo.com via HTTP;
	Fri, 13 Apr 2007 19:23:51 BST
Date: Fri, 13 Apr 2007 19:23:51 +0100 (BST)
From: Kapil Nayar <kapilnayar@yahoo.com>
Subject: Re: [Sipping] Question on draft-worley-sipping-pickup-03.txt
To: Dale.Worley@comcast.net, sipping@ietf.org
In-Reply-To: <200704112050.l3BKoS1m003679@dragon.ariadne.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <654668.56582.qm@web31512.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Thanks Dale.
The scenario that I was indicating is slightly
different. 

There could be 2 incoming calls on target123 and when
executingset456 tries to do a call pickup, it is
offered both the calls by way of 302-redirection -
multiple contact header. Is it legal?
Now if 456 forks the INVITE (with replaces) to both
the callers, it is likely that both would succeed.
And, if we try to sustain only the first established
dialog, we may end up terminating the other call. It
may be important to implement some level of call
screening either at the Pickup-agent level or
optionally at the 456 level.

It was in this respect that I wanted a pointer to the
Dan Petrie's technique.

thanks,
Kapil

--- Dale.Worley@comcast.net wrote:

>    From: Kapil Nayar <kapilnayar@yahoo.com>
> 
>    In section 9 the draft refers to using 302-Moved
> Temporarily with
>    contact header containing Replaces parameter
> (technique from Dan
>    Petrie). I am looking for further details on this
> technique - in
>    the sense that including multiple contact headers
> with Replaces
>    parameters, exactly how legal it is use this
> technique etc.
> 
> If you have multiple contact headers with Replaces,
> it's processed
> exactly as you'd expect -- the call forks, and the
> first successful
> contact establishes the dialog.
> 
>    In essence can somebody point me to the draft/
> RFC which explains
>    this technique in more detail?
> 
> You know of RFC 3261, of course.  INVITE with
> Replaces is described in
> RFC 3891.  I should probably reference those.
> 
> Dale
> 
> _______________________________________________
> Sipping mailing list 
> https://www1.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
> 



      ___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/ 


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 13 15:50:55 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcRnC-0007fq-8d; Fri, 13 Apr 2007 15:50:46 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HcRmz-0007N9-6g for sipping-confirm+ok@megatron.ietf.org;
	Fri, 13 Apr 2007 15:50:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcRmy-0007Ma-Pm; Fri, 13 Apr 2007 15:50:32 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HcRmy-0005sV-AS; Fri, 13 Apr 2007 15:50:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 42A192ACC9;
	Fri, 13 Apr 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HcRmT-0006t2-Vo; Fri, 13 Apr 2007 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HcRmT-0006t2-Vo@stiedprstage1.ietf.org>
Date: Fri, 13 Apr 2007 15:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-sbc-funcs-02.txt 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: Requirements from SIP (Session Initiation Protocol) Session Border Control Deployments
	Author(s)	: J. Hautakorpi, et al.
	Filename	: draft-ietf-sipping-sbc-funcs-02.txt
	Pages		: 23
	Date		: 2007-4-13
	
This documents describes functions implemented in Session Initiation
   Protocol (SIP) intermediaries known as Session Border Controllers
   (SBCs).  The goal of this document is to describe the commonly
   provided functions of SBCs.  A special focus is given to those
   practices that are viewed to be in conflict with SIP architectural
   principles.  This document also explores the underlying requirements
   of network operators that have led to the use of these functions and
   practices in order to identify protocol requirements and determine
   whether those requirements are satisfied by existing specifications
   or additional standards work is required.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-sbc-funcs-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sipping-sbc-funcs-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-sbc-funcs-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-4-13134056.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-sbc-funcs-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-sbc-funcs-02.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-4-13134056.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--NextPart--





From sipping-bounces@ietf.org Fri Apr 13 18:00:53 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcToy-00082D-Bi; Fri, 13 Apr 2007 18:00:44 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HcTow-0007tP-Mt for sipping-confirm+ok@megatron.ietf.org;
	Fri, 13 Apr 2007 18:00:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcTow-0007rf-Bv
	for sipping@ietf.org; Fri, 13 Apr 2007 18:00:42 -0400
Received: from rwcrmhc11.comcast.net ([204.127.192.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcTov-0003Z3-1o
	for sipping@ietf.org; Fri, 13 Apr 2007 18:00:42 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc11) with ESMTP
	id <20070413220040m11005gl6fe>; Fri, 13 Apr 2007 22:00:40 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l3DM0dLv025002
	for <sipping@ietf.org>; Fri, 13 Apr 2007 18:00:39 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l3DM0chq024998;
	Fri, 13 Apr 2007 18:00:38 -0400
Date: Fri, 13 Apr 2007 18:00:38 -0400
Message-Id: <200704132200.l3DM0chq024998@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <45F6124E.8050900@cisco.com> (jdrosen@cisco.com)
Subject: Re: [Sipping] draft-rajesh-sipping-303-01.txt
References: <EB9237EDF079AA4C9462B2ABC5D571647B5F34F1CD@DF-COLLIE-MSG.exchange.corp.microsoft.com>	<1ECE0EB50388174790F9694F77522CCF0F7995C9@zrc2hxm0.corp.nortel.com>	<76431CABEC5EED489807DB8AEBCCA0BCC1D4D4@sea02-mxc01.citel.com>	<1ECE0EB50388174790F9694F77522CCF0F7EDB68@zrc2hxm0.corp.nortel.com>
	<45F0163E.8070604@cisco.com> <45F6124E.8050900@cisco.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

In regard to draft-rajesh-sipping-303-01, which defines a new 303
response code that requires an upstream proxy to recurse (rather than
simply *permitting* it to recurse):

First, the motivations need to be explained much more thoroughly.
They really are the *essence* of the proposal, so they shouldn't just
be the second and third paragraphs of the Introduction.  (And in the
third paragraph, the motivation is "it is a requirement..." without
any explanation of *why* it is a requirement.  And history provides
many examples of people who thought they had one requirement but
actually had another.)

Second, there seem to be considerable upward-compatibility problems.
Currently, proxies can generally be divided into two classes -- those
than can recurse on 3xx and do, and those that cannot recurse on 3xx
and do not.  The I-D envisions a third class, proxies that can recurse
but due to some policy will not always recurse, but which a UAS can
force to always recurse with 303.  Until proxies of the third class
exist, 303 will cause no new behavior (of the type you are interested
in).

Worse, consider the situation where the UAS wants to redirect the
request to another UAS but in a way that will not reveal the
destination UAS's URI to the UAC (section 1, paragraph 2, sentence 2).
If the upstream proxies do not support 303 and do not recurse, they
will pass the 303 response back to the UAC, violating the privacy
objective -- The mechanism does not fail-safe.  (And it's not clear
that the objective can be achieved at all without a privacy service,
as the UAS will provide a Contact URI that will likely resemble the
Contact in the 303 that we wish to keep private.)

Third, there is too much concern about which proxy is responsible for
the callee domain (and thus is obligated to recurse on the 303).  That
criterion actually isn't definable, given that the call can be
redirected from one AOR to another several times, and each AOR may
have a different domain -- until the call is accepted by a user agent,
the *actual* callee is unknowable by all SIP agents.  The real point
of concern is that the UAS generating the 303 and the upstream proxy
which recurses on it should be within the same administrative domain.
And that concern cuts both ways:

1) It makes this mechanism harder to define, because the real goal is
   to ensure that the 303 does not escape from the administrative
   domain containing the UAS that generated it, and ensuring a
   negative is difficult.

2) Whatever mechanism ensures that the proxy implements the 303
   semantics can be used as easily to ensure that it recurses on all
   3xx responses.

And some editorial suggestions:

Don't say "internally routable", say "not globally routable".  We
assume that it's internally routable, what is interesting is that it's
not globally routable.

There is a reference "(1)" which seems to have little to do with the
bibliography.

The example call flow needs to be reduced to 80 columns.

The terminology should be more consistent.  E.g., one sentence uses
both "UAS" and "server".

A considerable amount of section 2 repeats behavior defined in 3261.
I think that the only addition to 3261 behavior is the assumption that
the UAS desires to enforce recursion at a "near" upstream proxy for
one of the reasons mentioned previously.  That can be said quite
briefly.

Dale


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 13 21:01:45 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcWe1-0008Ei-JS; Fri, 13 Apr 2007 21:01:37 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HcWdy-000892-SS for sipping-confirm+ok@megatron.ietf.org;
	Fri, 13 Apr 2007 21:01:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcWdy-00086Z-Gl; Fri, 13 Apr 2007 21:01:34 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HcWdx-0006xA-Fn; Fri, 13 Apr 2007 21:01:34 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JGG00BG3QT7TK@szxga03-in.huawei.com>; Sat,
	14 Apr 2007 09:00:43 +0800 (CST)
Received: from huawei.com ([172.24.1.6])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JGG008PMQT6OW@szxga03-in.huawei.com>; Sat,
	14 Apr 2007 09:00:43 +0800 (CST)
Received: from jys3105093470ty ([58.61.137.182])
	by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JGG00JDRQT14M@szxml02-in.huawei.com>; Sat,
	14 Apr 2007 09:00:42 +0800 (CST)
Date: Sat, 14 Apr 2007 09:01:28 +0800
From: Linyi Tian <tianlinyi@huawei.com>
To: sipping@ietf.org
Message-id: <019001c77e30$6f3c9600$0364a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/mixed; boundary="Boundary_(ID_hgKrzYg6/SAnx9k0HV0eKA)"
Thread-index: Acd+BRGvg5j3Onq2SFOXOU2/y8iMmwAKt1wA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Cc: xcon@ietf.org
Subject: [Sipping] FYI: I-D
	ACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--Boundary_(ID_hgKrzYg6/SAnx9k0HV0eKA)
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7BIT

Dear all

We just submitted an I-D to IETF regarding conference. Please kindly review and feel free to give us any comments. Thank you in advance. 

Abstract & Requirements Anaylyze
   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.

   some environments have tough requirements regarding conference
   establishment time.  This is true especially when a user wants to
   create a conference in ad hoc manner.  In addition user may only want
   very simple conference information and policy, for example the
   subject and maximum numbers of participants, to be provided for an ad
   hoc conference via only one operation.  In this case they rarely
   desire to manipulate the conference policy during the conference.

   In current art there is no mechanism for new participants to be aware
   of the conference information they are being invited to.  It causes
   difficulty for them to decide whether to accept this invitation which
   may not fall into their interest.

Best Regards,
Linyi

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
Sent: Saturday, April 14, 2007 3:50 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


	Title		: Session Initiation Protocol (SIP) INVITE with Conference Info
	Author(s)	: L. Tian, Q. Sun
	Filename	: draft-linyi-sipping-invite-with-conf-info-00.txt
	Pages		: 24
	Date		: 2007-4-13
	

   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-linyi-sipping-invite-with-conf-info-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-linyi-sipping-invite-with-conf-info-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-linyi-sipping-invite-with-conf-info-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_hgKrzYg6/SAnx9k0HV0eKA)
Content-type: Message/External-body; name=ATT00353.dat
Content-transfer-encoding: 7bit
Content-disposition: attachment; filename=ATT00353.dat

Content-Type: text/plain
Content-ID: <2007-4-13133531.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-linyi-sipping-invite-with-conf-info-00.txt

--Boundary_(ID_hgKrzYg6/SAnx9k0HV0eKA)
Content-type: Message/External-body;
	name=draft-linyi-sipping-invite-with-conf-info-00.txt
Content-transfer-encoding: 7bit
Content-disposition: attachment;
	filename=draft-linyi-sipping-invite-with-conf-info-00.txt

Content-Type: text/plain
Content-ID: <2007-4-13133531.I-D@ietf.org>


--Boundary_(ID_hgKrzYg6/SAnx9k0HV0eKA)
Content-type: text/plain; name=ATT00356.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=ATT00356.txt

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--Boundary_(ID_hgKrzYg6/SAnx9k0HV0eKA)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--Boundary_(ID_hgKrzYg6/SAnx9k0HV0eKA)--





From sipping-bounces@ietf.org Sat Apr 14 12:09:25 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HckoL-0001og-Lx; Sat, 14 Apr 2007 12:09:13 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HckoJ-0001oY-CP for sipping-confirm+ok@megatron.ietf.org;
	Sat, 14 Apr 2007 12:09:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HckoJ-0001oQ-0P; Sat, 14 Apr 2007 12:09:11 -0400
Received: from exprod6og53.obsmtp.com ([64.18.1.187])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HckoI-0004gm-IB; Sat, 14 Apr 2007 12:09:10 -0400
Received: from source ([192.150.20.142]) by exprod6ob53.postini.com
	([64.18.5.12]) with SMTP; Sat, 14 Apr 2007 09:09:00 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l3EG8vSd027210; Sat, 14 Apr 2007 09:08:58 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l3EG8fI9016492; Sat, 14 Apr 2007 09:08:41 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 14 Apr 2007 09:08:56 -0700
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
Subject: RE: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
Date: Sat, 14 Apr 2007 09:07:00 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D226B30AD@namail5.corp.adobe.com>
In-Reply-To: <019001c77e30$6f3c9600$0364a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
Thread-Index: Acd+BRGvg5j3Onq2SFOXOU2/y8iMmwAKt1wAAB9++ZA=
References: <019001c77e30$6f3c9600$0364a8c0@china.huawei.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Linyi Tian" <tianlinyi@huawei.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 14 Apr 2007 16:08:56.0068 (UTC)
	FILETIME=[34083C40:01C77EAF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: xcon@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

How would this compare with providing the conference info and policy
over a web page is now the 'standard procedure'?

Or is the assumption that there is no web and we live in a voice-only
world?

>'some environments have tough requirements regarding conference=20
> establishment time'

Why is this a SIP issue?

What about users having predefined access to their conference service by
IT or by contract and just telling the participants to dial in?

Thanks, Henry

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com]=20
Sent: Friday, April 13, 2007 6:01 PM
To: sipping@ietf.org
Cc: xcon@ietf.org
Subject: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Dear all

We just submitted an I-D to IETF regarding conference. Please kindly
review and feel free to give us any comments. Thank you in advance.=20

Abstract & Requirements Anaylyze
   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.

   some environments have tough requirements regarding conference
   establishment time.  This is true especially when a user wants to
   create a conference in ad hoc manner.  In addition user may only want
   very simple conference information and policy, for example the
   subject and maximum numbers of participants, to be provided for an ad
   hoc conference via only one operation.  In this case they rarely
   desire to manipulate the conference policy during the conference.

   In current art there is no mechanism for new participants to be aware
   of the conference information they are being invited to.  It causes
   difficulty for them to decide whether to accept this invitation which
   may not fall into their interest.

Best Regards,
Linyi

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
Sent: Saturday, April 14, 2007 3:50 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts=20
directories.


	Title		: Session Initiation Protocol (SIP) INVITE with
Conference Info
	Author(s)	: L. Tian, Q. Sun
	Filename	:
draft-linyi-sipping-invite-with-conf-info-00.txt
	Pages		: 24
	Date		: 2007-4-13
=09

   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-linyi-sipping-invite-with-conf
-info-00.txt

To remove yourself from the I-D Announcement list, send a message to=20
i-d-announce-request@ietf.org with the word unsubscribe in the body of=20
the message.=20
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the=20
username "anonymous" and a password of your e-mail address. After=20
logging in, type "cd internet-drafts" and then=20
"get draft-linyi-sipping-invite-with-conf-info-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE
/internet-drafts/draft-linyi-sipping-invite-with-conf-info-00.txt".
=09
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 15 01:05:04 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hcwuu-0004Fk-BH; Sun, 15 Apr 2007 01:04:48 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hcwus-0004Fe-VP for sipping-confirm+ok@megatron.ietf.org;
	Sun, 15 Apr 2007 01:04:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hcwus-0004FW-LQ
	for sipping@ietf.org; Sun, 15 Apr 2007 01:04:46 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hcwus-0006YJ-AA
	for sipping@ietf.org; Sun, 15 Apr 2007 01:04:46 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-5.cisco.com with ESMTP; 14 Apr 2007 22:04:46 -0700
X-IronPort-AV: i="4.14,411,1170662400"; 
	d="scan'208"; a="411574637:sNHT49994710"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l3F54jtw026343; 
	Sat, 14 Apr 2007 22:04:45 -0700
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with SMTP id l3F54hwo022392;
	Sun, 15 Apr 2007 05:04:43 GMT
In-Reply-To: <4613BFD4.9090107@bell-labs.com>
References: <4613BFD4.9090107@bell-labs.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B02B0F6A-A2A8-4929-8623-5902DA5F24CF@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sipping] Conclusion for merging
Date: Sat, 14 Apr 2007 22:04:14 -0700
To: Volker Hilt <volkerh@bell-labs.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2775; t=1176613485;
	x=1177477485; c=relaxed/simple; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Conclusion=20for=20merging
	|Sender:=20; bh=KtXz3MkDQiaNMq1BHaQt13rLJmljGj3uM27xW6CljwE=;
	b=QV2f8XKVsCle0NP3azVpb98He8NtgWeQQATov1B2CAGWmlWL5QWH7NYqrlAoO/t880mSzGpz
	Ow7RxAjpqsQIQunTmcycCVa+Noggg+yaiih5lvJ12PqZvw7tFoYn4V2p;
Authentication-Results: sj-dkim-8; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim8002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: Martin C Dolly <mdolly@att.com>, sipping <sipping@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


There is a third option which I have always been a fan of - basically  
do 1 below but then in the places where you do want two things, lets  
say, both local and network can set a max_bandwidth, well you have  
two things one call local_max_bandwidth and one called  
network_max_bandwidth. They are both separate fields and the  
application knows what to do with them.

This approach seems simple to understand, specify, and implement and  
even with the limitations of this approach, it is still easy to meet  
all the use cases people have proposed.

Cullen <with my individual hat on>

On Apr 4, 2007, at 8:10 AM, Volker Hilt wrote:

> One of the remaining issues for config and policy data sets is  
> whether merging of data sets is needed or not.
>
> A UA can receive data sets from multiple different sources (local  
> network provider, device provider and SIP service provider) and  
> needs to combine these sets into a single data set it can work  
> with. In principle, the following strategies exist for enable this:
>
> 1. For each property, define exactly one source that can set this  
> property. For example, define that codec usage can only be set by  
> the local network provider.
> -> It seems impossible to assign each property to exactly one  
> source. For example, if codec usage is assigned to the local  
> network provider, it can never be part of the user profile.
>
> 2. Define an order of precedence between sources so that, for  
> example, local profile overrides user profile and user profile  
> overrides device profile.
> -> This also does not seem to be practical. For example, a single  
> codec setting in the local profile would override all codec  
> settings in the user profile. Thus, the effects of the user profile  
> would depend on whether or not there is a local profile.
>
> 3. Define rules for each property that specify how data from  
> different sources is merged. Ideally, there are a small number of  
> common rules that can be referred to for each property. Examples:  
> use the lowest number for the allowed bandwidth, disable codecs if  
> they are disallowed in a data set.
> -> This approach seems feasible, however, it requires the  
> implementation of multiple merging rules.
>
> The current drafts uses option 3. Are there any concerns, comments,  
> thoughts on using this approach? Are we missing something?
>
> Thanks!
>
> Volker
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 15 10:11:39 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hd5Rx-00049b-RQ; Sun, 15 Apr 2007 10:11:29 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hd5Rv-00049P-Hb for sipping-confirm+ok@megatron.ietf.org;
	Sun, 15 Apr 2007 10:11:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hd5Rv-00049H-82
	for sipping@ietf.org; Sun, 15 Apr 2007 10:11:27 -0400
Received: from serrano.cc.columbia.edu ([128.59.29.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hd5Rt-0005oB-UT
	for sipping@ietf.org; Sun, 15 Apr 2007 10:11:27 -0400
Received: from [192.168.0.41] (pool-70-21-193-163.nwrk.east.verizon.net
	[70.21.193.163]) (user=hgs10 mech=PLAIN bits=0)
	by serrano.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id l3FEB0t4007654
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sun, 15 Apr 2007 10:11:05 -0400 (EDT)
In-Reply-To: <B02B0F6A-A2A8-4929-8623-5902DA5F24CF@cisco.com>
References: <4613BFD4.9090107@bell-labs.com>
	<B02B0F6A-A2A8-4929-8623-5902DA5F24CF@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BD4376EB-403C-4988-B6AA-1BADA9380EF3@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Conclusion for merging
Date: Sun, 15 Apr 2007 10:10:57 -0400
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.6
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: Volker Hilt <volkerh@bell-labs.com>, sipping <sipping@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	Martin C Dolly <mdolly@att.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 15, 2007, at 1:04 AM, Cullen Jennings wrote:

>
> There is a third option which I have always been a fan of -  
> basically do 1 below but then in the places where you do want two  
> things, lets say, both local and network can set a max_bandwidth,  
> well you have two things one call local_max_bandwidth and one  
> called network_max_bandwidth. They are both separate fields and the  
> application knows what to do with them.

Since the application has to obey a single bandwidth limit, the  
application still has to decide that either local_max_bandwidth  
overrides network_max_bandwidth or the result is min(local_,  
network_). If you want predictable behavior, you presumably need to  
standardize which it is.

Thus, I don't see how this addresses the problem at hand.


>
> This approach seems simple to understand, specify, and implement  
> and even with the limitations of this approach, it is still easy to  
> meet all the use cases people have proposed.
>
> Cullen <with my individual hat on>
>
> On Apr 4, 2007, at 8:10 AM, Volker Hilt wrote:
>
>> One of the remaining issues for config and policy data sets is  
>> whether merging of data sets is needed or not.
>>
>> A UA can receive data sets from multiple different sources (local  
>> network provider, device provider and SIP service provider) and  
>> needs to combine these sets into a single data set it can work  
>> with. In principle, the following strategies exist for enable this:
>>
>> 1. For each property, define exactly one source that can set this  
>> property. For example, define that codec usage can only be set by  
>> the local network provider.
>> -> It seems impossible to assign each property to exactly one  
>> source. For example, if codec usage is assigned to the local  
>> network provider, it can never be part of the user profile.
>>
>> 2. Define an order of precedence between sources so that, for  
>> example, local profile overrides user profile and user profile  
>> overrides device profile.
>> -> This also does not seem to be practical. For example, a single  
>> codec setting in the local profile would override all codec  
>> settings in the user profile. Thus, the effects of the user  
>> profile would depend on whether or not there is a local profile.
>>
>> 3. Define rules for each property that specify how data from  
>> different sources is merged. Ideally, there are a small number of  
>> common rules that can be referred to for each property. Examples:  
>> use the lowest number for the allowed bandwidth, disable codecs if  
>> they are disallowed in a data set.
>> -> This approach seems feasible, however, it requires the  
>> implementation of multiple merging rules.
>>
>> The current drafts uses option 3. Are there any concerns,  
>> comments, thoughts on using this approach? Are we missing something?
>>
>> Thanks!
>>
>> Volker
>>
>>
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.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
>
>
> _______________________________________________
> Sipping mailing list  https://www1.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



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 15 10:19:07 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hd5ZK-0007Ww-Q6; Sun, 15 Apr 2007 10:19:06 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hd5ZJ-0007Wr-6q for sipping-confirm+ok@megatron.ietf.org;
	Sun, 15 Apr 2007 10:19:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hd5ZI-0007Wj-Td
	for sipping@ietf.org; Sun, 15 Apr 2007 10:19:04 -0400
Received: from exprod6og55.obsmtp.com ([64.18.1.191])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hd5ZI-0007zz-GV
	for sipping@ietf.org; Sun, 15 Apr 2007 10:19:04 -0400
Received: from source ([192.150.20.142]) by exprod6ob55.postini.com
	([64.18.5.12]) with SMTP; Sun, 15 Apr 2007 07:19:02 PDT
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	l3FEIuSd026869; Sun, 15 Apr 2007 07:19:00 -0700 (PDT)
Received: from fe2.corp.adobe.com (fe2.corp.adobe.com [10.8.192.72])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	l3FEIf0e019362; Sun, 15 Apr 2007 07:18:46 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe2.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 15 Apr 2007 07:18:41 -0700
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
Subject: RE: [Sipping] Conclusion for merging
Date: Sun, 15 Apr 2007 07:18:09 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D226B30C6@namail5.corp.adobe.com>
In-Reply-To: <B02B0F6A-A2A8-4929-8623-5902DA5F24CF@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Conclusion for merging
Thread-Index: Acd/G6feHjVldwl6TaOOxGQDzz5TCgAS1Rog
References: <4613BFD4.9090107@bell-labs.com>
	<B02B0F6A-A2A8-4929-8623-5902DA5F24CF@cisco.com>
From: "Henry Sinnreich" <hsinnrei@adobe.com>
To: "Volker Hilt" <volkerh@bell-labs.com>
X-OriginalArrivalTime: 15 Apr 2007 14:18:41.0611 (UTC)
	FILETIME=[F7EBF1B0:01C77F68]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Depending on the application, there are several generic criteria, such
as:

- Bandwidth,
- Latency,
- Number of IP routing hops (less chance for sudden non-transitivity and
routing flaps).

A network distance metric based on the above provides more flexibility
to the application. Some usage scenarios would be helpful here: Do I use
video or voice only, other apps beside voice? What about a conference or
chat room with widely distributed members?

Such choices should be left IMHO to the application in the endpoints and
just define the metrics. So don't standardize the choice, just provide
information to developers about the best way to use the metrics.

Henry


On Apr 4, 2007, at 8:10 AM, Volker Hilt wrote:

> One of the remaining issues for config and policy data sets is =20
> whether merging of data sets is needed or not.
>
> A UA can receive data sets from multiple different sources (local =20
> network provider, device provider and SIP service provider) and =20
> needs to combine these sets into a single data set it can work =20
> with. In principle, the following strategies exist for enable this:
>
> 1. For each property, define exactly one source that can set this =20
> property. For example, define that codec usage can only be set by =20
> the local network provider.
> -> It seems impossible to assign each property to exactly one =20
> source. For example, if codec usage is assigned to the local =20
> network provider, it can never be part of the user profile.
>
> 2. Define an order of precedence between sources so that, for =20
> example, local profile overrides user profile and user profile =20
> overrides device profile.
> -> This also does not seem to be practical. For example, a single =20
> codec setting in the local profile would override all codec =20
> settings in the user profile. Thus, the effects of the user profile =20
> would depend on whether or not there is a local profile.
>
> 3. Define rules for each property that specify how data from =20
> different sources is merged. Ideally, there are a small number of =20
> common rules that can be referred to for each property. Examples: =20
> use the lowest number for the allowed bandwidth, disable codecs if =20
> they are disallowed in a data set.
> -> This approach seems feasible, however, it requires the =20
> implementation of multiple merging rules.
>
> The current drafts uses option 3. Are there any concerns, comments, =20
> thoughts on using this approach? Are we missing something?
>
> Thanks!
>
> Volker
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 16 14:54:58 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdWLg-0000lb-VC; Mon, 16 Apr 2007 14:54:48 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HdWLg-0000lT-9Q for sipping-confirm+ok@megatron.ietf.org;
	Mon, 16 Apr 2007 14:54:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdWLf-0000lL-W4; Mon, 16 Apr 2007 14:54:47 -0400
Received: from lhrga01-in.huawei.com ([195.33.106.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HdWLf-0004HJ-9P; Mon, 16 Apr 2007 14:54:47 -0400
Received: from huawei.com (lhrml01-in [172.18.7.5])
	by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JGL00KA0TVWRK@lhrga01-in.huawei.com>; Mon,
	16 Apr 2007 19:55:09 +0100 (BST)
Received: from jys3105093470ty ([62.159.183.141])
	by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JGL00INLTVSKM@lhrga01-in.huawei.com>; Mon,
	16 Apr 2007 19:55:08 +0100 (BST)
Date: Mon, 16 Apr 2007 20:55:27 +0300
From: Linyi Tian <tianlinyi@huawei.com>
Subject: RE: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
In-reply-to: <24CCCC428EFEA2469BF046DB3C7A8D226B30AD@namail5.corp.adobe.com>
To: 'Henry Sinnreich' <hsinnrei@adobe.com>, sipping@ietf.org
Message-id: <000501c78050$6c5de3e0$8b010a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7BIT
Thread-index: Acd+BRGvg5j3Onq2SFOXOU2/y8iMmwAKt1wAAB9++ZAAaEZKIA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: xcon@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dear Henry

Thank you very much for your comments. Some responses below:
In the mobile environment user may not desire to access the web site to create conf info for a conference especially when it is in ad hoc manner. So the assumption is that it is boring for user to create an ad hoc conference using two operations. 

This draft respects the same consideration like 'some environments have tough requirements regarding conference establishment time' in another I-D for uri list conferencing. In case of user only wants very simple conference information and policy, such as subject and maximum numbers of participants, to be provided for an ad hoc conference via only one operation. The SIP invite could be used to convey it to create a conference fulfilling this requirement.

Best Regards,
Linyi

-----Original Message-----
From: Henry Sinnreich [mailto:hsinnrei@adobe.com] 
Sent: Saturday, April 14, 2007 7:07 PM
To: Linyi Tian; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [Sipping] FYI: I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

How would this compare with providing the conference info and policy
over a web page is now the 'standard procedure'?

Or is the assumption that there is no web and we live in a voice-only
world?

>'some environments have tough requirements regarding conference 
> establishment time'

Why is this a SIP issue?

What about users having predefined access to their conference service by
IT or by contract and just telling the participants to dial in?

Thanks, Henry

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com] 
Sent: Friday, April 13, 2007 6:01 PM
To: sipping@ietf.org
Cc: xcon@ietf.org
Subject: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Dear all

We just submitted an I-D to IETF regarding conference. Please kindly
review and feel free to give us any comments. Thank you in advance. 

Abstract & Requirements Anaylyze
   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.

   some environments have tough requirements regarding conference
   establishment time.  This is true especially when a user wants to
   create a conference in ad hoc manner.  In addition user may only want
   very simple conference information and policy, for example the
   subject and maximum numbers of participants, to be provided for an ad
   hoc conference via only one operation.  In this case they rarely
   desire to manipulate the conference policy during the conference.

   In current art there is no mechanism for new participants to be aware
   of the conference information they are being invited to.  It causes
   difficulty for them to decide whether to accept this invitation which
   may not fall into their interest.

Best Regards,
Linyi

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
Sent: Saturday, April 14, 2007 3:50 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


	Title		: Session Initiation Protocol (SIP) INVITE with
Conference Info
	Author(s)	: L. Tian, Q. Sun
	Filename	:
draft-linyi-sipping-invite-with-conf-info-00.txt
	Pages		: 24
	Date		: 2007-4-13
	

   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-linyi-sipping-invite-with-conf
-info-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-linyi-sipping-invite-with-conf-info-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE
/internet-drafts/draft-linyi-sipping-invite-with-conf-info-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 16 16:54:45 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdYDY-0001eY-VX; Mon, 16 Apr 2007 16:54:33 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HdYDY-0001eT-Er for sipping-confirm+ok@megatron.ietf.org;
	Mon, 16 Apr 2007 16:54:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HdYDY-0001eL-5S
	for sipping@ietf.org; Mon, 16 Apr 2007 16:54:32 -0400
Received: from rwcrmhc13.comcast.net ([216.148.227.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HdYDV-0002it-TM
	for sipping@ietf.org; Mon, 16 Apr 2007 16:54:32 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc13) with ESMTP
	id <20070416205428m1300358j3e>; Mon, 16 Apr 2007 20:54:28 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l3GKsRLv020654
	for <sipping@ietf.org>; Mon, 16 Apr 2007 16:54:27 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l3GKsR46020650;
	Mon, 16 Apr 2007 16:54:27 -0400
Date: Mon, 16 Apr 2007 16:54:27 -0400
Message-Id: <200704162054.l3GKsR46020650@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <654668.56582.qm@web31512.mail.mud.yahoo.com>
	(kapilnayar@yahoo.com)
Subject: Re: [Sipping] Question on draft-worley-sipping-pickup-03.txt
References: <654668.56582.qm@web31512.mail.mud.yahoo.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: Kapil Nayar <kapilnayar@yahoo.com>

   There could be 2 incoming calls on target123 and when
   executingset456 tries to do a call pickup, it is
   offered both the calls by way of 302-redirection -
   multiple contact header. Is it legal?

It is legal.

   Now if 456 forks the INVITE (with replaces) to both
   the callers, it is likely that both would succeed.
   And, if we try to sustain only the first established
   dialog, we may end up terminating the other call.

Yes, that could happen.

In practice (e.g., in the sipX system), the redirector always picks
one target dialog (usually the one that has been ringing the longest,
with the largest <duration> value), and returns a single Contact.

   It may be important to implement some level of call screening
   either at the Pickup-agent level or optionally at the 456 level.

   It was in this respect that I wanted a pointer to the
   Dan Petrie's technique.

I received the information verbally from Dan Petrie, so there is no
further reference you can follow.

Dale


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 17 08:11:51 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdmX7-00038v-8W; Tue, 17 Apr 2007 08:11:41 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HdmX6-00038E-4u for sipping-confirm+ok@megatron.ietf.org;
	Tue, 17 Apr 2007 08:11:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HdmX5-000384-Kq
	for sipping@ietf.org; Tue, 17 Apr 2007 08:11:39 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HdmX2-00086i-3M
	for sipping@ietf.org; Tue, 17 Apr 2007 08:11:39 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	869C620726
	for <sipping@ietf.org>; Tue, 17 Apr 2007 14:11:35 +0200 (CEST)
X-AuditID: c1b4fb3c-aacefbb0000073d5-c9-4624b977235d 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	73D6C2067A
	for <sipping@ietf.org>; Tue, 17 Apr 2007 14:11:35 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 17 Apr 2007 14:11:35 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 17 Apr 2007 14:11:34 +0200
Message-ID: <CAC481363DB73049924DDDCFC1AC60A6044F8339@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New I-D for P-Served-User header
Thread-Index: AceA6Yq3RmIpuI/NTsW7zPR0z5OMJg==
From: "Hans Erik van Elburg \(RY/ETM\)" <hanserik.van.elburg@ericsson.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 17 Apr 2007 12:11:35.0334 (UTC)
	FILETIME=[8B21EC60:01C780E9]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Subject: [Sipping] New I-D for P-Served-User header
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0852751547=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0852751547==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C780E9.8ABA499C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C780E9.8ABA499C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I uploaded a new draft for the P-Served-User Private-Header, until it
gets available on the online Internet-Drafts directory you can retrieve
it here:
http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user
-00.txt=20

Abstract

   This document specifies the SIP P-Served-User P-header.  This header
   field addresses an issue that was found in the 3rd-Generation
   Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an
   S-CSCF (Serving Call Session Control Function) and an AS (Application
   Server) on the ISC (IMS Subsystem Service Control) interface to
   convey the identity of the served user and the session case that
   applies to this particular communication session and application
   invocation.

Best Regards,

/Hans Erik



------_=_NextPart_001_01C780E9.8ABA499C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>New I-D for P-Served-User header</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#800000" SIZE=3D2 FACE=3D"Arial">I uploaded a new =
draft for the P-Served-User Private-Header, until it gets available on =
the online Internet-Drafts directory you can retrieve it =
here:</FONT></P>

<P><A =
HREF=3D"http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serv=
ed-user-00.txt"><U></U><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://elburg.eln-research.nl/drafts/draft-vanelburg-sippi=
ng-served-user-00.txt</FONT></U></A><FONT SIZE=3D2 FACE=3D"Arial"> =
</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Abstract<BR>
<BR>
&nbsp;&nbsp; This document specifies the SIP P-Served-User =
P-header.&nbsp; This header<BR>
&nbsp;&nbsp; field addresses an issue that was found in the =
3rd-Generation<BR>
&nbsp;&nbsp; Partnership Project (3GPP) IMS (IP Multimedia Subsystem) =
between an<BR>
&nbsp;&nbsp; S-CSCF (Serving Call Session Control Function) and an AS =
(Application<BR>
&nbsp;&nbsp; Server) on the ISC (IMS Subsystem Service Control) =
interface to<BR>
&nbsp;&nbsp; convey the identity of the served user and the session case =
that<BR>
&nbsp;&nbsp; applies to this particular communication session and =
application<BR>
&nbsp;&nbsp; invocation.<BR>
</FONT>

<BR><FONT COLOR=3D"#800000" SIZE=3D2 FACE=3D"Arial">Best Regards,</FONT>
</P>

<P><B><FONT COLOR=3D"#800000" SIZE=3D2 FACE=3D"Arial">/Hans =
Erik</FONT></B>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C780E9.8ABA499C--



--===============0852751547==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0852751547==--





From sipping-bounces@ietf.org Tue Apr 17 09:30:10 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hdnkx-0005xC-9u; Tue, 17 Apr 2007 09:30:03 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hdnkv-0005vg-BC for sipping-confirm+ok@megatron.ietf.org;
	Tue, 17 Apr 2007 09:30:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hdnku-0005sS-Ur
	for sipping@ietf.org; Tue, 17 Apr 2007 09:30:00 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hdnku-0001Ro-Kz
	for sipping@ietf.org; Tue, 17 Apr 2007 09:30:00 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 17 Apr 2007 09:30:00 -0400
X-IronPort-AV: i="4.14,419,1170651600"; 
	d="scan'208"; a="118725089:sNHT65304020"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3HDU0mG002535; 
	Tue, 17 Apr 2007 09:30:00 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l3HDU0lG002480; 
	Tue, 17 Apr 2007 13:30:00 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 17 Apr 2007 09:30:00 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 17 Apr 2007 09:29:59 -0400
Message-ID: <4624CBD5.90106@cisco.com>
Date: Tue, 17 Apr 2007 09:29:57 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Hans Erik van Elburg (RY/ETM)" <hanserik.van.elburg@ericsson.com>
Subject: Re: [Sipping] New I-D for P-Served-User header
References: <CAC481363DB73049924DDDCFC1AC60A6044F8339@esealmw109.eemea.ericsson.se>
In-Reply-To: <CAC481363DB73049924DDDCFC1AC60A6044F8339@esealmw109.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Apr 2007 13:29:59.0815 (UTC)
	FILETIME=[7F38C170:01C780F4]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2226; t=1176816600;
	x=1177680600; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20New=20I-D=20for=20P-Served-User=20header
	|Sender:=20
	|To:=20=22Hans=20Erik=20van=20Elburg=20(RY/ETM)=22=20<hanserik.van.elburg
	@ericsson.com>;
	bh=xL9benfGN+Exe1lasmFaY8dFBmf6YPQzTS4vxoSV/MM=;
	b=P4Vcf7exShDZuZLjpqQ7l0TzihRQ9PSJaGh1zr60UW/a3YLhjEaZgaQpwxOE8MUfnxn3Si7D
	Sg7F3m0sm65bNB/zGTQut3KkkjQYx3UU2uN+lOd4WcPgZ7jJBM251Gli;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Unlike the proposal for the service id, this proposal seems benign. 
(While I could quibble about how things are done in IMS, this sort of 
thing is their business, not ours.)

I would make a small comment about the ABNF: as written the specifically 
defined parameters must appear in a particular order, and prior to any 
extension parameters. That is pretty limiting and contrary to common 
practice. So I would suggest instead making the syntax something like:

P-Served-User            = "P-Served-User" HCOLON PServedUser-value
                                            *(SEMI served-user-param)
served-user-param        = sessioncase-param
                            / registration-state-param
                            / generic-param )
PServedUser-value        = name-addr / addr-spec
sessioncase-param        = "sescase" EQUAL "orig" / "term"
registration-state-param = "regstate" EQUAL "unreg" / "reg"

	Paul


Hans Erik van Elburg (RY/ETM) wrote:
> I uploaded a new draft for the P-Served-User Private-Header, until it 
> gets available on the online Internet-Drafts directory you can retrieve 
> it here:
> 
> ___http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user-00.txt_ 
> 
> 
> Abstract
> 
>    This document specifies the SIP P-Served-User P-header.  This header
>    field addresses an issue that was found in the 3rd-Generation
>    Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an
>    S-CSCF (Serving Call Session Control Function) and an AS (Application
>    Server) on the ISC (IMS Subsystem Service Control) interface to
>    convey the identity of the served user and the session case that
>    applies to this particular communication session and application
>    invocation.
> 
> Best Regards,
> 
> */Hans Erik*
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 17 10:27:28 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdoeV-0006LL-Sj; Tue, 17 Apr 2007 10:27:27 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HdoeV-0006LG-F9 for sipping-confirm+ok@megatron.ietf.org;
	Tue, 17 Apr 2007 10:27:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HdoeV-0006L8-5c
	for sipping@ietf.org; Tue, 17 Apr 2007 10:27:27 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HdoeU-0004Dr-Fj
	for sipping@ietf.org; Tue, 17 Apr 2007 10:27:27 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A42A420454; Tue, 17 Apr 2007 16:27:25 +0200 (CEST)
X-AuditID: c1b4fb3c-a8cebbb0000073d5-e1-4624d94dab85 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	950042061D; Tue, 17 Apr 2007 16:27:25 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 17 Apr 2007 16:27:25 +0200
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
Subject: RE: [Sipping] New I-D for P-Served-User header
Date: Tue, 17 Apr 2007 16:27:24 +0200
Message-ID: <CAC481363DB73049924DDDCFC1AC60A6044F833D@esealmw109.eemea.ericsson.se>
In-Reply-To: <4624CBD5.90106@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] New I-D for P-Served-User header
Thread-Index: AceA9IIEAPjHEkOrQkiHyPrywH2f9QAAc21w
From: "Hans Erik van Elburg \(RY/ETM\)" <hanserik.van.elburg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 17 Apr 2007 14:27:25.0488 (UTC)
	FILETIME=[8500BB00:01C780FC]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Yes I think that is a good suggestion I will take this change in the
next version.
Thanks,
/Hans Erik=20

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
Sent: Tuesday, April 17, 2007 3:30 PM
To: Hans Erik van Elburg (RY/ETM)
Cc: sipping@ietf.org
Subject: Re: [Sipping] New I-D for P-Served-User header

Unlike the proposal for the service id, this proposal seems benign.=20
(While I could quibble about how things are done in IMS, this sort of
thing is their business, not ours.)

I would make a small comment about the ABNF: as written the specifically
defined parameters must appear in a particular order, and prior to any
extension parameters. That is pretty limiting and contrary to common
practice. So I would suggest instead making the syntax something like:

P-Served-User            =3D "P-Served-User" HCOLON PServedUser-value
                                            *(SEMI served-user-param)
served-user-param        =3D sessioncase-param
                            / registration-state-param
                            / generic-param )
PServedUser-value        =3D name-addr / addr-spec
sessioncase-param        =3D "sescase" EQUAL "orig" / "term"
registration-state-param =3D "regstate" EQUAL "unreg" / "reg"

	Paul


Hans Erik van Elburg (RY/ETM) wrote:
> I uploaded a new draft for the P-Served-User Private-Header, until it=20
> gets available on the online Internet-Drafts directory you can=20
> retrieve it here:
>=20
> ___http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served
> -user-00.txt_
>=20
>=20
> Abstract
>=20
>    This document specifies the SIP P-Served-User P-header.  This
header
>    field addresses an issue that was found in the 3rd-Generation
>    Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an
>    S-CSCF (Serving Call Session Control Function) and an AS
(Application
>    Server) on the ISC (IMS Subsystem Service Control) interface to
>    convey the identity of the served user and the session case that
>    applies to this particular communication session and application
>    invocation.
>=20
> Best Regards,
>=20
> */Hans Erik*
>=20
>=20
>=20
> ----------------------------------------------------------------------
> --
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use=20
> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 17 11:12:52 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdpMN-0001g1-75; Tue, 17 Apr 2007 11:12:47 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HdpML-0001fr-4Y for sipping-confirm+ok@megatron.ietf.org;
	Tue, 17 Apr 2007 11:12:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HdpMK-0001fi-R6
	for sipping@ietf.org; Tue, 17 Apr 2007 11:12:44 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HdpMJ-0007PN-6J
	for sipping@ietf.org; Tue, 17 Apr 2007 11:12:44 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 17 Apr 2007 08:12:43 -0700
X-IronPort-AV: i="4.14,419,1170662400"; 
	d="scan'208,217"; a="370211000:sNHT125871446"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3HFCg3i014886; 
	Tue, 17 Apr 2007 08:12:42 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3HFCgMJ029244;
	Tue, 17 Apr 2007 15:12:42 GMT
Received: from xmb-sjc-21e.amer.cisco.com ([171.70.151.156]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 17 Apr 2007 08:12:42 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] New I-D for P-Served-User header
Date: Tue, 17 Apr 2007 08:11:34 -0700
Message-ID: <75B2A84D9323BC4CA3977CF378CE75EB03120489@xmb-sjc-21e.amer.cisco.com>
In-Reply-To: <CAC481363DB73049924DDDCFC1AC60A6044F8339@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] New I-D for P-Served-User header
Thread-Index: AceA6Yq3RmIpuI/NTsW7zPR0z5OMJgAF1f8Q
From: "Arunachalam Venkatraman \(arunvenk\)" <arunvenk@cisco.com>
To: "Hans Erik van Elburg \(RY/ETM\)" <hanserik.van.elburg@ericsson.com>,
	<sipping@ietf.org>
X-OriginalArrivalTime: 17 Apr 2007 15:12:42.0543 (UTC)
	FILETIME=[D87E6BF0:01C78102]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=9229; t=1176822762;
	x=1177686762; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=arunvenk@cisco.com;
	z=From:=20=22Arunachalam=20Venkatraman=20\(arunvenk\)=22=20<arunvenk@cisco
	.com>
	|Subject:=20RE=3A=20[Sipping]=20New=20I-D=20for=20P-Served-User=20header
	|Sender:=20; bh=UVOnB8md2CyAnIDAycQHN0jAbJaDSoxpdDt7HJjn+/g=;
	b=gKG10yQGxvSU4JpdgCNwOxJqr9EOhA8tpkXvoxbcq1Fec5Lp3wmYQWRp+dEFq1K2VwMcWcHz
	7jiwkBAQGkqcmFupBO5dnT/zaKxyvaScLkZW2ffbxRFU7CIBLug+sEptN+m5LBfy+SbwdRlrgM
	1mqlrgeYbobN8D/iagDrpimQs=;
Authentication-Results: sj-dkim-1; header.From=arunvenk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 96d3a783a4707f1ab458eb15058bb2d7
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0620820763=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0620820763==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78102.D84F0EE4"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C78102.D84F0EE4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hans

Will it be correct to assert that there is no requirement to use this
header in the absence of diversion?

The  ServiceInfo in the iFC could convey the session case which, in
turn, implicitly indicate whether the served user is in the PAID or
ReqUri.

Until I read the (very well-written) diversion sections, I was
unconvinced about the need for this header.

=20

Perhaps, you could add a note indicating as much. This will help keep
the message size from becoming larger with redundant information.

=20

Perhaps it may be useful to point out the reg state needs to be sent
only if the AS is not getting triggered out (by an iFC) for REGISTERs.

=20

Regards

Venkat

________________________________

From: Hans Erik van Elburg (RY/ETM)
[mailto:hanserik.van.elburg@ericsson.com]=20
Sent: Tuesday, April 17, 2007 7:12 AM
To: sipping@ietf.org
Subject: [Sipping] New I-D for P-Served-User header

=20

I uploaded a new draft for the P-Served-User Private-Header, until it
gets available on the online Internet-Drafts directory you can retrieve
it here:

http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user
-00.txt
<http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-use
r-00.txt> =20

Abstract

   This document specifies the SIP P-Served-User P-header.  This header
   field addresses an issue that was found in the 3rd-Generation
   Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an
   S-CSCF (Serving Call Session Control Function) and an AS (Application
   Server) on the ISC (IMS Subsystem Service Control) interface to
   convey the identity of the served user and the session case that
   applies to this particular communication session and application
   invocation.

Best Regards,=20

/Hans Erik=20

=20


------_=_NextPart_001_01C78102.D84F0EE4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>New I-D for P-Served-User header</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hans<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Will it be correct to assert that =
there is
no requirement to use this header in the absence of =
diversion?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The &nbsp;ServiceInfo in the iFC =
could
convey the session case which, in turn, implicitly indicate whether the =
served
user is in the PAID or ReqUri.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Until I read the (very =
well-written) diversion
sections, I was unconvinced about the need for this =
header.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Perhaps, you could add a note =
indicating
as much. This will help keep the message size from becoming larger with
redundant information.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Perhaps it may be useful to point =
out the
reg state needs to be sent only if the AS is not getting triggered out =
(by an
iFC) for REGISTERs.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Regards<o:p></o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Venkat<o:p></o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Hans =
Erik van
Elburg (RY/ETM) [mailto:hanserik.van.elburg@ericsson.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 17, =
2007 7:12
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> sipping@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Sipping] New =
I-D for
P-Served-User header</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p><font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:maroon'>I uploaded a new draft for the =
P-Served-User
Private-Header, until it gets available on the online Internet-Drafts =
directory
you can retrieve it here:</span></font><o:p></o:p></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'><a
href=3D"http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serv=
ed-user-00.txt"><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>http://elburg.eln-research.n=
l/drafts/draft-vanelburg-sipping-served-user-00.txt</span></font></a></sp=
an></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> =
</span></font><o:p></o:p></p>

<p><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Abstract<br>
<br>
&nbsp;&nbsp; This document specifies the SIP P-Served-User =
P-header.&nbsp; This
header<br>
&nbsp;&nbsp; field addresses an issue that was found in the =
3rd-Generation<br>
&nbsp;&nbsp; Partnership Project (3GPP) IMS (IP Multimedia Subsystem) =
between
an<br>
&nbsp;&nbsp; S-CSCF (Serving Call Session Control Function) and an AS
(Application<br>
&nbsp;&nbsp; Server) on the ISC (IMS Subsystem Service Control) =
interface to<br>
&nbsp;&nbsp; convey the identity of the served user and the session case =
that<br>
&nbsp;&nbsp; applies to this particular communication session and =
application<br>
&nbsp;&nbsp; invocation.<br>
</span></font><br>
<font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:maroon'>Best Regards,</span></font> <o:p></o:p></p>

<p><b><font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:maroon;font-weight:bold'>/Hans =
Erik</span></font></b> <o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C78102.D84F0EE4--



--===============0620820763==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0620820763==--





From sipping-bounces@ietf.org Tue Apr 17 12:10:10 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdqFr-0005Vs-L0; Tue, 17 Apr 2007 12:10:07 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HdqFp-0005VW-S0 for sipping-confirm+ok@megatron.ietf.org;
	Tue, 17 Apr 2007 12:10:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HdqFp-0005VK-I6
	for sipping@ietf.org; Tue, 17 Apr 2007 12:10:05 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HdqFn-0004Jj-FD
	for sipping@ietf.org; Tue, 17 Apr 2007 12:10:05 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B736D20663; Tue, 17 Apr 2007 18:10:02 +0200 (CEST)
X-AuditID: c1b4fb3c-a9cedbb0000073d5-d1-4624f15ad40d 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	93D0D20558; Tue, 17 Apr 2007 18:10:02 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 17 Apr 2007 18:10:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] New I-D for P-Served-User header
Date: Tue, 17 Apr 2007 18:10:00 +0200
Message-ID: <CAC481363DB73049924DDDCFC1AC60A6044F8340@esealmw109.eemea.ericsson.se>
In-Reply-To: <75B2A84D9323BC4CA3977CF378CE75EB03120489@xmb-sjc-21e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] New I-D for P-Served-User header
Thread-Index: AceA6Yq3RmIpuI/NTsW7zPR0z5OMJgAF1f8QAAFKVnA=
From: "Hans Erik van Elburg \(RY/ETM\)" <hanserik.van.elburg@ericsson.com>
To: "Arunachalam Venkatraman \(arunvenk\)" <arunvenk@cisco.com>
X-OriginalArrivalTime: 17 Apr 2007 16:10:02.0222 (UTC)
	FILETIME=[DAB3C8E0:01C7810A]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79bb66f827e54e9d5c5c7f1f9d645608
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0789860263=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0789860263==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7810A.D9EC77A4"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7810A.D9EC77A4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Venkat,
=20
I think that there are two approaches:
1. Only include it when needed. Leads to slightly smaller messages in
the normal case.
2. Always include it, making the served user determination for the AS a
trivial task. And is a cleaner solution in general.=20
=20
Both approaches have their merits. I prefer to say nothing at all and
let 3GPP decide upon the usage when they design the procedures around
this.
=20
Regarding your last point similar applies, further I am hesitant to
introduce such cross iFC dependencies.
=20
Best Regards,
/Hans Erik

________________________________

From: Arunachalam Venkatraman (arunvenk) [mailto:arunvenk@cisco.com]=20
Sent: Tuesday, April 17, 2007 5:12 PM
To: Hans Erik van Elburg (RY/ETM); sipping@ietf.org
Subject: RE: [Sipping] New I-D for P-Served-User header



Hans

Will it be correct to assert that there is no requirement to use this
header in the absence of diversion?

The  ServiceInfo in the iFC could convey the session case which, in
turn, implicitly indicate whether the served user is in the PAID or
ReqUri.

Until I read the (very well-written) diversion sections, I was
unconvinced about the need for this header.

=20

Perhaps, you could add a note indicating as much. This will help keep
the message size from becoming larger with redundant information.

=20

Perhaps it may be useful to point out the reg state needs to be sent
only if the AS is not getting triggered out (by an iFC) for REGISTERs.

=20

Regards

Venkat

________________________________

From: Hans Erik van Elburg (RY/ETM)
[mailto:hanserik.van.elburg@ericsson.com]=20
Sent: Tuesday, April 17, 2007 7:12 AM
To: sipping@ietf.org
Subject: [Sipping] New I-D for P-Served-User header

=20

I uploaded a new draft for the P-Served-User Private-Header, until it
gets available on the online Internet-Drafts directory you can retrieve
it here:

http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user
-00.txt
<http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-use
r-00.txt> =20

Abstract

   This document specifies the SIP P-Served-User P-header.  This header
   field addresses an issue that was found in the 3rd-Generation
   Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an
   S-CSCF (Serving Call Session Control Function) and an AS (Application
   Server) on the ISC (IMS Subsystem Service Control) interface to
   convey the identity of the served user and the session case that
   applies to this particular communication session and application
   invocation.

Best Regards,=20

/Hans Erik=20

=20


------_=_NextPart_001_01C7810A.D9EC77A4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD><TITLE>New I-D for =
P-Served-User header</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1589" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =
size=3D2>Hi=20
Venkat,</FONT></SPAN></DIV>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =
size=3D2>I=20
think that there&nbsp;are two approaches:</FONT></SPAN></DIV>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =

size=3D2>1.&nbsp;Only include it when needed. Leads to slightly smaller =
messages=20
in the normal case.</FONT></SPAN></DIV>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =
size=3D2>2.=20
Always include it, making the served user determination for the AS a =
trivial=20
task. And is a cleaner solution in general.&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =
size=3D2>Both=20
approaches have their merits. I prefer to say nothing at all and let =
3GPP decide=20
upon the usage when they design the procedures around =
this.</FONT></SPAN></DIV>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =

size=3D2>Regarding your last point similar applies, further I am =
hesitant to=20
introduce such cross iFC dependencies.</FONT></SPAN></DIV>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =
size=3D2>Best=20
Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D547373515-17042007><FONT face=3DArial color=3D#800000 =
size=3D2>/Hans=20
Erik</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Arunachalam Venkatraman =
(arunvenk)=20
[mailto:arunvenk@cisco.com] <BR><B>Sent:</B> Tuesday, April 17, 2007 =
5:12=20
PM<BR><B>To:</B> Hans Erik van Elburg (RY/ETM);=20
sipping@ietf.org<BR><B>Subject:</B> RE: [Sipping] New I-D for =
P-Served-User=20
header<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Hans<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Will it be =
correct to=20
assert that there is no requirement to use this header in the absence of =

diversion?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">The =
&nbsp;ServiceInfo=20
in the iFC could convey the session case which, in turn, implicitly =
indicate=20
whether the served user is in the PAID or =
ReqUri.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Until I read =
the (very=20
well-written) diversion sections, I was unconvinced about the need for =
this=20
header.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Perhaps, you =
could add=20
a note indicating as much. This will help keep the message size from =
becoming=20
larger with redundant information.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Perhaps it =
may be=20
useful to point out the reg state needs to be sent only if the AS is not =
getting=20
triggered out (by an iFC) for REGISTERs.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Regards<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Venkat<o:p></o:p></SPAN></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Hans Erik=20
van Elburg (RY/ETM) [mailto:hanserik.van.elburg@ericsson.com] =
<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, April 17, 2007 =
7:12=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
sipping@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B>=20
[Sipping] New I-D for P-Served-User =
header</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P><FONT face=3DArial color=3Dmaroon size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: Arial">I uploaded =
a new=20
draft for the P-Served-User Private-Header, until it gets available on =
the=20
online Internet-Drafts directory you can retrieve it=20
here:</SPAN></FONT><o:p></o:p></P>
<P><FONT face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"><A=20
href=3D"http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serv=
ed-user-00.txt"><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serve=
d-user-00.txt</SPAN></FONT></A></SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">=20
</SPAN></FONT><o:p></o:p></P>
<P><FONT face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">Abstract<BR><BR>&nbsp;&nbsp;=20
This document specifies the SIP P-Served-User P-header.&nbsp; This=20
header<BR>&nbsp;&nbsp; field addresses an issue that was found in the=20
3rd-Generation<BR>&nbsp;&nbsp; Partnership Project (3GPP) IMS (IP =
Multimedia=20
Subsystem) between an<BR>&nbsp;&nbsp; S-CSCF (Serving Call Session =
Control=20
Function) and an AS (Application<BR>&nbsp;&nbsp; Server) on the ISC (IMS =

Subsystem Service Control) interface to<BR>&nbsp;&nbsp; convey the =
identity of=20
the served user and the session case that<BR>&nbsp;&nbsp; applies to =
this=20
particular communication session and application<BR>&nbsp;&nbsp;=20
invocation.<BR></SPAN></FONT><BR><FONT face=3DArial color=3Dmaroon =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: Arial">Best=20
Regards,</SPAN></FONT> <o:p></o:p></P>
<P><B><FONT face=3DArial color=3Dmaroon size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: =
Arial">/Hans=20
Erik</SPAN></FONT></B> <o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></BODY></HTML>

------_=_NextPart_001_01C7810A.D9EC77A4--



--===============0789860263==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0789860263==--





From sipping-bounces@ietf.org Tue Apr 17 16:19:13 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hdu8p-0005rE-8O; Tue, 17 Apr 2007 16:19:07 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hdu8o-0005r4-EB for sipping-confirm+ok@megatron.ietf.org;
	Tue, 17 Apr 2007 16:19:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hdu8o-0005qs-4S
	for sipping@ietf.org; Tue, 17 Apr 2007 16:19:06 -0400
Received: from rwcrmhc13.comcast.net ([204.127.192.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hdu8m-0002Iq-SB
	for sipping@ietf.org; Tue, 17 Apr 2007 16:19:06 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc13) with ESMTP
	id <20070417201903m13003e2ege>; Tue, 17 Apr 2007 20:19:03 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l3HKJ2c5017084
	for <sipping@ietf.org>; Tue, 17 Apr 2007 16:19:02 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l3HKJ2H0017080;
	Tue, 17 Apr 2007 16:19:02 -0400
Date: Tue, 17 Apr 2007 16:19:02 -0400
Message-Id: <200704172019.l3HKJ2H0017080@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [Sipping] Multiple ways to indicate "the user to whom this service
	applies"
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I'm trying to get caught up on all the traffic, and I'm starting to
get deja vu -- there seem to be no less than 4 proposals for
indicating "the user to whome this service applies".  Two documents
specify this information directly:

- "P-Served-User" in draft-vanelburg-sipping-served-user-00.txt

- RFC 4458 "target" and "cause" parameters to request-URI

And two documents specify this indirectly, by keeping a record of the
last destination "name" via which the request was routed:

- RFC 4244 History-Info header

- "request URN mechanism" in draft-rosenberg-sip-ua-loose-route-00.txt

Do these proposals serve different enough functions that they are all
needed?

Dale


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 18 04:26:58 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1He5V7-0002iC-9f; Wed, 18 Apr 2007 04:26:53 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1He5V5-0002i0-3s for sipping-confirm+ok@megatron.ietf.org;
	Wed, 18 Apr 2007 04:26:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1He5V2-0002hk-5J; Wed, 18 Apr 2007 04:26:48 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1He5Uz-0003pH-79; Wed, 18 Apr 2007 04:26:48 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	859DF21267; Wed, 18 Apr 2007 10:26:44 +0200 (CEST)
X-AuditID: c1b4fb3e-ae1ebbb0000061ca-fe-4625d644634d 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	62EF421133; Wed, 18 Apr 2007 10:26:44 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 18 Apr 2007 10:26:44 +0200
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
Subject: RE: [XCON] RE: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
Date: Wed, 18 Apr 2007 10:26:10 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F039EBE25@esealmw105.eemea.ericsson.se>
In-Reply-To: <000501c78050$6c5de3e0$8b010a0a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [XCON] RE: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
Thread-Index: Acd+BRGvg5j3Onq2SFOXOU2/y8iMmwAKt1wAAB9++ZAAaEZKIABPskUw
References: <24CCCC428EFEA2469BF046DB3C7A8D226B30AD@namail5.corp.adobe.com>
	<000501c78050$6c5de3e0$8b010a0a@china.huawei.com>
From: "Oscar Novo \(JO/LMF\)" <oscar.novo@ericsson.com>
To: "Linyi Tian" <tianlinyi@huawei.com>,
	"Henry Sinnreich" <hsinnrei@adobe.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 18 Apr 2007 08:26:44.0148 (UTC)
	FILETIME=[4C2C0F40:01C78193]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Cc: xcon@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi Linyi,

In the future, XCON WG will work in a protocol to create and manipulate
the conference information in a server. The use of that protocol may be
completely transparent for the mobile users. So, mobile users could
create ad hoc conferences in an easy way.

I think one important use cases to be describe in your draft would be
when the number of URIs in the URI-List exceeds the number specified in
<maximum-user-count> element send by the UAC.

Regards,

Oscar

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com]=20
Sent: 16. huhtikuuta 2007 20:55
To: 'Henry Sinnreich'; sipping@ietf.org
Cc: xcon@ietf.org
Subject: [XCON] RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Dear Henry

Thank you very much for your comments. Some responses below:
In the mobile environment user may not desire to access the web site to
create conf info for a conference especially when it is in ad hoc
manner. So the assumption is that it is boring for user to create an ad
hoc conference using two operations.=20

This draft respects the same consideration like 'some environments have
tough requirements regarding conference establishment time' in another
I-D for uri list conferencing. In case of user only wants very simple
conference information and policy, such as subject and maximum numbers
of participants, to be provided for an ad hoc conference via only one
operation. The SIP invite could be used to convey it to create a
conference fulfilling this requirement.

Best Regards,
Linyi

-----Original Message-----
From: Henry Sinnreich [mailto:hsinnrei@adobe.com]
Sent: Saturday, April 14, 2007 7:07 PM
To: Linyi Tian; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

How would this compare with providing the conference info and policy
over a web page is now the 'standard procedure'?

Or is the assumption that there is no web and we live in a voice-only
world?

>'some environments have tough requirements regarding conference =20
>establishment time'

Why is this a SIP issue?

What about users having predefined access to their conference service by
IT or by contract and just telling the participants to dial in?

Thanks, Henry

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com]
Sent: Friday, April 13, 2007 6:01 PM
To: sipping@ietf.org
Cc: xcon@ietf.org
Subject: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Dear all

We just submitted an I-D to IETF regarding conference. Please kindly
review and feel free to give us any comments. Thank you in advance.=20

Abstract & Requirements Anaylyze
   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.

   some environments have tough requirements regarding conference
   establishment time.  This is true especially when a user wants to
   create a conference in ad hoc manner.  In addition user may only want
   very simple conference information and policy, for example the
   subject and maximum numbers of participants, to be provided for an ad
   hoc conference via only one operation.  In this case they rarely
   desire to manipulate the conference policy during the conference.

   In current art there is no mechanism for new participants to be aware
   of the conference information they are being invited to.  It causes
   difficulty for them to decide whether to accept this invitation which
   may not fall into their interest.

Best Regards,
Linyi

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Saturday, April 14, 2007 3:50 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Session Initiation Protocol (SIP) INVITE with
Conference Info
	Author(s)	: L. Tian, Q. Sun
	Filename	:
draft-linyi-sipping-invite-with-conf-info-00.txt
	Pages		: 24
	Date		: 2007-4-13
=09

   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-linyi-sipping-invite-with-conf
-info-00.txt

To remove yourself from the I-D Announcement list, send a message to=20
i-d-announce-request@ietf.org with the word unsubscribe in the body of=20
the message.=20
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the=20
username "anonymous" and a password of your e-mail address. After=20
logging in, type "cd internet-drafts" and then=20
"get draft-linyi-sipping-invite-with-conf-info-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE
/internet-drafts/draft-linyi-sipping-invite-with-conf-info-00.txt".
=09
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.



_______________________________________________
XCON mailing list
XCON@ietf.org
https://www1.ietf.org/mailman/listinfo/xcon


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 18 04:27:49 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1He5W1-0002yp-LM; Wed, 18 Apr 2007 04:27:49 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hdupo-0006hW-Ms for sipping-confirm+ok@megatron.ietf.org;
	Tue, 17 Apr 2007 17:03:32 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hdupo-0006hO-Dd
	for sipping@ietf.org; Tue, 17 Apr 2007 17:03:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hduol-0006a7-EZ
	for sipping@ietf.org; Tue, 17 Apr 2007 17:02:27 -0400
Received: from omzesmtp04.mci.com ([199.249.17.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hduoj-00007h-07
	for sipping@ietf.org; Tue, 17 Apr 2007 17:02:27 -0400
Received: from dgismtp06.wcomnet.com ([166.38.58.89])
	by firewall.mci.com (Iplanet MTA 5.2)
	with ESMTP id <0JGN00G03UFZWP@firewall.mci.com> for sipping@ietf.org;
	Tue, 17 Apr 2007 21:02:24 +0000 (GMT)
Received: from dgismtp06.wcomnet.com ([127.0.0.1])
	by dgismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with SMTP id <0JGN00C2OUFZ12@dgismtp06.mcilink.com> for
	sipping@ietf.org; Tue, 17 Apr 2007 21:02:23 +0000 (GMT)
Received: from ASHSRV140.mcilink.com ([153.39.68.166])
	by dgismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with ESMTP id <0JGN00B9NUFZOK@dgismtp06.mcilink.com> for
	sipping@ietf.org; Tue, 17 Apr 2007 21:02:23 +0000 (GMT)
Received: from ASHEVS005.mcilink.com ([153.39.69.136])
	by ASHSRV140.mcilink.com with Microsoft SMTPSVC(6.0.3790.1830); Tue,
	17 Apr 2007 21:02:23 +0000
Date: Tue, 17 Apr 2007 21:02:17 +0000
From: "Iliff, Tina" <tina.iliff@verizonbusiness.com>
To: sipping@ietf.org
Message-id: <623C984B2206AC4CAE7CED15174F019D0684D531@ASHEVS005.mcilink.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
Thread-topic: SIP Overload control/mitigation Prototyping/Testing
Thread-index: AceBM65pflFMg3p/QmO+6T9xULLhmw==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-OriginalArrivalTime: 17 Apr 2007 21:02:23.0470 (UTC)
	FILETIME=[B219D0E0:01C78133]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
X-TMDA-Confirmed: Tue, 17 Apr 2007 17:03:32 -0400
X-Mailman-Approved-At: Wed, 18 Apr 2007 04:27:48 -0400
Subject: [Sipping] SIP Overload control/mitigation Prototyping/Testing
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0341087436=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0341087436==
Content-type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78133.B1B02BF5"
Content-class: urn:content-classes:message

This is a multi-part message in MIME format.

------_=_NextPart_001_01C78133.B1B02BF5
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi!  I am aware of two current IETF drafts regarding SIP Overload
Control and Requirements.  Is there any prototyping or testing currently
occurring based on these drafts?

Regards,

Tina Iliff



------_=_NextPart_001_01C78133.B1B02BF5
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>SIP Overload control/mitigation Prototyping/Testing</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT FACE=3D"Arial">Hi!&nbsp; I am aware of two current IETF drafts =
regarding SIP Overload Control and Requirements.&nbsp; Is there any =
prototyping or testing currently occurring based on these =
drafts?</FONT></P>

<P><FONT FACE=3D"Arial">Regards,</FONT>
</P>

<P><FONT FACE=3D"Arial">Tina Iliff</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C78133.B1B02BF5--




--===============0341087436==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0341087436==--






From sipping-bounces@ietf.org Wed Apr 18 09:25:30 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeA9w-0007TR-75; Wed, 18 Apr 2007 09:25:20 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeA9u-0007TM-Ux for sipping-confirm+ok@megatron.ietf.org;
	Wed, 18 Apr 2007 09:25:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeA9u-0007TD-LR
	for sipping@ietf.org; Wed, 18 Apr 2007 09:25:18 -0400
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeA9t-0002ia-Ax
	for sipping@ietf.org; Wed, 18 Apr 2007 09:25:18 -0400
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l3IDPEm00320; Wed, 18 Apr 2007 13:25:14 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] SIP Overload control/mitigation Prototyping/Testing
Date: Wed, 18 Apr 2007 08:25:08 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB16E797A1@zrc2hxm1.corp.nortel.com>
In-Reply-To: <623C984B2206AC4CAE7CED15174F019D0684D531@ASHEVS005.mcilink.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] SIP Overload control/mitigation Prototyping/Testing
Thread-Index: AceBM65pflFMg3p/QmO+6T9xULLhmwAiFNMA
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Iliff, Tina" <tina.iliff@verizonbusiness.com>, <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1932604811=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1932604811==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C781BC.FBCDAB0B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C781BC.FBCDAB0B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Tina,
=20
There is a design team that meets semi-regularly that has been doing
some modeling of the problem.  Jonathan presented the status at IETF-68
- here's a link to the charts:
http://www3.ietf.org/proceedings/07mar/slides/sipping-3/sld1.htm
=20
The requirements document will go through WGLC soon, so any feedback on
that document would be appreciated.  The expectation is to have a more
solid solution document (with a recommended algorithm) available around
the time of the summer meeting in Chicago.
=20
Regards,
Mary=20

	-----Original Message-----
	From: Iliff, Tina [mailto:tina.iliff@verizonbusiness.com]=20
	Sent: Tuesday, April 17, 2007 4:02 PM
	To: sipping@ietf.org
	Subject: [Sipping] SIP Overload control/mitigation
Prototyping/Testing
=09
=09

	Hi!  I am aware of two current IETF drafts regarding SIP
Overload Control and Requirements.  Is there any prototyping or testing
currently occurring based on these drafts?

	Regards,=20

	Tina Iliff=20



------_=_NextPart_001_01C781BC.FBCDAB0B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1589" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614081813-18042007>Hi=20
Tina,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614081813-18042007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614081813-18042007>There=20
is a design team that meets semi-regularly that has been doing some =
modeling of=20
the problem.&nbsp; Jonathan presented the status at IETF-68 - here's a =
link to=20
the charts:&nbsp; <A=20
href=3D"http://www3.ietf.org/proceedings/07mar/slides/sipping-3/sld1.htm"=
>http://www3.ietf.org/proceedings/07mar/slides/sipping-3/sld1.htm</A></SP=
AN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614081813-18042007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614081813-18042007>The=20
requirements document will go through WGLC soon, so any feedback on that =

document would be appreciated.&nbsp; The expectation is to have a more =
solid=20
solution document (with a recommended algorithm) available around the =
time of=20
the summer meeting in Chicago.</SPAN></FONT></DIV>
<DIV><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN lang=3Den-us><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D614081813-18042007>Regards,</SPAN></FONT></SPAN></DIV>
<DIV><SPAN lang=3Den-us><FONT><SPAN =
class=3D614081813-18042007></SPAN><FONT=20
face=3DArial color=3D#0000ff size=3D2>Mary</FONT></FONT></SPAN> </DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Iliff, Tina=20
  [mailto:tina.iliff@verizonbusiness.com] <BR><B>Sent:</B> Tuesday, =
April 17,=20
  2007 4:02 PM<BR><B>To:</B> sipping@ietf.org<BR><B>Subject:</B> =
[Sipping] SIP=20
  Overload control/mitigation =
Prototyping/Testing<BR><BR></FONT></DIV><!-- Converted from text/rtf =
format -->
  <P><FONT face=3DArial>Hi!&nbsp; I am aware of two current IETF drafts =
regarding=20
  SIP Overload Control and Requirements.&nbsp; Is there any prototyping =
or=20
  testing currently occurring based on these drafts?</FONT></P>
  <P><FONT face=3DArial>Regards,</FONT> </P>
  <P><FONT face=3DArial>Tina Iliff</FONT> =
</P><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C781BC.FBCDAB0B--



--===============1932604811==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1932604811==--





From sipping-bounces@ietf.org Wed Apr 18 10:33:34 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeBDv-00028J-CP; Wed, 18 Apr 2007 10:33:31 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeBDu-00028E-Ml for sipping-confirm+ok@megatron.ietf.org;
	Wed, 18 Apr 2007 10:33:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeBDu-000280-DA
	for sipping@ietf.org; Wed, 18 Apr 2007 10:33:30 -0400
Received: from [204.200.195.236] (helo=personeta.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeBDs-0007Av-HW
	for sipping@ietf.org; Wed, 18 Apr 2007 10:33:30 -0400
Received: from adii ([194.90.193.76]) (authenticated bits=0)
	by personeta.com (8.13.6.20060614/8.13.6) with ESMTP id l3IEXB5Z021170; 
	Wed, 18 Apr 2007 14:33:18 GMT
Message-Id: <200704181433.l3IEXB5Z021170@personeta.com>
From: "adi" <adi@personeta.com>
To: "'Hans Erik van Elburg \(RY/ETM\)'" <hanserik.van.elburg@ericsson.com>,
	<sipping@ietf.org>
Subject: RE: [Sipping] New I-D for P-Served-User header
Date: Wed, 18 Apr 2007 17:35:05 +0300
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceA6Yq3RmIpuI/NTsW7zPR0z5OMJgA3O8Ng
In-Reply-To: <CAC481363DB73049924DDDCFC1AC60A6044F8339@esealmw109.eemea.ericsson.se>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ed68cc91cc637fea89623888898579ba
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1279103619=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1279103619==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0248_01C781DF.F024C460"

This is a multi-part message in MIME format.

------=_NextPart_000_0248_01C781DF.F024C460
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In the case of call out of the blue, is the responsibility to add the
P-Served-User is on the AS 

 

Adi 

 

  _____  

From: Hans Erik van Elburg (RY/ETM)
[mailto:hanserik.van.elburg@ericsson.com] 
Sent: Tuesday, April 17, 2007 3:12 PM
To: sipping@ietf.org
Subject: [Sipping] New I-D for P-Served-User header

 

I uploaded a new draft for the P-Served-User Private-Header, until it gets
available on the online Internet-Drafts directory you can retrieve it here:

 
<http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user-00
.txt>
http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user-00.
txt 

Abstract

   This document specifies the SIP P-Served-User P-header.  This header
   field addresses an issue that was found in the 3rd-Generation
   Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an
   S-CSCF (Serving Call Session Control Function) and an AS (Application
   Server) on the ISC (IMS Subsystem Service Control) interface to
   convey the identity of the served user and the session case that
   applies to this particular communication session and application
   invocation.

Best Regards, 

/Hans Erik 

 


------=_NextPart_000_0248_01C781DF.F024C460
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>New I-D for P-Served-User header</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>In the case of call out of the =
blue, is
the responsibility to add the P-Served-User is on the AS =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Adi <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Hans =
Erik van
Elburg (RY/ETM) [mailto:hanserik.van.elburg@ericsson.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 17, =
2007 3:12
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> sipping@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Sipping] New =
I-D for
P-Served-User header</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p><font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:maroon'>I uploaded a new draft for the =
P-Served-User
Private-Header, until it gets available on the online Internet-Drafts =
directory
you can retrieve it here:</span></font><o:p></o:p></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'><a
href=3D"http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serv=
ed-user-00.txt"><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>http://elburg.eln-research.n=
l/drafts/draft-vanelburg-sipping-served-user-00.txt</span></font></a></sp=
an></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> =
</span></font><o:p></o:p></p>

<p><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Abstract<br>
<br>
&nbsp;&nbsp; This document specifies the SIP P-Served-User =
P-header.&nbsp; This
header<br>
&nbsp;&nbsp; field addresses an issue that was found in the =
3rd-Generation<br>
&nbsp;&nbsp; Partnership Project (3GPP) IMS (IP Multimedia Subsystem) =
between
an<br>
&nbsp;&nbsp; S-CSCF (Serving Call Session Control Function) and an AS
(Application<br>
&nbsp;&nbsp; Server) on the ISC (IMS Subsystem Service Control) =
interface to<br>
&nbsp;&nbsp; convey the identity of the served user and the session case =
that<br>
&nbsp;&nbsp; applies to this particular communication session and =
application<br>
&nbsp;&nbsp; invocation.<br>
</span></font><br>
<font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:maroon'>Best Regards,</span></font> <o:p></o:p></p>

<p><b><font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:maroon;font-weight:bold'>/Hans =
Erik</span></font></b> <o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0248_01C781DF.F024C460--




--===============1279103619==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1279103619==--






From sipping-bounces@ietf.org Wed Apr 18 10:38:33 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeBIm-0007BF-Dt; Wed, 18 Apr 2007 10:38:32 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeBIk-0007B6-P2 for sipping-confirm+ok@megatron.ietf.org;
	Wed, 18 Apr 2007 10:38:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeBIk-0007Ay-FV; Wed, 18 Apr 2007 10:38:30 -0400
Received: from lhrga01-in.huawei.com ([195.33.106.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HeBIi-0008DE-Sv; Wed, 18 Apr 2007 10:38:30 -0400
Received: from huawei.com (lhrml01-in [172.18.7.5])
	by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JGP00J0M7CVJI@lhrga01-in.huawei.com>; Wed,
	18 Apr 2007 15:38:55 +0100 (BST)
Received: from jys3105093470ty ([62.159.183.141])
	by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JGP001377CPO4@lhrga01-in.huawei.com>; Wed,
	18 Apr 2007 15:38:55 +0100 (BST)
Date: Wed, 18 Apr 2007 16:39:12 +0300
From: Linyi Tian <tianlinyi@huawei.com>
Subject: RE: [XCON] RE: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
In-reply-to: <A91F30A632473A47B40C18D2B107CA6F039EBE25@esealmw105.eemea.ericsson.se>
To: "'Oscar Novo (JO/LMF)'" <oscar.novo@ericsson.com>,
	'Henry Sinnreich' <hsinnrei@adobe.com>, sipping@ietf.org
Message-id: <006901c781be$f3609170$8b010a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7BIT
Thread-index: Acd+BRGvg5j3Onq2SFOXOU2/y8iMmwAKt1wAAB9++ZAAaEZKIABPskUwAAwdJ/A=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07
Cc: xcon@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi, Oscar

You are very much appreciated for the information and suggestion!

Yes, we are aware of the work ongoing in XCON. However we do not know when this protocol will be completed. There is much work to do with my guess. Maybe somebody can not wait, e.g. OMA is very interested in XCAP solution for pre-defined group communications. For ad-hoc conference, XCAP may not be suitable, but this draft will work well.

In addition to that, there is still no way to provide ad-hoc conference with conference information or policy in OMA. But we see some requirements within some ongoing work in other organizations. This I-D tries to provide the facility. It can be treated as a supplementary solution for existing arts which may particularly address some cases in a simple way.

Regarding maximum counts of participants, actually I have following sentence related in section 5:
The UAC MUST ensure the number of URIs in the URI-List will not exceed the number specified in <maximum-user-count> element if it presents.

Does it satisfy what you need? If not, could you give me some further explanation? If something needs to be changed, I can add them in the next version.

Again, much appreciated for your comments!

Thank you!

Best Regards,
Linyi

-----Original Message-----
From: Oscar Novo (JO/LMF) [mailto:oscar.novo@ericsson.com] 
Sent: Wednesday, April 18, 2007 11:26 AM
To: Linyi Tian; Henry Sinnreich; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [XCON] RE: [Sipping] FYI: I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Hi Linyi,

In the future, XCON WG will work in a protocol to create and manipulate
the conference information in a server. The use of that protocol may be
completely transparent for the mobile users. So, mobile users could
create ad hoc conferences in an easy way.

I think one important use cases to be describe in your draft would be
when the number of URIs in the URI-List exceeds the number specified in
<maximum-user-count> element send by the UAC.

Regards,

Oscar

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com] 
Sent: 16. huhtikuuta 2007 20:55
To: 'Henry Sinnreich'; sipping@ietf.org
Cc: xcon@ietf.org
Subject: [XCON] RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Dear Henry

Thank you very much for your comments. Some responses below:
In the mobile environment user may not desire to access the web site to
create conf info for a conference especially when it is in ad hoc
manner. So the assumption is that it is boring for user to create an ad
hoc conference using two operations. 

This draft respects the same consideration like 'some environments have
tough requirements regarding conference establishment time' in another
I-D for uri list conferencing. In case of user only wants very simple
conference information and policy, such as subject and maximum numbers
of participants, to be provided for an ad hoc conference via only one
operation. The SIP invite could be used to convey it to create a
conference fulfilling this requirement.

Best Regards,
Linyi

-----Original Message-----
From: Henry Sinnreich [mailto:hsinnrei@adobe.com]
Sent: Saturday, April 14, 2007 7:07 PM
To: Linyi Tian; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

How would this compare with providing the conference info and policy
over a web page is now the 'standard procedure'?

Or is the assumption that there is no web and we live in a voice-only
world?

>'some environments have tough requirements regarding conference  
>establishment time'

Why is this a SIP issue?

What about users having predefined access to their conference service by
IT or by contract and just telling the participants to dial in?

Thanks, Henry

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com]
Sent: Friday, April 13, 2007 6:01 PM
To: sipping@ietf.org
Cc: xcon@ietf.org
Subject: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Dear all

We just submitted an I-D to IETF regarding conference. Please kindly
review and feel free to give us any comments. Thank you in advance. 

Abstract & Requirements Anaylyze
   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.

   some environments have tough requirements regarding conference
   establishment time.  This is true especially when a user wants to
   create a conference in ad hoc manner.  In addition user may only want
   very simple conference information and policy, for example the
   subject and maximum numbers of participants, to be provided for an ad
   hoc conference via only one operation.  In this case they rarely
   desire to manipulate the conference policy during the conference.

   In current art there is no mechanism for new participants to be aware
   of the conference information they are being invited to.  It causes
   difficulty for them to decide whether to accept this invitation which
   may not fall into their interest.

Best Regards,
Linyi

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Saturday, April 14, 2007 3:50 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Session Initiation Protocol (SIP) INVITE with
Conference Info
	Author(s)	: L. Tian, Q. Sun
	Filename	:
draft-linyi-sipping-invite-with-conf-info-00.txt
	Pages		: 24
	Date		: 2007-4-13
	

   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-linyi-sipping-invite-with-conf
-info-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-linyi-sipping-invite-with-conf-info-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE
/internet-drafts/draft-linyi-sipping-invite-with-conf-info-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.



_______________________________________________
XCON mailing list
XCON@ietf.org
https://www1.ietf.org/mailman/listinfo/xcon




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 18 11:19:23 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeBwI-00010P-J0; Wed, 18 Apr 2007 11:19:22 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeBwG-0000xl-EJ for sipping-confirm+ok@megatron.ietf.org;
	Wed, 18 Apr 2007 11:19:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeBwG-0000xd-4f
	for sipping@ietf.org; Wed, 18 Apr 2007 11:19:20 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeBwE-0002eO-6w
	for sipping@ietf.org; Wed, 18 Apr 2007 11:19:20 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A1D0120192; Wed, 18 Apr 2007 17:19:17 +0200 (CEST)
X-AuditID: c1b4fb3e-af9eebb0000061ca-7b-462636f54178 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7AF05200A6; Wed, 18 Apr 2007 17:19:17 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 18 Apr 2007 17:19:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] New I-D for P-Served-User header
Date: Wed, 18 Apr 2007 17:19:16 +0200
Message-ID: <CAC481363DB73049924DDDCFC1AC60A6044F8350@esealmw109.eemea.ericsson.se>
In-Reply-To: <200704181433.l3IEXB5Z021170@personeta.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] New I-D for P-Served-User header
Thread-Index: AceA6Yq3RmIpuI/NTsW7zPR0z5OMJgA3O8NgAAGYMaA=
From: "Hans Erik van Elburg \(RY/ETM\)" <hanserik.van.elburg@ericsson.com>
To: "adi" <adi@personeta.com>,
	<sipping@ietf.org>
X-OriginalArrivalTime: 18 Apr 2007 15:19:17.0097 (UTC)
	FILETIME=[EE145590:01C781CC]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ed68cc91cc637fea89623888898579ba
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2050821832=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2050821832==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C781CC.EDBBC778"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C781CC.EDBBC778
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Yes.
/Hans Erik

________________________________

From: adi [mailto:adi@personeta.com]=20
Sent: Wednesday, April 18, 2007 4:35 PM
To: Hans Erik van Elburg (RY/ETM); sipping@ietf.org
Subject: RE: [Sipping] New I-D for P-Served-User header



In the case of call out of the blue, is the responsibility to add the
P-Served-User is on the AS=20

=20

Adi=20

=20

________________________________

From: Hans Erik van Elburg (RY/ETM)
[mailto:hanserik.van.elburg@ericsson.com]=20
Sent: Tuesday, April 17, 2007 3:12 PM
To: sipping@ietf.org
Subject: [Sipping] New I-D for P-Served-User header

=20

I uploaded a new draft for the P-Served-User Private-Header, until it
gets available on the online Internet-Drafts directory you can retrieve
it here:

http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user
-00.txt
<http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-use
r-00.txt> =20

Abstract

   This document specifies the SIP P-Served-User P-header.  This header
   field addresses an issue that was found in the 3rd-Generation
   Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an
   S-CSCF (Serving Call Session Control Function) and an AS (Application
   Server) on the ISC (IMS Subsystem Service Control) interface to
   convey the identity of the served user and the session case that
   applies to this particular communication session and application
   invocation.

Best Regards,=20

/Hans Erik=20

=20


------_=_NextPart_001_01C781CC.EDBBC778
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD><TITLE>New I-D for =
P-Served-User header</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1589" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue>
<DIV><SPAN class=3D336441815-18042007><FONT face=3DArial color=3D#800000 =

size=3D2>Yes.</FONT></SPAN></DIV>
<DIV><SPAN class=3D336441815-18042007><FONT face=3DArial color=3D#800000 =
size=3D2>/Hans=20
Erik</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> adi [mailto:adi@personeta.com] =

<BR><B>Sent:</B> Wednesday, April 18, 2007 4:35 PM<BR><B>To:</B> Hans =
Erik van=20
Elburg (RY/ETM); sipping@ietf.org<BR><B>Subject:</B> RE: [Sipping] New =
I-D for=20
P-Served-User header<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">In the case =
of call out=20
of the blue, is the responsibility to add the P-Served-User is on the AS =

<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Adi=20
<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Hans Erik=20
van Elburg (RY/ETM) [mailto:hanserik.van.elburg@ericsson.com] =
<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, April 17, 2007 =
3:12=20
PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
sipping@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B>=20
[Sipping] New I-D for P-Served-User =
header</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P><FONT face=3DArial color=3Dmaroon size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: Arial">I uploaded =
a new=20
draft for the P-Served-User Private-Header, until it gets available on =
the=20
online Internet-Drafts directory you can retrieve it=20
here:</SPAN></FONT><o:p></o:p></P>
<P><FONT face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"><A=20
href=3D"http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serv=
ed-user-00.txt"><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serve=
d-user-00.txt</SPAN></FONT></A></SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">=20
</SPAN></FONT><o:p></o:p></P>
<P><FONT face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">Abstract<BR><BR>&nbsp;&nbsp;=20
This document specifies the SIP P-Served-User P-header.&nbsp; This=20
header<BR>&nbsp;&nbsp; field addresses an issue that was found in the=20
3rd-Generation<BR>&nbsp;&nbsp; Partnership Project (3GPP) IMS (IP =
Multimedia=20
Subsystem) between an<BR>&nbsp;&nbsp; S-CSCF (Serving Call Session =
Control=20
Function) and an AS (Application<BR>&nbsp;&nbsp; Server) on the ISC (IMS =

Subsystem Service Control) interface to<BR>&nbsp;&nbsp; convey the =
identity of=20
the served user and the session case that<BR>&nbsp;&nbsp; applies to =
this=20
particular communication session and application<BR>&nbsp;&nbsp;=20
invocation.<BR></SPAN></FONT><BR><FONT face=3DArial color=3Dmaroon =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: Arial">Best=20
Regards,</SPAN></FONT> <o:p></o:p></P>
<P><B><FONT face=3DArial color=3Dmaroon size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: =
Arial">/Hans=20
Erik</SPAN></FONT></B> <o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></BODY></HTML>

------_=_NextPart_001_01C781CC.EDBBC778--



--===============2050821832==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============2050821832==--





From sipping-bounces@ietf.org Wed Apr 18 11:55:19 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeCV2-0001qG-I4; Wed, 18 Apr 2007 11:55:16 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeCV1-0001o6-Dk for sipping-confirm+ok@megatron.ietf.org;
	Wed, 18 Apr 2007 11:55:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeCV1-0001ny-46
	for sipping@ietf.org; Wed, 18 Apr 2007 11:55:15 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeCV0-0002Xm-R0
	for sipping@ietf.org; Wed, 18 Apr 2007 11:55:15 -0400
Received: from [206.176.144.212] (rcdn4-dmznat-gw1-nat-27.cisco.com
	[12.5.186.27]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3IF1xwv026610
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 18 Apr 2007 10:02:00 -0500
In-Reply-To: <406AC648B5523840AE2274F1CBE61FD2512E48@PMEXCB90.intranet-paris.francetelecom.fr>
References: <406AC648B5523840AE2274F1CBE61FD2512E48@PMEXCB90.intranet-paris.francetelecom.fr>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <15375C4F-0171-459F-AEAD-5BD0A8391E81@softarmor.com>
Content-Transfer-Encoding: quoted-printable
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Wed, 18 Apr 2007 10:55:12 -0500
To: =?ISO-8859-1?Q?GARCIN_S=E9bastien_AERM?=
	<sebastien.garcin@orange-ftgroup.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: Adam Roach <adam@nostrum.com>, SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 13, 2007, at 2:45 AM, GARCIN S=E9bastien AERM wrote:

>> Don't try and complicate our world by pretending that B2BUAs are =20
>> anything but UAs.
>>
>> We don't care WHERE your user agent is or what kind of bastardized =20=

>> protocol it uses to present a user. =46rom the SIP perspective, it's =20=

>> just a UA.
>
>
> As matter of fact the "bastardized protocol" that we have in mind =20
> is "SIP", and I wasn't pretending anything.

Well, the tone on my post came out all wrong. My apologies.

The point I'm trying to make is that much of the difficulty in =20
understanding POC comes from the idea that the protocol is user-to-=20
user SIP. It isn't. The POC controllers are the UAs. It's SIP (as we =20
know it) from controller to controller.

Instead of:

UA----Proxy----Proxy----UA

we have:

UA--Proxy--UA/UA---Proxy----Proxy-----UA/UA--Proxy--UA

In addition to SIP between the controllers (which possibly transits =20
proxies), there are almost unrelated controller-to-terminal protocols =20=

on each side (which may also transit proxies)

The controller-to-terminal protocol is currently defined in terms of =20
SIP. However, it could be replaced by some entirely different =20
protocol, and neither the controller nor the terminal "on the other =20
side" would be able to tell.

So to understand the environment, one has to be very clearly thinking =20=

about either the terminal-to-controller protocol or about the =20
controller-to-controller protocol. When you're working with the =20
controller-to-controller protocol (as would be the case when one POC =20
controller is queued by another), then it is both irrelevant and =20
confusing to bring "the terminal as a UA" into the discussion.

When I was participating in POC (or helping participants deal with =20
complexities outside of meetings) I frequently had to say something =20
like "Pretend the POC controllers are the final endpoints and that =20
they have microphones, speakers, and a talk button. What has to =20
happen between them for this to work?" This approach as necessitated =20
because people kept getting the dialog state on the controller-=20
terminal link mixed up with the dialog state on the controller-=20
controller link.

The other mistake people frequently made in POC was asserting that =20
the POC controller was somehow "special" and therefore exempt from =20
the rules of SIP processing at a user agent. It isn't -- it is a SIP =20
user agent, and it has to play by all the rules of a SIP user agent =20
or things aren't going to work right.

--
Dean=


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 18 16:21:34 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeGed-0000lq-BD; Wed, 18 Apr 2007 16:21:27 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeGea-0000fu-A1 for sipping-confirm+ok@megatron.ietf.org;
	Wed, 18 Apr 2007 16:21:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeGea-0000fh-0S; Wed, 18 Apr 2007 16:21:24 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HeGeZ-0001KP-M6; Wed, 18 Apr 2007 16:21:23 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id B7BD2329D9;
	Wed, 18 Apr 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HeGAE-0002Ef-K1; Wed, 18 Apr 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HeGAE-0002Ef-K1@stiedprstage1.ietf.org>
Date: Wed, 18 Apr 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-sbc-funcs-03.txt 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: Requirements from SIP (Session Initiation Protocol) Session Border Control Deployments
	Author(s)	: J. Hautakorpi, et al.
	Filename	: draft-ietf-sipping-sbc-funcs-03.txt
	Pages		: 23
	Date		: 2007-4-18
	
This document describes functions implemented in Session Initiation
   Protocol (SIP) intermediaries known as Session Border Controllers
   (SBCs).  The goal of this document is to describe the commonly
   provided functions of SBCs.  A special focus is given to those
   practices that are viewed to be in conflict with SIP architectural
   principles.  This document also explores the underlying requirements
   of network operators that have led to the use of these functions and
   practices in order to identify protocol requirements and determine
   whether those requirements are satisfied by existing specifications
   or additional standards work is required.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-sbc-funcs-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sipping-sbc-funcs-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-sbc-funcs-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-4-18120618.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-sbc-funcs-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-sbc-funcs-03.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-4-18120618.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--NextPart--





From sipping-bounces@ietf.org Thu Apr 19 02:07:20 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HePnP-00038p-8T; Thu, 19 Apr 2007 02:07:07 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HePnN-00038S-Ag for sipping-confirm+ok@megatron.ietf.org;
	Thu, 19 Apr 2007 02:07:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HePnM-00038C-Vv
	for sipping@ietf.org; Thu, 19 Apr 2007 02:07:04 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HePnL-0007I5-1l
	for sipping@ietf.org; Thu, 19 Apr 2007 02:07:04 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	68F4C2147E; Thu, 19 Apr 2007 08:07:02 +0200 (CEST)
X-AuditID: c1b4fb3e-b01efbb0000061ca-2a-46270706077a 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	573D6211A3; Thu, 19 Apr 2007 08:07:02 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Apr 2007 08:07:02 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Apr 2007 08:07:01 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 8B024236C;
	Thu, 19 Apr 2007 09:07:01 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 4C7DF4DBEE;
	Thu, 19 Apr 2007 09:07:01 +0300 (EEST)
Received: from localhost.localdomain (localhost [IPv6:::1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id E3D534DBE9;
	Thu, 19 Apr 2007 09:07:00 +0300 (EEST)
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
To: dan.ietf@sipez.com, sumanth@cablelabs.com
In-Reply-To: <CADF94D1-A6B5-43E4-B097-3CF9F3AA65E2@cs.columbia.edu>
References: <50B1CBA96870A34799A506B2313F26670B712023@ntht201e.siemenscomms.co.uk>
	<CADF94D1-A6B5-43E4-B097-3CF9F3AA65E2@cs.columbia.edu>
Content-Type: text/plain
Date: Thu, 19 Apr 2007 09:07:12 +0300
Message-Id: <1176962832.6769.7.camel@n95.nomadiclab.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-4.fc4) 
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 19 Apr 2007 06:07:01.0875 (UTC)
	FILETIME=[F25C7430:01C78248]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: sipping@ietf.org
Subject: [Sipping] config framework: device id
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi,

the draft states that a device identifier "should be based on MAC
address or UUID". 
I was wondering why don't include also IMEI (International Mobile
Equipment Identity) or at least mention it as a possible alternate
representation auto-generated by devices.  

thanks
Sal



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 19 05:06:01 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeSaL-00015Y-Ld; Thu, 19 Apr 2007 05:05:49 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeSaJ-00015Q-U7 for sipping-confirm+ok@megatron.ietf.org;
	Thu, 19 Apr 2007 05:05:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeSaJ-00015I-Es; Thu, 19 Apr 2007 05:05:47 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HeSaI-00082A-Pb; Thu, 19 Apr 2007 05:05:47 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
Subject: RE: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
MIME-Version: 1.0
Date: Thu, 19 Apr 2007 12:06:00 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C047C20EF@IsrExch01.israel.polycom.com>
In-Reply-To: <019001c77e30$6f3c9600$0364a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
Thread-Index: Acd+BRGvg5j3Onq2SFOXOU2/y8iMmwAKt1wAAQfxWcA=
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Linyi Tian" <tianlinyi@huawei.com>,
	<sipping@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: xcon@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0240738072=="
Errors-To: sipping-bounces@ietf.org

--===============0240738072==
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

TGlueWksDQoNCkkgcmVhZCB0aGUgZHJhZnQgYW5kIGhhdmUgc29tZSBjb21tZW50cyBhYm91dCB0
aGlzIGRpcmVjdGlvbi4NCg0KDQoxLiBJdCBpcyBhbiBhZHZhbnRhZ2UgaW4gbGV0dGluZyB0aGUg
aW52aXRlZSBrbm93IHRoZSBzdWJqZWN0IG9mIHRoZSBjb25mZXJlbmNlIGJ1dCB0aGlzIGlzIHRy
dWUgYWxzbyBmb3IgYSBwb2ludCB0byBwb2ludCBjYWxsLiBUaGlzIGlzIG5vdCB1bmlxdWUgdG8g
Y29uZmVyZW5jZS4NCg0KMi4gbGV0dGluZyB0aGUgaW52aXRlZSBrbm93IHdobyB0aGUgb3RoZXIg
cGFydGljaXBhbnRzIGluIHRoZSBjb25mZXJlbmNlIGFuZCB0aGUgY29uZmVyZW5jZSBpbmZvcm1h
dGlvbiBpcyBiZXR0ZXIgc2VydmVkIGJ5IHRoZSBldmVudCBwYWNrYWdlLg0KDQozLiBUaGUgaXNz
dWUgaW4gdGhlIFVSSSBsaXN0IHdhcyB0byByZXBsYWNlIG11bHRpcGxlIHJlZmVycyB3aXRoIG9u
IG1lc3NhZ2UgZm9yIGludml0aW5nIHBhcnRpY2lwYW50cywgdGhpcyB3YXMgcGFydCBvZiBhIGdl
bmVyYWwgbWVjaGFuaXNtLiBUaGUgaXNzdWUgb2YgZGVmaW5pbmcgdGhlIGNvbmZlcmVuY2UgcGFy
YW1ldGVycyBhbmQgY29udHJvbGxpbmcgdGhlIGNvbmZlcmVuY2Ugd2FzIG5vdCBjb25zaWRlcmVk
IGluIHNjb3BlIGZvciB0aGlzIHdvcmsuDQoNCjQuICJJbiBjdXJyZW50IGFydCB0aGVyZSBpcyBu
byBtZWNoYW5pc20gZm9yIG5ldyBwYXJ0aWNpcGFudHMgdG8gYmUgYXdhcmUgb2YgdGhlIGNvbmZl
cmVuY2UgaW5mb3JtYXRpb24gdGhleSBhcmUgYmVpbmcgaW52aXRlZCB0by4iIFRoaXMgaXMgd2hh
dCB0aGUgY29uZmVyZW5jZSBldmVudCBwYWNrYWdlIGlzIHVzZWQgZm9yLiBXaGVuIHlvdSBnZXQg
YW4gSW52aXRlIHdpdGggaXNmb2N1cyB5b3UgY2FuIHN1YnNjcmliZSB0byB0aGUgY29uZmVyZW5j
ZSBldmVudCBwYWNrYWdlIGFuZCBnZXQgbm90aWZpY2F0aW9uIGJlZm9yZSBqb2luaW5nLg0KDQo1
LiBSRVEgMSBpcyBjb3ZlcmVkIGJ5IFhDT04gd2hpbGUgUkVRIDIgaXMgY292ZXJlZCBieSB0aGUg
ZXZlbnQgcGFja2FnZS4NCg0KNi4gU2VjdGlvbiA0LjEuMiBhZGRzIGRhdGEgZnJvbSB0aGUgWENP
TiBkYXRhIG1vZGVsIGluY2x1ZGluZyB0aGUgc3RhcnQgdGltZSB5ZXQgdGhlIHJlcXVpcmVtZW50
cyB0YWxrIGFib3V0IGFkLWhvYyBjb25mZXJlbmNlcy4gDQoNCjcuIFVzaW5nIHRoaXMgbWV0aG9k
IGZvciBjb250cm9sbGluZyB0aGUgY29uZmVyZW5jZSBieSBzZW5kaW5nIHJlLUludml0ZSB3aWxs
IGNhdXNlIGEgbG90IG9mIHRyYWZmaWMgdGhyb3VnaCB0aGUgcHJveGllcyBpbiB0aGUgbWlkZGxl
IGFuZCB0aGF0IGlzIHdoeSBYQ09OIGlzIHRoZSB3YXkgdG8gZG8gaXQuDQoNCg0KVG8gc3VtbWFy
aXplIC0gSSBjYW4gc2VlIHNvbWUgdmFsdWUgaW4gYmVpbmcgYWJsZSB0byBzZW5kIHNvbWUgaW5m
b3JtYXRpb24gdG8gdGhlIGNvbmZlcmVuY2UgZmFjdG9yeSBmb3IgdGhlIGFkLWhvYyBjYXNlLiBU
aGUgaW5mb3JtYXRpb24gd2lsbCBpbmNsdWRlIHRoZSByZXF1aXJlZCBtZWRpYSBhbmQgdXNlciBj
b3VudCBidXQgdGhpcyBkcmFmdCBoYXMgYSB3aWRlciBzY29wZS4NCg0KUm9uaSBFdmVuIA0KDQoN
Cg0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogTGlueWkgVGlhbiBb
bWFpbHRvOnRpYW5saW55aUBodWF3ZWkuY29tXQ0KPiBTZW50OiBTYXR1cmRheSwgQXByaWwgMTQs
IDIwMDcgNDowMSBBTQ0KPiBUbzogc2lwcGluZ0BpZXRmLm9yZw0KPiBDYzogeGNvbkBpZXRmLm9y
Zw0KPiBTdWJqZWN0OiBbU2lwcGluZ10gRllJOiBJLURBQ1RJT046ZHJhZnQtbGlueWktc2lwcGlu
Zy1pbnZpdGUtd2l0aC1jb25mLQ0KPiBpbmZvLTAwLnR4dA0KPiANCj4gRGVhciBhbGwNCj4gDQo+
IFdlIGp1c3Qgc3VibWl0dGVkIGFuIEktRCB0byBJRVRGIHJlZ2FyZGluZyBjb25mZXJlbmNlLiBQ
bGVhc2Uga2luZGx5DQo+IHJldmlldyBhbmQgZmVlbCBmcmVlIHRvIGdpdmUgdXMgYW55IGNvbW1l
bnRzLiBUaGFuayB5b3UgaW4gYWR2YW5jZS4NCj4gDQo+IEFic3RyYWN0ICYgUmVxdWlyZW1lbnRz
IEFuYXlseXplDQo+ICAgIFRoaXMgc3BlY2lmaWNhdGlvbiBkZWZpbmVzIGEgbWVjaGFuaXNtIHRo
YXQgYWxsb3dzIGEgVUFDIHRvIHByb3ZpZGUgYQ0KPiAgICBjb25mZXJlbmNlIHNlcnZlciB3aXRo
IHRoZSBpbml0aWFsIGNvbmZlcmVuY2UgaW5mb3JtYXRpb24gYW5kIHBvbGljeQ0KPiAgICB1c2lu
ZyBhbiBJTlZJVEUtY29udGFpbmVkIGNvbmZlcmVuY2UgaW5mby4NCj4gDQo+ICAgIHNvbWUgZW52
aXJvbm1lbnRzIGhhdmUgdG91Z2ggcmVxdWlyZW1lbnRzIHJlZ2FyZGluZyBjb25mZXJlbmNlDQo+
ICAgIGVzdGFibGlzaG1lbnQgdGltZS4gIFRoaXMgaXMgdHJ1ZSBlc3BlY2lhbGx5IHdoZW4gYSB1
c2VyIHdhbnRzIHRvDQo+ICAgIGNyZWF0ZSBhIGNvbmZlcmVuY2UgaW4gYWQgaG9jIG1hbm5lci4g
IEluIGFkZGl0aW9uIHVzZXIgbWF5IG9ubHkgd2FudA0KPiAgICB2ZXJ5IHNpbXBsZSBjb25mZXJl
bmNlIGluZm9ybWF0aW9uIGFuZCBwb2xpY3ksIGZvciBleGFtcGxlIHRoZQ0KPiAgICBzdWJqZWN0
IGFuZCBtYXhpbXVtIG51bWJlcnMgb2YgcGFydGljaXBhbnRzLCB0byBiZSBwcm92aWRlZCBmb3Ig
YW4gYWQNCj4gICAgaG9jIGNvbmZlcmVuY2UgdmlhIG9ubHkgb25lIG9wZXJhdGlvbi4gIEluIHRo
aXMgY2FzZSB0aGV5IHJhcmVseQ0KPiAgICBkZXNpcmUgdG8gbWFuaXB1bGF0ZSB0aGUgY29uZmVy
ZW5jZSBwb2xpY3kgZHVyaW5nIHRoZSBjb25mZXJlbmNlLg0KPiANCj4gICAgSW4gY3VycmVudCBh
cnQgdGhlcmUgaXMgbm8gbWVjaGFuaXNtIGZvciBuZXcgcGFydGljaXBhbnRzIHRvIGJlIGF3YXJl
DQo+ICAgIG9mIHRoZSBjb25mZXJlbmNlIGluZm9ybWF0aW9uIHRoZXkgYXJlIGJlaW5nIGludml0
ZWQgdG8uICBJdCBjYXVzZXMNCj4gICAgZGlmZmljdWx0eSBmb3IgdGhlbSB0byBkZWNpZGUgd2hl
dGhlciB0byBhY2NlcHQgdGhpcyBpbnZpdGF0aW9uIHdoaWNoDQo+ICAgIG1heSBub3QgZmFsbCBp
bnRvIHRoZWlyIGludGVyZXN0Lg0KPiANCj4gQmVzdCBSZWdhcmRzLA0KPiBMaW55aQ0KPiANCj4g
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogSW50ZXJuZXQtRHJhZnRzQGlldGYu
b3JnIFttYWlsdG86SW50ZXJuZXQtRHJhZnRzQGlldGYub3JnXQ0KPiBTZW50OiBTYXR1cmRheSwg
QXByaWwgMTQsIDIwMDcgMzo1MCBBTQ0KPiBUbzogaS1kLWFubm91bmNlQGlldGYub3JnDQo+IFN1
YmplY3Q6IEktRCBBQ1RJT046ZHJhZnQtbGlueWktc2lwcGluZy1pbnZpdGUtd2l0aC1jb25mLWlu
Zm8tMDAudHh0DQo+IA0KPiBBIE5ldyBJbnRlcm5ldC1EcmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0
aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMNCj4gZGlyZWN0b3JpZXMuDQo+IA0KPiANCj4gCVRp
dGxlCQk6IFNlc3Npb24gSW5pdGlhdGlvbiBQcm90b2NvbCAoU0lQKSBJTlZJVEUgd2l0aA0KPiBD
b25mZXJlbmNlIEluZm8NCj4gCUF1dGhvcihzKQk6IEwuIFRpYW4sIFEuIFN1bg0KPiAJRmlsZW5h
bWUJOiBkcmFmdC1saW55aS1zaXBwaW5nLWludml0ZS13aXRoLWNvbmYtaW5mby0wMC50eHQNCj4g
CVBhZ2VzCQk6IDI0DQo+IAlEYXRlCQk6IDIwMDctNC0xMw0KPiANCj4gDQo+ICAgIFRoaXMgc3Bl
Y2lmaWNhdGlvbiBkZWZpbmVzIGEgbWVjaGFuaXNtIHRoYXQgYWxsb3dzIGEgVUFDIHRvIHByb3Zp
ZGUgYQ0KPiAgICBjb25mZXJlbmNlIHNlcnZlciB3aXRoIHRoZSBpbml0aWFsIGNvbmZlcmVuY2Ug
aW5mb3JtYXRpb24gYW5kIHBvbGljeQ0KPiAgICB1c2luZyBhbiBJTlZJVEUtY29udGFpbmVkIGNv
bmZlcmVuY2UgaW5mby4NCj4gDQo+IA0KPiANCj4gQSBVUkwgZm9yIHRoaXMgSW50ZXJuZXQtRHJh
ZnQgaXM6DQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWxpbnlp
LXNpcHBpbmctaW52aXRlLXdpdGgtY29uZi0NCj4gaW5mby0wMC50eHQNCj4gDQo+IFRvIHJlbW92
ZSB5b3Vyc2VsZiBmcm9tIHRoZSBJLUQgQW5ub3VuY2VtZW50IGxpc3QsIHNlbmQgYSBtZXNzYWdl
IHRvDQo+IGktZC1hbm5vdW5jZS1yZXF1ZXN0QGlldGYub3JnIHdpdGggdGhlIHdvcmQgdW5zdWJz
Y3JpYmUgaW4gdGhlIGJvZHkgb2YNCj4gdGhlIG1lc3NhZ2UuDQo+IFlvdSBjYW4gYWxzbyB2aXNp
dCBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9JLUQtYW5ub3VuY2UNCj4g
dG8gY2hhbmdlIHlvdXIgc3Vic2NyaXB0aW9uIHNldHRpbmdzLg0KPiANCj4gSW50ZXJuZXQtRHJh
ZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQLiBMb2dpbiB3aXRoIHRoZQ0K
PiB1c2VybmFtZSAiYW5vbnltb3VzIiBhbmQgYSBwYXNzd29yZCBvZiB5b3VyIGUtbWFpbCBhZGRy
ZXNzLiBBZnRlcg0KPiBsb2dnaW5nIGluLCB0eXBlICJjZCBpbnRlcm5ldC1kcmFmdHMiIGFuZCB0
aGVuDQo+ICJnZXQgZHJhZnQtbGlueWktc2lwcGluZy1pbnZpdGUtd2l0aC1jb25mLWluZm8tMDAu
dHh0Ii4NCj4gDQo+IEEgbGlzdCBvZiBJbnRlcm5ldC1EcmFmdHMgZGlyZWN0b3JpZXMgY2FuIGJl
IGZvdW5kIGluDQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwNCj4gb3IgZnRwOi8v
ZnRwLmlldGYub3JnL2lldGYvMXNoYWRvdy1zaXRlcy50eHQNCj4gDQo+IEludGVybmV0LURyYWZ0
cyBjYW4gYWxzbyBiZSBvYnRhaW5lZCBieSBlLW1haWwuDQo+IA0KPiBTZW5kIGEgbWVzc2FnZSB0
bzoNCj4gCW1haWxzZXJ2QGlldGYub3JnLg0KPiBJbiB0aGUgYm9keSB0eXBlOg0KPiAJIkZJTEUg
L2ludGVybmV0LWRyYWZ0cy9kcmFmdC1saW55aS1zaXBwaW5nLWludml0ZS13aXRoLWNvbmYtaW5m
by0NCj4gMDAudHh0Ii4NCj4gDQo+IE5PVEU6CVRoZSBtYWlsIHNlcnZlciBhdCBpZXRmLm9yZyBj
YW4gcmV0dXJuIHRoZSBkb2N1bWVudCBpbg0KPiAJTUlNRS1lbmNvZGVkIGZvcm0gYnkgdXNpbmcg
dGhlICJtcGFjayIgdXRpbGl0eS4gIFRvIHVzZSB0aGlzDQo+IAlmZWF0dXJlLCBpbnNlcnQgdGhl
IGNvbW1hbmQgIkVOQ09ESU5HIG1pbWUiIGJlZm9yZSB0aGUgIkZJTEUiDQo+IAljb21tYW5kLiAg
VG8gZGVjb2RlIHRoZSByZXNwb25zZShzKSwgeW91IHdpbGwgbmVlZCAibXVucGFjayIgb3INCj4g
CWEgTUlNRS1jb21wbGlhbnQgbWFpbCByZWFkZXIuICBEaWZmZXJlbnQgTUlNRS1jb21wbGlhbnQg
bWFpbCByZWFkZXJzDQo+IAlleGhpYml0IGRpZmZlcmVudCBiZWhhdmlvciwgZXNwZWNpYWxseSB3
aGVuIGRlYWxpbmcgd2l0aA0KPiAJIm11bHRpcGFydCIgTUlNRSBtZXNzYWdlcyAoaS5lLiBkb2N1
bWVudHMgd2hpY2ggaGF2ZSBiZWVuIHNwbGl0DQo+IAl1cCBpbnRvIG11bHRpcGxlIG1lc3NhZ2Vz
KSwgc28gY2hlY2sgeW91ciBsb2NhbCBkb2N1bWVudGF0aW9uIG9uDQo+IAlob3cgdG8gbWFuaXB1
bGF0ZSB0aGVzZSBtZXNzYWdlcy4NCj4gDQo+IEJlbG93IGlzIHRoZSBkYXRhIHdoaWNoIHdpbGwg
ZW5hYmxlIGEgTUlNRSBjb21wbGlhbnQgbWFpbCByZWFkZXINCj4gaW1wbGVtZW50YXRpb24gdG8g
YXV0b21hdGljYWxseSByZXRyaWV2ZSB0aGUgQVNDSUkgdmVyc2lvbiBvZiB0aGUNCj4gSW50ZXJu
ZXQtRHJhZnQuDQo=



--===============0240738072==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0240738072==--



From sipping-bounces@ietf.org Thu Apr 19 05:59:08 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeTPu-00019A-2H; Thu, 19 Apr 2007 05:59:06 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeTPs-00018y-G7 for sipping-confirm+ok@megatron.ietf.org;
	Thu, 19 Apr 2007 05:59:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeTPs-00018q-3v; Thu, 19 Apr 2007 05:59:04 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HeTPr-0005Fh-4Z; Thu, 19 Apr 2007 05:59:04 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	845472094E; Thu, 19 Apr 2007 11:59:02 +0200 (CEST)
X-AuditID: c1b4fb3c-aacefbb0000073d5-8c-46273d662ee0 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6399320502; Thu, 19 Apr 2007 11:59:02 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Apr 2007 11:59:01 +0200
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
Subject: RE: [XCON] RE: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
Date: Thu, 19 Apr 2007 11:58:24 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F039EBE30@esealmw105.eemea.ericsson.se>
In-Reply-To: <006901c781be$f3609170$8b010a0a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [XCON] RE: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
Thread-Index: Acd+BRGvg5j3Onq2SFOXOU2/y8iMmwAKt1wAAB9++ZAAaEZKIABPskUwAAwdJ/AAJ1F3YA==
References: <A91F30A632473A47B40C18D2B107CA6F039EBE25@esealmw105.eemea.ericsson.se>
	<006901c781be$f3609170$8b010a0a@china.huawei.com>
From: "Oscar Novo \(JO/LMF\)" <oscar.novo@ericsson.com>
To: "Linyi Tian" <tianlinyi@huawei.com>,
	<sipping@ietf.org>
X-OriginalArrivalTime: 19 Apr 2007 09:59:01.0727 (UTC)
	FILETIME=[5B3D4EF0:01C78269]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32029c790f79bd4a84a26bd2915c54b9
Cc: xcon@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi Linyi,

I guess the XCON WG will start working on the conference control
protocol in a few IETF but my impression is that we'll need long time to
complete this protocol. So, your supplementary solution could be fine
before we don't define anything in XCON.  =20

Regarding the possible inconsistency between the URI-List and the
maximum number of users, I think it would be useful to described the
server behaviour in this case. At least, I can think in two different
solutions for that use case:

- The server REJECTS the INVITE and sends an error to the UAC.
- The server ACCEPTS the INVITE and changes the maximum user number of
the conference to the number of URIs in the URI-List. =20

Cheers,

Oscar

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com]=20
Sent: 18. huhtikuuta 2007 16:39
To: Oscar Novo (JO/LMF); 'Henry Sinnreich'; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [XCON] RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Hi, Oscar

You are very much appreciated for the information and suggestion!

Yes, we are aware of the work ongoing in XCON. However we do not know
when this protocol will be completed. There is much work to do with my
guess. Maybe somebody can not wait, e.g. OMA is very interested in XCAP
solution for pre-defined group communications. For ad-hoc conference,
XCAP may not be suitable, but this draft will work well.

In addition to that, there is still no way to provide ad-hoc conference
with conference information or policy in OMA. But we see some
requirements within some ongoing work in other organizations. This I-D
tries to provide the facility. It can be treated as a supplementary
solution for existing arts which may particularly address some cases in
a simple way.

Regarding maximum counts of participants, actually I have following
sentence related in section 5:
The UAC MUST ensure the number of URIs in the URI-List will not exceed
the number specified in <maximum-user-count> element if it presents.

Does it satisfy what you need? If not, could you give me some further
explanation? If something needs to be changed, I can add them in the
next version.

Again, much appreciated for your comments!

Thank you!

Best Regards,
Linyi

-----Original Message-----
From: Oscar Novo (JO/LMF) [mailto:oscar.novo@ericsson.com]
Sent: Wednesday, April 18, 2007 11:26 AM
To: Linyi Tian; Henry Sinnreich; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [XCON] RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Hi Linyi,

In the future, XCON WG will work in a protocol to create and manipulate
the conference information in a server. The use of that protocol may be
completely transparent for the mobile users. So, mobile users could
create ad hoc conferences in an easy way.

I think one important use cases to be describe in your draft would be
when the number of URIs in the URI-List exceeds the number specified in
<maximum-user-count> element send by the UAC.

Regards,

Oscar

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com]
Sent: 16. huhtikuuta 2007 20:55
To: 'Henry Sinnreich'; sipping@ietf.org
Cc: xcon@ietf.org
Subject: [XCON] RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Dear Henry

Thank you very much for your comments. Some responses below:
In the mobile environment user may not desire to access the web site to
create conf info for a conference especially when it is in ad hoc
manner. So the assumption is that it is boring for user to create an ad
hoc conference using two operations.=20

This draft respects the same consideration like 'some environments have
tough requirements regarding conference establishment time' in another
I-D for uri list conferencing. In case of user only wants very simple
conference information and policy, such as subject and maximum numbers
of participants, to be provided for an ad hoc conference via only one
operation. The SIP invite could be used to convey it to create a
conference fulfilling this requirement.

Best Regards,
Linyi

-----Original Message-----
From: Henry Sinnreich [mailto:hsinnrei@adobe.com]
Sent: Saturday, April 14, 2007 7:07 PM
To: Linyi Tian; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

How would this compare with providing the conference info and policy
over a web page is now the 'standard procedure'?

Or is the assumption that there is no web and we live in a voice-only
world?

>'some environments have tough requirements regarding conference=20
>establishment time'

Why is this a SIP issue?

What about users having predefined access to their conference service by
IT or by contract and just telling the participants to dial in?

Thanks, Henry

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com]
Sent: Friday, April 13, 2007 6:01 PM
To: sipping@ietf.org
Cc: xcon@ietf.org
Subject: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Dear all

We just submitted an I-D to IETF regarding conference. Please kindly
review and feel free to give us any comments. Thank you in advance.=20

Abstract & Requirements Anaylyze
   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.

   some environments have tough requirements regarding conference
   establishment time.  This is true especially when a user wants to
   create a conference in ad hoc manner.  In addition user may only want
   very simple conference information and policy, for example the
   subject and maximum numbers of participants, to be provided for an ad
   hoc conference via only one operation.  In this case they rarely
   desire to manipulate the conference policy during the conference.

   In current art there is no mechanism for new participants to be aware
   of the conference information they are being invited to.  It causes
   difficulty for them to decide whether to accept this invitation which
   may not fall into their interest.

Best Regards,
Linyi

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Saturday, April 14, 2007 3:50 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Session Initiation Protocol (SIP) INVITE with
Conference Info
	Author(s)	: L. Tian, Q. Sun
	Filename	:
draft-linyi-sipping-invite-with-conf-info-00.txt
	Pages		: 24
	Date		: 2007-4-13
=09

   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-linyi-sipping-invite-with-conf
-info-00.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.=20
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then "get
draft-linyi-sipping-invite-with-conf-info-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html or
ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE
/internet-drafts/draft-linyi-sipping-invite-with-conf-info-00.txt".
=09
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.



_______________________________________________
XCON mailing list
XCON@ietf.org
https://www1.ietf.org/mailman/listinfo/xcon




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 19 06:59:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeUMB-0003hX-2v; Thu, 19 Apr 2007 06:59:19 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeUM9-0003hN-RK for sipping-confirm+ok@megatron.ietf.org;
	Thu, 19 Apr 2007 06:59:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeUM9-0003hF-Hn; Thu, 19 Apr 2007 06:59:17 -0400
Received: from lhrga01-in.huawei.com ([195.33.106.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HeUM8-0000Pj-PK; Thu, 19 Apr 2007 06:59:17 -0400
Received: from huawei.com (lhrml01-in [172.18.7.5])
	by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JGQ00A5VRVGV0@lhrga01-in.huawei.com>; Thu,
	19 Apr 2007 11:59:41 +0100 (BST)
Received: from jys3105093470ty ([62.159.183.141])
	by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JGQ00IUSRVCET@lhrga01-in.huawei.com>; Thu,
	19 Apr 2007 11:59:40 +0100 (BST)
Date: Thu, 19 Apr 2007 13:00:00 +0300
From: Linyi Tian <tianlinyi@huawei.com>
Subject: RE: [XCON] RE: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
In-reply-to: <A91F30A632473A47B40C18D2B107CA6F039EBE30@esealmw105.eemea.ericsson.se>
To: "'Oscar Novo (JO/LMF)'" <oscar.novo@ericsson.com>, sipping@ietf.org
Message-id: <012601c78269$7e966170$8b010a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7BIT
Thread-index: Acd+BRGvg5j3Onq2SFOXOU2/y8iMmwAKt1wAAB9++ZAAaEZKIABPskUwAAwdJ/AAJ1F3YAADbMMw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
Cc: xcon@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dear Oscar

Thank you very much for your valuable comments. I will reflect them in next revision.

By the way, I was noticed that the I-D draft-ietf-xcon-common-data-model-05 was submitted to IETF. It affects our draft. So I need to dig into it and reflect the changes as well.

Best Regards,
Linyi

-----Original Message-----
From: Oscar Novo (JO/LMF) [mailto:oscar.novo@ericsson.com] 
Sent: Thursday, April 19, 2007 12:58 PM
To: Linyi Tian; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [XCON] RE: [Sipping] FYI: I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Hi Linyi,

I guess the XCON WG will start working on the conference control
protocol in a few IETF but my impression is that we'll need long time to
complete this protocol. So, your supplementary solution could be fine
before we don't define anything in XCON.   

Regarding the possible inconsistency between the URI-List and the
maximum number of users, I think it would be useful to described the
server behaviour in this case. At least, I can think in two different
solutions for that use case:

- The server REJECTS the INVITE and sends an error to the UAC.
- The server ACCEPTS the INVITE and changes the maximum user number of
the conference to the number of URIs in the URI-List.  

Cheers,

Oscar

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com] 
Sent: 18. huhtikuuta 2007 16:39
To: Oscar Novo (JO/LMF); 'Henry Sinnreich'; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [XCON] RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Hi, Oscar

You are very much appreciated for the information and suggestion!

Yes, we are aware of the work ongoing in XCON. However we do not know
when this protocol will be completed. There is much work to do with my
guess. Maybe somebody can not wait, e.g. OMA is very interested in XCAP
solution for pre-defined group communications. For ad-hoc conference,
XCAP may not be suitable, but this draft will work well.

In addition to that, there is still no way to provide ad-hoc conference
with conference information or policy in OMA. But we see some
requirements within some ongoing work in other organizations. This I-D
tries to provide the facility. It can be treated as a supplementary
solution for existing arts which may particularly address some cases in
a simple way.

Regarding maximum counts of participants, actually I have following
sentence related in section 5:
The UAC MUST ensure the number of URIs in the URI-List will not exceed
the number specified in <maximum-user-count> element if it presents.

Does it satisfy what you need? If not, could you give me some further
explanation? If something needs to be changed, I can add them in the
next version.

Again, much appreciated for your comments!

Thank you!

Best Regards,
Linyi

-----Original Message-----
From: Oscar Novo (JO/LMF) [mailto:oscar.novo@ericsson.com]
Sent: Wednesday, April 18, 2007 11:26 AM
To: Linyi Tian; Henry Sinnreich; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [XCON] RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Hi Linyi,

In the future, XCON WG will work in a protocol to create and manipulate
the conference information in a server. The use of that protocol may be
completely transparent for the mobile users. So, mobile users could
create ad hoc conferences in an easy way.

I think one important use cases to be describe in your draft would be
when the number of URIs in the URI-List exceeds the number specified in
<maximum-user-count> element send by the UAC.

Regards,

Oscar

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com]
Sent: 16. huhtikuuta 2007 20:55
To: 'Henry Sinnreich'; sipping@ietf.org
Cc: xcon@ietf.org
Subject: [XCON] RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Dear Henry

Thank you very much for your comments. Some responses below:
In the mobile environment user may not desire to access the web site to
create conf info for a conference especially when it is in ad hoc
manner. So the assumption is that it is boring for user to create an ad
hoc conference using two operations. 

This draft respects the same consideration like 'some environments have
tough requirements regarding conference establishment time' in another
I-D for uri list conferencing. In case of user only wants very simple
conference information and policy, such as subject and maximum numbers
of participants, to be provided for an ad hoc conference via only one
operation. The SIP invite could be used to convey it to create a
conference fulfilling this requirement.

Best Regards,
Linyi

-----Original Message-----
From: Henry Sinnreich [mailto:hsinnrei@adobe.com]
Sent: Saturday, April 14, 2007 7:07 PM
To: Linyi Tian; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

How would this compare with providing the conference info and policy
over a web page is now the 'standard procedure'?

Or is the assumption that there is no web and we live in a voice-only
world?

>'some environments have tough requirements regarding conference 
>establishment time'

Why is this a SIP issue?

What about users having predefined access to their conference service by
IT or by contract and just telling the participants to dial in?

Thanks, Henry

-----Original Message-----
From: Linyi Tian [mailto:tianlinyi@huawei.com]
Sent: Friday, April 13, 2007 6:01 PM
To: sipping@ietf.org
Cc: xcon@ietf.org
Subject: [Sipping] FYI:
I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Dear all

We just submitted an I-D to IETF regarding conference. Please kindly
review and feel free to give us any comments. Thank you in advance. 

Abstract & Requirements Anaylyze
   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.

   some environments have tough requirements regarding conference
   establishment time.  This is true especially when a user wants to
   create a conference in ad hoc manner.  In addition user may only want
   very simple conference information and policy, for example the
   subject and maximum numbers of participants, to be provided for an ad
   hoc conference via only one operation.  In this case they rarely
   desire to manipulate the conference policy during the conference.

   In current art there is no mechanism for new participants to be aware
   of the conference information they are being invited to.  It causes
   difficulty for them to decide whether to accept this invitation which
   may not fall into their interest.

Best Regards,
Linyi

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Saturday, April 14, 2007 3:50 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Session Initiation Protocol (SIP) INVITE with
Conference Info
	Author(s)	: L. Tian, Q. Sun
	Filename	:
draft-linyi-sipping-invite-with-conf-info-00.txt
	Pages		: 24
	Date		: 2007-4-13
	

   This specification defines a mechanism that allows a UAC to provide a
   conference server with the initial conference information and policy
   using an INVITE-contained conference info.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-linyi-sipping-invite-with-conf
-info-00.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then "get
draft-linyi-sipping-invite-with-conf-info-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html or
ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE
/internet-drafts/draft-linyi-sipping-invite-with-conf-info-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.



_______________________________________________
XCON mailing list
XCON@ietf.org
https://www1.ietf.org/mailman/listinfo/xcon






_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 19 07:23:01 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeUj3-00080V-P3; Thu, 19 Apr 2007 07:22:57 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeUj2-00080J-NE for sipping-confirm+ok@megatron.ietf.org;
	Thu, 19 Apr 2007 07:22:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeUj2-000805-Bn
	for sipping@ietf.org; Thu, 19 Apr 2007 07:22:56 -0400
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeUj0-0001EN-UX
	for sipping@ietf.org; Thu, 19 Apr 2007 07:22:56 -0400
Received: from S4DE9JSAANO.ost.t-com.de (S4DE9JSAANO.ost.t-com.de
	[10.125.177.105]) by tcmail21.telekom.de with ESMTP;
	Thu, 19 Apr 2007 13:22:53 +0200
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANO.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Apr 2007 13:22:51 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: AW: AW: [Sipping] Call Completion: In Defense of Explicit Operations
Date: Thu, 19 Apr 2007 13:22:50 +0200
Message-Id: <CCA850DCD3FBE2479D5076C5C18732220168AA79@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <32ED04D2-7B32-4DA7-948E-60263ACACB33@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AW: [Sipping] Call Completion: In Defense of Explicit Operations
thread-index: Acd9G4aMnkXzE0H2TfyGKa6YKE4RnAFVOhLw
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <dean.willis@softarmor.com>,
    <pkyzivat@cisco.com>
X-OriginalArrivalTime: 19 Apr 2007 11:22:51.0606 (UTC)
	FILETIME=[1147EF60:01C78275]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: sipping@ietf.org, adam@nostrum.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi,

one open question seems to be, how can you differentiate between =
cancelling a subsription for suspension and cancelling it for =
deactivation?

I think because of performance reasons it's necessary to remove an entry =
from the queue if the queueing is not needed anymore.

Regards, Martin




> -----Urspr=FCngliche Nachricht-----
> Von: Dean Willis [mailto:dean.willis@softarmor.com]=20
> Gesendet: Donnerstag, 12. April 2007 17:59
> An: Paul Kyzivat
> Cc: Adam Roach; H=FClsemann, Martin; sipping@ietf.org
> Betreff: Re: AW: [Sipping] Call Completion: In Defense of=20
> Explicit Operations
=20
> >
> > I guess you could go ahead and enroll the caller of every failed =20
> > call, but only give a window of opportunity to a candidate=20
> that has =20
> > been notified that it is at the head of the queue.
> >
>=20
> That would work too -- if the NOTIFY times out, expunge. But it does =20
> add about 32s of latency.
>=20
> > That also suggests a way to handle suspend/resume: to suspend you =20
> > simply cancel your subscription. And to resume you make a new =20
> > subscription.
>=20
> yeah, that works. The requirement is that the queue-place is not =20
> purged as a side effect of canceling the subscription. Rather, the =20
> watcherinfo is used to determine the duration for which that queue-=20
> place will be held at the top of the queue.
>=20
> What happens if you "suspend" and your place comes and goes during =20
> the interval? Sounds like we'd also have to have a little more =20
> complex queue management to give a recovery window, but it is very =20
> doable.
>=20
> >
> > That seems somewhat interesting. But it presents a new problem - a =20
> > subscriber needs to know if they even have an entry in the queue. =20
> > If you only get notified when you get to the top, then you could =20
> > wait forever if you aren't in the queue.
> >
>=20
> Right. Would it be reasonable to have a server-side cancel on the =20
> subscription if your token goes stale?
>=20
> --
> Dean
>=20
>=20
>=20
>=20


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 19 08:53:04 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeW8D-0002Jp-LX; Thu, 19 Apr 2007 08:53:01 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeW8C-0002Jk-2I for sipping-confirm+ok@megatron.ietf.org;
	Thu, 19 Apr 2007 08:53:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeW8B-0002Jc-NY
	for sipping@ietf.org; Thu, 19 Apr 2007 08:52:59 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HeW8A-0005CN-90
	for sipping@ietf.org; Thu, 19 Apr 2007 08:52:59 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-4.cisco.com with ESMTP; 19 Apr 2007 05:52:57 -0700
X-IronPort-AV: i="4.14,426,1170662400"; 
	d="scan'208"; a="54619973:sNHT50659425"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l3JCqv3W020960; 
	Thu, 19 Apr 2007 05:52:57 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l3JCqmAG027625;
	Thu, 19 Apr 2007 12:52:54 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Apr 2007 08:52:54 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Apr 2007 08:52:53 -0400
Message-ID: <46276626.8060307@cisco.com>
Date: Thu, 19 Apr 2007 08:52:54 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
Subject: Re: AW: AW: [Sipping] Call Completion: In Defense of Explicit
	Operations
References: <CCA850DCD3FBE2479D5076C5C18732220168AA79@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <CCA850DCD3FBE2479D5076C5C18732220168AA79@S4DE9JSAAHW.ost.t-com.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 19 Apr 2007 12:52:53.0836 (UTC)
	FILETIME=[A542D0C0:01C78281]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2514; t=1176987177;
	x=1177851177; c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20AW=3A=20[Sipping]=20Call=20Completion=3A=20In
	=20Defense=20of=20Explicit=20Operations |Sender:=20;
	bh=RuD3iozELwer8l3hAN8wsNP6tBkS8XSg9ZrCfjkNvAA=;
	b=FWJkJ6+uvw6Zo6IRQ+TumVJj+Q1fOLb3vDGabYoJIx/1v+bm2FSaiYizjmH+SE3gfUkdIM9F
	fuMR3D+OeqgrzKb+J+KOo/0FXb/WuRMZRrxSbfnKtQQOMTcFYU/NAxQ7;
Authentication-Results: sj-dkim-6; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim6002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: sipping@ietf.org, adam@nostrum.com, dean.willis@softarmor.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org



Huelsemann, Martin wrote:
> Hi,
> 
> one open question seems to be, how can you differentiate between cancelling a subsription for suspension and cancelling it for deactivation?
> 
> I think because of performance reasons it's necessary to remove an entry from the queue if the queueing is not needed anymore.

In theory this might be significant. But will it be in practice? Under 
what circumstances would the cancellation for deactivation actually take 
place? What percentage of all queued requests will ever be canceled in 
this way?

If a simple mechanism will be sufficient without this capability, and a 
more complex mechanism will be required simply to support removing from 
the queue in this one case, is it worth it?

	Paul

> Regards, Martin
> 
> 
> 
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Dean Willis [mailto:dean.willis@softarmor.com] 
>> Gesendet: Donnerstag, 12. April 2007 17:59
>> An: Paul Kyzivat
>> Cc: Adam Roach; Hülsemann, Martin; sipping@ietf.org
>> Betreff: Re: AW: [Sipping] Call Completion: In Defense of 
>> Explicit Operations
>  
>>> I guess you could go ahead and enroll the caller of every failed  
>>> call, but only give a window of opportunity to a candidate 
>> that has  
>>> been notified that it is at the head of the queue.
>>>
>> That would work too -- if the NOTIFY times out, expunge. But it does  
>> add about 32s of latency.
>>
>>> That also suggests a way to handle suspend/resume: to suspend you  
>>> simply cancel your subscription. And to resume you make a new  
>>> subscription.
>> yeah, that works. The requirement is that the queue-place is not  
>> purged as a side effect of canceling the subscription. Rather, the  
>> watcherinfo is used to determine the duration for which that queue- 
>> place will be held at the top of the queue.
>>
>> What happens if you "suspend" and your place comes and goes during  
>> the interval? Sounds like we'd also have to have a little more  
>> complex queue management to give a recovery window, but it is very  
>> doable.
>>
>>> That seems somewhat interesting. But it presents a new problem - a  
>>> subscriber needs to know if they even have an entry in the queue.  
>>> If you only get notified when you get to the top, then you could  
>>> wait forever if you aren't in the queue.
>>>
>> Right. Would it be reasonable to have a server-side cancel on the  
>> subscription if your token goes stale?
>>
>> --
>> Dean
>>
>>
>>
>>
> 


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 19 14:51:14 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hebib-000245-K4; Thu, 19 Apr 2007 14:50:57 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hebia-00023v-Fe for sipping-confirm+ok@megatron.ietf.org;
	Thu, 19 Apr 2007 14:50:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hebia-00023n-5i; Thu, 19 Apr 2007 14:50:56 -0400
Received: from lhrga01-in.huawei.com ([195.33.106.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HebiZ-00062p-Ct; Thu, 19 Apr 2007 14:50:56 -0400
Received: from huawei.com (lhrml01-in [172.18.7.5])
	by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JGR00AWJDPI2D@lhrga01-in.huawei.com>; Thu,
	19 Apr 2007 19:51:19 +0100 (BST)
Received: from jys3105093470ty ([62.159.183.141])
	by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JGR00EJYDPAUQ@lhrga01-in.huawei.com>; Thu,
	19 Apr 2007 19:51:18 +0100 (BST)
Date: Thu, 19 Apr 2007 20:51:33 +0300
From: Linyi Tian <tianlinyi@huawei.com>
Subject: RE: [Sipping] FYI:
	I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
In-reply-to: <144ED8561CE90C41A3E5908EDECE315C047C20EF@IsrExch01.israel.polycom.com>
To: "'Even, Roni'" <roni.even@polycom.co.il>, sipping@ietf.org
Message-id: <000001c782ab$5e662740$8b010a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7BIT
Thread-index: Acd+BRGvg5j3Onq2SFOXOU2/y8iMmwAKt1wAAQfxWcAAFtkvIA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Cc: xcon@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Dear Roni Even

Thank your for your kind review and feedback. Some responses inline with mark [Linyi]:)

Best Regards,
Linyi

-----Original Message-----
From: Even, Roni [mailto:roni.even@polycom.co.il] 
Sent: Thursday, April 19, 2007 12:06 PM
To: Linyi Tian; sipping@ietf.org
Cc: xcon@ietf.org
Subject: RE: [Sipping] FYI: I-DACTION:draft-linyi-sipping-invite-with-conf-info-00.txt

Linyi,

I read the draft and have some comments about this direction.


Linyi,

I read the draft and have some comments about this direction.


1. It is an advantage in letting the invitee know the subject of the conference but this is true also for a point to point call. This is not unique to conference.
[Linyi Tian] Good point! Do you mean that we need to use this mechanism for point to point scenario?

2. letting the invitee know who the other participants in the conference and the conference information is better served by the event package.
[Linyi Tian] Actually I guess in ad hoc manner the mechanism in this draft is more efficient.

3. The issue in the URI list was to replace multiple refers with on message for inviting participants, this was part of a general mechanism. The issue of defining the conference parameters and controlling the conference was not considered in scope for this work.
[Linyi Tian] Yes, that's true. But our draft does not have any intention to affect the URI-List work. Actually the mechanism in our draft can be used together with URI list. We just gave the example to address different scenarios: 1. without URI list; 2. with URI list. So when URI-List the conference server needs to perform more actions in addition to those defined in URI-List work.

4. "In current art there is no mechanism for new participants to be aware of the conference information they are being invited to." This is what the conference event package is used for. When you get an Invite with isfocus you can subscribe to the conference event package and get notification before joining.
[Linyi Tian] Good catch! I guess the sentence I wrote is not quite precise. I will modify it. 

5. REQ 1 is covered by XCON while REQ 2 is covered by the event package.
[Linyi Tian] According to the comments you mentioned, I will update REQs to better reflect our intention.

6. Section 4.1.2 adds data from the XCON data model including the start time yet the requirements talk about ad-hoc conferences. 
[Linyi Tian] Good catch. That is a mistake. Anyway I need to change something in next revision since that draft was updated.

7. Using this method for controlling the conference by sending re-Invite will cause a lot of traffic through the proxies in the middle and that is why XCON is the way to do it.
[Linyi Tian] Yes. What is stated in the draft is there is no semantics defined for re-INVITE. Actually it is recommended not using re-INVITE for controlling the conference in this draft. I can make it clearer.


To summarize - I can see some value in being able to send some information to the conference factory for the ad-hoc case. The information will include the required media and user count but this draft has a wider scope.
[Linyi Tian] I think in addition to subject and user count, we may find other information which could be useful as well. For example, <keyword> for search purpose, <service-uris> which provides complementary information such as URI for presentations:)

Roni Even




> -----Original Message-----
> From: Linyi Tian [mailto:tianlinyi@huawei.com]
> Sent: Saturday, April 14, 2007 4:01 AM
> To: sipping@ietf.org
> Cc: xcon@ietf.org
> Subject: [Sipping] FYI: I-DACTION:draft-linyi-sipping-invite-with-conf-
> info-00.txt
> 
> Dear all
> 
> We just submitted an I-D to IETF regarding conference. Please kindly
> review and feel free to give us any comments. Thank you in advance.
> 
> Abstract & Requirements Anaylyze
>    This specification defines a mechanism that allows a UAC to provide a
>    conference server with the initial conference information and policy
>    using an INVITE-contained conference info.
> 
>    some environments have tough requirements regarding conference
>    establishment time.  This is true especially when a user wants to
>    create a conference in ad hoc manner.  In addition user may only want
>    very simple conference information and policy, for example the
>    subject and maximum numbers of participants, to be provided for an ad
>    hoc conference via only one operation.  In this case they rarely
>    desire to manipulate the conference policy during the conference.
> 
>    In current art there is no mechanism for new participants to be aware
>    of the conference information they are being invited to.  It causes
>    difficulty for them to decide whether to accept this invitation which
>    may not fall into their interest.
> 
> Best Regards,
> Linyi
> 
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Saturday, April 14, 2007 3:50 AM
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-linyi-sipping-invite-with-conf-info-00.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
> 	Title		: Session Initiation Protocol (SIP) INVITE with
> Conference Info
> 	Author(s)	: L. Tian, Q. Sun
> 	Filename	: draft-linyi-sipping-invite-with-conf-info-00.txt
> 	Pages		: 24
> 	Date		: 2007-4-13
> 
> 
>    This specification defines a mechanism that allows a UAC to provide a
>    conference server with the initial conference information and policy
>    using an INVITE-contained conference info.
> 
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-linyi-sipping-invite-with-conf-
> info-00.txt
> 
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> "get draft-linyi-sipping-invite-with-conf-info-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-linyi-sipping-invite-with-conf-info-
> 00.txt".
> 
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 19 17:14:41 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hedwg-0007w0-Rr; Thu, 19 Apr 2007 17:13:38 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hedwe-0007vh-Re for sipping-confirm+ok@megatron.ietf.org;
	Thu, 19 Apr 2007 17:13:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hedwe-0007vZ-Hu
	for sipping@ietf.org; Thu, 19 Apr 2007 17:13:36 -0400
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hedwd-00028K-8h
	for sipping@ietf.org; Thu, 19 Apr 2007 17:13:36 -0400
Received: from [206.176.144.212] (rcdn4-dmznat-gw1-nat-27.cisco.com
	[12.5.186.27]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l3JKK0Cq003531
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 19 Apr 2007 15:20:06 -0500
In-Reply-To: <CCA850DCD3FBE2479D5076C5C18732220168AA79@S4DE9JSAAHW.ost.t-com.de>
References: <CCA850DCD3FBE2479D5076C5C18732220168AA79@S4DE9JSAAHW.ost.t-com.de>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3206C229-4ACA-4C95-951B-197103DF89BD@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: AW: AW: [Sipping] Call Completion: In Defense of Explicit
	Operations
Date: Thu, 19 Apr 2007 16:13:07 -0500
To: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: sipping@ietf.org, pkyzivat@cisco.com, adam@nostrum.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 19, 2007, at 6:22 AM, Huelsemann, Martin wrote:

> Hi,
>
> one open question seems to be, how can you differentiate between  
> cancelling a subsription for suspension and cancelling it for  
> deactivation?
>

By how long the resources goes unwatched? That is, a matter of time.

--
Dean



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 20 13:36:47 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hex2H-0006RT-0O; Fri, 20 Apr 2007 13:36:41 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hex2F-0006LI-RQ for sipping-confirm+ok@megatron.ietf.org;
	Fri, 20 Apr 2007 13:36:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hex2F-0006JM-GI
	for sipping@ietf.org; Fri, 20 Apr 2007 13:36:39 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hex2D-000439-67
	for sipping@ietf.org; Fri, 20 Apr 2007 13:36:39 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 20 Apr 2007 10:36:36 -0700
X-IronPort-AV: i="4.14,433,1170662400"; 
	d="scan'208"; a="138530125:sNHT47488149"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l3KHaadZ004205; 
	Fri, 20 Apr 2007 10:36:36 -0700
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with SMTP id l3KHaVZU023659;
	Fri, 20 Apr 2007 17:36:35 GMT
In-Reply-To: <BD4376EB-403C-4988-B6AA-1BADA9380EF3@cs.columbia.edu>
References: <4613BFD4.9090107@bell-labs.com>
	<B02B0F6A-A2A8-4929-8623-5902DA5F24CF@cisco.com>
	<BD4376EB-403C-4988-B6AA-1BADA9380EF3@cs.columbia.edu>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DABAFEBE-90F5-4A42-A7C6-E4272B6B9171@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sipping] Conclusion for merging
Date: Fri, 20 Apr 2007 10:36:02 -0700
To: Henning Schulzrinne <hgs@cs.columbia.edu>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2301; t=1177090596;
	x=1177954596; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Conclusion=20for=20merging
	|Sender:=20; bh=viRE6/jmWW8iKswdJ3AEVUGQXVBxAkDuGK2bYC5/PLQ=;
	b=cZwm4ePDKDORx1Y4FaUlA7n8wxWYXt+5H7UasJXrMg4WgQS6jEv6pMdT96ydCPp7HWn133HR
	nueLUzyWGDHH5XcYrApDBmUeJ6E6FjLgVKHSZpEltFN5QvT15UJEn/sQ;
Authentication-Results: sj-dkim-3; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: Volker Hilt <volkerh@bell-labs.com>, sipping <sipping@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	Martin C Dolly <mdolly@att.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 15, 2007, at 7:10 AM, Henning Schulzrinne wrote:

>
> On Apr 15, 2007, at 1:04 AM, Cullen Jennings wrote:
>
>>
>> There is a third option which I have always been a fan of -  
>> basically do 1 below but then in the places where you do want two  
>> things, lets say, both local and network can set a max_bandwidth,  
>> well you have two things one call local_max_bandwidth and one  
>> called network_max_bandwidth. They are both separate fields and  
>> the application knows what to do with them.
>
> Since the application has to obey a single bandwidth limit, the  
> application still has to decide that either local_max_bandwidth  
> overrides network_max_bandwidth or the result is min(local_,  
> network_). If you want predictable behavior, you presumably need to  
> standardize which it is.
>
> Thus, I don't see how this addresses the problem at hand.

I am off in the area of angels on a pin head here so forgive me but ....

The UA needs to know the semantics of local_max_bandwidth means do  
not exceed this. It needs to know the semantics of  
network_max_bandwidth means do not exceed this and it need to pay  
attention to all the config it received or things may not operate as  
expected. I do understand that that a min(a,b) does eventually get  
solved.

The meta point is that only a device that understands the semantics  
of these two things needs to try and know what to do with them or how  
to "merge" them. I don't think of it is merging, it is just using  
them. The merging stuff in the framework was designed such that a  
devices that *did not* understand the semantics of what some data  
item meant could still merge them. Originally people had the idea  
that there would be servers that collected up all the local, network,  
etc profiles for the UA and then merged the data on behalf of the UA  
then passed the merged result down to the UA. I see no need for  
theses types of servers.

I see no need for devices that don't understand the semantics of the  
data to be required to merge the data thus I see no need for the data  
to have self describing rules about how to merge it. I think it adds  
complexity and no one has presented a use case where it is useful.

Cullen <with my individual hat on>


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 20 13:47:09 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HexCO-0002QH-6W; Fri, 20 Apr 2007 13:47:08 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HexCK-0002Pp-Qj for sipping-confirm+ok@megatron.ietf.org;
	Fri, 20 Apr 2007 13:47:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HexCK-0002Pf-HB
	for sipping@ietf.org; Fri, 20 Apr 2007 13:47:04 -0400
Received: from jalapeno.cc.columbia.edu ([128.59.29.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HexCJ-0006w5-JV
	for sipping@ietf.org; Fri, 20 Apr 2007 13:47:04 -0400
Received: from [128.59.23.102] (macmini1.cs.columbia.edu [128.59.23.102])
	(user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id
	l3KHkp2H022823
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 20 Apr 2007 13:46:51 -0400 (EDT)
In-Reply-To: <DABAFEBE-90F5-4A42-A7C6-E4272B6B9171@cisco.com>
References: <4613BFD4.9090107@bell-labs.com>
	<B02B0F6A-A2A8-4929-8623-5902DA5F24CF@cisco.com>
	<BD4376EB-403C-4988-B6AA-1BADA9380EF3@cs.columbia.edu>
	<DABAFEBE-90F5-4A42-A7C6-E4272B6B9171@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0B67995C-CFD7-4BFD-8604-3E61AF658CF7@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Conclusion for merging
Date: Fri, 20 Apr 2007 13:48:08 -0400
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: Volker Hilt <volkerh@bell-labs.com>, sipping <sipping@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	Martin C Dolly <mdolly@att.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I think we agree that "blind" merging is of very little use, since  
merging two parameters that the client doesn't understand adds little  
value, except in displaying them to the user.

However, the question is what the parameter-related spec should say.  
If the spec does not indicate what a device that knows about  
bandwidth limits should do, it is likely that two devices will differ  
in their behavior. Thus, I think the spec has to specify "min 
(network, local)", say, for this particular parameter. After all,  
there are other semi-reasonable algorithms, such as picking one of  
the parameters (override) or the average or maybe even the maximum.

Otherwise, a network operator can't rely on what a properly  
configured device will do. In that case, configuration becomes  
meaningless and largely useless. Why specify a bandwidth limit if  
every device treats this differently, in unpredictable fashion?

Henning

On Apr 20, 2007, at 1:36 PM, Cullen Jennings wrote:

>
> On Apr 15, 2007, at 7:10 AM, Henning Schulzrinne wrote:
>
>>
>> On Apr 15, 2007, at 1:04 AM, Cullen Jennings wrote:
>>
>>>
>>> There is a third option which I have always been a fan of -  
>>> basically do 1 below but then in the places where you do want two  
>>> things, lets say, both local and network can set a max_bandwidth,  
>>> well you have two things one call local_max_bandwidth and one  
>>> called network_max_bandwidth. They are both separate fields and  
>>> the application knows what to do with them.
>>
>> Since the application has to obey a single bandwidth limit, the  
>> application still has to decide that either local_max_bandwidth  
>> overrides network_max_bandwidth or the result is min(local_,  
>> network_). If you want predictable behavior, you presumably need  
>> to standardize which it is.
>>
>> Thus, I don't see how this addresses the problem at hand.
>
> I am off in the area of angels on a pin head here so forgive me  
> but ....
>
> The UA needs to know the semantics of local_max_bandwidth means do  
> not exceed this. It needs to know the semantics of  
> network_max_bandwidth means do not exceed this and it need to pay  
> attention to all the config it received or things may not operate  
> as expected. I do understand that that a min(a,b) does eventually  
> get solved.
>
> The meta point is that only a device that understands the semantics  
> of these two things needs to try and know what to do with them or  
> how to "merge" them. I don't think of it is merging, it is just  
> using them. The merging stuff in the framework was designed such  
> that a devices that *did not* understand the semantics of what some  
> data item meant could still merge them. Originally people had the  
> idea that there would be servers that collected up all the local,  
> network, etc profiles for the UA and then merged the data on behalf  
> of the UA then passed the merged result down to the UA. I see no  
> need for theses types of servers.
>
> I see no need for devices that don't understand the semantics of  
> the data to be required to merge the data thus I see no need for  
> the data to have self describing rules about how to merge it. I  
> think it adds complexity and no one has presented a use case where  
> it is useful.
>
> Cullen <with my individual hat on>



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 20 14:33:41 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HexvO-00045A-SK; Fri, 20 Apr 2007 14:33:38 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HexvN-000455-VX for sipping-confirm+ok@megatron.ietf.org;
	Fri, 20 Apr 2007 14:33:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HexvN-00044t-Lm
	for sipping@ietf.org; Fri, 20 Apr 2007 14:33:37 -0400
Received: from hoemail2.lucent.com ([192.11.226.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HexvM-0003XP-AN
	for sipping@ietf.org; Fri, 20 Apr 2007 14:33:37 -0400
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail2.lucent.com (8.13.8/IER-o) with ESMTP id l3KIX3OE005273;
	Fri, 20 Apr 2007 13:33:03 -0500 (CDT)
Received: from [135.180.240.247] (volker-hopc2.dnrc.bell-labs.com
	[135.180.240.247])
	by homail.ho.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l3KIX3n02536; Fri, 20 Apr 2007 14:33:03 -0400 (EDT)
Message-ID: <4629075F.2000500@bell-labs.com>
Date: Fri, 20 Apr 2007 14:33:03 -0400
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Conclusion for merging
References: <4613BFD4.9090107@bell-labs.com>
	<B02B0F6A-A2A8-4929-8623-5902DA5F24CF@cisco.com>
	<BD4376EB-403C-4988-B6AA-1BADA9380EF3@cs.columbia.edu>
	<DABAFEBE-90F5-4A42-A7C6-E4272B6B9171@cisco.com>
	<0B67995C-CFD7-4BFD-8604-3E61AF658CF7@cs.columbia.edu>
In-Reply-To: <0B67995C-CFD7-4BFD-8604-3E61AF658CF7@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 192.11.226.42
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: Cullen Jennings <fluffy@cisco.com>, Martin C Dolly <mdolly@att.com>,
	sipping <sipping@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Henning Schulzrinne wrote:
> I think we agree that "blind" merging is of very little use, since 
> merging two parameters that the client doesn't understand adds little 
> value, except in displaying them to the user.
> 
> However, the question is what the parameter-related spec should say. If 
> the spec does not indicate what a device that knows about bandwidth 
> limits should do, it is likely that two devices will differ in their 
> behavior. Thus, I think the spec has to specify "min(network, local)", 
> say, for this particular parameter. After all, there are other 
> semi-reasonable algorithms, such as picking one of the parameters 
> (override) or the average or maybe even the maximum.
> 
I fully agree! I think a rule for merging should be part of the 
semantics of an element and therefore part of the document spec. It 
should enable a device that has received two documents to generate a set 
of properties it understands and can work with.

I believe this is essentially the approach we have taken in the current 
draft. For each element, there is one merging rule as part of the spec 
that explains what to do if someone receives multiple instance of this 
element. The common merging rules in the framework were an attempt to 
simplify the specification and implementations since many of the rules 
look alike. It was not intended that they are used blindly without 
knowing the semantics of a specific element. I guess this needs to be 
clarified in the draft.

Volker



> Otherwise, a network operator can't rely on what a properly configured 
> device will do. In that case, configuration becomes meaningless and 
> largely useless. Why specify a bandwidth limit if every device treats 
> this differently, in unpredictable fashion?
> 
 >
 > Henning
 >
> On Apr 20, 2007, at 1:36 PM, Cullen Jennings wrote:
> 
>>
>> On Apr 15, 2007, at 7:10 AM, Henning Schulzrinne wrote:
>>
>>>
>>> On Apr 15, 2007, at 1:04 AM, Cullen Jennings wrote:
>>>
>>>>
>>>> There is a third option which I have always been a fan of - 
>>>> basically do 1 below but then in the places where you do want two 
>>>> things, lets say, both local and network can set a max_bandwidth, 
>>>> well you have two things one call local_max_bandwidth and one called 
>>>> network_max_bandwidth. They are both separate fields and the 
>>>> application knows what to do with them.
>>>
>>> Since the application has to obey a single bandwidth limit, the 
>>> application still has to decide that either local_max_bandwidth 
>>> overrides network_max_bandwidth or the result is min(local_, 
>>> network_). If you want predictable behavior, you presumably need to 
>>> standardize which it is.
>>>
>>> Thus, I don't see how this addresses the problem at hand.
>>
>> I am off in the area of angels on a pin head here so forgive me but ....
>>
>> The UA needs to know the semantics of local_max_bandwidth means do not 
>> exceed this. It needs to know the semantics of network_max_bandwidth 
>> means do not exceed this and it need to pay attention to all the 
>> config it received or things may not operate as expected. I do 
>> understand that that a min(a,b) does eventually get solved.
>>
>> The meta point is that only a device that understands the semantics of 
>> these two things needs to try and know what to do with them or how to 
>> "merge" them. I don't think of it is merging, it is just using them. 
>> The merging stuff in the framework was designed such that a devices 
>> that *did not* understand the semantics of what some data item meant 
>> could still merge them. Originally people had the idea that there 
>> would be servers that collected up all the local, network, etc 
>> profiles for the UA and then merged the data on behalf of the UA then 
>> passed the merged result down to the UA. I see no need for theses 
>> types of servers.
>>
>> I see no need for devices that don't understand the semantics of the 
>> data to be required to merge the data thus I see no need for the data 
>> to have self describing rules about how to merge it. I think it adds 
>> complexity and no one has presented a use case where it is useful.
>>
>> Cullen <with my individual hat on>
> 


-- 
Volker Hilt                      Bell Labs / Alcatel-Lucent
phone: +1 732 332 6432           101 Crawfords Corner Rd
email: volkerh@bell-labs.com     Holmdel, NJ 07733


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 20 14:55:17 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeyGE-0001VI-A7; Fri, 20 Apr 2007 14:55:10 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeyGC-0001VD-Ch for sipping-confirm+ok@megatron.ietf.org;
	Fri, 20 Apr 2007 14:55:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeyGC-0001UY-2i
	for sipping@ietf.org; Fri, 20 Apr 2007 14:55:08 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeyGB-00034j-KB
	for sipping@ietf.org; Fri, 20 Apr 2007 14:55:08 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 20 Apr 2007 14:55:08 -0400
X-IronPort-AV: i="4.14,433,1170651600"; 
	d="scan'208"; a="119084407:sNHT366915970"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l3KIt6Z2003253; 
	Fri, 20 Apr 2007 14:55:06 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l3KIt2lU013753; 
	Fri, 20 Apr 2007 18:55:02 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 20 Apr 2007 14:54:56 -0400
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 20 Apr 2007 14:54:56 -0400
Message-ID: <46290C80.9010206@cisco.com>
Date: Fri, 20 Apr 2007 14:54:56 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Conclusion for merging
References: <4613BFD4.9090107@bell-labs.com>	<B02B0F6A-A2A8-4929-8623-5902DA5F24CF@cisco.com>	<BD4376EB-403C-4988-B6AA-1BADA9380EF3@cs.columbia.edu>	<DABAFEBE-90F5-4A42-A7C6-E4272B6B9171@cisco.com>
	<0B67995C-CFD7-4BFD-8604-3E61AF658CF7@cs.columbia.edu>
In-Reply-To: <0B67995C-CFD7-4BFD-8604-3E61AF658CF7@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Apr 2007 18:54:56.0535 (UTC)
	FILETIME=[63696270:01C7837D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4302; t=1177095307;
	x=1177959307; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Conclusion=20for=20merging
	|Sender:=20
	|To:=20Henning=20Schulzrinne=20<hgs@cs.columbia.edu>;
	bh=HnKirFlp51AYRaYw/eCDfCPDjfgqpfm5HJLoKPIo7TI=;
	b=DLXVKcPPjFr1559Prpwi68pOpECNOoMX2+ibvVWx0XdjdckWvnljsGPP3fIV/v8b+tMGO2So
	jE7m2U/vFNOjTD2VKdaT17REi3ON55Lors5SWPF2Z8FxMOChYOWHwsKf;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: Cullen Jennings <fluffy@cisco.com>, Volker Hilt <volkerh@bell-labs.com>,
	sipping <sipping@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	Martin C Dolly <mdolly@att.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I think Cullen and Henning have different conceptualizations of 
equivalent solutions.

What Cullen seems to say is that the UA is faced with a general 
constraint satisfaction problem: it must satisfy both the 
network-bandwidth parameter and the local-bandwidth parameter.

If both of those are maximum bandwidth values, then satisfying both of 
them does indeed mean conforming to the min of them. But you don't have 
to write that down anywhere - it is implicit in the semantics of the 
parameters.

	Paul

Henning Schulzrinne wrote:
> I think we agree that "blind" merging is of very little use, since 
> merging two parameters that the client doesn't understand adds little 
> value, except in displaying them to the user.
> 
> However, the question is what the parameter-related spec should say. If 
> the spec does not indicate what a device that knows about bandwidth 
> limits should do, it is likely that two devices will differ in their 
> behavior. Thus, I think the spec has to specify "min(network, local)", 
> say, for this particular parameter. After all, there are other 
> semi-reasonable algorithms, such as picking one of the parameters 
> (override) or the average or maybe even the maximum.
> 
> Otherwise, a network operator can't rely on what a properly configured 
> device will do. In that case, configuration becomes meaningless and 
> largely useless. Why specify a bandwidth limit if every device treats 
> this differently, in unpredictable fashion?
> 
> Henning
> 
> On Apr 20, 2007, at 1:36 PM, Cullen Jennings wrote:
> 
>>
>> On Apr 15, 2007, at 7:10 AM, Henning Schulzrinne wrote:
>>
>>>
>>> On Apr 15, 2007, at 1:04 AM, Cullen Jennings wrote:
>>>
>>>>
>>>> There is a third option which I have always been a fan of - 
>>>> basically do 1 below but then in the places where you do want two 
>>>> things, lets say, both local and network can set a max_bandwidth, 
>>>> well you have two things one call local_max_bandwidth and one called 
>>>> network_max_bandwidth. They are both separate fields and the 
>>>> application knows what to do with them.
>>>
>>> Since the application has to obey a single bandwidth limit, the 
>>> application still has to decide that either local_max_bandwidth 
>>> overrides network_max_bandwidth or the result is min(local_, 
>>> network_). If you want predictable behavior, you presumably need to 
>>> standardize which it is.
>>>
>>> Thus, I don't see how this addresses the problem at hand.
>>
>> I am off in the area of angels on a pin head here so forgive me but ....
>>
>> The UA needs to know the semantics of local_max_bandwidth means do not 
>> exceed this. It needs to know the semantics of network_max_bandwidth 
>> means do not exceed this and it need to pay attention to all the 
>> config it received or things may not operate as expected. I do 
>> understand that that a min(a,b) does eventually get solved.
>>
>> The meta point is that only a device that understands the semantics of 
>> these two things needs to try and know what to do with them or how to 
>> "merge" them. I don't think of it is merging, it is just using them. 
>> The merging stuff in the framework was designed such that a devices 
>> that *did not* understand the semantics of what some data item meant 
>> could still merge them. Originally people had the idea that there 
>> would be servers that collected up all the local, network, etc 
>> profiles for the UA and then merged the data on behalf of the UA then 
>> passed the merged result down to the UA. I see no need for theses 
>> types of servers.
>>
>> I see no need for devices that don't understand the semantics of the 
>> data to be required to merge the data thus I see no need for the data 
>> to have self describing rules about how to merge it. I think it adds 
>> complexity and no one has presented a use case where it is useful.
>>
>> Cullen <with my individual hat on>
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.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
> 


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 20 16:23:20 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hezcg-0005h1-Na; Fri, 20 Apr 2007 16:22:26 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hezcf-0005f1-Kr for sipping-confirm+ok@megatron.ietf.org;
	Fri, 20 Apr 2007 16:22:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HezEz-0007RM-U8
	for sipping@ietf.org; Fri, 20 Apr 2007 15:57:58 -0400
Received: from hoemail2.lucent.com ([192.11.226.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HezA9-000068-Tu
	for sipping@ietf.org; Fri, 20 Apr 2007 15:53:09 -0400
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail2.lucent.com (8.13.8/IER-o) with ESMTP id l3KJqY6u028818;
	Fri, 20 Apr 2007 14:52:34 -0500 (CDT)
Received: from [135.180.240.247] (volker-hopc2.dnrc.bell-labs.com
	[135.180.240.247])
	by homail.ho.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l3KJqYn17207; Fri, 20 Apr 2007 15:52:34 -0400 (EDT)
Message-ID: <46291A01.5090202@bell-labs.com>
Date: Fri, 20 Apr 2007 15:52:33 -0400
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping] Conclusion for merging
References: <4613BFD4.9090107@bell-labs.com>	<B02B0F6A-A2A8-4929-8623-5902DA5F24CF@cisco.com>	<BD4376EB-403C-4988-B6AA-1BADA9380EF3@cs.columbia.edu>	<DABAFEBE-90F5-4A42-A7C6-E4272B6B9171@cisco.com>	<0B67995C-CFD7-4BFD-8604-3E61AF658CF7@cs.columbia.edu>
	<46290C80.9010206@cisco.com>
In-Reply-To: <46290C80.9010206@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 192.11.226.42
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: Cullen Jennings <fluffy@cisco.com>, Martin C Dolly <mdolly@att.com>,
	sipping <sipping@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	Henning Schulzrinne <hgs@cs.columbia.edu>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I think it is an advantage if this is written down explicitly in the 
document spec. This seems to produce more predictable results than if 
this is left to the interpretation of each implementation.

Also, it seems somewhat complicated to have a format in which the use of 
an element depends on the role the of the document source. It would for 
example require a server to check the profile type used in the 
subscription to find out if it is acting as local, device or user 
profile server and then use the correct elements when building its 
document. Also, some elements would be defined up to three times or more 
if new sources are added.

Volker


Paul Kyzivat wrote:
> I think Cullen and Henning have different conceptualizations of 
> equivalent solutions.
> 
> What Cullen seems to say is that the UA is faced with a general 
> constraint satisfaction problem: it must satisfy both the 
> network-bandwidth parameter and the local-bandwidth parameter.
> 
> If both of those are maximum bandwidth values, then satisfying both of 
> them does indeed mean conforming to the min of them. But you don't have 
> to write that down anywhere - it is implicit in the semantics of the 
> parameters.
> 
>     Paul
> 
> Henning Schulzrinne wrote:
>> I think we agree that "blind" merging is of very little use, since 
>> merging two parameters that the client doesn't understand adds little 
>> value, except in displaying them to the user.
>>
>> However, the question is what the parameter-related spec should say. 
>> If the spec does not indicate what a device that knows about bandwidth 
>> limits should do, it is likely that two devices will differ in their 
>> behavior. Thus, I think the spec has to specify "min(network, local)", 
>> say, for this particular parameter. After all, there are other 
>> semi-reasonable algorithms, such as picking one of the parameters 
>> (override) or the average or maybe even the maximum.
>>
>> Otherwise, a network operator can't rely on what a properly configured 
>> device will do. In that case, configuration becomes meaningless and 
>> largely useless. Why specify a bandwidth limit if every device treats 
>> this differently, in unpredictable fashion?
>>
>> Henning
>>
>> On Apr 20, 2007, at 1:36 PM, Cullen Jennings wrote:
>>
>>>
>>> On Apr 15, 2007, at 7:10 AM, Henning Schulzrinne wrote:
>>>
>>>>
>>>> On Apr 15, 2007, at 1:04 AM, Cullen Jennings wrote:
>>>>
>>>>>
>>>>> There is a third option which I have always been a fan of - 
>>>>> basically do 1 below but then in the places where you do want two 
>>>>> things, lets say, both local and network can set a max_bandwidth, 
>>>>> well you have two things one call local_max_bandwidth and one 
>>>>> called network_max_bandwidth. They are both separate fields and the 
>>>>> application knows what to do with them.
>>>>
>>>> Since the application has to obey a single bandwidth limit, the 
>>>> application still has to decide that either local_max_bandwidth 
>>>> overrides network_max_bandwidth or the result is min(local_, 
>>>> network_). If you want predictable behavior, you presumably need to 
>>>> standardize which it is.
>>>>
>>>> Thus, I don't see how this addresses the problem at hand.
>>>
>>> I am off in the area of angels on a pin head here so forgive me but ....
>>>
>>> The UA needs to know the semantics of local_max_bandwidth means do 
>>> not exceed this. It needs to know the semantics of 
>>> network_max_bandwidth means do not exceed this and it need to pay 
>>> attention to all the config it received or things may not operate as 
>>> expected. I do understand that that a min(a,b) does eventually get 
>>> solved.
>>>
>>> The meta point is that only a device that understands the semantics 
>>> of these two things needs to try and know what to do with them or how 
>>> to "merge" them. I don't think of it is merging, it is just using 
>>> them. The merging stuff in the framework was designed such that a 
>>> devices that *did not* understand the semantics of what some data 
>>> item meant could still merge them. Originally people had the idea 
>>> that there would be servers that collected up all the local, network, 
>>> etc profiles for the UA and then merged the data on behalf of the UA 
>>> then passed the merged result down to the UA. I see no need for 
>>> theses types of servers.
>>>
>>> I see no need for devices that don't understand the semantics of the 
>>> data to be required to merge the data thus I see no need for the data 
>>> to have self describing rules about how to merge it. I think it adds 
>>> complexity and no one has presented a use case where it is useful.
>>>
>>> Cullen <with my individual hat on>
>>
>>
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.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
>>
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.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



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 20 16:28:33 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeziZ-00085S-58; Fri, 20 Apr 2007 16:28:31 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HeziX-00084V-AV for sipping-confirm+ok@megatron.ietf.org;
	Fri, 20 Apr 2007 16:28:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeziW-00084N-WE
	for sipping@ietf.org; Fri, 20 Apr 2007 16:28:29 -0400
Received: from serrano.cc.columbia.edu ([128.59.29.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeziW-0002Wt-LW
	for sipping@ietf.org; Fri, 20 Apr 2007 16:28:28 -0400
Received: from [128.59.23.102] (macmini1.cs.columbia.edu [128.59.23.102])
	(user=hgs10 mech=PLAIN bits=0)
	by serrano.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id l3KKS5Uk015350
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 20 Apr 2007 16:28:07 -0400 (EDT)
In-Reply-To: <46290C80.9010206@cisco.com>
References: <4613BFD4.9090107@bell-labs.com>	<B02B0F6A-A2A8-4929-8623-5902DA5F24CF@cisco.com>	<BD4376EB-403C-4988-B6AA-1BADA9380EF3@cs.columbia.edu>	<DABAFEBE-90F5-4A42-A7C6-E4272B6B9171@cisco.com>
	<0B67995C-CFD7-4BFD-8604-3E61AF658CF7@cs.columbia.edu>
	<46290C80.9010206@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BF7CDFCF-3670-4E1D-A7F4-6B16ED2CD17C@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Sipping] Conclusion for merging
Date: Fri, 20 Apr 2007 16:29:23 -0400
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.6
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: Cullen Jennings <fluffy@cisco.com>, Volker Hilt <volkerh@bell-labs.com>,
	sipping <sipping@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	Martin C Dolly <mdolly@att.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I suspect that there will be relatively few basic operations, just  
like we defined in the common policy. In other words, for numeric  
parameters, there will be either min() or max(), for server selection  
some prioritization (try X first) and for others, there may simply be  
a conflict that can't be resolved mechanically. Thus, labeling the  
classes of things is probably sufficient.

I'm not convinced that implicit semantics are a productive approach.  
We got some of it wrong on first writing in the common policy, after  
all.

On Apr 20, 2007, at 2:54 PM, Paul Kyzivat wrote:

> I think Cullen and Henning have different conceptualizations of  
> equivalent solutions.
>
> What Cullen seems to say is that the UA is faced with a general  
> constraint satisfaction problem: it must satisfy both the network- 
> bandwidth parameter and the local-bandwidth parameter.
>
> If both of those are maximum bandwidth values, then satisfying both  
> of them does indeed mean conforming to the min of them. But you  
> don't have to write that down anywhere - it is implicit in the  
> semantics of the parameters.
>
> 	Paul
>
> Henning Schulzrinne wrote:
>> I think we agree that "blind" merging is of very little use, since  
>> merging two parameters that the client doesn't understand adds  
>> little value, except in displaying them to the user.
>> However, the question is what the parameter-related spec should  
>> say. If the spec does not indicate what a device that knows about  
>> bandwidth limits should do, it is likely that two devices will  
>> differ in their behavior. Thus, I think the spec has to specify  
>> "min(network, local)", say, for this particular parameter. After  
>> all, there are other semi-reasonable algorithms, such as picking  
>> one of the parameters (override) or the average or maybe even the  
>> maximum.
>> Otherwise, a network operator can't rely on what a properly  
>> configured device will do. In that case, configuration becomes  
>> meaningless and largely useless. Why specify a bandwidth limit if  
>> every device treats this differently, in unpredictable fashion?
>> Henning
>> On Apr 20, 2007, at 1:36 PM, Cullen Jennings wrote:
>>>
>>> On Apr 15, 2007, at 7:10 AM, Henning Schulzrinne wrote:
>>>
>>>>
>>>> On Apr 15, 2007, at 1:04 AM, Cullen Jennings wrote:
>>>>
>>>>>
>>>>> There is a third option which I have always been a fan of -  
>>>>> basically do 1 below but then in the places where you do want  
>>>>> two things, lets say, both local and network can set a  
>>>>> max_bandwidth, well you have two things one call  
>>>>> local_max_bandwidth and one called network_max_bandwidth. They  
>>>>> are both separate fields and the application knows what to do  
>>>>> with them.
>>>>
>>>> Since the application has to obey a single bandwidth limit, the  
>>>> application still has to decide that either local_max_bandwidth  
>>>> overrides network_max_bandwidth or the result is min(local_,  
>>>> network_). If you want predictable behavior, you presumably need  
>>>> to standardize which it is.
>>>>
>>>> Thus, I don't see how this addresses the problem at hand.
>>>
>>> I am off in the area of angels on a pin head here so forgive me  
>>> but ....
>>>
>>> The UA needs to know the semantics of local_max_bandwidth means  
>>> do not exceed this. It needs to know the semantics of  
>>> network_max_bandwidth means do not exceed this and it need to pay  
>>> attention to all the config it received or things may not operate  
>>> as expected. I do understand that that a min(a,b) does eventually  
>>> get solved.
>>>
>>> The meta point is that only a device that understands the  
>>> semantics of these two things needs to try and know what to do  
>>> with them or how to "merge" them. I don't think of it is merging,  
>>> it is just using them. The merging stuff in the framework was  
>>> designed such that a devices that *did not* understand the  
>>> semantics of what some data item meant could still merge them.  
>>> Originally people had the idea that there would be servers that  
>>> collected up all the local, network, etc profiles for the UA and  
>>> then merged the data on behalf of the UA then passed the merged  
>>> result down to the UA. I see no need for theses types of servers.
>>>
>>> I see no need for devices that don't understand the semantics of  
>>> the data to be required to merge the data thus I see no need for  
>>> the data to have self describing rules about how to merge it. I  
>>> think it adds complexity and no one has presented a use case  
>>> where it is useful.
>>>
>>> Cullen <with my individual hat on>
>> _______________________________________________
>> Sipping mailing list  https://www1.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



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sat Apr 21 01:08:44 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hf7pq-00072N-Sg; Sat, 21 Apr 2007 01:08:34 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hf7pp-00070E-Ay for sipping-confirm+ok@megatron.ietf.org;
	Sat, 21 Apr 2007 01:08:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hf7po-0006ze-RI; Sat, 21 Apr 2007 01:08:32 -0400
Received: from fw21above.mobilkom.at ([194.48.128.75]
	helo=srvmxtreme1.mobilkom.at)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hf7po-0003ac-4q; Sat, 21 Apr 2007 01:08:32 -0400
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: Sat, 21 Apr 2007 07:07:17 +0200
Message-ID: <03972E773D99AF4680D5DD84E6E2ABB010365CF7@ntxms01.ms.mobilkom.at>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Geopriv] Location Presence Event Package
Thread-Index: Acd6a/HMn5cHW6ybTY6l4vF+LYIT6QAKy53gAkz0tNA=
From: "Pailer Rudolf" <r.pailer@mobilkom.at>
To: "Brian Rosen" <br@brianrosen.net>, <sipping@ietf.org>, <geopriv@ietf.org>
Received-SPF: none
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
Cc: 
Subject: [Sipping] AW: [Geopriv] Location Presence Event Package
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hello Brian!
=20
Sorry, that it took me some time to reply to your mail.
=20
We looked at RFC 4660 that defines event notification filters for
presence, but did not see a feasibile way to express the following rule:
"Send a notification, if the presentity enters an area (e.g. specified
by a circle (center point + radius) or a rectangle)."
There was e.g. the proposal in our research group to use presence event
filters in the following way:
<changed from=3D"-67.563 -13.834" by=3D"0.2 0.2">
We think that such a notation is highly ambigous and will lead to
interoperability problems.
=20
RFC 4660 builds on the assumtion that the state space of presence is
restricted to a few logical states that can be filtered by a boolean
combination of filter rules. The location presence event package
notifies on geographical positions, that have an (nearly infinite) state
space. Combining geograhical shapes in boolean terms and calculating if
the presentity is now inside/outside of this area is not feasible on
mobile devices with restricted computation resources.

Therfore we propose to use some different kind of filtering approach
(see
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-loc-filters-01.tx
t).

Now there is the question, why not to use geopriv-loc-filters inside the
presence package:
Our main goal is to route SIP SUBSCRIBE messages containing
geopriv-loc-filters documents from the watcher to the presentity. The
location presence event package is targeted at mobile devices and we
argue that filters have to be executed on the mobile device (otherwise
you will no be able to restrict the number of notification messages on
the radio interface). This means that the subscription cannot be
processed by a (conventional) presence server in the network, but has to
be routed to the mobile phone of the user (but only to those mobile
phones, that have an edge presence server running).
Location presence subscriptions and notifications are processed by
different nodes than conventional presence. The scale of location
presence data may be significatly different to conventional presence.
This means that SUBCRIBE and NOTIFY messages have to take different
paths in the network and will be processed by different nodes than
conventional presence.
We thus discussed several methods, to differentiate the routing of
conventional presence to location presence:
	1) Introduce another URI-scheme. This does not seem to be as
elegent as the introduction of the locpres event package.
	2) The edge presence server on the mobile device registers with
an own SIP URI. This requires a lot of a priori knowledge of the
watcher.
	3) define an own event package - we favored this solution

The idea of the locpres event package is, that it uses the same
framework than conventional presence (e.g. for user profiles, policy
decisions etc.), but that it indicates that this type of presence has to
be routed and processed differently than conventional presence.=20
Thus SIP routing of initial SUBCRIBE messages can be based on the
content "locpres" of the SIP Event header field. This solution seems to
integrate well in the existing SIP presence framework and general SIP
specifications. Presence user agents can for example use the "Watcher
Information Event Template-Package" [RFC 3857]. This means that the
Presence User Agent can subscribe to "locpres.winfo" notifications in
order to be notified about changes in the subscription state regarding
locpres events.=20
Furthermore [RFC 3840] introduces "User Agent Capabilities" in form of
feature tags that can be conveyed in form of parameters in the Contact
header field to other user agents and registrars. In particular a
Contact header with the sip.event media tag containing a value of
"locpres" can be used by a Presence User Agent to indicate that
subscriptions for location presence data shall be routed to this
address. Sip.event feature tag parameters are also used in [RFC 3841]
that defines the notion of "caller preferences" about request handling
in servers. These preferences include the ability to select which
Uniform Resource Identifiers (URI) a request gets routed to, and to
specify certain request handling directives in proxies and redirect
servers. Again a value of "locpres" in a sip.event media feature tag can
be used by a presence server to route a subscription for location
presence data to the responsible edge presence server or state agent.

greetings
Rudolf

________________________________

Von: Brian Rosen [mailto:br@brianrosen.net]=20
Gesendet: Montag, 09. April 2007 13:35
An: Pailer Rudolf; sipping@ietf.org; geopriv@ietf.org
Betreff: RE: [Geopriv] Location Presence Event Package



I've read this, and I don't really understand why real presence (with
the filter package) doesn't provide the same service.

Can you give an example where presence+filter is significantly different
from this package, with the filter inclusion?   It seems to me that you
get roughly the same number of messages, with roughly the same content.

=20

Brian

=20

________________________________

From: Pailer Rudolf [mailto:r.pailer@mobilkom.at]=20
Sent: Monday, April 09, 2007 1:57 AM
To: sipping@ietf.org; geopriv@ietf.org
Subject: [Geopriv] Location Presence Event Package

=20

Hello!=20

I would like to notify you about the the Internet Draft "A Location
Presence Event Package for the Session Initiation Protocol (SIP)".

http://www.ietf.org/internet-drafts/draft-pailer-locpres-00.txt
<http://www.ietf.org/internet-drafts/draft-pailer-locpres-00.txt> =20

The draft describes the usage of the Session Initiation Protocol (SIP)
for subscriptions and notifications of location presence. Location
presence is information about the geographical position of a user.
Subscriptions and notifications of location presence are supported by
defining an event package within the general SIP event notification
framework.

The concept of a SIP based location enabler that is the core of the
proposed draft was published on several occasions:=20
*) A Terminal-Based Location Service Enabler for the IP Multimedia
Subsystem, R. Pailer, S. Bessler, F. Wegscheider, IEEE Wireless
Communications and Networking Conference April 2006 (WCNC06), Las Vegas,
USA

*) Terminal-Centric Location Services for the IP Multimedia Subsystem,
J. Fabini, M. Happenhofer, R. Pailer, IEEE 63rd Vehicular Technology
Conference, May 2006, Melbourne, Australia

*) Implementing a Native IMS Location Service Enabler over a
Prototypical IMS Core Network Testbed, P. Reichl, S. Bessler, J. Fabini,
R. Pailer, J. Zeiss,The Third IEEE International Workshop on Mobile
Commerce and Wireless Services (WMCS'06) June 26, 2006, San Francisco,
USA

*) Practical Experiences with an IMS-Aware Location Service Enabler on
Top of an Experimental Open Source IMS Core Implementation, P. Reichl,
S. Bessler, J. Fabini, R. Pailer, A. Poropatich, N. Jordan, R. Huber, H.
Weisgrab, C. Brandner, I. Gojmerac, M. Ries, F. Wegscheider, Journal of
Mobile Multimedia, Rinton Press, Fall 2006

*) Lecture Notes in Geoinformation and Cartography, Location Based
Services an TeleCartography, G. Gartner, W. Cartwright, M. P. Peterson
(Eds.), Springer, 2007

I can provide above documents in PDF format, if needed.=20

Feedback from the IETF Working Groups GEOPRIV and SIPPING would be
appreciated very much indeed.=20

greetings=20
Rudolf=20



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sat Apr 21 01:23:21 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hf843-00070J-8o; Sat, 21 Apr 2007 01:23:15 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hf841-000708-N7 for sipping-confirm+ok@megatron.ietf.org;
	Sat, 21 Apr 2007 01:23:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hf841-0006zx-9P; Sat, 21 Apr 2007 01:23:13 -0400
Received: from fw21above.mobilkom.at ([194.48.128.75]
	helo=srvmxtreme1.mobilkom.at)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hf83y-00082I-Ja; Sat, 21 Apr 2007 01:23:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: [Sipping] RE: [Geopriv] Location Presence Event Package
Date: Sat, 21 Apr 2007 07:22:34 +0200
Message-ID: <03972E773D99AF4680D5DD84E6E2ABB010365CF8@ntxms01.ms.mobilkom.at>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] RE: [Geopriv] Location Presence Event Package
Thread-Index: Acd6q/OTnMFFUzf6TvS6Bvi+C8OOewJJxwnQ
From: "Pailer Rudolf" <r.pailer@mobilkom.at>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Brian Rosen" <br@brianrosen.net>
Received-SPF: none
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: geopriv@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hello Paul!

Please see my reply to Brian's posting regarding the routing of =
subscriptions and notifications for loaction presence.
Location Presence scales differently than conventional presence and =
different nodes need to process subscriptions for location presence. We =
were thus looking for a way to differentiate the routing of locpres SIP =
messages from conventional presence and do propose to use an own event =
package to do so.

Regading the number of watchers:
In the scientific papers that we published on the topic of location =
presence, we introduced a node called 'WatcherLister Server'. This =
server deals with a list of watchers that all subscribe to the same =
event. We did not include this idea in the location presence draft. The =
reason for this is, that we think that the specification of a 'Watcher =
List Server' would be a generic addtion to the SIP presence framework =
rather than something only valid for location presence. Therefore a =
'Watcher List Server' should be specified in an own draft/RFC.

greetings
Rudolf


-----Urspr=FCngliche Nachricht-----
Von: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
Gesendet: Montag, 09. April 2007 15:35
An: Brian Rosen
Cc: Pailer Rudolf; sipping@ietf.org; geopriv@ietf.org
Betreff: Re: [Sipping] RE: [Geopriv] Location Presence Event Package

Like Brian I think this seems so close to existing presence that you=20
need to work harder to make the case for something different, and to=20
show how the two packages would be coordinated.

It appears to me that a major goal you have is to avoid sending out=20
messages as a result of movement when there are no watchers that are=20
interested in that movement. While I can see how that could be helpful=20
in some cases, it needs to be reconciled with the resulting need to=20
manage subscriptions from what could be a large number of watchers.

In any case, I think what you suggest could be achieved by introducing=20
some special filters for geoloc information into standard presence. At=20
least that would work when there is no separate presence aggregator.

	Paul

Brian Rosen wrote:
> I've read this, and I don't really understand why real presence (with=20
> the filter package) doesn't provide the same service.
>=20
> Can you give an example where presence+filter is significantly =
different=20
> from this package, with the filter inclusion?   It seems to me that =
you=20
> get roughly the same number of messages, with roughly the same =
content.
>=20
> =20
>=20
> Brian
>=20
> =20
>=20
> =
------------------------------------------------------------------------
>=20
> *From:* Pailer Rudolf [mailto:r.pailer@mobilkom.at]
> *Sent:* Monday, April 09, 2007 1:57 AM
> *To:* sipping@ietf.org; geopriv@ietf.org
> *Subject:* [Geopriv] Location Presence Event Package
>=20
> =20
>=20
> Hello!
>=20
> I would like to notify you about the the Internet Draft "A Location=20
> Presence Event Package for the Session Initiation Protocol (SIP)".
>=20
> http://www.ietf.org/internet-drafts/draft-pailer-locpres-00.txt
>=20
> The draft describes the usage of the Session Initiation Protocol (SIP) =

> for subscriptions and notifications of location presence. Location=20
> presence is information about the geographical position of a user. =20
> Subscriptions and notifications of location presence are supported by=20
> defining an event package within the general SIP event notification=20
> framework.
>=20
> The concept of a SIP based location enabler that is the core of the=20
> proposed draft was published on several occasions:
> *) A Terminal-Based Location Service Enabler for the IP Multimedia=20
> Subsystem, R. Pailer, S. Bessler, F. Wegscheider, IEEE Wireless=20
> Communications and Networking Conference April 2006 (WCNC06), Las =
Vegas, USA
>=20
> *) Terminal-Centric Location Services for the IP Multimedia Subsystem, =

> J. Fabini, M. Happenhofer, R. Pailer, IEEE 63rd Vehicular Technology=20
> Conference, May 2006, Melbourne, Australia
>=20
> *) Implementing a Native IMS Location Service Enabler over a=20
> Prototypical IMS Core Network Testbed, P. Reichl, S. Bessler, J. =
Fabini,=20
> R. Pailer, J. Zeiss,The Third IEEE International Workshop on Mobile=20
> Commerce and Wireless Services (WMCS'06) June 26, 2006, San Francisco, =
USA
>=20
> *) Practical Experiences with an IMS-Aware Location Service Enabler on =

> Top of an Experimental Open Source IMS Core Implementation, P. Reichl, =

> S. Bessler, J. Fabini, R. Pailer, A. Poropatich, N. Jordan, R. Huber, =
H.=20
> Weisgrab, C. Brandner, I. Gojmerac, M. Ries, F. Wegscheider, Journal =
of=20
> Mobile Multimedia, Rinton Press, Fall 2006
>=20
> *) Lecture Notes in Geoinformation and Cartography, Location Based=20
> Services an TeleCartography, G. Gartner, W. Cartwright, M. P. Peterson =

> (Eds.), Springer, 2007
>=20
> I can provide above documents in PDF format, if needed.
>=20
> Feedback from the IETF Working Groups GEOPRIV and SIPPING would be=20
> appreciated very much indeed.
>=20
> greetings
> Rudolf
>=20
>=20
> =
------------------------------------------------------------------------
>=20
> _______________________________________________
> Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 23 09:30:43 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hfych-0000Rg-Ok; Mon, 23 Apr 2007 09:30:31 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hfycg-0000QX-7X for sipping-confirm+ok@megatron.ietf.org;
	Mon, 23 Apr 2007 09:30:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hfycf-0000PP-Sy
	for sipping@ietf.org; Mon, 23 Apr 2007 09:30:29 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hfyce-0003k7-9e
	for sipping@ietf.org; Mon, 23 Apr 2007 09:30:29 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9730E2011A; Mon, 23 Apr 2007 15:30:27 +0200 (CEST)
X-AuditID: c1b4fb3e-af9eebb0000061ca-36-462cb4f347a4 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7F8162010E; Mon, 23 Apr 2007 15:30:27 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Apr 2007 15:30:27 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Apr 2007 15:30:27 +0200
Received: from [131.160.36.33] (E000FB0F665DD.lmf.ericsson.se [131.160.36.33])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id E368B2358;
	Mon, 23 Apr 2007 16:30:26 +0300 (EEST)
Message-ID: <462CB4F1.1020905@ericsson.com>
Date: Mon, 23 Apr 2007 16:30:25 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Apr 2007 13:30:27.0265 (UTC)
	FILETIME=[8E0FCB10:01C785AB]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: Mary Barnes <mary.barnes@nortel.com>
Subject: [Sipping] WGLC: draft-ietf-sipping-race-examples-01.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Folks,

we would like to WGLC the following draft:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-race-examples-01.txt

This WGLC will end on May 14th, as you can see at:

http://www.softarmor.com/sipping/process/wg-review/sipping-rt-wglc.html

We already have one volunteer to review this draft. We would like to 
get, at least, two more reviewers. If you would like to perform a 
dedicated review of this draft, please contact the chairs. If you do not 
want to perform a formal review but still have comments on the draft, 
please post them to the list.

Thanks,

Gonzalo
SIPPING co-chair


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 23 10:04:07 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hfz9B-0003S6-Lv; Mon, 23 Apr 2007 10:04:05 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hfz9A-0003OJ-Kk for sipping-confirm+ok@megatron.ietf.org;
	Mon, 23 Apr 2007 10:04:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hfz9A-0003ML-9m
	for sipping@ietf.org; Mon, 23 Apr 2007 10:04:04 -0400
Received: from mail44.opentransfer.com ([76.162.254.44])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hfz98-0006zN-TN
	for sipping@ietf.org; Mon, 23 Apr 2007 10:04:04 -0400
Received: (qmail 29884 invoked by uid 399); 23 Apr 2007 14:04:01 -0000
Received: from unknown (HELO ?192.168.0.40?) (24.107.197.43)
	by mail44.opentransfer.com with SMTP; 23 Apr 2007 14:04:01 -0000
Message-ID: <462CBCD1.1070706@sipstation.com>
Date: Mon, 23 Apr 2007 09:04:01 -0500
From: Alan Johnston <alan@sipstation.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Subject: Re: [Sipping] WGLC  of draft-ietf-sipping-service-examples-10.txt
References: <000f01c7626d$7aa3f030$0601a8c0@BEMBUSTER>
	<45F19BBC.3030405@alcatel-lucent.com>
In-Reply-To: <45F19BBC.3030405@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi Vijay,

Thanks for your comments and review of the document.

I try to only use the <allOneLine> when there is no choice - if there is 
an option to use LWS then I use it as I think it is more clear.  I plan 
to leave it as is in the draft.

Thanks,
Alan


Vijay K. Gurbani wrote:
> Gonzalo Camarillo wrote:
>> Dear reviewers of the service examples draft,
>>
>> the authors have submitted yet another revision of the draft that is
>> supposed to address your last set of comments on revision 11. As in
>> previous occasions, could you please have a look at it and send a note
>> to the SIPPING mailing list, cc:ing the chairs, stating whether or not
>> you are now OK with the draft?
>
> In -12 I looked at sections 2.1 and 2.2 assigned to me.  They
> are fine.
>
> However, I did notice one thing - in many of the SIP signaling
> messages, the Via field is displayed as:
>
>      Via: SIP/2.0/TLS ss1.example.com:5061
>        ;branch=z9hG4bK83749.1
>        ;received=192.0.2.54
>
> Syntactically, this is perfect; no problem.  However, I will
> leave it to the editor to decide whether he should move the
> "received" parameter one line up, and whether, for the sake of
> orthogonality with other SIP*-documents, he should use the <allOneLine>
> directive established by RjS.
>
> Besides this minor feedback, which can the editor can choose to
> ignore in the interest of getting the draft out expeditiously,
> I am fine with my sections of the draft as they appear in -12.
>
> - vijay



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 23 10:08:47 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HfzDj-0007bD-It; Mon, 23 Apr 2007 10:08:47 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HfzDh-0007aw-In for sipping-confirm+ok@megatron.ietf.org;
	Mon, 23 Apr 2007 10:08:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HfzDh-0007ao-99
	for sipping@ietf.org; Mon, 23 Apr 2007 10:08:45 -0400
Received: from mail44.opentransfer.com ([76.162.254.44])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HfzDf-0008Eo-JG
	for sipping@ietf.org; Mon, 23 Apr 2007 10:08:45 -0400
Received: (qmail 11049 invoked by uid 399); 23 Apr 2007 14:08:42 -0000
Received: from unknown (HELO ?192.168.0.40?) (24.107.197.43)
	by mail44.opentransfer.com with SMTP; 23 Apr 2007 14:08:42 -0000
Message-ID: <462CBDEA.5070500@sipstation.com>
Date: Mon, 23 Apr 2007 09:08:42 -0500
From: Alan Johnston <alan@sipstation.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Jeroen van Bemmel <jbemmel@zonnet.nl>
Subject: Re: [Sipping] WGLC  of draft-ietf-sipping-service-examples-10.txt
References: <000f01c7626d$7aa3f030$0601a8c0@BEMBUSTER>
In-Reply-To: <000f01c7626d$7aa3f030$0601a8c0@BEMBUSTER>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: e16ce0269ccb2f59707d16700199d13b
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi Jeroen,

Thanks for your comments - I will make the corrections.

Thanks,
Alan

Jeroen van Bemmel wrote:
> 2.12 find me (was 2.13):
>  
> all previous 6 comments resolved, 2 new ones introduced:
>  
> - F14 top Via is missing a 'received' parameter
> - F15 (ACK) has an incorrect Via branch (should be z9hG4bK83749.3)
>  
> Regards,
> Jeroen
>  
>
>     ----- Original Message -----
>     *From:* Ravipati, Chandra (Chandra) <mailto:ravipati@avaya.com>
>     *To:* joel.repiquet@tech-invite.com
>     <mailto:joel.repiquet@tech-invite.com> ; Gonzalo Camarillo
>     <mailto:Gonzalo.Camarillo@ericsson.com> ; sipping@ietf.org
>     <mailto:sipping@ietf.org>
>     *Cc:* vkg@lucent.com <mailto:vkg@lucent.com> ;
>     john.elwell@siemens.com <mailto:john.elwell@siemens.com> ;
>     bvnkumar@gmail.com <mailto:bvnkumar@gmail.com> ;
>     dworley@pingtel.com <mailto:dworley@pingtel.com> ;
>     jbemmel@zonnet.nl <mailto:jbemmel@zonnet.nl> ; eburger@cantata.com
>     <mailto:eburger@cantata.com> ; Miguel.An.Garcia@nokia.com
>     <mailto:Miguel.An.Garcia@nokia.com> ; Mary Barnes
>     <mailto:mary.barnes@nortel.com> ; Alan Johnston
>     <mailto:alan@sipstation.com> ; Robert Sparks
>     <mailto:RjS@estacado.net> ; kevin.summers@prodeasystems.com
>     <mailto:kevin.summers@prodeasystems.com> ; Cullen Jennings
>     <mailto:fluffy@cisco.com> ; Jon Peterson
>     <mailto:jon.peterson@neustar.biz>
>     *Sent:* Friday, March 09, 2007 12:05 AM
>     *Subject:* RE: [Fwd: WGLC of
>     draft-ietf-sipping-service-examples-10.txt]
>
>     2.10 and 2.11 look fine to me.
>
>      
>
>     Thanks,
>
>     -Chandra.
>
>     ------------------------------------------------------------------------
>
>     *From:* Joel Repiquet [mailto:joel.repiquet@tech-invite.com]
>     *Sent:* Monday, March 05, 2007 6:41 AM
>     *To:* Gonzalo Camarillo
>     *Cc:* vkg@lucent.com <mailto:vkg@lucent.com>;
>     john.elwell@siemens.com <mailto:john.elwell@siemens.com>;
>     joel.repiquet@tech-invite.com
>     <mailto:joel.repiquet@tech-invite.com>; bvnkumar@gmail.com
>     <mailto:bvnkumar@gmail.com>; Ravipati, Chandra (Chandra);
>     dworley@pingtel.com <mailto:dworley@pingtel.com>;
>     jbemmel@zonnet.nl <mailto:jbemmel@zonnet.nl>; eburger@cantata.com
>     <mailto:eburger@cantata.com>; Miguel.An.Garcia@nokia.com
>     <mailto:Miguel.An.Garcia@nokia.com>; Mary Barnes; Alan Johnston;
>     Robert Sparks; kevin.summers@prodeasystems.com
>     <mailto:kevin.summers@prodeasystems.com>; Cullen Jennings; Jon
>     Peterson
>     *Subject:* Re: [Fwd: WGLC of
>     draft-ietf-sipping-service-examples-10.txt]
>
>      
>
>     Hi,
>     It is OK to me regarding examples 2.4, 2.5 and 2.6 related to
>     Transfer.
>     BR
>     Joel
>
>
>
>     *On Sam Mar 3 13:46 , Gonzalo Camarillo sent:
>
>
>     *
>
>     Dear reviewers of the service examples draft,
>
>     the authors have submitted yet another revision of the draft that is
>     supposed to address your last set of comments on revision 11. As in
>     previous occasions, could you please have a look at it and send a
>     note
>     to the SIPPING mailing list, cc:ing the chairs, stating whether or
>     not
>     you are now OK with the draft?
>
>     http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-examples-12.txt
>
>     For your convenience, your reviews are stored at:
>
>     http://www.softarmor.com/sipping/process/wg-review/sipping-rt-wglc.html
>
>     The diff between revisions 11 and 12 is available at:
>
>     http://tools.ietf.org/wg/sipping/draft-ietf-sipping-service-examples/draft-ietf-sipping-service-examples-12-from-11.diff.html
>
>     Thanks,
>
>     Gonzalo
>
>
>     Gonzalo Camarillo wrote:
>     > Dear reviewers of the service examples draft,
>     >
>     > the authors of the draft have submitted a new revision of the
>     draft that
>     > is supposed to address all your WGLC comments. Could you please
>     have a
>     > look at it and send a note to the SIPPING mailing list, cc:ing the
>     > chairs, stating whether or not you are now OK with the draft?
>     >
>     > http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-examples-11.txt
>     <parse.pl?redirect=http%3A%2F%2Fwww.ietf.org%2Finternet-drafts%2Fdraft-ietf-sipping-service-examples-11.txt>
>     >
>     >
>     > For your convenience, your reviews are stored at:
>     > http://www.softarmor.com/sipping/process/wg-review/sipping-rt-wglc.html
>     <parse.pl?redirect=http%3A%2F%2Fwww.softarmor.com%2Fsipping%2Fprocess%2Fwg-review%2Fsipping-rt-wglc.html>
>     >
>     > Thanks,
>     >
>     > Gonzalo
>     >
>     > Gonzalo Camarillo wrote:
>     >> Hi,
>     >>
>     >> all of you in the 'To' field of this email have volunteered to
>     review
>     >> the service examples draft. Thanks a lot for agreeing to perform
>     this
>     >> review.
>     >>
>     >> This is how we would like to divide the work: in the list below,
>     I have
>     >> assigned a few sections to each of the reviewers. When you are
>     done with
>     >> your review, send it in a reply-to-all to the email below, which
>     was the
>     >> WGLC for this draft on the SIPPING mailing list. We would like
>     to have
>     >> all the reviews ready by the end of the WGLC, on July 1st.
>     >>
>     >>
>     >> <vkg@lucent.com
>     <javascript:top.opencompose('vkg@lucent.com','','','')>>
>     >> 2.1. Call Hold
>     >> 2.2. Consultation Hold
>     >>
>     >> <john.elwell@siemens.com
>     <javascript:top.opencompose('john.elwell@siemens.com','','','')>>
>     >> 2.3. Music On Hold
>     >> 2.18. Automatic Redial
>     >> 2.19. Click to Dial
>     >>
>     >> <joel.repiquet@tech-invite.com
>     <javascript:top.opencompose('joel.repiquet@tech-invite.com','','','')>>
>     >> 2.4. Transfer - Unattended
>     >> 2.5. Transfer - Attended
>     >> 2.6. Transfer - Instant Messaging
>     >>
>     >> <bvnkumar@gmail.com
>     <javascript:top.opencompose('bvnkumar@gmail.com','','','')>>
>     >> 2.7. Call Forwarding Unconditional
>     >> 2.8. Call Forwarding - Busy
>     >> 2.9. Call Forwarding - No Answer
>     >>
>     >> <ravipati@avaya.com
>     <javascript:top.opencompose('ravipati@avaya.com','','','')>>
>     >> 2.10. 3-way Conference - Third Party is Added
>     >> 2.11. 3-way Conference - Third Party Joins
>     >>
>     >> <eburger@cantata.com
>     <javascript:top.opencompose('eburger@cantata.com','','','')>>
>     >> 2.12. Single Line Extension
>     >>
>     >> <jbemmel@zonnet.nl
>     <javascript:top.opencompose('jbemmel@zonnet.nl','','','')>>
>     >> 2.13. Find-Me
>     >>
>     >> <Miguel.An.Garcia@nokia.com
>     <javascript:top.opencompose('Miguel.An.Garcia@nokia.com','','','')>>
>     >> 2.14. Call Management (Incoming Call Screening)
>     >> 2.15. Call Management (Outgoing Call Screening)
>     >>
>     >> <dworley@pingtel.com
>     <javascript:top.opencompose('dworley@pingtel.com','','','')>>
>     >> 2.16. Call Park
>     >> 2.17. Call Pickup
>     >>
>     >>
>     >> Thanks,
>     >>
>     >> Gonzalo
>     >>
>     >>
>     >>
>     >> -------- Original Message --------
>     >> Subject: WGLC of draft-ietf-sipping-service-examples-10.txt
>     >> Date: Thu, 11 May 2006 20:37:40 +0300
>     >> From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com
>     <javascript:top.opencompose('Gonzalo.Camarillo@ericsson.com','','','')>>
>     >> To: sipping <sipping@ietf.org
>     <javascript:top.opencompose('sipping@ietf.org','','','')>>
>     >> CC: Samuli Pöykkö <samuli.poykko@hut.fi
>     <javascript:top.opencompose('samuli.poykko@hut.fi','','','')>>,
>     Mary Barnes
>     >> <mary.barnes@nortel.com
>     <javascript:top.opencompose('mary.barnes@nortel.com','','','')>>,
>     Alan Johnston <alan@sipstation.com
>     <javascript:top.opencompose('alan@sipstation.com','','','')>>, Robert
>     >> Sparks <RjS@estacado.net
>     <javascript:top.opencompose('RjS@estacado.net','','','')>>,
>     kevin.summers@sonusnet.com
>     <javascript:top.opencompose('kevin.summers@sonusnet.com','','','')>
>     >>
>     >> Folks,
>     >>
>     >> we would like to working group last call (WGLC) the following draft:
>     >>
>     >>
>     http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-examples-10.txt
>     <parse.pl?redirect=http%3A%2F%2Fwww.ietf.org%2Finternet-drafts%2Fdraft-ietf-sipping-service-examples-10.txt>
>     >>
>     >>
>     >> as you have probably noticed if you clicked on the link above,
>     this is a
>     >> very long draft. Therefore, we would like to get at least ten
>     volunteers
>     >> to review it. We will assign a couple of sections to each reviewer.
>     >>
>     >> If you are interested and willing to review this draft, please
>     send an
>     >> email to the SIPPING chairs.
>     >>
>     >> The email below should be considered as a WGLC comment:
>     >>
>     >>
>     http://www1.ietf.org/mail-archive/web/sipping/current/msg10886.html
>     <parse.pl?redirect=http%3A%2F%2Fwww1.ietf.org%2Fmail-archive%2Fweb%2Fsipping%2Fcurrent%2Fmsg10886.html>
>     >>
>     >> This is the output of the idnits tool:
>     >>
>     >> idnits 1.96
>     >>
>     >> tmp/draft-ietf-sipping-service-examples-10.txt:
>     >>
>     >>
>     >> Checking nits according to http://www.ietf.org/ID-Checklist.html
>     <parse.pl?redirect=http%3A%2F%2Fwww.ietf.org%2FID-Checklist.html>:
>     >>
>     >> Checking conformance with RFC 3978/3979 boilerplate...
>     >>
>     >> the boilerplate looks good.
>     >>
>     >> * There is 1 instance of too long lines in the document, the
>     longest
>     >> one
>     >> being 1 character in excess of 72.
>     >>
>     >> Checking nits according to
>     http://www.ietf.org/ietf/1id-guidelines.txt
>     <parse.pl?redirect=http%3A%2F%2Fwww.ietf.org%2Fietf%2F1id-guidelines.txt>:
>     >> Nothing found here (but these checks do not cover all of
>     >> 1id-guidelines.txt yet).
>     >>
>     >> Miscellaneous warnings:
>     >> - Line 1028 has weird spacing: '... /* Bob place...'
>     >> - Line 1404 has weird spacing: '... /* Bob takes...'
>     >> - Line 1732 has weird spacing: '... /* Bob place...'
>     >> - Line 2459 has weird spacing: '...and Bob have ...'
>     >> - Line 2597 has weird spacing: '... /* Bob puts ...'
>     >> - (4 more instances...)
>     >>
>     >> Experimental warnings:
>     >> - Unused Reference: [18] is defined on line 7860, but not referenced
>     >> - Unused Reference: [13] is defined on line 7839, but not referenced
>     >> - Unused Reference: [14] is defined on line 7842, but not referenced
>     >> - Unused Reference: [1] is defined on line 7795, but not referenced
>     >>
>     >>
>     >>
>     >>
>     >> This WGLC will end on July 1st, 2006 (a long draft needs a long
>     WGLC).
>     >>
>     >> Thanks,
>     >>
>     >> Gonzalo
>     >> SIPPING co-chair
>     >>
>     >>
>     >>
>     >
>     >
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Sipping mailing list  https://www1.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



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 23 11:15:54 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg0Ga-0007Ce-F7; Mon, 23 Apr 2007 11:15:48 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hg0GX-0007BN-PP for sipping-confirm+ok@megatron.ietf.org;
	Mon, 23 Apr 2007 11:15:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg0GX-0007BF-Fh
	for sipping@ietf.org; Mon, 23 Apr 2007 11:15:45 -0400
Received: from mail44.opentransfer.com ([76.162.254.44])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hg0GV-0006zp-Lg
	for sipping@ietf.org; Mon, 23 Apr 2007 11:15:45 -0400
Received: (qmail 5699 invoked by uid 399); 23 Apr 2007 15:15:38 -0000
Received: from unknown (HELO ?192.168.0.40?) (24.107.197.43)
	by mail44.opentransfer.com with SMTP; 23 Apr 2007 15:15:38 -0000
Message-ID: <462CCD97.9030206@sipstation.com>
Date: Mon, 23 Apr 2007 10:15:35 -0500
From: Alan Johnston <alan@sipstation.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.An.Garcia@nokia.com>
References: <44830772.4080905@ericsson.com> <454859B5.8090504@ericsson.com>
	<45E96E10.6030302@ericsson.com> <45EBFED4.8090502@nokia.com>
In-Reply-To: <45EBFED4.8090502@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7698d1420ecbbce1995432e99bb6d1a1
Cc: sipping <sipping@ietf.org>
Subject: [Sipping] Re: [Fwd: WGLC of
	draft-ietf-sipping-service-examples-10.txt]
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi Miguel,

Thanks for the comments - see my answers below.

Thanks,
Alan

Miguel Garcia wrote:
> Hi:
>
> I went through my comments again, and I noticed two of them that 
> haven't been implemented. I can't really recall now if we discussed 
> these two issues in the past or they are still oversights (it's been 
> long time with this draft).
>
> I reproduce my old comments here. Note that sections have changed, and 
> when the comment refers to Section 2.14 corresponds to Section 2.13 in 
> version -12:
>
> 1) About the call flow in Section 2.14: Alice receives the 403 in flow
> F8, including an Error-Info URI. I would assume that the INVITE F10 goes
> straight forward to that URI. However, flow F10 traverses once more the
> Proxy (proxy that wasn't initially traversed in flow F1). I don't think
> this is the natural behavior, why should Alice route the INVITE F10 via
> the proxy, once she got a URI that does not embed a Route header? Notice
> that the proxy is not Alice's outbound proxy, so I see no reason for
> this behavior.
>

I will fix this, showing the INVITE from the Error-Info URI bypassing 
the proxy.

> 8) I noticed that flow F9 in Section 2.14 contains a Proxy-Authorization
> header. I think it is weird that the ACK request for a 403 response
> contains a Proxy-Authorization header. There is nothing the proxy can do
> with that group of credentials. The same applies to Flow F6 in Section 
> 2.15.

You are correct - a proxy can not challenge an ACK.  However, RFC 3261 
advises UAs to include the Proxy-Authorization in the ACK in Section 22.1.

>
> Is it possible to get some comments about them?
>
> BR,
>
>       Miguel
>
> Gonzalo Camarillo wrote:
>> Dear reviewers of the service examples draft,
>>
>> the authors have submitted yet another revision of the draft that is 
>> supposed to address your last set of comments on revision 11. As in 
>> previous occasions, could you please have a look at it and send a 
>> note to the SIPPING mailing list, cc:ing the chairs, stating whether 
>> or not you are now OK with the draft?
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-examples-12.txt 
>>
>>
>> For your convenience, your reviews are stored at:
>>
>> http://www.softarmor.com/sipping/process/wg-review/sipping-rt-wglc.html
>>
>> The diff between revisions 11 and 12 is available at:
>>
>> http://tools.ietf.org/wg/sipping/draft-ietf-sipping-service-examples/draft-ietf-sipping-service-examples-12-from-11.diff.html 
>>
>>
>> Thanks,
>>
>> Gonzalo
>>
>>
>> Gonzalo Camarillo wrote:
>>> Dear reviewers of the service examples draft,
>>>
>>> the authors of the draft have submitted a new revision of the draft 
>>> that is supposed to address all your WGLC comments. Could you please 
>>> have a look at it and send a note to the SIPPING mailing list, 
>>> cc:ing the chairs, stating whether or not you are now OK with the 
>>> draft?
>>>
>>> http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-examples-11.txt 
>>>
>>>
>>> For your convenience, your reviews are stored at:
>>> http://www.softarmor.com/sipping/process/wg-review/sipping-rt-wglc.html
>>>
>>> Thanks,
>>>
>>> Gonzalo
>>>
>>> Gonzalo Camarillo wrote:
>>>> Hi,
>>>>
>>>> all of you in the 'To' field of this email have volunteered to review
>>>> the service examples draft. Thanks a lot for agreeing to perform this
>>>> review.
>>>>
>>>> This is how we would like to divide the work: in the list below, I 
>>>> have
>>>> assigned a few sections to each of the reviewers. When you are done 
>>>> with
>>>> your review, send it in a reply-to-all to the email below, which 
>>>> was the
>>>> WGLC for this draft on the SIPPING mailing list. We would like to 
>>>> have all the reviews ready by the end of the WGLC, on July 1st.
>>>>
>>>>
>>>> <vkg@lucent.com>
>>>>      2.1.  Call Hold
>>>>      2.2.  Consultation Hold
>>>>
>>>> <john.elwell@siemens.com>
>>>>      2.3.  Music On Hold
>>>>      2.18. Automatic Redial
>>>>      2.19. Click to Dial
>>>>
>>>> <joel.repiquet@tech-invite.com>
>>>>      2.4.  Transfer - Unattended
>>>>      2.5.  Transfer - Attended
>>>>      2.6.  Transfer - Instant Messaging
>>>>
>>>> <bvnkumar@gmail.com>
>>>>      2.7.  Call Forwarding Unconditional
>>>>      2.8.  Call Forwarding - Busy
>>>>      2.9.  Call Forwarding - No Answer
>>>>
>>>> <ravipati@avaya.com>
>>>>      2.10. 3-way Conference - Third Party is Added
>>>>      2.11. 3-way Conference - Third Party Joins
>>>>
>>>> <eburger@cantata.com>
>>>>      2.12. Single Line Extension
>>>>
>>>> <jbemmel@zonnet.nl>
>>>>      2.13. Find-Me
>>>>
>>>> <Miguel.An.Garcia@nokia.com>
>>>>      2.14. Call Management (Incoming Call Screening)
>>>>      2.15. Call Management (Outgoing Call Screening)
>>>>
>>>> <dworley@pingtel.com>
>>>>      2.16. Call Park
>>>>      2.17. Call Pickup
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Gonzalo
>>>>
>>>>
>>>>
>>>> -------- Original Message --------
>>>> Subject: WGLC  of draft-ietf-sipping-service-examples-10.txt
>>>> Date: Thu, 11 May 2006 20:37:40 +0300
>>>> From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
>>>> To: sipping <sipping@ietf.org>
>>>> CC: Samuli Pöykkö <samuli.poykko@hut.fi>,  Mary Barnes
>>>> <mary.barnes@nortel.com>, Alan Johnston <alan@sipstation.com>, Robert
>>>> Sparks <RjS@estacado.net>,  kevin.summers@sonusnet.com
>>>>
>>>> Folks,
>>>>
>>>> we would like to working group last call (WGLC) the following draft:
>>>>
>>>> http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-examples-10.txt 
>>>>
>>>>
>>>> as you have probably noticed if you clicked on the link above, this 
>>>> is a
>>>> very long draft. Therefore, we would like to get at least ten 
>>>> volunteers
>>>> to review it. We will assign a couple of sections to each reviewer.
>>>>
>>>> If you are interested and willing to review this draft, please send an
>>>> email to the SIPPING chairs.
>>>>
>>>> The email below should be considered as a WGLC comment:
>>>>
>>>> http://www1.ietf.org/mail-archive/web/sipping/current/msg10886.html
>>>>
>>>> This is the output of the idnits tool:
>>>>
>>>> idnits 1.96
>>>>
>>>> tmp/draft-ietf-sipping-service-examples-10.txt:
>>>>
>>>>
>>>>   Checking nits according to http://www.ietf.org/ID-Checklist.html:
>>>>
>>>>     Checking conformance with RFC 3978/3979 boilerplate...
>>>>
>>>>     the boilerplate looks good.
>>>>
>>>>   * There is 1 instance of too long lines in the document, the 
>>>> longest one
>>>>     being 1 character in excess of 72.
>>>>
>>>>   Checking nits according to 
>>>> http://www.ietf.org/ietf/1id-guidelines.txt:
>>>>     Nothing found here (but these checks do not cover all of
>>>>     1id-guidelines.txt yet).
>>>>
>>>>   Miscellaneous warnings:
>>>>   - Line 1028 has weird spacing: '... /* Bob  place...'
>>>>   - Line 1404 has weird spacing: '... /* Bob  takes...'
>>>>   - Line 1732 has weird spacing: '... /* Bob  place...'
>>>>   - Line 2459 has weird spacing: '...and Bob  have ...'
>>>>   - Line 2597 has weird spacing: '... /* Bob  puts ...'
>>>>   - (4 more instances...)
>>>>
>>>>   Experimental warnings:
>>>>   - Unused Reference: [18] is defined on line 7860, but not referenced
>>>>   - Unused Reference: [13] is defined on line 7839, but not referenced
>>>>   - Unused Reference: [14] is defined on line 7842, but not referenced
>>>>   - Unused Reference: [1] is defined on line 7795, but not referenced
>>>>
>>>>
>>>>
>>>>
>>>> This WGLC will end on July 1st, 2006 (a long draft needs a long WGLC).
>>>>
>>>> Thanks,
>>>>
>>>> Gonzalo
>>>> SIPPING co-chair
>>>>
>>>>
>>>>
>>>
>>>
>>
>



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 23 13:45:59 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg2br-0000c2-M3; Mon, 23 Apr 2007 13:45:55 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hg2bq-0000Zx-Cd for sipping-confirm+ok@megatron.ietf.org;
	Mon, 23 Apr 2007 13:45:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg2bq-0000Zp-2w
	for sipping@ietf.org; Mon, 23 Apr 2007 13:45:54 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg2bp-0003rK-Jb
	for sipping@ietf.org; Mon, 23 Apr 2007 13:45:54 -0400
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l3NHjqbB027712
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <sipping@ietf.org>; Mon, 23 Apr 2007 10:45:52 -0700
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l3NHjpLm011084
	for <sipping@ietf.org>; Mon, 23 Apr 2007 10:45:51 -0700 (PDT)
Received: from NAEX07.na.qualcomm.com ([129.46.133.195]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Apr 2007 10:45:42 -0700
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: Mon, 23 Apr 2007 10:45:53 -0700
Message-ID: <90D469E18343DE47961207F6851040B30190CD73@NAEX07.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-sipping-cc-framework-07.txt
Thread-Index: AceFzz0llvM8XpUwSY+D7Rczzxtx8A==
From: "Mahendran, AC" <mahendra@qualcomm.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 23 Apr 2007 17:45:42.0883 (UTC)
	FILETIME=[36E1A330:01C785CF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Subject: [Sipping] Comments on draft-ietf-sipping-cc-framework-07.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


Hi all,

Here are my comments in draft-ietf-sipping-cc-framework-07.txt.

1) Section 1

Text: "Primitives should be sufficiently robust that when they are
combined they can be used to build lots of services."

Replace with=20

"Primitives should be sufficiently robust, so that when they are
combined with each other, they can be used to build lots of services. "

2) Section 1, in the paragraph starting with "Primitives make full use
of URIs....", replace two instances of "URLs" with "URIs".

Note: there are other places in the document which use URL, where URI is
more appropriate. So, please do a global search and replace of URLs with
URIs.


3) Section 2, describes a bunch of key concepts (e.g., conversational
space, signaling models, mixing etc). It is not clear how these "key
concepts" are tied together. It'd be good to have a brief description
indicating what section 2 trying to achieve.

4) Section 2.1, the second diagram has four participants (A, b, C, D),
however, the entry above it only shows [A, B].

So, replace "[A, B]", with "[A, b, C, D]".

5) In section 2.1, text: "(essentially as a set of participants who
believe they are all
   communicating among one another).", remove the brackets "()".

6) Section 2.2, the title "Comparison with Related Definitions" can be
replaced to "Relationship between Conversation space, SIP Dialogs and
SIP Sessions".

>From the current title, it is not clear what is being compared to what!

7) It is not clear what sigaling models section 2.3 is trying to compare
- is it 3pcc vs peer-to-peer? It would be better to compare
"centralized" and "peer-to-peer" signaling models; 3pcc is one possible
way to realize the centralized model.

8) In section 2.4.1.3, it'd be good to mention that media mixing is done
by the end points.

9) In 2.4.2.2, replace two instances of "SIP" with "Signaling".

10) Section 2.7.1, text: "When a caller sends a request, it can
optionally request Caller Preferences [21], by including the
Accept-Contact and Reject-Contact headers that request certain handling
by the proxy in the target domain."

We should include "Request-Disposition" to the list of Caller
Preferences header.

11) In section 2.7.2, text:  "As we have shown, SIP URIs represent an
ideal, flexible mechanism for describing and naming service resources,
be they queues, conferences, voice dialogs, announcements, voicemail
treatments, or phone features."

"be they queues"? This phrase needs to be replaced.

12) Terminology issues: Section 1 uses the term "primitives", whereas
section 3, uses the term "Call control actions". Are these the same? If
yes, we should try to be consistent with the terminology.

13) Section 3.3.1 was confusing the first time I read it. It would be
better to start out saying that the following section describes how call
transfer can be achieved using 3pcc and REFER, and then describe the
operations/procedures.

Also, the sentence "Features enabled by this action..." can be reworded
as: "The following features can be enabled by the "Transfer" action: "=20

14) Section 3.3.5 (Insert), we can add a reference to the "Join" RFC.

15) In section 3, in many of the examples, the messages needed to
achieve a particular service are all shown in a single line (for
example, in 3.3.6, to achieve split, the following messages are sent:
REFER C Refer-To: conference-URI (new URI) REFER D Refer-To:
conference-URI (new URI) BYE C BYE D).

For better readability, it is advisable to split these into multiple
lines.



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 23 15:51:18 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg4Z7-0005fo-S8; Mon, 23 Apr 2007 15:51:13 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hg4YW-0004Jk-LU for sipping-confirm+ok@megatron.ietf.org;
	Mon, 23 Apr 2007 15:50:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg4YV-0004HV-BN; Mon, 23 Apr 2007 15:50:35 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Hg4YS-00083U-QF; Mon, 23 Apr 2007 15:50:35 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id AE576176A9;
	Mon, 23 Apr 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Hg4Xy-0004CW-Du; Mon, 23 Apr 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Hg4Xy-0004CW-Du@stiedprstage1.ietf.org>
Date: Mon, 23 Apr 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-ipv6-torture-tests-02.txt 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: Session Initiation Protocol (SIP) Torture Test Messages for Internet Protocol Version 6 (IPv6)
	Author(s)	: V. Gurbani, et al.
	Filename	: draft-ietf-sipping-ipv6-torture-tests-02.txt
	Pages		: 15
	Date		: 2007-4-23
	
This informational document provides examples of Session Initiation
   Protocol (SIP) test messages designed to exercise and "torture" the
   code of a SIP implementation that parses IPv6 addresses.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-ipv6-torture-tests-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sipping-ipv6-torture-tests-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-ipv6-torture-tests-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-4-23113453.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-ipv6-torture-tests-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-ipv6-torture-tests-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-4-23113453.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--NextPart--





From sipping-bounces@ietf.org Mon Apr 23 21:08:38 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg9WG-0008AQ-MG; Mon, 23 Apr 2007 21:08:36 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hg9WF-0008AL-2g for sipping-confirm+ok@megatron.ietf.org;
	Mon, 23 Apr 2007 21:08:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg9WE-0008AD-PO
	for sipping@ietf.org; Mon, 23 Apr 2007 21:08:34 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg9WC-0003hH-9m
	for sipping@ietf.org; Mon, 23 Apr 2007 21:08:34 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l3O18SG8017318
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <sipping@ietf.org>; Mon, 23 Apr 2007 18:08:30 -0700
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l3O18SEr006434
	for <sipping@ietf.org>; Mon, 23 Apr 2007 18:08:28 -0700
Received: from NAEX07.na.qualcomm.com ([129.46.133.195]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Apr 2007 18:08:28 -0700
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
Subject: RE: [Sipping] Comments on draft-ietf-sipping-cc-framework-07.txt
Date: Mon, 23 Apr 2007 18:08:30 -0700
Message-ID: <90D469E18343DE47961207F6851040B30190CE58@NAEX07.na.qualcomm.com>
In-Reply-To: <90D469E18343DE47961207F6851040B30190CD73@NAEX07.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Comments on draft-ietf-sipping-cc-framework-07.txt
Thread-Index: AceFzz0llvM8XpUwSY+D7Rczzxtx8AAPNw2g
References: <90D469E18343DE47961207F6851040B30190CD73@NAEX07.na.qualcomm.com>
From: "Mahendran, AC" <mahendra@qualcomm.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 24 Apr 2007 01:08:28.0368 (UTC)
	FILETIME=[1124F500:01C7860D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

=20
One more comment...

Section 2.1 defines a "Conversation space" model.  According to
Webster's dictionary, conversation means "(1) : ORAL exchange of
sentiments, observations, opinions, or ideas". However, the framework is
equally applicable to media sessions which are not audio/speech. So, may
be, the model can be called "Communication Space" instead of
"Conversation space".

Thanks,
-AC

-----Original Message-----
From: Mahendran, AC [mailto:mahendra@qualcomm.com]=20
Sent: Monday, April 23, 2007 10:46 AM
To: sipping@ietf.org
Subject: [Sipping] Comments on draft-ietf-sipping-cc-framework-07.txt


Hi all,

Here are my comments in draft-ietf-sipping-cc-framework-07.txt.

1) Section 1

Text: "Primitives should be sufficiently robust that when they are
combined they can be used to build lots of services."

Replace with=20

"Primitives should be sufficiently robust, so that when they are
combined with each other, they can be used to build lots of services. "

2) Section 1, in the paragraph starting with "Primitives make full use
of URIs....", replace two instances of "URLs" with "URIs".

Note: there are other places in the document which use URL, where URI is
more appropriate. So, please do a global search and replace of URLs with
URIs.


3) Section 2, describes a bunch of key concepts (e.g., conversational
space, signaling models, mixing etc). It is not clear how these "key
concepts" are tied together. It'd be good to have a brief description
indicating what section 2 trying to achieve.

4) Section 2.1, the second diagram has four participants (A, b, C, D),
however, the entry above it only shows [A, B].

So, replace "[A, B]", with "[A, b, C, D]".

5) In section 2.1, text: "(essentially as a set of participants who
believe they are all
   communicating among one another).", remove the brackets "()".

6) Section 2.2, the title "Comparison with Related Definitions" can be
replaced to "Relationship between Conversation space, SIP Dialogs and
SIP Sessions".

>From the current title, it is not clear what is being compared to what!

7) It is not clear what sigaling models section 2.3 is trying to compare
- is it 3pcc vs peer-to-peer? It would be better to compare
"centralized" and "peer-to-peer" signaling models; 3pcc is one possible
way to realize the centralized model.

8) In section 2.4.1.3, it'd be good to mention that media mixing is done
by the end points.

9) In 2.4.2.2, replace two instances of "SIP" with "Signaling".

10) Section 2.7.1, text: "When a caller sends a request, it can
optionally request Caller Preferences [21], by including the
Accept-Contact and Reject-Contact headers that request certain handling
by the proxy in the target domain."

We should include "Request-Disposition" to the list of Caller
Preferences header.

11) In section 2.7.2, text:  "As we have shown, SIP URIs represent an
ideal, flexible mechanism for describing and naming service resources,
be they queues, conferences, voice dialogs, announcements, voicemail
treatments, or phone features."

"be they queues"? This phrase needs to be replaced.

12) Terminology issues: Section 1 uses the term "primitives", whereas
section 3, uses the term "Call control actions". Are these the same? If
yes, we should try to be consistent with the terminology.

13) Section 3.3.1 was confusing the first time I read it. It would be
better to start out saying that the following section describes how call
transfer can be achieved using 3pcc and REFER, and then describe the
operations/procedures.

Also, the sentence "Features enabled by this action..." can be reworded
as: "The following features can be enabled by the "Transfer" action: "=20

14) Section 3.3.5 (Insert), we can add a reference to the "Join" RFC.

15) In section 3, in many of the examples, the messages needed to
achieve a particular service are all shown in a single line (for
example, in 3.3.6, to achieve split, the following messages are sent:
REFER C Refer-To: conference-URI (new URI) REFER D Refer-To:
conference-URI (new URI) BYE C BYE D).

For better readability, it is advisable to split these into multiple
lines.



_______________________________________________
Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 24 03:04:27 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgF4a-000386-Gk; Tue, 24 Apr 2007 03:04:24 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HgF4Y-00037x-UZ for sipping-confirm+ok@megatron.ietf.org;
	Tue, 24 Apr 2007 03:04:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgF4V-00037l-KX
	for sipping@ietf.org; Tue, 24 Apr 2007 03:04:19 -0400
Received: from corp2.ipunity.com ([65.106.79.133] helo=exchangevm.ipunity.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgF4U-0001G5-CM
	for sipping@ietf.org; Tue, 24 Apr 2007 03:04:19 -0400
Received: from BLRPC6 ([10.253.253.150]) by exchangevm.ipunity.com with
	Microsoft SMTPSVC(5.0.2195.6713); Tue, 24 Apr 2007 00:04:02 -0700
From: "Darshan Bildikar" <dbildikar@ipunity.com>
To: <sipping@ietf.org>,
	<oritl@microsoft.com>
Date: Tue, 24 Apr 2007 12:34:05 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <E1Hg4Xy-0004CW-Du@stiedprstage1.ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AceF4Y8zF8Yj3P2xRteFAXVNEjOr1AAVczuw
Message-ID: <EXCHANGEVMs60XxsXfx00000b28@exchangevm.ipunity.com>
X-OriginalArrivalTime: 24 Apr 2007 07:04:03.0124 (UTC)
	FILETIME=[BDA65F40:01C7863E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 
Subject: [Sipping] Question on RFC 4488
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I've been going through the "norefersub" RFC. 

While I do understand the reasoning behind the header and option tag, I
wonder what the concrete use cases for it are. 

Take where REFER is used for transfer. Does this header change anything in
terms how transfers are implemented?

I'm thinking that a use case for this would be to implement blind transfer
where we don't care about the outcome of the transfer. 

Am I mistaken in looking for a use case for this? Is the assumption that a
REFER with a "norefersub" can be used in the same scenarios as a normal
REFER except that it doesn't create a subscription? (obviously NOT for
scenarios that REQUIRE a subscription)

Darshan



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 24 03:21:07 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgFKj-0001LY-Ch; Tue, 24 Apr 2007 03:21:05 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HgFKi-0001LT-I0 for sipping-confirm+ok@megatron.ietf.org;
	Tue, 24 Apr 2007 03:21:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgFKi-0001LL-5i
	for sipping@ietf.org; Tue, 24 Apr 2007 03:21:04 -0400
Received: from corp2.ipunity.com ([65.106.79.133] helo=exchangevm.ipunity.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgFKg-00007P-RG
	for sipping@ietf.org; Tue, 24 Apr 2007 03:21:04 -0400
Received: from BLRPC6 ([10.253.253.150]) by exchangevm.ipunity.com with
	Microsoft SMTPSVC(5.0.2195.6713); Tue, 24 Apr 2007 00:20:51 -0700
From: "Darshan Bildikar" <dbildikar@ipunity.com>
To: <sipping@ietf.org>
Date: Tue, 24 Apr 2007 12:50:54 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <90D469E18343DE47961207F6851040B30190CE58@NAEX07.na.qualcomm.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AceFzz0llvM8XpUwSY+D7Rczzxtx8AAPNw2gAAyvCyA=
Message-ID: <EXCHANGEVMAVnMKzRez00000b2e@exchangevm.ipunity.com>
X-OriginalArrivalTime: 24 Apr 2007 07:20:51.0702 (UTC)
	FILETIME=[16CF2960:01C78641]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: RjS@estacado.net, alan@sisptation.com, dan.ietf@SIPez.com
Subject: [Sipping] Question on draft-ietf-sipping-cc-transfer
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

This is what "draft-ietf-sipping-cc-transfer" says about blind transfer

Section 6: Basic transfer

"If the Transferor's agent does not wish to participate in the remainder of
the REFER process and has no intention of assisting with recovery from
transfer failure, it could emit a BYE to the Transferee as soon as the REFER
transaction completes.  This flow is sometimes known as "unattended
transfer" or "blind transfer"

There are two possible scenarios here

1) REFER within dialog: A REFER obviously creates a dialog usage here. A BYE
will therefore ONLY end the INVITE dialog usage and the dialog with the
REFER usage is still active. This would mean that the transferor would still
receive NOTIFY messages with transfer status in essence NOT making this a
"blind transfer". Is the assumption that a NOTIFY needs to be sent with a
subscription termination implicit?

2) REFER outside dialog: Tdialog and gruu would be used here. But the draft
does not talk about the termination of the subscription created by REFER.

I have two suggestions here

1) Would it not be better to recommend the use of "norefersub - RFC 4488" to
implement blind transfer?

2) I can't actually see an example flow for blind/unattended transfer. Would
it be possible to put one in there?

Darshan



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 24 04:30:06 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgGPT-0002gP-5D; Tue, 24 Apr 2007 04:30:03 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HgGPR-0002g7-Iq for sipping-confirm+ok@megatron.ietf.org;
	Tue, 24 Apr 2007 04:30:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgGPR-0002fz-7k
	for sipping@ietf.org; Tue, 24 Apr 2007 04:30:01 -0400
Received: from mx02.lb01.inode.at ([62.99.145.2] helo=mx.inode.at)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgGPO-0001nk-Oc
	for sipping@ietf.org; Tue, 24 Apr 2007 04:30:01 -0400
Received: from [195.58.170.124] (port=8573 helo=inode.at)
	by smartmx-02.inode.at with smtp (Exim 4.50)
	id 1HgGPO-0001uU-4x; Tue, 24 Apr 2007 10:29:58 +0200
Received: from 194.113.59.80
	(SquirrelMail authenticated user franz.edler@inode.at)
	by webmail.inode.at with HTTP; Tue, 24 Apr 2007 10:29:57 +0200 (CEST)
Message-ID: <194.113.59.80.1177403397.wm@webmail.inode.at>
Date: Tue, 24 Apr 2007 10:29:57 +0200 (CEST)
Subject: Re: [Sipping] Question on RFC 4488
From: <franz.edler@inode.at>
To: <dbildikar@ipunity.com>
In-Reply-To: <EXCHANGEVMs60XxsXfx00000b28@exchangevm.ipunity.com>
References: <E1Hg4Xy-0004CW-Du@stiedprstage1.ietf.org>
	<EXCHANGEVMs60XxsXfx00000b28@exchangevm.ipunity.com>
X-Priority: 3
Importance: Normal
X-Mailer: SquirrelMail (version 1.2.8)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: oritl@microsoft.com, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

> While I do understand the reasoning behind the header and option tag, I
> wonder what the concrete use cases for it are.

Look at draft-ietf-sip-multiple-refer chapter 5 "Suppressing REFER's
Implicit Subscription".

-franz




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Tue Apr 24 09:06:19 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgKij-0005FA-UZ; Tue, 24 Apr 2007 09:06:13 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HgKih-0005Ex-Pj for sipping-confirm+ok@megatron.ietf.org;
	Tue, 24 Apr 2007 09:06:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgKih-0005Ep-GK
	for sipping@ietf.org; Tue, 24 Apr 2007 09:06:11 -0400
Received: from mail44.opentransfer.com ([76.162.254.44])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HgKig-0001OG-5H
	for sipping@ietf.org; Tue, 24 Apr 2007 09:06:11 -0400
Received: (qmail 6769 invoked by uid 399); 24 Apr 2007 13:06:09 -0000
Received: from unknown (HELO ?192.168.0.40?) (24.107.197.43)
	by mail44.opentransfer.com with SMTP; 24 Apr 2007 13:06:09 -0000
Message-ID: <462E00C0.6080702@sipstation.com>
Date: Tue, 24 Apr 2007 08:06:08 -0500
From: Alan Johnston <alan@sipstation.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: franz.edler@inode.at
Subject: Re: [Sipping] Question on RFC 4488
References: <E1Hg4Xy-0004CW-Du@stiedprstage1.ietf.org>	<EXCHANGEVMs60XxsXfx00000b28@exchangevm.ipunity.com>
	<194.113.59.80.1177403397.wm@webmail.inode.at>
In-Reply-To: <194.113.59.80.1177403397.wm@webmail.inode.at>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: sipping@ietf.org, oritl@microsoft.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi Darshan,

This extension is especially useful when there is already a dialog 
package subscription between the two parties.  For example, see:

   http://tools.ietf.org/wg/sip/draft-mahy-sip-remote-cc-05.txt

Another use would be when using REFER in a conference where there is a 
conference package subscription already in place.

    http://tools.ietf.org/html/rfc4579#section-5.5

Thanks,
Alan


franz.edler@inode.at wrote:
>> While I do understand the reasoning behind the header and option tag, I
>> wonder what the concrete use cases for it are.
>>     
>
> Look at draft-ietf-sip-multiple-refer chapter 5 "Suppressing REFER's
> Implicit Subscription".
>
> -franz
>
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.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
>
>
>   



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 25 05:19:09 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgdeL-0000AY-Tr; Wed, 25 Apr 2007 05:18:57 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HgdeK-0008WI-L6 for sipping-confirm+ok@megatron.ietf.org;
	Wed, 25 Apr 2007 05:18:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgdeJ-0008PO-TD
	for sipping@ietf.org; Wed, 25 Apr 2007 05:18:55 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgdeI-0004eV-7x
	for sipping@ietf.org; Wed, 25 Apr 2007 05:18:55 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Apr 2007 11:18:50 +0200
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
Subject: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
Date: Wed, 25 Apr 2007 11:18:42 +0200
Message-ID: <2AF8FF7D89242541B12E7A47F6ECB4BE055EBC73@ftrdmel3.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
Thread-Index: AceHGrfJZuqidJGMTKm/pz03rqHTDw==
From: "CHADLI Youssef RD-CORE-ISS" <youssef.chadli@orange-ftgroup.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>,
	"sipping" <sipping@ietf.org>
X-OriginalArrivalTime: 25 Apr 2007 09:18:50.0191 (UTC)
	FILETIME=[BC549DF0:01C7871A]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi,

I have two comments on draft-ietf-sipping-overload-reqs
<http://www.ietf.org/internet-drafts/draft-ietf-sipping-overload-reqs-00
.txt> :

1) There are two requirements dealing with security aspects:=20

REQ 5: The mechanism should not assume that it will only be deployed
      in environments with completely trusted elements.  It should seek
      to operate as effectively as possible in environments where other
      elements are malicious, including preventing malicious elements
      from obtaining more than a fair share of service.

REQ 17: The overload mechanism must not provide an avenue for
      malicious attack. =20

To prevent malicious attacks, it's necessary to prevent untrusted
elements to access load information of the SIP servers. Consequently, I
think that it is important to specify explicitly that the overload
mechanism must allow preventing load information to be sent to untrusted
elements. This precision can be added to the text of REQ 17 or can be
added as a separate requirement.
                               =20
2) Big SIP server are in general implemented as a cluster of servers
with one or more front-end servers. The frond-end server interfaces to
the other SIP nodes and performs load balancing on the different servers
of the cluster. In such a case, the load control mechanism can be
implemented and managed only by front-ends servers as only those servers
can know the overall load of the cluster. It's then important that the
overload mechanism can be easily centralised on the front-ends servers
in this case. Consequently, I propose to add a requirement on this;
something like:

REQ 22: The mechanism should be easily centralised in the front-end
servers in case the SIP server is implemented as a cluster of servers
running on different machines. =20

        +----------+    +----------+      +----------+ =20
     	  | Server#1 |    | Server#2 |..... | Server#n |=20
        +----------+    +----------+      +----------+

 			|         |              |=20
                  |         |              |
                  |         |              |=20
			|	+----------+       |=20
			+-----| Front-End|-------+

              	      | Server   |=09
        			+----------+=20

Best regards,

Youssef CHADLI			     =20



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 25 09:06:23 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HghCL-0000TJ-Na; Wed, 25 Apr 2007 09:06:17 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HghCK-0000TE-Sz for sipping-confirm+ok@megatron.ietf.org;
	Wed, 25 Apr 2007 09:06:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HghCK-0000T6-JP
	for sipping@ietf.org; Wed, 25 Apr 2007 09:06:16 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HghCI-0000nG-93
	for sipping@ietf.org; Wed, 25 Apr 2007 09:06:16 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 25 Apr 2007 09:06:14 -0400
X-IronPort-AV: i="4.14,450,1170651600"; 
	d="scan'208"; a="58572399:sNHT1562457852"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3PD6DNG003408; 
	Wed, 25 Apr 2007 09:06:13 -0400
Received: from [172.17.179.223] (rtp-vpn3-588.cisco.com [10.82.218.79])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l3PD6ClG017179; 
	Wed, 25 Apr 2007 13:06:13 GMT
In-Reply-To: <2AF8FF7D89242541B12E7A47F6ECB4BE055EBC73@ftrdmel3.rd.francetelecom.fr>
References: <2AF8FF7D89242541B12E7A47F6ECB4BE055EBC73@ftrdmel3.rd.francetelecom.fr>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <68CE80AC-2A88-4A51-9C00-B99ED6BF5CE8@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
Date: Wed, 25 Apr 2007 09:06:05 -0400
To: "CHADLI Youssef RD-CORE-ISS" <youssef.chadli@orange-ftgroup.com>
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3151; t=1177506373;
	x=1178370373; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[SIPPING]=20Comments=20on=20draft-ietf-sipping-overlo
	ad-reqs-00 |Sender:=20
	|To:=20=22CHADLI=20Youssef=20RD-CORE-ISS=22=20<youssef.chadli@orange-ftgr
	oup.com>; bh=KDsaASgwF2jv3mgFSBQkdQQp59YiPnSUj81VMFoeynM=;
	b=P9YaTCOJXtp+oAn3YVmMUtCFQ/Sq5aW+PD/owQW4GBypT0o2mYcbb2suYYJIMc6vJIRrnj4m
	0hKrVJUc2iN3IdJUzdV7SQlGp55jZ2LXpfT4UbVCWpEADYjPgVr/A02J;
Authentication-Results: rtp-dkim-1; header.From=oran@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 1.1 (+)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 25, 2007, at 5:18 AM, CHADLI Youssef RD-CORE-ISS wrote:

> Hi,
>
> I have two comments on draft-ietf-sipping-overload-reqs
> <http://www.ietf.org/internet-drafts/draft-ietf-sipping-overload- 
> reqs-00
> .txt> :
>
> 1) There are two requirements dealing with security aspects:
>
> REQ 5: The mechanism should not assume that it will only be deployed
>       in environments with completely trusted elements.  It should  
> seek
>       to operate as effectively as possible in environments where  
> other
>       elements are malicious, including preventing malicious elements
>       from obtaining more than a fair share of service.
>
> REQ 17: The overload mechanism must not provide an avenue for
>       malicious attack.
>
> To prevent malicious attacks, it's necessary to prevent untrusted
> elements to access load information of the SIP servers.
I must be dense, so bear with me. Could you explain what new  
malicious attack is opened or existing attack amplified by treating  
the load information as confidential?

> Consequently, I
> think that it is important to specify explicitly that the overload
> mechanism must allow preventing load information to be sent to  
> untrusted
> elements. This precision can be added to the text of REQ 17 or can be
> added as a separate requirement.
>
> 2) Big SIP server are in general implemented as a cluster of servers
> with one or more front-end servers. The frond-end server interfaces to
> the other SIP nodes and performs load balancing on the different  
> servers
> of the cluster. In such a case, the load control mechanism can be
> implemented and managed only by front-ends servers as only those  
> servers
> can know the overall load of the cluster. It's then important that the
> overload mechanism can be easily centralised on the front-ends servers
> in this case. Consequently, I propose to add a requirement on this;
> something like:
>
> REQ 22: The mechanism should be easily centralised in the front-end
> servers in case the SIP server is implemented as a cluster of servers
> running on different machines.
>
I'm not sure how you ascertain if this requirement is met. I can see  
how you could write a requirement that the scheme allow such  
configurations, just not that it be "easy". Easy compared to what?


>         +----------+    +----------+      +----------+
>      	  | Server#1 |    | Server#2 |..... | Server#n |
>         +----------+    +----------+      +----------+
>
>  			|         |              |
>                   |         |              |
>                   |         |              |
> 			|	+----------+       |
> 			+-----| Front-End|-------+
>
>               	      | Server   |	
>         			+----------+
>
> Best regards,
>
> Youssef CHADLI			
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 25 09:31:36 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hghap-00072D-Sd; Wed, 25 Apr 2007 09:31:35 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hghao-000724-Ss for sipping-confirm+ok@megatron.ietf.org;
	Wed, 25 Apr 2007 09:31:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hghao-00071w-JL
	for sipping@ietf.org; Wed, 25 Apr 2007 09:31:34 -0400
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hgham-0000au-BR
	for sipping@ietf.org; Wed, 25 Apr 2007 09:31:34 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JH2007UV2WJWW@usaga01-in.huawei.com> for
	sipping@ietf.org; Wed, 25 Apr 2007 06:31:31 -0700 (PDT)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0JH200LVG2WDIB@usaga01-in.huawei.com> for
	sipping@ietf.org; Wed, 25 Apr 2007 06:31:31 -0700 (PDT)
Date: Wed, 25 Apr 2007 08:29:58 -0500
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
To: sipping <sipping@ietf.org>
Message-id: <0d5f01c7873d$d380fff0$ad600240@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=response
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <2AF8FF7D89242541B12E7A47F6ECB4BE055EBC73@ftrdmel3.rd.francetelecom.fr>
	<68CE80AC-2A88-4A51-9C00-B99ED6BF5CE8@cisco.com>
X-Spam-Score: 1.1 (+)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Just checking -

From: "David R Oran" <oran@cisco.com>

> On Apr 25, 2007, at 5:18 AM, CHADLI Youssef RD-CORE-ISS wrote:
>
>> REQ 17: The overload mechanism must not provide an avenue for
>>       malicious attack.
>>
>> To prevent malicious attacks, it's necessary to prevent untrusted
>> elements to access load information of the SIP servers.
> I must be dense, so bear with me. Could you explain what new  malicious 
> attack is opened or existing attack amplified by treating  the load 
> information as confidential?

I am just as dense as David - please explain...

>> REQ 22: The mechanism should be easily centralised in the front-end
>> servers in case the SIP server is implemented as a cluster of servers
>> running on different machines.
>>
> I'm not sure how you ascertain if this requirement is met. I can see  how 
> you could write a requirement that the scheme allow such  configurations, 
> just not that it be "easy". Easy compared to what?

I like the requirement (although I agree with David that "easily" is a 
weasel word), but I'm concerned that we may not have a basis for judging 
"can be centralized in the front-end servers".

If things have changed in the past few years, I apologize for my confusion, 
but my understanding was that most of the front-end-to-cluster schemes were 
proprietary, so we might be able to say "works on THIS front-end-to-cluster 
scheme", but wouldn't know if it works on ANY front-end-to-cluster scheme.

Can someone smarter than I am express an opinion about this?

Thanks,

Spencer 




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 25 10:39:05 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hgie4-0006bF-3J; Wed, 25 Apr 2007 10:39:00 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hgie2-0006S0-2O for sipping-confirm+ok@megatron.ietf.org;
	Wed, 25 Apr 2007 10:38:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hgie1-0006PZ-NH; Wed, 25 Apr 2007 10:38:57 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Hgie1-0006BP-Eo; Wed, 25 Apr 2007 10:38:57 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 663732AC79;
	Wed, 25 Apr 2007 14:38:27 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HgidX-0000F1-6Q; Wed, 25 Apr 2007 10:38:27 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1HgidX-0000F1-6Q@stiedprstage1.ietf.org>
Date: Wed, 25 Apr 2007 10:38:27 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: sipping@ietf.org
Subject: [Sipping] Last Call: draft-ietf-sipping-spam (The Session
 Initiation Protocol (SIP) and Spam) to Informational RFC 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

The IESG has received a request from the Session Initiation Proposal 
Investigation WG (sipping) to consider the following document:

- 'The Session Initiation Protocol (SIP) and Spam '
   <draft-ietf-sipping-spam-04.txt> as an Informational RFC

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 2007-05-09. 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://www.ietf.org/internet-drafts/draft-ietf-sipping-spam-04.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=12840&rfc_flag=0



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 25 10:44:10 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hgij4-000879-79; Wed, 25 Apr 2007 10:44:10 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hgij3-00086T-7n for sipping-confirm+ok@megatron.ietf.org;
	Wed, 25 Apr 2007 10:44:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hgij2-00086D-T2
	for sipping@ietf.org; Wed, 25 Apr 2007 10:44:08 -0400
Received: from alnrmhc13.comcast.net ([204.127.225.93])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Hgij1-0006um-Hp
	for sipping@ietf.org; Wed, 25 Apr 2007 10:44:08 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (alnrmhc13) with ESMTP
	id <20070425144406b1300ds2ape>; Wed, 25 Apr 2007 14:44:06 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l3PEi5UA002353
	for <sipping@ietf.org>; Wed, 25 Apr 2007 10:44:05 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l3PEi5bN002349;
	Wed, 25 Apr 2007 10:44:05 -0400
Date: Wed, 25 Apr 2007 10:44:05 -0400
Message-Id: <200704251444.l3PEi5bN002349@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <2AF8FF7D89242541B12E7A47F6ECB4BE055EBC73@ftrdmel3.rd.francetelecom.fr>
	(youssef.chadli@orange-ftgroup.com)
Subject: Re: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
References: <2AF8FF7D89242541B12E7A47F6ECB4BE055EBC73@ftrdmel3.rd.francetelecom.fr>
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: "CHADLI Youssef RD-CORE-ISS" <youssef.chadli@orange-ftgroup.com>

   To prevent malicious attacks, it's necessary to prevent untrusted
   elements to access load information of the SIP servers.

As other have said, this point needs further elaboration.

   2) Big SIP server are in general implemented as a cluster of servers
   with one or more front-end servers. The frond-end server interfaces to
   the other SIP nodes and performs load balancing on the different servers
   of the cluster. In such a case, the load control mechanism can be
   implemented and managed only by front-ends servers as only those servers
   can know the overall load of the cluster. It's then important that the
   overload mechanism can be easily centralised on the front-ends servers
   in this case. Consequently, I propose to add a requirement on this;
   something like:

The fact that the load balancing actions are performed by the
front-end servers does not imply that that the overload mechanism
implementation is "centralised" on those front-end servers.  (And
given that there may be more than one front-end server, in what sense
can anything be "centralised" on them?)

A much better requirement would be to provide the diagram of the
architecture you are concerned with:

        +----------+    +----------+      +----------+  
        | Server#1 |    | Server#2 |..... | Server#n | 
        +----------+    +----------+      +----------+
                  |         |              | 
                  |         |              |
                  |         |              | 
                  |     +----------+       | 
                  +-----| Front-End|-------+
                        | Server   |      
                        +----------+ 

and state a requirement that the solution work effectively in such an
architecture.

(Although I would prefer to see the requirment generalized to several
front-end servers feeding one cluster of servers -- the front-end
servers must cooperate in balancing the load they deliver to the
servers.)

Dale


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 25 11:04:50 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hgj33-0008Pc-3b; Wed, 25 Apr 2007 11:04:49 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hgj31-0008PX-6M for sipping-confirm+ok@megatron.ietf.org;
	Wed, 25 Apr 2007 11:04:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hgj30-0008PO-T2
	for sipping@ietf.org; Wed, 25 Apr 2007 11:04:46 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hgj2y-00066w-Hf
	for sipping@ietf.org; Wed, 25 Apr 2007 11:04:46 -0400
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l3PF4fS22629; Wed, 25 Apr 2007 15:04:41 GMT
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, 25 Apr 2007 10:04:41 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB16E797D5@zrc2hxm1.corp.nortel.com>
In-Reply-To: <E3F9D87C63E2774390FE67C924EC99BB16E79744@zrc2hxm1.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Updates to SIPPING WG Review process spreadsheets,
	reviews and reviewer list
Thread-Index: Acdy6VjsrIcVcC7GRquyyNzxwHveVAUXdyqg
From: "Mary Barnes" <mary.barnes@nortel.com>
To: <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: gonzalo.camarillo@ericsson.com
Subject: [Sipping] Updates to SIPPING WG Review process spreadsheets,
	reviews and reviewer list
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi all,=20

I've updated the spreadsheets with the recent reviews and new reviewers
for documents undergoing WGLC:=20
http://www.softarmor.com/sipping/process/review_procedure.html (root
directory for reviews/process)=20

http://www.softarmor.com/sipping/process/wg-review/sipping-rt.html=20
(sorted by Review due date - most useful for WG to know what they should
be reviewing now)=20

http://www.softarmor.com/sipping/process/wg-review/sipping-rt-rev-due.ht
ml
(sorted by revision due date - most useful for doc editors to know when
their next update is expected)=20

http://www.softarmor.com/sipping/process/wg-review/sipping-rt-wglc.html=20
(sorted by WGLC dates - most useful for tracking official WG milestones)


http://www.softarmor.com/sipping/process/wg-review/sipping-rt-editor.htm
l=20
(sorted by document editor - most useful for document editors to know
how to prioritize work)=20

In addition, the list of Reviewers has been updated with new reviewers:
http://www.softarmor.com/sipping/process/wg-review/sipping-reviewer-list
.html

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The following summarizes some of the most relevant information from the
spreadsheets, including who has the token in terms of actions on the
document:=20


Docs currently undergoing WGLC:=20
------------------------------
- draft-ietf-sipping-race-examples-02.txt (WGLC 23 April - 14 May 2007)
Token: WG, reviewers: Vijay Gurbani =20
Note: Still need more reviewers!


Docs having completed WGLC:=20
------------------------------
- draft-ietf-sipping-ipv6-torture-tests-01 (WGLC ended on 06 April 2007)
(-02 now available )
Token: reviewers (to double-check changes are okay):  AB Nataraju, AC
Mahendran=20

- draft-ietf-sipping-cc-framework-07 (WGLC ended on 13 April 2007) =20
Token: Editor to make updates, per nits identified


Docs having been forwarded to AD for publication:=20
--------------------------------------------------
- draft-ietf-sipping-sbc-funcs-03  Token: AD


Docs ready to be forwarded to AD for publication:=20
--------------------------------------------------
- draft-ietf-sipping-consent-format-03.txt    Token: Chair (once -03
available in repository)
- draft-ietf-sipping-pending-additions-02.txt Token: Chair=20


Docs planned for WGLC during May/June 2007:=20
-------------------------------------------=20
- draft-ietf-sipping-overload-reqs-00 (WGLC 30 April - 21 May 2007)
Token: WG to provide feedback as to readiness
Note: will need dedicated reviewers.

- draft-ietf-sipping-config-framework-12 (WGLC 14 May - 11 June 2007)
Token: Design Team, WG

WGLC of the following 2 documents coordinated with WGLC of
draft-ietf-sip-policy-framework (Token: Document editor (Volker Hilt) to
update by date indicated for "Revision Due" in the spreadsheet):=20
-  draft-ietf-sipping-policy-package-03 (WGLC 21 May - 11 Jun 2007)=20
-  draft-ietf-sipping-media-policy-dataset-03 (WGLC 21 May - 11 Jun
2007)=20

- draft-ietf-sipping-sip-offeranswer-00.txt (WGLC 11 June - 9 July 2007)
Token: Doc editor (Takuya Sawada) to submit -01


-----------------------------------=20
Regards,=20
Mary=20
SIPPING WG co-chair=20


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Wed Apr 25 15:50:55 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgnVj-0005bV-G2; Wed, 25 Apr 2007 15:50:43 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HgnVZ-0005OK-Hg for sipping-confirm+ok@megatron.ietf.org;
	Wed, 25 Apr 2007 15:50:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgnVZ-0005Nw-5c; Wed, 25 Apr 2007 15:50:33 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HgnVY-0006fL-PV; Wed, 25 Apr 2007 15:50:33 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id B24762AC89;
	Wed, 25 Apr 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HgnV4-000796-EY; Wed, 25 Apr 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HgnV4-000796-EY@stiedprstage1.ietf.org>
Date: Wed, 25 Apr 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-consent-format-03.txt 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: A Document Format for Requesting Consent
	Author(s)	: G. Camarillo
	Filename	: draft-ietf-sipping-consent-format-03.txt
	Pages		: 13
	Date		: 2007-4-25
	
This document defines an Extensible Markup Language (XML) format for
   a permission document used to request consent.  A permission document
   written in this format is used by a relay to request a specific
   recipient permission to perform a particular routing translation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-consent-format-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-sipping-consent-format-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-consent-format-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-4-25112233.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-consent-format-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-consent-format-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-4-25112233.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--NextPart--






From sipping-bounces@ietf.org Wed Apr 25 23:17:03 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HguTb-0004nG-5t; Wed, 25 Apr 2007 23:16:59 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HguTZ-0004hs-JC for sipping-confirm+ok@megatron.ietf.org;
	Wed, 25 Apr 2007 23:16:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HguTZ-0004hk-9P
	for sipping@ietf.org; Wed, 25 Apr 2007 23:16:57 -0400
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HguTX-0001ch-Ts
	for sipping@ietf.org; Wed, 25 Apr 2007 23:16:57 -0400
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l3Q3Gtj6007713
	for <sipping@ietf.org>; Wed, 25 Apr 2007 22:16:55 -0500 (CDT)
Received: from [135.244.34.99] (vkg.lra.lucent.com [135.244.34.99])
	by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id
	l3Q3GtA09152
	for <sipping@ietf.org>; Wed, 25 Apr 2007 22:16:55 -0500 (CDT)
Message-ID: <463019A7.9040500@alcatel-lucent.com>
Date: Wed, 25 Apr 2007 22:16:55 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: SIPPING LIST <sipping@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [Sipping] Post-WGLC revision of ipv6-torture-tests
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Folks: Based on the WGLC comments, a new revision of
sip-torture-tests (-02) has appeared in the IETF archives.

http://www.ietf.org/internet-drafts/draft-ietf-sipping-ipv6-torture-tests-02.txt

Would the WGLC reviewers kindly make sure that their comments
and concerns from -01 were adequately addressed in -02?

Chairs: barring any other changes, the document is now ready to
progress further.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 26 02:50:20 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hgxo0-0003Iu-RT; Thu, 26 Apr 2007 02:50:16 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hg0O5-0002Pj-4U for sipping-confirm+ok@megatron.ietf.org;
	Mon, 23 Apr 2007 11:23:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg0O4-0002Pb-R7
	for sipping@ietf.org; Mon, 23 Apr 2007 11:23:32 -0400
Received: from paoakoavas09.cable.comcast.com ([208.17.35.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg0O0-0000ya-QB
	for sipping@ietf.org; Mon, 23 Apr 2007 11:23:32 -0400
Received: from ([10.52.116.31])
	by paoakoavas09.cable.comcast.com with ESMTP  id KP-NTF18.42191943;
	Mon, 23 Apr 2007 11:23:00 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	PAOAKEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 23 Apr 2007 11:23:00 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 23 Apr 2007 11:22:59 -0400
Message-ID: <EF2F0EC839870F43A6637360BC12ABD401462A9F@PACDCEXCMB05.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-vanelburg-sipping-served-user-00.txt
Thread-Index: AceFu0a57pd1MYB4Rm25lib0USwlkw==
From: "Khan, Sohel" <Sohel_Khan@cable.comcast.com>
To: <HansErik.van.Elburg@ericsson.com>,
	<sipping@ietf.org>
X-OriginalArrivalTime: 23 Apr 2007 15:23:00.0768 (UTC)
	FILETIME=[47769200:01C785BB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a630332fa112280ecc4c4186b5c9ea83
X-Mailman-Approved-At: Thu, 26 Apr 2007 02:50:14 -0400
Cc: 
Subject: [Sipping] draft-vanelburg-sipping-served-user-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1986355117=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1986355117==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C785BB.469029C5"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C785BB.469029C5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

Review comments to improve the
draft-vanelburg-sipping-served-user-00.txt:

Introduction needs revising to include problem statements (a summary of
the scenarios of chapter 3), summary of the requirement to resolve
issues, and proposal (addition of a new P-header field) presented in
chapter 5. At a current form, the introduction is very confusing. Also,
it will be helpful to include abstract call flows in the scenarios
presented in chapter 3.=20

=20

=20

Thank you.

=20

Sincerely,


Sohel Khan, Ph.D.

Product Engineering
Comcast Cable Communications
1500 Market St, Philadelphia, PA.
Ph: (215) 286-4853 (o)
      (215)-828-6896 (m), (913-)486-3145 (m)

This message and any attachments to it may contain PROPRIETARY AND
CONFIDENTIAL INFORMATION exclusively for intended recipients. Please DO
NOT FORWARD OR DISTRIBUTE to anyone else. If you are not the intended
recipient, please contact the sender and delete all copies of this
e-mail from your system.

From: Hans Erik van Elburg (RY/ETM) [mailto:hanserik.van.elburg at
ericsson.com]=20
Sent: Tuesday, April 17, 2007 3:12 PM
To: sipping at ietf.org
Subject: [Sipping] New I-D for P-Served-User header

=20

I uploaded a new draft for the P-Served-User Private-Header, until it
gets available on the online Internet-Drafts directory you can retrieve
it here:

http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user
-00.txt
<http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-use
r-00.txt> =20

Abstract

   This document specifies the SIP P-Served-User P-header.  This header
   field addresses an issue that was found in the 3rd-Generation
   Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an
   S-CSCF (Serving Call Session Control Function) and an AS (Application
   Server) on the ISC (IMS Subsystem Service Control) interface to
   convey the identity of the served user and the session case that
   applies to this particular communication session and application
   invocation.

Best Regards,=20

/Hans Erik=20

=20


------_=_NextPart_001_01C785BB.469029C5
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns0=3D"urn:schemas-microsoft-com:office:smarttags">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Review comments to improve the =
draft-vanelburg-sipping-served-user-00.txt:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Introduction needs revising to include problem =
statements (a
summary of the scenarios of chapter 3), summary of the requirement to =
resolve
issues, and proposal (addition of a new P-header field) presented in =
chapter 5.
At a current form, the introduction is very confusing. Also, it will be =
helpful
to include abstract call flows in the scenarios presented in chapter 3. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thank you.</span></font><o:p></o:p></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Sincerely,</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'><br>
</span></font><font size=3D1 color=3Dnavy face=3DArial><span =
style=3D'font-size:7.5pt;
font-family:Arial;color:navy'>Sohel Khan, =
Ph.D.</span></font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D1 color=3Dnavy face=3DArial><span =
style=3D'font-size:7.5pt;font-family:Arial;
color:navy'>Product Engineering<br>
Comcast Cable Communications<br>
</span></font><font size=3D1 face=3DArial><span =
style=3D'font-size:7.5pt;font-family:
Arial'><ns0:address w:insAuthor=3D"Comcast User" =
w:insDate=3D"2007-04-23T11:05:00Z"
 w:endInsAuthor=3D"Comcast User" =
w:endInsDate=3D"2007-04-23T11:05:00Z"><ns0:Street
  w:insAuthor=3D"Comcast User" w:insDate=3D"2007-04-23T11:05:00Z"
  w:endInsAuthor=3D"Comcast User" =
w:endInsDate=3D"2007-04-23T11:05:00Z"><st1:address
  w:st=3D"on"><st1:Street w:st=3D"on"><font color=3Dnavy><span =
style=3D'color:navy'>1500
    Market St</span></font></st1:Street></ns0:Street></st1:address><font
 color=3Dnavy><span style=3D'color:navy'>, </span></font><ns0:City
  w:insAuthor=3D"Comcast User" w:insDate=3D"2007-04-23T11:05:00Z"
  w:endInsAuthor=3D"Comcast User" =
w:endInsDate=3D"2007-04-23T11:05:00Z"><st1:City
  w:st=3D"on"><font color=3Dnavy><span =
style=3D'color:navy'>Philadelphia</span></font></st1:City></ns0:City><fon=
t
 color=3Dnavy><span style=3D'color:navy'>, </span></font><ns0:State
  w:insAuthor=3D"Comcast User" w:insDate=3D"2007-04-23T11:05:00Z"
  w:endInsAuthor=3D"Comcast User" =
w:endInsDate=3D"2007-04-23T11:05:00Z"><st1:State
  w:st=3D"on"><font color=3Dnavy><span =
style=3D'color:navy'>PA.</span></font></st1:State></ns0:State></ns0:addre=
ss><font
color=3Dnavy><span style=3D'color:navy'><br>
Ph: (215) 286-4853 (o)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (215)-828-6896 (m), (913-)486-3145 =
(m)</span></font></span></font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D1 color=3Dnavy face=3DArial><span =
style=3D'font-size:7.5pt;font-family:Arial;
color:navy'>This message and any attachments to it may contain =
PROPRIETARY AND
CONFIDENTIAL INFORMATION exclusively for intended recipients. Please DO =
NOT
FORWARD OR DISTRIBUTE to anyone else. If you are not the intended =
recipient,
please contact the sender and delete all copies of this e-mail from your =
system.</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:
bold'>From:</span></font></b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma'> Hans Erik van Elburg (RY/ETM)
[mailto:hanserik.van.elburg at ericsson.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, April 17, =
2007 3:12
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> sipping at =
ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Sipping] New =
I-D for
P-Served-User header</span></font><O:P></O:P><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'><O:P>&nbsp;</O:P><o:p></o:p></span></font></p>=


<p><font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:maroon'>I uploaded a new draft for the =
P-Served-User
Private-Header, until it gets available on the online Internet-Drafts =
directory
you can retrieve it here:</span></font><O:P></O:P><o:p></o:p></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'><a
href=3D"http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serv=
ed-user-00.txt"><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>http://elburg.eln-research.n=
l/drafts/draft-vanelburg-sipping-served-user-00.txt</span></font></a></sp=
an></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> =
</span></font><o:p></o:p></p>

<O:P></O:P>

<p><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Abstract<br>
<br>
&nbsp;&nbsp; This document specifies the SIP P-Served-User =
P-header.&nbsp; This
header<br>
&nbsp;&nbsp; field addresses an issue that was found in the =
3rd-Generation<br>
&nbsp;&nbsp; Partnership Project (3GPP) IMS (IP Multimedia Subsystem) =
between
an<br>
&nbsp;&nbsp; S-CSCF (Serving Call Session Control Function) and an AS
(Application<br>
&nbsp;&nbsp; Server) on the ISC (IMS Subsystem Service Control) =
interface to<br>
&nbsp;&nbsp; convey the identity of the served user and the session case =
that<br>
&nbsp;&nbsp; applies to this particular communication session and =
application<br>
&nbsp;&nbsp; invocation.<br>
</span></font><br>
<font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:maroon'>Best Regards,</span></font> =
<O:P></O:P><o:p></o:p></p>

<p><b><font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:maroon;font-weight:bold'>/Hans =
Erik</span></font></b> <O:P></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C785BB.469029C5--



--===============1986355117==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1986355117==--





From sipping-bounces@ietf.org Thu Apr 26 04:18:04 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgzAw-0006Re-Ds; Thu, 26 Apr 2007 04:18:02 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HgzAv-0006RK-4E for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 04:18:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgzAu-0006R9-6M
	for sipping@ietf.org; Thu, 26 Apr 2007 04:18:00 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgzAs-0006HO-Dy
	for sipping@ietf.org; Thu, 26 Apr 2007 04:18:00 -0400
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
Subject: RE: [Sipping]
	I-DACTION:draft-ietf-sipping-uri-list-conferencing-05.txt 
Date: Thu, 26 Apr 2007 11:18:21 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C0484E8BC@IsrExch01.israel.polycom.com>
In-Reply-To: <E1FDs7u-0005i9-48@stiedprstage1.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping]
	I-DACTION:draft-ietf-sipping-uri-list-conferencing-05.txt 
Thread-Index: AcY7+K/OZrChJZQIS0erlS2HpUZwz1L4nzmg
From: "Even, Roni" <roni.even@polycom.co.il>
To: <sipping@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: Mary Barnes <mary.barnes@nortelnetworks.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi,
I was wondering what the status of this draft is since it shows that it
expired.
=20
Thanks
Roni Even

> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Tuesday, February 28, 2006 1:50 AM
> To: i-d-announce@ietf.org
> Cc: sipping@ietf.org
> Subject: [Sipping] I-DACTION:draft-ietf-sipping-uri-list-conferencing-
> 05.txt
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Session Initiation Proposal
Investigation
> Working Group of the IETF.
>=20
> 	Title		: Conference Establishment Using
Request-Contained Lists
> in the Session Initiation Protocol (SIP)
> 	Author(s)	: G. Camarillo, A. Johnston
> 	Filename	:
draft-ietf-sipping-uri-list-conferencing-05.txt
> 	Pages		: 14
> 	Date		: 2006-2-27
>=20
> This document describes how to create a conference using SIP URI-list
> services.  In particular, it describes a mechanism that allows a
> client to provide a conference server with the initial list of
> participants using an INVITE-contained URI-list.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-uri-list-
> conferencing-05.txt
>=20
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
the
> message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>=20
>=20
> Internet-Drafts are also available by anonymous FTP. Login with the
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-sipping-uri-list-conferencing-05.txt".
>=20
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-sipping-uri-list-conferencing-
> 05.txt".
>=20
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>=20
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 26 04:24:04 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgzGl-0003J5-6o; Thu, 26 Apr 2007 04:24:03 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HgzGi-0003Ip-7O for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 04:24:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgzGh-0003Ie-LJ
	for sipping@ietf.org; Thu, 26 Apr 2007 04:23:59 -0400
Received: from szxga04-in.huawei.com ([61.144.161.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgzGh-0008SH-06
	for sipping@ietf.org; Thu, 26 Apr 2007 04:23:59 -0400
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JH300FF5JAPHV@szxga04-in.huawei.com> for
	sipping@ietf.org; Thu, 26 Apr 2007 16:23:13 +0800 (CST)
Received: from szxmp02-in.huawei.com ([172.24.2.32])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JH300KWHJA53G@szxga04-in.huawei.com> for
	sipping@ietf.org; Thu, 26 Apr 2007 16:23:13 +0800 (CST)
Received: from 172.24.1.24 (EHLO huawei.com) ([172.24.1.24])
	by szxmp02-in.huawei.com (MOS 3.8.4-GA FastPath queued)
	with ESMTP id AHP05393; Fri, 27 Apr 2007 16:22:42 +0800 (CST)
Received: from t34932 ([10.70.108.106])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JH300AF0JAIN2@szxml04-in.huawei.com> for
	sipping@ietf.org; Thu, 26 Apr 2007 16:23:09 +0800 (CST)
Date: Thu, 26 Apr 2007 16:23:06 +0800
From: Linyi Tian <tianlinyi@huawei.com>
Subject: RE: [Sipping]	I-DACTION:draft-ietf-sipping-uri-list-conferencing-05.txt
In-reply-to: <144ED8561CE90C41A3E5908EDECE315C0484E8BC@IsrExch01.israel.polycom.com>
To: "'Even, Roni'" <roni.even@polycom.co.il>, sipping@ietf.org
Message-id: <015601c787dc$1deaf200$6a6c460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7BIT
Thread-index: AcY7+K/OZrChJZQIS0erlS2HpUZwz1L4nzmgAAAz+BA=
X-Junkmail-IP-Whitelist: YES (by domain ip whitelist at szxmp02-in.huawei.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: 'Mary Barnes' <mary.barnes@nortelnetworks.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi Roni
It was moved to SIP WG. The new name is: draft-ietf-sip-uri-list-conferencing-01.txt
Best Regards,
Linyi

-----Original Message-----
From: Even, Roni [mailto:roni.even@polycom.co.il] 
Sent: Thursday, April 26, 2007 4:18 PM
To: sipping@ietf.org
Cc: Mary Barnes
Subject: RE: [Sipping] I-DACTION:draft-ietf-sipping-uri-list-conferencing-05.txt

Hi,
I was wondering what the status of this draft is since it shows that it
expired.
 
Thanks
Roni Even

> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Tuesday, February 28, 2006 1:50 AM
> To: i-d-announce@ietf.org
> Cc: sipping@ietf.org
> Subject: [Sipping] I-DACTION:draft-ietf-sipping-uri-list-conferencing-
> 05.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Session Initiation Proposal
Investigation
> Working Group of the IETF.
> 
> 	Title		: Conference Establishment Using
Request-Contained Lists
> in the Session Initiation Protocol (SIP)
> 	Author(s)	: G. Camarillo, A. Johnston
> 	Filename	:
draft-ietf-sipping-uri-list-conferencing-05.txt
> 	Pages		: 14
> 	Date		: 2006-2-27
> 
> This document describes how to create a conference using SIP URI-list
> services.  In particular, it describes a mechanism that allows a
> client to provide a conference server with the initial list of
> participants using an INVITE-contained URI-list.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-uri-list-
> conferencing-05.txt
> 
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
the
> message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
> 
> 
> Internet-Drafts are also available by anonymous FTP. Login with the
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-sipping-uri-list-conferencing-05.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-sipping-uri-list-conferencing-
> 05.txt".
> 
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.


_______________________________________________
Sipping mailing list  https://www1.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




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 26 05:47:46 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh0Zg-0000w6-CP; Thu, 26 Apr 2007 05:47:40 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hh0Zf-0000w1-4I for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 05:47:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh0Ze-0000vt-OS
	for sipping@ietf.org; Thu, 26 Apr 2007 05:47:38 -0400
Received: from [203.187.132.25] (helo=tapal.aricent.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh0Zd-0003Oh-17
	for sipping@ietf.org; Thu, 26 Apr 2007 05:47:38 -0400
Received: from tapal.aricent.com (localhost [127.0.0.1])
	by tapal.aricent.com (8.13.8/8.13.8) with ESMTP id l3Q9kGP9030417
	for <sipping@ietf.org>; Thu, 26 Apr 2007 15:16:16 +0530
Received: from pragati.blr.hss.hns.com (pragati.blr.hss.hns.com 
	[10.203.193.22])by tapal.aricent.com (8.13.8/8.13.8) with ESMTP id 
	l3Q9kGiY030414for <sipping@ietf.org>; Thu, 26 Apr 2007 15:16:16 +0530
To: sipping@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OF6934D3A1.1CC2A5F1-ON652572C9.0034FFBD-652572C9.0035F075@flextronicssoftware.com>
From: Preethi.Sadasivan@aricent.com
Date: Thu, 26 Apr 2007 15:17:29 +0530
X-MIMETrack: Serialize by Router on Pragati/BLR/HSS(Release 6.5.5|November 
	30, 2005) at04/26/2007 03:13:43 PM,Serialize complete at 04/26/2007 
	03:13:43 PM
X-imss-version: 2.046
X-imss-result: Passed
X-imss-scanInfo: M:B L:N SM:2
X-imss-tmaseResult: TT:1 TS:-15.5478 TC:1F TRN:53 TV:3.6.1039(15138.002)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:2 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: Preethi.Sadasivan@aricent.com
Subject: [Sipping] 433 error response format.
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1975704558=="
Errors-To: sipping-bounces@ietf.org

This is a multipart message in MIME format.
--===============1975704558==
Content-Type: multipart/alternative;
	boundary="=_alternative 0035F06F652572C9_="

This is a multipart message in MIME format.
--=_alternative 0035F06F652572C9_=
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: base64

SGkgQWxsLA0KICBJIGhhdmUgYSBxdWVyeSB3aXRoIHJlZmVyZW5jZSB0byB0aGUgZm9sbG93aW5n
IGxpbmVzIGZyb20gdGhlIGRyYWZ0ICAiDQpkcmFmdC1pZXRmLXNpcC1hY3ItY29kZS0wNC50eHQi
IA0KZm9yIDQzMyBlcnJvciByZXNwb25zZSBTZWN0aW9uIDQuDQoNCjQgLlVBQyBCZWhhdmlvcg0K
DQogICBBIFVBQyByZWNlaXZpbmcgYSA0MzMgKEFub255bWl0eSBEaXNhbGxvd2VkKSBNVVNUIE5P
VCByZXRyeSB0aGUNCiAgIHJlcXVlc3Qgd2l0aG91dCBhbm9ueW1pdHkgdW5sZXNzIGl0IG9idGFp
bnMgY29uZmlybWF0aW9uIGZyb20gdGhlDQogICB1c2VyIHRoYXQgdGhpcyBpcyBkZXNpcmFibGUu
ICBTdWNoIGNvbmZpcm1hdGlvbiBjb3VsZCBiZSBvYnRhaW5lZA0KICAgdGhyb3VnaCB0aGUgdXNl
ciBpbnRlcmZhY2UsIG9yIGJ5IGFjY2Vzc2luZyB1c2VyIGRlZmluZWQgcG9saWN5LiAgSWYNCiAg
IHRoZSB1c2VyIGhhcyBpbmRpY2F0ZWQgdGhhdCB0aGlzIGlzIGRlc2lyYWJsZSwgdGhlIFVBQyBN
QVkgcmV0cnkgdGhlDQogICByZXF1ZXN0IHdpdGhvdXQgcmVxdWVzdGluZyBhbm9ueW1pdHkuIA0K
DQpIb3cgd2lsbCB0aGUgVUFTIGluZGljYXRlIHRoZSBVQUMgdGhhdCBpdCBoYXMgYSBkZXNpcmUg
Zm9yIHRoZSByZXF1ZXN0IHRvIA0KYmUgcmV0cmllZC4gV2lsbCB0aGlzIGJlIGNvbW11bmljYXRl
ZCBpbiBzb21lIGhlYWRlcnMgbGlrZSB0aGF0IG9mIA0KUmV0cnktSGVhZGVyLg0KUGxlYXNlIHRo
cm93IHNvbWUgbGlnaHQgb24gdGhpcyBpc3N1ZS4NCg0KDQpUaGFua3MgYW5kIFJlZ2FyZHMsDQog
UHJlZXRoaS4uDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClByZWV0aGkgU2FkYXNpdmFuLA0KU29m
dHdhcmUgRW5naW5lZXIsDQpBUklDRU5UICwNCkJhbmdhbG9yZS4NCnRlbDogKzkxLTgwLTQxMDY5
MTE4DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KDQoqKioqKioqKioqKioqKioqKioqKioqKiAg
QXJpY2VudC1Qcml2YXRlICAgKioqKioqKioqKioqKioqKioqKioqKioNCiJESVNDTEFJTUVSOiBU
aGlzIG1lc3NhZ2UgaXMgcHJvcHJpZXRhcnkgdG8gQXJpY2VudCBhbmQgaXMgaW50ZW5kZWQgc29s
ZWx5IGZvciB0aGUgdXNlIG9mIAp0aGUgaW5kaXZpZHVhbCB0byB3aG9tIGl0IGlzIGFkZHJlc3Nl
ZC4gSXQgbWF5IGNvbnRhaW4gcHJpdmlsZWdlZCBvciBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24g
YW5kIHNob3VsZCBub3QgYmUgCmNpcmN1bGF0ZWQgb3IgdXNlZCBmb3IgYW55IHB1cnBvc2Ugb3Ro
ZXIgdGhhbiBmb3Igd2hhdCBpdCBpcyBpbnRlbmRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhp
cyBtZXNzYWdlIGluIGVycm9yLCAKcGxlYXNlIG5vdGlmeSB0aGUgb3JpZ2luYXRvciBpbW1lZGlh
dGVseS4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwgeW91IGFyZSBub3Rp
ZmllZCB0aGF0IHlvdSBhcmUgc3RyaWN0bHkKcHJvaGliaXRlZCBmcm9tIHVzaW5nLCBjb3B5aW5n
LCBhbHRlcmluZywgb3IgZGlzY2xvc2luZyB0aGUgY29udGVudHMgb2YgdGhpcyBtZXNzYWdlLiBB
cmljZW50IGFjY2VwdHMgbm8gcmVzcG9uc2liaWxpdHkgZm9yIApsb3NzIG9yIGRhbWFnZSBhcmlz
aW5nIGZyb20gdGhlIHVzZSBvZiB0aGUgaW5mb3JtYXRpb24gdHJhbnNtaXR0ZWQgYnkgdGhpcyBl
bWFpbCBpbmNsdWRpbmcgZGFtYWdlIGZyb20gdmlydXMuIgo=
--=_alternative 0035F06F652572C9_=
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpIEFsbCw8L2ZvbnQ+DQo8YnI+
PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyBJIGhhdmUgYSBxdWVyeSB3aXRo
IHJlZmVyZW5jZQ0KdG8gdGhlIGZvbGxvd2luZyBsaW5lcyBmcm9tIHRoZSBkcmFmdCAmbmJzcDsm
cXVvdDs8Yj5kcmFmdC1pZXRmLXNpcC1hY3ItY29kZS0wNC50eHQ8L2I+JnF1b3Q7DQo8L2ZvbnQ+
DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPmZvciA0MzMgZXJyb3IgcmVzcG9u
c2UgU2VjdGlvbiA0LjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1z
ZXJpZiI+NCAuVUFDIEJlaGF2aW9yPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNl
PSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7QSBVQUMgcmVjZWl2aW5nIGEgNDMzIChBbm9ueW1p
dHkNCkRpc2FsbG93ZWQpIE1VU1QgTk9UIHJldHJ5IHRoZTwvZm9udD4NCjxicj48Zm9udCBzaXpl
PTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO3JlcXVlc3Qgd2l0aG91dCBhbm9ueW1p
dHkNCnVubGVzcyBpdCBvYnRhaW5zIGNvbmZpcm1hdGlvbiBmcm9tIHRoZTwvZm9udD4NCjxicj48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO3VzZXIgdGhhdCB0aGlz
IGlzIGRlc2lyYWJsZS4NCiZuYnNwO1N1Y2ggY29uZmlybWF0aW9uIGNvdWxkIGJlIG9idGFpbmVk
PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7
dGhyb3VnaCB0aGUgdXNlciBpbnRlcmZhY2UsDQpvciBieSBhY2Nlc3NpbmcgdXNlciBkZWZpbmVk
IHBvbGljeS4gJm5ic3A7SWY8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2Vy
aWYiPiZuYnNwOyAmbmJzcDt0aGUgdXNlciBoYXMgaW5kaWNhdGVkDQp0aGF0IHRoaXMgaXMgZGVz
aXJhYmxlLCB0aGUgVUFDIE1BWSByZXRyeSB0aGU8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZh
Y2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDtyZXF1ZXN0IHdpdGhvdXQgcmVxdWVzdGluZw0K
YW5vbnltaXR5LiA8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2Vy
aWYiPkhvdyB3aWxsIHRoZSBVQVMgaW5kaWNhdGUgdGhlIFVBQyB0aGF0DQppdCBoYXMgYSBkZXNp
cmUgZm9yIHRoZSByZXF1ZXN0IHRvIDwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fu
cy1zZXJpZiI+YmUgcmV0cmllZC4gV2lsbCB0aGlzIGJlIGNvbW11bmljYXRlZA0KaW4gc29tZSBo
ZWFkZXJzIGxpa2UgdGhhdCBvZiBSZXRyeS1IZWFkZXIuPC9mb250Pg0KPGJyPjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj5QbGVhc2UgdGhyb3cgc29tZSBsaWdodCBvbiB0aGlzIGlzc3Vl
Ljxicj4NCjxicj4NCjxicj4NClRoYW5rcyBhbmQgUmVnYXJkcyw8YnI+DQogUHJlZXRoaS4uPGJy
Pg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPGJyPg0KUHJlZXRoaSBTYWRhc2l2YW4sPGJyPg0KU29m
dHdhcmUgRW5naW5lZXIsPGJyPg0KQVJJQ0VOVCAsPGJyPg0KQmFuZ2Fsb3JlLjxicj4NCnRlbDog
KzkxLTgwLTQxMDY5MTE4PGJyPg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPGJyPg0KPGJyPg0KPGJy
Pg0KKioqKioqKioqKioqKioqKioqKioqKiogJm5ic3A7QXJpY2VudC1Qcml2YXRlICZuYnNwOyAq
KioqKioqKioqKioqKioqKioqKioqKjwvZm9udD4NCjx0YWJsZT48dHI+PHRkIGJnY29sb3I9I2Zm
ZmZmZj48Zm9udCBjb2xvcj0jMDAwMDAwPjxwcmU+IkRJU0NMQUlNRVI6IFRoaXMgbWVzc2FnZSBp
cyBwcm9wcmlldGFyeSB0byBBcmljZW50IGFuZCBpcyBpbnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1
c2Ugb2YgCnRoZSBpbmRpdmlkdWFsIHRvIHdob20gaXQgaXMgYWRkcmVzc2VkLiBJdCBtYXkgY29u
dGFpbiBwcml2aWxlZ2VkIG9yIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiBhbmQgc2hvdWxkIG5v
dCBiZSAKY2lyY3VsYXRlZCBvciB1c2VkIGZvciBhbnkgcHVycG9zZSBvdGhlciB0aGFuIGZvciB3
aGF0IGl0IGlzIGludGVuZGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIG1lc3NhZ2UgaW4g
ZXJyb3IsIApwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9yIGltbWVkaWF0ZWx5LiBJZiB5b3Ug
YXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCB5b3UgYXJlIG5vdGlmaWVkIHRoYXQgeW91
IGFyZSBzdHJpY3RseQpwcm9oaWJpdGVkIGZyb20gdXNpbmcsIGNvcHlpbmcsIGFsdGVyaW5nLCBv
ciBkaXNjbG9zaW5nIHRoZSBjb250ZW50cyBvZiB0aGlzIG1lc3NhZ2UuIEFyaWNlbnQgYWNjZXB0
cyBubyByZXNwb25zaWJpbGl0eSBmb3IgCmxvc3Mgb3IgZGFtYWdlIGFyaXNpbmcgZnJvbSB0aGUg
dXNlIG9mIHRoZSBpbmZvcm1hdGlvbiB0cmFuc21pdHRlZCBieSB0aGlzIGVtYWlsIGluY2x1ZGlu
ZyBkYW1hZ2UgZnJvbSB2aXJ1cy4iCjwvcHJlPjwvZm9udD48L3RkPjwvdHI+PC90YWJsZT4=
--=_alternative 0035F06F652572C9_=--



--===============1975704558==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1975704558==--





From sipping-bounces@ietf.org Thu Apr 26 06:07:46 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh0t5-00086T-Q5; Thu, 26 Apr 2007 06:07:43 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hh0t5-00085z-Ab for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 06:07:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh0t4-00085m-JI
	for sipping@ietf.org; Thu, 26 Apr 2007 06:07:42 -0400
Received: from ihemail4.lucent.com ([135.245.0.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh0t2-0000N6-9y
	for sipping@ietf.org; Thu, 26 Apr 2007 06:07:42 -0400
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id l3QA6u2u024335;
	Thu, 26 Apr 2007 05:07:33 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Apr 2007 05:05:35 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.26]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Apr 2007 12:05:32 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] 433 error response format.
Date: Thu, 26 Apr 2007 12:05:30 +0200
Message-ID: <5D1A7985295922448D5550C94DE2918001084B97@DEEXC1U01.de.lucent.com>
In-Reply-To: <OF6934D3A1.1CC2A5F1-ON652572C9.0034FFBD-652572C9.0035F075@flextronicssoftware.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] 433 error response format.
Thread-Index: AceH6AJoQoqRvPIuSIqd/XPQmGX0FgAAf7Bw
References: <OF6934D3A1.1CC2A5F1-ON652572C9.0034FFBD-652572C9.0035F075@flextronicssoftware.com>
From: "Drage, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: <Preethi.Sadasivan@aricent.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 26 Apr 2007 10:05:32.0546 (UTC)
	FILETIME=[6D13CE20:01C787EA]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0781960570=="
Errors-To: sipping-bounces@ietf.org

--===============0781960570==
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

Rmlyc3QgZHJhZnQtaWV0Zi1zaXAtYWNyLWNvZGUgYmVsb25ncyB0byBTSVAsIG5vdCBTSVBQSU5H
IGFuZCBpcyBpbiBhIHN0YXRlIG9mIHB1YmxpY2F0aW9uIHJlcXVlc3RlZC4NCiANClRvIGFuc3dl
ciB5b3VyIHF1ZXN0aW9uLCB0aGUgZXJyb3IgaXMgbm90IHRpbWUgZGVwZW5kZW50LCBhbmQgdGhl
cmVmb3JlIGEgUmV0cnktQWZ0ZXIgaGVhZGVyIGlzIGlycmVsZXZhbnQuDQogDQpUaGUgVUFDIHJl
ZnVzZWQgdG8gYWNjZXB0IHRoZSByZXF1ZXN0IGJlY2F1c2UgY2VydGFpbiBjb25kaXRpb25zIHdl
cmUgbm90IG1ldC4gQSByZWF0dGVtcHQgaXMgYWx3YXlzIGFwcHJvcHJpYXRlIGlmIHRoZSBjb25k
aXRpb25zIGNhbiBiZSBtZXQsIG90aGVyd2lzZSB0aGV5IHdpbGwgYWx3YXlzIHByb2R1Y2UgdGhl
IHNhbWUgZmFpbHVyZS4gUmVzb2x1dGlvbiBvZiB0aGUgcHJvYmxlbSBsaWVzIGVudGlyZWx5IHdp
dGggdGhlIFVBQyB3aXRoIG5vIGZ1cnRoZXIgaW5mb3JtYXRpb24gcmVxdWlyZWQgZnJvbSB0aGUg
VUFTLg0KIA0KcmVnYXJkcw0KIA0KS2VpdGgNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KDQoJRnJvbTogUHJlZXRoaS5TYWRhc2l2YW5AYXJpY2VudC5jb20gW21haWx0bzpQ
cmVldGhpLlNhZGFzaXZhbkBhcmljZW50LmNvbV0gDQoJU2VudDogVGh1cnNkYXksIEFwcmlsIDI2
LCAyMDA3IDEwOjQ3IEFNDQoJVG86IHNpcHBpbmdAaWV0Zi5vcmcNCglDYzogUHJlZXRoaS5TYWRh
c2l2YW5AYXJpY2VudC5jb20NCglTdWJqZWN0OiBbU2lwcGluZ10gNDMzIGVycm9yIHJlc3BvbnNl
IGZvcm1hdC4NCgkNCgkNCg0KCUhpIEFsbCwgDQoJICBJIGhhdmUgYSBxdWVyeSB3aXRoIHJlZmVy
ZW5jZSB0byB0aGUgZm9sbG93aW5nIGxpbmVzIGZyb20gdGhlIGRyYWZ0ICAiZHJhZnQtaWV0Zi1z
aXAtYWNyLWNvZGUtMDQudHh0IiANCglmb3IgNDMzIGVycm9yIHJlc3BvbnNlIFNlY3Rpb24gNC4g
DQoJDQoJNCAuVUFDIEJlaGF2aW9yIA0KCQ0KCSAgIEEgVUFDIHJlY2VpdmluZyBhIDQzMyAoQW5v
bnltaXR5IERpc2FsbG93ZWQpIE1VU1QgTk9UIHJldHJ5IHRoZSANCgkgICByZXF1ZXN0IHdpdGhv
dXQgYW5vbnltaXR5IHVubGVzcyBpdCBvYnRhaW5zIGNvbmZpcm1hdGlvbiBmcm9tIHRoZSANCgkg
ICB1c2VyIHRoYXQgdGhpcyBpcyBkZXNpcmFibGUuICBTdWNoIGNvbmZpcm1hdGlvbiBjb3VsZCBi
ZSBvYnRhaW5lZCANCgkgICB0aHJvdWdoIHRoZSB1c2VyIGludGVyZmFjZSwgb3IgYnkgYWNjZXNz
aW5nIHVzZXIgZGVmaW5lZCBwb2xpY3kuICBJZiANCgkgICB0aGUgdXNlciBoYXMgaW5kaWNhdGVk
IHRoYXQgdGhpcyBpcyBkZXNpcmFibGUsIHRoZSBVQUMgTUFZIHJldHJ5IHRoZSANCgkgICByZXF1
ZXN0IHdpdGhvdXQgcmVxdWVzdGluZyBhbm9ueW1pdHkuIA0KCQ0KCUhvdyB3aWxsIHRoZSBVQVMg
aW5kaWNhdGUgdGhlIFVBQyB0aGF0IGl0IGhhcyBhIGRlc2lyZSBmb3IgdGhlIHJlcXVlc3QgdG8g
DQoJYmUgcmV0cmllZC4gV2lsbCB0aGlzIGJlIGNvbW11bmljYXRlZCBpbiBzb21lIGhlYWRlcnMg
bGlrZSB0aGF0IG9mIFJldHJ5LUhlYWRlci4gDQoJUGxlYXNlIHRocm93IHNvbWUgbGlnaHQgb24g
dGhpcyBpc3N1ZS4NCgkNCgkNCglUaGFua3MgYW5kIFJlZ2FyZHMsDQoJUHJlZXRoaS4uDQoJLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tDQoJUHJlZXRoaSBTYWRhc2l2YW4sDQoJU29mdHdhcmUgRW5naW5l
ZXIsDQoJQVJJQ0VOVCAsDQoJQmFuZ2Fsb3JlLg0KCXRlbDogKzkxLTgwLTQxMDY5MTE4DQoJLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tDQoJDQoJDQoJKioqKioqKioqKioqKioqKioqKioqKiogIEFyaWNl
bnQtUHJpdmF0ZSAgICoqKioqKioqKioqKioqKioqKioqKioqIA0KCQkiRElTQ0xBSU1FUjogVGhp
cyBtZXNzYWdlIGlzIHByb3ByaWV0YXJ5IHRvIEFyaWNlbnQgYW5kIGlzIGludGVuZGVkIHNvbGVs
eSBmb3IgdGhlIHVzZSBvZiANCgl0aGUgaW5kaXZpZHVhbCB0byB3aG9tIGl0IGlzIGFkZHJlc3Nl
ZC4gSXQgbWF5IGNvbnRhaW4gcHJpdmlsZWdlZCBvciBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24g
YW5kIHNob3VsZCBub3QgYmUgDQoJY2lyY3VsYXRlZCBvciB1c2VkIGZvciBhbnkgcHVycG9zZSBv
dGhlciB0aGFuIGZvciB3aGF0IGl0IGlzIGludGVuZGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0
aGlzIG1lc3NhZ2UgaW4gZXJyb3IsIA0KCXBsZWFzZSBub3RpZnkgdGhlIG9yaWdpbmF0b3IgaW1t
ZWRpYXRlbHkuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsIHlvdSBhcmUg
bm90aWZpZWQgdGhhdCB5b3UgYXJlIHN0cmljdGx5DQoJcHJvaGliaXRlZCBmcm9tIHVzaW5nLCBj
b3B5aW5nLCBhbHRlcmluZywgb3IgZGlzY2xvc2luZyB0aGUgY29udGVudHMgb2YgdGhpcyBtZXNz
YWdlLiBBcmljZW50IGFjY2VwdHMgbm8gcmVzcG9uc2liaWxpdHkgZm9yIA0KCWxvc3Mgb3IgZGFt
YWdlIGFyaXNpbmcgZnJvbSB0aGUgdXNlIG9mIHRoZSBpbmZvcm1hdGlvbiB0cmFuc21pdHRlZCBi
eSB0aGlzIGVtYWlsIGluY2x1ZGluZyBkYW1hZ2UgZnJvbSB2aXJ1cy4iDQoJDQoJCQ0KDQo=



--===============0781960570==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0781960570==--



From sipping-bounces@ietf.org Thu Apr 26 06:17:17 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh12K-0007OR-2A; Thu, 26 Apr 2007 06:17:16 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hh12I-0007OC-TP for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 06:17:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh12I-0007O3-CF
	for sipping@ietf.org; Thu, 26 Apr 2007 06:17:14 -0400
Received: from [204.200.195.236] (helo=personeta.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh12G-0002ls-GI
	for sipping@ietf.org; Thu, 26 Apr 2007 06:17:14 -0400
Received: from adii ([194.90.193.76]) (authenticated bits=0)
	by personeta.com (8.13.6.20060614/8.13.6) with ESMTP id l3QAH8p1091157
	for <sipping@ietf.org>; Thu, 26 Apr 2007 10:17:10 GMT
Message-Id: <200704261017.l3QAH8p1091157@personeta.com>
From: "adi" <adi@personeta.com>
To: <sipping@ietf.org>
Subject: RE: [Sipping] 433 error response format.
Date: Thu, 26 Apr 2007 13:19:04 +0300
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceH5/kdH4AxqpxaTHe/iC8yPEWS3wAA7P6w
In-Reply-To: <OF6934D3A1.1CC2A5F1-ON652572C9.0034FFBD-652572C9.0035F075@flextronicssoftware.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73f7847c44628482de9d5f1018acf469
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0539848856=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0539848856==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0494_01C78805.7B1D72D0"

This is a multi-part message in MIME format.

------=_NextPart_000_0494_01C78805.7B1D72D0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

When receiving 433 it's the UAC responsibility to announce the user that
other party of the call is blocking the call because of the anonymity of the
caller and the user in case he wants to make the call must remove his
anonymity from the new request. This request must be done as a user request
and not automatically by the UAC.

 

 

 

  _____  

From: Preethi.Sadasivan@aricent.com [mailto:Preethi.Sadasivan@aricent.com] 
Sent: Thursday, April 26, 2007 12:47 PM
To: sipping@ietf.org
Cc: Preethi.Sadasivan@aricent.com
Subject: [Sipping] 433 error response format.

 


Hi All, 
  I have a query with reference to the following lines from the draft
"draft-ietf-sip-acr-code-04.txt" 
for 433 error response Section 4. 

4 .UAC Behavior 

   A UAC receiving a 433 (Anonymity Disallowed) MUST NOT retry the 
   request without anonymity unless it obtains confirmation from the 
   user that this is desirable.  Such confirmation could be obtained 
   through the user interface, or by accessing user defined policy.  If 
   the user has indicated that this is desirable, the UAC MAY retry the 
   request without requesting anonymity. 

How will the UAS indicate the UAC that it has a desire for the request to 
be retried. Will this be communicated in some headers like that of
Retry-Header. 
Please throw some light on this issue.


Thanks and Regards,
Preethi..
----------------------------------------------------------------------------
--
Preethi Sadasivan,
Software Engineer,
ARICENT ,
Bangalore.
tel: +91-80-41069118
----------------------------------------------------------------------------
--


***********************  Aricent-Private   *********************** 


"DISCLAIMER: This message is proprietary to Aricent and is intended solely
for the use of 
the individual to whom it is addressed. It may contain privileged or
confidential information and should not be 
circulated or used for any purpose other than for what it is intended. If
you have received this message in error, 
please notify the originator immediately. If you are not the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this
message. Aricent accepts no responsibility for 
loss or damage arising from the use of the information transmitted by this
email including damage from virus."

 


------=_NextPart_000_0494_01C78805.7B1D72D0
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:sans-serif;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>When receiving 433 it&#8217;s the =
UAC
responsibility to announce the user that other party of the call is =
blocking
the call because of the anonymity of the caller and the user in case he =
wants
to make the call must remove his anonymity from the new request. This =
request
must be done as a user request and not automatically by the =
UAC.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
Preethi.Sadasivan@aricent.com [mailto:Preethi.Sadasivan@aricent.com] =
<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, April 26, =
2007
12:47 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> sipping@ietf.org<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
Preethi.Sadasivan@aricent.com<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Sipping] 433 =
error
response format.</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
</span></font><font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;
font-family:sans-serif'>Hi All,</span></font> <br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
I have a query with reference to the following lines from the draft =
&nbsp;&quot;<b><span
style=3D'font-weight:bold'>draft-ietf-sip-acr-code-04.txt</span></b>&quot=
; </span></font><br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>for
433 error response Section 4.</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>4
.UAC Behavior</span></font> <br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
&nbsp;A UAC receiving a 433 (Anonymity Disallowed) MUST NOT retry =
the</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
&nbsp;request without anonymity unless it obtains confirmation from =
the</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
&nbsp;user that this is desirable. &nbsp;Such confirmation could be =
obtained</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
&nbsp;through the user interface, or by accessing user defined policy. =
&nbsp;If</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
&nbsp;the user has indicated that this is desirable, the UAC MAY retry =
the</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>&nbsp;
&nbsp;request without requesting anonymity. </span></font><br>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>How
will the UAS indicate the UAC that it has a desire for the request to =
</span></font><br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>be
retried. Will this be communicated in some headers like that of =
Retry-Header.</span></font>
<br>
<font size=3D2 face=3Dsans-serif><span =
style=3D'font-size:10.0pt;font-family:sans-serif'>Please
throw some light on this issue.<br>
<br>
<br>
Thanks and Regards,<br>
Preethi..<br>
-------------------------------------------------------------------------=
-----<br>
Preethi Sadasivan,<br>
Software Engineer,<br>
ARICENT ,<br>
<st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Bangalore</st1:place></st1:City>.<br>
tel: +91-80-41069118<br>
-------------------------------------------------------------------------=
-----<br>
<br>
<br>
*********************** &nbsp;Aricent-Private &nbsp; =
***********************</span></font>
<o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellpadding=3D0>
 <tr>
  <td bgcolor=3Dwhite style=3D'background:white;padding:.75pt .75pt =
.75pt .75pt'><pre><font
  size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
  color:black'>&quot;DISCLAIMER: This message is proprietary to Aricent =
and is intended solely for the use of =
<o:p></o:p></span></font></pre><pre><font
  size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
  color:black'>the individual to whom it is addressed. It may contain =
privileged or confidential information and should not be =
<o:p></o:p></span></font></pre><pre><font
  size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
  color:black'>circulated or used for any purpose other than for what it =
is intended. If you have received this message in error, =
<o:p></o:p></span></font></pre><pre><font
  size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
  color:black'>please notify the originator immediately. If you are not =
the intended recipient, you are notified that you are =
strictly<o:p></o:p></span></font></pre><pre><font
  size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
  color:black'>prohibited from using, copying, altering, or disclosing =
the contents of this message. Aricent accepts no responsibility for =
<o:p></o:p></span></font></pre><pre><font
  size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
  color:black'>loss or damage arising from the use of the information =
transmitted by this email including damage from =
virus.&quot;<o:p></o:p></span></font></pre></td>
 </tr>
</table>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0494_01C78805.7B1D72D0--




--===============0539848856==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0539848856==--






From sipping-bounces@ietf.org Thu Apr 26 06:51:00 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh1Ys-0000bK-Bk; Thu, 26 Apr 2007 06:50:54 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hh1Yr-0000bE-8v for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 06:50:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh1Yq-0000b6-VS
	for sipping@ietf.org; Thu, 26 Apr 2007 06:50:52 -0400
Received: from ihemail2.lucent.com ([135.245.0.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh1Yo-00023z-78
	for sipping@ietf.org; Thu, 26 Apr 2007 06:50:52 -0400
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id l3QAoNtm011967;
	Thu, 26 Apr 2007 05:50:44 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Apr 2007 05:50:42 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.26]) by
	DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Apr 2007 12:50:39 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping]	I-DACTION:draft-ietf-sipping-uri-list-conferencing-05.txt
Date: Thu, 26 Apr 2007 12:50:37 +0200
Message-ID: <5D1A7985295922448D5550C94DE2918001084BD4@DEEXC1U01.de.lucent.com>
In-Reply-To: <015601c787dc$1deaf200$6a6c460a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping]	I-DACTION:draft-ietf-sipping-uri-list-conferencing-05.txt
Thread-Index: AcY7+K/OZrChJZQIS0erlS2HpUZwz1L4nzmgAAAz+BAABPuRAA==
References: <144ED8561CE90C41A3E5908EDECE315C0484E8BC@IsrExch01.israel.polycom.com>
	<015601c787dc$1deaf200$6a6c460a@china.huawei.com>
From: "Drage, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Linyi Tian" <tianlinyi@huawei.com>,
	"Even, Roni" <roni.even@polycom.co.il>, <sipping@ietf.org>
X-OriginalArrivalTime: 26 Apr 2007 10:50:39.0253 (UTC)
	FILETIME=[BA668450:01C787F0]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: Mary Barnes <mary.barnes@nortelnetworks.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0219754390=="
Errors-To: sipping-bounces@ietf.org

--===============0219754390==
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

QW5kIHRvIGNvbXBsZXRlIHRoZSBzdG9yeSwgdGhlIGRyYWZ0IHRyYWNrZXIgYXQNCg0KaHR0cHM6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9wdWJsaWMvcGlkdHJhY2tlci5jZ2kNCg0KU2hvd3MgYSBz
dGF0dXMgb2YgSW4gU3RhdGU6IFB1YmxpY2F0aW9uIFJlcXVlc3RlZCA6OiBFeHRlcm5hbCBQYXJ0
eQ0KDQpUaGlzIGlzIGJlY2F1c2UgaXQgaXMgd2FpdGluZyBmb3IgdGhlIHB1YmxpY2F0aW9uIHJl
cXVlc3Qgb2YgZHJhZnQgaWV0Zi1zaXAtY29uc2VudC1mcmFtZXdvcmsgaW4gb3JkZXIgdG8gcHJv
Y2VlZCB0aHJvdWdoIElFU0cuIFRoZSBzdGF0dXMgb2YgdGhlIGxhdHRlciBkb2N1bWVudCBpcyB0
aGF0IGl0IGlzIHRlY2huaWNhbCBjb21wbGV0ZSwgYnV0IHRoZSBQUk9UTyBzaGVwaGVyZCAobWUp
IG5lZWRzIHRvIGRvIHNvbWUgd29yayB3aXRoIHRoZSBhdXRob3JzIHRvIHRpZHkgdXAgc29tZSBS
RkMgNDQ4NSBhbmQgUkZDIDIxMTkgY29uY2VybnMsIGFuZCBkcmFmdCB0aGUgUFJPVE8gd3JpdGV1
cCB3aGljaCBmb3JtcyBwYXJ0IG9mIHRoZSBwdWJsaWNhdGlvbiByZXF1ZXN0LiBUaGlzIGlzIHRo
ZSBsYXN0IGxpbmsgaW4gYSBjaGFpbiBvZiBjb21wbGV4IGRlcGVuZGVudCByZWZlcmVuY2VzLg0K
DQpLZWl0aA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IExpbnlpIFRp
YW4gW21haWx0bzp0aWFubGlueWlAaHVhd2VpLmNvbV0gDQo+IFNlbnQ6IFRodXJzZGF5LCBBcHJp
bCAyNiwgMjAwNyA5OjIzIEFNDQo+IFRvOiAnRXZlbiwgUm9uaSc7IHNpcHBpbmdAaWV0Zi5vcmcN
Cj4gQ2M6ICdNYXJ5IEJhcm5lcycNCj4gU3ViamVjdDogUkU6IFtTaXBwaW5nXSANCj4gSS1EQUNU
SU9OOmRyYWZ0LWlldGYtc2lwcGluZy11cmktbGlzdC1jb25mZXJlbmNpbmctMDUudHh0DQo+IA0K
PiBIaSBSb25pDQo+IEl0IHdhcyBtb3ZlZCB0byBTSVAgV0cuIFRoZSBuZXcgbmFtZSBpczogDQo+
IGRyYWZ0LWlldGYtc2lwLXVyaS1saXN0LWNvbmZlcmVuY2luZy0wMS50eHQNCj4gQmVzdCBSZWdh
cmRzLA0KPiBMaW55aQ0KPiANCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTog
RXZlbiwgUm9uaSBbbWFpbHRvOnJvbmkuZXZlbkBwb2x5Y29tLmNvLmlsXQ0KPiBTZW50OiBUaHVy
c2RheSwgQXByaWwgMjYsIDIwMDcgNDoxOCBQTQ0KPiBUbzogc2lwcGluZ0BpZXRmLm9yZw0KPiBD
YzogTWFyeSBCYXJuZXMNCj4gU3ViamVjdDogUkU6IFtTaXBwaW5nXSANCj4gSS1EQUNUSU9OOmRy
YWZ0LWlldGYtc2lwcGluZy11cmktbGlzdC1jb25mZXJlbmNpbmctMDUudHh0DQo+IA0KPiBIaSwN
Cj4gSSB3YXMgd29uZGVyaW5nIHdoYXQgdGhlIHN0YXR1cyBvZiB0aGlzIGRyYWZ0IGlzIHNpbmNl
IGl0IA0KPiBzaG93cyB0aGF0IGl0IGV4cGlyZWQuDQo+ICANCj4gVGhhbmtzDQo+IFJvbmkgRXZl
bg0KPiANCj4gPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+IEZyb206IEludGVybmV0
LURyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOkludGVybmV0LURyYWZ0c0BpZXRmLm9yZ10NCj4gPiBT
ZW50OiBUdWVzZGF5LCBGZWJydWFyeSAyOCwgMjAwNiAxOjUwIEFNDQo+ID4gVG86IGktZC1hbm5v
dW5jZUBpZXRmLm9yZw0KPiA+IENjOiBzaXBwaW5nQGlldGYub3JnDQo+ID4gU3ViamVjdDogW1Np
cHBpbmddIA0KPiBJLURBQ1RJT046ZHJhZnQtaWV0Zi1zaXBwaW5nLXVyaS1saXN0LWNvbmZlcmVu
Y2luZy0NCj4gPiAwNS50eHQNCj4gPiANCj4gPiBBIE5ldyBJbnRlcm5ldC1EcmFmdCBpcyBhdmFp
bGFibGUgZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMgDQo+ID4gZGlyZWN0b3JpZXMu
DQo+ID4gVGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRlbSBvZiB0aGUgU2Vzc2lvbiBJbml0aWF0aW9u
IFByb3Bvc2FsDQo+IEludmVzdGlnYXRpb24NCj4gPiBXb3JraW5nIEdyb3VwIG9mIHRoZSBJRVRG
Lg0KPiA+IA0KPiA+IAlUaXRsZQkJOiBDb25mZXJlbmNlIEVzdGFibGlzaG1lbnQgVXNpbmcNCj4g
UmVxdWVzdC1Db250YWluZWQgTGlzdHMNCj4gPiBpbiB0aGUgU2Vzc2lvbiBJbml0aWF0aW9uIFBy
b3RvY29sIChTSVApDQo+ID4gCUF1dGhvcihzKQk6IEcuIENhbWFyaWxsbywgQS4gSm9obnN0b24N
Cj4gPiAJRmlsZW5hbWUJOg0KPiBkcmFmdC1pZXRmLXNpcHBpbmctdXJpLWxpc3QtY29uZmVyZW5j
aW5nLTA1LnR4dA0KPiA+IAlQYWdlcwkJOiAxNA0KPiA+IAlEYXRlCQk6IDIwMDYtMi0yNw0KPiA+
IA0KPiA+IFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGhvdyB0byBjcmVhdGUgYSBjb25mZXJlbmNl
IHVzaW5nIA0KPiBTSVAgVVJJLWxpc3QgDQo+ID4gc2VydmljZXMuICBJbiBwYXJ0aWN1bGFyLCBp
dCBkZXNjcmliZXMgYSBtZWNoYW5pc20gdGhhdCBhbGxvd3MgYSANCj4gPiBjbGllbnQgdG8gcHJv
dmlkZSBhIGNvbmZlcmVuY2Ugc2VydmVyIHdpdGggdGhlIGluaXRpYWwgbGlzdCBvZiANCj4gPiBw
YXJ0aWNpcGFudHMgdXNpbmcgYW4gSU5WSVRFLWNvbnRhaW5lZCBVUkktbGlzdC4NCj4gPiANCj4g
PiBBIFVSTCBmb3IgdGhpcyBJbnRlcm5ldC1EcmFmdCBpczoNCj4gPiBodHRwOi8vd3d3LmlldGYu
b3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLXNpcHBpbmctdXJpLWxpc3QtDQo+ID4gY29u
ZmVyZW5jaW5nLTA1LnR4dA0KPiA+IA0KPiA+IFRvIHJlbW92ZSB5b3Vyc2VsZiBmcm9tIHRoZSBJ
LUQgQW5ub3VuY2VtZW50IGxpc3QsIHNlbmQgYSANCj4gbWVzc2FnZSB0byANCj4gPiBpLWQtYW5u
b3VuY2UtcmVxdWVzdEBpZXRmLm9yZyB3aXRoIHRoZSB3b3JkIHVuc3Vic2NyaWJlIGluIA0KPiB0
aGUgYm9keSBvZg0KPiB0aGUNCj4gPiBtZXNzYWdlLg0KPiA+IFlvdSBjYW4gYWxzbyB2aXNpdCAN
Cj4gaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vSS1ELWFubm91bmNlDQo+
ID4gdG8gY2hhbmdlIHlvdXIgc3Vic2NyaXB0aW9uIHNldHRpbmdzLg0KPiA+IA0KPiA+IA0KPiA+
IEludGVybmV0LURyYWZ0cyBhcmUgYWxzbyBhdmFpbGFibGUgYnkgYW5vbnltb3VzIEZUUC4gTG9n
aW4gd2l0aCB0aGUgDQo+ID4gdXNlcm5hbWUgImFub255bW91cyIgYW5kIGEgcGFzc3dvcmQgb2Yg
eW91ciBlLW1haWwgYWRkcmVzcy4gQWZ0ZXIgDQo+ID4gbG9nZ2luZyBpbiwgdHlwZSAiY2QgaW50
ZXJuZXQtZHJhZnRzIiBhbmQgdGhlbg0KPiA+IAkiZ2V0IGRyYWZ0LWlldGYtc2lwcGluZy11cmkt
bGlzdC1jb25mZXJlbmNpbmctMDUudHh0Ii4NCj4gPiANCj4gPiBBIGxpc3Qgb2YgSW50ZXJuZXQt
RHJhZnRzIGRpcmVjdG9yaWVzIGNhbiBiZSBmb3VuZCBpbiANCj4gPiBodHRwOi8vd3d3LmlldGYu
b3JnL3NoYWRvdy5odG1sIG9yIA0KPiA+IGZ0cDovL2Z0cC5pZXRmLm9yZy9pZXRmLzFzaGFkb3ct
c2l0ZXMudHh0DQo+ID4gDQo+ID4gDQo+ID4gSW50ZXJuZXQtRHJhZnRzIGNhbiBhbHNvIGJlIG9i
dGFpbmVkIGJ5IGUtbWFpbC4NCj4gPiANCj4gPiBTZW5kIGEgbWVzc2FnZSB0bzoNCj4gPiAJbWFp
bHNlcnZAaWV0Zi5vcmcuDQo+ID4gSW4gdGhlIGJvZHkgdHlwZToNCj4gPiAJIkZJTEUgL2ludGVy
bmV0LWRyYWZ0cy9kcmFmdC1pZXRmLXNpcHBpbmctdXJpLWxpc3QtY29uZmVyZW5jaW5nLQ0KPiA+
IDA1LnR4dCIuDQo+ID4gDQo+ID4gTk9URToJVGhlIG1haWwgc2VydmVyIGF0IGlldGYub3JnIGNh
biByZXR1cm4gdGhlIGRvY3VtZW50IGluDQo+ID4gCU1JTUUtZW5jb2RlZCBmb3JtIGJ5IHVzaW5n
IHRoZSAibXBhY2siIHV0aWxpdHkuICBUbyB1c2UgdGhpcw0KPiA+IAlmZWF0dXJlLCBpbnNlcnQg
dGhlIGNvbW1hbmQgIkVOQ09ESU5HIG1pbWUiIGJlZm9yZSB0aGUgIkZJTEUiDQo+ID4gCWNvbW1h
bmQuICBUbyBkZWNvZGUgdGhlIHJlc3BvbnNlKHMpLCB5b3Ugd2lsbCBuZWVkICJtdW5wYWNrIiBv
cg0KPiA+IAlhIE1JTUUtY29tcGxpYW50IG1haWwgcmVhZGVyLiAgRGlmZmVyZW50IE1JTUUtY29t
cGxpYW50IG1haWwNCj4gcmVhZGVycw0KPiA+IAlleGhpYml0IGRpZmZlcmVudCBiZWhhdmlvciwg
ZXNwZWNpYWxseSB3aGVuIGRlYWxpbmcgd2l0aA0KPiA+IAkibXVsdGlwYXJ0IiBNSU1FIG1lc3Nh
Z2VzIChpLmUuIGRvY3VtZW50cyB3aGljaCBoYXZlIGJlZW4gc3BsaXQNCj4gPiAJdXAgaW50byBt
dWx0aXBsZSBtZXNzYWdlcyksIHNvIGNoZWNrIHlvdXIgbG9jYWwgZG9jdW1lbnRhdGlvbiBvbg0K
PiA+IAlob3cgdG8gbWFuaXB1bGF0ZSB0aGVzZSBtZXNzYWdlcy4NCj4gPiANCj4gPiANCj4gPiBC
ZWxvdyBpcyB0aGUgZGF0YSB3aGljaCB3aWxsIGVuYWJsZSBhIE1JTUUgY29tcGxpYW50IG1haWwg
cmVhZGVyIA0KPiA+IGltcGxlbWVudGF0aW9uIHRvIGF1dG9tYXRpY2FsbHkgcmV0cmlldmUgdGhl
IEFTQ0lJIHZlcnNpb24gb2YgdGhlIA0KPiA+IEludGVybmV0LURyYWZ0Lg0KPiANCj4gDQo+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IFNpcHBpbmcg
bWFpbGluZyBsaXN0ICBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXBw
aW5nDQo+IFRoaXMgbGlzdCBpcyBmb3IgTkVXIGRldmVsb3BtZW50IG9mIHRoZSBhcHBsaWNhdGlv
biBvZiBTSVAgDQo+IFVzZSBzaXAtaW1wbGVtZW50b3JzQGNzLmNvbHVtYmlhLmVkdSBmb3IgcXVl
c3Rpb25zIG9uIGN1cnJlbnQgDQo+IHNpcCBVc2Ugc2lwQGlldGYub3JnIGZvciBuZXcgZGV2ZWxv
cG1lbnRzIG9mIGNvcmUgU0lQDQo+IA0KPiANCj4gDQo+IA0KPiBfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBTaXBwaW5nIG1haWxpbmcgbGlzdCAgaHR0
cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lwcGluZw0KPiBUaGlzIGxpc3Qg
aXMgZm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0aGUgYXBwbGljYXRpb24gb2YgU0lQIA0KPiBVc2Ug
c2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJpYS5lZHUgZm9yIHF1ZXN0aW9ucyBvbiBjdXJyZW50
IA0KPiBzaXAgVXNlIHNpcEBpZXRmLm9yZyBmb3IgbmV3IGRldmVsb3BtZW50cyBvZiBjb3JlIFNJ
UA0KPiANCg==



--===============0219754390==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0219754390==--



From sipping-bounces@ietf.org Thu Apr 26 07:01:22 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh1j0-00010e-1k; Thu, 26 Apr 2007 07:01:22 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hh1iy-00010Q-59 for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 07:01:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh1ix-00010I-Rq
	for sipping@ietf.org; Thu, 26 Apr 2007 07:01:19 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh1iv-0003ZQ-ND
	for sipping@ietf.org; Thu, 26 Apr 2007 07:01:19 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	EFE8F20B91; Thu, 26 Apr 2007 13:01:16 +0200 (CEST)
X-AuditID: c1b4fb3c-a94ecbb0000073d5-71-4630867c86b0 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B8923207DC; Thu, 26 Apr 2007 13:01:16 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Apr 2007 13:01:16 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Apr 2007 13:01:15 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 7A43E2356;
	Thu, 26 Apr 2007 14:01:15 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 3D6614DBFA;
	Thu, 26 Apr 2007 14:01:15 +0300 (EEST)
Received: from localhost.localdomain (localhost [IPv6:::1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id B61234DBEE;
	Thu, 26 Apr 2007 14:01:14 +0300 (EEST)
Subject: Re: [Sipping] Recommendation from xcap-config design team meeting
	and response to OMA LS 178
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <89E8B680-1D5E-4349-AD6F-02D9589BE7E3@softarmor.com>
References: <89E8B680-1D5E-4349-AD6F-02D9589BE7E3@softarmor.com>
Content-Type: text/plain
Date: Thu, 26 Apr 2007 14:01:27 +0300
Message-Id: <1177585288.3513.6.camel@n95.nomadiclab.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-4.fc4) 
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 26 Apr 2007 11:01:15.0796 (UTC)
	FILETIME=[35CF4540:01C787F2]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: Cullen Jennings <fluffy@cisco.com>, rohan Mahy <rohan.mahy@plantronics.com>,
	Jon Peterson <jon.peterson@neustar.biz>,
	"Robert Sparks <rjs@estacado.net>" <rjs@estacado.net>,
	krisztian.kiss@nokia.com,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mary Barnes <mary.barnes@nortel.com>, sipping LIST <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi,

in my understanding reading the notes of the xcap-config design
team meeting in Prague,
the Sipping Config document will re-include an Application Identifier.

is it correct?

best regards
Sal


On Wed, 2007-03-21 at 18:30 +0100, Dean Willis wrote:
> Several people from the IETF community met as a design team on March  
> 21, 2007 during IETF 68 in Prague to discuss OMA liaison statement  
> 178 on XCAP diff-event. This LS relates to OMA's requirement for an  
> event package for use in monitoring changes to non-configuration XML  
> documents. The document draft-urpalainen-sip-xcap-diff-event-01.txt  
> had been previously submitted with the intent of meeting these  
> requirements.
> 
> Attendees at this discussion included:
> 
> Jari Urpalainen
> Krisztian Kiss
> Robert Sparks
> Dan Petrie
> Cullen Jennings
> Rohan Mahy
> Sumanth Channabasappa	
> Jonathan Rosenburg
> Dean Willis
> 
> 
> The conclusion of the meeting was to recommend some changes in the  
> current sipping-config document and to recommend development of a  
> separate xcap-config document tailored to OMA's requirements (while  
> still meeting general IETF applicability goals).
> 
> Changes to the sipping-config document include adding the application  
> identifier and error responses previously identified in design team  
> discussion.
> 
> The new xcap-event package will need to support several requirements  
> referred to in draft-urpalainen-sip-xcap-diff-event-01.txt, including  
> subscribing to a xcap document or a sub-element of an xcap element.  
> It will also need to support deferred or aggregated notification. The  
> design team recommends starting with the text in draft-urpalainen-sip- 
> xcap-diff-event-01.txt, but has not agreed to the current  re-synch  
> mechanism therein which is expected to require some further work.  
> This package could be developed either as a WG effort (probably  
> within the SIPPING working group) or as an area-director sponsored  
> individual contribution. The design team feels that the general  
> applicability of this specification is sufficiently broad that it  
> should be pursued as a standards track effort, even though RFC 3325  
> and 3427 allows informational documents to define event packages of  
> this sort.
> 
> If this recommendation is accepted or declined we will need to  
> respond with an appropriate LS to OMA informing them of our intent.  
> They would like an answer within the next week or so.
> 
> --
> Dean Willis
> IETF to OMA liaison manager
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.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



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 26 09:31:48 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh44S-0004Jm-T2; Thu, 26 Apr 2007 09:31:40 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hh44R-0004Jh-Di for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 09:31:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh44R-0004JZ-4F
	for sipping@ietf.org; Thu, 26 Apr 2007 09:31:39 -0400
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh44P-00053P-Lh
	for sipping@ietf.org; Thu, 26 Apr 2007 09:31:39 -0400
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l3QDVYQ14777; Thu, 26 Apr 2007 13:31:34 GMT
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
Subject: RE: [Sipping]	I-DACTION:draft-ietf-sipping-uri-list-conferencing-05.txt
Date: Thu, 26 Apr 2007 08:31:17 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB16E797E1@zrc2hxm1.corp.nortel.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C0484E8BC@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping]	I-DACTION:draft-ietf-sipping-uri-list-conferencing-05.txt
Thread-Index: AcY7+K/OZrChJZQIS0erlS2HpUZwz1L4nzmgAAqiiHA=
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Even, Roni" <roni.even@polycom.co.il>, <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: Mary Barnes <mary.barnes@nortel.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

We ended up moving that doc and a few of the others over to SIP since
they had normative protocol impacts:
http://www.ietf.org/internet-drafts/draft-ietf-sip-uri-list-conferencing
-01.txt
http://www.ietf.org/internet-drafts/draft-ietf-sip-uri-list-message-01.t
xt
http://www.ietf.org/internet-drafts/draft-ietf-sip-uri-list-subscribe-01
.txt
http://www.ietf.org/internet-drafts/draft-ietf-sip-multiple-refer-01.txt

Those docs are all in a "Publication Requested" state.=20

I guess this points out that this is likely some historical information
that we should maintain in the WG spreadsheet.=20

Mary


-----Original Message-----
From: Even, Roni [mailto:roni.even@polycom.co.il]=20
Sent: Thursday, April 26, 2007 3:18 AM
To: sipping@ietf.org
Cc: Mary Barnes
Subject: RE: [Sipping]
I-DACTION:draft-ietf-sipping-uri-list-conferencing-05.txt


Hi,
I was wondering what the status of this draft is since it shows that it
expired.
=20
Thanks
Roni Even

> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Tuesday, February 28, 2006 1:50 AM
> To: i-d-announce@ietf.org
> Cc: sipping@ietf.org
> Subject: [Sipping] I-DACTION:draft-ietf-sipping-uri-list-conferencing-
> 05.txt
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Session Initiation Proposal
Investigation
> Working Group of the IETF.
>=20
> 	Title		: Conference Establishment Using
Request-Contained Lists
> in the Session Initiation Protocol (SIP)
> 	Author(s)	: G. Camarillo, A. Johnston
> 	Filename	:
draft-ietf-sipping-uri-list-conferencing-05.txt
> 	Pages		: 14
> 	Date		: 2006-2-27
>=20
> This document describes how to create a conference using SIP URI-list
> services.  In particular, it describes a mechanism that allows a
> client to provide a conference server with the initial list of
> participants using an INVITE-contained URI-list.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-uri-list-
> conferencing-05.txt
>=20
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
the
> message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>=20
>=20
> Internet-Drafts are also available by anonymous FTP. Login with the
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-sipping-uri-list-conferencing-05.txt".
>=20
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-sipping-uri-list-conferencing-
> 05.txt".
>=20
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>=20
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.


_______________________________________________
Sipping mailing list  https://www1.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


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 26 09:39:47 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh4CJ-0002XB-AS; Thu, 26 Apr 2007 09:39:47 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hh4CH-0002Wv-Po for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 09:39:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh4CH-0002Wn-GL; Thu, 26 Apr 2007 09:39:45 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hh4CH-0006bP-A9; Thu, 26 Apr 2007 09:39:45 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 1ED8826E5B;
	Thu, 26 Apr 2007 13:39:45 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Hh4CH-0005jM-0q; Thu, 26 Apr 2007 09:39:45 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1Hh4CH-0005jM-0q@stiedprstage1.ietf.org>
Date: Thu, 26 Apr 2007 09:39:45 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: sipping@ietf.org
Subject: [Sipping] Last Call: draft-ietf-sipping-dialogusage (Multiple
 Dialog 
 Usages in the Session Initiation Protocol) to Informational RFC 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

The IESG has received a request from the Session Initiation Proposal 
Investigation WG (sipping) to consider the following document:

- 'Multiple Dialog Usages in the Session Initiation Protocol '
   <draft-ietf-sipping-dialogusage-06.txt> as an Informational RFC

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 2007-05-10. 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://www.ietf.org/internet-drafts/draft-ietf-sipping-dialogusage-06.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14041&rfc_flag=0



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 26 10:06:53 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh4cV-0002xK-Dc; Thu, 26 Apr 2007 10:06:51 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hh4cU-0002xF-8T for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 10:06:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh4cT-0002x7-VB
	for sipping@ietf.org; Thu, 26 Apr 2007 10:06:49 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh4cT-0002jf-7K
	for sipping@ietf.org; Thu, 26 Apr 2007 10:06:49 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9265F20B59
	for <sipping@ietf.org>; Thu, 26 Apr 2007 16:06:48 +0200 (CEST)
X-AuditID: c1b4fb3c-a8cebbb0000073d5-ab-4630b1f8cf78 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	7196C20652
	for <sipping@ietf.org>; Thu, 26 Apr 2007 16:06:48 +0200 (CEST)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Apr 2007 16:06:48 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 26 Apr 2007 16:06:48 +0200
Message-ID: <C0E80510684FE94DBDE3A4AF6B968D2D01125F5E@esealmw118.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Clarification required on
	draft-ietf-sipping-sip-offeranswer-00.txt
Thread-Index: AceIDCGeu/d4VTrARsCjupx4X4B4+A==
From: "Ian Elz \(CV/ETL\)" <ian.elz@ericsson.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 26 Apr 2007 14:06:48.0304 (UTC)
	FILETIME=[214D2F00:01C7880C]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Subject: [Sipping] Clarification required on
	draft-ietf-sipping-sip-offeranswer-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0921690323=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0921690323==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7880C.21288D2F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7880C.21288D2F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The draft draft-ietf-sipping-sip-offeranswer-00.txt shows table (Table
1) shows a concise summary of the legal offer/answer combinations
allowed in SIP.

I have a little concern about some of the wording used in the
description of the table:

In the description of the 'ini' column the following sentence is
included:

	Only the initial INVITE request can be used to exchange the
offer/answer to establish multimedia session.

This could be taken to mean that only an INVITE Request can be used for
the sdp offer when a multimedia session, as opposed to a uni-media
session is to be established.

Conversely this could be taken that if an INVITE with no sdp offer is
received the UA may only respond with a single media offer so that there
is no multi-media session.

I am sure that this is not the intent but the wording could perhaps be
made more clear.

In the description of the 'early' column the following sentence is used:

	'Early' column shows the ability to be used to modify the
established session in an early dialog.

This is confusing as the early dialog is usually used to modify a
session which has not yet been established. Once a session has been
established 'early' is no longer applicable.

Ian Elz

Office: + 44 24 764 35256
gsm: +44 7801723668
ian.elz@ericsson.com



------_=_NextPart_001_01C7880C.21288D2F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>Clarification required on =
draft-ietf-sipping-sip-offeranswer-00.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Courier New">The draft =
draft-ietf-sipping-sip-offeranswer-00.txt shows table (Table 1) shows a =
concise summary of the legal offer/answer combinations allowed in =
SIP.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">I have a little concern about =
some of the wording used in the description of the table:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">In the description of the 'ini' =
column the following sentence is included:</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Courier New">Only the initial INVITE request can be used to =
exchange the offer/answer to establish multimedia session.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">This could be taken to mean that =
only an INVITE Request can be used for the sdp offer when a multimedia =
session, as opposed to a uni-media session is to be =
established.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Conversely this could be taken =
that if an INVITE with no sdp offer is received the UA may only respond =
with a single media offer so that there is no multi-media =
session.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">I am sure that this is not the =
intent but the wording could perhaps be made more clear.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">In the description of the 'early' =
column the following sentence is used:</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Courier New">'Early' column shows the ability to be used to =
modify the established session in an early dialog.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">This is confusing as the early =
dialog is usually used to modify a session which has not yet been =
established. Once a session has been established 'early' is no longer =
applicable.</FONT></P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">Ian Elz</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">Office: + 44 24 764 35256</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">gsm: +44 7801723668</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">ian.elz@ericsson.com</FONT></I>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C7880C.21288D2F--



--===============0921690323==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0921690323==--





From sipping-bounces@ietf.org Thu Apr 26 10:08:03 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh4df-00057S-H1; Thu, 26 Apr 2007 10:08:03 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hh4dd-0004rQ-K4 for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 10:08:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh4dd-0004mO-4k
	for sipping@ietf.org; Thu, 26 Apr 2007 10:08:01 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh4db-0002vX-Ln
	for sipping@ietf.org; Thu, 26 Apr 2007 10:08:01 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	152D820570
	for <sipping@ietf.org>; Thu, 26 Apr 2007 16:07:59 +0200 (CEST)
X-AuditID: c1b4fb3e-b01efbb0000061ca-24-4630b23fd548 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	F27A32007C
	for <sipping@ietf.org>; Thu, 26 Apr 2007 16:07:58 +0200 (CEST)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Apr 2007 16:07:58 +0200
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: Thu, 26 Apr 2007 16:07:59 +0200
Message-ID: <C0E80510684FE94DBDE3A4AF6B968D2D01125F64@esealmw118.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comment on draft-ietf-sipping-cc-transfer-07
Thread-Index: AceIDEt2zn/0douORyabEvvomrqGKg==
From: "Ian Elz \(CV/ETL\)" <ian.elz@ericsson.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 26 Apr 2007 14:07:58.0878 (UTC)
	FILETIME=[4B5DEBE0:01C7880C]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Subject: [Sipping] Comment on draft-ietf-sipping-cc-transfer-07
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

In section 7 of the draft (draft-ietf-sipping-cc-transfer-07) you
discuss transfer with a consultative call. In this discussion you refer
to the use of the Replaces header as defined in RFC3891.

You do not mention however that for the purpose of this draft the
original dialog between the transferor and the  transfer target must not
have an B2BUA in the message path as the use of the Replaces header in
the later INVITE between the transfer target and transferee as any B2BUA
may have resulted one or more components of the Replaces header
(call-id, from-tag, to-tag) may have been modified as shown below.

+------------+               +---------+               +-----------+
|            |               |         |               |           |
| transferor |-------------->| B2BUA   |-------------->| transfer  |
|            |               |         |               | target    |
+------------+               +---------+               +-----------+
Call-id =3D 1234                call-id                  Call-id =3D =
4321
From-tag =3D ab12               mapped                   From-tag =3D =
ab12
To-tag =3D cd34                                          To-tag =3D cd34

Thus the Replaces header sent from the transferor to the transferee in
the REFER request Refer-to header would be Replaces
(call-id=3D1234,from-tag=3Dab12,to-tag=3Dcd34). This would not be valid =
if
received in an INVITE at the transfer target and the INVITE would be
rejected as the Replaces header does not match an existing dialog.

Thus when mentioning the INVITE with the Replaces header you need to
explicitly state that the UAC generating the INVITE must know that there
was no b2bua in the original call or that no impacted header was mapped.

OR

Reference should be made to the appropriate routing algorithm which
indicates how routing should be performed when a parameter from another
dialog is used as part of the initiation of a new dialog.

Unfortunately SIP does not provide any information as to whether any
header has been mapped in a dialog or what node may have mapped any
header(s). As a result the first option is not practical as it would
require every user agent to know the topology of the entire network and
the message path of a dialog to understand whether the Replaces header
was valid.

As the other drafts currently being considered by the sipping WG:
draft-ietf-sipping-sbc-funcs-03 & draft-marjou-sipping-b2bua-00; both
reference b2bua capability and why it is used within the network
consideration must be given to the correct routing of Requests which use
a value obtained from one dialog as part of a subsequent dialog.

Ian Elz

Office: + 44 24 764 35256
gsm: +44 7801723668
ian.elz@ericsson.com




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 26 11:47:28 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh6Bk-0003C5-Sh; Thu, 26 Apr 2007 11:47:20 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hh6Bj-0003C0-4T for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 11:47:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh6Bi-0003Bs-If
	for sipping@ietf.org; Thu, 26 Apr 2007 11:47:18 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh6Bh-0003Ln-2c
	for sipping@ietf.org; Thu, 26 Apr 2007 11:47:18 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-5.cisco.com with ESMTP; 26 Apr 2007 08:47:17 -0700
X-IronPort-AV: i="4.14,455,1170662400"; 
	d="scan'208"; a="415935898:sNHT174986124"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id l3QFlGsI014990; 
	Thu, 26 Apr 2007 08:47:16 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l3QFlGwp018723;
	Thu, 26 Apr 2007 15:47:16 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Apr 2007 08:47:16 -0700
Received: from [10.21.155.160] ([10.21.155.160]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Apr 2007 08:47:15 -0700
Message-ID: <4630C983.20807@cisco.com>
Date: Thu, 26 Apr 2007 11:47:15 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Ian Elz (CV/ETL)" <ian.elz@ericsson.com>
Subject: Re: [Sipping] Comment on draft-ietf-sipping-cc-transfer-07
References: <C0E80510684FE94DBDE3A4AF6B968D2D01125F64@esealmw118.eemea.ericsson.se>
In-Reply-To: <C0E80510684FE94DBDE3A4AF6B968D2D01125F64@esealmw118.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Apr 2007 15:47:15.0555 (UTC)
	FILETIME=[29D2B330:01C7881A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3661; t=1177602436;
	x=1178466436; c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Comment=20on=20draft-ietf-sipping-cc-tran
	sfer-07 |Sender:=20;
	bh=zU2RlAhA5VV6nH/BKEPxy8ya93OtTXhX5ZKs+fxgot0=;
	b=a7oOuSJjsqrq7h5SWqi4vEW9SzsrB8DWjIXoU74kV2f+DbQud1p3DL77Z+Gq19fwmaegaukT
	suDZLT7ybs2BdzKTMC3IMsaQVMxigJsiThPDxI45osKAyaThYIWuNdug;
Authentication-Results: sj-dkim-5; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim5002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

inline

Ian Elz (CV/ETL) wrote:
> In section 7 of the draft (draft-ietf-sipping-cc-transfer-07) you
> discuss transfer with a consultative call. In this discussion you refer
> to the use of the Replaces header as defined in RFC3891.
> 
> You do not mention however that for the purpose of this draft the
> original dialog between the transferor and the  transfer target must not
> have an B2BUA in the message path as the use of the Replaces header in
> the later INVITE between the transfer target and transferee as any B2BUA
> may have resulted one or more components of the Replaces header
> (call-id, from-tag, to-tag) may have been modified as shown below.
> 
> +------------+               +---------+               +-----------+
> |            |               |         |               |           |
> | transferor |-------------->| B2BUA   |-------------->| transfer  |
> |            |               |         |               | target    |
> +------------+               +---------+               +-----------+
> Call-id = 1234                call-id                  Call-id = 4321
> From-tag = ab12               mapped                   From-tag = ab12
> To-tag = cd34                                          To-tag = cd34
> 
> Thus the Replaces header sent from the transferor to the transferee in
> the REFER request Refer-to header would be Replaces
> (call-id=1234,from-tag=ab12,to-tag=cd34). This would not be valid if
> received in an INVITE at the transfer target and the INVITE would be
> rejected as the Replaces header does not match an existing dialog.

In this case, the REFER would in fact be sent to the B2BUA, since that 
is remote contact of the dialog that the transferor has. The B2BUA will 
have to relay the REFER on to the transfer target. Since the B2BUA has 
decided to interfere in the call, it has the obligation to fix up the 
problems it has caused. In this case it has the responsibility to fix up 
the Replaces header.

> Thus when mentioning the INVITE with the Replaces header you need to
> explicitly state that the UAC generating the INVITE must know that there
> was no b2bua in the original call or that no impacted header was mapped.
> 
> OR
> 
> Reference should be made to the appropriate routing algorithm which
> indicates how routing should be performed when a parameter from another
> dialog is used as part of the initiation of a new dialog.

So far we have never specified how B2BUAs should work.

> Unfortunately SIP does not provide any information as to whether any
> header has been mapped in a dialog or what node may have mapped any
> header(s). As a result the first option is not practical as it would
> require every user agent to know the topology of the entire network and
> the message path of a dialog to understand whether the Replaces header
> was valid.
> 
> As the other drafts currently being considered by the sipping WG:
> draft-ietf-sipping-sbc-funcs-03 & draft-marjou-sipping-b2bua-00; both
> reference b2bua capability and why it is used within the network
> consideration must be given to the correct routing of Requests which use
> a value obtained from one dialog as part of a subsequent dialog.
> 
> Ian Elz
> 
> Office: + 44 24 764 35256
> gsm: +44 7801723668
> ian.elz@ericsson.com
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.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
> 


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 26 16:34:37 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhAfk-0004gv-0M; Thu, 26 Apr 2007 16:34:36 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HhAfi-0004gW-7G for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 16:34:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhAfh-0004gK-Tv
	for sipping@ietf.org; Thu, 26 Apr 2007 16:34:33 -0400
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhAff-0007IQ-Sx
	for sipping@ietf.org; Thu, 26 Apr 2007 16:34:33 -0400
Received: from kyzyl.cablelabs.com (kyzyl.cablelabs.com [10.253.0.7])
	by ondar.cablelabs.com (8.13.8/8.13.8) with ESMTP id l3QKYTaK022408;
	Thu, 26 Apr 2007 14:34:29 -0600 (MDT)
Received: from srvxchg3.cablelabs.com (10.5.0.25)
	by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com);
	Thu, 26 Apr 2007 14:34:29 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com)
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
Subject: RE: [Sipping] Recommendation from xcap-config design team meetingand
	response to OMA LS 178
Date: Thu, 26 Apr 2007 14:34:43 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C607A3E8@srvxchg3.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Recommendation from xcap-config design team meetingand
	response to OMA LS 178
Thread-Index: AceH8lZlPhAaj88fRfyFvG53l6sagwATuDaQAAA5BnA=
References: <89E8B680-1D5E-4349-AD6F-02D9589BE7E3@softarmor.com>
	<1177585288.3513.6.camel@n95.nomadiclab.com> 
From: "Sumanth Channabasappa" <sumanth@cablelabs.com>
To: "Salvatore Loreto" <salvatore.loreto@ericsson.com>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: sipping LIST <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Sal,

AFAIK :^), we decided to reintroduce the 'application' profile type for
use with the SIP Configuration framework. However, we did not discuss
(or decide) if this will be part of the existing SIP configuration
framework I-D or a separate I-D. (The design team working on the I-D is
leaning towards making this a separate I-D at this point in time.)=20

- S

-----Original Message-----
From: Salvatore Loreto [mailto:salvatore.loreto@ericsson.com]
Sent: Thursday, April 26, 2007 5:01 AM
To: Dean Willis
Cc: Cullen Jennings; rohan Mahy; Jon Peterson; Robert Sparks
<rjs@estacado.net>; krisztian.kiss@nokia.com; Gonzalo Camarillo; mary
Barnes; sipping LIST
Subject: Re: [Sipping] Recommendation from xcap-config design team
meetingand response to OMA LS 178

Hi,

in my understanding reading the notes of the xcap-config design team
meeting in Prague, the Sipping Config document will re-include an
Application Identifier.

is it correct?

best regards
Sal


On Wed, 2007-03-21 at 18:30 +0100, Dean Willis wrote:
> Several people from the IETF community met as a design team on March=20
> 21, 2007 during IETF 68 in Prague to discuss OMA liaison statement
> 178 on XCAP diff-event. This LS relates to OMA's requirement for an=20
> event package for use in monitoring changes to non-configuration XML=20
> documents. The document draft-urpalainen-sip-xcap-diff-event-01.txt
> had been previously submitted with the intent of meeting these=20
> requirements.
>=20
> Attendees at this discussion included:
>=20
> Jari Urpalainen
> Krisztian Kiss
> Robert Sparks
> Dan Petrie
> Cullen Jennings
> Rohan Mahy
> Sumanth Channabasappa=09
> Jonathan Rosenburg
> Dean Willis
>=20
>=20
> The conclusion of the meeting was to recommend some changes in the=20
> current sipping-config document and to recommend development of a=20
> separate xcap-config document tailored to OMA's requirements (while=20
> still meeting general IETF applicability goals).
>=20
> Changes to the sipping-config document include adding the application=20
> identifier and error responses previously identified in design team=20
> discussion.
>=20
> The new xcap-event package will need to support several requirements=20
> referred to in draft-urpalainen-sip-xcap-diff-event-01.txt, including=20
> subscribing to a xcap document or a sub-element of an xcap element.
> It will also need to support deferred or aggregated notification. The=20
> design team recommends starting with the text in draft-urpalainen-sip-

> xcap-diff-event-01.txt, but has not agreed to the current  re-synch=20
> mechanism therein which is expected to require some further work.
> This package could be developed either as a WG effort (probably within

> the SIPPING working group) or as an area-director sponsored individual

> contribution. The design team feels that the general applicability of=20
> this specification is sufficiently broad that it should be pursued as=20
> a standards track effort, even though RFC 3325 and 3427 allows=20
> informational documents to define event packages of this sort.
>=20
> If this recommendation is accepted or declined we will need to respond

> with an appropriate LS to OMA informing them of our intent.
> They would like an answer within the next week or so.
>=20
> --
> Dean Willis
> IETF to OMA liaison manager
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use=20
> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> sip@ietf.org for new developments of core SIP



_______________________________________________
Sipping mailing list  https://www1.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



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Thu Apr 26 21:05:34 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhEtw-0007k2-W4; Thu, 26 Apr 2007 21:05:32 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HhEtv-0007jx-8l for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 21:05:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhEtu-0007jp-U6
	for sipping@ietf.org; Thu, 26 Apr 2007 21:05:30 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhEtu-0007D7-6h
	for sipping@ietf.org; Thu, 26 Apr 2007 21:05:30 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Apr 2007 03:05:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
Date: Fri, 27 Apr 2007 03:04:51 +0200
Message-ID: <2AF8FF7D89242541B12E7A47F6ECB4BE05614159@ftrdmel3.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
Thread-Index: AceHPjXEfLaXARMPQQWYghB4ozul3wA6QMgQ
From: "CHADLI Youssef RD-CORE-ISS" <youssef.chadli@orange-ftgroup.com>
To: "Spencer Dawkins" <spencer@mcsr-labs.org>, "David R Oran" <oran@cisco.com>
X-OriginalArrivalTime: 27 Apr 2007 01:05:17.0747 (UTC)
	FILETIME=[1EC3C030:01C78868]
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 9f79b8e383fd3af2b1b5b1d0910f6094
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1675260528=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1675260528==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78868.1E23039D"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C78868.1E23039D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,=20
=20
Inline

Youssef

-----Message d'origine-----
De : Spencer Dawkins [mailto:spencer@mcsr-labs.org]=20
Envoy=E9 : mercredi 25 avril 2007 15:30
=C0 : sipping
Objet : Re: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00

Just checking -

From: "David R Oran" <oran@cisco.com>

>> On Apr 25, 2007, at 5:18 AM, CHADLI Youssef RD-CORE-ISS wrote:
>>
>>> REQ 17: The overload mechanism must not provide an avenue for
>>>       malicious attack.
>>>
>>> To prevent malicious attacks, it's necessary to prevent untrusted=20
>>> elements to access load information of the SIP servers.
>> I must be dense, so bear with me. Could you explain what new =20
>> malicious attack is opened or existing attack amplified by treating =20
>> the load information as confidential?

> I am just as dense as David - please explain...

One of the elementary security rules is to provide the minimum =
information of a given server (e.g. server name, software version =
...etc): the more information you give, the more the risk of malicious =
attacks increases. In fact, having information about the server can be =
used by malicious elements to detect the server weaknesses. For =
instance, a server that is 100 % overloaded may be more vulnerable which =
facilitates malicious attacks.=20

Another argument in favour of controlling the access to the load =
information is that for confidentiality reasons, a service provider may =
do no want that an untrusted service provider  knows the load level of =
its servers.=20



>>> REQ 22: The mechanism should be easily centralised in the front-end=20
>>> servers in case the SIP server is implemented as a cluster of =
servers=20
>>> running on different machines.
>>>
>> I'm not sure how you ascertain if this requirement is met. I can see  =

>> how you could write a requirement that the scheme allow such =20
>> configurations, just not that it be "easy". Easy compared to what?

> I like the requirement (although I agree with David that "easily" is a =
weasel word), but I'm concerned that we may not have a basis for judging =
"can be centralized in the  > front-end servers".

What I mean by "can be easily centralised on the front-ends servers" is =
: implementing overload mechanism shall not heavily impact the =
performance of front-ends servers:=20
1) the mechanism shall not require front-ends parsing all received =
messages to look for overload control information
2) the mechanism shall not require front-end servers to open messages =
sent by applications to insert overload control information=20
3) the mechanism shall support aggregating load information from =
different elements of a server farm
  =20

> If things have changed in the past few years, I apologize for my =
confusion, but my understanding was that most of the =
front-end-to-cluster schemes were proprietary, so > we might be able to =
say "works on THIS front-end-to-cluster scheme", but wouldn't know if it =
works on ANY front-end-to-cluster scheme.

I agree that front-end-to-cluster schemes can be considered as =
proprietary. We can assume that the front-end server knows the load =
status of the whole cluster.

> Can someone smarter than I am express an opinion about this?

Thanks,

Spencer=20




_______________________________________________
Sipping mailing list  https://www1.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

------_=_NextPart_001_01C78868.1E23039D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">
<TITLE>RE: [SIPPING] Comments on =
draft-ietf-sipping-overload-reqs-00</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Hi, </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT COLOR=3D"#800080" SIZE=3D2 =
FACE=3D"Arial">Inline</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Youssef</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">-----Message =
d'origine-----</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">De : Spencer Dawkins =
[</FONT></SPAN><A HREF=3D"mailto:spencer@mcsr-labs.org"><SPAN =
LANG=3D"fr"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">mailto:spencer@mcsr-labs.org</FONT></U></SPAN></A><SPAN =
LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">] </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Envoy=E9 : mercredi =
25 avril 2007 15:30</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">=C0 : =
sipping</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Objet : Re: =
[SIPPING] Comments on draft-ietf-sipping-overload-reqs-00</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Just checking =
-</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">From: &quot;David R =
Oran&quot; &lt;oran@cisco.com&gt;</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; On Apr 25, =
2007, at 5:18 AM, CHADLI Youssef RD-CORE-ISS wrote:</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; REQ 17: =
The overload mechanism must not provide an avenue for</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
malicious attack.</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; To =
prevent malicious attacks, it's necessary to prevent untrusted =
</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; =
elements to access load information of the SIP servers.</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; I must be =
dense, so bear with me. Could you explain what new&nbsp; </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; malicious =
attack is opened or existing attack amplified by treating&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; the load =
information as confidential?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; I am just as =
dense as David - please explain&#8230;</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-gb"><FONT COLOR=3D"#800000" SIZE=3D2 =
FACE=3D"Arial">One of the elementary security rules is to provide the =
minimum information of a given server (e.g. server name, software =
version &#8230;etc): the more information you give, the more the risk of =
malicious attacks increases. In fact, having information about the =
server can be used by malicious elements to detect the server =
weaknesses. For instance, a server that is 100 % overloaded may be more =
vulnerable which facilitates malicious attacks. </FONT></SPAN></P>

<P><SPAN LANG=3D"en-gb"><FONT COLOR=3D"#800000" SIZE=3D2 =
FACE=3D"Arial">Another argument in favour of controlling the access to =
the load information is that for confidentiality reasons, a service =
provider may do no want that an untrusted service provider&nbsp; knows =
the load level of its servers. </FONT></SPAN></P>
<BR>
<BR>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; REQ 22: =
The mechanism should be easily centralised in the front-end =
</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; servers =
in case the SIP server is implemented as a cluster of servers =
</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; running =
on different machines.</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; I'm not =
sure how you ascertain if this requirement is met. I can see&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; how you =
could write a requirement that the scheme allow such&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; =
configurations, just not that it be &quot;easy&quot;. Easy compared to =
what?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; I like the =
requirement (although I agree with David that &quot;easily&quot; is a =
weasel word), but I'm concerned that we may not have a basis for judging =
&quot;can be centralized in the&nbsp; &gt; front-end =
servers&quot;.</FONT></SPAN></P>

<P><SPAN LANG=3D"fr"><FONT COLOR=3D"#800000" SIZE=3D2 =
FACE=3D"Arial">What I mean by &quot;</FONT><FONT COLOR=3D"#800000" =
SIZE=3D2 FACE=3D"Courier New">can be easily centralised on the =
front-ends servers</FONT><FONT COLOR=3D"#800000" SIZE=3D2 =
FACE=3D"Arial">&quot; is : implementing overload mechanism shall not =
heavily impact the performance of front-ends servers: </FONT></SPAN></P>

<P><SPAN LANG=3D"en-gb"><FONT COLOR=3D"#800000" SIZE=3D2 =
FACE=3D"Arial">1) the mechanism shall not require front-ends parsing all =
received messages to look for overload control information</FONT></SPAN>

<BR><SPAN LANG=3D"en-gb"><FONT COLOR=3D"#800000" SIZE=3D2 =
FACE=3D"Arial">2) the mechanism shall not require front-end servers to =
open messages sent by applications to insert overload control =
information </FONT></SPAN></P>

<P><SPAN LANG=3D"en-gb"><FONT COLOR=3D"#800000" SIZE=3D2 =
FACE=3D"Arial">3) the mechanism shall support aggregating load =
information from different elements of a server farm</FONT></SPAN><SPAN =
LANG=3D"fr"></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; =
</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; If things have =
changed in the past few years, I apologize for my confusion, but my =
understanding was that most of the front-end-to-cluster schemes were =
proprietary, so &gt; we might be able to say &quot;works on THIS =
front-end-to-cluster scheme&quot;, but wouldn't know if it works on ANY =
front-end-to-cluster scheme.</FONT></SPAN></P>

<P><SPAN LANG=3D"fr"><FONT COLOR=3D"#800000" SIZE=3D2 FACE=3D"Arial">I =
agree that front-end-to-cluster schemes can be considered as =
proprietary. We can assume that the front-end server knows the load =
status of the whole cluster.</FONT></SPAN></P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; Can someone =
smarter than I am express an opinion about this?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Thanks,</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Spencer =
</FONT></SPAN>
</P>
<BR>
<BR>
<BR>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">_______________________________________________</FONT></SP=
AN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Sipping mailing =
list&nbsp; </FONT></SPAN><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping"><SPAN =
LANG=3D"fr"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">https://www1.ietf.org/mailman/listinfo/sipping</FONT></U><=
/SPAN></A><SPAN LANG=3D"fr"></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">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</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C78868.1E23039D--



--===============1675260528==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1675260528==--





From sipping-bounces@ietf.org Thu Apr 26 21:32:18 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhFJn-0008KC-8S; Thu, 26 Apr 2007 21:32:15 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HhFJm-0008K5-IO for sipping-confirm+ok@megatron.ietf.org;
	Thu, 26 Apr 2007 21:32:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhFJm-0008Jx-8o
	for sipping@ietf.org; Thu, 26 Apr 2007 21:32:14 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhFJk-0003Kd-Ir
	for sipping@ietf.org; Thu, 26 Apr 2007 21:32:14 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Apr 2007 03:32:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
Date: Fri, 27 Apr 2007 03:32:02 +0200
Message-ID: <2AF8FF7D89242541B12E7A47F6ECB4BE0561415A@ftrdmel3.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
Thread-Index: AceHSDNonQ5zzO02SRi1Xbm3sY5nEABIDy/g
From: "CHADLI Youssef RD-CORE-ISS" <youssef.chadli@orange-ftgroup.com>
To: <Dale.Worley@comcast.net>,
	<sipping@ietf.org>
X-OriginalArrivalTime: 27 Apr 2007 01:32:09.0335 (UTC)
	FILETIME=[DF589070:01C7886B]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: b360bd6cb019c35178e5cf9eeb747a5c
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2062505127=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2062505127==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7886B.DEBB16D3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7886B.DEBB16D3
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Inline,=20

Youssef=20
=20

-----Message d'origine-----
De : Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]=20
Envoy=E9 : mercredi 25 avril 2007 16:44
=C0 : sipping@ietf.org
Objet : Re: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00

   From: "CHADLI Youssef RD-CORE-ISS" =
<youssef.chadli@orange-ftgroup.com>

   To prevent malicious attacks, it's necessary to prevent untrusted
   elements to access load information of the SIP servers.

As other have said, this point needs further elaboration.

   2) Big SIP server are in general implemented as a cluster of servers
   with one or more front-end servers. The frond-end server interfaces =
to
   the other SIP nodes and performs load balancing on the different =
servers
   of the cluster. In such a case, the load control mechanism can be
   implemented and managed only by front-ends servers as only those =
servers
   can know the overall load of the cluster. It's then important that =
the
   overload mechanism can be easily centralised on the front-ends =
servers
   in this case. Consequently, I propose to add a requirement on this;
   something like:

The fact that the load balancing actions are performed by the front-end =
servers does not imply that that the overload mechanism implementation =
is "centralised" on those front-end servers.  (And given that there may =
be more than one front-end server, in what sense can anything be =
"centralised" on them?)

YC: It is necessary to centralize the overload mechanism implementation =
on font-end servers because only those servers konw the load level of =
the whole cluster. In case there are more than one front-end sever we =
can consider that each one of them knows the load level of the whole =
cluster. The way the frond-end servers exhange information of the "work" =
each one has distribute to the cluster elements is proprietary and "out =
of the scope".  =20


A much better requirement would be to provide the diagram of the =
architecture you are concerned with:

        +----------+    +----------+      +----------+ =20
        | Server#1 |  | Server#2 |....| Server#n |=20
        +----------+    +----------+      +----------+
                  |         |              |=20
                  |         |              |
                  |         |              |=20
                  |     +----------+       |=20
                  +-----| Front-End|-------+
                        | Server   |     =20
                        +----------+=20

and state a requirement that the solution work effectively in such an =
architecture.

(Although I would prefer to see the requirment generalized to several =
front-end servers feeding one cluster of servers -- the front-end =
servers must cooperate in balancing the load they deliver to the
servers.)

YC: The way the front-end servers cooperate in balancing the load they =
deliver to the servers is proprietary and should remain "out of the =
scope"

Dale


_______________________________________________
Sipping mailing list  https://www1.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

------_=_NextPart_001_01C7886B.DEBB16D3
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">
<TITLE>RE: [SIPPING] Comments on =
draft-ietf-sipping-overload-reqs-00</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

<P><SPAN LANG=3D"fr"><FONT COLOR=3D"#800000" SIZE=3D2 =
FACE=3D"Arial">Inline, </FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT COLOR=3D"#800000" SIZE=3D2 =
FACE=3D"Arial">Youssef</FONT><FONT SIZE=3D2 FACE=3D"Arial"> =
</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">-----Message =
d'origine-----</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">De : =
Dale.Worley@comcast.net [</FONT></SPAN><A =
HREF=3D"mailto:Dale.Worley@comcast.net"><SPAN LANG=3D"fr"><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">mailto:Dale.Worley@comcast.net</FONT></U></SPAN></A><SPAN =
LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">] </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Envoy=E9 : mercredi =
25 avril 2007 16:44</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">=C0 : =
sipping@ietf.org</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Objet : Re: =
[SIPPING] Comments on draft-ietf-sipping-overload-reqs-00</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; From: =
&quot;CHADLI Youssef RD-CORE-ISS&quot; =
&lt;youssef.chadli@orange-ftgroup.com&gt;</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; To =
prevent malicious attacks, it's necessary to prevent =
untrusted</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; =
elements to access load information of the SIP servers.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">As other have said, =
this point needs further elaboration.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; 2) Big =
SIP server are in general implemented as a cluster of =
servers</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; with =
one or more front-end servers. The frond-end server interfaces =
to</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; the =
other SIP nodes and performs load balancing on the different =
servers</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; of the =
cluster. In such a case, the load control mechanism can be</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; =
implemented and managed only by front-ends servers as only those =
servers</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; can =
know the overall load of the cluster. It's then important that =
the</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; =
overload mechanism can be easily centralised on the front-ends =
servers</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; in this =
case. Consequently, I propose to add a requirement on =
this;</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; =
something like:</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">The fact that the =
load balancing actions are performed by the front-end servers does not =
imply that that the overload mechanism implementation is =
&quot;centralised&quot; on those front-end servers.&nbsp; (And given =
that there may be more than one front-end server, in what sense can =
anything be &quot;centralised&quot; on them?)</FONT></SPAN></P>

<P><SPAN LANG=3D"fr"><FONT COLOR=3D"#800000" SIZE=3D2 FACE=3D"Arial">YC: =
It is necessary to centralize the overload mechanism implementation on =
font-end servers because only those servers konw the load level of the =
whole cluster. In case there are more than one front-end sever we can =
consider that each one of them knows the load level of the whole =
cluster. The way the frond-end servers exhange information of the =
&quot;work&quot; each one has distribute to the cluster elements is =
proprietary and &quot;out of the scope&quot;.</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp; </FONT></SPAN></P>
<BR>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">A much better =
requirement would be to provide the diagram of the architecture you are =
concerned with:</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+----------+&nbsp;&nbsp;&nbsp; =
+----------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +----------+&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Server#1 =
|&nbsp; | Server#2 |....| Server#n | </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+----------+&nbsp;&nbsp;&nbsp; =
+----------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +----------+</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; | </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; |</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; | </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; =
+----------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +-----| =
Front-End|-------+</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; | Server&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; +----------+ </FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">and state a =
requirement that the solution work effectively in such an =
architecture.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">(Although I would =
prefer to see the requirment generalized to several front-end servers =
feeding one cluster of servers -- the front-end servers must cooperate =
in balancing the load they deliver to the</FONT></SPAN></P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">servers.)</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT COLOR=3D"#800000" SIZE=3D2 FACE=3D"Arial">YC: =
The way the front-end servers cooperate in balancing the load they =
deliver to the servers is proprietary and should remain &quot;out of the =
scope&quot;</FONT></SPAN></P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Dale</FONT></SPAN>
</P>
<BR>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">_______________________________________________</FONT></SP=
AN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Sipping mailing =
list&nbsp; </FONT></SPAN><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping"><SPAN =
LANG=3D"fr"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">https://www1.ietf.org/mailman/listinfo/sipping</FONT></U><=
/SPAN></A><SPAN LANG=3D"fr"></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">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</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C7886B.DEBB16D3--



--===============2062505127==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============2062505127==--





From sipping-bounces@ietf.org Fri Apr 27 05:20:21 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhMca-000754-TO; Fri, 27 Apr 2007 05:20:08 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HhMcY-00074v-SV for sipping-confirm+ok@megatron.ietf.org;
	Fri, 27 Apr 2007 05:20:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhMcY-00074n-BY
	for sipping@ietf.org; Fri, 27 Apr 2007 05:20:06 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhMcX-0001zK-H3
	for sipping@ietf.org; Fri, 27 Apr 2007 05:20:06 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E0352215ED; Fri, 27 Apr 2007 11:20:04 +0200 (CEST)
X-AuditID: c1b4fb3e-ad9eabb0000061ca-01-4631c044d285 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	BC69421272; Fri, 27 Apr 2007 11:20:04 +0200 (CEST)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Apr 2007 11:20:04 +0200
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
Subject: RE: [Sipping] Comment on draft-ietf-sipping-cc-transfer-07
Date: Fri, 27 Apr 2007 11:20:01 +0200
Message-ID: <C0E80510684FE94DBDE3A4AF6B968D2D0115391F@esealmw118.eemea.ericsson.se>
In-Reply-To: <4630C983.20807@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] Comment on draft-ietf-sipping-cc-transfer-07
Thread-Index: AceIGiv5+J9x4sCzQimaSTMzyVbvYQAjwtsA
From: "Ian Elz \(CV/ETL\)" <ian.elz@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 27 Apr 2007 09:20:04.0654 (UTC)
	FILETIME=[3D8A44E0:01C788AD]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Paul,

Comments inline marked with [Ian Elz]


Ian Elz

Office: + 44 24 764 35256
gsm: +44 7801723668
ian.elz@ericsson.com


-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
Sent: 26 April 2007 16:47
To: Ian Elz (CV/ETL)
Cc: sipping@ietf.org
Subject: Re: [Sipping] Comment on draft-ietf-sipping-cc-transfer-07

inline

Ian Elz (CV/ETL) wrote:
> In section 7 of the draft (draft-ietf-sipping-cc-transfer-07) you=20
> discuss transfer with a consultative call. In this discussion you=20
> refer to the use of the Replaces header as defined in RFC3891.
>=20
> You do not mention however that for the purpose of this draft the=20
> original dialog between the transferor and the  transfer target must=20
> not have an B2BUA in the message path as the use of the Replaces=20
> header in the later INVITE between the transfer target and transferee=20
> as any B2BUA may have resulted one or more components of the Replaces=20
> header (call-id, from-tag, to-tag) may have been modified as shown
below.
>=20
> +------------+               +---------+               +-----------+
> |            |               |         |               |           |
> | transferor |-------------->| B2BUA   |-------------->| transfer  |
> |            |               |         |               | target    |
> +------------+               +---------+               +-----------+
> Call-id =3D 1234                call-id                  Call-id =3D =
4321
> From-tag =3D ab12               mapped                   From-tag =3D =
ab12
> To-tag =3D cd34                                          To-tag =3D =
cd34
>=20
> Thus the Replaces header sent from the transferor to the transferee in

> the REFER request Refer-to header would be Replaces=20
> (call-id=3D1234,from-tag=3Dab12,to-tag=3Dcd34). This would not be =
valid if=20
> received in an INVITE at the transfer target and the INVITE would be=20
> rejected as the Replaces header does not match an existing dialog.

In this case, the REFER would in fact be sent to the B2BUA, since that
is remote contact of the dialog that the transferor has. The B2BUA will
have to relay the REFER on to the transfer target. Since the B2BUA has
decided to interfere in the call, it has the obligation to fix up the
problems it has caused. In this case it has the responsibility to fix up
the Replaces header.

[Ian Elz] When the REFER is sent it will use the same B2BUA if the REFER
is used inside the dialog for the original INVITE. If the REFER is sent
in a separate dialog then the same B2BUAs may not be used. Even if the
REFER modifies the Replaces header parameter in the Refer-To then in the
subsequent INVITE the Replaces header must be correctly mapped back. The
correction of any mapping of the Replaces header can only be performed
in the path of the REFER, i.e. between the transferor and the
transferee. If there are B2BUAs in the path of the consultative call
between the transfer target and the transferor then there is nothing the
handling of the REFER can do with this leg of the call. Due to the
specification of the Replaces header in RFC3891 you cannot send the
Replaces information in the Refer-To if there are any B2BUAs in the path
of the REFER the Replaces applies to the dialog on the transfer target
side of the transferor. Passing the Replaces information on the
transferee side means that the INVITE Replaces may have to be passed
back via the B2BUAs on the transferee to transferor dialog where the
Replaces would not match an existing dialog and the INVITE would be
rejected. The INVITE Replaces header specifically needs mapping on the
dialog where the REFER is not applicable.

> Thus when mentioning the INVITE with the Replaces header you need to=20
> explicitly state that the UAC generating the INVITE must know that=20
> there was no b2bua in the original call or that no impacted header was
mapped.
>=20
> OR
>=20
> Reference should be made to the appropriate routing algorithm which=20
> indicates how routing should be performed when a parameter from=20
> another dialog is used as part of the initiation of a new dialog.

So far we have never specified how B2BUAs should work.

[Ian Elz] I understand that B2BUA functionality has not been specified
but from the draft from Marjou and SBC there are some headers which are
mapped by B2BUAs for specific reasons: privacy, topology hiding etc. In
the Transfer service the specific example is the Replaces header which
is why I used this as an example in my original comment. It is not only
the B2BUA functionality which needs to be specified and as long as the
B2BUA conforms to the basic UAC/UAS rules then much of this
functionality can actually be left to the specific implementation. The
key issue is the UA functionality in networks where B2BUAs exist. Where
there may be a B2BUA in the network and a new Request uses a header
value from a previous dialog then there is always the possibility that
the 'inherited' value has been mapped by a B2BUA in the previous dialog.
Key headers which I have identified are Replaces (call-id, from-tag,
to-tag), Target-Dialog (call-id, from-tag, to-tag), Contact (where the
contact URI is used as the Request URI in a new dialog or as a Refer-To
URI in a REFER). There are probably others but when any of these headers
is used then the new Request must follow the same B2BUA path as the
original dialog to ensure that the new dialog is associated with the
previous dialog and the headers are mapped correctly.

> Unfortunately SIP does not provide any information as to whether any=20
> header has been mapped in a dialog or what node may have mapped any=20
> header(s). As a result the first option is not practical as it would=20
> require every user agent to know the topology of the entire network=20
> and the message path of a dialog to understand whether the Replaces=20
> header was valid.
>=20
> As the other drafts currently being considered by the sipping WG:
> draft-ietf-sipping-sbc-funcs-03 & draft-marjou-sipping-b2bua-00; both=20
> reference b2bua capability and why it is used within the network=20
> consideration must be given to the correct routing of Requests which=20
> use a value obtained from one dialog as part of a subsequent dialog.
>=20
> Ian Elz
>=20
> Office: + 44 24 764 35256
> gsm: +44 7801723668
> ian.elz@ericsson.com
>=20
>=20
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use=20
> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> sip@ietf.org for new developments of core SIP
>=20


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 27 11:48:41 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhSgT-000054-90; Fri, 27 Apr 2007 11:48:33 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HhSgR-0008WE-Oq for sipping-confirm+ok@megatron.ietf.org;
	Fri, 27 Apr 2007 11:48:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhSgR-0008VC-Dt
	for sipping@ietf.org; Fri, 27 Apr 2007 11:48:31 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhSgP-0007fz-Pd
	for sipping@ietf.org; Fri, 27 Apr 2007 11:48:31 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 27 Apr 2007 08:48:29 -0700
X-IronPort-AV: i="4.14,462,1170662400"; 
	d="scan'208"; a="141471340:sNHT68029506"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3RFmTtN026503; 
	Fri, 27 Apr 2007 08:48:29 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l3RFmTEk015707;
	Fri, 27 Apr 2007 15:48:29 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Apr 2007 08:48:29 -0700
Received: from [10.21.99.4] ([10.21.99.4]) by xfe-sjc-211.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Apr 2007 08:48:28 -0700
Message-ID: <46321B4C.3040006@cisco.com>
Date: Fri, 27 Apr 2007 11:48:28 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Ian Elz (CV/ETL)" <ian.elz@ericsson.com>
Subject: Re: [Sipping] Comment on draft-ietf-sipping-cc-transfer-07
References: <C0E80510684FE94DBDE3A4AF6B968D2D0115391F@esealmw118.eemea.ericsson.se>
In-Reply-To: <C0E80510684FE94DBDE3A4AF6B968D2D0115391F@esealmw118.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Apr 2007 15:48:28.0425 (UTC)
	FILETIME=[7FAB8790:01C788E3]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8595; t=1177688909;
	x=1178552909; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20Comment=20on=20draft-ietf-sipping-cc-tran
	sfer-07 |Sender:=20;
	bh=wupSxQf1JNTE1g7jpqbol53YNk89r6XvoTpu1gkvCpk=;
	b=WyoIPXtIy46R1RcvxZkaivA3n5+wnNRthkp5ReT2GtfWhP3DujY/GAQyQWbeZ5M7xhs2XyXz
	/gfTgPfLkVSrq+gIMhrJBBgxtV/l+5rx1ipEizwvuBSlFILVDH+G5ysSF8D8h9+f5V8ZFVEWLi
	kBvaty1Ob1PYWKTOb+n364HWU=;
Authentication-Results: sj-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

inline

Ian Elz (CV/ETL) wrote:
> Paul,
> 
> Comments inline marked with [Ian Elz]
> 
> 
> Ian Elz
> 
> Office: + 44 24 764 35256
> gsm: +44 7801723668
> ian.elz@ericsson.com
> 
> 
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: 26 April 2007 16:47
> To: Ian Elz (CV/ETL)
> Cc: sipping@ietf.org
> Subject: Re: [Sipping] Comment on draft-ietf-sipping-cc-transfer-07
> 
> inline
> 
> Ian Elz (CV/ETL) wrote:
>> In section 7 of the draft (draft-ietf-sipping-cc-transfer-07) you 
>> discuss transfer with a consultative call. In this discussion you 
>> refer to the use of the Replaces header as defined in RFC3891.
>>
>> You do not mention however that for the purpose of this draft the 
>> original dialog between the transferor and the  transfer target must 
>> not have an B2BUA in the message path as the use of the Replaces 
>> header in the later INVITE between the transfer target and transferee 
>> as any B2BUA may have resulted one or more components of the Replaces 
>> header (call-id, from-tag, to-tag) may have been modified as shown
> below.
>> +------------+               +---------+               +-----------+
>> |            |               |         |               |           |
>> | transferor |-------------->| B2BUA   |-------------->| transfer  |
>> |            |               |         |               | target    |
>> +------------+               +---------+               +-----------+
>> Call-id = 1234                call-id                  Call-id = 4321
>> From-tag = ab12               mapped                   From-tag = ab12
>> To-tag = cd34                                          To-tag = cd34
>>
>> Thus the Replaces header sent from the transferor to the transferee in
> 
>> the REFER request Refer-to header would be Replaces 
>> (call-id=1234,from-tag=ab12,to-tag=cd34). This would not be valid if 
>> received in an INVITE at the transfer target and the INVITE would be 
>> rejected as the Replaces header does not match an existing dialog.
> 
> In this case, the REFER would in fact be sent to the B2BUA, since that
> is remote contact of the dialog that the transferor has. The B2BUA will
> have to relay the REFER on to the transfer target. Since the B2BUA has
> decided to interfere in the call, it has the obligation to fix up the
> problems it has caused. In this case it has the responsibility to fix up
> the Replaces header.
> 
> [Ian Elz] When the REFER is sent it will use the same B2BUA if the REFER
> is used inside the dialog for the original INVITE. If the REFER is sent
> in a separate dialog then the same B2BUAs may not be used.

If the refer is intended for the transfer target then the transferor has 
only a few options of where to send it. Note that the transferor doesn't 
in general know there is a B2BUA in the call. Instead, it thinks it has 
a dialog with the transfer target. Practically speaking, the B2BUA *is* 
the transfer target.

If the refer is not sent within the existing dialog, then it must be 
addressed so that it will reach the transfer target. 3261 says that the 
remote contact must be globally routable. So in general the right thing 
to do is to send the refer out of dialog to the remote contact. That 
would be the contact address provided by the B2BUA. If the B2BUA didn't 
use a globally unique routable contact then there may be problems. In 
regular cases, without B2BUAs, we know that UAs often don't have 
globally routable contacts and so this strategy doesn't work. That is 
why GRUU was invented.

In lieu of gruu support, various work-arounds may be tried. The trouble 
is that none of them is entirely reliable. A common one is to send the 
out of dialog request to the To address of the original call. If that 
were tried here, its hard to say what would happen. Probably nothing good.

The above argues for the support of GRUU, for the B2BUA to use a contact 
with gruu properties, and for the transferor to send the out of dialog 
refer to the remote contact.

If you can't do that, then your best bet is to send the refer in-dialog.

The absolutely worst thing you could possibly do would be to have the 
transferor take some special action based on the assumption that there 
is a B2BUA in the call.

	Paul

> Even if the
> REFER modifies the Replaces header parameter in the Refer-To then in the
> subsequent INVITE the Replaces header must be correctly mapped back. The
> correction of any mapping of the Replaces header can only be performed
> in the path of the REFER, i.e. between the transferor and the
> transferee. If there are B2BUAs in the path of the consultative call
> between the transfer target and the transferor then there is nothing the
> handling of the REFER can do with this leg of the call. Due to the
> specification of the Replaces header in RFC3891 you cannot send the
> Replaces information in the Refer-To if there are any B2BUAs in the path
> of the REFER the Replaces applies to the dialog on the transfer target
> side of the transferor. Passing the Replaces information on the
> transferee side means that the INVITE Replaces may have to be passed
> back via the B2BUAs on the transferee to transferor dialog where the
> Replaces would not match an existing dialog and the INVITE would be
> rejected. The INVITE Replaces header specifically needs mapping on the
> dialog where the REFER is not applicable.
> 
>> Thus when mentioning the INVITE with the Replaces header you need to 
>> explicitly state that the UAC generating the INVITE must know that 
>> there was no b2bua in the original call or that no impacted header was
> mapped.
>> OR
>>
>> Reference should be made to the appropriate routing algorithm which 
>> indicates how routing should be performed when a parameter from 
>> another dialog is used as part of the initiation of a new dialog.
> 
> So far we have never specified how B2BUAs should work.
> 
> [Ian Elz] I understand that B2BUA functionality has not been specified
> but from the draft from Marjou and SBC there are some headers which are
> mapped by B2BUAs for specific reasons: privacy, topology hiding etc. In
> the Transfer service the specific example is the Replaces header which
> is why I used this as an example in my original comment. It is not only
> the B2BUA functionality which needs to be specified and as long as the
> B2BUA conforms to the basic UAC/UAS rules then much of this
> functionality can actually be left to the specific implementation. The
> key issue is the UA functionality in networks where B2BUAs exist. Where
> there may be a B2BUA in the network and a new Request uses a header
> value from a previous dialog then there is always the possibility that
> the 'inherited' value has been mapped by a B2BUA in the previous dialog.
> Key headers which I have identified are Replaces (call-id, from-tag,
> to-tag), Target-Dialog (call-id, from-tag, to-tag), Contact (where the
> contact URI is used as the Request URI in a new dialog or as a Refer-To
> URI in a REFER). There are probably others but when any of these headers
> is used then the new Request must follow the same B2BUA path as the
> original dialog to ensure that the new dialog is associated with the
> previous dialog and the headers are mapped correctly.
> 
>> Unfortunately SIP does not provide any information as to whether any 
>> header has been mapped in a dialog or what node may have mapped any 
>> header(s). As a result the first option is not practical as it would 
>> require every user agent to know the topology of the entire network 
>> and the message path of a dialog to understand whether the Replaces 
>> header was valid.
>>
>> As the other drafts currently being considered by the sipping WG:
>> draft-ietf-sipping-sbc-funcs-03 & draft-marjou-sipping-b2bua-00; both 
>> reference b2bua capability and why it is used within the network 
>> consideration must be given to the correct routing of Requests which 
>> use a value obtained from one dialog as part of a subsequent dialog.
>>
>> Ian Elz
>>
>> Office: + 44 24 764 35256
>> gsm: +44 7801723668
>> ian.elz@ericsson.com
>>
>>
>>
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.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
>>
> 


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 27 12:14:59 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhT61-0007uI-CW; Fri, 27 Apr 2007 12:14:57 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HhT5z-0007sQ-Qu for sipping-confirm+ok@megatron.ietf.org;
	Fri, 27 Apr 2007 12:14:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhT5z-0007sI-HQ
	for sipping@ietf.org; Fri, 27 Apr 2007 12:14:55 -0400
Received: from an-out-0708.google.com ([209.85.132.247])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhT5z-0006nK-8b
	for sipping@ietf.org; Fri, 27 Apr 2007 12:14:55 -0400
Received: by an-out-0708.google.com with SMTP id d30so703553and
	for <sipping@ietf.org>; Fri, 27 Apr 2007 09:14:54 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=c6zAvfSvS7wKxI+puvnraROufO/ttDy4A3f7pHEmXj37pZ5NWEIx1jqqq2q4KdX29Bn98reQDViVi8skRNYsSaxSUjoleTneTyT6LVdl8tm7JEILeRFMCxqPh6GFM2hAj6ozmHuM7uOuS0brWnzouHVFdh46Xk1ia3mfPHlvLlA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=KLD6Lo8axHPJW5Ef06nb3pySg44P9LFLrWrWFfl5kV4iQbsZnS1gbkqIN3eGD6767l6rKNDK5gBxNQgF4aus+t+Gw+IcOtcYUXk8NR7Emh5jeDTsI2Zhg+yhII+g4iEpO23mBF1Ejs0GxFF1lLpon1lVBZYEHo/Tmf36tlcnuZY=
Received: by 10.100.216.3 with SMTP id o3mr2167458ang.1177690494505;
	Fri, 27 Apr 2007 09:14:54 -0700 (PDT)
Received: by 10.100.194.13 with HTTP; Fri, 27 Apr 2007 09:14:54 -0700 (PDT)
Message-ID: <458913680704270914r73259796p306617c6a3d617d2@mail.gmail.com>
Date: Fri, 27 Apr 2007 18:14:54 +0200
From: "Xavier Marjou" <xavier.marjou@orange-ftgroup.com>
To: "Ian Elz (CV/ETL)" <ian.elz@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Google-Sender-Auth: 9ee95b1ae1c6468d
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: sipping@ietf.org
Subject: [Sipping] b2bua and cc-transfer
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

I renamed the thread, as I think that this topic should be left out of
the draft-ietf-sipping-cc-transfer-07. Such a b2bua topic may affect
any SIP-related draft or RFC.


> So far we have never specified how B2BUAs should work.

Indeed: the draft-ietf-sipping-sbc-funcs looks at some b2buas in order
to investigate some missing functions in SIP. The
draft-marjou-sipping-b2bua is an individual draft, which means that it
is not an IETF working item. This later draft tries to catch best
practices about some type of B2BUA (the so-called transparent B2BUA
type) because many of them exist in the nature and because there is no
existing document on this topic. To sum-up, the situation with SIP and
B2BUA is very similar to the situation with SIP-RTP and NAT: NATs make
life harder for everybody and solutions to cope with them are not
easy.

> Since the B2BUA has decided to interfere in the call, it has the
> obligation to fix up the problems it has caused.
I agree with Paul.

For the following call-flows, a B2BUA may be located in different
places. I think it is important to look for which UA the B2BUA is
acting for. (cf 3 examples below for the following regular call-flow).
I would say that if someone deploys a B2BUA acting on the behalf of a
UA, he needs to make sure that the B2BUA is in the path of all SIP
flows for this UA and that the B2BUA will also correct the discrepancy
it introduces (I know this is heavy, but I do not see any other
solutions).

Cheers,
Xavier

transferor(b)             transfereree(a)               t-target(c)
|                                |                                |
|                                |                                |
| INV d1                         |                                |
|<-------------------------------|                                |
| INV d2                                                          |
|---------------------------------------------------------------->|
| REF dx Replaces:d2             |                                |
|------------------------------->|                                |
|                                |INV d3 Rpl:d2                   |
|                                |------------------------------->|


transferor(b)             transfereree(a)    b2bua_c    t-target(c)
|                                |               ||               |
|                                |               ||               |
| INV d1                         |               ||               |
|<-------------------------------|               ||               |
| INV d2                                         || INV d2'       |
|------------------------------------------------||-------------->|
| REF dx Replaces:d2             |                                |
|------------------------------->|                                |
|                                |INV d3 Rpl:d2  || INV d3'Rpl:d2'|
|                                |---------------||-------------->|


transferor(b)  b2bua_a    transfereree(a)    b2bua_a    t-target(c)
|               ||               |                                |
|               ||               |                                |
| INV d1'       || INV d1        |                                |
|<--------------||---------------|                                |
| INV d2                                                          |
|---------------------------------------------------------------->|
| REF dx  Rpl:d2                 |                                |
|------------------------------->|                                |
|                                |INV d3 Rpl:d2  || INV d3'Rpl:d2 |
|                                |---------------||-------------->|


transferor(b)  b2bua_b    transfereree(a)               t-target(c)
|               ||               |                                |
|               ||               |                                |
| INV d1'       || INV d1        |                                |
|<--------------||---------------|                                |
| INV d2        || INV d2'                                        |
|---------------||----------------------------------------------->|
| REF dx  Rpl:d2|| REF dx' Rpl:d2'                                |
|---------------||-------------->|                                |
|                                |INV d3 Rpl:d2'                  |
|                                |------------------------------->|


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 27 15:38:08 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhWGb-0001mj-1k; Fri, 27 Apr 2007 15:38:05 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HhWGZ-0001me-Ja for sipping-confirm+ok@megatron.ietf.org;
	Fri, 27 Apr 2007 15:38:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhWGZ-0001mW-9z
	for sipping@ietf.org; Fri, 27 Apr 2007 15:38:03 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhWGY-0000ph-NN
	for sipping@ietf.org; Fri, 27 Apr 2007 15:38:03 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-5.cisco.com with ESMTP; 27 Apr 2007 12:37:52 -0700
X-IronPort-AV: i="4.14,462,1170662400"; 
	d="scan'208"; a="416462911:sNHT57966356"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l3RJbpkm029019; 
	Fri, 27 Apr 2007 12:37:51 -0700
Received: from [10.32.245.158] (stealth-10-32-245-158.cisco.com
	[10.32.245.158])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l3RJbown002374;
	Fri, 27 Apr 2007 19:37:50 GMT
In-Reply-To: <2AF8FF7D89242541B12E7A47F6ECB4BE05614159@ftrdmel3.rd.francetelecom.fr>
References: <2AF8FF7D89242541B12E7A47F6ECB4BE05614159@ftrdmel3.rd.francetelecom.fr>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <B73D810F-25B0-4295-93ED-DE1ED108FCA6@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: David R Oran <oran@cisco.com>
Subject: Re: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
Date: Fri, 27 Apr 2007 15:37:43 -0400
To: CHADLI Youssef RD-CORE-ISS <youssef.chadli@orange-ftgroup.com>
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4897; t=1177702671;
	x=1178566671; c=relaxed/simple; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[SIPPING]=20Comments=20on=20draft-ietf-sipping-overlo
	ad-reqs-00 |Sender:=20;
	bh=RdPoMshnP55qgFHnXym7hz/yURV0QTHU+r351aSEbt8=;
	b=D+LPGU8qG+j866vbAA303JsTsbn9fzCbqpfyNNy7Z2kHlIXxjRM3to6OaHBaE1y61wsD1Mm5
	neCnWg7fSatsw/U6luQCTSKcF1PJVTQUa0pfJD0Vy2jvTrGx9NkZGl3H;
Authentication-Results: sj-dkim-8; header.From=oran@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim8002 verified; ); 
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org


On Apr 26, 2007, at 9:04 PM, CHADLI Youssef RD-CORE-ISS wrote:

> Hi,
>
> Inline
>
> Youssef
>
> -----Message d'origine-----
> De : Spencer Dawkins [mailto:spencer@mcsr-labs.org]
> Envoy=E9 : mercredi 25 avril 2007 15:30
> =C0 : sipping
> Objet : Re: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
>
> Just checking -
>
> From: "David R Oran" <oran@cisco.com>
>
> >> On Apr 25, 2007, at 5:18 AM, CHADLI Youssef RD-CORE-ISS wrote:
> >>
> >>> REQ 17: The overload mechanism must not provide an avenue for
> >>>       malicious attack.
> >>>
> >>> To prevent malicious attacks, it's necessary to prevent untrusted
> >>> elements to access load information of the SIP servers.
> >> I must be dense, so bear with me. Could you explain what new
> >> malicious attack is opened or existing attack amplified by treating
> >> the load information as confidential?
>
> > I am just as dense as David - please explain=85
>
> One of the elementary security rules is to provide the minimum =20
> information of a given server (e.g. server name, software version =85=20=

> etc): the more information you give, the more the risk of malicious =20=

> attacks increases.
This is proof by emphatic assertion. Please give an existence proof =20
of a case where a new attack or an enhanced attack is enabled. I'm =20
not claiming one DOESN'T exist, I just want exidence to back up your =20
assertion.
> In fact, having information about the server can be used by =20
> malicious elements to detect the server weaknesses. For instance, a =20=

> server that is 100 % overloaded may be more vulnerable which =20
> facilitates malicious attacks.
Why?
> Another argument in favour of controlling the access to the load =20
> information is that for confidentiality reasons, a service provider =20=

> may do no want that an untrusted service provider  knows the load =20
> level of its servers.
>
>
But this may be true of ANY information about a server, including its =20=

very existence. Again, what is special about the load information?

>
> >>> REQ 22: The mechanism should be easily centralised in the front-=20=

> end
> >>> servers in case the SIP server is implemented as a cluster of =20
> servers
> >>> running on different machines.
> >>>
> >> I'm not sure how you ascertain if this requirement is met. I can =20=

> see
> >> how you could write a requirement that the scheme allow such
> >> configurations, just not that it be "easy". Easy compared to what?
>
> > I like the requirement (although I agree with David that "easily" =20=

> is a weasel word), but I'm concerned that we may not have a basis =20
> for judging "can be centralized in the  > front-end servers".
>
> What I mean by "can be easily centralised on the front-ends =20
> servers" is : implementing overload mechanism shall not heavily =20
> impact the performance of front-ends servers:
>
> 1) the mechanism shall not require front-ends parsing all received =20
> messages to look for overload control information
> 2) the mechanism shall not require front-end servers to open =20
> messages sent by applications to insert overload control information
These two completely lost me. Either boxes participate in the load =20
control scheme or they don't. If the "front end" doesn't participate =20
then the requirements are moot for them. If they do participate, I =20
don't see how you can mandate these requirements for in a practical =20
scheme with cascaded proxy farms (e.g on entry and exit at the =20
borders of an SP cloud).
> 3) the mechanism shall support aggregating load information from =20
> different elements of a server farm
>
This seems like a good requirement.
> > If things have changed in the past few years, I apologize for my =20
> confusion, but my understanding was that most of the front-end-to-=20
> cluster schemes were proprietary, so > we might be able to say =20
> "works on THIS front-end-to-cluster scheme", but wouldn't know if =20
> it works on ANY front-end-to-cluster scheme.
>
> I agree that front-end-to-cluster schemes can be considered as =20
> proprietary. We can assume that the front-end server knows the load =20=

> status of the whole cluster.
If that's the case, then I don't see the need for this discussion or =20
these requirements since the front end is part of the cluster and the =20=

internal composition is invisible form the outside.
> > Can someone smarter than I am express an opinion about this?
>
> Thanks,
>
> Spencer
>
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use sip-=20
> implementors@cs.columbia.edu for questions on current sip Use =20
> sip@ietf.org for new developments of core SIP
>


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 27 15:56:40 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhWYZ-0003eJ-0L; Fri, 27 Apr 2007 15:56:39 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HhWYX-0003e9-R6 for sipping-confirm+ok@megatron.ietf.org;
	Fri, 27 Apr 2007 15:56:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhWYX-0003e1-Hc
	for sipping@ietf.org; Fri, 27 Apr 2007 15:56:37 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhWYV-0007Bl-SU
	for sipping@ietf.org; Fri, 27 Apr 2007 15:56:37 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 27 Apr 2007 12:56:35 -0700
X-IronPort-AV: i="4.14,463,1170662400"; 
	d="scan'208"; a="141575804:sNHT53033031"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l3RJuZnd006629; 
	Fri, 27 Apr 2007 12:56:35 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l3RJuPZt010567;
	Fri, 27 Apr 2007 19:56:35 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Apr 2007 12:56:34 -0700
Received: from [128.107.106.89] ([128.107.106.89]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Apr 2007 12:56:33 -0700
Message-ID: <46325571.3060309@cisco.com>
Date: Fri, 27 Apr 2007 15:56:33 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Xavier Marjou <xavier.marjou@orange-ftgroup.com>
Subject: Re: [Sipping] b2bua and cc-transfer
References: <458913680704270914r73259796p306617c6a3d617d2@mail.gmail.com>
In-Reply-To: <458913680704270914r73259796p306617c6a3d617d2@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Apr 2007 19:56:33.0356 (UTC)
	FILETIME=[27C7C0C0:01C78906]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=6019; t=1177703795;
	x=1178567795; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20b2bua=20and=20cc-transfer
	|Sender:=20; bh=f65wNa/e2EHGTnY7NeDcygKg/GMeCdGGBpI5eeiIj9s=;
	b=RIE6KKxCbD7OEUKI+6/t2ieRGX2droZkoSH+70CvbpKCSCiJYlCdhzAFaGyzccK/gdtJ8yac
	VWoWi7AtXCDdluf2chgdrrHbd+con1vPM9s7D8kmenOap+mN7Bd3j9fm;
Authentication-Results: sj-dkim-3; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: "Ian Elz \(CV/ETL\)" <ian.elz@ericsson.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Xavier,

Thanks for reorganizing this. I agree with you that there have been 
*some* works on B2BUAs, and maybe it is time for some further work on 
topics such as this. I definitely think such work should be addressed as 
additional clarification on B2BUA behavior, rather than rules for 
everybody else so that they may work around what a B2BUA might do to them.

However I don't think it is possible to provide guidelines for this kind 
of behavior for B2BUAs in general, because the concept of B2BUA is too 
general. There can be many kinds of B2BUA, and not all should behave in 
the same way. For instance, an SBC and a conference focus are both 
B2BUAs. But the way they handle a REFER is likely to be quite different.

In most cases when people ask questions about B2BUAs they are assuming 
the B2BUA acts much like a proxy, as an SBC typically does. So it might 
be worthwhile to focus on that kind initially.

	Paul

Xavier Marjou wrote:
> I renamed the thread, as I think that this topic should be left out of
> the draft-ietf-sipping-cc-transfer-07. Such a b2bua topic may affect
> any SIP-related draft or RFC.
> 
> 
>> So far we have never specified how B2BUAs should work.
> 
> Indeed: the draft-ietf-sipping-sbc-funcs looks at some b2buas in order
> to investigate some missing functions in SIP. The
> draft-marjou-sipping-b2bua is an individual draft, which means that it
> is not an IETF working item. This later draft tries to catch best
> practices about some type of B2BUA (the so-called transparent B2BUA
> type) because many of them exist in the nature and because there is no
> existing document on this topic. To sum-up, the situation with SIP and
> B2BUA is very similar to the situation with SIP-RTP and NAT: NATs make
> life harder for everybody and solutions to cope with them are not
> easy.
> 
>> Since the B2BUA has decided to interfere in the call, it has the
>> obligation to fix up the problems it has caused.
> I agree with Paul.
> 
> For the following call-flows, a B2BUA may be located in different
> places. I think it is important to look for which UA the B2BUA is
> acting for. (cf 3 examples below for the following regular call-flow).
> I would say that if someone deploys a B2BUA acting on the behalf of a
> UA, he needs to make sure that the B2BUA is in the path of all SIP
> flows for this UA and that the B2BUA will also correct the discrepancy
> it introduces (I know this is heavy, but I do not see any other
> solutions).
> 
> Cheers,
> Xavier
> 
> transferor(b)             transfereree(a)               t-target(c)
> |                                |                                |
> |                                |                                |
> | INV d1                         |                                |
> |<-------------------------------|                                |
> | INV d2                                                          |
> |---------------------------------------------------------------->|
> | REF dx Replaces:d2             |                                |
> |------------------------------->|                                |
> |                                |INV d3 Rpl:d2                   |
> |                                |------------------------------->|
> 
> 
> transferor(b)             transfereree(a)    b2bua_c    t-target(c)
> |                                |               ||               |
> |                                |               ||               |
> | INV d1                         |               ||               |
> |<-------------------------------|               ||               |
> | INV d2                                         || INV d2'       |
> |------------------------------------------------||-------------->|
> | REF dx Replaces:d2             |                                |
> |------------------------------->|                                |
> |                                |INV d3 Rpl:d2  || INV d3'Rpl:d2'|
> |                                |---------------||-------------->|
> 
> 
> transferor(b)  b2bua_a    transfereree(a)    b2bua_a    t-target(c)
> |               ||               |                                |
> |               ||               |                                |
> | INV d1'       || INV d1        |                                |
> |<--------------||---------------|                                |
> | INV d2                                                          |
> |---------------------------------------------------------------->|
> | REF dx  Rpl:d2                 |                                |
> |------------------------------->|                                |
> |                                |INV d3 Rpl:d2  || INV d3'Rpl:d2 |
> |                                |---------------||-------------->|
> 
> 
> transferor(b)  b2bua_b    transfereree(a)               t-target(c)
> |               ||               |                                |
> |               ||               |                                |
> | INV d1'       || INV d1        |                                |
> |<--------------||---------------|                                |
> | INV d2        || INV d2'                                        |
> |---------------||----------------------------------------------->|
> | REF dx  Rpl:d2|| REF dx' Rpl:d2'                                |
> |---------------||-------------->|                                |
> |                                |INV d3 Rpl:d2'                  |
> |                                |------------------------------->|
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.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
> 


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Fri Apr 27 19:56:36 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhaIk-00027d-0s; Fri, 27 Apr 2007 19:56:34 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HhaIi-00027Y-CL for sipping-confirm+ok@megatron.ietf.org;
	Fri, 27 Apr 2007 19:56:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhaIi-00026X-1i
	for sipping@ietf.org; Fri, 27 Apr 2007 19:56:32 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhaIh-0004qD-Ir
	for sipping@ietf.org; Fri, 27 Apr 2007 19:56:32 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 27 Apr 2007 16:56:31 -0700
X-IronPort-AV: i="4.14,463,1170662400"; 
	d="scan'208"; a="141665273:sNHT51926211"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l3RNuUjH028581; 
	Fri, 27 Apr 2007 16:56:30 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3RNuTMN007206;
	Fri, 27 Apr 2007 23:56:30 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Apr 2007 16:56:30 -0700
Received: from [10.32.241.148] ([10.32.241.148]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Apr 2007 16:56:29 -0700
Message-ID: <46328DAC.9080200@cisco.com>
Date: Fri, 27 Apr 2007 19:56:28 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: CHADLI Youssef RD-CORE-ISS <youssef.chadli@orange-ftgroup.com>
Subject: Re: [SIPPING] Comments on draft-ietf-sipping-overload-reqs-00
References: <2AF8FF7D89242541B12E7A47F6ECB4BE05614159@ftrdmel3.rd.francetelecom.fr>
In-Reply-To: <2AF8FF7D89242541B12E7A47F6ECB4BE05614159@ftrdmel3.rd.francetelecom.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 27 Apr 2007 23:56:29.0409 (UTC)
	FILETIME=[AC7F1D10:01C78927]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4346; t=1177718190;
	x=1178582190; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[SIPPING]=20Comments=20on=20draft-ietf-sipping-overlo
	ad-reqs-00 |Sender:=20;
	bh=9HpV2f5E9RgvYLebd0U1zoxN3lsMgf4Vt91FFEpW44A=;
	b=DXOQbKwb9+ZhzBlNjgS2TcLl1ZQ7aZBEIGyryCTjPD8dpVnizcXNkIVyfLZjW4pd33993rc7
	hEBglwe4WW/2kRlDHEHHobaan505ceaFjLd5GXx0jr33gEUE9KU3nJH+;
Authentication-Results: sj-dkim-4; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 1.1 (+)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: sipping <sipping@ietf.org>, David R Oran <oran@cisco.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

inline.

CHADLI Youssef RD-CORE-ISS wrote:


>> >> REQ 17: The overload mechanism must not provide an avenue for
>> >>       malicious attack.
>> >>
>> >> To prevent malicious attacks, it's necessary to prevent untrusted
>> >> elements to access load information of the SIP servers.
>> > I must be dense, so bear with me. Could you explain what new 
>> > malicious attack is opened or existing attack amplified by treating 
>> > the load information as confidential?
> 
>>  I am just as dense as David - please explain…
> 
> One of the elementary security rules is to provide the minimum 
> information of a given server (e.g. server name, software version …etc): 
> the more information you give, the more the risk of malicious attacks 
> increases. In fact, having information about the server can be used by 
> malicious elements to detect the server weaknesses. For instance, a 
> server that is 100 % overloaded may be more vulnerable which facilitates 
> malicious attacks.

I, like others, do not see what attack this opens up. I think you need 
to give a specific example.

> 
> Another argument in favour of controlling the access to the load 
> information is that for confidentiality reasons, a service provider may 
> do no want that an untrusted service provider  knows the load level of 
> its servers.

I'm OK with a requirement around this point speifically. I do understand 
that service providers view the load on their network overall as 
proprietary. The simple answer, of course, is that you are always free 
to not implement this extension towards proxies outside of your domain. 
If you want to capture that in a requirement, how about:

REQ XX: It must be possible to disable the reporting of load information 
towards upstream targets based on the identity of those targets. Of 
course, in such cases, there is no expectation that the overload 
mechanism itself will help prevent overload from that upstream target.

I think we'd have a hard time not meeting this requirement, but I'm fine 
to make it explicit.



> 
> 
> 
>> >> REQ 22: The mechanism should be easily centralised in the front-end
>> >> servers in case the SIP server is implemented as a cluster of servers
>> >> running on different machines.
>> >>
>> > I'm not sure how you ascertain if this requirement is met. I can see 
>> > how you could write a requirement that the scheme allow such 
>> > configurations, just not that it be "easy". Easy compared to what?
> 
>>  I like the requirement (although I agree with David that "easily" is a 
> weasel word), but I'm concerned that we may not have a basis for judging 
> "can be centralized in the  > front-end servers".
> 

I'd propose:

REQ XX: It must be possible for the overload mechanism to work in cases 
where there is a load balancer in front of a farm of proxies, and that 
load balancer tracks the state of the nodes in the cluster, and actually 
implements the overload mechanism.

I suspect we'd have a hard time not meeting this requirement, but I am 
OK with adding it.

> What I mean by "can be easily centralised on the front-ends servers" is 
> : implementing overload mechanism shall not heavily impact the 
> performance of front-ends servers:
> 
> 1) the mechanism shall not require front-ends parsing all received 
> messages to look for overload control information

This is impossible to meet. We are going to be doing this as a sip 
extension, and that necesarily requires looking at sip messages to process.

> 2) the mechanism shall not require front-end servers to open messages 
> sent by applications to insert overload control information

Also impossible to meet. The load balancer will have to insert load into 
the SIP header somewhere.

> 
> 3) the mechanism shall support aggregating load information from 
> different elements of a server farm

I think this is implied by the requirement above that I proposed, which 
I prefer.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sat Apr 28 17:27:03 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhuRK-0006r9-KD; Sat, 28 Apr 2007 17:26:46 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HhuRJ-0006pq-CE for sipping-confirm+ok@megatron.ietf.org;
	Sat, 28 Apr 2007 17:26:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhuRJ-0006nj-1m
	for sipping@ietf.org; Sat, 28 Apr 2007 17:26:45 -0400
Received: from rwcrmhc13.comcast.net ([204.127.192.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhuRF-00087x-0E
	for sipping@ietf.org; Sat, 28 Apr 2007 17:26:45 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc13) with ESMTP
	id <20070428212639m130035k9be>; Sat, 28 Apr 2007 21:26:39 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l3SLQcqi026317
	for <sipping@ietf.org>; Sat, 28 Apr 2007 17:26:38 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l3SLQcPg026313;
	Sat, 28 Apr 2007 17:26:38 -0400
Date: Sat, 28 Apr 2007 17:26:38 -0400
Message-Id: <200704282126.l3SLQcPg026313@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <OF6934D3A1.1CC2A5F1-ON652572C9.0034FFBD-652572C9.0035F075@flextronicssoftware.com>
	(Preethi.Sadasivan@aricent.com)
Subject: Re: [Sipping] 433 error response format.
References: <OF6934D3A1.1CC2A5F1-ON652572C9.0034FFBD-652572C9.0035F075@flextronicssoftware.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

   From: Preethi.Sadasivan@aricent.com

      A UAC receiving a 433 (Anonymity Disallowed) MUST NOT retry the
      [...]

   How will the UAS indicate the UAC that it has a desire for the
   request to be retried. Will this be communicated in some headers
   like that of Retry-Header.

The UAS has no input into the decision by the UAC to retry the request
(without anonymity).

Dale


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 29 06:14:36 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hi6QI-000804-2J; Sun, 29 Apr 2007 06:14:30 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hi6QH-0007zz-2T for sipping-confirm+ok@megatron.ietf.org;
	Sun, 29 Apr 2007 06:14:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hi6QG-0007zr-Kg
	for sipping@ietf.org; Sun, 29 Apr 2007 06:14:28 -0400
Received: from [204.200.195.236] (helo=personeta.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hi6QE-0005bo-Vs
	for sipping@ietf.org; Sun, 29 Apr 2007 06:14:28 -0400
Received: from adii ([194.90.193.76]) (authenticated bits=0)
	by personeta.com (8.13.6.20060614/8.13.6) with ESMTP id l3TAENDo000599; 
	Sun, 29 Apr 2007 10:14:25 GMT
Message-Id: <200704291014.l3TAENDo000599@personeta.com>
From: "adi" <adi@personeta.com>
To: <Dale.Worley@comcast.net>, <sipping@ietf.org>
Subject: RE: [Sipping] 433 error response format.
Date: Sun, 29 Apr 2007 13:14:16 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <200704282126.l3SLQcPg026313@dragon.ariadne.com>
Thread-Index: AceJ2/qvFLlPUrCAS2WjeZSYKvmcOAAapYww
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

UAS don't need to instruct UAC on retry since the decision on retry is user
dependent and the reason to send 433 is because the UAC don't have a way to
handle the case (announcements to dial #82 and the number for example to
allow normal call without hiding caller information).
In some cases of international call the UAC can't identify treatment to the
caller.

Adi

-----Original Message-----
From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net] 
Sent: Sunday, April 29, 2007 12:27 AM
To: sipping@ietf.org
Subject: Re: [Sipping] 433 error response format.

   From: Preethi.Sadasivan@aricent.com

      A UAC receiving a 433 (Anonymity Disallowed) MUST NOT retry the
      [...]

   How will the UAS indicate the UAC that it has a desire for the
   request to be retried. Will this be communicated in some headers
   like that of Retry-Header.

The UAS has no input into the decision by the UAC to retry the request
(without anonymity).

Dale


_______________________________________________
Sipping mailing list  https://www1.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



_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Sun Apr 29 16:47:54 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HiGJ8-000231-5A; Sun, 29 Apr 2007 16:47:46 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HiGJ7-00022w-2w for sipping-confirm+ok@megatron.ietf.org;
	Sun, 29 Apr 2007 16:47:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HiGJ6-00022o-Ph
	for sipping@ietf.org; Sun, 29 Apr 2007 16:47:44 -0400
Received: from smtp2.versatel.nl ([62.58.50.89])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HiGJ4-0000qP-3R
	for sipping@ietf.org; Sun, 29 Apr 2007 16:47:44 -0400
Received: (qmail 5020 invoked by uid 0); 29 Apr 2007 20:47:40 -0000
Received: from ip198-11-212-87.adsl2.versatel.nl (HELO BEMBUSTER)
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp2.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 29 Apr 2007 20:47:40 -0000
Message-ID: <01f901c78a9f$71022e70$0601a8c0@BEMBUSTER>
From: "Jeroen van Bemmel" <jbemmel@zonnet.nl>
To: "Hans Erik van Elburg \(RY/ETM\)" <hanserik.van.elburg@ericsson.com>,
	<sipping@ietf.org>
References: <CAC481363DB73049924DDDCFC1AC60A6044F8339@esealmw109.eemea.ericsson.se>
Subject: Re: [Sipping] New I-D for P-Served-User header
Date: Sun, 29 Apr 2007 22:46:20 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1800509063=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1800509063==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_01F5_01C78AB0.3464D8D0"

This is a multi-part message in MIME format.

------=_NextPart_000_01F5_01C78AB0.3464D8D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

New I-D for P-Served-User headerHans,

A colleague of mine pointed out sections 6.5.1 and 6.5.2 in TS 23.218, third 
bullet:
-     in case the Request-URI changes when visiting an Application Server, 
terminate the checking of filter criterias, route the request based on the 
changed value of the Request-URI and do not execute the subsequent steps;

In other words, what you describe in your section 3.2 (diversion while 
continueing on terminating leg) would not occur for an S-CSCF that follows 
the standards

Regarding section 3.3: if the AS converts the incoming terminating request 
to a new originating request for user B, shouldn't it also update the 
P-Asserted-Identity header to reflect the new originating user?

Regards,
Jeroen
  ----- Original Message ----- 
  From: Hans Erik van Elburg (RY/ETM)
  To: sipping@ietf.org
  Sent: Tuesday, April 17, 2007 2:11 PM
  Subject: [Sipping] New I-D for P-Served-User header


  I uploaded a new draft for the P-Served-User Private-Header, until it gets 
available on the online Internet-Drafts directory you can retrieve it here:

  http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user-00.txt

  Abstract

     This document specifies the SIP P-Served-User P-header.  This header
     field addresses an issue that was found in the 3rd-Generation
     Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an
     S-CSCF (Serving Call Session Control Function) and an AS (Application
     Server) on the ISC (IMS Subsystem Service Control) interface to
     convey the identity of the served user and the session case that
     applies to this particular communication session and application
     invocation.

  Best Regards,

  /Hans Erik





------------------------------------------------------------------------------


  _______________________________________________
  Sipping mailing list  https://www1.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 

------=_NextPart_000_01F5_01C78AB0.3464D8D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>New I-D for P-Served-User header</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16414" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hans,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>A colleague of mine pointed =
out&nbsp;sections 6.5.1=20
and&nbsp;6.5.2 in TS 23.218, third bullet:</FONT></DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2>-<SPAN=20
style=3D"mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>in case the =
Request-URI=20
changes when visiting an Application Server, terminate the checking of =
filter=20
criterias, route the request based on the changed value of the =
Request-URI and=20
do not execute the subsequent steps;</FONT></SPAN></DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2>In other words, what you describe =
in your=20
section 3.2 (diversion while continueing on terminating leg) would not =
occur for=20
an S-CSCF that follows the&nbsp;standards</FONT></SPAN></DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2></FONT></SPAN><SPAN =
lang=3DEN-GB><FONT=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2>Regarding section 3.3: if the AS =
converts the=20
incoming terminating request to a new originating request for user B, =
shouldn't=20
it&nbsp;also update the P-Asserted-Identity header to reflect the new=20
originating user?</FONT></SPAN></DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2>Jeroen</FONT></SPAN></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dhanserik.van.elburg@ericsson.com=20
  href=3D"mailto:hanserik.van.elburg@ericsson.com">Hans Erik van Elburg=20
  (RY/ETM)</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dsipping@ietf.org =

  href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, April 17, 2007 =
2:11=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Sipping] New I-D for=20
  P-Served-User header</DIV>
  <DIV><BR></DIV><!-- Converted from text/rtf format -->
  <P><FONT face=3DArial color=3D#800000 size=3D2>I uploaded a new draft =
for the=20
  P-Served-User Private-Header, until it gets available on the online=20
  Internet-Drafts directory you can retrieve it here:</FONT></P>
  <P><A=20
  =
href=3D"http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serv=
ed-user-00.txt"><U></U><U><FONT=20
  face=3DArial color=3D#0000ff=20
  =
size=3D2>http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-ser=
ved-user-00.txt</FONT></U></A><FONT=20
  face=3DArial size=3D2> </FONT></P>
  <P><FONT face=3D"Courier New" size=3D2>Abstract<BR><BR>&nbsp;&nbsp; =
This document=20
  specifies the SIP P-Served-User P-header.&nbsp; This =
header<BR>&nbsp;&nbsp;=20
  field addresses an issue that was found in the =
3rd-Generation<BR>&nbsp;&nbsp;=20
  Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between=20
  an<BR>&nbsp;&nbsp; S-CSCF (Serving Call Session Control Function) and =
an AS=20
  (Application<BR>&nbsp;&nbsp; Server) on the ISC (IMS Subsystem Service =

  Control) interface to<BR>&nbsp;&nbsp; convey the identity of the =
served user=20
  and the session case that<BR>&nbsp;&nbsp; applies to this particular=20
  communication session and application<BR>&nbsp;&nbsp;=20
  invocation.<BR></FONT><BR><FONT face=3DArial color=3D#800000 =
size=3D2>Best=20
  Regards,</FONT> </P>
  <P><B><FONT face=3DArial color=3D#800000 size=3D2>/Hans =
Erik</FONT></B> </P><BR>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>Sipping =
mailing=20
  list&nbsp; https://www1.ietf.org/mailman/listinfo/sipping<BR>This list =
is for=20
  NEW development of the application of SIP<BR>Use=20
  sip-implementors@cs.columbia.edu for questions on current sip<BR>Use=20
  sip@ietf.org for new developments of core =
SIP</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_01F5_01C78AB0.3464D8D0--




--===============1800509063==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1800509063==--






From sipping-bounces@ietf.org Mon Apr 30 03:55:19 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HiQj1-0006mM-F1; Mon, 30 Apr 2007 03:55:11 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HiQiz-0006mD-W6 for sipping-confirm+ok@megatron.ietf.org;
	Mon, 30 Apr 2007 03:55:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HiQiz-0006m5-Jg
	for sipping@ietf.org; Mon, 30 Apr 2007 03:55:09 -0400
Received: from [204.200.195.236] (helo=personeta.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HiQiw-00042k-OB
	for sipping@ietf.org; Mon, 30 Apr 2007 03:55:09 -0400
Received: from adii ([194.90.193.76]) (authenticated bits=0)
	by personeta.com (8.13.6.20060614/8.13.6) with ESMTP id l3U7stBH046223; 
	Mon, 30 Apr 2007 07:55:00 GMT
Message-Id: <200704300755.l3U7stBH046223@personeta.com>
From: "adi" <adi@personeta.com>
To: "'Jeroen van Bemmel'" <jbemmel@zonnet.nl>,
	"'Hans Erik van Elburg \(RY/ETM\)'" <hanserik.van.elburg@ericsson.com>, 
	<sipping@ietf.org>
Subject: RE: [Sipping] New I-D for P-Served-User header
Date: Mon, 30 Apr 2007 10:54:48 +0300
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <01f901c78a9f$71022e70$0601a8c0@BEMBUSTER>
Thread-Index: AceKn6z8SGjejeWsQIqNsM41ddlcvQAXJDPg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 439b8e44c906b144bce6744ebb966e60
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1382201062=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1382201062==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0037_01C78B15.FFE80BC0"

This is a multi-part message in MIME format.

------=_NextPart_000_0037_01C78B15.FFE80BC0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Jeroen,

 

P-Asserted-Identity it needs to remain the originator of the call and to use
history-info or diversion to pass the redirector address.

Look at VM redirection or any Call Forwarding for example.

 

Adi

  _____  

From: Jeroen van Bemmel [mailto:jbemmel@zonnet.nl] 
Sent: Sunday, April 29, 2007 11:46 PM
To: Hans Erik van Elburg (RY/ETM); sipping@ietf.org
Subject: Re: [Sipping] New I-D for P-Served-User header

 

Hans,

 

A colleague of mine pointed out sections 6.5.1 and 6.5.2 in TS 23.218, third
bullet:

-               in case the Request-URI changes when visiting an Application
Server, terminate the checking of filter criterias, route the request based
on the changed value of the Request-URI and do not execute the subsequent
steps;

 

In other words, what you describe in your section 3.2 (diversion while
continueing on terminating leg) would not occur for an S-CSCF that follows
the standards

 

Regarding section 3.3: if the AS converts the incoming terminating request
to a new originating request for user B, shouldn't it also update the
P-Asserted-Identity header to reflect the new originating user?

 

Regards,

Jeroen

----- Original Message ----- 

From: Hans Erik van Elburg (RY/ETM)
<mailto:hanserik.van.elburg@ericsson.com>  

To: sipping@ietf.org 

Sent: Tuesday, April 17, 2007 2:11 PM

Subject: [Sipping] New I-D for P-Served-User header

 

I uploaded a new draft for the P-Served-User Private-Header, until it gets
available on the online Internet-Drafts directory you can retrieve it here:

 
<http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user-00
.txt>
http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user-00.
txt 

Abstract

   This document specifies the SIP P-Served-User P-header.  This header
   field addresses an issue that was found in the 3rd-Generation
   Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an
   S-CSCF (Serving Call Session Control Function) and an AS (Application
   Server) on the ISC (IMS Subsystem Service Control) interface to
   convey the identity of the served user and the session case that
   applies to this particular communication session and application
   invocation.

Best Regards, 

/Hans Erik 

 


  _____  


_______________________________________________
Sipping mailing list  https://www1.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


------=_NextPart_000_0037_01C78B15.FFE80BC0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>New I-D for P-Served-User header</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Jeroen,<o:p></o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>P-Asserted-Identity it needs to =
remain the
originator of the call and to use history-info or diversion to pass the
redirector address.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Look at VM redirection or any Call
Forwarding for example.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Adi<o:p></o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Jeroen van
Bemmel [mailto:jbemmel@zonnet.nl] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Sunday, April 29, =
2007 11:46
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Hans Erik van Elburg =
(RY/ETM);
sipping@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [Sipping] =
New I-D for
P-Served-User header</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hans,</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>A colleague of mine pointed out&nbsp;sections 6.5.1
and&nbsp;6.5.2 in TS 23.218, third bullet:</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt'>-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in case the Request-URI changes =
when
visiting an Application Server, terminate the checking of filter =
criterias,
route the request based on the changed value of the Request-URI and do =
not
execute the subsequent steps;</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt'>In other words, what you describe in your =
section 3.2
(diversion while continueing on terminating leg) would not occur for an =
S-CSCF
that follows the&nbsp;standards</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt'>Regarding section 3.3: if the AS converts the =
incoming
terminating request to a new originating request for user B, shouldn't
it&nbsp;also update the P-Asserted-Identity header to reflect the new
originating user?</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt'>Regards,</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt'>Jeroen</span></font><o:p></o:p></p>

</div>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>----- Original Message ----- =
<o:p></o:p></span></font></p>

</div>

<div style=3D'font-color:black'>

<p class=3DMsoNormal style=3D'background:#E4E4E4'><b><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-weight:bold'>From:</span=
></font></b><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> <a
href=3D"mailto:hanserik.van.elburg@ericsson.com"
title=3D"hanserik.van.elburg@ericsson.com">Hans Erik van Elburg =
(RY/ETM)</a> <o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;font-weight:bold'>To:</span></font></b><font size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> <a
href=3D"mailto:sipping@ietf.org" =
title=3D"sipping@ietf.org">sipping@ietf.org</a> =
<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;font-weight:bold'>Sent:</span></font></b><font =
size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> =
Tuesday, April 17,
2007 2:11 PM<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;font-weight:bold'>Subject:</span></font></b><font =
size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> =
[Sipping] New I-D
for P-Served-User header<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<p><font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:maroon'><!-- Converted from text/rtf format -->I
uploaded a new draft for the P-Served-User Private-Header, until it gets
available on the online Internet-Drafts directory you can retrieve it =
here:</span></font><o:p></o:p></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'><a
href=3D"http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serv=
ed-user-00.txt"><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>http://elburg.eln-research.n=
l/drafts/draft-vanelburg-sipping-served-user-00.txt</span></font></a></sp=
an></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> =
</span></font><o:p></o:p></p>

<p><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Abstract<br>
<br>
&nbsp;&nbsp; This document specifies the SIP P-Served-User =
P-header.&nbsp; This
header<br>
&nbsp;&nbsp; field addresses an issue that was found in the =
3rd-Generation<br>
&nbsp;&nbsp; Partnership Project (3GPP) IMS (IP Multimedia Subsystem) =
between
an<br>
&nbsp;&nbsp; S-CSCF (Serving Call Session Control Function) and an AS
(Application<br>
&nbsp;&nbsp; Server) on the ISC (IMS Subsystem Service Control) =
interface to<br>
&nbsp;&nbsp; convey the identity of the served user and the session case =
that<br>
&nbsp;&nbsp; applies to this particular communication session and =
application<br>
&nbsp;&nbsp; invocation.<br>
</span></font><br>
<font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:maroon'>Best Regards,</span></font> <o:p></o:p></p>

<p><b><font size=3D2 color=3Dmaroon face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:maroon;font-weight:bold'>/Hans =
Erik</span></font></b> <o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>_______________________________________________<br>
Sipping mailing list&nbsp; =
https://www1.ietf.org/mailman/listinfo/sipping<br>
This list is for NEW development of the application of SIP<br>
Use sip-implementors@cs.columbia.edu for questions on current sip<br>
Use sip@ietf.org for new developments of core =
SIP<o:p></o:p></span></font></p>

</blockquote>

</div>

</body>

</html>

------=_NextPart_000_0037_01C78B15.FFE80BC0--




--===============1382201062==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============1382201062==--






From sipping-bounces@ietf.org Mon Apr 30 09:40:31 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HiW75-0002aV-AK; Mon, 30 Apr 2007 09:40:23 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HiW72-0002aQ-Uo for sipping-confirm+ok@megatron.ietf.org;
	Mon, 30 Apr 2007 09:40:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HiW72-0002aI-GZ
	for sipping@ietf.org; Mon, 30 Apr 2007 09:40:20 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HiW71-0002Ac-Cy
	for sipping@ietf.org; Mon, 30 Apr 2007 09:40:20 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B843B2074F; Mon, 30 Apr 2007 15:40:18 +0200 (CEST)
X-AuditID: c1b4fb3c-a94ecbb0000073d5-45-4635f1c2d8f8 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9D6E720572; Mon, 30 Apr 2007 15:40:18 +0200 (CEST)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 30 Apr 2007 15:40:18 +0200
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
Subject: RE: [Sipping] b2bua and cc-transfer
Date: Mon, 30 Apr 2007 15:40:28 +0200
Message-ID: <C0E80510684FE94DBDE3A4AF6B968D2D0115459E@esealmw118.eemea.ericsson.se>
In-Reply-To: <46325571.3060309@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] b2bua and cc-transfer
Thread-Index: AceJBip58RhryYRdQ4qRlP8W7rYeyQCIu9JA
From: "Ian Elz \(CV/ETL\)" <ian.elz@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Xavier Marjou" <xavier.marjou@orange-ftgroup.com>
X-OriginalArrivalTime: 30 Apr 2007 13:40:18.0535 (UTC)
	FILETIME=[1760AF70:01C78B2D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 343d06d914165ffd9d590a64755216ca
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Paul, Xavier,

I have been looking at this in a little more detail and have drawn a
couple of example flows with and without b2buas.

The appear to show the following requirements:

1. b2buas MUST map the Contact header

2. when sending a Replaces header the UA MUST use the contact of the
dialog being replaced as the URI.=20

i.e. For a REFER where the Refer-To is used with a Replaces parameter
header the Refer-to URI must be the Contact for the dialog being
replaced; in an INVITE Replaces the Request URI must be the Contact of
the dialog being replaced.

This will ensure that each b2bua will receive the new request based upon
the contact information they have inserted. This then allows them to map
the other headers as required (this could apply to Target-Dialog as well
as Replaces).

In addition to the requirements above the b2bua must be able to
recognise the call with a Request URI and be able to look for the fields
which need to be mapped that that is an implementation detail not a
protocol one.

I have checked the transfer draft (draft-ietf-sipping-cc-transfer-07)
and it shows the Contact being used in the REFER-To and Subsequent
INVITE in the consultation transfer example. RFC 3891 does not show this
however as it only shows one example without all of the message details.

The examples I have used are as follows:=20

A simple transfer example, no b2bua.

Figure 1

+-----+             +------+                   +-----+
|UA -A|             | UA-B |                   |UB-C |
+-----+             +------+                   +-----+
         INVITE B
  --------------------->
    200 OK Contact B'
  <---------------------
         ACK
  --------------------->
 dialog established (D1)
........................
                     INVITE C
  ------------------------------------------------>
                     200 OK Contact C'
  <-----------------------------------------------
                     ACK
  ------------------------------------------------>
               dialog established (D2)
...................................................

    REFER B Refer-to: C'
       Replaces D2
  --------------------->
        202
  <---------------------

                           INVITE C' Replaces D2
                         ------------------------->
                              200 OK
                         <-------------------------
                               ACK
                         ------------------------->
                            dialog established (D3)
                         ..........................

This should work OK.

If there is a B2BUA in the path of the dialog to be replaced and the
b2bua maps the contact as well as the Replaces value(s).

Figure 2

+-----+             +------+           +------+            +-----+
|UA -A|             | UA-B |           |b2bua |            |UB-C |
+-----+             +------+           +------+            +-----+
                                     maps: call-id
                                           Contact
         INVITE B
  --------------------->
     200 OK Contact B'
  <---------------------
         ACK
  --------------------->
 dialog established (D1)
........................
                     INVITE C                 INVITE C
  ---------------------------------------> ------------------>
                200 OK  Contact X'          200 OK  Contact C'
  <--------------------------------------- <------------------
                     ACK
  ---------------------------------------> ------------------>
               dialog established (D2)     dialog  (D3)
.......................................... ...................

     REFER B Refer-to: X'
       Replaces D2
  --------------------->
        202
  <---------------------

                         INVITE X' Replaces D2
                         --------------->
                                            INVITE C' Replaces D3
                                            ------------------>   =20
=20
This will work OK as the Refer-To URI is the Contact and the B2BUA and
mapped the Contact.

If the Contact is not mapped at the B2BUA the following will occur.

Figure 3

+-----+             +------+           +------+            +-----+
|UA -A|             | UA-B |           |b2bua |            |UB-C |
+-----+             +------+           +------+            +-----+
                                     maps: call-id
           INVITE B
  --------------------->
     200 OK Contact B'
  <---------------------
         ACK
  --------------------->
 dialog established (D1)
........................
                     INVITE C
  ---------------------------------------> ------------------>
                200 OK  Contact C'          200 OK  Contact C'
  <--------------------------------------- <------------------
                     ACK
  ---------------------------------------> ------------------>
               dialog established (D2)     dialog  (D3)
.......................................... ...................

     REFER B Refer-to: C'
       Replaces D2
  --------------------->
        202
  <---------------------

                               INVITE C' Replaces D2
                         ------------------------------------>
                                           =20
                            =20
This will fail as C will reject the INVITE as the dialog D2 cannot be
matched. To ensure that the sequence works there needs to be a mechanism
to ensure that the INVITE Replaces is passed to the B2BUA which was in
the original dialog so that the correct mapping occurs.

Ian Elz

Office: + 44 24 764 35256
gsm: +44 7801723668
ian.elz@ericsson.com


-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
Sent: 27 April 2007 20:57
To: Xavier Marjou
Cc: Ian Elz (CV/ETL); sipping@ietf.org
Subject: Re: [Sipping] b2bua and cc-transfer

Xavier,

Thanks for reorganizing this. I agree with you that there have been
*some* works on B2BUAs, and maybe it is time for some further work on
topics such as this. I definitely think such work should be addressed as
additional clarification on B2BUA behavior, rather than rules for
everybody else so that they may work around what a B2BUA might do to
them.

However I don't think it is possible to provide guidelines for this kind
of behavior for B2BUAs in general, because the concept of B2BUA is too
general. There can be many kinds of B2BUA, and not all should behave in
the same way. For instance, an SBC and a conference focus are both
B2BUAs. But the way they handle a REFER is likely to be quite different.

In most cases when people ask questions about B2BUAs they are assuming
the B2BUA acts much like a proxy, as an SBC typically does. So it might
be worthwhile to focus on that kind initially.

	Paul

Xavier Marjou wrote:
> I renamed the thread, as I think that this topic should be left out of

> the draft-ietf-sipping-cc-transfer-07. Such a b2bua topic may affect=20
> any SIP-related draft or RFC.
>=20
>=20
>> So far we have never specified how B2BUAs should work.
>=20
> Indeed: the draft-ietf-sipping-sbc-funcs looks at some b2buas in order

> to investigate some missing functions in SIP. The=20
> draft-marjou-sipping-b2bua is an individual draft, which means that it

> is not an IETF working item. This later draft tries to catch best=20
> practices about some type of B2BUA (the so-called transparent B2BUA
> type) because many of them exist in the nature and because there is no

> existing document on this topic. To sum-up, the situation with SIP and

> B2BUA is very similar to the situation with SIP-RTP and NAT: NATs make

> life harder for everybody and solutions to cope with them are not=20
> easy.
>=20
>> Since the B2BUA has decided to interfere in the call, it has the=20
>> obligation to fix up the problems it has caused.
> I agree with Paul.
>=20
> For the following call-flows, a B2BUA may be located in different=20
> places. I think it is important to look for which UA the B2BUA is=20
> acting for. (cf 3 examples below for the following regular call-flow).
> I would say that if someone deploys a B2BUA acting on the behalf of a=20
> UA, he needs to make sure that the B2BUA is in the path of all SIP=20
> flows for this UA and that the B2BUA will also correct the discrepancy

> it introduces (I know this is heavy, but I do not see any other=20
> solutions).
>=20
> Cheers,
> Xavier
>=20
> transferor(b)             transfereree(a)               t-target(c)
> |                                |                                |
> |                                |                                |
> | INV d1                         |                                |
> |<-------------------------------|                                |
> | INV d2                                                          |
> |---------------------------------------------------------------->|
> | REF dx Replaces:d2             |                                |
> |------------------------------->|                                |
> |                                |INV d3 Rpl:d2                   |
> |                                |------------------------------->|
>=20
>=20
> transferor(b)             transfereree(a)    b2bua_c    t-target(c)
> |                                |               ||               |
> |                                |               ||               |
> | INV d1                         |               ||               |
> |<-------------------------------|               ||               |
> | INV d2                                         || INV d2'       |
> |------------------------------------------------||-------------->|
> | REF dx Replaces:d2             |                                |
> |------------------------------->|                                |
> |                                |INV d3 Rpl:d2  || INV d3'Rpl:d2'|
> |                                |---------------||-------------->|
>=20
>=20
> transferor(b)  b2bua_a    transfereree(a)    b2bua_a    t-target(c)
> |               ||               |                                |
> |               ||               |                                |
> | INV d1'       || INV d1        |                                |
> |<--------------||---------------|                                |
> | INV d2                                                          |
> |---------------------------------------------------------------->|
> | REF dx  Rpl:d2                 |                                |
> |------------------------------->|                                |
> |                                |INV d3 Rpl:d2  || INV d3'Rpl:d2 |
> |                                |---------------||-------------->|
>=20
>=20
> transferor(b)  b2bua_b    transfereree(a)               t-target(c)
> |               ||               |                                |
> |               ||               |                                |
> | INV d1'       || INV d1        |                                |
> |<--------------||---------------|                                |
> | INV d2        || INV d2'                                        |
> |---------------||----------------------------------------------->|
> | REF dx  Rpl:d2|| REF dx' Rpl:d2'                                |
> |---------------||-------------->|                                |
> |                                |INV d3 Rpl:d2'                  |
> |                                |------------------------------->|
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use=20
> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> sip@ietf.org for new developments of core SIP
>=20


_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 30 10:13:07 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HiWcg-0003bG-6I; Mon, 30 Apr 2007 10:13:02 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HiWce-0003bB-M2 for sipping-confirm+ok@megatron.ietf.org;
	Mon, 30 Apr 2007 10:13:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HiWce-0003b3-C4
	for sipping@ietf.org; Mon, 30 Apr 2007 10:13:00 -0400
Received: from smtp7.bbsi.ca ([207.229.55.133] helo=smtp.bbsconnect.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HiWcd-0004k9-U3
	for sipping@ietf.org; Mon, 30 Apr 2007 10:13:00 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] b2bua and cc-transfer
Date: Mon, 30 Apr 2007 08:12:58 -0600
Message-ID: <D6DDE2706695D34F8263D17DD29606D99129D7@BBSC-EX01.bbsconnect.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: [Sipping] b2bua and cc-transfer
Thread-Index: AceLMaegjHm0p3gdTy+DmyNDeuAxGg==
From: "Peter Musgrave" <PMusgrave@newheights.com>
To: <pkyzivat@cisco.com>, <xavier.marjou@orange-ftgroup.com>,
	<ian.elz@ericsson.coms>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7c1a129dc3801d79d40c5ca8dee767eb
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0878524749=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0878524749==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78B31.7CF685F9"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C78B31.7CF685F9
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,=20

=20

In addition to mapping the Call Id and the contact header, the B2B will
need to map the to-tag and from-tag information in the Replaces header.=20

=20

According to RFC3891 Section 3:

The User Agent Server

(UAS) matches the to-tag and from-tag parameters as if they were tags
present in an incoming request.  In other words, the to-tag parameter is
compared to the local tag, and the from-tag parameter is compared to the
remote tag.

=20

This introduces an additional wrinkle.=20

=20

+-----+             +------+           +------+            +-----+

|UA -A|             | UA-B |           |b2bua |            |UB-C |

+-----+             +------+           +------+            +-----+

                                     maps: call-id

                                           Contact

=20

Assume C calls B and establishes a dialog. B then calls A and sends A a
REFER to C with a Replaces telling it to replace the dialog C has with
B. So the B2B must adjust the call id, and ensure that the to-tag in the
resulting INVITE with replaces matches the local tag provided by C in
it's initial call to B (i.e. the tag in the From header).=20

=20

The other scenario is as above but when the initial call is caused by B
calling C. In this case C's local tag will be in the To: header. When
the transfer occurs and an INVITE with replaces goes through to C, the
B2B now needs to ensure the to-tag value comes from the To: header in
the initial dialog.=20

=20

As long as the B2B keeps track of "local" and "remote" tags for each
dialog, this mapping should be fairly straight-forward.=20

=20

Peter

=20


------_=_NextPart_001_01C78B31.7CF685F9
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi all, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In addition to mapping the Call Id and the contact =
header,
the B2B will need to map the to-tag and from-tag information in the =
Replaces
header. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>According to RFC3891 Section =
3:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>The User Agent =
Server<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>(UAS) matches the =
to-tag and
from-tag parameters as if they were tags present in an incoming =
request.&nbsp;
In other words, the to-tag parameter is compared to the local tag, and =
the
from-tag parameter is compared to the remote =
tag.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>This introduces an =
additional
wrinkle. <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>+-----+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
+------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
+-----+<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>|UA
-A|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; |
UA-B |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|b2bua
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|UB-C |<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>+-----+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
+------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
+-----+<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
maps: call-id<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;Contact<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;<o:p></o:p></span></fo=
nt></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Assume C calls B and =
establishes a
dialog. B then calls A and sends A a REFER to C with a Replaces telling =
it to
replace the dialog C has with B. So the B2B must adjust the call id, and =
ensure
that the to-tag in the resulting INVITE with replaces matches the local =
tag
provided by C in it&#8217;s initial call to B (i.e. the tag in the From
header). <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>The other scenario is as =
above but
when the initial call is caused by B calling C. In this case C&#8217;s =
local
tag will be in the To: header. When the transfer occurs and an INVITE =
with
replaces goes through to C, the B2B now needs to ensure the to-tag value =
comes
from the To: header in the initial dialog. <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>As long as the B2B keeps =
track of &#8220;local&#8221;
and &#8220;remote&#8221; tags for each dialog, this mapping should be =
fairly
straight-forward. <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Peter<o:p></o:p></span></fon=
t></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C78B31.7CF685F9--



--===============0878524749==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0878524749==--





From sipping-bounces@ietf.org Mon Apr 30 15:38:07 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hibh7-00050e-94; Mon, 30 Apr 2007 15:37:57 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hibh5-00050X-Pe for sipping-confirm+ok@megatron.ietf.org;
	Mon, 30 Apr 2007 15:37:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hibh5-00050P-FR
	for sipping@ietf.org; Mon, 30 Apr 2007 15:37:55 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hibh2-0001iu-9c
	for sipping@ietf.org; Mon, 30 Apr 2007 15:37:55 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	50CD020163; Mon, 30 Apr 2007 21:37:51 +0200 (CEST)
X-AuditID: c1b4fb3e-ad1e9bb0000061ca-65-4636458f9d26 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2F51820085; Mon, 30 Apr 2007 21:37:51 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 30 Apr 2007 21:37:51 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] New I-D for P-Served-User header
Date: Mon, 30 Apr 2007 21:37:50 +0200
Message-ID: <CAC481363DB73049924DDDCFC1AC60A6044F83EA@esealmw109.eemea.ericsson.se>
In-Reply-To: <01f901c78a9f$71022e70$0601a8c0@BEMBUSTER>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] New I-D for P-Served-User header
Thread-Index: AceKn6IpI/wPT+JRTSeNh5zSPGDGBAAvW5DA
From: "Hans Erik van Elburg \(RY/ETM\)" <hanserik.van.elburg@ericsson.com>
To: "Jeroen van Bemmel" <jbemmel@zonnet.nl>,
	<sipping@ietf.org>
X-OriginalArrivalTime: 30 Apr 2007 19:37:51.0086 (UTC)
	FILETIME=[0A1830E0:01C78B5F]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a0ecb232550b38fd41a3cf6a312fbabc
Cc: 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0862878098=="
Errors-To: sipping-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0862878098==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78B5F.09CE7832"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C78B5F.09CE7832
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Jeroen,
=20
When a call is forwarded the originator of the call does not change,
therefore it is required that the P-Asserted-Identity remains the same.
=20
Regarding your other comment, it is true that it is not possible now as
this scenario was not envisioned in 3GPP, when th e procedures where
written. The P-Served-User header makes it possible, but still there are
changes required to the 3GPP procedures. You spotted one place. What we
need to do is make these changes in a backward compatible manner. For
example when the P-Served-User header is not included, the existing
behaviour prevails.=20
=20
So the scenario is kind of a what-if, then what is needed to make it
work. I got similar commments before and I added a note to section 3.2
clarifying this:
http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user
-01-presubmission-rev2.txt
=20
Best Regards,
=20
/Hans Erik


________________________________

From: Jeroen van Bemmel [mailto:jbemmel@zonnet.nl]=20
Sent: Sunday, April 29, 2007 10:46 PM
To: Hans Erik van Elburg (RY/ETM); sipping@ietf.org
Subject: Re: [Sipping] New I-D for P-Served-User header


Hans,
=20
A colleague of mine pointed out sections 6.5.1 and 6.5.2 in TS 23.218,
third bullet:
-     in case the Request-URI changes when visiting an Application
Server, terminate the checking of filter criterias, route the request
based on the changed value of the Request-URI and do not execute the
subsequent steps;
=20
In other words, what you describe in your section 3.2 (diversion while
continueing on terminating leg) would not occur for an S-CSCF that
follows the standards
=20
Regarding section 3.3: if the AS converts the incoming terminating
request to a new originating request for user B, shouldn't it also
update the P-Asserted-Identity header to reflect the new originating
user?
=20
Regards,
Jeroen

	----- Original Message -----=20
	From: Hans Erik van Elburg (RY/ETM)
<mailto:hanserik.van.elburg@ericsson.com> =20
	To: sipping@ietf.org=20
	Sent: Tuesday, April 17, 2007 2:11 PM
	Subject: [Sipping] New I-D for P-Served-User header


	I uploaded a new draft for the P-Served-User Private-Header,
until it gets available on the online Internet-Drafts directory you can
retrieve it here:

=09
http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user
-00.txt
<http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-use
r-00.txt> =20

	Abstract
=09
	   This document specifies the SIP P-Served-User P-header.  This
header
	   field addresses an issue that was found in the 3rd-Generation
	   Partnership Project (3GPP) IMS (IP Multimedia Subsystem)
between an
	   S-CSCF (Serving Call Session Control Function) and an AS
(Application
	   Server) on the ISC (IMS Subsystem Service Control) interface
to
	   convey the identity of the served user and the session case
that
	   applies to this particular communication session and
application
	   invocation.
=09
	Best Regards,=20

	/Hans Erik=20


=09
________________________________


=09

	_______________________________________________
	Sipping mailing list
https://www1.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


------_=_NextPart_001_01C78B5F.09CE7832
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>New I-D for P-Served-User header</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1589" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D737422319-30042007><FONT face=3DArial color=3D#800000 =
size=3D2>Hi=20
Jeroen,</FONT></SPAN></DIV>
<DIV><SPAN class=3D737422319-30042007><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D737422319-30042007><FONT face=3DArial color=3D#800000 =
size=3D2>When a=20
call is forwarded the originator of the call does not change, therefore =
it is=20
required that the P-Asserted-Identity&nbsp;remains the =
same.</FONT></SPAN></DIV>
<DIV><SPAN class=3D737422319-30042007><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D737422319-30042007><FONT face=3DArial color=3D#800000 =

size=3D2>Regarding your other comment, it is true =
that&nbsp;</FONT></SPAN><SPAN=20
class=3D737422319-30042007><FONT face=3DArial color=3D#800000 =
size=3D2><SPAN=20
class=3D765050716-19042007>it is not possible now as this scenario was =
not=20
envisioned in 3GPP, when th e procedures where written. =
</SPAN></FONT><FONT=20
face=3DArial color=3D#800000 size=3D2><SPAN =
class=3D765050716-19042007>The P-Served-User=20
header makes it possible, but still there are changes required to the =
3GPP=20
procedures. You spotted one place. What we need to do is make these =
changes in a=20
backward compatible manner. For example when the P-Served-User header is =
not=20
included, the existing behaviour prevails. </SPAN></FONT></DIV>
<DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D765050716-19042007></SPAN></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D765050716-19042007><FONT face=3DArial><FONT =
color=3D#800000><FONT=20
size=3D2>So the scenario is kind of a what-if, then&nbsp;what is needed =
to make it=20
work.<SPAN class=3D737422319-30042007> I got similar commments before =
and I added=20
a note to section 3.2 clarifying =
this:</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D765050716-19042007><FONT face=3DArial><FONT =
color=3D#800000><FONT=20
size=3D2><SPAN class=3D737422319-30042007><A=20
href=3D"http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serv=
ed-user-01-presubmission-rev2.txt">http://elburg.eln-research.nl/drafts/d=
raft-vanelburg-sipping-served-user-01-presubmission-rev2.txt</A></SPAN></=
FONT></FONT></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D765050716-19042007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN =
class=3D765050716-19042007><SPAN=20
class=3D737422319-30042007>Best Regards,</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D765050716-19042007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN =
class=3D765050716-19042007>/Hans=20
Erik</SPAN></FONT></DIV></SPAN></DIV><FONT face=3DArial color=3D#800000=20
size=3D2></FONT><FONT face=3DArial color=3D#800000 size=3D2></FONT><FONT =
face=3DArial=20
color=3D#800000 size=3D2></FONT><FONT face=3DArial color=3D#800000 =
size=3D2></FONT><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Jeroen van Bemmel=20
[mailto:jbemmel@zonnet.nl] <BR><B>Sent:</B> Sunday, April 29, 2007 10:46 =

PM<BR><B>To:</B> Hans Erik van Elburg (RY/ETM);=20
sipping@ietf.org<BR><B>Subject:</B> Re: [Sipping] New I-D for =
P-Served-User=20
header<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=3DArial size=3D2>Hans,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>A colleague of mine pointed =
out&nbsp;sections 6.5.1=20
and&nbsp;6.5.2 in TS 23.218, third bullet:</FONT></DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2>-<SPAN=20
style=3D"mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>in case the =
Request-URI=20
changes when visiting an Application Server, terminate the checking of =
filter=20
criterias, route the request based on the changed value of the =
Request-URI and=20
do not execute the subsequent steps;</FONT></SPAN></DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2>In other words, what you describe =
in your=20
section 3.2 (diversion while continueing on terminating leg) would not =
occur for=20
an S-CSCF that follows the&nbsp;standards</FONT></SPAN></DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2></FONT></SPAN><SPAN =
lang=3DEN-GB><FONT=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2>Regarding section 3.3: if the AS =
converts the=20
incoming terminating request to a new originating request for user B, =
shouldn't=20
it&nbsp;also update the P-Asserted-Identity header to reflect the new=20
originating user?</FONT></SPAN></DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN lang=3DEN-GB><FONT size=3D2>Jeroen</FONT></SPAN></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dhanserik.van.elburg@ericsson.com=20
  href=3D"mailto:hanserik.van.elburg@ericsson.com">Hans Erik van Elburg=20
  (RY/ETM)</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dsipping@ietf.org =

  href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, April 17, 2007 =
2:11=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Sipping] New I-D for=20
  P-Served-User header</DIV>
  <DIV><BR></DIV><!-- Converted from text/rtf format -->
  <P><FONT face=3DArial color=3D#800000 size=3D2>I uploaded a new draft =
for the=20
  P-Served-User Private-Header, until it gets available on the online=20
  Internet-Drafts directory you can retrieve it here:</FONT></P>
  <P><A=20
  =
href=3D"http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-serv=
ed-user-00.txt"><U></U><U><FONT=20
  face=3DArial color=3D#0000ff=20
  =
size=3D2>http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-ser=
ved-user-00.txt</FONT></U></A><FONT=20
  face=3DArial size=3D2> </FONT></P>
  <P><FONT face=3D"Courier New" size=3D2>Abstract<BR><BR>&nbsp;&nbsp; =
This document=20
  specifies the SIP P-Served-User P-header.&nbsp; This =
header<BR>&nbsp;&nbsp;=20
  field addresses an issue that was found in the =
3rd-Generation<BR>&nbsp;&nbsp;=20
  Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between=20
  an<BR>&nbsp;&nbsp; S-CSCF (Serving Call Session Control Function) and =
an AS=20
  (Application<BR>&nbsp;&nbsp; Server) on the ISC (IMS Subsystem Service =

  Control) interface to<BR>&nbsp;&nbsp; convey the identity of the =
served user=20
  and the session case that<BR>&nbsp;&nbsp; applies to this particular=20
  communication session and application<BR>&nbsp;&nbsp;=20
  invocation.<BR></FONT><BR><FONT face=3DArial color=3D#800000 =
size=3D2>Best=20
  Regards,</FONT> </P>
  <P><B><FONT face=3DArial color=3D#800000 size=3D2>/Hans =
Erik</FONT></B> </P><BR>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>Sipping =
mailing=20
  list&nbsp; https://www1.ietf.org/mailman/listinfo/sipping<BR>This list =
is for=20
  NEW development of the application of SIP<BR>Use=20
  sip-implementors@cs.columbia.edu for questions on current sip<BR>Use=20
  sip@ietf.org for new developments of core =
SIP</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C78B5F.09CE7832--



--===============0862878098==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0862878098==--





From sipping-bounces@ietf.org Mon Apr 30 16:19:47 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HicLZ-0001qS-P4; Mon, 30 Apr 2007 16:19:45 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1HicLY-0001qN-UQ for sipping-confirm+ok@megatron.ietf.org;
	Mon, 30 Apr 2007 16:19:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HicLY-0001q9-K9
	for sipping@ietf.org; Mon, 30 Apr 2007 16:19:44 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HicLX-0003Fq-C4
	for sipping@ietf.org; Mon, 30 Apr 2007 16:19:44 -0400
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l3UKJeJ08802; Mon, 30 Apr 2007 20:19:40 GMT
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: Mon, 30 Apr 2007 15:19:39 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB16E79803@zrc2hxm1.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC: draft-ietf-sipping-overload-reqs-00
Thread-Index: AceLZOENJTeZ6L0FQ3aUWR7ePudi3g==
From: "Mary Barnes" <mary.barnes@nortel.com>
To: <sipping@ietf.org>
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: gonzalo.camarillo@ericsson.com
Subject: [Sipping] WGLC: draft-ietf-sipping-overload-reqs-00
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi all,

This is to announce Working Group Last Call on the following document:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-overload-reqs-00.
txt

This WGLC will end on 21 May 2007.

There were a few comments on this document already that can be
incorporated with last call comments, but we would like 3 volunteers to
commit to reviewing the document in detail.  If interested, please let
us know. =20

As always, anyone else that gets a chance to review should also send
their feedback to the authors and copy the SIPPING mailing list. =20

Thanks,=20
Mary=20
SIPPING WG co-chair




_______________________________________________
Sipping mailing list  https://www1.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



From sipping-bounces@ietf.org Mon Apr 30 21:06:34 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Higp5-0007cv-N5; Mon, 30 Apr 2007 21:06:31 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Higp3-0007cq-IG for sipping-confirm+ok@megatron.ietf.org;
	Mon, 30 Apr 2007 21:06:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Higp3-0007ci-8Q
	for sipping@ietf.org; Mon, 30 Apr 2007 21:06:29 -0400
Received: from py-out-1112.google.com ([64.233.166.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Higp1-0007bw-MM
	for sipping@ietf.org; Mon, 30 Apr 2007 21:06:29 -0400
Received: by py-out-1112.google.com with SMTP id f31so1506455pyh
	for <sipping@ietf.org>; Mon, 30 Apr 2007 18:06:27 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	b=rm39KWfw2Nudsar7OuQ9pDZjF4tBNdrvAAOZ0q56dPoN+Z8cQ9014A/2xdpEivuvVWegRb8xFatObil5m6z4hka3q9S/fFVHl434hgUc+bBPRlFVPJPUgjvX75R0jQL8EWUpSeBoSdkF8V+GzcJjmRMJZzZbNgcwQ71jG+fd5tg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=YeGubaxmy9wvZYuFk2GkyXD5lTDlqCUXe+VpT1XFd3cj+Wzud96KlUiAA1g37HX0pufLP64K8LnBcYXDVYb5bpNegZVdqybHSGXU7+930gT/vgQ0yRpDoWJpMQnZGOikrMo1v2hZU3odE535f1bNzkJL2eg2iQ4RH/yFMRTc3iA=
Received: by 10.35.66.1 with SMTP id t1mr12369291pyk.1177981586369;
	Mon, 30 Apr 2007 18:06:26 -0700 (PDT)
Received: by 10.35.88.14 with HTTP; Mon, 30 Apr 2007 18:06:26 -0700 (PDT)
Message-ID: <5c5981350704301806r44243f4dy617649ea2c8d762d@mail.gmail.com>
Date: Mon, 30 Apr 2007 18:06:26 -0700
From: "Mohsen Soroushnejad" <msoroush@gmail.com>
To: sipping@ietf.org
Subject: Re: [Sipping] New I-D for P-Served-User header
MIME-Version: 1.0
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0094275893=="
Errors-To: sipping-bounces@ietf.org

--===============0094275893==
Content-Type: multipart/alternative; 
	boundary="----=_Part_163583_30729920.1177981586299"

------=_Part_163583_30729920.1177981586299
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

This discussion may be more relevant on a 3GPP/IMS mailing list.....having
said that:

I believe the intent of this draft (at least one of them) is to facilitate
to fill a "big" hole
in the IMS technical specs w.r.t. support for advanced features by
application servers.

The generic use case is:

1) A calls B (B is IMS subscriber or service PSI).
2) Request is routed to AS and a session is established.
3) AS initiates a request to a new destination C and requires to preserve
the identity of A
4) If you're adhering to the present IMS specs, you're stuck!

There are many advanced telephony-based features that fall into this
framework. Among them:

- "dial-out" services (e.g., calling out from a UM server or a voice portal
application)
-  call center automatic call distributions
-  find me/follow type me services


At present, many IMS vendors either have a "proprietary" solution to
this "standard gap" or have not yet realized (or deny:-) ) that there exists
a gap.


Regards,
Mohsen Soroush


--------------------------------------------------------------------------------------------
 Re: [Sipping] New I-D for P-Served-User header
------------------------------

   - *To*: "Hans Erik van Elburg \(RY/ETM\)" <hanserik.van.elburg at
   ericsson.com <hanserik.van.elburg@DOMAIN.HIDDEN>>, <sipping at
   ietf.org <sipping@DOMAIN.HIDDEN>>
   - *Subject*: Re: [Sipping] New I-D for P-Served-User header
   - *From*: "Jeroen van Bemmel" <jbemmel at zonnet.nl<jbemmel@DOMAIN.HIDDEN>>

   - *Date*: Sun, 29 Apr 2007 22:46:20 +0200
   - *Cc*:
   - *List-help*:
<mailto:sipping-request@ietf.org?subject=help<sipping-request@ietf.org?subject=help>>

   - *List-id*: "SIPPING Working Group \(applications of SIP\)" <
   sipping.ietf.org>
   - *List-post*: <mailto:sipping@ietf.org <sipping@ietf.org>>
   - *List-subscribe*: <https://www1.ietf.org/mailman/listinfo/sipping>,
   <mailto:sipping-request@ietf.org?subject=subscribe
   <sipping-request@ietf.org?subject=subscribe>>
   - *List-unsubscribe*: <https://www1.ietf.org/mailman/listinfo/sipping>,
   <mailto:sipping-request@ietf.org?subject=unsubscribe
   <sipping-request@ietf.org?subject=unsubscribe>>
   - *References*: <
   CAC481363DB73049924DDDCFC1AC60A6044F8339@esealmw109.eemea.ericsson.se<http://www1.ietf.org/mail-archive/web/sipping/current/msg13556.html>>


------------------------------
Title: *New I-D for P-Served-User header*   Hans,

A colleague of mine pointed out sections 6.5.1 and 6.5.2 in TS 23.218, third
bullet:
-     in case the Request-URI changes when visiting an Application Server,
terminate the checking of filter criterias, route the request based on the
changed value of the Request-URI and do not execute the subsequent steps;

In other words, what you describe in your section 3.2 (diversion while
continueing on terminating leg) would not occur for an S-CSCF that follows
the standards

Regarding section 3.3: if the AS converts the incoming terminating request
to a new originating request for user B, shouldn't it also update the
P-Asserted-Identity header to reflect the new originating user?

Regards,
Jeroen

----- Original Message -----
*From:* Hans Erik van Elburg (RY/ETM)<hanserik.van.elburg%20at%20ericsson.com>
*To:* sipping at ietf.org <sipping%20at%20ietf.org>
*Sent:* Tuesday, April 17, 2007 2:11 PM
*Subject:* [Sipping] New I-D for P-Served-User header



I uploaded a new draft for the P-Served-User Private-Header, until it gets
available on the online Internet-Drafts directory you can retrieve it here:

***http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user-00.txt
*<http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user-00.txt>

Abstract

   This document specifies the SIP P-Served-User P-header.  This header
   field addresses an issue that was found in the 3rd-Generation
   Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an
   S-CSCF (Serving Call Session Control Function) and an AS (Application
   Server) on the ISC (IMS Subsystem Service Control) interface to
   convey the identity of the served user and the session case that
   applies to this particular communication session and application
   invocation.

Best Regards,

*/Hans Erik*

 ------------------------------

_______________________________________________

------=_Part_163583_30729920.1177981586299
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>This discussion may be more relevant on a 3GPP/IMS mailing list.....having said that:</div>
<div>&nbsp;</div>
<div>I believe the intent of this draft (at least one of them) is to facilitate to fill a &quot;big&quot; hole</div>
<div>in the IMS technical specs w.r.t. support for advanced features by application servers.</div>
<div>&nbsp;</div>
<div>The generic use case is:</div>
<div>&nbsp;</div>
<div>1) A calls B (B is IMS subscriber or service PSI).</div>
<div>2) Request is routed to AS and a session is established.</div>
<div>3) AS initiates a request to a new destination C&nbsp;and requires to preserve the identity of A</div>
<div>4) If you&#39;re adhering to the present IMS specs, you&#39;re stuck!</div>
<div>&nbsp;</div>
<div>There are many advanced telephony-based features that fall into this framework. Among them:</div>
<div>&nbsp;</div>
<div>-&nbsp;&quot;dial-out&quot; services (e.g., calling out from a UM server or a voice portal application)</div>
<div>-&nbsp; call center automatic call distributions</div>
<div>-&nbsp; find me/follow type me services</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>At present,&nbsp;many IMS vendors either have a &quot;proprietary&quot; solution to this&nbsp;&quot;standard gap&quot;&nbsp;or have not yet realized (or deny:-) ) that there exists a gap.</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>Regards,</div>
<div>Mohsen Soroush</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>--------------------------------------------------------------------------------------------</div>
<div>
<h1>Re: [Sipping] New I-D for P-Served-User header</h1>
<hr>

<ul>
<li><em>To</em>: &quot;Hans Erik van Elburg \(RY/ETM\)&quot; &lt;<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:hanserik.van.elburg@DOMAIN.HIDDEN" target="_blank">hanserik.van.elburg at ericsson.com
</a>&gt;, &lt;<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sipping@DOMAIN.HIDDEN" target="_blank">sipping at ietf.org </a>&gt; 
<li><em>Subject</em>: Re: [Sipping] New I-D for P-Served-User header 
<li><em>From</em>: &quot;Jeroen van Bemmel&quot; &lt;<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:jbemmel@DOMAIN.HIDDEN" target="_blank">jbemmel at zonnet.nl</a>&gt; 
<li><em>Date</em>: Sun, 29 Apr 2007 22:46:20 +0200 
<li><em>Cc</em>: 
<li><em>List-help</em>: &lt;<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sipping-request@ietf.org?subject=help" target="_blank">mailto:sipping-request@ietf.org?subject=help</a>&gt; 
<li><em>List-id</em>: &quot;SIPPING Working Group \(applications of SIP\)&quot; &lt;<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://sipping.ietf.org/" target="_blank">sipping.ietf.org</a>&gt; 
<li><em>List-post</em>: &lt;<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sipping@ietf.org" target="_blank">mailto:sipping@ietf.org</a>&gt; 
<li><em>List-subscribe</em>: &lt;<a onclick="return top.js.OpenExtLink(window,event,this)" href="https://www1.ietf.org/mailman/listinfo/sipping" target="_blank">https://www1.ietf.org/mailman/listinfo/sipping</a>&gt;, &lt;
<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sipping-request@ietf.org?subject=subscribe" target="_blank">mailto:sipping-request@ietf.org?subject=subscribe </a>&gt; 
<li><em>List-unsubscribe</em>: &lt;<a onclick="return top.js.OpenExtLink(window,event,this)" href="https://www1.ietf.org/mailman/listinfo/sipping" target="_blank">https://www1.ietf.org/mailman/listinfo/sipping</a>&gt;, &lt;
<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sipping-request@ietf.org?subject=unsubscribe" target="_blank">mailto:sipping-request@ietf.org?subject=unsubscribe </a>&gt; 
<li><em>References</em>: &lt;<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www1.ietf.org/mail-archive/web/sipping/current/msg13556.html" target="_blank">CAC481363DB73049924DDDCFC1AC60A6044F8339@esealmw109.eemea.ericsson.se
</a>&gt; </li></li></li></li></li></li></li></li></li></li></li></ul>
<hr>

<address>Title: <strong>New I-D for P-Served-User header</strong></address>
<table width="100%">
<tbody>
<tr>
<td style="BACKGROUND-COLOR: #ffffff" bgcolor="#ffffff">
<div><font face="Arial" size="2">Hans,</font></div>
<div><font face="Arial" size="2"></font>&nbsp;</div>
<div><font face="Arial" size="2">A colleague of mine pointed out&nbsp;sections 6.5.1 and&nbsp;6.5.2 in TS 23.218, third bullet:</font></div>
<div><span lang="EN-GB"><font size="2">-<span>&nbsp;&nbsp;&nbsp;&nbsp; </span>in case the Request-URI changes when visiting an Application Server, terminate the checking of filter criterias, route the request based on the changed value of the Request-URI and do not execute the subsequent steps; 
</font></span></div>
<div><span lang="EN-GB"><font size="2"></font></span>&nbsp;</div>
<div><span lang="EN-GB"><font size="2">In other words, what you describe in your section 3.2 (diversion while continueing on terminating leg) would not occur for an S-CSCF that follows the&nbsp;standards</font></span></div>
<div><span lang="EN-GB"><font size="2"></font></span><span lang="EN-GB"><font size="2"></font></span>&nbsp;</div>
<div><span lang="EN-GB"><font size="2">Regarding section 3.3: if the AS converts the incoming terminating request to a new originating request for user B, shouldn&#39;t it&nbsp;also update the P-Asserted-Identity header to reflect the new originating user? 
</font></span></div>
<div><span lang="EN-GB"><font size="2"></font></span>&nbsp;</div>
<div><span lang="EN-GB"><font size="2">Regards,</font></span></div>
<div><span lang="EN-GB"><font size="2">Jeroen</font></span></div>
<blockquote style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<div style="FONT: 10pt arial">----- Original Message ----- </div>
<div style="BACKGROUND: #e4e4e4; FONT: 10pt arial"><b>From:</b> <a title="hanserik.van.elburg" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:hanserik.van.elburg%20at%20ericsson.com" target="_blank">
Hans Erik van Elburg (RY/ETM)</a> </div>
<div style="FONT: 10pt arial"><b>To:</b> <a title="sipping" onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sipping%20at%20ietf.org" target="_blank">sipping at ietf.org</a> </div>
<div style="FONT: 10pt arial"><b>Sent:</b> Tuesday, April 17, 2007 2:11 PM</div>
<div style="FONT: 10pt arial"><b>Subject:</b> [Sipping] New I-D for P-Served-User header</div>
<div><br>&nbsp;</div>
<p><font face="Arial" color="#800000" size="2">I uploaded a new draft for the P-Served-User Private-Header, until it gets available on the online Internet-Drafts directory you can retrieve it here:</font></p>
<p><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user-00.txt" target="_blank"><u></u><u><font face="Arial" color="#0000ff" size="2">http://elburg.eln-research.nl/drafts/draft-vanelburg-sipping-served-user-00.txt 
</font></u></a><font face="Arial" size="2"></font></p>
<p><font face="Courier New" size="2">Abstract<br><br>&nbsp;&nbsp; This document specifies the SIP P-Served-User P-header.&nbsp; This header<br>&nbsp;&nbsp; field addresses an issue that was found in the 3rd-Generation<br>&nbsp;&nbsp; Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an 
<br>&nbsp;&nbsp; S-CSCF (Serving Call Session Control Function) and an AS (Application<br>&nbsp;&nbsp; Server) on the ISC (IMS Subsystem Service Control) interface to<br>&nbsp;&nbsp; convey the identity of the served user and the session case that<br>
&nbsp;&nbsp; applies to this particular communication session and application<br>&nbsp;&nbsp; invocation.<br></font><br><font face="Arial" color="#800000" size="2">Best Regards,</font> </p>
<p><b><font face="Arial" color="#800000" size="2">/Hans Erik</font></b> </p><br>
<p>
<hr>

<p></p>_______________________________________________<br>
<p></p></p></blockquote></td></tr></tbody></table></div>

------=_Part_163583_30729920.1177981586299--



--===============0094275893==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sipping mailing list  https://www1.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
--===============0094275893==--





From sipping-bounces@ietf.org Mon Apr 30 22:59:53 2007
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hiiag-0001Dz-OG; Mon, 30 Apr 2007 22:59:46 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43)
	id 1Hiiaf-0001Dp-Sg for sipping-confirm+ok@megatron.ietf.org;
	Mon, 30 Apr 2007 22:59:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hiiaf-0001Dh-If
	for sipping@ietf.org; Mon, 30 Apr 2007 22:59:45 -0400
Received: from py-out-1112.google.com ([64.233.166.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hiiaf-0004Ya-4D
	for sipping@ietf.org; Mon, 30 Apr 2007 22:59:45 -0400
Received: by py-out-1112.google.com with SMTP id f31so1522289pyh
	for <sipping@ietf.org>; Mon, 30 Apr 2007 19:59:44 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=m2AwZWWTrZM04RfBng+n3bPs8bSLaWfAH0DBeSaOtTv8r7KKeq00LogcGLSwbUMOQPtXIfmg9Cgoh6bI5bOdzsXrnPOqARIv4W+GaEprJOlJ99g8Mot6lbgLBNfou1bqBiOBMkLYwlT12GRvqsVTnQAzO7jUIV8Zfq61wQBlli4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Wwsvn8rjXe85vITtA68J9YRX/Jy7rnoGveFWXSdXxtkCKFwpP/WGEBLGsU/mNGdI6BgqITu5AtRDjYK4rf8fQMkcWnqT9AKXA6SSaNr1zGN0PP1aI17Uh3qLl5OqFJpYr/GdXQszhf4LczTUt8ugbPMPykXg13Pk65AA6CQ0bFU=
Received: by 10.65.250.11 with SMTP id c11mr13027056qbs.1177988384517;
	Mon, 30 Apr 2007 19:59:44 -0700 (PDT)
Received: by 10.64.179.6 with HTTP; Mon, 30 Apr 2007 19:59:44 -0700 (PDT)
Message-ID: <66cd252f0704301959n4a8bc913j48ced178aad19c7b@mail.gmail.com>
Date: Tue, 1 May 2007 12:59:44 +1000
From: "Hisham Khartabil" <hisham.khartabil@gmail.com>
To: "Pailer Rudolf" <r.pailer@mobilkom.at>
Subject: Re: [Sipping] AW: [Geopriv] Location Presence Event Package
In-Reply-To: <03972E773D99AF4680D5DD84E6E2ABB010365CF7@ntxms01.ms.mobilkom.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <Acd6a/HMn5cHW6ybTY6l4vF+LYIT6QAKy53gAkz0tNA=>
	<03972E773D99AF4680D5DD84E6E2ABB010365CF7@ntxms01.ms.mobilkom.at>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Cc: geopriv@ietf.org, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

On 21/04/07, Pailer Rudolf <r.pailer@mobilkom.at> wrote:
> Hello Brian!
>
> Sorry, that it took me some time to reply to your mail.
>
> We looked at RFC 4660 that defines event notification filters for
> presence, but did not see a feasibile way to express the following rule:
> "Send a notification, if the presentity enters an area (e.g. specified
> by a circle (center point + radius) or a rectangle)."
> There was e.g. the proposal in our research group to use presence event
> filters in the following way:
> <changed from="-67.563 -13.834" by="0.2 0.2">
> We think that such a notation is highly ambigous and will lead to
> interoperability problems.

What kind of interoperability problem?

Please also note that you can extend RFC4660.

Hisham

>
> RFC 4660 builds on the assumtion that the state space of presence is
> restricted to a few logical states that can be filtered by a boolean
> combination of filter rules. The location presence event package
> notifies on geographical positions, that have an (nearly infinite) state
> space. Combining geograhical shapes in boolean terms and calculating if
> the presentity is now inside/outside of this area is not feasible on
> mobile devices with restricted computation resources.
>
> Therfore we propose to use some different kind of filtering approach
> (see
> http://www.ietf.org/internet-drafts/draft-ietf-geopriv-loc-filters-01.tx
> t).
>
> Now there is the question, why not to use geopriv-loc-filters inside the
> presence package:
> Our main goal is to route SIP SUBSCRIBE messages containing
> geopriv-loc-filters documents from the watcher to the presentity. The
> location presence event package is targeted at mobile devices and we
> argue that filters have to be executed on the mobile device (otherwise
> you will no be able to restrict the number of notification messages on
> the radio interface). This means that the subscription cannot be
> processed by a (conventional) presence server in the network, but has to
> be routed to the mobile phone of the user (but only to those mobile
> phones, that have an edge presence server running).
> Location presence subscriptions and notifications are processed by
> different nodes than conventional presence. The scale of location
> presence data may be significatly different to conventional presence.
> This means that SUBCRIBE and NOTIFY messages have to take different
> paths in the network and will be processed by different nodes than
> conventional presence.
> We thus discussed several methods, to differentiate the routing of
> conventional presence to location presence:
>         1) Introduce another URI-scheme. This does not seem to be as
> elegent as the introduction of the locpres event package.
>         2) The edge presence server on the mobile device registers with
> an own SIP URI. This requires a lot of a priori knowledge of the
> watcher.
>         3) define an own event package - we favored this solution
>
> The idea of the locpres event package is, that it uses the same
> framework than conventional presence (e.g. for user profiles, policy
> decisions etc.), but that it indicates that this type of presence has to
> be routed and processed differently than conventional presence.
> Thus SIP routing of initial SUBCRIBE messages can be based on the
> content "locpres" of the SIP Event header field. This solution seems to
> integrate well in the existing SIP presence framework and general SIP
> specifications. Presence user agents can for example use the "Watcher
> Information Event Template-Package" [RFC 3857]. This means that the
> Presence User Agent can subscribe to "locpres.winfo" notifications in
> order to be notified about changes in the subscription state regarding
> locpres events.
> Furthermore [RFC 3840] introduces "User Agent Capabilities" in form of
> feature tags that can be conveyed in form of parameters in the Contact
> header field to other user agents and registrars. In particular a
> Contact header with the sip.event media tag containing a value of
> "locpres" can be used by a Presence User Agent to indicate that
> subscriptions for location presence data shall be routed to this
> address. Sip.event feature tag parameters are also used in [RFC 3841]
> that defines the notion of "caller preferences" about request handling
> in servers. These preferences include the ability to select which
> Uniform Resource Identifiers (URI) a request gets routed to, and to
> specify certain request handling directives in proxies and redirect
> servers. Again a value of "locpres" in a sip.event media feature tag can
> be used by a presence server to route a subscription for location
> presence data to the responsible edge presence server or state agent.
>
> greetings
> Rudolf
>
> ________________________________
>
> Von: Brian Rosen [mailto:br@brianrosen.net]
> Gesendet: Montag, 09. April 2007 13:35
> An: Pailer Rudolf; sipping@ietf.org; geopriv@ietf.org
> Betreff: RE: [Geopriv] Location Presence Event Package
>
>
>
> I've read this, and I don't really understand why real presence (with
> the filter package) doesn't provide the same service.
>
> Can you give an example where presence+filter is significantly different
> from this package, with the filter inclusion?   It seems to me that you
> get roughly the same number of messages, with roughly the same content.
>
>
>
> Brian
>
>
>
> ________________________________
>
> From: Pailer Rudolf [mailto:r.pailer@mobilkom.at]
> Sent: Monday, April 09, 2007 1:57 AM
> To: sipping@ietf.org; geopriv@ietf.org
> Subject: [Geopriv] Location Presence Event Package
>
>
>
> Hello!
>
> I would like to notify you about the the Internet Draft "A Location
> Presence Event Package for the Session Initiation Protocol (SIP)".
>
> http://www.ietf.org/internet-drafts/draft-pailer-locpres-00.txt
> <http://www.ietf.org/internet-drafts/draft-pailer-locpres-00.txt>
>
> The draft describes the usage of the Session Initiation Protocol (SIP)
> for subscriptions and notifications of location presence. Location
> presence is information about the geographical position of a user.
> Subscriptions and notifications of location presence are supported by
> defining an event package within the general SIP event notification
> framework.
>
> The concept of a SIP based location enabler that is the core of the
> proposed draft was published on several occasions:
> *) A Terminal-Based Location Service Enabler for the IP Multimedia
> Subsystem, R. Pailer, S. Bessler, F. Wegscheider, IEEE Wireless
> Communications and Networking Conference April 2006 (WCNC06), Las Vegas,
> USA
>
> *) Terminal-Centric Location Services for the IP Multimedia Subsystem,
> J. Fabini, M. Happenhofer, R. Pailer, IEEE 63rd Vehicular Technology
> Conference, May 2006, Melbourne, Australia
>
> *) Implementing a Native IMS Location Service Enabler over a
> Prototypical IMS Core Network Testbed, P. Reichl, S. Bessler, J. Fabini,
> R. Pailer, J. Zeiss,The Third IEEE International Workshop on Mobile
> Commerce and Wireless Services (WMCS'06) June 26, 2006, San Francisco,
> USA
>
> *) Practical Experiences with an IMS-Aware Location Service Enabler on
> Top of an Experimental Open Source IMS Core Implementation, P. Reichl,
> S. Bessler, J. Fabini, R. Pailer, A. Poropatich, N. Jordan, R. Huber, H.
> Weisgrab, C. Brandner, I. Gojmerac, M. Ries, F. Wegscheider, Journal of
> Mobile Multimedia, Rinton Press, Fall 2006
>
> *) Lecture Notes in Geoinformation and Cartography, Location Based
> Services an TeleCartography, G. Gartner, W. Cartwright, M. P. Peterson
> (Eds.), Springer, 2007
>
> I can provide above documents in PDF format, if needed.
>
> Feedback from the IETF Working Groups GEOPRIV and SIPPING would be
> appreciated very much indeed.
>
> greetings
> Rudolf
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.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
>


_______________________________________________
Sipping mailing list  https://www1.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



