"Da Silva, Pedro" wrote:
Multiple PDPs may manage a PEP but not concurrently. The PEP can only make
requests to one and only one PDP at a given time.
There is also the scenario where the PEP has a local PDP. In this case, you
may actually have two entities concurrently providing decisions to the PEP.
Note that the PEP must relay all local decisions to the remote PDP, as it is
*the authoritative source* of decisions (LPDPDecision).cheers,
Pedro-----Original Message-----
From: Abdul Malick [mailto:abdulmk@future.futsoft.com]
Sent: Thursday, November 22, 2001 4:00 AM
To: Da Silva, Pedro; IETF RAP WG
Subject: RE: PIB Incarnation [sic]Hello Pedro,
But can multiple PDPs manage a PEP at the same time?
Also to make a particular incarnation active, i think the PDP only has to
make the decision. In this case how is the activation of incarnations
co-ordinated among different PDPs given the fact that only one incarnation
can be active at the same time.Regards,
Malick-----Original Message-----
From: owner-rap@ops.ietf.org [mailto:owner-rap@ops.ietf.org]On Behalf Of
Da Silva, Pedro
Sent: Wednesday, 21 November 2001 8:15 PM
To: IETF RAP WG
Subject: RE: PIB Incarnation [sic]Krishna,
The frwkPibIncarnationName identifies the PDP that provided the PIB instance
refered to by the frwkPibIncarnationId. It can be say 'Primary Manager', or
'Manager X' and/or an ip address or whatever, in your system, *uniquely*
identifies each PDP.
It is the responsibility of the PDP to populate the entry, it's effectively
part of the decision.IHTH,
Pedro-----Original Message-----
From: Krishna Prasad Akkineni [mailto:krishna.akkineni@wipro.com]
Sent: Wednesday, November 21, 2001 10:29 AM
To: IETF RAP WG
Subject: PIB IncarnationHi,
This is a query with reference to ID on framework PIB.
>From the document, I could not understand how PDP & PEP
exchange PIB incarnation table details.Specifically, What can be the name of "frwkPibIncarnationName"
attribute. Is it the responsibility of PDP to fill this
attribute?For your reference, structure of FrwkPibIncarnationEntry
is given below.FrwkPibIncarnationEntry ::= SEQUENCE
frwkPibIncarnationPrid InstanceId,
frwkPibIncarnationName SnmpAdminString,
frwkPibIncarnationId OCTET STRING,
frwkPibIncarnationLongevity Unsigned32,
frwkPibIncarnationTtl Unsigned32,
frwkPibIncarnationActive TruthValue
}Thanks & Regards
Krishna
The Information contained and transmitted by this E-MAIL is proprietary to Wipro and/or its Customer and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail & notify us immediately at mailadmin@wipro.com