
From shida@ntt-at.com  Tue Dec  1 18:36: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 82A2A3A69E2 for <bliss@core3.amsl.com>; Tue,  1 Dec 2009 18:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.665
X-Spam-Level: 
X-Spam-Status: No, score=-1.665 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_66=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 JaBDsbR8H1bb for <bliss@core3.amsl.com>; Tue,  1 Dec 2009 18:36:12 -0800 (PST)
Received: from gateway09.websitewelcome.com (gateway09.websitewelcome.com [67.18.16.73]) by core3.amsl.com (Postfix) with SMTP id 74BCF3A67D2 for <bliss@ietf.org>; Tue,  1 Dec 2009 18:36:12 -0800 (PST)
Received: (qmail 21721 invoked from network); 2 Dec 2009 02:43:45 -0000
Received: from gator465.hostgator.com (69.56.174.130) by gateway09.websitewelcome.com with SMTP; 2 Dec 2009 02:43:45 -0000
Received: from em60-254-241-57.pool.e-mobile.ne.jp ([60.254.241.57]:49693) by gator465.hostgator.com with esmtpa (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1NFexp-0003yi-Ky for bliss@ietf.org; Tue, 01 Dec 2009 20:29:11 -0600
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
From: Shida Schubert <shida@ntt-at.com>
In-Reply-To: <1971b0b60911191804m7c88617fk448c982532d033f3@mail.gmail.com>
Date: Wed, 2 Dec 2009 11:29:17 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <40000D87-837E-40C1-A7FB-6232F0E4D3E8@ntt-at.com>
References: <4AF7C6F3.1070400@sipstation.com> <A909DA5B-FFD5-4E5F-A712-FE5B0AC2E702@ntt-at.com> <1971b0b60911191804m7c88617fk448c982532d033f3@mail.gmail.com>
To: BLISS <bliss@ietf.org>
X-Mailer: Apple Mail (2.1077)
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: Re: [BLISS] Shared Appearance use of Event header parameter
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, 02 Dec 2009 02:36:13 -0000

 As there were no more comments on this matter, and no=20
issues were raised during WGLC I will go ahead and start=20
writing up the proto writeup.=20

 Regards
  Shida

On Nov 20, 2009, at 11:04 AM, Raj Jain wrote:

> Hi Shida,
>=20
> I think the semantics in your question are about SIP protocol level
> negotiation vs. event package level negotiation. The SA draft is
> extending RFC 4235 for the shared appearences feature. I see it as
> more of an event package extension as opposed to a SIP option tag
> extension.
>=20
> Just my 2 cents,
> Raj
>=20
>=20
>=20
>=20
> On Thu, Nov 19, 2009 at 7:09 PM, Shida Schubert <shida@ntt-at.com> =
wrote:
>>=20
>>  I think option tag is necessary if UA that does not understand
>> this specification barfs or breaks by receiving the parameter
>> mentioned.
>>=20
>>  Regards
>>  Shida as an individual.
>>=20
>> On Nov 9, 2009, at 4:38 PM, Alan Johnston wrote:
>>=20
>>> Here's an issue Robert has raised that we should have some =
discussion on before sending this on the IESG.
>>>=20
>>> The Shared Appearance draft defines a "shared" event parameter.
>>>=20
>>> The question is whether this should instead be a SIP feature tag =
used in a Supported and Require header fields.
>>>=20
>>> I've pulled out some text from the draft, RFC 3265, and a summary of =
how it is used.
>>>=20
>>> What do people think?
>>>=20
>>> Thanks,
>>> Alan
>>>=20
>>> - - - - -
>>>=20
>>> =46rom draft-bliss-shared-appearance:
>>>=20
>>> Section 12.1
>>>=20
>>>  This specification defines a new event parameter 'shared' for the
>>>  Dialog Package.  When used in a NOTIFY, it indicates that the
>>>  notifier supports the shared appearance feature.  When used in a
>>>  PUBLISH, it indicates that the publisher has explicit appearance
>>>  information contained in the message body.  If not present in a
>>>  PUBLISH, the Appearance Agent MAY assign an appearance number to =
any
>>>  new dialogs in the message body.
>>>=20
>>> =46rom RFC 3265:
>>>=20
>>> 4.4.2. Event Package Parameters
>>>=20
>>>  If parameters are to be used on the "Event" header to modify the
>>>  behavior of the event package, the syntax and semantics of such
>>>  headers MUST be clearly defined.
>>>=20
>>> Details on the usage:
>>>=20
>>> - Appearance Agent discovery of non-Shared Appearance UA during =
subscriptions.  A NOTIFY sent without <appearance> elements does not =
necessarily mean the UA does not understand or support the extension, =
but a NOTIFY sent without the Event:dialog;shared does  indicate this.
>>>=20
>>> - Sent by a UA and interpreted by an Appearance Agent to request no =
appearance number be assigned to a dialog (PUBLISH sent without =
<appearance> attribute but containing Event: dialog;shared
>>>=20
>>>=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
>>=20


From dworley@nortel.com  Fri Dec  4 14:03:11 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 5741928C0EF for <bliss@core3.amsl.com>; Fri,  4 Dec 2009 14:03:11 -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 gS7QRNyFM52l for <bliss@core3.amsl.com>; Fri,  4 Dec 2009 14:03:09 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 744FD3A63C9 for <bliss@ietf.org>; Fri,  4 Dec 2009 14:03:08 -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 nB4M2cC28129; Fri, 4 Dec 2009 22:02:38 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 4 Dec 2009 17:02:07 -0500
From: "Dale Worley" <dworley@nortel.com>
To: Shida Schubert <shida@ntt-at.com>
In-Reply-To: <40000D87-837E-40C1-A7FB-6232F0E4D3E8@ntt-at.com>
References: <4AF7C6F3.1070400@sipstation.com> <A909DA5B-FFD5-4E5F-A712-FE5B0AC2E702@ntt-at.com> <1971b0b60911191804m7c88617fk448c982532d033f3@mail.gmail.com> <40000D87-837E-40C1-A7FB-6232F0E4D3E8@ntt-at.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Fri, 04 Dec 2009 17:02:07 -0500
Message-Id: <1259964127.3761.31.camel@khone.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Dec 2009 22:02:07.0820 (UTC) FILETIME=[6BEDB8C0:01CA752D]
Cc: BLISS <bliss@ietf.org>
Subject: Re: [BLISS] Shared Appearance use of Event header parameter
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, 04 Dec 2009 22:03:11 -0000

My apologies for not getting to this sooner, but November was a busy
month for me.

Comments on draft-ietf-bliss-shared-appearances-04:

Technical items

T1. In 4.2 items 1 and 2, it is asserted that a successful dialog event
by a UA subscription to its AOR indicates the presence of an
Appearance Agent.  But this is not so -- there may be a state agent
that does not support SA.  The correct test seems to be:

   1.  A UA is configured with the AOR of a shared appearance group.
       It registers against the AOR, then attempts a dialog state
       subscription to the AOR with the "shared" parameter, that is,
       with "Event: dialog;shared".  If the subscription fails or loops
       back to itself, the UA knows there is no State Agent, and hence
       no Appearance Agent and this feature is not implemented.

   2.  If the subscription receives a 200 OK, the UA knows there is a
       State Agent If the resulting NOTIFYs contain "Event:
       dialog;shared" rather than "Event: dialog", then the State
       Agent is an Appearance Agent that this feature is implemented.
       The UA then follows the steps in this list.

T2. In 5, perhaps between 5.1 and 5.2 should be a normative description of
appearance numbers, along these lines:

    Each AOR that implements Shared Appearances has a separate set of
    appearance numbers, which are consecutive integers starting at
    zero, running to some upper limit.

    Most dialog endpoints at an implementing AOR will be assigned an
    appearance number.  This appearance number (or lack thereof) will
    not change during the life of the dialog, and, except as provided
    herein, will not be shared with any other dialog endpoint.

    The two endpoints of a dialog are assigned appearance numbers
    independently of each other, even if they are to/from the same
    AOR.

    A dialog which replaces or joins another dialog may share the
    appearance number of the replaced/joined dialog.

    The originating endpoints of multiple dialogs which are created by
    a single INVITE perforce share the same appearance number.

Note that this description includes a number of technical issues,
viz., (1) that the two endpoints of a dialog are assigned appearance
numbers independently (see also comments on 10.8), (2) that the
appearance number of a dialog cannot be changed (see also comments on
10.2), and (3) the originating endpoints of multiple dialogs created
by a single INVITE share the same appearance number (for their
duration).

T3. In 5.1 item 3 is "A forking proxy server that can communicate with the
State Agent".  Technically, the information that must be communicated
between the forking proxy and the Appearance Agent should be
specified.  Note that it is not required that the forking proxy send
dialog state data to the Appearance Agent (as the AA can obtain it
from subscriptions).  The minimum requirement is that the forking
proxy uses the Appearance Agent to allocate appearance numbers to
incoming dialog requests, and that can be done without any "special"
data path.  (E.g., by sending the request to the Appearance Agent,
which would attach a suitable Alert-Info header field via a
redirection response.  See section 11.)

T4. In 5.2.2, the default value of the <exclusive> element needs to be
specified, i.e., the effect if <exclusive> is omitted from a <dialog>.

T5. In 5.3 is a repetition of the "subscription test" of 4.2 item 1, and
it needs the same clarifications.

T6. In 5.3 in order to allow a subscribing UA to accurately know whether a
notifier is an Appearance Agent that supports SA, it seems that the
NOTIFY Event header fields MUST include the 'shared' parameter, rather
than just SHOULD include it.  If we do not make this a MUST, the
dialog events need some other indicator of this fact.  (The extension
elements do not suffice, as a dialog event with zero dialogs will
never contain an extension element.)

T7. In 5.3 there should be a description of the correspondence/interaction
between PUBLISHs sent by a UA to the AA and NOTIFYs sent by the UA to
the AA (when the AA is using such subscriptions).  The central
questions seem to be:

	The correspondence between the <dialog> 'id' values in the
	PUBLISHs and NOTIFYs.

	Whether or not a NOTIFY containing a dialog with an appearance
	number constitutes a refreshment of the appearance number
	assignment.  This determines whether the UA can send NOTIFYs
	every 60 seconds instead of sending PUBLISHs every 60 seconds.

T8. In 5.3, in regard to preventing pickup/join, it would be helpful if
some guidance was provided as to what specific information should be
concealed.  As far as I can see, one needs to conceal the identity and
target URIs (to prevent the remote UA from being queried directly for
the dialog identifiers) and to replace consistently the call-id with a
generated unique pseudo-random value.  The tags should remain
unchanged so as to assure that (e.g.) multiple dialogs generated by a
single INVITE remain distinct.  And perhaps we should establish a
convention as to how the generated call-id appears so as to avoid
confusing someone trying to debug the system, e.g., suggest that the
generated call-id start with "exclusive:".  The identity/target URIs
should be replaced with an "anonymous" URI rather than being deleted,
so that any parameters (especially "+sip.rendering") can be carried
normally.

T9. It isn't clear (to me) exactly what actions need to be taken by
the UA to seize and hold an appearance number.  There is relevant text
in In 5.3, 5.4, and 10.4, but it is not consistent.

In 5.3 is "Once the dialog has transitioned to the confirmed state, no
publication refreshes are necessary.".  But this contradicts the
statement in 10.4 "As long as Bob is using the appearance number, he
must refresh the publication every 60 seconds or loose the
appearance."

In 5.4 is another discussion of the expiration time of PUBLISHed
appearance numbers.  This needs to be reconciled with the text in 5.3
and 10.4.

In 10.4 is "As long as Bob is using the appearance number, he must
refresh the publication every 60 seconds or loose the appearance."
This seems to contradict text in 5.2 and 5.3.

T10. In 5.4 is "If an INVITE is sent and no appearance number is
available, the proxy MAY reject the INVITE with a 403 Forbidden
response code."  Is any alternative behavior possible?  E.g., should
we add, "Alternatively, the Appearance Agent may choose to not assign
an appearance number to the dialog."

T11. In 6, should the minOccurs and maxOccurs attributes be present,
since the <element>s are children of <schema>?  It doesn't look like
the XML Schema Language allows that.

T12. In 9, it is stated that a UA can discover whether SA is available for
a given AOR.  But this seems to not be true in the common case where a
central system provides dialog events for all AORs, but the central
system does not support SA -- in that case, a SUBSCRIBE to the AOR
with ";shared" will be accepted (since the notifier ignores ";shared",
not knowing what it means), and the subscription will not loop to the
requesting UA.  A new attribute could be added to the <dialog-info>
element, or better, the Event header field of the NOTIFYs could be
tested for the "shared" parameter.

T13. In 10.2 is "However, if Carol answers both Alice and Bob and keeps
both dialogs active, then the Appearance Agent will need to resolve
the situation by moving either Alice or Bob's dialog to a different
appearance."  But there is no defined operation for changing the
appearance number of a dialog that is in progress, and there is no
guarantee that the participating UA can render the new appearance
number.  (E.g., suppose Alice's UA is a single-line UA, and the AA
tries to move Alice's dialog to appearance number 1.)  This seems to
require that multiple dialogs generated by one INVITE be allowed to
keep using the same appearance number, or alternatively, that we
define how the appearance number of an established dialog can be
changed.

T14. In 10.8, the overall logic seems to be incorrect, at least if the
intention is to simulate a key system and/or to handle this situation
as a logical extension of the previous cases:  The originating and the
terminating ends of the call should be on separate appearances.  But
the events shown assign the same appearance number to both ends of the
call.

Not treating the two ends of the call separately is actually
constructing a special case for how these calls are to be handled, but
there is no normative text describing how this special case is to be
handled, and no discussion of whether treating this as a special case
would cause problems.  Much better, IMHO, would be to treat this
situation via the general case, where the UAC seizes an appearance
number for the originating end, sends the INVITE, the proxy assigns
another appearance number for the terminating end, and everything
works as normal.

Editorial items

E1. In 1 is "This document looks at how this feature can be implemented",
but the section does not clearly state that the document specifies a
method of implementation.  (This seems to be a remnant from when the
text was used in a requirements-definition or
implementation-comparison document.  See also comments about section
11.)

E2. In 1 is "In traditional telephony, the line is physical."  Let us be
explicit about this and say, "In traditional telephony, the line is
physical, a single copper pair that runs to the central office."

E3. In 1, "typically each appearance or an AOR" should be "typically each
appearance { of } an AOR".

E4. In 1, "visual display" would probably be better as "visual indicator".

E5. In 3.2, "Users with similar business needs or tasks can be assigned to
specific groups and share the line appearances of each other on each
others SIP telephony devices." is awkward.  Perhaps better phrased as
"... and share each other's line appearances on their SIP telephony
devices."

E6.In 3.3, "If another UA in the group seizes the line (i.e. goes off
hook)," would probably be better as "If another UA in the group
selects an appearance with an active call (i.e. goes off hook),".

E7. In 4.1 REQ-9, "incoming session request" should probably be "incoming
dialog request".

E8. In 4.2 item 1: "If the subscription fails, loops back to itself, or
returns an error, it knows there is no State Agent...".  In 5.3, "If
the SUBSCRIBE request fails or loops back to itself, then no Appearance
Agent is present...".  Both seem to be poorly phrased, and should be
"...fails or loops back to the UA itself...".  ("fails" and "returns
an error" are equivalent.)

E9. In 4.2 item 8, "Since the same appearance number is used for these
types of operations, this information is published prior to sending
the INVITE Join or INVITE Replaces." would be better explained as
"Since the new dialog uses the same appearance number as the target
dialog, the new dialog's appearance number is published prior to
sending the INVITE Join or INVITE Replaces."

E10. In 4.2 item 9, "the Appearance Agent may not have full access" would
be more clearly stated as "the Appearance Agent may not have { direct
} access".

E11. In 5 item "Seizing", the end of the paragraph would be clearer as:

   ... communicating an artificial state of "trying" prior to actually
   initiating a dialog, in order to appear as { if the UA } was
   already initiating a dialog.  { The UA waits until the allocation
   of the appearance number is confirmed } prior to sending the
   INVITE.

E12. In 5.1 item 3 is "A forking proxy server that can communicate with the
State Agent".  For consistency, this item should end with a period,
and "State Agent" should be "Appearance Agent".

E13. In 5.2, reference to I-D.ietf-sipcore-rfc3265bis is incorrect, as
the dialog event package is defined in RFC 4235.

E14. In 5.2.1 should be added, "The absence of an <appearance> element for
a <dialog> element from a notifier that implements Shared Appearances
indicates that the dialog is not assigned an appearance number."

E15. In 5.2.2 is "The <exclusive> element is a boolean used to indicate
whether the UA will accept Join or Replaces INVITEs for this dialog.".
This could be clarified to:

    The <exclusive> element is a boolean used to indicate whether this
    dialog is allowed to be the target of a pickup or join action.  As an XML
    boolean value, its content is "true" or "false".  The default value is
    { what??? }.  If <exclusive> is "true", the UA will not accept a Join or
    Replaces INVITE for this dialog, and other UAs should not issue them.

E16. In 5.3 is:

      The presence of the 'shared' Event package parameter tells the
      Appearance Agent that this UA supports this specification.

However, this should be generalized, as it (e.g.) also is how the UA
determines that a State Agent supports this specification:

      The presence of the 'shared' Event package parameter tells the
      recipient that the sender supports this specification.

E17. In 5.3 there should probably be a note that as an event state
compositor, the AA may generate new <dialog> 'id' values in the
NOTIFYs it generates (relative to the 'id' values in the
PUBLISHs/NOTIFYs it receives).  (This is described in passing in 10.4,
but it should be noted in a normative section.)

E18. In 5.3 is "Dialog identification includes local and remote target URIs
..." which should be expanded to "Dialog identification includes local
and remote { identity and } target URIs".  The reason to include
identity URIs is that very often the target UA can be effectively
reached through its identity URI, so hiding the target without hiding
the identity provides no additional security.

E19. In 5.3 item 1 is "It registers against the AOR ..." should be
clarified as "It registers (once) against the AOR ...", because some
SA proposals have included registration once for each appearance
number.

E20. In 5.3, items 2 to 4, the text is not very clear about what moment the
PUBLISH should be sent.  Each should start with "Before sending the
INVITE when ...".  In addition, there should be an item listing when
PUBLISHs need to be sent periodically by a UA to continue to hold an
appearance number.  (The latter interacts with the question of whether
a NOTIFY holds an appearance number.)

E21. In 5.4 is "The Appearance Agent MUST support publications and
subscriptions for this event package.".  This would be clearer as "The
Appearance Agent MUST be a UAS for publications and a notifier for
subscriptions for this event package."

E22. In 5.4 is "... also to pass the appearance number to the proxy to
insert in the Alert-Info header field." would be clearer as "... also
to pass the appearance number to the proxy to insert in the Alert-Info
header field { of incoming INVITEs to the AOR }."

E23. In 5.4 is "... if a PUBLISH has not been received selecting/seizing a
particular appearance number" would be clearer as "if a PUBLISH has
not been received selecting/seizing a particular appearance number {
or specifying that no appearance number is to be assigned }".

E24. In 6, indenting of XML in the schema is inconsistent.

E25. In 6, the XML schema describes the new elements but does not describe
where in the larger <dialog-info> it is valid to place them.  I'm not
sure that XML Schema Language provides a way to do this, though.  In
any case, the text in 5.2, "The elements are <appearance>,
<exclusive>, <joined-dialog>, and <replaced-dialog> which are
sub-elements of the <dialog> element." should be replicated here, so
that 6 is a reasonably complete syntax of the new elements within the
dialog event package.

E26. In 7, the last sentence uses "also" twice.

E27. In 7.1 et seq., the descriptions of the UA types don't really describe
how the appearances are managed.

Suggested improvements to these sections are { inside braces }:

    7.1.1.  Single Appearance UAs

       These devices are constrained by only having the capability of
       displaying status indications for a single call.  { Thus, the device
       must annotate all calls it makes with a fixed appearance number
       (usually "0"), and must display only the status of calls with
       that appearance number.  Any incoming call indications
       for appearances other than for that appearance number should be 
       rejected with a 486 or 480 response. }

    7.1.2.  Dual Appearance UAs

       These devices are essentially single appearance phones that implement
       call waiting.  They have a very simple user interface that allows
       them to switch between two appearances (toggle or flash hook) and
       perhaps audible tones to indicate the status of the other appearance.

       { Thus, the device
       must annotate all calls it makes with one of two fixed appearance numbers
       (usually "0" and "1"), and must display only the status
       of calls with
       those appearance numbers.  Any incoming call indications
       for appearances other than for those appearance numbers should
       be rejected with a 486 or 480 response. }

    7.1.3.  Shared Appearance UAs with Fixed Appearance Number

       This UA is the typical 'business-class' hard-phone.  A number of
       appearances are typically configured statically and labeled on
       buttons, and calls may be managed using these configured appearances.
       Any calls outside this range should be ignored, and not mapped to a
       free button.  Users of these devices often seize specific appearance
       numbers for outgoing calls, and the UA will need to seize the
       appearance number and wait for confirmation from the Appearance Agent
       before proceeding with { a call } .

    7.1.4.  Shared Appearance UAs with Variable Appearance Number

       This UA is typically a soft-phone or graphically rich user interface
       hard-phone.  In these cases, even the idea of an appearance { number } may
       seem unnecessary.  However, for these phones to be able to interwork
       successfully with other phone types, it is important that they still
       use the appearance { number } to govern the order of appearance of calls
       in progress.  No specific guidance on presentation is given except
       that the { presentation order should reflect the ordering of 
       appearance numbers } .  Thought should also be given to
       how an appearance number that has no call associated with it should
       be rendered to the user.  These devices can typically make calls
       without waiting for confirmation from the Appearance Agent {
       regarding } the
       appearance number.

       [...]

       4.  A third call arrives, and is assigned the appearance number of 0.
	   All UAs should be able to render the arrival of this new call to
	   the user.  Multiple appearance UAs should continue to indicate the
	   presence of the second call, and should also ensure that the
	   { order of presentation of calls is that of the appearance
	   numbers and not the order of call arrival } .

E28. In 7.1.4, uses "appearance index", but "index" is used nowhere else in
the draft.  That probably should be "appearance number".

E29. In 7.1.4, the text from "The problems faced by each style" to the end
does not seem to be part of 7.1.4, but rather of section 7.1.  Perhaps
it should be moved to 7.1, between the two existing paragraphs.

E30. In 8.2, "such as hold, etc" does not put a period after "etc".

E31. Sections 8.1, 8.2, and 8.3 appear to be co-equal, but the first two
regard one topic and 8.3 regards another topic.  Instead, the last
paragraph of 8 should become the first paragraph of a new 8.1, of
which the current 8.1 and 8.2 should become subordinates.  (8.3 is
then renumbered as 8.2.)  Since the current 8.1 and 8.2 are short,
perhaps they should be combined to form the new 8.1 without
sectioning, rather than making them the new 8.1.1 and 8.1.2.

E32. In 10, "the Appearance Agent is aware of dialog state events" would be
better phrased "the Appearance Agent is directly aware of dialog
state".

E33. In 10.3, "the appearance assigns" should be "the appearance agent
assigns".

E34. In 10.4 is "Before sending the outgoing INVITE request, Bob publishes
to the state agent that Alice line appearance is in (trying) state.",
which doesn't parse.  Presumably "Alice" is incorrect or incomplete.

E35. In 10.4 is "Note the shortened expiration interval in F2 of 60
seconds."  The significance of this needs to be explained more
carefully.

E36. In 10.4 is:

       <dialog id="id3d4f9c83"
            call-id="f3b3cbd0-a2c5775e-5df9f8d5"
            local-tag="15A3DE7C-9283203B"
                                            direction="initiator">

It appears that the final line is not indented correctly.

E37. In 10.6 is "Bob publishes the termination of the dialog", but the
flow diagram and the listing of messages does not show such
publishing.

E38. In 10.7 is "has a established session" which should be "has an
established session".

E39. In 10.7 is "an attempt to pickup" which should be "an attempt to pick
up".  ("pick up" is the verb, "pickup" is the noun.)

E40. In 10.7 is:

      <dialog id="id3d4f9c83"
          call-id="3d57cd17-47deb849-dca8b6c6"
                         local-tag="8C4183CB-BCEAB710" >

which seems to have the indentation and spacing (before ">") damaged.

E41. Section 10.8 could use some more descriptive text explaining the
sequence of operations.

E42. In 10.8, the text is not clear that the call is between AORs that are
both in the appearance group.  (UAs per se are not in an appearance
group, they have AORs that are (and perhaps some that are not.)  What
is happening is that the UAC is "calling out on" an AOR that is also
the destination AOR.

E43. In 10.9 is "Bob will publish the termination of the dialog with Carol
and also publish the appearance with the dialog with Alice", but it
would be better described as "Bob will publish the termination of the
dialog with Carol and (simultaneously) the appearance with the dialog
with Alice".  The two operations need to be in one PUBLISH request to
prevent any opportunity for another UA to seize the appearance.  The
latter case should be illustrated.

E44. In 10.11 is a reference to messages R24 and F26, but there are no such
messages in the flow diagram.  Presumably they should be F14 and F16.

E45. In 10.13, there should be a sentence or two describing the calling
operations that are illustrated in the flow diagram.

E46. In 10.14 is "Alice cancels the pickup attempt with the PUBLISH F48."
This would be better stated as "Alice reports the failure of the
attempted pickup attempt with PUBLISH F48.", since Alice didn't cancel
the pickup attempt, she tried and it failed.

E47. Why is section 11, "Incoming Appearance Assignment" not part of
section 5, "Normative Description"?

E48. In 11 is "follows normal policies Alert-Info policies", which must be
a mistake.

E49. In 11 is "a normal ringtone should be indicated using the
urn:alert:tone:normal in the Alert-Info", which would be better
phrased "a normal ringtone should be indicated using the URI
urn:alert:tone:normal in the Alert-Info header field".

E50. In 11 is:

   appearance-param = "appearance" EQUAL *DIGIT

Presumably this is supposed to be:

   appearance-param = "appearance" EQUAL 1*DIGIT

E51. In 11, the text does describes several approaches as possible, but
does not make it clear what approach (or combination of approaches) is
required of the system.

E52. In 12, IANA Considerations, the 409 response code is not listed, but I
do not see it listed in the IANA registry.  Is the 409 response new?
If so, it needs to be specified in IANA Considerations.

E53. In 14, "Event Package for Dialog State as define in" should be "Event
Package for Dialog State as defined in [RFC4235]".

E54. Section 14 refers to a number of RFCs, but none of them are listed as
Normative References.  It seems to me that any RFC that is "included
by reference" into the Security Considerations should be listed as a
Normative Reference.

Dale




From dworley@nortel.com  Fri Dec  4 14:07:19 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 993363A687C for <bliss@core3.amsl.com>; Fri,  4 Dec 2009 14:07:19 -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 vmTSPYV8kjnx for <bliss@core3.amsl.com>; Fri,  4 Dec 2009 14:07:19 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 911F13A63C9 for <bliss@ietf.org>; Fri,  4 Dec 2009 14:07:18 -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 nB4M6gC02909; Fri, 4 Dec 2009 22:06:53 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 4 Dec 2009 17:04:41 -0500
From: "Dale Worley" <dworley@nortel.com>
To: Alan Johnston <alan@sipstation.com>
In-Reply-To: <4AF7C6F3.1070400@sipstation.com>
References: <4AF7C6F3.1070400@sipstation.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Fri, 04 Dec 2009 17:04:41 -0500
Message-Id: <1259964281.3761.34.camel@khone.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Dec 2009 22:04:41.0867 (UTC) FILETIME=[C7BF6DB0:01CA752D]
Cc: BLISS <bliss@ietf.org>
Subject: Re: [BLISS] Shared Appearance use of Event header parameter
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, 04 Dec 2009 22:07:19 -0000

On Mon, 2009-11-09 at 01:38 -0600, Alan Johnston wrote:
> The Shared Appearance draft defines a "shared" event parameter.
> 
> The question is whether this should instead be a SIP feature tag used in 
> a Supported and Require header fields.

Using a feature tag would make the determination by the UA of whether it
was talking to an Appearance Agent completely unambiguous.  Currently
the logic of that test is a bit fuzzy, since sending SUBSCRIBE with
"Event: dialog;shared" to a dialog state agent that does not understand
SA will succeed.

Dale



From dworley@nortel.com  Fri Dec  4 14:16:54 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 BE0E328C0EF for <bliss@core3.amsl.com>; Fri,  4 Dec 2009 14:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_66=0.6, 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 D01s3mJT4vWR for <bliss@core3.amsl.com>; Fri,  4 Dec 2009 14:16:43 -0800 (PST)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 883AE3A6970 for <bliss@ietf.org>; Fri,  4 Dec 2009 14:16:38 -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 nB4MGO626715 for <bliss@ietf.org>; Fri, 4 Dec 2009 22:16:24 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 4 Dec 2009 17:16:23 -0500
From: "Dale Worley" <dworley@nortel.com>
To: BLISS <bliss@ietf.org>
Content-Type: text/plain
Organization: Nortel Networks
Date: Fri, 04 Dec 2009 17:16:23 -0500
Message-Id: <1259964983.3761.39.camel@khone.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Dec 2009 22:16:23.0960 (UTC) FILETIME=[6A3A5180:01CA752F]
Subject: [BLISS] Comments on draft-ietf-bliss-shared-appearances-04 by implementor
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, 04 Dec 2009 22:16:57 -0000

I've been sitting on the following notes written by Carolyn Beeton.  She
has the distinction of having implemented a Shared Appearance Agent
(draft-anil-03, IIRC), so I think that her comments in regard to the
machinery are particularly relevant.

Dale

-----------------------------------------------------------------------

>From Carolyn Beeton:

    Overall discussion of appearance number and handling of multiple calls

I think the notion that an appearance number can be known to map to a
known physical button on a UA breaks down pretty quickly (e.g. scenarios
in section 10.3, 10.9, 10.12, 10.15).  So I think we should give up on
that one right away, and instead recommend even more strongly than the
current draft does that "the appearance number is readily apparent to
the user" (which is currently mentioned in the Intro).

Also, I think that trying to hold too firmly to the old key system
model is a mistake.  In the old system, if one set had seized the line,
no-one else could.  That is not the case in SIP, and I think that to,
for example, prevent a call from ringing at a set with one button for
the shared AOR because some other set is currently on a call, is a
huge mistake.  (This scenario is described in the examples at the end
of section 7.1.4)

And I think that expecting users to be able to figure out which call to
pick up or join is unreasonable without a lot of help from the UA, and
displaying call information (e.g. From user) is not sufficient.  If you
think of a help desk application, and Alice wants Bob to pick up a call
she has placed on hold, she needs to be able to tell him which call.
She shouldn't have to figure out which appearance number her button
happens to map to, and hope that he can figure it out on his set too.
"appearance 2" does not map to a physical button labelled "line 2".
On one set it might be physically in a different place from line 2 on
another set (e.g.

     x x   vs x                    
     x x      x   

- is line two the second one in the first row or the first one in the
second row?)  And she shouldn't have to announce the calling user's name
or number, if a unique one is even available.  Therefore it seems to me
to be a requirement that the UAs mark each appearance instance clearly,
by number.

Note that since I recommend exposing the appearance number to the user, I
also recommend starting at "1", not "0" - I don't think this is explicitly
called out anywhere in this spec, though most places seem to assume
"0" except maybe in section 10.2 which seems to show "1" for a first
incoming call.

All of this is very important in a Call Group scenario where more than
one call is likely to be active or on hold at the same time.  You don't
want to guess when you're taking a call off hold - is this the president
or my wife?

Abstract:
    - missing something like "This feature allows several sets to share a
      common AOR, and pick up or join calls within the group." i.e. what does
      the feature DO.

Introduction    
    - para 4: typo "typically each appearance or an AOR" ==> "of"  
    - para 4: recommend splitting the paragraph before "In addition..."
    - "appearance number": its purpose is to identify active calls to
      facilitate sharing between users (e.g. passing a call from one
      user to another).  If a telephone has enough buttons/lamps, calls
      could be presented on the nth button.  If not, it may still be
      desirable to present the call state, but the appearance number
      should be displayed so that users know which call, for example,
      is on hold on which key.


3.  Usage Scenarios    
    - "The differences relate to the user interface considerations of
    the device." ???

3.2 Call Group
    - it said above that it would not use the term "line appearance".  
    - "share the line appearances of each other" - these phones are not
      sharing appearances "of each other": they are all sharing the
      shared AOR.
    - "A shout"... sounds very unprofessional. 
    - "Another phone can request to be added, joined, or bridged to
      an existing appearance": here "appearance" really means a call.
      Are "added, joined, or bridged" three words for the same thing or
      three different things"?
    - What happens in this model if a phone selects a busy line?

4.1.  Requirements 

    - REQ-3 worded quite differently from the others "Calls
      can be joined"...  maybe "A UA must be able to join (bridge or
      conference) or pick up an existing call"
    - REQ-5 what about large numbers of shared AORs?
    - REQ-7 typo "learn the appearance status of the the group" -
      delete second 'the'
	     -  I think it means "the status of all appearances of the group 
            (shared AOR)" 
    - REQ-9.  Really? the importance of the appearance number is that users
      can tell each other which call to join or pick up.  Do they need to be
      able to tell each other which call they are answering? (maybe)
    - REQ-12.  Why not? (why not allow UAs outside the group to select
      or manipulate app numbers).  I'm thinking there might be some app
      which wants to call "line 2".  Also, don't we want to require that
      NOTHING (including one of our UAs) manipulate the appearance number
      once it's set?
    - REQ-13 - how is this different from any normal SIP call on hold etc?    
    - REQ-14 - this point isn't really developed anywhere else in the spec
    - REQ-16: I don't understand "ringdown".  If appearance number
      corresponds to a physical button, then how can this work?  What if
      two users press the same button at the same time?

4.2.  Implementation

    4: "UAs receive the appearance number to use in rendering the
       incoming call in a NOTIFY from the Appearance Agent and in the
       INVITE itself."  Why in two places?  This increases the complexity.
       Or is it in the NOTIFY just because all NOTIFYs with dialog state
       changes will include it?  In which case, why mention it specially?

    6: "if the user does not select an appearance or does not care" - why
       allow this?  Why not require PUBLISH with appearance number
       before seize?  If the UA can "learn" appearance number as the
       call progresses, why can't it "learn" it for incoming calls also?
       Then we wouldn't need to INVITE to include Alert-Info, which
       simplifies all implementations as it removes a big tie between
       the Proxy and the AA (all that is left is status updates).

5.2.3 <joined-dialog>

    - "Only the UA which is performing the actual media mixing
       should include this element in notifications to the Appearance
       Agent."
    - what notifications?  default impl does not have notifications from
      UA to AA? (should it read publications?)

5.3 UA

    - OPEN ISSUE #2 (pg 11): "Replaces and Join support is a SHOULD".
      Without these, we just have another BLF implementation... I think
      Replaces at least should be a MUST.

    - point 2. on pg 12: UA must PUBLISH when "the user has requested
      that an appearance number not be used for an outgoing call" -
      I think this would also be used for Music on Hold calls (we don't
      want them rendered at other sets!), but in this case it wouldn't
      be requested by the user...

    - para at top of pg 13: "This publication SHOULD be refreshed
      during the early dialog state... one it has transitioned to the
      confirmed state, no publication refreshes are necessary"  Does
      this conform to the PUBLISH spec?  The shorter refresh during
      early is forced by the OK response to the PUBLISH, but how is a
      longer refresh once confirmed communicated?  Also, why are we not
      worried about sets dying while they are on a call?

    - para 2 on pg 13: "A UA SHOULD render the appearance number to
      the user or display appearance status information to the user in
      a way that preserves the appearance order." I think this should
      be a MUST.

    - para 3 on pg 13: "A UA that does not need to select a particular
      appearance number (or doesn't care) would just send an INVITE as normal"
      (i.e. without PUBLISHing first)
      - and the AA will assign one.  But I don't see why we allow this.  It
        muddies the appearance number waters even more.  How will the user be
        able to tell someone else how to pick this call up?

    - para 4 on pg 13:  "If the Appearance Agent policy does not allow
      calls without an assigned appearance number, a 409 Conflict response
      will be received, and the UA will republish either selecting/seizing
      an appearance number or without one, in which case the Appearance
      Agent will assign one."  
      - so second PUBLISH with same info is handled differently... is this
        good?  AA must remember previous requests... 
      - wouldn't it be better to have an explicit "don't care" value?
      - why would AA not allow calls w/o assigned appearance number?

    - para 5 on pg 13: "When an INVITE is generated to attempt to
      bridge or take a call... the appearance number of the joined or
      replaced call SHOULD be used".  Really?  i.e. in 10.7 (Appearance
      Pickup), the INVITE from Alice to the Proxy at F38 should have
      Alert-Info header? I don't think so...

 5.4 Appearance Agent

    - para 5: "An Appearance Agent SHOULD assign an appearance number
      to an outgoing INVITE if a PUBLISH has not been received
      selecting/seizing a particular appearance number."  
      - but we won't put Alert-Info headers in outgoing INVITEs?  does it
      mean dialog here (i.e. "to the dialog for an outgoing call")?
      - why is this a SHOULD?  if it doesn't assign an appearance number,
        should it then do what is described in the 2nd para on pg 15?

    - para 6: "Note that if the appearance group has non-shared
      appearance UAs, the Appearance Agent will still allocate appearance
      numbers for INVITEs sent by those UAs."
      - why? if I press a not-shared line key for the group AOR, and
        place an outgoing call there, why should it be assigned an
        appearance number, so that the next INCOMING call would ring on
        app 2 of the shared AOR keys?
      - is the AA supposed to send NOTIFYs telling group members that this
        appearance number is being used? even though I didn't press a shared
        line key?

    - para 1 on pg 15: "A 409 Conflict response is returned if the
      chosen appearance number is invalid, and an immediate NOTIFY should
      be sent to the UA containing full dialog event state."
      - why send a NOTIFY as well?  409 is a legit error if two users
      press the line key at the same time... one will get 409, and its
      UA can resend with another appearance number... no need to send
      full NOTIFY... (NOTIFY will happen anyway because of the first
      user's seize; no special logic should be required)

    - para 2 on pg 15: Can you give some examples of why an AA might
      have a policy of not allowing PUBLISH without an appearance number?
      The most common use case I have encountered would be a Music
      On Hold call, which should not be shared with other members of
      the group.  This spec also mentions consultation calls (I'm not
      so sure about that).  Why would they be refused?

    - para 5 on pg 15: "If an INVITE is sent and no appearance number
      is available, the proxy MAY reject the INVITE with a 403 Forbidden
      response code."
      - INVITE sent by whom and to whom?  It sounds like it means an INVITE
        incoming to a set (i.e. "an INVITE is received and...").  
      - "No appearance number is available"... what is the limit? INTMAX?

7. User Interface Considerations
    
    7.1.1 Single Appearance UAs
    - regular SIP mechanisms for rejecting a second call will not kick in
      because the set is not really "busy"
    - these sets are not really suitable for shared lines... for example, they
      could not place a call if anyone else in the group was busy
        
    7.1.2 Dual Appearance UAs
    - so, and?  do we expect them to reject all but "0" and "1"? or just "0"?

    7.1.4 Shared Appearance UAs with Variable Appearance Number
    - even with the fanciest set, it will still be necessary for Joe to shout
      to his colleague, "pick up the call on line 2", and he needs to know
      what "line" it is (even though it isn't a line at all...)
    - "Thought should also be given to how an appearance number that has no 
      call associated with it should be rendered..." ?huh? you mean one that
      is reserved for some other set?  why render it at all until there's a
      call?

    7.1.4 2nd para (which shouldn't really be part of 7.1.4)
    - point 4: typo "Multiple appearnce UAs should continue " ==> appearance
    - UAs should strongly consider displaying the appearance number
      directly beside the lamp, to facilitate communication (e.g. pick
      up line 2)


8 Interop with non-Shared Appearance UAs

    - "It is desirable to allow a basic UA that does not directly support
       shared appearance to be part of a shared appearance group."
       - is it?  they won't be able to pick up calls on hold or join calls.
       Calls they make will be visible to others in the group (if implemented
       the way described here), but they won't be able to tell anyone WHICH
       call...
    - We can't prevent UAs which don't support shared appearances from
      registering to the group AOR
    - This part is "desirable", not required - if not implemented, then
      non-shared registrations to shared AORs will not consume appearances and
      will not function as shared appearances - I think this model is fine too

8.1 Appearance Assignment
    - it's not clear to me why a UA that is registered to the group AOR
      but is not shared should be using appearances at all.  Is the intent
      that it could still put calls on hold, which others could then
      pick up?  But that user could not tell the others which call to
      pick up...  and especially if the non-shared UA does not support
      Join or Replaces, then there was really no point in consuming
      an appearance (and perhaps, according to examples in the spec,
      preventing another set with only one appearance from alerting for
      an incoming call at all!)

8.3 UAs Supporting Dialog Events but Not Shared Appearance
    - presumably the AA will SUBSCRIBE for dialog events from these sets?
      (that being the point of the section) - which it does not normally do
    - "This type of UA will be detected by the Appearance Agent by the
       absence of the 'shared' event parameter in SUBSCRIBE or PUBLISH
       messages."
       - the UA won't send SUBSCRIBE ever (since it doesn't support
       this spec).  So how will the AA detect the absence of the
       'shared' event?
       - I think this will need to be provisioned (and so should be mentioned
         in 9. Provisioning Considerations)

10.1 flow for Registration and Subscription
    - Bob REGISTERS with contact bob@ua2; Alice with alice@ua1; but in
      practice the part before the @ might be the group AOR?  What if a UA
      registers to two shared AORs?
    - subscription flow is triggered by UAs SUBSCRIBEing to "dialog;shared" events
      (AA does nothing on startup)
    - F3 to F6 (pg 22): delete one of the "also"s (probably the second one)
    - CSeq numbers are awfully high!
    - F4: Allow-Events is just "dialog"? not "dialog;shared"?

10.2 Appearance Selection/Seizure for Incoming Call
    - para 2: "if Carol answers both Alice and Bob and keeps both dialogs
      active, then the Appearance Agent will need to resolve the situation
      by moving either Alice or Bob's dialog to a different appearance."
      ===> which means that the whole appearance number thing is mucked up,
      unless you require the UA to SHOW it
    - is "appearance" going to start at 1?  should this be mentioned somewhere?
    - what is the point of the NOTIFYs at F2 and F4? since all the sets are
      going to be ringing, and the INVITE will have the appearance number in
      it?  Are UAs really supposed to wait for a NOTIFY before they present
      the call? 
    - F4 and all dialog;shared events in the doc: missing the "sa:"
      prefix on the end tag (e.g. "<sa:appearance>1</appearance>" should
      read "<sa:appearance>1</sa:appearance>")
    - F4: the AA creates a unique dialog id
    - F21, 23: NOTIFYs are sent to all members of the group (everyone
      SUBSCRIBEd to the group AOR)

10.3 Outgoing Call without Appearance Pre-Selection
    - it's pretty hard to map this scenario onto one where sets have buttons
      which are called "line 1" or "line 2".  Doesn't Bob have to pick one?
      And if he doesn't, how do we tell him what appearance number he got, so
      that he can "shout or IM" to someone else to tell them to pick up the
      call after he holds it? (or to join the call)
    - F4: appearance is 0 here.  Are they going to start with 1 or 0? or does
      0 mean something special?
    - F10, F12: what are these?  the state in F4 is "trying"; would these be
      "early"?  Do we need to know that the far end is ringing?  Instead of
      (or maybe as well as) F6, one at least of these should be spelled out.
    - F18, 20: these are "confirmed".

10.4 Outgoing Call with Appearance Pre-Selection
    - note that all subscribers receive the NOTIFY marking the appearance as
      "seized" (F3, F5).  This could be spelled out in the "F1 to F4"
      discussion by saying 
      "The Appearance Agent notifies Alice (and all other appearances 
      *, including Bob*) of the same event..."
    - probably should NOT say "by forwarding the NOTIFY payload provided by
      Bob".  For one thing, it wasn't NOTIFY content - it was PUBLISH content.
      For another, it isn't being forwarded, it is being sent as a partial
      update to all subscribers.
    - typo "loose the appearance" ==> "lose the appearance"
    - F2: Allow-Events is just "dialog"?
    - if the AA changes the dialog id, this would presumably show up in F3/F5.
      Would Bob be expected to use it in F10?

10.5 Outgoing Call without using an Appearance Number
    - example use case: music on hold call?
    - what's the use case for refusing such a request?  After all, we allow
      outgoing calls that didn't do this PUBLISH step at all...
    - isn't the point of not using an appearance number that the other sets
      won't see it?  so no F3, F5, F14, F16, etc... 

10.6 Appearance Release

    - "Bob publishes the termination of the dialog and the Appearance
    Agent de-allocates the appearance number used." but this is not shown in
    the callflow.  Bob does not need to publish the termination of the dialog,
    because the AA is aware of it from the Proxy. (PUBLISH on termination is
    not listed in section 5.3 where it describes when UAs must PUBLISH)


10.7 Appearance Pickup
    - what if Alice doesn't PUBLISH?  regular SIP rules must handle the INVITE
      w REPLACES contention.  F42/F44 will still happen...  What value does
      the PUBLISH add?  is the Proxy supposed to reject the INVITE?

10.8 Calls between UAs within the Group
    - what is this trying to show?
    - it isn't clear to me whether Bob is calling Alice or HelpDesk@ua1.example.com
    - it isn't clear to me whether Bob is calling "on" the shared line (from
      Bob or from HelpDesk@ua2.example.com)
    - if so, why isn't the regular PUBLISH-to-seize stuff happening?
    - is the NOTIFY at F2/F4 to show that app=0 is in early state for Bob's
      outgoing call? or that app=1 is in early state for the incoming call?
    - why is only one NOTIFY frame called out in detail?  and it isn't F16
      (which is an ACK). don't know which one it is...  It shows
      <state>connected</state> - I thought it would be "confirmed" not
      "connected"

10.9 Consultation Hold with Appearances
    - how is this going to work in practice?  If Bob only has one key for the
      shared line, how can he call Alice on the shared line if Carol is on
      hold? this describes how the UA might do it, but I don't see how a user
      would do it...
    - "Note that if Carol hangs up while Bob is consulting with Alice, Bob
       can decide if he wants to reuse the appearance number used with Carol
       for the call with Alice." -- how the heck would you model that for
       a user?


10.10 Joining or Bridging an Appearance
    - what is the difference between the NOTIFYs at F27/29 and F40/42?  trying
      vs confirmed? is the one at F27/29 really necessary?
       
10.11 Appearance Allocation - Loss of Appearance
    - typo "frees up the appearance using NOTIFYs R24 and F26" should be F26 -
      actually, should be F14 and F16!
    - what is the line between Proxy and AA showing after Appearance selection
      times out?  Isn't it the AA's PUBLISH server which will detect the
      timeout?  Why is the Proxy involved?
    - "After retransmitting the NOTIFY F26 [should be F16] to Bob, the
      subscription is terminated" - does "retransmit" mean "transmit"
      or are there two NOTIFYs? (I expect not...) Does the NOTIFY have
      subscription-state="terminated"? (not sure if this is even legal if
      the other end didn't send SUBSCRIBE with Expires=0) Shouldn't the
      subscription be terminated when the PUBLISH receives a fatal error
      (i.e.  timeout), and is there any point in sending a NOTIFY then?

10.12 Appearance Selection Contention
    - this is a fine example but also shows why expecting a hard mapping
      between appearance number and physical button on the set is
      unsupportable (i.e. Alice did not press the 3rd button for the
      appearance, she pressed the 2nd one...).  The UA must be required
      to display the appearance number somewhere.

10.13 Appearance Agent Subscription to UAs
    - maybe it's just because I'm used to the anil draft, but this does not
      make clear whether the AA SUBSCRIBEs to "dialog" or "dialog;shared".  I
      think it is just "dialog", i.e. the events will not contain any
      appearance number info.  But since F5 and F9 are not spelled out, I'm
      not sure.
    - I would think that Bob should still PUBLISH - the UA behaviour should be
      exactly the same, and the AA's subscription to it should be completely
      independent (because anyone can subscribe for "dialog" events any time,
      can't they?)
    - F5 is the AA SUBSCRIBEing for "dialog" (I think)
    - F9 is Bob SUBSCRIBEing for "dialog;shared"
    - this section should follow 10.15

10.14 Appearance Pickup Race Condition
    - ?? Bob (shared user) on call with Carol; Bob presses hold; "Alice
      attempts to pick up the call but Bob hangs up before the pickup can
      complete" - I think it means Carol hangs up (based on the flow at F38).
      Rather important distinction...
    - a UA is not required to PUBLISH when a call is released, (see 10.6)
      so why would a failed call be any different?  The Proxy knows
      that the call failed, so I would expect a dotted line after F47
      and then a NOTIFY from the AA to Bob and Alice

11 Incoming Appearance Assignment
    - this section is pretty rough
    - "For the dialog package parameter approach" - unclear.  Are two ways
      really described here?  I think one way is NOTIFY independent of the
      INVITE, and the second way is INVITE with Alert-Info (and also NOTIFY!)
      but this paragraph is not very clear
    - missing period at the end of the 2nd para
    - here it implies that "appearance=0" means the first instance - as it
      does in most places, except in section 10.2

14. Security Considerations
    - section should appear before section 12



From dworley@nortel.com  Sun Dec  6 12:53:22 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 66F633A67B0 for <bliss@core3.amsl.com>; Sun,  6 Dec 2009 12:53:22 -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 sehjmtSKc7VP for <bliss@core3.amsl.com>; Sun,  6 Dec 2009 12:53:21 -0800 (PST)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id BE3493A68BD for <bliss@ietf.org>; Sun,  6 Dec 2009 12:53:20 -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 nB6Kr6817905 for <bliss@ietf.org>; Sun, 6 Dec 2009 20:53:06 GMT
Received: from [47.141.31.136] ([47.141.31.136]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 6 Dec 2009 15:53:05 -0500
From: "Dale Worley" <dworley@nortel.com>
To: BLISS <bliss@ietf.org>
Content-Type: text/plain
Organization: Nortel Networks
Date: Sun, 06 Dec 2009 15:53:05 -0500
Message-Id: <1260132785.18861.11.camel@khone.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 Dec 2009 20:53:05.0658 (UTC) FILETIME=[1BD575A0:01CA76B6]
Subject: [BLISS] Updated open issues list for draft-ietf-bliss-call-completion-05
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, 06 Dec 2009 20:53:22 -0000

The new -05 version of draft-ietf-bliss-call-completion moves things
along considerably.  I've updated the open-issues list (excepting the
purely editorial items) and appended it to this message.  I'll follow up
with fuller discussion of the open items.

Dale
------------------------------------------------------------------------
[Open issues list, annotated and updated based on the -05 draft.  New
text is indented.]

Now that we are close to completion on
draft-ietf-bliss-call-completion, I am compiling a comprehensive list
of open issues.  The list is divided into three sections, which need
to be tackled in order:  "Substantial" issues which involve the
sequence of operations or dataflow among the participants, "Technical"
issues like the particular format of headers, and "Editorial" issues
which are entirely about how the document is written.  The issues are
assigned numbers as we insert them, starting at 1001, 2001, or 3001,
depending on the group that it was initially inserted in.

Status of issues (in my opinion):

    Substantial
	1001 resolved
	1002 resolved
	1003 open
	1004 resolved
	1005 resolved
	1006 resolved
	1007 resolved
	1008 open
	1009 open
	1010 open
	1011 open
    Technical
	2001 resolved
	2002 resolved
	2003 resolved
	2004 open

** Substantial

* 1001  Do we need to correlate a CC SUBSCRIBE with its original INVITE?

Do we need to correlate a CC SUBSCRIBE with its original INVITE as a
security mechanism?

    We have decided that since the PSTN CC mechanism does not verify
    that the CC request comes from a phone that previously made a call
    to the destination, SIP CC will not attempt to do so.

* 1002  Describe use of dialog event package as a fallback strategy

I'm marking this as a substantial change, as we seem to intend to
include the fallback as an integral part of the CC mechanism, even if
it is technically separate.  There may need to be a discussion as to
how to structure the I-Ds/RFCs...

We also should think about interoperation, where both techniques are
used together.

    This is taken care of by section 4.3.

* 1003  Hutton: CC URI

"Hutton, Andrew" <andrew.hutton@siemens.com>
Section 5.6: "Question: Should the callee's monitor supply a URI which
should be used in the CC call?"
I think it should.

[Responded to.  Proposed that MAY->SHOULD in section 5.7:  The
notification MAY also contain also a URI which should be used in the
CC call.  Text change proposed.]

    The text in question is now in 7.3:

    The notification MAY also contain a URI which should be used for
    suspension requestst.

    Should we change this to SHOULD?

* 1004  Hutton: Marking

"Hutton, Andrew" <andrew.hutton@siemens.com>
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).

[Replied to.  This is part of the "correlation problem", 1001.]

    As previously, CC recalls are marked with "m=XX" in the
    request-URI.  And we have decided to not implement correlation, so
    that original call Call-ID does not need to be carried.

* 1005  Hutton: Failure

"Hutton, Andrew" <andrew.hutton@siemens.com>
Section 5.6: "Can a call appear to succeed from the 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 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 answered, so it
would be up to the caller to invoke CCNR (again) if that is what he
wants

[section 5.5 of -03 seems to cover this]

    See the 4th para of 4.2:

    The calling user indicates to the caller's agent that he wishes to
    invoke call-completion services on the recent call.  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".

* 1006  Hutton: 180 Ringing

"Hutton, Andrew" <andrew.hutton@siemens.com>
Section 6: I think that the URI of the monitor (i.e. 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.

[Responded to.  I think there is a consensus for this change, but -03
doesn't include it.  Text change proposed.]

    This has been incorporated by stating that the Call-Info header should
    be added to both provisional and final responses.  This change is in a
    number of places in the text; search for 'provisional'.

* 1007  Suspend/resume

OK, what was the consensus regarding suspend/resume procedures?

    Suspend/resume is done via PUBLISH.  See section 5 para 7 et seq.

* 1008  Absence of correlation requries elucidation of security issues

If CC does not enforce correlation with incoming calls, we need to
document how implementations should ensure privacy.

    Section 11 (Security Considerations) needs to be updated to take care
    of this.  The text in -05 still describes CC correlation.

* 1009  Retain option

We need to establish how the retain option is handled.

    I think we still need to flesh out how retain is implemented.  My
    impression is that in the PSTN, the two endpoints negotiate
    whether retain will be used, and we need to duplicate that
    process.

* 1010  Effect of non-correlation on the event model

In principle, each SUBSCRIBE that arrives identifies some particular
state data.  This is problematic in CC, because we really want to have
each SUBSCRIBE (or rather, each group of SUBSCRIBEs with the same
Call-Id) to identify one "state" (whether that CC request is chosen
for callback), even if there is no overt difference between two
SUBSCRIBEs (other than a different Call-Id).  If we are doing
correlation, then each SUBSCRIBE can be modeled as monitoring the
state associated with the original call.  But if we do not do
correlation, SUBSCRIBEs do not map into original calls, even in
theory, and we need to construct a new event subscription model.  This
is probably not difficult, but does need to be done.

    Section 5 discusses this.  I think this has not been fully
    clarified, though, as section 5 says that the SUBSCRIBE is
    "addressed to the managed URI" but that the CECE it refers to is
    "identified by the request URI".

* 1011  Forking of the CC SUBSCRIBE to multiple destinations

Andrew Hutton notes that the SIP stack in some UAs may not be able to
send several SUBSCRIBEs to several destinations using the same
Call-Id.

The answer is that it is not *necessary* for these SUBSCRIBEs to be
forks of the same transaction.  If they have separate Call-Ids, there
are certain inefficiencies but no loss of functionality:  A monitor
might receive forks of more than one of these SUBSCRIBEs and not
realize that they are merged requests, and will establish multiple
queue elements.  But only one of these queue elements will be selected
for callback.

    We need to add some text to section 6.2 about this.  (I think in older
    versions there was a requirement that the same Call-Id should be
    used.)  This shouldn't be difficult to address as it is actually an
    efficiency measure.

** Technical

* 2001  Hutton: SUBSCRIBE

"Hutton, Andrew" <andrew.hutton@siemens.com>
Section 5.4: "Question: Should the specification of the original call be
done in the SUBSCRIBE body rather than in an event-param?".
I think I would vote for using the event-param.

    This is (probably) obviated by the decision to not do call correlation.

* 2002  Timers

The protocol timers still need to be specified.  See the note in
section 7.6.

    The discussion of timers is now in 9.4 and 9.6, and appears to be
    sufficient.  (The timer specifications needed for CC are minimal.)

* 2003  Rate of Notifications

John has the following question regarding section 7.11 and the rate of
notifications:

   The call completion service typically involves a single notification
   per notifier and per subscription but MAY involve several
   notifications separated by a call completion call that failed due to
   a busy call completion target.  Typically, notifications will be
   separated by at least tens of seconds.  Notifiers SHOULD NOT generate
   more than two notifications in any ten-second interval.

   John: A common situation might be a successful subscription to CCBS,
   resulting in an initial NOTIFY "queued", and then the callee becomes
   free a couple seconds later, resulting a second NOTIFY "ready".
   Similarly following resume.  It does not seem reasonable to suppress
   or delay that second NOTIFY.  I think the recommendation is too
   severe.  Perhaps NOTIFYs in response to SUBSCRIBEs need to be
   excluded from this.

   Dale: I'm quite willing to modify this prescription.  I only included
   it because RFC 3265 says that there must be a prescription; I believe
   that if a monitor generate NOTIFYs only in response to relevant
   events, its NOTIFY rate will be low enough.

   However each of in the two cases you mention, there are only two
   NOTIFYs, so the prescription as stated cannot be violation, since a
   violation requires 3 NOTIFYs.

Regarding -05:
   The current 9.1 modifies that restriction to "SHOULD NOT generate
   more than { three } notifications...".  9.1 also includes a
   better explanation of the consequences of this rule.  I think the
   increase in the limit is to allow transitions from queued to
   ready to more often be sent promptly, which would reduce the
   problem John identifies.

* 2004 Failure codes for CC SUBSCRIBE

[New for -05.]  The text is inconsistent regarding the failure code
for a CC SUBSCRIBE for a call that the monitor has no record of:  7.2
says 404, 9.7 says 481.  It seems to me that 404 should be reserved
for SUBSCRIBEs for which the monitor cannot identify the managed AOR,
and 481 used for SUBSCRIBEs that designate a proper AOR but not a
known call for that AOR.


