Re: [Dime] Private-Info AVP

Tom Taylor <tom111.taylor@bell.net> Fri, 06 August 2010 18:08 UTC

Return-Path: <tom111.taylor@bell.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 B2CCE3A6924 for <dime@core3.amsl.com>; Fri, 6 Aug 2010 11:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.123
X-Spam-Level:
X-Spam-Status: No, score=-100.123 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_05=-1.11, MSGID_FROM_MTA_HEADER=0.803, 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 D418e9nmCvDP for <dime@core3.amsl.com>; Fri, 6 Aug 2010 11:08:38 -0700 (PDT)
Received: from blu0-omc3-s32.blu0.hotmail.com (blu0-omc3-s32.blu0.hotmail.com [65.55.116.107]) by core3.amsl.com (Postfix) with ESMTP id CB3923A6A10 for <dime@ietf.org>; Fri, 6 Aug 2010 11:08:37 -0700 (PDT)
Received: from BLU0-SMTP65 ([65.55.116.73]) by blu0-omc3-s32.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 6 Aug 2010 11:09:07 -0700
X-Originating-IP: [69.158.64.160]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP65CB4FEF991EE243761EBFD8910@phx.gbl>
Received: from [192.168.2.11] ([69.158.64.160]) by BLU0-SMTP65.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 6 Aug 2010 11:09:04 -0700
Date: Fri, 06 Aug 2010 14:08:46 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: David Lehmann <dlehmann@ulticom.com>
References: <mailman.123.1280948420.8403.dime@ietf.org><7C3581CDE8F4EE488C7C2A497B59DF161B8E46D995@EXUS.comverse.com><AANLkTin2gcK59pEBP_EzNsct=v5O16dhQMc9C=SOVPCN@mail.gmail.com><A51D8ACD861B7E41BFC7FE5C64BE96481167B026@MTLEXVS01.ulticom.com><fad8d306988.988fad8d306@huawei.com><A51D8ACD861B7E41BFC7FE5C64BE96481167B029@MTLEXVS01.ulticom.com><AANLkTimELdyghDfaxqBcyzV0ujnyVe5RHqBK9AiZtzBM@mail.gmail.com><A51D8ACD861B7E41BFC7FE5C64BE96481167B02C@MTLEXVS01.ulticom.com><AANLkTikR1kY8haazZB0fDao0FX=bFi-GB6scKr2Jkkxu@mail.gmail.com><A51D8ACD861B7E41BFC7FE5C64BE96481167B032@MTLEXVS01.ulticom.com><AANLkTik0dEDTkRLeP1ziQqSuXUbTVj+mCgOOAW25-GAh@mail.gmail.com><A51D8ACD861B7E41BFC7FE5C64BE96481167B034@MTLEXVS01.ulticom.com> <AANLkTimr0X-EFrRD6JLdgnye+OyRWdf5zb-N=RbSD9vB@mail.gmail.com> <A51D8ACD861B7E41BFC7FE5C64BE96481167B03E@MTLEXVS01.ulticom.com> <007d01cb3572$4e48d150$eada73f0$@net> <A51D8ACD861B7E41BFC7FE5C64BE96481167B046@MTLEXVS01.ulticom.com>
In-Reply-To: <A51D8ACD861B7E41BFC7FE5C64BE96481167B046@MTLEXVS01.ulticom.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Aug 2010 18:09:05.0599 (UTC) FILETIME=[7514DCF0:01CB3592]
Cc: Daily William <Bill.Daily@comverse.com>, dime@ietf.org
Subject: Re: [Dime] Private-Info AVP
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: Fri, 06 Aug 2010 18:08:40 -0000

Somewhere back in this correspondence the use of the Class AVP for this purpose 
was noted. I know that we used it to preserve state in the IETF Rs application, 
running in stateless mode. Does it not serve your needs too?

David Lehmann wrote:
> I was using the general term "agent" because it doesn't matter which
> type it is, from the RFC's point of view.  The Private-Info is just an
> extension of the Proxy-Info.  For the same reason that the Proxy-Info
> exists, the Private-Info AVP has the same desired purpose:  "It contains
> state information that would otherwise be stored at the Diameter entity
> that created it.  As such, this AVP MUST be treated as opaque data by
> entities other Diameter entities."  The RFC (section 6.1.9) states that
> the Proxy-Info can be use by a Proxy or Relay agent.  So it really does
> matter which type of agent uses the AVP nor does it matter for which
> purpose.  Who knows all of the clever ways an agent uses the Proxy-Info?
> The RFC does not provide the specific purposes of the Proxy-Info, and
> rightly so.  Nor does the RFC need to spell out the purposes of the
> Private-Info AVP.   It is simply a tool to aid agents.
> 
>  
> 
> --
> 
> David Lehmann
> 
> Ulticom, Inc.
> 
> 856-787-2952
> 
...