RE: index object restrictions for ipv4/v6 in raqmon-pdu

Possibly also for index objects (in pdu document):

  raqmonPeerAddrType
  raqmonPeerAddr

you ought to do something like below indeed.
For the raqmonParticipantAddr occurence in the raqmonParticipantAddrTable
you are re-using an object defined in another table, so I would not
think that defining restriction here in this table makes sense, does it?
You define the restrictions in the original object (which is defined
read-only if I see it correctly). So see next para.

For raqmonParticipantAddrType and raqmonParticipantAddr
and for raqmonParticipantPeerAddrType and raqmonParticipantPeerAddr
(in raqmon-mib document), you can do normal OBJECT clauses, 
they are read-only objects, no?


Or am I mistaken here?

Bert
> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:[email protected]]
> Sent: Friday, March 11, 2005 00:58
> To: Wijnen, Bert (Bert)
> Cc: RMON WG (E-mail)
> Subject: RE: index object restrictions for ipv4/v6 in raqmon-pdu
> 
> 
> So, if I am to take the model that you are providing, we 
> should include in the DESCRIPTION clause of the compliance 
> the following:
> 
>                 There is one INDEX object that cannot be 
>                 represented in the form of OBJECT clause in SMIv2, 
>                 but for which there are compliance requirements, 
>                 expressed in OBJECT clause form in this description: 
>      
>                            
>                 -- OBJECT      raqmonParticipantAddr 
>                 -- SYNTAX      InetAddress (SIZE (4 | 8 | 16 | 20)) 
>                 -- DESCRIPTION 
>                 --     This MIB requires support for global and 
>                 --     non-global IPv4 and IPv6 addresses. 
> 
> Good time for anyone who has an objection to express it.
> 
> Thanks and Regards,
> 
> 
> Dan
> 
> 
> 
> > -----Original Message-----
> > From: Wijnen, Bert (Bert) [mailto:[email protected]]
> > Sent: 10 March, 2005 9:38 PM
> > To: Romascanu, Dan (Dan)
> > Cc: RMON WG (E-mail)
> > Subject: index object restrictions for ipv4/v6 in raqmon-pdu
> > 
> > 
> > draft-ietf-ipv6-rfc2096-update-07.txt is a doc that shows
> > how we did it for InetAddressType and InetAddress in that
> > document. I think it would make sense to do a simialr thing.
> > 
> > As discussed at IETF62
> > 
> > Bert
> > 
>