Re: [Gen-art] Gen-ART review of draft-ietf-bliss-shared-appearances-11

"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 29 June 2012 19:18 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54B0C21F8865; Fri, 29 Jun 2012 12:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.952
X-Spam-Level:
X-Spam-Status: No, score=-102.952 tagged_above=-999 required=5 tests=[AWL=0.647, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 D2sT0e2dOwwG; Fri, 29 Jun 2012 12:18:32 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id D1EF821F87EC; Fri, 29 Jun 2012 12:18:31 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAIj+7U+HCzI1/2dsb2JhbABFhVqvXoEegQeCGAEBAQEDEhERRRACAQgNCwICJgICAjAVEAEBBA4NGodpnnqKHpMggSCPDzJgA5sriguCew
X-IronPort-AV: E=Sophos;i="4.77,499,1336363200"; d="scan'208";a="313255578"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 29 Jun 2012 15:15:55 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 29 Jun 2012 14:59:49 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Fri, 29 Jun 2012 15:18:28 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "alan.b.johnston@gmail.com" <alan.b.johnston@gmail.com>
Date: Fri, 29 Jun 2012 15:18:24 -0400
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Index: Ac1WK/SS5AOXm0ZpSfqMaQa/q754dw==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A1D0C@DC-US1MBEX4.global.avaya.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com>
In-Reply-To: <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 29 Jun 2012 13:18:37 -0700
Cc: "mohsen.soroush@sylantro.com" <mohsen.soroush@sylantro.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "bliss@ietf.org" <bliss@ietf.org>, "vvenkatar@gmail.com" <vvenkatar@gmail.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bliss-shared-appearances-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 19:18:33 -0000

On Thu, 2012-06-28 at 20:05 -0500, Alan Johnston wrote:
> >
> > 4.1 - REQ-16:
> >
> >   in this case, seizing the line is the same thing as dialing.
> >
> > 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.
> 
> 
> This requirement is about sending one request that causes both actions
> to occur.  In a PSTN ringdown circuit (a very specialized circuit,
> used for "hotlines"), the two operations are the same thing.  Besides
> this statement, is REQ-16 itself not clear?  Perhaps I should just
> remove this statement if it adds confusion rather than clarity to the
> requirement.

IMHO, a good fix is:

   REQ-16 The mechanism should support a way for a UA to seize a
   particular appearance number and also send the request at the same
   time.  This is needed when an automatic ringdown feature (a telephone
   configured to immediately dial a phone number when it goes off hook)
   is combined with shared appearances - in this case, seizing the line
   is >>>integrated with<<< dialing.

Dale