Re: [VIPR] [ViPR] draft-jennings-vipr-overview-00, Clarification on Ticket verification

Cullen Jennings <fluffy@cisco.com> Fri, 15 July 2011 00:51 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: vipr@ietfa.amsl.com
Delivered-To: vipr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB2521F86D6 for <vipr@ietfa.amsl.com>; Thu, 14 Jul 2011 17:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.408
X-Spam-Level:
X-Spam-Status: No, score=-104.408 tagged_above=-999 required=5 tests=[AWL=-1.809, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bq76TQxHuqWZ for <vipr@ietfa.amsl.com>; Thu, 14 Jul 2011 17:51:53 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id EDD4321F86D2 for <vipr@ietf.org>; Thu, 14 Jul 2011 17:51:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1181; q=dns/txt; s=iport; t=1310691113; x=1311900713; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=kniBV3/EpzqgESa6OqwQptGN7aequb8Kbp02KCa9HE0=; b=So1FRHmBnQuEA4Tuu7rPo/vOqjJMI4nP86FFkyymb/A2pALBOilnODDK xJBhq7eIJjpnL9fh9n6RmgChdCHE53u1/QGqkw+Yxx5ti1zvlCPT+zyVL 9pr47AfMI1U9Rqa2EO3mvCbL2UjX4JnXZqWt/EuXml8IhT3P327mb+bRf E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsQHANWOH06rRDoJ/2dsb2JhbABUmGWOe3eIeqVHngmFW18Eh1OLEZBx
X-IronPort-AV: E=Sophos;i="4.65,532,1304294400"; d="scan'208";a="3127243"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-8.cisco.com with ESMTP; 15 Jul 2011 00:51:51 +0000
Received: from sjc-vpn6-1818.cisco.com (sjc-vpn6-1818.cisco.com [10.21.127.26]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p6F0poRr030693; Fri, 15 Jul 2011 00:51:50 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <1892288606.4720447.1304009158854.JavaMail.root@sz0129a.emeryville.ca.mail.comcast.net>
Date: Thu, 14 Jul 2011 17:51:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C405FE9-0B0A-40DE-A789-552585A84066@cisco.com>
References: <1892288606.4720447.1304009158854.JavaMail.root@sz0129a.emeryville.ca.mail.comcast.net>
To: rob.maidhof@comcast.net
X-Mailer: Apple Mail (2.1084)
Cc: vipr@ietf.org
Subject: Re: [VIPR] [ViPR] draft-jennings-vipr-overview-00, Clarification on Ticket verification
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2011 00:51:53 -0000

On Apr 28, 2011, at 9:45 , rob.maidhof@comcast.net wrote:

> I was looking for some clarification on whether the intent is for the Border Element or Call Agent on the terminating side of the call to verify the ticket? 
> 
> For example, the last paragraph of section 8.4 page36, states that the terminating call agent verifies the ticket, then at the end of the paragraph it states that the call is then forwarded to the terminating call agent. Was the intent to say the BE verifies and then forwards to the CA?
> In relation to this, section 6.3 page 27 states that a responsibility of the BE is to perform ticket verification, while the call agent section 6.2 does not list this as a responsibility. Page 22 states that the CA performs ticket verification.  
> I understand an individual network element could perform both CA and BE functions, if it is simply a terminology issue, perhaps we could structure the text to insure consistency.
> 

Good catches. The intention is the BE would verify the ticket.  A single device could be both the BE and CA but clearly we have text out of sync here. I tried to update it.