Re: [Dime] AD review of draft-ietf-dime-capablities-update-05

"Glen Zorn" <gwz@net-zen.net> Tue, 21 September 2010 15:35 UTC

Return-Path: <gwz@net-zen.net>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 443473A6A4F for <dime@core3.amsl.com>; Tue, 21 Sep 2010 08:35:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.096
X-Spam-Level:
X-Spam-Status: No, score=-102.096 tagged_above=-999 required=5 tests=[AWL=0.503, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 rMS3lQ+p0TMi for <dime@core3.amsl.com>; Tue, 21 Sep 2010 08:35:39 -0700 (PDT)
Received: from smtpout08.prod.mesa1.secureserver.net (smtpout08-01.prod.mesa1.secureserver.net [64.202.165.119]) by core3.amsl.com (Postfix) with SMTP id 8DB983A6A3F for <dime@ietf.org>; Tue, 21 Sep 2010 08:35:39 -0700 (PDT)
Received: (qmail 29082 invoked from network); 21 Sep 2010 15:36:02 -0000
Received: from unknown (110.164.147.175) by smtpout08.prod.mesa1.secureserver.net (64.202.165.119) with ESMTP; 21 Sep 2010 15:36:01 -0000
From: Glen Zorn <gwz@net-zen.net>
To: "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A0402570160@307622ANEX5.global.avaya.com> <000001cb58dd$b6f53110$24df9330$@net> <EDC652A26FB23C4EB6384A4584434A0402570400@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0402570400@307622ANEX5.global.avaya.com>
Date: Tue, 21 Sep 2010 22:35:28 +0700
Organization: Network Zen
Message-ID: <000f01cb59a2$a28377d0$e78a6770$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: ActYuNAHgWq9++BEQ7un4Mb4eDI9WgAAygEgADSdkVAABP7k0A==
Content-Language: en-us
Cc: dime@ietf.org
Subject: Re: [Dime] AD review of draft-ietf-dime-capablities-update-05
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 15:35:41 -0000

Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] writes:

> > > T2. What happens if the receiver of a CUR does not return a
> > > Capabilities-Update-Answer (CUA)? Is there any timeout or
> > > retransmission strategy in place?
> >
> > Um, TCP?  I guess that I don't understand the question.
> 
> So the answer is that there is no mechanism for timeout / retransmission
> at the application layer.

I guess so.

...