
From dworley@nortel.com  Sun Mar  1 12:53:17 2009
Return-Path: <dworley@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69B623A6B9E for <bliss@core3.amsl.com>; Sun,  1 Mar 2009 12:53:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9JHLkZGNiqfO for <bliss@core3.amsl.com>; Sun,  1 Mar 2009 12:53:16 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 2639B3A6880 for <bliss@ietf.org>; Sun,  1 Mar 2009 12:53:15 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n21Krc712543; Sun, 1 Mar 2009 20:53:38 GMT
Received: from [47.141.31.215] ([47.141.31.215]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 1 Mar 2009 15:53:35 -0500
From: "Dale Worley" <dworley@nortel.com>
To: BLISS <bliss@ietf.org>
Content-Type: text/plain
Organization: Nortel Networks
Date: Sun, 01 Mar 2009 15:53:33 -0500
Message-Id: <1235940813.5885.21.camel@victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Mar 2009 20:53:35.0089 (UTC) FILETIME=[C9B64610:01C99AAF]
Subject: [BLISS] More comments on draft-ietf-bliss-call-completion-03
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Mar 2009 20:53:17 -0000

* 1004  Hutton: Marking

        Section 5.6: "Question: The CC must be marked in some way as a CC call
        in order for the callee's monitor to know that the CC activation is
        being acted upon by the caller's agent.  And the marking must include
        the original Call-Id to allow correlation with the original call.
        Possibilities for a marking are a special URI-parameter on the request
        URI or a special header".  
        
        We need to make sure it works across intermediate B2BUAs that translate
        Call-Ids, so Call-Id should not be the means of correlation (otherwise
        it would require intermediate B2BUAs to perform appropriate translations
        on this information, but this would not work if different routes were
        taken).

This is indeed problematic.  In the call-completion design group we call
it "the correlation problem" and no ideal solution has been found.

The current thinking is based on the fact that the PSTN protocols do not
enforce this correlation, that is, the ETSI specification for
call-completion requests does not require the recipient to verify that
the caller has previously made a call to that destination, and indeed,
there may not be enough information in the request to verify it.
(Although the ETSI specification does imply that the originating
exchange should do such verification itself.)

So the suggestion under consideration is to abandon all attempts at
correlation (which we don't seem to be able to do successfully) and
instead warn that the callees' monitor (which receives CC requests)
should beware that illegitimate CC requests could be used for
cyber-stalking, and take appropriate countermeasures.

* 3006  Hutton: m values
        
        Section 4.2: "However, SIP call completion operations MAY carry an 'm'
        parameter to label call completion actions as to the original cause of
        the failure. 
        
        Surely it is not the cause of the failure that is important it is the
        flavor of call completion that is being requested (i.e. initiate
        ccRecall on caller becoming free or when next used).
        
We have to define the m values.  Each m value corresponds to both a
flavor of initial call failure (which is what causes that code to be
generated) and a flavor of call completion (which is the behavior that
that code elicits).

A fuller description of the meaning, cause, and effect of the m
parameter is in later sections; section 4.2 is meant to be a summary.
In particular, section 5.3 contains this:

   The monitor has a method of monitoring the status of the UA(s) and/or
   their users to determine when they are "available" for a CC call,
   that is, in a suitable state to receive a CC call.  In a system with
   rich presence information, the presence information may directly
   provide this status.  In a more restricted system, this determination
   MAY depend on the mode of the CC call in question, which is provided
   by the 'm' parameter.  E.g., a UA is considered available for CCBS
   ("m=BS") when it is not busy, but a UA is considered available for
   CCNR ("m=NR") when it becomes not busy after being busy with an
   established call.


* 3007  Hutton: Callbacks
        
        Section 5.1: "The agent can order the UA(s) at which the relevant
        calling user is available to generate a CC call to the callee".
        
        The agent can only do this if it is centralised rather than being in the
        endpoint that made the original call. So is a reason why the agent may
        be located in the server but is it really a requirement for callback to
        mature at a different UA to which it was originated. This is possibly
        added value that an agent could provide but maybe not something that
        should be stated in this draft.
        
I don't follow this argument.  If the agent is integrated into the UAC,
then the agent can trivially "order" the UAC to generate a CC call, the
agent and the UAC being the same device.
        
        * 3008  Hutton: Forking
        
        Section 6: "In this case, the caller's agent forks the SUBSCRIBE to two
        destinations, with appropriate Request-Disposition.  The first SUBSCRIBE
        is to the URI from Call-Info.  The second SUBSCRIBE is to the original
        request-URI, and reaches the same callee's monitor.
        
        It is not clear to me why the caller's agent would fork the SUBSCRIBE.
        Why would it not just send it to the URI from the Call-Info ?
        
First, beware that the descriptions in section 6 are meant to be an
example, and are simplified versions of the descriptions in section 5.
The relevant text for this issue is in section 5.5:

   Additionally,
   the caller's agent needs to include the original request-URI in its
   set of monitor URIs, because the call may have forked to additional
   callees whose responses the caller has not seen.  (A SUBSCRIBE to the
   request-URI alone is used in cases where the caller's agent has not
   received or cannot remember any monitor URI.)

Dale



From andrew.hutton@siemens.com  Tue Mar  3 05:52:26 2009
Return-Path: <andrew.hutton@siemens.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 087003A6C54 for <bliss@core3.amsl.com>; Tue,  3 Mar 2009 05:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level: 
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1bnkSZVNCnNS for <bliss@core3.amsl.com>; Tue,  3 Mar 2009 05:52:25 -0800 (PST)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id B0EC23A6C58 for <bliss@ietf.org>; Tue,  3 Mar 2009 05:52:24 -0800 (PST)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KFX00MBBNW18R@siemenscomms.co.uk> for bliss@ietf.org; Tue, 03 Mar 2009 13:52:50 +0000 (GMT)
Date: Tue, 03 Mar 2009 13:52:42 +0000
From: "Hutton, Andrew" <andrew.hutton@siemens.com>
In-reply-to: <1235768388.3834.73.camel@victoria-pingtel-com.us.nortel.com>
To: Dale Worley <dworley@nortel.com>
Message-id: <719F9BBB3E7E71428A2D13F3D76C768F0174D208@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Thread-Topic: [BLISS] Some of Andrew Hutton's concerns aboutdraft-ietf-bliss-call-completion-03
Thread-Index: AcmZHlp2YSL6PWY3R7m5pBkM2Oka/AC6O/zw
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <1235768388.3834.73.camel@victoria-pingtel-com.us.nortel.com>
Cc: BLISS <bliss@ietf.org>
Subject: Re: [BLISS] Some of Andrew Hutton's concerns	aboutdraft-ietf-bliss-call-completion-03
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2009 13:52:26 -0000

Hi Dale,

In general I am happy with your responses below.

However this did prompt me to have a look at section 6 of -03
(Examples). This shows that the caller UA generates two SUBSCRIBE's
using the same Call-Id and the text below the diagram states:

"The caller's agent adds to these URIs an 'm' parameter (if possible).
In this case, the caller's agent forks the SUBSCRIBE to two
destinations, with appropriate Request-Disposition."

This I think is a bit strange as I don't think that many UA SIP Stack
implementations provide a service to "fork" in this way. Therefore I
think we may need a different mechanism to allow the callee to determine
that the two subscribes are related.

Regards
Andy=20

>-----Original Message-----
>From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]=20
>On Behalf Of Dale Worley
>Sent: 27 February 2009 21:00
>To: BLISS
>Subject: [BLISS] Some of Andrew Hutton's concerns=20
>aboutdraft-ietf-bliss-call-completion-03
>
>[These are keyed to the issue identifiers in the list of open issues we
>keep on the BLISS-CC mailing list.]
>
>> * 1003  Hutton: CC URI
>>=20
>> "Hutton, Andrew" <andrew.hutton@siemens.com>
>> Section 5.6: "Question: Should the callee's monitor supply a=20
>URI which
>> should be used in the CC call?"
>> I think it should.
>
>This text has been moved to section 5.7 of -03.  The current text is:
>"The notification MAY also contain also a URI which should be used in
>the CC call.  In practice, this may be the AOR of the callee."
>
>I think we should change the MAY to SHOULD.
>
>> * 1005  Hutton: Failure
>>=20
>> "Hutton, Andrew" <andrew.hutton@siemens.com>
>> Section 5.6: "Can a call appear to succeed from the=20
>monitor's point of
>> view but fail from the calling user's point of view?"
>> It is not clear to me what constitutes success from the=20
>monitor's point
>> of view. Does just getting back a 180 constitute success? If so, from
>> the caller's perspective the call could still fail to be=20
>answered, so it
>> would be up to the caller to invoke CCNR (again) if that is what he
>> wants
>
>In section 5.5 of -03, the text is:
>
>   Note that from
>   the SIP point of view, the INVITE may be successful, but from the
>   user's point of view, the call may be unsuccessful.  E.g., the call
>   may have connected to the callee's voicemail, which would return a
>   200 status to the INVITE but from the caller's point of view is "no
>   reply".
>
>I think this satisfies your concern.
>
>> * 3004  Hutton: Failure of initial call
>>=20
>> "Hutton, Andrew" <andrew.hutton@siemens.com>
>> Terminology: "CC request: (1) the indication by the caller to the
>> caller's agent that the caller desires CC for a failed=20
>original call".=20
>> Why does there have to be a failed original call should it=20
>be possible
>> to initiate a CC request with no previous call or even if=20
>the previous
>> call was "successful". The concept of "failure" really only=20
>applies to
>> the user and cannot be specified.
>
>> * 3005  Hutton: Queue
>>=20
>> "Hutton, Andrew" <andrew.hutton@siemens.com>
>> Terminology: "Call-completion queue: a buffer at the callee' monitor
>> which stores incoming calls which have failed or may have failed"
>> Presumably this means that it is left to the implementation to decide
>> what failed means and that potentially all calls will be in=20
>this "queue"?
>
>It does appear that these definitions need to be revised so that
>"failed" is not seen as restrictive.
>
>> * 1006  Hutton: 180 Ringing
>>=20
>> "Hutton, Andrew" <andrew.hutton@siemens.com>
>> Section 6: I think that the URI of the monitor (i.e.=20
>Call-Info) should
>> be included also in a 180 Ringing because the caller may need to know
>> that callback is available before deciding to give up on the ringing
>> call.
>
>That is a good point, and I think that the group agreed with=20
>it when you
>made it, but the -03 text does not reflect that consensus.  I will
>propose some edits about this.
>
>> * 3002  Hutton: Location of agents
>>=20
>> "Hutton, Andrew" <andrew.hutton@siemens.com>:
>> Abstract: "implementations at the caller's and callee's endpoints
>> cooperate to place the caller's request for call completion=20
>into a queue
>> at the callee's endpoint".
>> I think the draft gives some mixed messages regarding the options for
>> where the caller's and callee's agent may be located and some
>> clarification is needed. Maybe the abstract should make it clear that
>> the document does not specify the location of the agents.
>
>Yes, I think that sentence in the Abstract needs to be revised.  The
>idea we want to convey is that the agent/monitor can be in the UAs
>themselves, or be in "servers" that are presumably involved in the
>endpoint's networks.
>
>> * 3003  Hutton: Appendixes
>>=20
>> "Hutton, Andrew" <andrew.hutton@siemens.com>
>> Introduction: "As a proof-of-concept, simple agents and monitors can
>be
>> devised that interact with users and UAs entirely through=20
>standard SIP
>> mechanisms [RFC3265], [RFC4235] and [RFC3515], as described in the
>> Appendixes".
>> The appendixes do I think add to the confusion regarding where the
>> caller's agent is located as it describes features codes=20
>being used to
>> invoke the service which seems at odd's with the abstract.
>
>> * 3009  Hutton: Example
>>=20
>> "Hutton, Andrew" <andrew.hutton@siemens.com>
>> Appendix A.  "Example Caller's Agent".=20
>> This is an example of using a feature code to invoke the feature from
>> the "UA" would it be possible to also include an example=20
>where the agent
>> is in the UA ?
>
>We could write such an example, but I don't think that it would add
>much to the document.  The call flow example in section 6 of -03 shows
>what behavior would look like if the agent/monitor were integrated into
>the UAs.  Indeed, the point of the Appendixes is to show that one can
>separate the agent/monitor from the UAs and still use SIP signaling to
>coordinate the agent/monitor with their respective UAs.
>
>Dale
>
>
>_______________________________________________
>BLISS mailing list
>BLISS@ietf.org
>https://www.ietf.org/mailman/listinfo/bliss
>

From andrew.hutton@siemens.com  Tue Mar  3 06:44:43 2009
Return-Path: <andrew.hutton@siemens.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0DE003A6A19 for <bliss@core3.amsl.com>; Tue,  3 Mar 2009 06:44:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level: 
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GTrchWWnwQeu for <bliss@core3.amsl.com>; Tue,  3 Mar 2009 06:44:42 -0800 (PST)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id A60073A6929 for <bliss@ietf.org>; Tue,  3 Mar 2009 06:44:41 -0800 (PST)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KFX00281QB8GU@siemenscomms.co.uk> for bliss@ietf.org; Tue, 03 Mar 2009 14:45:08 +0000 (GMT)
Date: Tue, 03 Mar 2009 14:45:05 +0000
From: "Hutton, Andrew" <andrew.hutton@siemens.com>
In-reply-to: <1235940813.5885.21.camel@victoria-pingtel-com.us.nortel.com>
To: Dale Worley <dworley@nortel.com>
Message-id: <719F9BBB3E7E71428A2D13F3D76C768F0174D295@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Thread-Topic: More comments on draft-ietf-bliss-call-completion-03
Thread-Index: Acmar89KKasRi/s8RvGlJUvf+20PTwBXD5Kw
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <1235940813.5885.21.camel@victoria-pingtel-com.us.nortel.com>
Cc: BLISS <bliss@ietf.org>
Subject: Re: [BLISS] More comments on draft-ietf-bliss-call-completion-03
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2009 14:44:43 -0000

Hi Dale,

A couple of comments below.

Regards
Andy

>-----Original Message-----
>From: Dale Worley [mailto:dworley@nortel.com]=20
>Sent: 01 March 2009 20:54
>To: BLISS
>Cc: Hutton, Andrew
>Subject: More comments on draft-ietf-bliss-call-completion-03
>
>* 1004  Hutton: Marking
>
>        Section 5.6: "Question: The CC must be marked in some=20
>way as a CC call
>        in order for the callee's monitor to know that the CC=20
>activation is
>        being acted upon by the caller's agent.  And the=20
>marking must include
>        the original Call-Id to allow correlation with the=20
>original call.
>        Possibilities for a marking are a special=20
>URI-parameter on the request
>        URI or a special header". =20
>       =20
>        We need to make sure it works across intermediate=20
>B2BUAs that translate
>        Call-Ids, so Call-Id should not be the means of=20
>correlation (otherwise
>        it would require intermediate B2BUAs to perform=20
>appropriate translations
>        on this information, but this would not work if=20
>different routes were
>        taken).
>
>This is indeed problematic.  In the call-completion design=20
>group we call
>it "the correlation problem" and no ideal solution has been found.
>
>The current thinking is based on the fact that the PSTN=20
>protocols do not
>enforce this correlation, that is, the ETSI specification for
>call-completion requests does not require the recipient to verify that
>the caller has previously made a call to that destination, and indeed,
>there may not be enough information in the request to verify it.
>(Although the ETSI specification does imply that the originating
>exchange should do such verification itself.)
>
>So the suggestion under consideration is to abandon all attempts at
>correlation (which we don't seem to be able to do successfully) and
>instead warn that the callees' monitor (which receives CC requests)
>should beware that illegitimate CC requests could be used for
>cyber-stalking, and take appropriate countermeasures.
>
>* 3006  Hutton: m values
>       =20
>        Section 4.2: "However, SIP call completion operations=20
>MAY carry an 'm'
>        parameter to label call completion actions as to the=20
>original cause of
>        the failure.=20
>       =20
>        Surely it is not the cause of the failure that is=20
>important it is the
>        flavor of call completion that is being requested=20
>(i.e. initiate
>        ccRecall on caller becoming free or when next used).
>       =20
>We have to define the m values.  Each m value corresponds to both a
>flavor of initial call failure (which is what causes that code to be
>generated) and a flavor of call completion (which is the behavior that
>that code elicits).
>
>A fuller description of the meaning, cause, and effect of the m
>parameter is in later sections; section 4.2 is meant to be a summary.
>In particular, section 5.3 contains this:
>
>   The monitor has a method of monitoring the status of the=20
>UA(s) and/or
>   their users to determine when they are "available" for a CC call,
>   that is, in a suitable state to receive a CC call.  In a system with
>   rich presence information, the presence information may directly
>   provide this status.  In a more restricted system, this=20
>determination
>   MAY depend on the mode of the CC call in question, which is provided
>   by the 'm' parameter.  E.g., a UA is considered available for CCBS
>   ("m=3DBS") when it is not busy, but a UA is considered available for
>   CCNR ("m=3DNR") when it becomes not busy after being busy with an
>   established call.
>
>
>* 3007  Hutton: Callbacks
>       =20
>        Section 5.1: "The agent can order the UA(s) at which=20
>the relevant
>        calling user is available to generate a CC call to the callee".
>       =20
>        The agent can only do this if it is centralised rather=20
>than being in the
>        endpoint that made the original call. So is a reason=20
>why the agent may
>        be located in the server but is it really a=20
>requirement for callback to
>        mature at a different UA to which it was originated.=20
>This is possibly
>        added value that an agent could provide but maybe not=20
>something that
>        should be stated in this draft.
>       =20
>I don't follow this argument.  If the agent is integrated into the UAC,
>then the agent can trivially "order" the UAC to generate a CC call, the
>agent and the UAC being the same device.

[AndyH] - The text in what is now in section 5.2. of -03 when it states
various things that the callers agent "can" do but if I understand the
text correctly these are all outside the scope of the document. However
whether the agent can do these things or not depends on the architecture
of the solution (i.e. where the caller's agent is located) so I think it
is best just not to mention the things that the agent "can" do but are
outside the scope of the document as it just complicates the draft.


>       =20
>        * 3008  Hutton: Forking
>       =20
>        Section 6: "In this case, the caller's agent forks the=20
>SUBSCRIBE to two
>        destinations, with appropriate Request-Disposition. =20
>The first SUBSCRIBE
>        is to the URI from Call-Info.  The second SUBSCRIBE is=20
>to the original
>        request-URI, and reaches the same callee's monitor.
>       =20
>        It is not clear to me why the caller's agent would=20
>fork the SUBSCRIBE.
>        Why would it not just send it to the URI from the Call-Info ?
>       =20
>First, beware that the descriptions in section 6 are meant to be an
>example, and are simplified versions of the descriptions in section 5.
>The relevant text for this issue is in section 5.5:
>
>   Additionally,
>   the caller's agent needs to include the original request-URI in its
>   set of monitor URIs, because the call may have forked to additional
>   callees whose responses the caller has not seen.  (A=20
>SUBSCRIBE to the
>   request-URI alone is used in cases where the caller's agent has not
>   received or cannot remember any monitor URI.)

[AndyH] - This relates to me previous message on the list I am not sure
that a SIP UA implementation will be able to "fork" the request as it is
really not a proxy and probably does not have the capability within it's
SIP stack to do this. I think we should try to remove this requirement
for the UA to "fork" the request.


>
>Dale
>
>
>

From dworley@nortel.com  Tue Mar  3 08:48:38 2009
Return-Path: <dworley@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E59628C2CA for <bliss@core3.amsl.com>; Tue,  3 Mar 2009 08:48:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.594
X-Spam-Level: 
X-Spam-Status: No, score=-6.594 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CMGpCaivSyo4 for <bliss@core3.amsl.com>; Tue,  3 Mar 2009 08:48:37 -0800 (PST)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id EFD8E3A690E for <bliss@ietf.org>; Tue,  3 Mar 2009 08:47:58 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n23Gm7i00965; Tue, 3 Mar 2009 16:48:07 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 3 Mar 2009 11:48:20 -0500
From: "Dale Worley" <dworley@nortel.com>
To: "Sanjay Sinha (sanjsinh)" <sanjsinh@cisco.com>
In-Reply-To: <C7FFFFDD779F2047A0FBAC811C5C5A0007DEAA15@xmb-rtp-201.amer.cisco.com>
References: <A8C03747-2392-4D22-92A1-2D1F048E5929@ntt-at.com> <1235763907.3834.37.camel@victoria-pingtel-com.us.nortel.com> <C7FFFFDD779F2047A0FBAC811C5C5A0007DEAA15@xmb-rtp-201.amer.cisco.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Tue, 03 Mar 2009 11:48:19 -0500
Message-Id: <1236098899.3740.10.camel@victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Mar 2009 16:48:20.0080 (UTC) FILETIME=[DBB59700:01C99C1F]
Cc: bliss@ietf.org
Subject: Re: [BLISS] Use-Cases for ACH
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2009 16:48:38 -0000

On Sat, 2009-02-28 at 01:01 -0500, Sanjay Sinha (sanjsinh) wrote:
> >Call-waiting is always implemented locally on the phone in 
> >SIP, so I don't see the need for a SIP ACH function for it.
> 
> I think it is an ACH feature in the sense that the proxy can decide
> whether to extend the call to called party or send 486 otherwise.

That assumes that the proxy is call-stateful, that is, it knows whether
there is a call on the phone or not.  In some SIP systems, proxies do
not track that information.

> >But it looks like "barring outgoing" functions are all 
> >implemented in the UA, and so aren't an ACH function per se.  
> >("Barring incoming" needs to be done at the proxy, so that's 
> >an ACH function.)
> 
> How about the case where a system administrator sets barring outgoing
> calls based on Class of Service for a given user.

That's still a function that needs to be configured into the UA (since
the UA can address an INVITE that circumvents any particular proxy).

Dale



From shida@ntt-at.com  Wed Mar  4 00:43:13 2009
Return-Path: <shida@ntt-at.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9991E3A6B69 for <bliss@core3.amsl.com>; Wed,  4 Mar 2009 00:43:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.336
X-Spam-Level: 
X-Spam-Status: No, score=-1.336 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ogJf7S0EblAs for <bliss@core3.amsl.com>; Wed,  4 Mar 2009 00:43:13 -0800 (PST)
Received: from gateway05.websitewelcome.com (gateway05.websitewelcome.com [67.18.21.3]) by core3.amsl.com (Postfix) with SMTP id 40EF13A6B44 for <bliss@ietf.org>; Wed,  4 Mar 2009 00:43:12 -0800 (PST)
Received: (qmail 21373 invoked from network); 4 Mar 2009 09:01:46 -0000
Received: from gator465.hostgator.com (69.56.174.130) by gateway05.websitewelcome.com with SMTP; 4 Mar 2009 09:01:46 -0000
Received: from flh1ahc140.tky.mesh.ad.jp ([125.192.94.140]:59384 helo=[192.168.1.4]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1LemhL-0003dE-3Y for bliss@ietf.org; Wed, 04 Mar 2009 02:43:27 -0600
Message-Id: <9E2D44DD-C9D5-4CF6-82F9-08AB6F0432DA@ntt-at.com>
From: Shida Schubert <shida@ntt-at.com>
To: bliss@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 4 Mar 2009 17:43:25 +0900
X-Mailer: Apple Mail (2.930.3)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
Subject: [BLISS] Agenda Requests etc.
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 08:43:13 -0000

All,

  The 74th IETF is quickly approaching. We have a 2 hour slot on  
Thursday,
so please send in your agenda request.

  Regards
   Shida

From john.elwell@siemens.com  Thu Mar  5 23:48:56 2009
Return-Path: <john.elwell@siemens.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 646AE3A67D7 for <bliss@core3.amsl.com>; Thu,  5 Mar 2009 23:48:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.418
X-Spam-Level: 
X-Spam-Status: No, score=-2.418 tagged_above=-999 required=5 tests=[AWL=0.181,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJTEil9dncXf for <bliss@core3.amsl.com>; Thu,  5 Mar 2009 23:48:55 -0800 (PST)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id 7A9723A69DE for <bliss@ietf.org>; Thu,  5 Mar 2009 23:48:55 -0800 (PST)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KG20036SR2C41@siemenscomms.co.uk> for bliss@ietf.org; Fri, 06 Mar 2009 07:49:24 +0000 (GMT)
Date: Fri, 06 Mar 2009 07:49:22 +0000
From: "Elwell, John" <john.elwell@siemens.com>
To: bliss@ietf.org, Theo Zourzouvillys <theo@crazygreek.co.uk>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0019C0596@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Thread-Topic: Comments on draft-zourzouvillys-bliss-ach-http-api-00
Thread-Index: AcmeMBBL3zf+a6PMQKi7edvqYBP+ZA==
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Subject: [BLISS] Comments on draft-zourzouvillys-bliss-ach-http-api-00
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 07:48:56 -0000

1. Concerning the question of call forwarding unconditional versus no
answer, one drawback of using no answer with timeout of 0 for
unconditional is that it forces you to use the same destination for
both.

So for example, if I permanently have no answer forwarding set to
forward to my voicemail after 15s, but when I go away I want to set
forwarding unconditional to an assistant, I have to change 2 parameters.
Also when I return I have to remember not only to cancel unconditional
but also to set no answer again.

Another drawback is that forwarding busy or not reachable normally take
precedence over forwarding no answer, yet forwarding unconditional
normally takes precedence over forwarding busy and not reachable.
Although the different timeout values could be used to change the order
of precedence, it would be rather ugly.

So I would prefer to keep the two forwarding types separate.

2. "DND could be achived by defining some service URNs that return
   the status code, for example 480. e.g: urn:sip:status:unavailable,
   and then setting unconditional call forward to it, for example?"
This sounds like a rather convoluted way of doing it, and I am not sure
I understand it. Why not just have two settings: target and status,
where target could be null (resulting in call rejection)?

3. I am not entirely clear about the motivation for including outgoing
call barring. First, it has not been considered under the topic ACH,
because ACH concerns itself only with inbound calls. Second, it could be
done at the UA (the not-registered case clearly doesn't apply). I
suppose an advantage of doing it at the proxy is that you can do it once
and it covers all UAs. My next comment is also related.

4. What credentials are used for HTTP digest authentication - the same
as for SIP? I suppose one advantage of using separate credentials is
that a user with multiple UAs can supply SIP credentials to all those
UAs, but only supply (or unlock) HTTP credentials on the one he is
actually using to do configuration changes. Therefore other individuals
using other UAs on behalf of that user would not be able to change
configuration settings, and in particular would not be able to change
outgoing call barring. On the other hand, it is more information to
configure.

John


From theo@crazygreek.co.uk  Fri Mar  6 08:35:25 2009
Return-Path: <theo@crazygreek.co.uk>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C321E3A657C for <bliss@core3.amsl.com>; Fri,  6 Mar 2009 08:35:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level: 
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xDbl4gLtrdxE for <bliss@core3.amsl.com>; Fri,  6 Mar 2009 08:35:24 -0800 (PST)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by core3.amsl.com (Postfix) with SMTP id 687B43A6D08 for <bliss@ietf.org>; Fri,  6 Mar 2009 08:35:24 -0800 (PST)
Received: from source ([209.85.220.172]) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKSbFQ647jeIiCKAq0bOgW3UJVpiTvktc1@postini.com; Fri, 06 Mar 2009 08:35:55 PST
Received: by fxm20 with SMTP id 20so420210fxm.42 for <bliss@ietf.org>; Fri, 06 Mar 2009 08:35:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.86.27.9 with SMTP id a9mr2053866fga.49.1236357354378; Fri, 06  Mar 2009 08:35:54 -0800 (PST)
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0019C0596@GBNTHT12009MSX.gb002.siemens.net>
References: <0D5F89FAC29E2C41B98A6A762007F5D0019C0596@GBNTHT12009MSX.gb002.siemens.net>
Date: Fri, 6 Mar 2009 16:35:54 +0000
Message-ID: <167dfb9b0903060835s4d2f3367jc68c85f3397e3507@mail.gmail.com>
From: Theo Zourzouvillys <theo@crazygreek.co.uk>
To: "Elwell, John" <john.elwell@siemens.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: bliss@ietf.org
Subject: Re: [BLISS] Comments on draft-zourzouvillys-bliss-ach-http-api-00
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 16:35:25 -0000

On Fri, Mar 6, 2009 at 7:49 AM, Elwell, John <john.elwell@siemens.com> wrot=
e:

Hi John,

thank you very much for your feedback.

> 1. Concerning the question of call forwarding unconditional versus no
> answer, one drawback of using no answer with timeout of 0 for
> unconditional is that it forces you to use the same destination for
> both.
>
> So I would prefer to keep the two forwarding types separate.

Yup - the design team has also raised this, and i've added a
'noanswer' mode into the -01-pre version.

> 2. "DND could be achived by defining some service URNs that return
> =A0 the status code, for example 480. e.g: urn:sip:status:unavailable,
> =A0 and then setting unconditional call forward to it, for example?"
> This sounds like a rather convoluted way of doing it, and I am not sure
> I understand it.

My point was that (logically), DND is actually just the same as
unconditionally forwarding to something that always returns the status
code you want, for example:

  A -> B INVITE sip:responder.proxy.com;status=3D480;reason=3D"Out to lunch=
" SIP/2.0
  B -> A SIP/2.0 480 Out to lunch

> Why not just have two settings: target and status,
> where target could be null (resulting in call rejection)?

Because it would be nice to be able to configure the reason phrase and
possibly also the status code that is returned.  We could of course
instead have a 'response' node that contains the status code and
reason phrase that is always returned.

What are other peoples thoughts on this?

> 3. I am not entirely clear about the motivation for including outgoing
> call barring. First, it has not been considered under the topic ACH,
> because ACH concerns itself only with inbound calls.

These items were identified by the design team as we were (iirc)
targeting the same functionality as the GSM initially.

> Second, it could be
> done at the UA (the not-registered case clearly doesn't apply). I
> suppose an advantage of doing it at the proxy is that you can do it once
> and it covers all UAs. My next comment is also related.

When the UA and HTTP credentials are separate, it has some great uses.
 It would also be possible for this node to be read only unless using
credentials other than the HTTP ones, at which point it becomes
read/write.

> 4. What credentials are used for HTTP digest authentication - the same
> as for SIP? I suppose one advantage of using separate credentials is
> that a user with multiple UAs can supply SIP credentials to all those
> UAs, but only supply (or unlock) HTTP credentials on the one he is
> actually using to do configuration changes. Therefore other individuals
> using other UAs on behalf of that user would not be able to change
> configuration settings, and in particular would not be able to change
> outgoing call barring. On the other hand, it is more information to
> configure.

I think my personal preference to that is "network defined" - SIP
credentials would of course be a good candidate for many, however
there are scenarios as you mention where it's preferable to have
separate.

my view is that all UAs MUST support HTTP digest, using the SIP
credentials, as well as a way to let a user/administrator configure
alternative Digest credentials.

of course, auto provisioning only works if the SIP credentials are used.

another option that i'd be more than happy with is client certificate
over SSL, although it seems vendors run away screaming as soon as
anything related to PKI is mentioned :-)

 ~ Theo

From dworley@nortel.com  Fri Mar  6 12:56:08 2009
Return-Path: <dworley@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 94B493A6870 for <bliss@core3.amsl.com>; Fri,  6 Mar 2009 12:56:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.453
X-Spam-Level: 
X-Spam-Status: No, score=-6.453 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6EIMgzVLcpfc for <bliss@core3.amsl.com>; Fri,  6 Mar 2009 12:56:07 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 8E2F23A676A for <bliss@ietf.org>; Fri,  6 Mar 2009 12:56:07 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n26KuZA17782; Fri, 6 Mar 2009 20:56:36 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 6 Mar 2009 15:56:26 -0500
From: "Dale Worley" <dworley@nortel.com>
To: "Hutton, Andrew" <andrew.hutton@siemens.com>
In-Reply-To: <719F9BBB3E7E71428A2D13F3D76C768F0174D201@GBNTHT12009MSX.gb002.siemens.net>
References: <1235768388.3834.73.camel@victoria-pingtel-com.us.nortel.com> <719F9BBB3E7E71428A2D13F3D76C768F0174D201@GBNTHT12009MSX.gb002.siemens.net>
Content-Type: text/plain
Organization: Nortel Networks
Date: Fri, 06 Mar 2009 15:56:26 -0500
Message-Id: <1236372986.3762.28.camel@victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Mar 2009 20:56:26.0670 (UTC) FILETIME=[040C34E0:01C99E9E]
Cc: BLISS <bliss@ietf.org>
Subject: Re: [BLISS] Some of Andrew Hutton's concerns	aboutdraft-ietf-bliss-call-completion-03
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 20:56:08 -0000

On Tue, 2009-03-03 at 13:51 +0000, Hutton, Andrew wrote:
> However this did prompt me to have a look at section 6 of -03
> (Examples). This shows that the caller UA generates two SUBSCRIBE's
> using the same Call-Id and the text below the diagram states:
> 
> "The caller's agent adds to these URIs an 'm' parameter (if possible).
> In this case, the caller's agent forks the SUBSCRIBE to two
> destinations, with appropriate Request-Disposition."
> 
> This I think is a bit strange as I don't think that many UA SIP Stack
> implementations provide a service to "fork" in this way. Therefore I
> think we may need a different mechanism to allow the callee to determine
> that the two subscribes are related.

The stack I am most familiar with (sipX) can be used to implement
proxies, so it has no trouble issuing two requests with the same
Call-Id.  But that may not be true of other stacks, particularly those
intended exclusively for use in UAs.

The tremendous advantage of using the same Call-Id in both SUBSCRIBEs is
that the existing "merged request" logic will identify duplicates.

Other than for efficiency, I don't think that it is necessary to detect
duplicate subscriptions arriving at a callee -- if duplication is not
detected, the caller has two entries in the callee's queue.  The worst
result from that is that the caller is not available when the first
entry is selected, and then the second entry is selected, causing the
caller to be rung again.

Dale



From dworley@nortel.com  Fri Mar  6 13:00:53 2009
Return-Path: <dworley@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8F5C3A680C for <bliss@core3.amsl.com>; Fri,  6 Mar 2009 13:00:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.031
X-Spam-Level: 
X-Spam-Status: No, score=-6.031 tagged_above=-999 required=5 tests=[AWL=-0.432, BAYES_00=-2.599, J_BACKHAIR_53=1, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6OIqIGTXlkN0 for <bliss@core3.amsl.com>; Fri,  6 Mar 2009 13:00:53 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id B19663A676A for <bliss@ietf.org>; Fri,  6 Mar 2009 13:00:52 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n26L1LA21276; Fri, 6 Mar 2009 21:01:21 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 6 Mar 2009 16:01:07 -0500
From: "Dale Worley" <dworley@nortel.com>
To: "Hutton, Andrew" <andrew.hutton@siemens.com>
In-Reply-To: <719F9BBB3E7E71428A2D13F3D76C768F0174D295@GBNTHT12009MSX.gb002.siemens.net>
References: <1235940813.5885.21.camel@victoria-pingtel-com.us.nortel.com> <719F9BBB3E7E71428A2D13F3D76C768F0174D295@GBNTHT12009MSX.gb002.siemens.net>
Content-Type: text/plain
Organization: Nortel Networks
Date: Fri, 06 Mar 2009 16:01:07 -0500
Message-Id: <1236373267.3762.33.camel@victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Mar 2009 21:01:07.0615 (UTC) FILETIME=[AB8102F0:01C99E9E]
Cc: BLISS <bliss@ietf.org>
Subject: Re: [BLISS] More comments on draft-ietf-bliss-call-completion-03
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 21:00:53 -0000

On Tue, 2009-03-03 at 14:45 +0000, Hutton, Andrew wrote:
> [AndyH] - The text in what is now in section 5.2. of -03 when it states
> various things that the callers agent "can" do but if I understand the
> text correctly these are all outside the scope of the document. However
> whether the agent can do these things or not depends on the architecture
> of the solution (i.e. where the caller's agent is located) so I think it
> is best just not to mention the things that the agent "can" do but are
> outside the scope of the document as it just complicates the draft.

It's out of scope *how* the agent does these things, but it is a
requirement on the agent that it *can* do them.  My goal for that
section is to notify implementors as to what the agent must be able to
do.  Conversely, having enumerated the necessary capabilities of the
agent, the reader can verify that the defined procedures later in the
document do not require any further capabilities.  Otherwise, the
implementor will have to comb through the procedures to develop his own
list of agent<-->UAC facilities.

Dale



From root@core3.amsl.com  Mon Mar  9 14:00:02 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: bliss@ietf.org
Delivered-To: bliss@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 406DB3A6C5B; Mon,  9 Mar 2009 14:00:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090309210002.406DB3A6C5B@core3.amsl.com>
Date: Mon,  9 Mar 2009 14:00:02 -0700 (PDT)
Cc: bliss@ietf.org
Subject: [BLISS] I-D Action:draft-ietf-bliss-problem-statement-04.txt
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 21:00:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Basic Level of Interoperability for SIP Services Working Group of the IETF.


	Title           : Basic Level of Interoperability for Session Initiation Protocol (SIP) Services (BLISS) Problem Statement
	Author(s)       : J. Rosenberg
	Filename        : draft-ietf-bliss-problem-statement-04.txt
	Pages           : 20
	Date            : 2009-03-09

The Session Initiation Protocol (SIP) has been designed as a general
purpose protocol for establishing and managing multimedia sessions.
It provides many core functions and extensions in support of features
such as transferring of calls, parking calls, and so on.  However,
interoperability of more advanced features between different vendors
has been poor.  This document describes the reason behind these
interoperability problems, and presents a framework for addressing
them.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bliss-problem-statement-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-bliss-problem-statement-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-03-09135912.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Mon Mar  9 15:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: bliss@ietf.org
Delivered-To: bliss@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 98A753A6811; Mon,  9 Mar 2009 15:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090309220001.98A753A6811@core3.amsl.com>
Date: Mon,  9 Mar 2009 15:00:01 -0700 (PDT)
Cc: bliss@ietf.org
Subject: [BLISS] I-D Action:draft-ietf-bliss-shared-appearances-02.txt
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 22:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Basic Level of Interoperability for SIP Services Working Group of the IETF.


	Title           : Shared Appearances of a Session Initiation Protocol (SIP) Address of Record (AOR)
	Author(s)       : A. Johnston, et al.
	Filename        : draft-ietf-bliss-shared-appearances-02.txt
	Pages           : 65
	Date            : 2009-03-09

This document describes the requirements and implementation of a
group telephony feature commonly known as Bridged Line Appearance
(BLA) or Multiple Line Appearance (MLA), or Shared Call/Line
Appearance (SCA).  When implemented using the Session Initiation
Protocol (SIP), it is referred to as shared appearances of an Address
of Record (AOR) since SIP does not have the concept of lines.  This
feature is commonly offered in IP Centrex services and IP-PBX
offerings and is likely to be implemented on SIP IP telephones and
SIP feature servers used in a business environment.  This document
lists requirements and compares implementation options for this
feature.  Extensions to the SIP dialog event package are proposed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bliss-shared-appearances-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-bliss-shared-appearances-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-03-09145301.I-D@ietf.org>


--NextPart--

From alan@sipstation.com  Tue Mar 10 06:33:41 2009
Return-Path: <alan@sipstation.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C221A3A6907 for <bliss@core3.amsl.com>; Tue, 10 Mar 2009 06:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CiadxVYutIFo for <bliss@core3.amsl.com>; Tue, 10 Mar 2009 06:33:40 -0700 (PDT)
Received: from mho-01-bos.mailhop.org (mho-01-bos.mailhop.org [63.208.196.178]) by core3.amsl.com (Postfix) with ESMTP id D987A3A68B1 for <bliss@ietf.org>; Tue, 10 Mar 2009 06:33:40 -0700 (PDT)
Received: from 71-81-68-141.dhcp.stls.mo.charter.com ([71.81.68.141] helo=alan-johnstons-powerbook-g4-17.local) by mho-01-bos.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <alan@sipstation.com>) id 1Lh262-0009lX-VC for bliss@ietf.org; Tue, 10 Mar 2009 13:34:15 +0000
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 71.81.68.141
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+6U78ERbgu31BehdZBKeLHgMRsAKBLzKY=
Message-ID: <49B66C52.2050503@sipstation.com>
Date: Tue, 10 Mar 2009 08:34:10 -0500
From: Alan Johnston <alan@sipstation.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: bliss@ietf.org
References: <20090309220001.98A753A6811@core3.amsl.com>
In-Reply-To: <20090309220001.98A753A6811@core3.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [BLISS] I-D Action:draft-ietf-bliss-shared-appearances-02.txt
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2009 13:33:41 -0000

All,

Some of the major changes to this version of the document include:

- Publish only on appearance selection or seizure/call join or 
bridge/call take or pickup
- Allow Appearance Agent to subscribe to dialog events if it is not a 
call stateful proxy or B2BUA(shown in Section 10.13)
- Publications to the shared appearances AOR
- Major rewrite of call flows

As always, comments most welcome.

Thanks,
Alan


Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Basic Level of Interoperability for SIP Services Working Group of the IETF.
>
>
> 	Title           : Shared Appearances of a Session Initiation Protocol (SIP) Address of Record (AOR)
> 	Author(s)       : A. Johnston, et al.
> 	Filename        : draft-ietf-bliss-shared-appearances-02.txt
> 	Pages           : 65
> 	Date            : 2009-03-09
>
> This document describes the requirements and implementation of a
> group telephony feature commonly known as Bridged Line Appearance
> (BLA) or Multiple Line Appearance (MLA), or Shared Call/Line
> Appearance (SCA).  When implemented using the Session Initiation
> Protocol (SIP), it is referred to as shared appearances of an Address
> of Record (AOR) since SIP does not have the concept of lines.  This
> feature is commonly offered in IP Centrex services and IP-PBX
> offerings and is likely to be implemented on SIP IP telephones and
> SIP feature servers used in a business environment.  This document
> lists requirements and compares implementation options for this
> feature.  Extensions to the SIP dialog event package are proposed.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-bliss-shared-appearances-02.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss
>   


From HKaplan@acmepacket.com  Thu Mar 12 11:48:25 2009
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBC2C3A6AF5 for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 11:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HXaPuE1tqk+r for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 11:48:22 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id EF8C43A6962 for <bliss@ietf.org>; Thu, 12 Mar 2009 11:48:21 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.340.0; Thu, 12 Mar 2009 14:48:58 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Thu, 12 Mar 2009 14:48:58 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "marianne.mohali@orange-ftgroup.com" <marianne.mohali@orange-ftgroup.com>,  Jason Fischl <jason@counterpath.com>, Shida Schubert <shida@ntt-at.com>
Date: Thu, 12 Mar 2009 14:48:58 -0400
Thread-Topic: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
Thread-Index: Ack8KYP1Il2NqWRDShuhi9Ml+MJytAAACZcwGcYUTdA=
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail>
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2>
In-Reply-To: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "bliss@ietf.org" <bliss@ietf.org>
Subject: Re: [BLISS] TR: New Version Notification for	draft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 18:48:26 -0000

Hi Marianne and BLISS Chairs,
Why was this submitted as an individual-draft again and not a Working-Group=
 draft?

Didn't we have consensus in Dublin to make this a BLISS WG Item?

If we want to make History-Info the new white meat, we have to provide a tr=
ansition mechanism.  That transition mechanism can either be done different=
ly by every system, or be done the same way.=20

-hadriel

> -----Original Message-----
> From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] On Behalf Of
> marianne.mohali@orange-ftgroup.com
> Sent: Sunday, November 02, 2008 7:38 AM
> To: bliss@ietf.org
>=20
> A new version of the draft-mohali-diversion-history-info is available at
> the following URL :
> http://www.ietf.org/internet-drafts/draft-mohali-diversion-history-info-
> 01.txt
>=20
> Note that interworking between Diversion header and Voicemail URI has bee=
n
> added in addition to interworking from Diversion header to History-Info
> header.
>=20
> Regards,
>=20
> Marianne.

From shida@ntt-at.com  Thu Mar 12 20:15:34 2009
Return-Path: <shida@ntt-at.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 98A803A6A15 for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 20:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.057
X-Spam-Level: 
X-Spam-Status: No, score=-2.057 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gUJqz6XpDU+8 for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 20:15:33 -0700 (PDT)
Received: from gateway03.websitewelcome.com (gateway03.websitewelcome.com [69.93.196.21]) by core3.amsl.com (Postfix) with SMTP id C45123A657C for <bliss@ietf.org>; Thu, 12 Mar 2009 20:15:33 -0700 (PDT)
Received: (qmail 14622 invoked from network); 13 Mar 2009 03:16:13 -0000
Received: from gator465.hostgator.com (69.56.174.130) by gateway03.websitewelcome.com with SMTP; 13 Mar 2009 03:16:13 -0000
Received: from flh1ahc140.tky.mesh.ad.jp ([125.192.94.140]:59588 helo=[192.168.1.4]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1LhxsV-0001I0-Qf; Thu, 12 Mar 2009 22:16:08 -0500
Message-Id: <134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com>
From: Shida Schubert <shida@ntt-at.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 13 Mar 2009 09:00:31 +0900
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2> <E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail>
X-Mailer: Apple Mail (2.930.3)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
Cc: "bliss@ietf.org" <bliss@ietf.org>
Subject: Re: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 03:15:34 -0000

Hi Hadriel;

  As far as I know there was no clear consensus on the way forward of  
this draft,
and as you may recall, there was as much of an opposition as there was  
support
to work on this.

  Only thing I believe we agreed on was that, if we were to discuss  
the draft,
we were to use BLISS mailing list until we know what we are doing.

  Regards
   Shida

On 13-Mar-09, at 3:48 AM, Hadriel Kaplan wrote:

> Hi Marianne and BLISS Chairs,
> Why was this submitted as an individual-draft again and not a  
> Working-Group draft?
>
> Didn't we have consensus in Dublin to make this a BLISS WG Item?
>
> If we want to make History-Info the new white meat, we have to  
> provide a transition mechanism.  That transition mechanism can  
> either be done differently by every system, or be done the same way.
>
> -hadriel
>
>> -----Original Message-----
>> From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] On  
>> Behalf Of
>> marianne.mohali@orange-ftgroup.com
>> Sent: Sunday, November 02, 2008 7:38 AM
>> To: bliss@ietf.org
>>
>> A new version of the draft-mohali-diversion-history-info is  
>> available at
>> the following URL :
>> http://www.ietf.org/internet-drafts/draft-mohali-diversion-history-info-
>> 01.txt
>>
>> Note that interworking between Diversion header and Voicemail URI  
>> has been
>> added in addition to interworking from Diversion header to History- 
>> Info
>> header.
>>
>> Regards,
>>
>> Marianne.


From AUDET@nortel.com  Thu Mar 12 20:20:01 2009
Return-Path: <AUDET@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 139AF3A6999 for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 20:20:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.232
X-Spam-Level: 
X-Spam-Status: No, score=-4.232 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ww7fYp6tW6Vb for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 20:20:00 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id BF0B03A6879 for <bliss@ietf.org>; Thu, 12 Mar 2009 20:19:59 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n2D3KYY15010; Fri, 13 Mar 2009 03:20:34 GMT
Received: from 47.102.152.45 ([47.102.152.45]) by zrc2hxm0.corp.nortel.com ([47.103.123.71]) with Microsoft Exchange Server HTTP-DAV ;  Fri, 13 Mar 2009 03:20:29 +0000
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Thu, 12 Mar 2009 20:20:26 -0700
From: "Francois Audet" <audet@nortel.com>
To: Alan Johnston <alan@sipstation.com>, <bliss@ietf.org>
Message-ID: <C5DF1F0A.255F%audet@nortel.com>
Thread-Topic: [BLISS] I-D Action:draft-ietf-bliss-shared-appearances-02.txt
Thread-Index: AcmjiqcJC1b5e5BqTWmiMk8rZNV4sA==
In-Reply-To: <49B66C52.2050503@sipstation.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [BLISS] I-D Action:draft-ietf-bliss-shared-appearances-02.txt
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 03:20:01 -0000

Minor comment:

In Annex A, there is an example using Alert-Info with a file://ring.pcm.

I don't think this makes much sense. You can't really know the file
structure of the remote endpoint.

Rather, the example should show an http://biloxi.com/ring.pc type address.

In reality, I'd say that some URN would make more sense (as per
http://tools.ietf.org/html/draft-alexeitsev-bliss-alert-info-urns-01 for
example).


On Mar10 2009 06:34 , "Alan Johnston" <alan@sipstation.com> wrote:

> All,
> 
> Some of the major changes to this version of the document include:
> 
> - Publish only on appearance selection or seizure/call join or
> bridge/call take or pickup
> - Allow Appearance Agent to subscribe to dialog events if it is not a
> call stateful proxy or B2BUA(shown in Section 10.13)
> - Publications to the shared appearances AOR
> - Major rewrite of call flows
> 
> As always, comments most welcome.
> 
> Thanks,
> Alan
> 
> 
> Internet-Drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Basic Level of Interoperability for SIP
>> Services Working Group of the IETF.
>> 
>> 
>> Title           : Shared Appearances of a Session Initiation Protocol (SIP)
>> Address of Record (AOR)
>> Author(s)       : A. Johnston, et al.
>> Filename        : draft-ietf-bliss-shared-appearances-02.txt
>> Pages           : 65
>> Date            : 2009-03-09
>> 
>> This document describes the requirements and implementation of a
>> group telephony feature commonly known as Bridged Line Appearance
>> (BLA) or Multiple Line Appearance (MLA), or Shared Call/Line
>> Appearance (SCA).  When implemented using the Session Initiation
>> Protocol (SIP), it is referred to as shared appearances of an Address
>> of Record (AOR) since SIP does not have the concept of lines.  This
>> feature is commonly offered in IP Centrex services and IP-PBX
>> offerings and is likely to be implemented on SIP IP telephones and
>> SIP feature servers used in a business environment.  This document
>> lists requirements and compares implementation options for this
>> feature.  Extensions to the SIP dialog event package are proposed.
>> 
>> A URL for this Internet-Draft is:
>> 
http://www.ietf.org/internet-drafts/draft-ietf-bliss-shared-appearances-02.tx>>
t
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>>   
>> ------------------------------------------------------------------------
>> 
>> _______________________________________________
>> BLISS mailing list
>> BLISS@ietf.org
>> https://www.ietf.org/mailman/listinfo/bliss
>>   
> 
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss


From AUDET@nortel.com  Thu Mar 12 20:24:34 2009
Return-Path: <AUDET@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0D123A68CF for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 20:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.382
X-Spam-Level: 
X-Spam-Status: No, score=-4.382 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GkMv+xlRPRdj for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 20:24:33 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id A06B43A6879 for <bliss@ietf.org>; Thu, 12 Mar 2009 20:24:33 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n2D3OcD03104; Fri, 13 Mar 2009 03:24:38 GMT
Received: from 47.102.152.45 ([47.102.152.45]) by zrc2hxm0.corp.nortel.com ([47.103.123.71]) with Microsoft Exchange Server HTTP-DAV ;  Fri, 13 Mar 2009 03:24:56 +0000
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Thu, 12 Mar 2009 20:24:55 -0700
From: "Francois Audet" <audet@nortel.com>
To: Shida Schubert <shida@ntt-at.com>, Hadriel Kaplan <HKaplan@acmepacket.com>
Message-ID: <C5DF2017.2563%audet@nortel.com>
Thread-Topic: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
Thread-Index: Acmji0dfhQRDafZGT7GuR3bKq5IK8g==
In-Reply-To: <134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: "bliss@ietf.org" <bliss@ietf.org>
Subject: Re: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 03:24:34 -0000

I think with the 4244bis+target-URI, it will be a  lot easier to fulfill
what this draft is trying to do.

Provided that we are capable of "marking" the URIs in the target-URI draft
that correspond to a retargeting by mapping the URIs to a different URI.


On Mar12 2009 17:00 , "Shida Schubert" <shida@ntt-at.com> wrote:

> 
> Hi Hadriel;
> 
>   As far as I know there was no clear consensus on the way forward of
> this draft,
> and as you may recall, there was as much of an opposition as there was
> support
> to work on this.
> 
>   Only thing I believe we agreed on was that, if we were to discuss
> the draft,
> we were to use BLISS mailing list until we know what we are doing.
> 
>   Regards
>    Shida
> 
> On 13-Mar-09, at 3:48 AM, Hadriel Kaplan wrote:
> 
>> Hi Marianne and BLISS Chairs,
>> Why was this submitted as an individual-draft again and not a
>> Working-Group draft?
>> 
>> Didn't we have consensus in Dublin to make this a BLISS WG Item?
>> 
>> If we want to make History-Info the new white meat, we have to
>> provide a transition mechanism.  That transition mechanism can
>> either be done differently by every system, or be done the same way.
>> 
>> -hadriel
>> 
>>> -----Original Message-----
>>> From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] On
>>> Behalf Of
>>> marianne.mohali@orange-ftgroup.com
>>> Sent: Sunday, November 02, 2008 7:38 AM
>>> To: bliss@ietf.org
>>> 
>>> A new version of the draft-mohali-diversion-history-info is
>>> available at
>>> the following URL :
>>> http://www.ietf.org/internet-drafts/draft-mohali-diversion-history-info-
>>> 01.txt
>>> 
>>> Note that interworking between Diversion header and Voicemail URI
>>> has been
>>> added in addition to interworking from Diversion header to History-
>>> Info
>>> header.
>>> 
>>> Regards,
>>> 
>>> Marianne.
> 
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss


From HKaplan@acmepacket.com  Thu Mar 12 20:52:46 2009
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B97923A6ABB for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 20:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uUAP-0fWNJBS for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 20:52:45 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 9A5FB3A6A04 for <bliss@ietf.org>; Thu, 12 Mar 2009 20:52:45 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.340.0; Thu, 12 Mar 2009 23:53:22 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Thu, 12 Mar 2009 23:53:22 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Shida Schubert <shida@ntt-at.com>
Date: Thu, 12 Mar 2009 23:53:20 -0400
Thread-Topic: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
Thread-Index: AcmjihasELKxhYw1QkuXXSpUj0BhtgAADCdw
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail>
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2> <E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail> <134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com>
In-Reply-To: <134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "bliss@ietf.org" <bliss@ietf.org>
Subject: Re: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 03:52:46 -0000

Right someone pointed out to me offline that the minutes had no consensus o=
r any action.  I guess I remembered what I wanted to remember. :)

So then, to get such a discussion going...

Here are the Pro's to making it a WG doc as I see it:
1) It's Informational, not a Standards Track document.
2) Diversion is widely deployed, and if we want H-I to be widely deployed i=
n its place with fewer interop problems, discussing and agreeing on the rig=
ht conversion for a transition would be good.
3) We can make sure the semantics follows H-I as much as possible.
4) If we discuss it in a WG, and we find we need to add something to H-I, w=
e can discuss doing that.
5) Documenting interworking of non-IETF mechanisms to SIP is not without pr=
ecedent in the IETF, for example H.323 and PSTN/ISUP interworking.
6) If we don't document this, people will do it differently, and cause even=
 more interop or operational issues.
7) There is clear market demand for this function, since the main authors o=
f the draft are users of SIP.  If they want it, it's because they want a tr=
ansition to H-I to go smoothly, and it's within our purview to make that po=
ssible. =20
8) One could argue we all are to blame for them needing this, because we to=
ok a long time to come up with a standards-track solution and the market wa=
s forced to implement something, and Diversion had running code and solved =
their immediate need. =20

The Con's, as I see them:
1) From a procedural aspect, we would need to actually document Diversion i=
n something reference-able.
2) Documenting this may lead people to think Diversion is a standard, or th=
at it's fine to use instead of H-I, which could prolong a transition.
3) Diversion is a proprietary header and mechanism, and was not the path we=
 chose to go, and this sets a bad precedent.
4) This could lead us down a slippery-slope of documenting interworking to/=
from other proprietary mechanisms, which is waste of the WG's time.

Is that a fair and complete list?

Proposed action:
1) We can ask the RFC Editor to publish the Diversion draft as an informati=
onal individual-submission, and add lots of warning text (and perhaps Skull=
 and Cross-bones acii art ;) =20
2) We take draft-mohali-diversion-history-info-01 as a WG Item, and again m=
ake sure the text clearly articulates that Diversion is proprietary.

-hadriel

> -----Original Message-----
> From: Shida Schubert [mailto:shida@ntt-at.com]
> Sent: Thursday, March 12, 2009 8:01 PM
>=20
>   As far as I know there was no clear consensus on the way forward of
> this draft,
> and as you may recall, there was as much of an opposition as there was
> support
> to work on this.
>=20
>   Only thing I believe we agreed on was that, if we were to discuss
> the draft,
> we were to use BLISS mailing list until we know what we are doing.
>=20
>   Regards
>    Shida

From AUDET@nortel.com  Thu Mar 12 20:56:24 2009
Return-Path: <AUDET@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 95C173A6877 for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 20:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.113
X-Spam-Level: 
X-Spam-Status: No, score=-5.113 tagged_above=-999 required=5 tests=[AWL=-0.581, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eWFe2wW+Aj6a for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 20:56:23 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 885EB3A6A04 for <bliss@ietf.org>; Thu, 12 Mar 2009 20:56:23 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n2D3uoY18114; Fri, 13 Mar 2009 03:56:50 GMT
Received: from 47.103.119.44 ([47.103.119.44]) by zrc2hxm0.corp.nortel.com ([47.103.119.44]) with Microsoft Exchange Server HTTP-DAV ;  Fri, 13 Mar 2009 03:56:32 +0000
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2> <E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail> <134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com> <E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail>
Message-ID: <D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com>
From: "Francois Audet" <audet@nortel.com>
To: "Hadriel Kaplan" <HKaplan@acmepacket.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail>
thread-topic: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
thread-index: Acmjj7Jx8HzMr3bdRxuIJKdD4H7tRg==
Content-Type: text/plain; format=flowed; delsp=yes; charset="us-ascii"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (iPod Mail 5H11a)
Date: Thu, 12 Mar 2009 20:56:30 -0700
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 03:56:24 -0000

It is premature to make this a working group draft or publishing it  
until we have progressed on 4244bis/targetURI.

On Mar 12, 2009, at 20:53, "Hadriel Kaplan" <HKaplan@acmepacket.com>  
wrote:

>
> Right someone pointed out to me offline that the minutes had no  
> consensus or any action.  I guess I remembered what I wanted to  
> remember. :)
>
> So then, to get such a discussion going...
>
> Here are the Pro's to making it a WG doc as I see it:
> 1) It's Informational, not a Standards Track document.
> 2) Diversion is widely deployed, and if we want H-I to be widely  
> deployed in its place with fewer interop problems, discussing and  
> agreeing on the right conversion for a transition would be good.
> 3) We can make sure the semantics follows H-I as much as possible.
> 4) If we discuss it in a WG, and we find we need to add something to  
> H-I, we can discuss doing that.
> 5) Documenting interworking of non-IETF mechanisms to SIP is not  
> without precedent in the IETF, for example H.323 and PSTN/ISUP  
> interworking.
> 6) If we don't document this, people will do it differently, and  
> cause even more interop or operational issues.
> 7) There is clear market demand for this function, since the main  
> authors of the draft are users of SIP.  If they want it, it's  
> because they want a transition to H-I to go smoothly, and it's  
> within our purview to make that possible.
> 8) One could argue we all are to blame for them needing this,  
> because we took a long time to come up with a standards-track  
> solution and the market was forced to implement something, and  
> Diversion had running code and solved their immediate need.
>
> The Con's, as I see them:
> 1) From a procedural aspect, we would need to actually document  
> Diversion in something reference-able.
> 2) Documenting this may lead people to think Diversion is a  
> standard, or that it's fine to use instead of H-I, which could  
> prolong a transition.
> 3) Diversion is a proprietary header and mechanism, and was not the  
> path we chose to go, and this sets a bad precedent.
> 4) This could lead us down a slippery-slope of documenting  
> interworking to/from other proprietary mechanisms, which is waste of  
> the WG's time.
>
> Is that a fair and complete list?
>
> Proposed action:
> 1) We can ask the RFC Editor to publish the Diversion draft as an  
> informational individual-submission, and add lots of warning text  
> (and perhaps Skull and Cross-bones acii art ;)
> 2) We take draft-mohali-diversion-history-info-01 as a WG Item, and  
> again make sure the text clearly articulates that Diversion is  
> proprietary.
>
> -hadriel
>
>> -----Original Message-----
>> From: Shida Schubert [mailto:shida@ntt-at.com]
>> Sent: Thursday, March 12, 2009 8:01 PM
>>
>>  As far as I know there was no clear consensus on the way forward of
>> this draft,
>> and as you may recall, there was as much of an opposition as there  
>> was
>> support
>> to work on this.
>>
>>  Only thing I believe we agreed on was that, if we were to discuss
>> the draft,
>> we were to use BLISS mailing list until we know what we are doing.
>>
>>  Regards
>>   Shida
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss

From HKaplan@acmepacket.com  Thu Mar 12 21:06:00 2009
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECF093A6A1D for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 21:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M725U+BPQ+16 for <bliss@core3.amsl.com>; Thu, 12 Mar 2009 21:06:00 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 2D97D3A6A04 for <bliss@ietf.org>; Thu, 12 Mar 2009 21:06:00 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.340.0; Fri, 13 Mar 2009 00:06:37 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Fri, 13 Mar 2009 00:06:34 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Francois Audet <audet@nortel.com>
Date: Fri, 13 Mar 2009 00:06:25 -0400
Thread-Topic: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
Thread-Index: Acmjj7Jx8HzMr3bdRxuIJKdD4H7tRgAALoFw
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail>
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2> <E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail> <134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com> <E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail> <D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com>
In-Reply-To: <D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "bliss@ietf.org" <bliss@ietf.org>
Subject: Re: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 04:06:01 -0000

Then we will once again fail our customers in delivering a timely solution =
to their problems.

-hadriel

> -----Original Message-----
> From: Francois Audet [mailto:audet@nortel.com]
> Sent: Thursday, March 12, 2009 11:57 PM
>=20
> It is premature to make this a working group draft or publishing it
> until we have progressed on 4244bis/targetURI.

From marianne.mohali@orange-ftgroup.com  Fri Mar 13 02:52:53 2009
Return-Path: <marianne.mohali@orange-ftgroup.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7CC23A6B16 for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 02:52:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.051
X-Spam-Level: 
X-Spam-Status: No, score=-0.051 tagged_above=-999 required=5 tests=[AWL=3.198,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c+pX6Y1rHYfF for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 02:52:46 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 753FE3A6AA5 for <bliss@ietf.org>; Fri, 13 Mar 2009 02:52:27 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 13 Mar 2009 10:52:52 +0100
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
Date: Fri, 13 Mar 2009 10:52:52 +0100
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026064C8505@ftrdmel2>
In-Reply-To: <134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
Thread-Index: AcmjijPCrCKCf48lRwajgLCM7bCl0QAMtdVg
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2> <E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail> <134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com>
From: <marianne.mohali@orange-ftgroup.com>
To: <shida@ntt-at.com>, <HKaplan@acmepacket.com>
X-OriginalArrivalTime: 13 Mar 2009 09:52:52.0742 (UTC) FILETIME=[79FD2A60:01C9A3C1]
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: New Version Notification for draft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 09:52:53 -0000

Hi all,

I can just say that it is true that in Dublin there was not a clear =
consensus but it is not fair to say "there was as much of an opposition =
as there was support to work on this." The opposition was on the fact =
that Diversion was not an IETF draft (as expired) but many people was =
saying that this argument was not valid because there is still the =
possibility to edit the draft as historical.

Regards
Marianne

-----Message d'origine-----
De : Shida Schubert [mailto:shida@ntt-at.com]=20
Envoy=E9 : vendredi 13 mars 2009 01:01
=C0 : Hadriel Kaplan
Cc : MOHALI Marianne RD-CORE-ISS; Jason Fischl; bliss@ietf.org
Objet : Re: [BLISS] TR: New Version Notification for =
draft-mohali-diversion-history-info-01


Hi Hadriel;

  As far as I know there was no clear consensus on the way forward of =
this draft, and as you may recall, there was as much of an opposition as =
there was support to work on this.

  Only thing I believe we agreed on was that, if we were to discuss the =
draft, we were to use BLISS mailing list until we know what we are =
doing.

  Regards
   Shida

On 13-Mar-09, at 3:48 AM, Hadriel Kaplan wrote:

> Hi Marianne and BLISS Chairs,
> Why was this submitted as an individual-draft again and not a=20
> Working-Group draft?
>
> Didn't we have consensus in Dublin to make this a BLISS WG Item?
>
> If we want to make History-Info the new white meat, we have to provide =

> a transition mechanism.  That transition mechanism can either be done=20
> differently by every system, or be done the same way.
>
> -hadriel


From marianne.mohali@orange-ftgroup.com  Fri Mar 13 03:12:32 2009
Return-Path: <marianne.mohali@orange-ftgroup.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 588233A6AA5 for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 03:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CXutnNb4X16C for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 03:12:25 -0700 (PDT)
Received: from R-MAIL1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id 9D8A83A6A60 for <bliss@ietf.org>; Fri, 13 Mar 2009 03:12:21 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 13 Mar 2009 11:12:50 +0100
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, 13 Mar 2009 11:12:38 +0100
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] TR: New Version Notification fordraft-mohali-diversion-history-info-01
Thread-Index: Acmjj7Jx8HzMr3bdRxuIJKdD4H7tRgAALoFwAAx23pA=
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2><E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail><134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail><D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com> <E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail>
From: <marianne.mohali@orange-ftgroup.com>
To: <HKaplan@acmepacket.com>, <audet@nortel.com>
X-OriginalArrivalTime: 13 Mar 2009 10:12:50.0397 (UTC) FILETIME=[43D8D0D0:01C9A3C4]
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: New Version Notification fordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 10:12:32 -0000

Hi,
=20
I don't understand why this is premature. On the contrary, this is late.
It is long time that Diversion header is implemented and now there are
implementations based on History-Info header (RFC4244)(Here I'm just
talking about call frowarding service). RFC4244 will still be as it is
and making the History-info header interwork with the Diversion header
will still be needed as RFC4244 is implemented.=20
In the other hand, the work in progress on 4244bis/targetURI could takes
time and interworking with Diversion header will may be also needed with
the "new History-Info".=20

Regards
Marianne

> -----Original Message-----
> From: Francois Audet [mailto:audet@nortel.com]
> Sent: Thursday, March 12, 2009 11:57 PM
>=20
> It is premature to make this a working group draft or publishing it=20
> until we have progressed on 4244bis/targetURI.
_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss

From mary.barnes@nortel.com  Fri Mar 13 07:17:03 2009
Return-Path: <mary.barnes@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86F313A6883 for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 07:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.421
X-Spam-Level: 
X-Spam-Status: No, score=-6.421 tagged_above=-999 required=5 tests=[AWL=0.178,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bj+57OEcOosl for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 07:16:56 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 280593A684A for <bliss@ietf.org>; Fri, 13 Mar 2009 07:16:55 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n2DEHJn16988; Fri, 13 Mar 2009 14:17:19 GMT
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
Date: Fri, 13 Mar 2009 09:19:23 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF1CD7F390@zrc2hxm0.corp.nortel.com>
In-Reply-To: <7DBAFEC6A76F3E42817DF1EBE64CB026064C8505@ftrdmel2>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] TR: New Version Notification fordraft-mohali-diversion-history-info-01
Thread-Index: AcmjijPCrCKCf48lRwajgLCM7bCl0QAMtdVgAAk2yWA=
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2><E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail><134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com> <7DBAFEC6A76F3E42817DF1EBE64CB026064C8505@ftrdmel2>
From: "Mary Barnes" <mary.barnes@nortel.com>
To: <marianne.mohali@orange-ftgroup.com>, <shida@ntt-at.com>, <HKaplan@acmepacket.com>
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: New Version Notification fordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 14:17:03 -0000

If you go through the minutes, you can count the number of statements =
for and those against, and it was fairly evenly divided, so it is =
totally fair and indeed accurate to say so.=20
Here's my lists of Pros and cons.

Pros:
=3D=3D=3D=3D=3D
1) Provides a single document (rather than vendor, SP or other SDO =
specific documents) for something that is fairly widely deployed.


Cons:
=3D=3D=3D=3D=3D=3D
1) In order for the document to be useful and accurate, it effectively =
is standarizing the Diversion header. Diversion would need to be =
registered, normative "i"s dotted and "t"s crossed, etc. You can't get =
around that.=20
2) Re-enforces the idea that what we do in standards isn't translating =
to the real world - History-Info was there quite some time ago, but =
folks chose not to implement.=20
3) Leading to my next point, that as Hadriel noted, this sets the =
precendent for documenting all sorts of proprietary interworking (and =
there's a lot of that).  In my mind, this is just reverse engineering =
the standards from product implementations, which is more the purview of =
groups like SIP Forum or one of the Service Provider focused =
organizations to provide guidelines on the Industry standards vs IETF =
standards - there's already lots of cross-pollination amongst the =
various organizations.  If we want to do this (in IETF) we need to =
acknowledge this is what we're doing, but it certainly doesn't seem to =
be the charter of any of the current RAI WGs.=20
4) From a technical perspective, there is the potential for loss of =
information when mapping from History-Info -> Diversion -> History-Info. =
My suggestion would be to just carry both headers through the network.
5) This puts the burden of inter-working on the vendors that have gone =
the standards route
6) Successfully implementing inter-working is likely more work than =
implementing HI (i.e., carriers are wanting vendors to implement a =
standard that's yet to be clearly defined rather than implementing an =
existing RFC).
7) Interworking has a negative impact on capacity - i.e., overall it's =
more work to do the interworking than implement 4244 (although perhaps =
in this day and age this isn't so much an issue - in the old days, =
capacity was an important consideration).=20
=20
And, I'm not sure if this is a PRO or a CON, but this is a fine example =
of the ineffectiveness of RAI in some areas -  Those of us that worked =
on History-Info would honestly have been perfectly happy had Diversion =
been accepted almost a decade ago, as we could have built upon that.  It =
wasn't, so we orginally went in with a proposal that used a header that =
was planned to be standardized (remote-party-id). That idea was soundly =
rejected and the WG consensus was to develop a very general building =
block.  So, the WG spent the usual several long and painful years =
developing RFC 4244. The most interesting aspect of this is that some of =
the folks most vehemently opposed to History-Info in the WG because it =
could be used for all these legacy services, now believe we should =
progress this document. Certainly, this based on the current business =
environment, but it's also an example of the philosophical split in the =
RAI area - some folks are here (as already noted) based on corporate =
objectives, others might be here to support corporate objectives, but =
they also believe in the fundamental e2e principles and still others =
have no corporate affiliation and thus may not need to compromise.  So, =
it seems in the end, we're getting the worst of both worlds and it's =
exemplified with this document IMHO.  =20

That all said, if this document were written from a more general =
perspective of how to interwork legacy protocol information into =
History-Info, then I would support the work. But, interworking a =
proprietary SIP header with a standardized SIP header sets a horrible =
precendent IMHO.  If another SDO wants to do so, then that's fine - I =
don't have any say in other SDOs and there's seems far more inline what =
many of them do regularly anyways.=20

Regards,
Mary.=20



-----Original Message-----
From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] On Behalf =
Of marianne.mohali@orange-ftgroup.com
Sent: Friday, March 13, 2009 4:53 AM
To: shida@ntt-at.com; HKaplan@acmepacket.com
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: New Version Notification =
fordraft-mohali-diversion-history-info-01

Hi all,

I can just say that it is true that in Dublin there was not a clear =
consensus but it is not fair to say "there was as much of an opposition =
as there was support to work on this." The opposition was on the fact =
that Diversion was not an IETF draft (as expired) but many people was =
saying that this argument was not valid because there is still the =
possibility to edit the draft as historical.

Regards
Marianne

-----Message d'origine-----
De : Shida Schubert [mailto:shida@ntt-at.com] Envoy=E9 : vendredi 13 =
mars 2009 01:01 =C0 : Hadriel Kaplan Cc : MOHALI Marianne RD-CORE-ISS; =
Jason Fischl; bliss@ietf.org Objet : Re: [BLISS] TR: New Version =
Notification for draft-mohali-diversion-history-info-01


Hi Hadriel;

  As far as I know there was no clear consensus on the way forward of =
this draft, and as you may recall, there was as much of an opposition as =
there was support to work on this.

  Only thing I believe we agreed on was that, if we were to discuss the =
draft, we were to use BLISS mailing list until we know what we are =
doing.

  Regards
   Shida

On 13-Mar-09, at 3:48 AM, Hadriel Kaplan wrote:

> Hi Marianne and BLISS Chairs,
> Why was this submitted as an individual-draft again and not a=20
> Working-Group draft?
>
> Didn't we have consensus in Dublin to make this a BLISS WG Item?
>
> If we want to make History-Info the new white meat, we have to provide =

> a transition mechanism.  That transition mechanism can either be done=20
> differently by every system, or be done the same way.
>
> -hadriel

_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss

From mary.barnes@nortel.com  Fri Mar 13 07:18:28 2009
Return-Path: <mary.barnes@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 524993A6991 for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 07:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.423
X-Spam-Level: 
X-Spam-Status: No, score=-6.423 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sbQ-iJug2CNH for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 07:18:21 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 476503A6883 for <bliss@ietf.org>; Fri, 13 Mar 2009 07:18:21 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n2DEItn17509; Fri, 13 Mar 2009 14:18:55 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: Fri, 13 Mar 2009 09:21:12 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com>
In-Reply-To: <7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] TR: New Version Notificationfordraft-mohali-diversion-history-info-01
Thread-Index: Acmjj7Jx8HzMr3bdRxuIJKdD4H7tRgAALoFwAAx23pAACR3HAA==
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2><E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail><134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail><D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail> <7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2>
From: "Mary Barnes" <mary.barnes@nortel.com>
To: <marianne.mohali@orange-ftgroup.com>, <HKaplan@acmepacket.com>, "Francois Audet" <audet@nortel.com>
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: New Version Notificationfordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 14:18:28 -0000

Hi Marianne,

And, the standardization of this document could well take longer than it
will take to complete 4244bis. Per my list of pros/cons, to be correct
and useful, this document is effectively standardizing Diversion header,
which is actually more work than what's being done in the 4244bis and
target-uri docs. So, you're waiting either way.=20

Regards,
Mary.=20

-----Original Message-----
From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] On Behalf
Of marianne.mohali@orange-ftgroup.com
Sent: Friday, March 13, 2009 5:13 AM
To: HKaplan@acmepacket.com; Audet, Francois (SC100:3055)
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: New Version
Notificationfordraft-mohali-diversion-history-info-01

Hi,
=20
I don't understand why this is premature. On the contrary, this is late.
It is long time that Diversion header is implemented and now there are
implementations based on History-Info header (RFC4244)(Here I'm just
talking about call frowarding service). RFC4244 will still be as it is
and making the History-info header interwork with the Diversion header
will still be needed as RFC4244 is implemented.=20
In the other hand, the work in progress on 4244bis/targetURI could takes
time and interworking with Diversion header will may be also needed with
the "new History-Info".=20

Regards
Marianne

> -----Original Message-----
> From: Francois Audet [mailto:audet@nortel.com]
> Sent: Thursday, March 12, 2009 11:57 PM
>=20
> It is premature to make this a working group draft or publishing it=20
> until we have progressed on 4244bis/targetURI.
_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss
_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss

From alan@sipstation.com  Fri Mar 13 07:20:34 2009
Return-Path: <alan@sipstation.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E9E43A6A3D for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 07:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MDw5plzqFWgE for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 07:20:27 -0700 (PDT)
Received: from mho-02-bos.mailhop.org (mho-02-bos.mailhop.org [63.208.196.179]) by core3.amsl.com (Postfix) with ESMTP id EF2203A684A for <bliss@ietf.org>; Fri, 13 Mar 2009 07:20:26 -0700 (PDT)
Received: from 71-81-68-141.dhcp.stls.mo.charter.com ([71.81.68.141] helo=alan-johnstons-powerbook-g4-17.local) by mho-02-bos.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <alan@sipstation.com>) id 1Li8G0-000GDJ-Kp; Fri, 13 Mar 2009 14:21:05 +0000
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 71.81.68.141
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/cGn5XXodMfWF+OMgVLBCHO2FameM3gmw=
Message-ID: <49BA6BCF.4060300@sipstation.com>
Date: Fri, 13 Mar 2009 09:21:03 -0500
From: Alan Johnston <alan@sipstation.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
References: <C5DF1F0A.255F%audet@nortel.com>
In-Reply-To: <C5DF1F0A.255F%audet@nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: bliss@ietf.org
Subject: Re: [BLISS] I-D Action:draft-ietf-bliss-shared-appearances-02.txt
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 14:20:34 -0000

Francois,

I agree completely.  I meant to include a reference to the Alert-Info 
URN draft but forgot.

If we need this Alert-Info functionality, we need the URN functionality 
in draft-alexeitsev-bliss-alert-info-urns.

Thanks,
Alan



Francois Audet wrote:
> Minor comment:
>
> In Annex A, there is an example using Alert-Info with a file://ring.pcm.
>
> I don't think this makes much sense. You can't really know the file
> structure of the remote endpoint.
>
> Rather, the example should show an http://biloxi.com/ring.pc type address.
>
> In reality, I'd say that some URN would make more sense (as per
> http://tools.ietf.org/html/draft-alexeitsev-bliss-alert-info-urns-01 for
> example).
>
>
> On Mar10 2009 06:34 , "Alan Johnston" <alan@sipstation.com> wrote:
>
>   
>> All,
>>
>> Some of the major changes to this version of the document include:
>>
>> - Publish only on appearance selection or seizure/call join or
>> bridge/call take or pickup
>> - Allow Appearance Agent to subscribe to dialog events if it is not a
>> call stateful proxy or B2BUA(shown in Section 10.13)
>> - Publications to the shared appearances AOR
>> - Major rewrite of call flows
>>
>> As always, comments most welcome.
>>
>> Thanks,
>> Alan
>>
>>
>> Internet-Drafts@ietf.org wrote:
>>     
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>> This draft is a work item of the Basic Level of Interoperability for SIP
>>> Services Working Group of the IETF.
>>>
>>>
>>> Title           : Shared Appearances of a Session Initiation Protocol (SIP)
>>> Address of Record (AOR)
>>> Author(s)       : A. Johnston, et al.
>>> Filename        : draft-ietf-bliss-shared-appearances-02.txt
>>> Pages           : 65
>>> Date            : 2009-03-09
>>>
>>> This document describes the requirements and implementation of a
>>> group telephony feature commonly known as Bridged Line Appearance
>>> (BLA) or Multiple Line Appearance (MLA), or Shared Call/Line
>>> Appearance (SCA).  When implemented using the Session Initiation
>>> Protocol (SIP), it is referred to as shared appearances of an Address
>>> of Record (AOR) since SIP does not have the concept of lines.  This
>>> feature is commonly offered in IP Centrex services and IP-PBX
>>> offerings and is likely to be implemented on SIP IP telephones and
>>> SIP feature servers used in a business environment.  This document
>>> lists requirements and compares implementation options for this
>>> feature.  Extensions to the SIP dialog event package are proposed.
>>>
>>> A URL for this Internet-Draft is:
>>>
>>>       
> http://www.ietf.org/internet-drafts/draft-ietf-bliss-shared-appearances-02.tx>>
> t
>   
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> Below is the data which will enable a MIME compliant mail reader
>>> implementation to automatically retrieve the ASCII version of the
>>> Internet-Draft.
>>>   
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> BLISS mailing list
>>> BLISS@ietf.org
>>> https://www.ietf.org/mailman/listinfo/bliss
>>>   
>>>       
>> _______________________________________________
>> BLISS mailing list
>> BLISS@ietf.org
>> https://www.ietf.org/mailman/listinfo/bliss
>>     
>
>
>   


From HKaplan@acmepacket.com  Fri Mar 13 07:56:44 2009
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63B2F28C0EE for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 07:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level: 
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vu-dtsMTR0bG for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 07:56:38 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 5ADD028C0E8 for <bliss@ietf.org>; Fri, 13 Mar 2009 07:56:38 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.340.0; Fri, 13 Mar 2009 10:57:16 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Fri, 13 Mar 2009 10:57:16 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Mary Barnes <mary.barnes@nortel.com>, "marianne.mohali@orange-ftgroup.com" <marianne.mohali@orange-ftgroup.com>, "shida@ntt-at.com" <shida@ntt-at.com>
Date: Fri, 13 Mar 2009 10:57:15 -0400
Thread-Topic: [BLISS] TR: New Version Notification fordraft-mohali-diversion-history-info-01
Thread-Index: AcmjijPCrCKCf48lRwajgLCM7bCl0QAMtdVgAAk2yWAAAdn/gA==
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC314E76C58ED@mail>
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2><E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail><134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com> <7DBAFEC6A76F3E42817DF1EBE64CB026064C8505@ftrdmel2> <1ECE0EB50388174790F9694F77522CCF1CD7F390@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1CD7F390@zrc2hxm0.corp.nortel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "bliss@ietf.org" <bliss@ietf.org>
Subject: Re: [BLISS] TR: New Version Notification fordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 14:56:44 -0000

> -----Original Message-----
> From: Mary Barnes [mailto:mary.barnes@nortel.com]
> Sent: Friday, March 13, 2009 10:19 AM
>=20
> Cons:
> =3D=3D=3D=3D=3D=3D
> 1) In order for the document to be useful and accurate, it effectively is
> standarizing the Diversion header. Diversion would need to be registered,
> normative "i"s dotted and "t"s crossed, etc. You can't get around that.

Of course you can.  The Diversion draft can be submitted as historical for =
information only.  I believe there's even precedence for this in the IETF, =
where proprietary protocols or extensions were documented simply so that pe=
ople could figure out how to interwork away from them.


> 2) Re-enforces the idea that what we do in standards isn't translating to
> the real world - History-Info was there quite some time ago, but folks
> chose not to implement.

We need to be honest with ourselves about this.  We screwed up.  We took a =
really long time, making a more extensible/flexible/pretty mechanism, in a =
more general way, instead of solving the specific problem at hand.  I think=
 we've all expressed our frustration recently about this type of problem, a=
nd hopefully the re-org and new model will improve things.  But that doesn'=
t absolve us of responsibility for Diversion's prevalence.  We can't go bla=
me 3GPP or OMA or whatever for this - it was *us*.


> 3) Leading to my next point, that as Hadriel noted, this sets the
> precendent for documenting all sorts of proprietary interworking (and
> there's a lot of that).  In my mind, this is just reverse engineering the
> standards from product implementations, which is more the purview of
> groups like SIP Forum or one of the Service Provider focused organization=
s
> to provide guidelines on the Industry standards vs IETF standards -
> there's already lots of cross-pollination amongst the various
> organizations.  If we want to do this (in IETF) we need to acknowledge
> this is what we're doing, but it certainly doesn't seem to be the charter
> of any of the current RAI WGs.

If it were just one vendor that implemented it, I would find it a lot more =
troublesome in terms of precedence setting.  But it wasn't one vendor.  Man=
y vendors implemented it.  It's effectively a defacto standard.


> 4) From a technical perspective, there is the potential for loss of
> information when mapping from History-Info -> Diversion -> History-Info.
> My suggestion would be to just carry both headers through the network.

That won't work, and we discussed why that won't work in Dublin.


> 5) This puts the burden of inter-working on the vendors that have gone th=
e
> standards route

They already have that burden, because of how long it took us.  The incumbe=
nt deployed legacy gear almost always has the upper hand in this regard.

-hadriel

From marianne.mohali@orange-ftgroup.com  Fri Mar 13 08:20:16 2009
Return-Path: <marianne.mohali@orange-ftgroup.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE3263A6BA4 for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 08:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[AWL=1.599,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YxJYG0c4ODY1 for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 08:20:10 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 669B93A6991 for <bliss@ietf.org>; Fri, 13 Mar 2009 08:20:07 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 13 Mar 2009 16:20:44 +0100
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
Date: Fri, 13 Mar 2009 16:20:41 +0100
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026064C86FC@ftrdmel2>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] TR: New Version Notificationfordraft-mohali-diversion-history-info-01
Thread-Index: Acmjj7Jx8HzMr3bdRxuIJKdD4H7tRgAALoFwAAx23pAACR3HAAAA+wkQ
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2><E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail><134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail><D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail> <7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2> <1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com>
From: <marianne.mohali@orange-ftgroup.com>
To: <mary.barnes@nortel.com>, <HKaplan@acmepacket.com>, <audet@nortel.com>
X-OriginalArrivalTime: 13 Mar 2009 15:20:44.0499 (UTC) FILETIME=[47451230:01C9A3EF]
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: New Version Notificationfordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 15:20:16 -0000

Hi Mary,

I am not comparing Diversion header and History-Info header. In fact, I =
don't care if Diversion header is not standartized. The problem is that =
it has been implemented and not only by one implementor. I just try to =
recommend a solution to a real issue towards the standardized solution =
(like for other cases as H323 interworking).
History-Info header has been standardized for many reasons, after many =
time and discussions. It is the normalized solution and this is not the =
subject of the draft. The work on 4244bis/target-uri is necessary and =
good but a separate topic.

Regards,
Marianne=20

-----Message d'origine-----
De : Mary Barnes [mailto:mary.barnes@nortel.com]=20
Envoy=E9 : vendredi 13 mars 2009 15:21
=C0 : MOHALI Marianne RD-CORE-ISS; HKaplan@acmepacket.com; Francois =
Audet
Cc : bliss@ietf.org
Objet : RE: [BLISS] TR: New Version =
Notificationfordraft-mohali-diversion-history-info-01

Hi Marianne,

And, the standardization of this document could well take longer than it =
will take to complete 4244bis. Per my list of pros/cons, to be correct =
and useful, this document is effectively standardizing Diversion header, =
which is actually more work than what's being done in the 4244bis and =
target-uri docs. So, you're waiting either way.=20

Regards,
Mary.=20

-----Original Message-----
From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] On Behalf =
Of marianne.mohali@orange-ftgroup.com
Sent: Friday, March 13, 2009 5:13 AM
To: HKaplan@acmepacket.com; Audet, Francois (SC100:3055)
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: New Version
Notificationfordraft-mohali-diversion-history-info-01

Hi,
=20
I don't understand why this is premature. On the contrary, this is late.
It is long time that Diversion header is implemented and now there are =
implementations based on History-Info header (RFC4244)(Here I'm just =
talking about call frowarding service). RFC4244 will still be as it is =
and making the History-info header interwork with the Diversion header =
will still be needed as RFC4244 is implemented.=20
In the other hand, the work in progress on 4244bis/targetURI could takes =
time and interworking with Diversion header will may be also needed with =
the "new History-Info".=20

Regards
Marianne

> -----Original Message-----
> From: Francois Audet [mailto:audet@nortel.com]
> Sent: Thursday, March 12, 2009 11:57 PM
>=20
> It is premature to make this a working group draft or publishing it=20
> until we have progressed on 4244bis/targetURI.
_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss
_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss

From mary.barnes@nortel.com  Fri Mar 13 08:23:25 2009
Return-Path: <mary.barnes@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 72B6228C174 for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 08:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.431
X-Spam-Level: 
X-Spam-Status: No, score=-6.431 tagged_above=-999 required=5 tests=[AWL=0.168,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JklPoboImfQl for <bliss@core3.amsl.com>; Fri, 13 Mar 2009 08:23:19 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id DC49828C177 for <bliss@ietf.org>; Fri, 13 Mar 2009 08:23:14 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n2DFNI402221; Fri, 13 Mar 2009 15:23:18 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: Fri, 13 Mar 2009 10:26:10 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF1CD7F5D6@zrc2hxm0.corp.nortel.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC314E76C58ED@mail>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] TR: New Version Notification fordraft-mohali-diversion-history-info-01
Thread-Index: AcmjijPCrCKCf48lRwajgLCM7bCl0QAMtdVgAAk2yWAAAdn/gAABBrGA
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2><E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail><134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com> <7DBAFEC6A76F3E42817DF1EBE64CB026064C8505@ftrdmel2> <1ECE0EB50388174790F9694F77522CCF1CD7F390@zrc2hxm0.corp.nortel.com> <E6C2E8958BA59A4FB960963D475F7AC314E76C58ED@mail>
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Hadriel Kaplan" <HKaplan@acmepacket.com>, <marianne.mohali@orange-ftgroup.com>, <shida@ntt-at.com>
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: New Version Notification fordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 15:23:25 -0000

Responses below [MB].=20

-----Original Message-----
From: Hadriel Kaplan [mailto:HKaplan@acmepacket.com]=20
Sent: Friday, March 13, 2009 9:57 AM
To: Barnes, Mary (RICH2:AR00); marianne.mohali@orange-ftgroup.com;
shida@ntt-at.com
Cc: bliss@ietf.org
Subject: RE: [BLISS] TR: New Version Notification
fordraft-mohali-diversion-history-info-01



> -----Original Message-----
> From: Mary Barnes [mailto:mary.barnes@nortel.com]
> Sent: Friday, March 13, 2009 10:19 AM
>=20
> Cons:
> =3D=3D=3D=3D=3D=3D
> 1) In order for the document to be useful and accurate, it effectively

> is standarizing the Diversion header. Diversion would need to be=20
> registered, normative "i"s dotted and "t"s crossed, etc. You can't get
around that.

Of course you can.  The Diversion draft can be submitted as historical
for information only.  I believe there's even precedence for this in the
IETF, where proprietary protocols or extensions were documented simply
so that people could figure out how to interwork away from them.
[MB] I agree that they have indeed published proprietary protocols, but
I am not at all aware of a case where they have published a new header
for a protocol that provides the same functionality as a standardized
header.  Why will it not work for another SDO to describe Diversion and
then just register the header?  This doc could reference the other SDO
document (there is a precendent for that). Indeed, even when docs are
published by the RFC editor, the expert review requires consideration as
to whether the work duplicates existing IETF work. Now, proprietary
protocols can be considered okay, but this isn't a protocol we're
talking about - it's a header.  And, even with independent submissions,
the IESG (per BCP 92) still  checks  for conflicts between the work of
the IETF and the documents submitted. And, as far as I understand it (at
least per today's process) "Historic" is not appropriate for this header
- that's used for things that are obsolete. [/MB]


> 2) Re-enforces the idea that what we do in standards isn't translating

> to the real world - History-Info was there quite some time ago, but=20
> folks chose not to implement.

We need to be honest with ourselves about this.  We screwed up.  We took
a really long time, making a more extensible/flexible/pretty mechanism,
in a more general way, instead of solving the specific problem at hand.
I think we've all expressed our frustration recently about this type of
problem, and hopefully the re-org and new model will improve things.
But that doesn't absolve us of responsibility for Diversion's
prevalence.  We can't go blame 3GPP or OMA or whatever for this - it was
*us*.
[MB] In this case, I'm not blaming other SDOs. The fault in my opinion
is with the vendors that chose not to implement the standards and SPs
that don't expect vendors to implement the standards. And, that's fine -
if we want to say we messed up, then let's obsolete 4244 and jump back
on the Diversion band wagon and extend it to do the other things we want
to do. I just cannot see how having two ways to do the same thing
enhances interoperability or maintainability in the long run. [/MB]


> 3) Leading to my next point, that as Hadriel noted, this sets the=20
> precendent for documenting all sorts of proprietary interworking (and=20
> there's a lot of that).  In my mind, this is just reverse engineering=20
> the standards from product implementations, which is more the purview=20
> of groups like SIP Forum or one of the Service Provider focused=20
> organizations to provide guidelines on the Industry standards vs IETF=20
> standards - there's already lots of cross-pollination amongst the=20
> various organizations.  If we want to do this (in IETF) we need to=20
> acknowledge this is what we're doing, but it certainly doesn't seem to

> be the charter of any of the current RAI WGs.

If it were just one vendor that implemented it, I would find it a lot
more troublesome in terms of precedence setting.  But it wasn't one
vendor.  Many vendors implemented it.  It's effectively a defacto
standard.
[MB] It was a trickle down thing - if vendor x wanted to I/W with vendor
y that only implemented diversion, then vendor X had to implement it as
well as did any other vendor that wanted to I/W with vendor Y, who for
whatever reason didn't implement History-Info. IMHO, 4 or 5 years ago,
this wouldn't have been a problem, but when a specs been out for 4+
years, then I think it's a different issue. I still can't fathom that
none of these vendors have made any changes to their products in the
past 4+ years, that they couldn't have added History-Info.[/MB]


> 4) From a technical perspective, there is the potential for loss of=20
> information when mapping from History-Info -> Diversion ->
History-Info.
> My suggestion would be to just carry both headers through the network.

That won't work, and we discussed why that won't work in Dublin.
[MB] The only reason I can see (as I don't recall the Dublin discussion)
is that vendor y from my example doesn't want to change a line of code
to do anything new. [/MB]


> 5) This puts the burden of inter-working on the vendors that have gone

> the standards route

They already have that burden, because of how long it took us.  The
incumbent deployed legacy gear almost always has the upper hand in this
regard.
[MB] I don't agree - History-Info has been out for quite some time and
again, I can't fathom that folks haven't made some enhancements to their
products. Now, perhaps, no one told them, but then that's not the IETF's
fault. [/MB]

-hadriel

From dworley@nortel.com  Wed Mar 18 15:03:14 2009
Return-Path: <dworley@nortel.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31EDA3A68DA for <bliss@core3.amsl.com>; Wed, 18 Mar 2009 15:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.782
X-Spam-Level: 
X-Spam-Status: No, score=-5.782 tagged_above=-999 required=5 tests=[AWL=-0.672, BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jGiX8bX7Mm4x for <bliss@core3.amsl.com>; Wed, 18 Mar 2009 15:03:13 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 41DD43A688D for <bliss@ietf.org>; Wed, 18 Mar 2009 15:03:13 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n2IM3VV10361 for <bliss@ietf.org>; Wed, 18 Mar 2009 22:03:31 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 18 Mar 2009 18:03:54 -0400
From: "Dale Worley" <dworley@nortel.com>
To: BLISS <bliss@ietf.org>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com>
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2> <E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail> <134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com> <E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail> <D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com> <E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail> <7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2> <1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Wed, 18 Mar 2009 18:03:53 -0400
Message-Id: <1237413833.3807.50.camel@victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Mar 2009 22:03:54.0248 (UTC) FILETIME=[6D8C9880:01C9A815]
Subject: Re: [BLISS] TR: New Version	Notificationfordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2009 22:03:14 -0000

On Fri, 2009-03-13 at 09:21 -0500, Mary Barnes wrote:
> And, the standardization of this document could well take longer than it
> will take to complete 4244bis. Per my list of pros/cons, to be correct
> and useful, this document is effectively standardizing Diversion header,
> which is actually more work than what's being done in the 4244bis and
> target-uri docs. So, you're waiting either way. 

The wretched reality is that you can't solidify interoperation between
Diversion and History-Info until you get *both* headers defined, and
everyone agrees that Diversion is not fully defined and the definition
of History-Info needs to be revised.

As for which header occupied the promised land first, it's not
immediately clear:  draft-levy-sip-diversion-08 existed in 2004, and
draft-barnes-sipping-history-info-02 existed in 2003.

Any even slight official blessing of conversion between the two will
lead people to consider that SIP supports both headers equally, which
increase the complexity of the protocol and implementations.

On the other hand, there is no reason that the *work* can't go on, even
if it receives no support from the IETF.  Indeed, it's clear that there
are market support for doing the work, which means that the work *will*
go on.

We can exploit that -- Let us delay *official* recognition until it's
clear whether the interoperation will work well or badly.  Since
operators *will* get experience defining and using interoperation, we
can make the big decisions when we know better what the consequences
are.

Dale



From marianne.mohali@orange-ftgroup.com  Thu Mar 19 03:57:13 2009
Return-Path: <marianne.mohali@orange-ftgroup.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F5013A69AB for <bliss@core3.amsl.com>; Thu, 19 Mar 2009 03:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.183
X-Spam-Level: 
X-Spam-Status: No, score=-2.183 tagged_above=-999 required=5 tests=[AWL=1.066,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7sL2h9l7NerA for <bliss@core3.amsl.com>; Thu, 19 Mar 2009 03:57:12 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 3C9A13A6931 for <bliss@ietf.org>; Thu, 19 Mar 2009 03:57:12 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 19 Mar 2009 11:57:54 +0100
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
Date: Thu, 19 Mar 2009 11:57:52 +0100
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026064FF16E@ftrdmel2>
In-Reply-To: <1237413833.3807.50.camel@victoria-pingtel-com.us.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] TR: NewVersion	Notificationfordraft-mohali-diversion-history-info-01
Thread-Index: AcmoFXKYf1SclMYTRra/eSInseBrbwAA4N9A
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2><E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail><134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail><D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail><7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2><1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com> <1237413833.3807.50.camel@victoria-pingtel-com.us.nortel.com>
From: <marianne.mohali@orange-ftgroup.com>
To: <dworley@nortel.com>
X-OriginalArrivalTime: 19 Mar 2009 10:57:54.0675 (UTC) FILETIME=[8E336430:01C9A881]
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: NewVersion	Notificationfordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2009 10:57:13 -0000

Hi Dale,
My answer in your text.

Regards,
Marianne=20

-----Message d'origine-----
De : bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] De la part =
de Dale Worley
Envoy=E9 : mercredi 18 mars 2009 23:04
=C0 : BLISS
Objet : Re: [BLISS] TR: NewVersion =
Notificationfordraft-mohali-diversion-history-info-01

On Fri, 2009-03-13 at 09:21 -0500, Mary Barnes wrote:
> And, the standardization of this document could well take longer than=20
> it will take to complete 4244bis. Per my list of pros/cons, to be=20
> correct and useful, this document is effectively standardizing=20
> Diversion header, which is actually more work than what's being done=20
> in the 4244bis and target-uri docs. So, you're waiting either way.

The wretched reality is that you can't solidify interoperation between =
Diversion and History-Info until you get *both* headers defined, and =
everyone agrees that Diversion is not fully defined and the definition =
of History-Info needs to be revised.
[MM] The matter is not to say if Diversion is fully defined, it is that =
the Diversion header is fully implemented. So, it could defined in 5 =
minutes as it has not to be updated. An historical document is enough. =
About History-Info, I think it is yet late to revise History-Info but =
better late than never. The fact is that implementors are yet working on =
its implementation (and it is yet implemented for some of them) and they =
need this interworking today (if not yesterday). If the RFC4244bis is =
backward compatible, there is no issue standardizing the interworking =
from now and the interworking could be udated easily to be in line with =
the new History-Info.[/MM]
=20
As for which header occupied the promised land first, it's not =
immediately clear:  draft-levy-sip-diversion-08 existed in 2004, and
draft-barnes-sipping-history-info-02 existed in 2003.
[MM]First, I AM NOT COMPARING THOSE HEADERS. You are raising an useless =
point. We want to move forward and not to say if v08 of one was before =
v02 of the other (but for your information, first Diversion draft =
existed in oct 2000 and first History-Info draft existed in oct 2002 and =
becames RFC4244 in 2005). Both headers are differents and History-Info =
has a larger scope than Diversion, that's why it has been standardized. =
Because discussions were too long, Diversion header was widely =
implemented. That is the facts and it is the only reason why we need an =
interworking guideline if we want that H-I header becomes the only =
implemented solution.[/MM]

Any even slight official blessing of conversion between the two will =
lead people to consider that SIP supports both headers equally, which =
increase the complexity of the protocol and implementations.
[MM]If it is "necessary" to standardize Diversion header, it is =
recommended to make an historical document.[/MM]

On the other hand, there is no reason that the *work* can't go on, even =
if it receives no support from the IETF.  Indeed, it's clear that there =
are market support for doing the work, which means that the work *will* =
go on.

We can exploit that -- Let us delay *official* recognition until it's =
clear whether the interoperation will work well or badly.  Since =
operators *will* get experience defining and using interoperation, we =
can make the big decisions when we know better what the consequences =
are.
[MM] This work has yet been done with operators and implementors. Since =
the draft was available, everybody could do comments. The only thing to =
do if we have to wait is to update the document according to RFC4244bis =
but in my opinion, it will be late.[/MM]

Dale


_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss

From drage@alcatel-lucent.com  Thu Mar 19 15:51:55 2009
Return-Path: <drage@alcatel-lucent.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0033D3A68CC for <bliss@core3.amsl.com>; Thu, 19 Mar 2009 15:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.247
X-Spam-Level: 
X-Spam-Status: No, score=-6.247 tagged_above=-999 required=5 tests=[AWL=0.002,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qUFtnmZQpaCL for <bliss@core3.amsl.com>; Thu, 19 Mar 2009 15:51:54 -0700 (PDT)
Received: from smail6.alcatel.fr (colt-na5.alcatel.fr [62.23.212.5]) by core3.amsl.com (Postfix) with ESMTP id B687A3A6902 for <bliss@ietf.org>; Thu, 19 Mar 2009 15:51:53 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2JMleSH010741 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 19 Mar 2009 23:47:41 +0100
Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.39]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Thu, 19 Mar 2009 23:47:41 +0100
From: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
To: "marianne.mohali@orange-ftgroup.com" <marianne.mohali@orange-ftgroup.com>,  "dworley@nortel.com" <dworley@nortel.com>
Date: Thu, 19 Mar 2009 23:47:40 +0100
Thread-Topic: [BLISS] TR:	NewVersion Notificationfordraft-mohali-diversion-history-info-01
Thread-Index: AcmoFXKYf1SclMYTRra/eSInseBrbwAA4N9AADC0DCA=
Message-ID: <28B7C3AA2A7ABA4A841F11217ABE78D67577BA0D@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2><E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail><134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail><D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail><7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2><1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com> <1237413833.3807.50.camel@victoria-pingtel-com.us.nortel.com> <7DBAFEC6A76F3E42817DF1EBE64CB026064FF16E@ftrdmel2>
In-Reply-To: <7DBAFEC6A76F3E42817DF1EBE64CB026064FF16E@ftrdmel2>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Cc: "bliss@ietf.org" <bliss@ietf.org>
Subject: Re: [BLISS] TR:	NewVersion	Notificationfordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2009 22:51:55 -0000

I believe my implementors have implemented History-Info.

I believe my implementors have implemented Diversion.

They have implemented interworking between the two.

Assuming you use my implementations as reference implementations and docume=
nt exactly what they do, and nothing else, I have no problem with proceedin=
g with this work.

Other people may however have a problem with that approach, but I am quite =
happy to ignore them.

regards

Keith

> -----Original Message-----
> From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]=20
> On Behalf Of marianne.mohali@orange-ftgroup.com
> Sent: Thursday, March 19, 2009 10:58 AM
> To: dworley@nortel.com
> Cc: bliss@ietf.org
> Subject: Re: [BLISS] TR: NewVersion=20
> Notificationfordraft-mohali-diversion-history-info-01
>=20
> Hi Dale,
> My answer in your text.
>=20
> Regards,
> Marianne=20
>=20
> -----Message d'origine-----
> De : bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]=20
> De la part de Dale Worley Envoy=E9 : mercredi 18 mars 2009=20
> 23:04 =C0 : BLISS Objet : Re: [BLISS] TR: NewVersion=20
> Notificationfordraft-mohali-diversion-history-info-01
>=20
> On Fri, 2009-03-13 at 09:21 -0500, Mary Barnes wrote:
> > And, the standardization of this document could well take=20
> longer than=20
> > it will take to complete 4244bis. Per my list of pros/cons, to be=20
> > correct and useful, this document is effectively standardizing=20
> > Diversion header, which is actually more work than what's=20
> being done=20
> > in the 4244bis and target-uri docs. So, you're waiting either way.
>=20
> The wretched reality is that you can't solidify=20
> interoperation between Diversion and History-Info until you=20
> get *both* headers defined, and everyone agrees that=20
> Diversion is not fully defined and the definition of=20
> History-Info needs to be revised.
> [MM] The matter is not to say if Diversion is fully defined,=20
> it is that the Diversion header is fully implemented. So, it=20
> could defined in 5 minutes as it has not to be updated. An=20
> historical document is enough. About History-Info, I think it=20
> is yet late to revise History-Info but better late than=20
> never. The fact is that implementors are yet working on its=20
> implementation (and it is yet implemented for some of them)=20
> and they need this interworking today (if not yesterday). If=20
> the RFC4244bis is backward compatible, there is no issue=20
> standardizing the interworking from now and the interworking=20
> could be udated easily to be in line with the new History-Info.[/MM]
> =20
> As for which header occupied the promised land first, it's=20
> not immediately clear:  draft-levy-sip-diversion-08 existed=20
> in 2004, and
> draft-barnes-sipping-history-info-02 existed in 2003.
> [MM]First, I AM NOT COMPARING THOSE HEADERS. You are raising=20
> an useless point. We want to move forward and not to say if=20
> v08 of one was before v02 of the other (but for your=20
> information, first Diversion draft existed in oct 2000 and=20
> first History-Info draft existed in oct 2002 and becames=20
> RFC4244 in 2005). Both headers are differents and=20
> History-Info has a larger scope than Diversion, that's why it=20
> has been standardized. Because discussions were too long,=20
> Diversion header was widely implemented. That is the facts=20
> and it is the only reason why we need an interworking=20
> guideline if we want that H-I header becomes the only=20
> implemented solution.[/MM]
>=20
> Any even slight official blessing of conversion between the=20
> two will lead people to consider that SIP supports both=20
> headers equally, which increase the complexity of the=20
> protocol and implementations.
> [MM]If it is "necessary" to standardize Diversion header, it=20
> is recommended to make an historical document.[/MM]
>=20
> On the other hand, there is no reason that the *work* can't=20
> go on, even if it receives no support from the IETF.  Indeed,=20
> it's clear that there are market support for doing the work,=20
> which means that the work *will* go on.
>=20
> We can exploit that -- Let us delay *official* recognition=20
> until it's clear whether the interoperation will work well or=20
> badly.  Since operators *will* get experience defining and=20
> using interoperation, we can make the big decisions when we=20
> know better what the consequences are.
> [MM] This work has yet been done with operators and=20
> implementors. Since the draft was available, everybody could=20
> do comments. The only thing to do if we have to wait is to=20
> update the document according to RFC4244bis but in my=20
> opinion, it will be late.[/MM]
>=20
> Dale
>=20
>=20
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss
> =

From john.elwell@siemens.com  Fri Mar 20 01:20:29 2009
Return-Path: <john.elwell@siemens.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADCCE3A6A51 for <bliss@core3.amsl.com>; Fri, 20 Mar 2009 01:20:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M6aRJ1ia5STB for <bliss@core3.amsl.com>; Fri, 20 Mar 2009 01:20:28 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id 581E73A6A49 for <bliss@ietf.org>; Fri, 20 Mar 2009 01:20:27 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KGS0000MPV9VF@siemenscomms.co.uk> for bliss@ietf.org; Fri, 20 Mar 2009 08:21:11 +0000 (GMT)
Date: Fri, 20 Mar 2009 08:21:12 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: A <28B7C3AA2A7ABA4A841F11217ABE78D67577BA0D@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>, marianne.mohali@orange-ftgroup.com, dworley@nortel.com
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D001AAD3AB@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Thread-Topic: [BLISS]	TR: NewVersionNotificationfordraft-mohali-diversion-history-info-01
Thread-Index: AcmoFXKYf1SclMYTRra/eSInseBrbwAA4N9AADC0DCAAFhzj0A==
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2> <E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail> <134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com> <E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail> <D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com> <E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail> <7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2> <1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com> <1237413833.3807.50.camel@victoria-pingtel-com.us.nortel.com> <7DBAFEC6A76F3E42817DF1EBE64CB026064FF16E@ftrdmel2> A <28B7C3AA2A7ABA4A841F11217ABE78D67577BA0D@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR:	NewVersionNotificationfordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Mar 2009 08:20:29 -0000

And I can chime in with work that Ecma-International did a few years =
ago, published as Standard ECMA-360, on mapping between History-Info (in =
draft form) and QSIG. I expect that mapping to/from QSIG has many =
similarities to mapping to/from the Diversion header field. At the time =
the SIPPING group was not interested in taking this up, so I don't see =
why 5 years later it suddenly becomes important. As Keith says, people =
are already doing it.

John

> -----Original Message-----
> From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]=20
> On Behalf Of DRAGE, Keith (Keith)
> Sent: 19 March 2009 22:48
> To: marianne.mohali@orange-ftgroup.com; dworley@nortel.com
> Cc: bliss@ietf.org
> Subject: Re: [BLISS] TR:=20
> NewVersionNotificationfordraft-mohali-diversion-history-info-01
>=20
> I believe my implementors have implemented History-Info.
>=20
> I believe my implementors have implemented Diversion.
>=20
> They have implemented interworking between the two.
>=20
> Assuming you use my implementations as reference=20
> implementations and document exactly what they do, and=20
> nothing else, I have no problem with proceeding with this work.
>=20
> Other people may however have a problem with that approach,=20
> but I am quite happy to ignore them.
>=20
> regards
>=20
> Keith
>=20
> > -----Original Message-----
> > From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]=20
> > On Behalf Of marianne.mohali@orange-ftgroup.com
> > Sent: Thursday, March 19, 2009 10:58 AM
> > To: dworley@nortel.com
> > Cc: bliss@ietf.org
> > Subject: Re: [BLISS] TR: NewVersion=20
> > Notificationfordraft-mohali-diversion-history-info-01
> >=20
> > Hi Dale,
> > My answer in your text.
> >=20
> > Regards,
> > Marianne=20
> >=20
> > -----Message d'origine-----
> > De : bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]=20
> > De la part de Dale Worley Envoy=E9 : mercredi 18 mars 2009=20
> > 23:04 =C0 : BLISS Objet : Re: [BLISS] TR: NewVersion=20
> > Notificationfordraft-mohali-diversion-history-info-01
> >=20
> > On Fri, 2009-03-13 at 09:21 -0500, Mary Barnes wrote:
> > > And, the standardization of this document could well take=20
> > longer than=20
> > > it will take to complete 4244bis. Per my list of pros/cons, to be=20
> > > correct and useful, this document is effectively standardizing=20
> > > Diversion header, which is actually more work than what's=20
> > being done=20
> > > in the 4244bis and target-uri docs. So, you're waiting either way.
> >=20
> > The wretched reality is that you can't solidify=20
> > interoperation between Diversion and History-Info until you=20
> > get *both* headers defined, and everyone agrees that=20
> > Diversion is not fully defined and the definition of=20
> > History-Info needs to be revised.
> > [MM] The matter is not to say if Diversion is fully defined,=20
> > it is that the Diversion header is fully implemented. So, it=20
> > could defined in 5 minutes as it has not to be updated. An=20
> > historical document is enough. About History-Info, I think it=20
> > is yet late to revise History-Info but better late than=20
> > never. The fact is that implementors are yet working on its=20
> > implementation (and it is yet implemented for some of them)=20
> > and they need this interworking today (if not yesterday). If=20
> > the RFC4244bis is backward compatible, there is no issue=20
> > standardizing the interworking from now and the interworking=20
> > could be udated easily to be in line with the new History-Info.[/MM]
> > =20
> > As for which header occupied the promised land first, it's=20
> > not immediately clear:  draft-levy-sip-diversion-08 existed=20
> > in 2004, and
> > draft-barnes-sipping-history-info-02 existed in 2003.
> > [MM]First, I AM NOT COMPARING THOSE HEADERS. You are raising=20
> > an useless point. We want to move forward and not to say if=20
> > v08 of one was before v02 of the other (but for your=20
> > information, first Diversion draft existed in oct 2000 and=20
> > first History-Info draft existed in oct 2002 and becames=20
> > RFC4244 in 2005). Both headers are differents and=20
> > History-Info has a larger scope than Diversion, that's why it=20
> > has been standardized. Because discussions were too long,=20
> > Diversion header was widely implemented. That is the facts=20
> > and it is the only reason why we need an interworking=20
> > guideline if we want that H-I header becomes the only=20
> > implemented solution.[/MM]
> >=20
> > Any even slight official blessing of conversion between the=20
> > two will lead people to consider that SIP supports both=20
> > headers equally, which increase the complexity of the=20
> > protocol and implementations.
> > [MM]If it is "necessary" to standardize Diversion header, it=20
> > is recommended to make an historical document.[/MM]
> >=20
> > On the other hand, there is no reason that the *work* can't=20
> > go on, even if it receives no support from the IETF.  Indeed,=20
> > it's clear that there are market support for doing the work,=20
> > which means that the work *will* go on.
> >=20
> > We can exploit that -- Let us delay *official* recognition=20
> > until it's clear whether the interoperation will work well or=20
> > badly.  Since operators *will* get experience defining and=20
> > using interoperation, we can make the big decisions when we=20
> > know better what the consequences are.
> > [MM] This work has yet been done with operators and=20
> > implementors. Since the draft was available, everybody could=20
> > do comments. The only thing to do if we have to wait is to=20
> > update the document according to RFC4244bis but in my=20
> > opinion, it will be late.[/MM]
> >=20
> > Dale
> >=20
> >=20
> > _______________________________________________
> > BLISS mailing list
> > BLISS@ietf.org
> > https://www.ietf.org/mailman/listinfo/bliss
> > _______________________________________________
> > BLISS mailing list
> > BLISS@ietf.org
> > https://www.ietf.org/mailman/listinfo/bliss
> >=20
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss
>=20

From marianne.mohali@orange-ftgroup.com  Fri Mar 20 02:02:53 2009
Return-Path: <marianne.mohali@orange-ftgroup.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCCCC3A6A68 for <bliss@core3.amsl.com>; Fri, 20 Mar 2009 02:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.800,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ypIgc-3kIrVR for <bliss@core3.amsl.com>; Fri, 20 Mar 2009 02:02:52 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 5AD983A694D for <bliss@ietf.org>; Fri, 20 Mar 2009 02:02:52 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 20 Mar 2009 10:03:30 +0100
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
Date: Fri, 20 Mar 2009 10:03:30 +0100
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026064FF413@ftrdmel2>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D001AAD3AB@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS]	TR:NewVersionNotificationfordraft-mohali-diversion-history-info-01
Thread-Index: AcmoFXKYf1SclMYTRra/eSInseBrbwAA4N9AADC0DCAAFhzj0AABGyHw
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2><E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail><134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail><D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail><7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2><1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com><1237413833.3807.50.camel@victoria-pingtel-com.us.nortel.com><7DBAFEC6A76F3E42817DF1EBE64CB026064FF16E@ftrdmel2> A<28B7C3AA2A7ABA4A841F11217ABE78D67577BA0D@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> <0D5F89FAC29E2C41B98A6A762007F5D001AAD3AB@GBNTHT12009MSX.gb002.siemens.net>
From: <marianne.mohali@orange-ftgroup.com>
To: <john.elwell@siemens.com>, <drage@alcatel-lucent.com>, <dworley@nortel.com>
X-OriginalArrivalTime: 20 Mar 2009 09:03:30.0443 (UTC) FILETIME=[BD3675B0:01C9A93A]
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR:NewVersionNotificationfordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Mar 2009 09:02:53 -0000

That's why the draft is needed but only informational.
I know implementors waiting for this draft to implement the =
interwroking. For those who have yet implemented the interworking, what =
are they afraid of ? They don't care.
It is obviously possible that everyone do it on his side, but the =
consequence is that bad mapping will introduce wrong information in =
History-Info header.=20
To avoid various interpretations, a guidline is useful.

Regards,
Marianne



-----Message d'origine-----
De : Elwell, John [mailto:john.elwell@siemens.com]=20
Envoy=E9 : vendredi 20 mars 2009 09:21
=C0 : DRAGE, Keith (Keith); MOHALI Marianne RD-CORE-ISS; =
dworley@nortel.com
Cc : bliss@ietf.org
Objet : RE: [BLISS] =
TR:NewVersionNotificationfordraft-mohali-diversion-history-info-01

And I can chime in with work that Ecma-International did a few years =
ago, published as Standard ECMA-360, on mapping between History-Info (in =
draft form) and QSIG. I expect that mapping to/from QSIG has many =
similarities to mapping to/from the Diversion header field. At the time =
the SIPPING group was not interested in taking this up, so I don't see =
why 5 years later it suddenly becomes important. As Keith says, people =
are already doing it.

John

> -----Original Message-----
> From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] On Behalf =

> Of DRAGE, Keith (Keith)
> Sent: 19 March 2009 22:48
> To: marianne.mohali@orange-ftgroup.com; dworley@nortel.com
> Cc: bliss@ietf.org
> Subject: Re: [BLISS] TR:=20
> NewVersionNotificationfordraft-mohali-diversion-history-info-01
>=20
> I believe my implementors have implemented History-Info.
>=20
> I believe my implementors have implemented Diversion.
>=20
> They have implemented interworking between the two.
>=20
> Assuming you use my implementations as reference implementations and=20
> document exactly what they do, and nothing else, I have no problem=20
> with proceeding with this work.
>=20
> Other people may however have a problem with that approach, but I am=20
> quite happy to ignore them.
>=20
> regards
>=20
> Keith
>=20
> > -----Original Message-----
> > From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] On=20
> > Behalf Of marianne.mohali@orange-ftgroup.com
> > Sent: Thursday, March 19, 2009 10:58 AM
> > To: dworley@nortel.com
> > Cc: bliss@ietf.org
> > Subject: Re: [BLISS] TR: NewVersion
> > Notificationfordraft-mohali-diversion-history-info-01
> >=20
> > Hi Dale,
> > My answer in your text.
> >=20
> > Regards,
> > Marianne
> >=20
> > -----Message d'origine-----
> > De : bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] De la=20
> > part de Dale Worley Envoy=E9 : mercredi 18 mars 2009
> > 23:04 =C0 : BLISS Objet : Re: [BLISS] TR: NewVersion
> > Notificationfordraft-mohali-diversion-history-info-01
> >=20
> > On Fri, 2009-03-13 at 09:21 -0500, Mary Barnes wrote:
> > > And, the standardization of this document could well take
> > longer than
> > > it will take to complete 4244bis. Per my list of pros/cons, to be=20
> > > correct and useful, this document is effectively standardizing=20
> > > Diversion header, which is actually more work than what's
> > being done
> > > in the 4244bis and target-uri docs. So, you're waiting either way.
> >=20
> > The wretched reality is that you can't solidify interoperation=20
> > between Diversion and History-Info until you get *both* headers=20
> > defined, and everyone agrees that Diversion is not fully defined and =

> > the definition of History-Info needs to be revised.
> > [MM] The matter is not to say if Diversion is fully defined, it is=20
> > that the Diversion header is fully implemented. So, it could defined =

> > in 5 minutes as it has not to be updated. An historical document is=20
> > enough. About History-Info, I think it is yet late to revise=20
> > History-Info but better late than never. The fact is that=20
> > implementors are yet working on its implementation (and it is yet=20
> > implemented for some of them) and they need this interworking today=20
> > (if not yesterday). If the RFC4244bis is backward compatible, there=20
> > is no issue standardizing the interworking from now and the=20
> > interworking could be udated easily to be in line with the new=20
> > History-Info.[/MM]
> > =20
> > As for which header occupied the promised land first, it's not=20
> > immediately clear:  draft-levy-sip-diversion-08 existed in 2004, and
> > draft-barnes-sipping-history-info-02 existed in 2003.
> > [MM]First, I AM NOT COMPARING THOSE HEADERS. You are raising an=20
> > useless point. We want to move forward and not to say if
> > v08 of one was before v02 of the other (but for your information,=20
> > first Diversion draft existed in oct 2000 and first History-Info=20
> > draft existed in oct 2002 and becames
> > RFC4244 in 2005). Both headers are differents and History-Info has a =

> > larger scope than Diversion, that's why it has been standardized.=20
> > Because discussions were too long, Diversion header was widely=20
> > implemented. That is the facts and it is the only reason why we need =

> > an interworking guideline if we want that H-I header becomes the=20
> > only implemented solution.[/MM]
> >=20
> > Any even slight official blessing of conversion between the two will =

> > lead people to consider that SIP supports both headers equally,=20
> > which increase the complexity of the protocol and implementations.
> > [MM]If it is "necessary" to standardize Diversion header, it is=20
> > recommended to make an historical document.[/MM]
> >=20
> > On the other hand, there is no reason that the *work* can't go on,=20
> > even if it receives no support from the IETF.  Indeed, it's clear=20
> > that there are market support for doing the work, which means that=20
> > the work *will* go on.
> >=20
> > We can exploit that -- Let us delay *official* recognition until=20
> > it's clear whether the interoperation will work well or badly. =20
> > Since operators *will* get experience defining and using=20
> > interoperation, we can make the big decisions when we know better=20
> > what the consequences are.
> > [MM] This work has yet been done with operators and implementors.=20
> > Since the draft was available, everybody could do comments. The only =

> > thing to do if we have to wait is to update the document according=20
> > to RFC4244bis but in my opinion, it will be late.[/MM]
> >=20
> > Dale
> >=20
> >=20
> > _______________________________________________
> > BLISS mailing list
> > BLISS@ietf.org
> > https://www.ietf.org/mailman/listinfo/bliss
> > _______________________________________________
> > BLISS mailing list
> > BLISS@ietf.org
> > https://www.ietf.org/mailman/listinfo/bliss
> >=20
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss
>=20

From ietf.hanserik@gmail.com  Fri Mar 20 02:15:16 2009
Return-Path: <ietf.hanserik@gmail.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 439AF3A694D for <bliss@core3.amsl.com>; Fri, 20 Mar 2009 02:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BzNDNMbIA4ff for <bliss@core3.amsl.com>; Fri, 20 Mar 2009 02:15:14 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by core3.amsl.com (Postfix) with ESMTP id 224AD3A691E for <bliss@ietf.org>; Fri, 20 Mar 2009 02:15:13 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 4so197835eyf.31 for <bliss@ietf.org>; Fri, 20 Mar 2009 02:15:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=2sHKyMyl5yRYyhxdFmPyxkXsXNDGZS+iWv6anCykgvg=; b=HF6gqVEGeotpHVp/wKTbzRAuCplBBdvdSaqOUjScx2nDpAUVTmfVQMk9/t40YzKtM0 ZxAzVl7uYszhkWiIcZxd6Wcvre17KHF+MV6s9BY50MMe3JpFnyewxetBgW+bcjtfBRx9 TBZSXvm5Zvc5NF4BbH9b12wOIJKiKFkDI6/xA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=K1uMH9rChEPShsDNoyKAmvuw7iagcJQlks/GDO5Rg2eGAO9N0B2WkdMYsRceW9ezat 81suDIeESKPXlM8H+RzNecHEohZ0ykKUYAXt/HZ/bRLEmtt98rrXHx7cekzWCz2j/aHk VXq/NJlIGpwU0S1XGwSAVnnmndEiwD5amfgRs=
MIME-Version: 1.0
Received: by 10.216.18.84 with SMTP id k62mr1306933wek.126.1237540559577; Fri,  20 Mar 2009 02:15:59 -0700 (PDT)
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D001AAD3AB@GBNTHT12009MSX.gb002.siemens.net>
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2> <E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail> <D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com> <E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail> <7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2> <1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com> <1237413833.3807.50.camel@victoria-pingtel-com.us.nortel.com> <7DBAFEC6A76F3E42817DF1EBE64CB026064FF16E@ftrdmel2> <28B7C3AA2A7ABA4A841F11217ABE78D67577BA0D@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> <0D5F89FAC29E2C41B98A6A762007F5D001AAD3AB@GBNTHT12009MSX.gb002.siemens.net>
Date: Fri, 20 Mar 2009 10:15:59 +0100
Message-ID: <9ae56b1e0903200215r78e0fa70l4c696fc54b843a5e@mail.gmail.com>
From: Hans Erik van Elburg <ietf.hanserik@gmail.com>
To: "Elwell, John" <john.elwell@siemens.com>
Content-Type: multipart/alternative; boundary=0016364d1dc572e5230465895d9d
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR: NewVersionNotificationfordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Mar 2009 09:15:16 -0000

--0016364d1dc572e5230465895d9d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

But Q.SIG -IS- a standard, so the comparison does not hold.
Interesting to see that you regard Q.SIG and Diversion header field
equivalent.

/Hans Erik van Elburg


On Fri, Mar 20, 2009 at 9:21 AM, Elwell, John <john.elwell@siemens.com>wrot=
e:

> And I can chime in with work that Ecma-International did a few years ago,
> published as Standard ECMA-360, on mapping between History-Info (in draft
> form) and QSIG. I expect that mapping to/from QSIG has many similarities =
to
> mapping to/from the Diversion header field. At the time the SIPPING group
> was not interested in taking this up, so I don't see why 5 years later it
> suddenly becomes important. As Keith says, people are already doing it.
>
> John
>
> > -----Original Message-----
> > From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]
> > On Behalf Of DRAGE, Keith (Keith)
> > Sent: 19 March 2009 22:48
> > To: marianne.mohali@orange-ftgroup.com; dworley@nortel.com
> > Cc: bliss@ietf.org
> > Subject: Re: [BLISS] TR:
> > NewVersionNotificationfordraft-mohali-diversion-history-info-01
> >
> > I believe my implementors have implemented History-Info.
> >
> > I believe my implementors have implemented Diversion.
> >
> > They have implemented interworking between the two.
> >
> > Assuming you use my implementations as reference
> > implementations and document exactly what they do, and
> > nothing else, I have no problem with proceeding with this work.
> >
> > Other people may however have a problem with that approach,
> > but I am quite happy to ignore them.
> >
> > regards
> >
> > Keith
> >
> > > -----Original Message-----
> > > From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]
> > > On Behalf Of marianne.mohali@orange-ftgroup.com
> > > Sent: Thursday, March 19, 2009 10:58 AM
> > > To: dworley@nortel.com
> > > Cc: bliss@ietf.org
> > > Subject: Re: [BLISS] TR: NewVersion
> > > Notificationfordraft-mohali-diversion-history-info-01
> > >
> > > Hi Dale,
> > > My answer in your text.
> > >
> > > Regards,
> > > Marianne
> > >
> > > -----Message d'origine-----
> > > De : bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]
> > > De la part de Dale Worley Envoy=E9 : mercredi 18 mars 2009
> > > 23:04 =C0 : BLISS Objet : Re: [BLISS] TR: NewVersion
> > > Notificationfordraft-mohali-diversion-history-info-01
> > >
> > > On Fri, 2009-03-13 at 09:21 -0500, Mary Barnes wrote:
> > > > And, the standardization of this document could well take
> > > longer than
> > > > it will take to complete 4244bis. Per my list of pros/cons, to be
> > > > correct and useful, this document is effectively standardizing
> > > > Diversion header, which is actually more work than what's
> > > being done
> > > > in the 4244bis and target-uri docs. So, you're waiting either way.
> > >
> > > The wretched reality is that you can't solidify
> > > interoperation between Diversion and History-Info until you
> > > get *both* headers defined, and everyone agrees that
> > > Diversion is not fully defined and the definition of
> > > History-Info needs to be revised.
> > > [MM] The matter is not to say if Diversion is fully defined,
> > > it is that the Diversion header is fully implemented. So, it
> > > could defined in 5 minutes as it has not to be updated. An
> > > historical document is enough. About History-Info, I think it
> > > is yet late to revise History-Info but better late than
> > > never. The fact is that implementors are yet working on its
> > > implementation (and it is yet implemented for some of them)
> > > and they need this interworking today (if not yesterday). If
> > > the RFC4244bis is backward compatible, there is no issue
> > > standardizing the interworking from now and the interworking
> > > could be udated easily to be in line with the new History-Info.[/MM]
> > >
> > > As for which header occupied the promised land first, it's
> > > not immediately clear:  draft-levy-sip-diversion-08 existed
> > > in 2004, and
> > > draft-barnes-sipping-history-info-02 existed in 2003.
> > > [MM]First, I AM NOT COMPARING THOSE HEADERS. You are raising
> > > an useless point. We want to move forward and not to say if
> > > v08 of one was before v02 of the other (but for your
> > > information, first Diversion draft existed in oct 2000 and
> > > first History-Info draft existed in oct 2002 and becames
> > > RFC4244 in 2005). Both headers are differents and
> > > History-Info has a larger scope than Diversion, that's why it
> > > has been standardized. Because discussions were too long,
> > > Diversion header was widely implemented. That is the facts
> > > and it is the only reason why we need an interworking
> > > guideline if we want that H-I header becomes the only
> > > implemented solution.[/MM]
> > >
> > > Any even slight official blessing of conversion between the
> > > two will lead people to consider that SIP supports both
> > > headers equally, which increase the complexity of the
> > > protocol and implementations.
> > > [MM]If it is "necessary" to standardize Diversion header, it
> > > is recommended to make an historical document.[/MM]
> > >
> > > On the other hand, there is no reason that the *work* can't
> > > go on, even if it receives no support from the IETF.  Indeed,
> > > it's clear that there are market support for doing the work,
> > > which means that the work *will* go on.
> > >
> > > We can exploit that -- Let us delay *official* recognition
> > > until it's clear whether the interoperation will work well or
> > > badly.  Since operators *will* get experience defining and
> > > using interoperation, we can make the big decisions when we
> > > know better what the consequences are.
> > > [MM] This work has yet been done with operators and
> > > implementors. Since the draft was available, everybody could
> > > do comments. The only thing to do if we have to wait is to
> > > update the document according to RFC4244bis but in my
> > > opinion, it will be late.[/MM]
> > >
> > > Dale
> > >
> > >
> > > _______________________________________________
> > > BLISS mailing list
> > > BLISS@ietf.org
> > > https://www.ietf.org/mailman/listinfo/bliss
> > > _______________________________________________
> > > BLISS mailing list
> > > BLISS@ietf.org
> > > https://www.ietf.org/mailman/listinfo/bliss
> > >
> > _______________________________________________
> > BLISS mailing list
> > BLISS@ietf.org
> > https://www.ietf.org/mailman/listinfo/bliss
> >
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss
>

--0016364d1dc572e5230465895d9d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

But Q.SIG -IS- a standard, so the comparison does not hold.<br>
Interesting to see that you regard Q.SIG and Diversion header field equival=
ent.<br>
<br clear=3D"all">/Hans Erik van Elburg<br>
<br><br><div class=3D"gmail_quote">On Fri, Mar 20, 2009 at 9:21 AM, Elwell,=
 John <span dir=3D"ltr">&lt;<a href=3D"mailto:john.elwell@siemens.com">john=
.elwell@siemens.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt=
 0.8ex; padding-left: 1ex;">
And I can chime in with work that Ecma-International did a few years ago, p=
ublished as Standard ECMA-360, on mapping between History-Info (in draft fo=
rm) and QSIG. I expect that mapping to/from QSIG has many similarities to m=
apping to/from the Diversion header field. At the time the SIPPING group wa=
s not interested in taking this up, so I don&#39;t see why 5 years later it=
 suddenly becomes important. As Keith says, people are already doing it.<br=
>

<font color=3D"#888888"><br>
John<br>
</font><div class=3D"im"><br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:bliss-bounces@ietf.org">bliss-bounces@ietf.org=
</a> [mailto:<a href=3D"mailto:bliss-bounces@ietf.org">bliss-bounces@ietf.o=
rg</a>]<br>
</div><div class=3D"im">&gt; On Behalf Of DRAGE, Keith (Keith)<br>
&gt; Sent: 19 March 2009 22:48<br>
&gt; To: <a href=3D"mailto:marianne.mohali@orange-ftgroup.com">marianne.moh=
ali@orange-ftgroup.com</a>; <a href=3D"mailto:dworley@nortel.com">dworley@n=
ortel.com</a><br>
&gt; Cc: <a href=3D"mailto:bliss@ietf.org">bliss@ietf.org</a><br>
&gt; Subject: Re: [BLISS] TR:<br>
</div><div><div></div><div class=3D"h5">&gt; NewVersionNotificationfordraft=
-mohali-diversion-history-info-01<br>
&gt;<br>
&gt; I believe my implementors have implemented History-Info.<br>
&gt;<br>
&gt; I believe my implementors have implemented Diversion.<br>
&gt;<br>
&gt; They have implemented interworking between the two.<br>
&gt;<br>
&gt; Assuming you use my implementations as reference<br>
&gt; implementations and document exactly what they do, and<br>
&gt; nothing else, I have no problem with proceeding with this work.<br>
&gt;<br>
&gt; Other people may however have a problem with that approach,<br>
&gt; but I am quite happy to ignore them.<br>
&gt;<br>
&gt; regards<br>
&gt;<br>
&gt; Keith<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: <a href=3D"mailto:bliss-bounces@ietf.org">bliss-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:bliss-bounces@ietf.org">bliss-bounces@i=
etf.org</a>]<br>
&gt; &gt; On Behalf Of <a href=3D"mailto:marianne.mohali@orange-ftgroup.com=
">marianne.mohali@orange-ftgroup.com</a><br>
&gt; &gt; Sent: Thursday, March 19, 2009 10:58 AM<br>
&gt; &gt; To: <a href=3D"mailto:dworley@nortel.com">dworley@nortel.com</a><=
br>
&gt; &gt; Cc: <a href=3D"mailto:bliss@ietf.org">bliss@ietf.org</a><br>
&gt; &gt; Subject: Re: [BLISS] TR: NewVersion<br>
&gt; &gt; Notificationfordraft-mohali-diversion-history-info-01<br>
&gt; &gt;<br>
&gt; &gt; Hi Dale,<br>
&gt; &gt; My answer in your text.<br>
&gt; &gt;<br>
&gt; &gt; Regards,<br>
&gt; &gt; Marianne<br>
&gt; &gt;<br>
&gt; &gt; -----Message d&#39;origine-----<br>
&gt; &gt; De : <a href=3D"mailto:bliss-bounces@ietf.org">bliss-bounces@ietf=
.org</a> [mailto:<a href=3D"mailto:bliss-bounces@ietf.org">bliss-bounces@ie=
tf.org</a>]<br>
&gt; &gt; De la part de Dale Worley Envoy=E9 : mercredi 18 mars 2009<br>
&gt; &gt; 23:04 =C0 : BLISS Objet : Re: [BLISS] TR: NewVersion<br>
&gt; &gt; Notificationfordraft-mohali-diversion-history-info-01<br>
&gt; &gt;<br>
&gt; &gt; On Fri, 2009-03-13 at 09:21 -0500, Mary Barnes wrote:<br>
&gt; &gt; &gt; And, the standardization of this document could well take<br=
>
&gt; &gt; longer than<br>
&gt; &gt; &gt; it will take to complete 4244bis. Per my list of pros/cons, =
to be<br>
&gt; &gt; &gt; correct and useful, this document is effectively standardizi=
ng<br>
&gt; &gt; &gt; Diversion header, which is actually more work than what&#39;=
s<br>
&gt; &gt; being done<br>
&gt; &gt; &gt; in the 4244bis and target-uri docs. So, you&#39;re waiting e=
ither way.<br>
&gt; &gt;<br>
&gt; &gt; The wretched reality is that you can&#39;t solidify<br>
&gt; &gt; interoperation between Diversion and History-Info until you<br>
&gt; &gt; get *both* headers defined, and everyone agrees that<br>
&gt; &gt; Diversion is not fully defined and the definition of<br>
&gt; &gt; History-Info needs to be revised.<br>
&gt; &gt; [MM] The matter is not to say if Diversion is fully defined,<br>
&gt; &gt; it is that the Diversion header is fully implemented. So, it<br>
&gt; &gt; could defined in 5 minutes as it has not to be updated. An<br>
&gt; &gt; historical document is enough. About History-Info, I think it<br>
&gt; &gt; is yet late to revise History-Info but better late than<br>
&gt; &gt; never. The fact is that implementors are yet working on its<br>
&gt; &gt; implementation (and it is yet implemented for some of them)<br>
&gt; &gt; and they need this interworking today (if not yesterday). If<br>
&gt; &gt; the RFC4244bis is backward compatible, there is no issue<br>
&gt; &gt; standardizing the interworking from now and the interworking<br>
&gt; &gt; could be udated easily to be in line with the new History-Info.[/=
MM]<br>
&gt; &gt;<br>
&gt; &gt; As for which header occupied the promised land first, it&#39;s<br=
>
&gt; &gt; not immediately clear: =A0draft-levy-sip-diversion-08 existed<br>
&gt; &gt; in 2004, and<br>
&gt; &gt; draft-barnes-sipping-history-info-02 existed in 2003.<br>
&gt; &gt; [MM]First, I AM NOT COMPARING THOSE HEADERS. You are raising<br>
&gt; &gt; an useless point. We want to move forward and not to say if<br>
&gt; &gt; v08 of one was before v02 of the other (but for your<br>
&gt; &gt; information, first Diversion draft existed in oct 2000 and<br>
&gt; &gt; first History-Info draft existed in oct 2002 and becames<br>
&gt; &gt; RFC4244 in 2005). Both headers are differents and<br>
&gt; &gt; History-Info has a larger scope than Diversion, that&#39;s why it=
<br>
&gt; &gt; has been standardized. Because discussions were too long,<br>
&gt; &gt; Diversion header was widely implemented. That is the facts<br>
&gt; &gt; and it is the only reason why we need an interworking<br>
&gt; &gt; guideline if we want that H-I header becomes the only<br>
&gt; &gt; implemented solution.[/MM]<br>
&gt; &gt;<br>
&gt; &gt; Any even slight official blessing of conversion between the<br>
&gt; &gt; two will lead people to consider that SIP supports both<br>
&gt; &gt; headers equally, which increase the complexity of the<br>
&gt; &gt; protocol and implementations.<br>
&gt; &gt; [MM]If it is &quot;necessary&quot; to standardize Diversion heade=
r, it<br>
&gt; &gt; is recommended to make an historical document.[/MM]<br>
&gt; &gt;<br>
&gt; &gt; On the other hand, there is no reason that the *work* can&#39;t<b=
r>
&gt; &gt; go on, even if it receives no support from the IETF. =A0Indeed,<b=
r>
&gt; &gt; it&#39;s clear that there are market support for doing the work,<=
br>
&gt; &gt; which means that the work *will* go on.<br>
&gt; &gt;<br>
&gt; &gt; We can exploit that -- Let us delay *official* recognition<br>
&gt; &gt; until it&#39;s clear whether the interoperation will work well or=
<br>
&gt; &gt; badly. =A0Since operators *will* get experience defining and<br>
&gt; &gt; using interoperation, we can make the big decisions when we<br>
&gt; &gt; know better what the consequences are.<br>
&gt; &gt; [MM] This work has yet been done with operators and<br>
&gt; &gt; implementors. Since the draft was available, everybody could<br>
&gt; &gt; do comments. The only thing to do if we have to wait is to<br>
&gt; &gt; update the document according to RFC4244bis but in my<br>
&gt; &gt; opinion, it will be late.[/MM]<br>
&gt; &gt;<br>
&gt; &gt; Dale<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; BLISS mailing list<br>
&gt; &gt; <a href=3D"mailto:BLISS@ietf.org">BLISS@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/bliss" target=3D=
"_blank">https://www.ietf.org/mailman/listinfo/bliss</a><br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; BLISS mailing list<br>
&gt; &gt; <a href=3D"mailto:BLISS@ietf.org">BLISS@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/bliss" target=3D=
"_blank">https://www.ietf.org/mailman/listinfo/bliss</a><br>
&gt; &gt;<br>
&gt; _______________________________________________<br>
&gt; BLISS mailing list<br>
&gt; <a href=3D"mailto:BLISS@ietf.org">BLISS@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/bliss" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/bliss</a><br>
&gt;<br>
_______________________________________________<br>
BLISS mailing list<br>
<a href=3D"mailto:BLISS@ietf.org">BLISS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/bliss" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/bliss</a><br>
</div></div></blockquote></div><br>

--0016364d1dc572e5230465895d9d--

From ian.elz@ericsson.com  Mon Mar 23 02:25:48 2009
Return-Path: <ian.elz@ericsson.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5218D3A6BE8 for <bliss@core3.amsl.com>; Mon, 23 Mar 2009 02:25:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.088
X-Spam-Level: 
X-Spam-Status: No, score=-6.088 tagged_above=-999 required=5 tests=[AWL=0.161,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nGi1mkLJ1qMu for <bliss@core3.amsl.com>; Mon, 23 Mar 2009 02:25:47 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id A255A3A695C for <bliss@ietf.org>; Mon, 23 Mar 2009 02:25:46 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 0F9F120D90; Mon, 23 Mar 2009 10:26:34 +0100 (CET)
X-AuditID: c1b4fb3c-ad7f8bb000004c86-bf-49c755c9a65e
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.253.124]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 335B920DD8; Mon, 23 Mar 2009 10:26:33 +0100 (CET)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 23 Mar 2009 10:26:23 +0100
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
Date: Mon, 23 Mar 2009 10:28:06 +0100
Message-ID: <C0E80510684FE94DBDE3A4AF6B968D2D054D7526@esealmw118.eemea.ericsson.se>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D001AAD3AB@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS]TR:	NewVersionNotificationfordraft-mohali-diversion-history-info-01
Thread-Index: AcmoFXKYf1SclMYTRra/eSInseBrbwAA4N9AADC0DCAAFhzj0ACZE/EA
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2><E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail><134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail><D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail><7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2><1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com><1237413833.3807.50.camel@victoria-pingtel-com.us.nortel.com><7DBAFEC6A76F3E42817DF1EBE64CB026064FF16E@ftrdmel2> A<28B7C3AA2A7ABA4A841F11217ABE78D67577BA0D@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> <0D5F89FAC29E2C41B98A6A762007F5D001AAD3AB@GBNTHT12009MSX.gb002.siemens.net>
From: "Ian Elz" <ian.elz@ericsson.com>
To: "Elwell, John" <john.elwell@siemens.com>, "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>, <marianne.mohali@orange-ftgroup.com>, <dworley@nortel.com>
X-OriginalArrivalTime: 23 Mar 2009 09:26:23.0657 (UTC) FILETIME=[6EF38990:01C9AB99]
X-Brightmail-Tracker: AAAAAA==
Cc: bliss@ietf.org
Subject: Re: [BLISS] TR:	NewVersionNotificationfordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 09:25:48 -0000

John,

The ECMA work is interesting but works well as the interworking can be =
done at a definitive point in the network where Diversion exists on one =
side but not on another.

If you have design your SIP network in a similar manner with a Diversion =
island and a History-Info island with a definitive interworking point(s) =
then you can take the same approach.

The complexity arises if you have a mixed network where there are some =
nodes which add and use Diversion headers and some H-I. Unfortunately =
this is the type of deployment which is being seen.

In this latter case as a node which converts from H-I <-> Diversion it =
is necessary to try and keep the information in both headers in step. =
This is the difficult part as H-I and Diversion are not used for the =
same purposes then it can be difficult to align the two different =
headers.

The ECNA work, Diversion <-> QSIG, and the 3GPP work, H-I <-> ISUP, =
provide input and mechanisms which can be used in the direct mapping but =
consideration needs to be given for the network topology.

Ian Elz

System Manager
DUCI LDC UK
(Lucid Duck)

Office: + 44 24 764 35256
ian.elz@ericsson.com

-----Original Message-----
From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] On Behalf =
Of Elwell, John
Sent: 20 March 2009 08:21
To: DRAGE, Keith (Keith); marianne.mohali@orange-ftgroup.com; =
dworley@nortel.com
Cc: bliss@ietf.org
Subject: Re: [BLISS]TR: =
NewVersionNotificationfordraft-mohali-diversion-history-info-01

And I can chime in with work that Ecma-International did a few years =
ago, published as Standard ECMA-360, on mapping between History-Info (in =
draft form) and QSIG. I expect that mapping to/from QSIG has many =
similarities to mapping to/from the Diversion header field. At the time =
the SIPPING group was not interested in taking this up, so I don't see =
why 5 years later it suddenly becomes important. As Keith says, people =
are already doing it.

John

> -----Original Message-----
> From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]=20
> On Behalf Of DRAGE, Keith (Keith)
> Sent: 19 March 2009 22:48
> To: marianne.mohali@orange-ftgroup.com; dworley@nortel.com
> Cc: bliss@ietf.org
> Subject: Re: [BLISS] TR:=20
> NewVersionNotificationfordraft-mohali-diversion-history-info-01
>=20
> I believe my implementors have implemented History-Info.
>=20
> I believe my implementors have implemented Diversion.
>=20
> They have implemented interworking between the two.
>=20
> Assuming you use my implementations as reference=20
> implementations and document exactly what they do, and=20
> nothing else, I have no problem with proceeding with this work.
>=20
> Other people may however have a problem with that approach,=20
> but I am quite happy to ignore them.
>=20
> regards
>=20
> Keith
>=20
> > -----Original Message-----
> > From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]=20
> > On Behalf Of marianne.mohali@orange-ftgroup.com
> > Sent: Thursday, March 19, 2009 10:58 AM
> > To: dworley@nortel.com
> > Cc: bliss@ietf.org
> > Subject: Re: [BLISS] TR: NewVersion=20
> > Notificationfordraft-mohali-diversion-history-info-01
> >=20
> > Hi Dale,
> > My answer in your text.
> >=20
> > Regards,
> > Marianne=20
> >=20
> > -----Message d'origine-----
> > De : bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]=20
> > De la part de Dale Worley Envoy=E9 : mercredi 18 mars 2009=20
> > 23:04 =C0 : BLISS Objet : Re: [BLISS] TR: NewVersion=20
> > Notificationfordraft-mohali-diversion-history-info-01
> >=20
> > On Fri, 2009-03-13 at 09:21 -0500, Mary Barnes wrote:
> > > And, the standardization of this document could well take=20
> > longer than=20
> > > it will take to complete 4244bis. Per my list of pros/cons, to be=20
> > > correct and useful, this document is effectively standardizing=20
> > > Diversion header, which is actually more work than what's=20
> > being done=20
> > > in the 4244bis and target-uri docs. So, you're waiting either way.
> >=20
> > The wretched reality is that you can't solidify=20
> > interoperation between Diversion and History-Info until you=20
> > get *both* headers defined, and everyone agrees that=20
> > Diversion is not fully defined and the definition of=20
> > History-Info needs to be revised.
> > [MM] The matter is not to say if Diversion is fully defined,=20
> > it is that the Diversion header is fully implemented. So, it=20
> > could defined in 5 minutes as it has not to be updated. An=20
> > historical document is enough. About History-Info, I think it=20
> > is yet late to revise History-Info but better late than=20
> > never. The fact is that implementors are yet working on its=20
> > implementation (and it is yet implemented for some of them)=20
> > and they need this interworking today (if not yesterday). If=20
> > the RFC4244bis is backward compatible, there is no issue=20
> > standardizing the interworking from now and the interworking=20
> > could be udated easily to be in line with the new History-Info.[/MM]
> > =20
> > As for which header occupied the promised land first, it's=20
> > not immediately clear:  draft-levy-sip-diversion-08 existed=20
> > in 2004, and
> > draft-barnes-sipping-history-info-02 existed in 2003.
> > [MM]First, I AM NOT COMPARING THOSE HEADERS. You are raising=20
> > an useless point. We want to move forward and not to say if=20
> > v08 of one was before v02 of the other (but for your=20
> > information, first Diversion draft existed in oct 2000 and=20
> > first History-Info draft existed in oct 2002 and becames=20
> > RFC4244 in 2005). Both headers are differents and=20
> > History-Info has a larger scope than Diversion, that's why it=20
> > has been standardized. Because discussions were too long,=20
> > Diversion header was widely implemented. That is the facts=20
> > and it is the only reason why we need an interworking=20
> > guideline if we want that H-I header becomes the only=20
> > implemented solution.[/MM]
> >=20
> > Any even slight official blessing of conversion between the=20
> > two will lead people to consider that SIP supports both=20
> > headers equally, which increase the complexity of the=20
> > protocol and implementations.
> > [MM]If it is "necessary" to standardize Diversion header, it=20
> > is recommended to make an historical document.[/MM]
> >=20
> > On the other hand, there is no reason that the *work* can't=20
> > go on, even if it receives no support from the IETF.  Indeed,=20
> > it's clear that there are market support for doing the work,=20
> > which means that the work *will* go on.
> >=20
> > We can exploit that -- Let us delay *official* recognition=20
> > until it's clear whether the interoperation will work well or=20
> > badly.  Since operators *will* get experience defining and=20
> > using interoperation, we can make the big decisions when we=20
> > know better what the consequences are.
> > [MM] This work has yet been done with operators and=20
> > implementors. Since the draft was available, everybody could=20
> > do comments. The only thing to do if we have to wait is to=20
> > update the document according to RFC4244bis but in my=20
> > opinion, it will be late.[/MM]
> >=20
> > Dale
> >=20
> >=20
> > _______________________________________________
> > BLISS mailing list
> > BLISS@ietf.org
> > https://www.ietf.org/mailman/listinfo/bliss
> > _______________________________________________
> > BLISS mailing list
> > BLISS@ietf.org
> > https://www.ietf.org/mailman/listinfo/bliss
> >=20
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss
>=20
_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss

From HKaplan@acmepacket.com  Tue Mar 24 03:04:43 2009
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB7BC3A68DB for <bliss@core3.amsl.com>; Tue, 24 Mar 2009 03:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.528
X-Spam-Level: 
X-Spam-Status: No, score=-2.528 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k2uHxkUaxQ+0 for <bliss@core3.amsl.com>; Tue, 24 Mar 2009 03:04:43 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id E03D33A684C for <bliss@ietf.org>; Tue, 24 Mar 2009 03:04:42 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.340.0; Tue, 24 Mar 2009 06:05:32 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Tue, 24 Mar 2009 06:05:32 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>, "marianne.mohali@orange-ftgroup.com" <marianne.mohali@orange-ftgroup.com>,  "dworley@nortel.com" <dworley@nortel.com>
Date: Tue, 24 Mar 2009 06:05:33 -0400
Thread-Topic: [BLISS]	TR:	NewVersion Notificationfordraft-mohali-diversion-history-info-01
Thread-Index: AcmoFXKYf1SclMYTRra/eSInseBrbwAA4N9AADC0DCAA4tGgoA==
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC314F9761FEA@mail>
References: <7DBAFEC6A76F3E42817DF1EBE64CB02605F809C0@ftrdmel2><E6C2E8958BA59A4FB960963D475F7AC314E619B9F3@mail><134A00CA-C49D-4609-BF93-99CBBF122F39@ntt-at.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53B2@mail><D2A4F8BD-09FA-491D-B3D2-08602D3E74E3@nortel.com><E6C2E8958BA59A4FB960963D475F7AC314E76C53BB@mail><7DBAFEC6A76F3E42817DF1EBE64CB026064C8538@ftrdmel2><1ECE0EB50388174790F9694F77522CCF1CD7F3A0@zrc2hxm0.corp.nortel.com> <1237413833.3807.50.camel@victoria-pingtel-com.us.nortel.com> <7DBAFEC6A76F3E42817DF1EBE64CB026064FF16E@ftrdmel2> <28B7C3AA2A7ABA4A841F11217ABE78D67577BA0D@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
In-Reply-To: <28B7C3AA2A7ABA4A841F11217ABE78D67577BA0D@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "bliss@ietf.org" <bliss@ietf.org>
Subject: Re: [BLISS] TR:	NewVersion	Notificationfordraft-mohali-diversion-history-info-01
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Mar 2009 10:04:43 -0000

> -----Original Message-----
> From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] On Behalf Of
> DRAGE, Keith (Keith)
> Sent: Thursday, March 19, 2009 6:48 PM
> To: marianne.mohali@orange-ftgroup.com; dworley@nortel.com
>=20
> I believe my implementors have implemented History-Info.
> I believe my implementors have implemented Diversion.
> They have implemented interworking between the two.
> Assuming you use my implementations as reference implementations and
> document exactly what they do, and nothing else, I have no problem with
> proceeding with this work.
> Other people may however have a problem with that approach, but I am quit=
e
> happy to ignore them.

Sounds fine by me.  Document what you've done for H-I <-> Div.  If we don't=
 all agree with it, we can argue about it before it becomes an RFC and pote=
ntially make changes.  You can ignore those changes, as you can for any RFC=
, but my guess is your customers will force/demand you to change your imple=
mentation to comply with an RFC over your current proprietary interworking.

If we don't define and publish an RFC, the customers will have no reference=
 document to point to, to make you comply with, and you and everyone else w=
ill continue to have proprietary interworking implementations.

One of the reasons I come to the IETF is to avoid that latter scenario.  I'=
m not quite sure why others come, but my guess is it's something similar.

-hadriel
