Shared Appearances of a Session Initiation Protocol (SIP) Address of Record (AOR)
draft-ietf-bliss-shared-appearances-11

The information below is for an old version of the document
Document Type Active Internet-Draft (bliss WG)
Last updated 2012-06-28 (latest revision 2012-06-08)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state Waiting for AD Go-Ahead
Telechat date
Responsible AD Robert Sparks
IESG note Shida Schubert (shida@ntt-at.com) is the document shepherd.
Send notices to bliss-chairs@tools.ietf.org, draft-ietf-bliss-shared-appearances@tools.ietf.org
BLISS                                                   A. Johnston, Ed.
Internet-Draft                                                     Avaya
Updates: 3261, 4235 (if approved)                        M. Soroushnejad
Intended status: Standards Track                       V. Venkataramanan
Expires: December 10, 2012                         Sylantro Systems Corp
                                                            June 8, 2012

  Shared Appearances of a Session Initiation Protocol (SIP) Address of
                              Record (AOR)
                 draft-ietf-bliss-shared-appearances-11

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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 10, 2012.

Copyright Notice

Johnston, et al.        Expires December 10, 2012               [Page 1]
Internet-Draft           SIP Shared Appearances                June 2012

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Johnston, et al.        Expires December 10, 2012               [Page 2]
Internet-Draft           SIP Shared Appearances                June 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Conventions used in this document  . . . . . . . . . . . . . .  6
   3.  Usage Scenarios  . . . . . . . . . . . . . . . . . . . . . . .  6
     3.1.   Executive/Assistant Arrangement . . . . . . . . . . . . .  6
     3.2.   Call Group  . . . . . . . . . . . . . . . . . . . . . . .  7
     3.3.   Single Line Extension . . . . . . . . . . . . . . . . . .  7
     3.4.   Changing UAs  . . . . . . . . . . . . . . . . . . . . . .  7
   4.  Requirements and Implementation  . . . . . . . . . . . . . . .  7
     4.1.   Requirements  . . . . . . . . . . . . . . . . . . . . . .  7
     4.2.   Implementation  . . . . . . . . . . . . . . . . . . . . .  9
   5.  Normative Description  . . . . . . . . . . . . . . . . . . . . 11
Show full document text