From internet-drafts@ietf.org Fri Jul 13 12:16:18 2012 Return-Path: X-Original-To: bliss@ietfa.amsl.com Delivered-To: bliss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA4711E80E2; Fri, 13 Jul 2012 12:16:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.514 X-Spam-Level: X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dolNglG90xv3; Fri, 13 Jul 2012 12:16:17 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46AA811E80C7; Fri, 13 Jul 2012 12:16:17 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.30p3 Message-ID: <20120713191617.7423.49874.idtracker@ietfa.amsl.com> Date: Fri, 13 Jul 2012 12:16:17 -0700 Cc: bliss@ietf.org Subject: [BLISS] I-D Action: draft-ietf-bliss-shared-appearances-12.txt X-BeenThere: bliss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2012 19:16:18 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Basic Level of Interoperability for SIP S= ervices Working Group of the IETF. Title : Shared Appearances of a Session Initiation Protocol (SIP= ) Address of Record (AOR) Author(s) : Alan Johnston Mohsen Soroushnejad Venkatesh Venkataramanan Filename : draft-ietf-bliss-shared-appearances-12.txt Pages : 70 Date : 2012-07-13 Abstract: 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 feature allows several user agents (UAs) to share a common AOR, learn about calls placed and received by other UAs in the group, and pick up or join calls within the group. This document discusses use cases, lists requirements and defines extensions to implement this feature. This specification updates RFC3261 and RFC4235. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bliss-shared-appearances There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-bliss-shared-appearances-12 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-bliss-shared-appearances-12 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From david.black@emc.com Fri Jul 13 15:24:34 2012 Return-Path: X-Original-To: bliss@ietfa.amsl.com Delivered-To: bliss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D588211E80F2; Fri, 13 Jul 2012 15:24:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.482 X-Spam-Level: X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gecG0an+kQNf; Fri, 13 Jul 2012 15:24:33 -0700 (PDT) Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id B6DFE11E80EC; Fri, 13 Jul 2012 15:24:33 -0700 (PDT) Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q6DMP7gM018177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Jul 2012 18:25:07 -0400 Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 13 Jul 2012 18:24:52 -0400 Received: from mxhub31.corp.emc.com (mxhub31.corp.emc.com [128.222.70.171]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q6DMOoCO013417; Fri, 13 Jul 2012 18:24:51 -0400 Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub31.corp.emc.com ([128.222.70.171]) with mapi; Fri, 13 Jul 2012 18:24:50 -0400 From: To: , , , , Date: Fri, 13 Jul 2012 18:24:49 -0400 Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-12 Thread-Index: Ac1Vb8Dn5IHpqMlJQDmiZm9plrtFJQL1mcsg Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208DD8672@MX15A.corp.emc.com> References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.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="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EMM-MHVC: 1 Cc: bliss@ietf.org, ietf@ietf.org Subject: [BLISS] Gen-ART review of draft-ietf-bliss-shared-appearances-12 X-BeenThere: bliss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2012 22:24:35 -0000 The -12 version of this draft resolves all of the comments in the Gen-ART review of the -11 version. Thanks, --David > -----Original Message----- > From: Black, David > Sent: Thursday, June 28, 2012 4:51 PM > To: alan.b.johnston@gmail.com; mohsen.soroush@sylantro.com; > vvenkatar@gmail.com; gen-art@ietf.org > Cc: Black, David; Shida Schubert; bliss@ietf.org; IETF Discussion; Robert > Sparks > Subject: Gen-ART review of draft-ietf-bliss-shared-appearances-11 >=20 > I am the assigned Gen-ART reviewer for this draft. For background on > Gen-ART, please see the FAQ at > . >=20 > Please resolve these comments along with any other Last Call comments > you may receive. >=20 > Document: draft-ietf-bliss-shared-appearances-11 > Reviewer: David L. Black > Review Date: June 28, 2012 > IETF LC End Date: June 28, 2012 > IESG Telechat date: (if known) >=20 > Summary: >=20 > This draft is on the right track but has open issues, described in the re= view. >=20 > This draft describes support for shared appearances in support of multi-l= ine > and shared-line telephone often found in businesses. All of the open iss= ues > are minor. The draft is well-written and reasonably clear for the most p= art, > although significant SIP expertise is required to completely understand i= t. >=20 > Major issues: None. >=20 > Minor issues: >=20 > 4.1 - REQ-16: >=20 > in this case, seizing the line is the same thing as dialing. >=20 > That seems wrong - I would have thought it was a "prerequisite" as > opposed to "the same thing" because seizing the line is immediately > followed by a dialing request. >=20 > 5.3. >=20 > A user may select an appearance number but then abandon placing a > call (go back on hook). In this case, the UA MUST free up the > appearance number by removing the event state with a PUBLISH as > described in [RFC3903]. >=20 > What happens when that can't be done due to UA or network failure? >=20 > 5.4. >=20 > A 400 response is returned if the chosen appearance number is invalid, >=20 > Is that always a 400 (Bad Request) or is any 4xx response allowed? If > it's always 400, add the words "Bad Request" after "400". >=20 > If the Appearance Agent policy does not allow this, a 400 response > is returned. >=20 > Same question. In addition, is 403 Forbidden allowed here? >=20 > If an INVITE is sent by a member of the group to the shared AOR (i.e. > they call their own AOR), the Appearance Agent MUST assign two > appearance numbers. The first appearance number will be the one > selected or assigned to the outgoing INVITE. The second appearance > number will be another one assigned by the Appearance Agent for the > INVITE as it is forked back to the members of the group. >=20 > How does that interact with the single appearance UAs in 8.1.1 that won't > understand the second appearance number? A warning that such a UA can't > pick up its call to its own AOR would suffice, either here or in 8.1.1. >=20 > 9.1 >=20 > A UA that has no knowledge of appearances must will only have > appearance numbers for outgoing calls if assigned by the Appearance > Agent. If the non-shared appearance UA does not support Join or > Replaces, all dialogs could be marked "exclusive" to indicate that > these options are not available. >=20 > Should that "could be marked" be changed to "SHOULD be marked" ? > Also, analogous questions for "could" in 9.2 and "can" in 9.3. >=20 > All three of these affect interoperability. >=20 > 12. Security Considerations >=20 > In general, this section is weak on rationale - the second, third and > fourth paragraphs should all explain more about the purpose of and/or > rationale for their security requirements (e.g., what does the security > mechanism protect against and when/why might that protection be desired > and/or required?). >=20 > NOTIFY or PUBLISH message bodies that provide the dialog state > information and the dialog identifiers MAY be encrypted end-to-end > using the standard mechanisms. >=20 > What are "the standard mechanisms"? List them, and provide references, > please. >=20 > Please ensure that the section 6 XML and Section 7 ABNF are > syntax-checked with actual tools. >=20 > Nits/editorial comments: >=20 > p.10: >=20 > The next section discusses the operations used to implement parts of > the shared appearance feature. >=20 > "The following list describes the operations ..." would be better. >=20 > 5.3.1. >=20 > A UA wanting to place a call but not have an appearance number > assigned publishes before sending the INVITE without an 'appearance' > element but with the 'shared' event package parameter present. >=20 > I think I understand what was intended here, but this would be clearer > if "publishes" was replaced with language about sending a PUBLISH. > It's also not completely clear whether "without" applies to the > INVITE or the PUBLISH, so this sentence probably needs to be reworded. >=20 > 5.4. - Expand B2BUA acronym on first use. >=20 > idnits 2.12.13 ran clean. >=20 > Thanks, > --David > ---------------------------------------------------- > David L. Black, Distinguished Engineer > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748 > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7= 786 > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754 > ---------------------------------------------------- From internet-drafts@ietf.org Mon Jul 30 12:07:33 2012 Return-Path: X-Original-To: bliss@ietfa.amsl.com Delivered-To: bliss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0054C11E819E; Mon, 30 Jul 2012 12:07:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.478 X-Spam-Level: X-Spam-Status: No, score=-102.478 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hQI1GKcj7zym; Mon, 30 Jul 2012 12:07:32 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FDA011E8152; Mon, 30 Jul 2012 12:07:32 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.32 Message-ID: <20120730190732.26595.98603.idtracker@ietfa.amsl.com> Date: Mon, 30 Jul 2012 12:07:32 -0700 Cc: bliss@ietf.org Subject: [BLISS] I-D Action: draft-ietf-bliss-shared-appearances-13.txt X-BeenThere: bliss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2012 19:07:33 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Basic Level of Interoperability for SIP S= ervices Working Group of the IETF. Title : Shared Appearances of a Session Initiation Protocol (SIP= ) Address of Record (AOR) Author(s) : Alan Johnston Mohsen Soroushnejad Venkatesh Venkataramanan Filename : draft-ietf-bliss-shared-appearances-13.txt Pages : 70 Date : 2012-07-30 Abstract: 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 feature allows several user agents (UAs) to share a common AOR, learn about calls placed and received by other UAs in the group, and pick up or join calls within the group. This document discusses use cases, lists requirements and defines extensions to implement this feature. This specification updates RFC3261 and RFC4235. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bliss-shared-appearances There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-bliss-shared-appearances-13 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-bliss-shared-appearances-13 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/