[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ANCP] ANCP MIB



Hi Dan,

Then I think the current MIB is fine because currently we have in the
MIB:

IMPORTS
       GsmpVersion, GsmpNameType, GsmpPartitionIdType
            FROM GSMP-MIB                              -- [RFC3295] 

So that is exactly what you mean what should be done?

Regards,
Stefaan



-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca at avaya.com] 
Sent: maandag 17 maart 2008 17:57
To: DE CNODDER Stefaan; Mark Townsley; ancp at ietf.org
Subject: RE: [ANCP] ANCP MIB

It is even simpler than I thought. You just need to IMPORT the three TCs
from the GSMP MIB (not the whole MIB, only the TCs). 

Disclaimer - I did not yet fully review the ANCP MIB so other things may
pop up at the time of the review. 

Dan


 

> -----Original Message-----
> From: DE CNODDER Stefaan
> [mailto:stefaan.de_cnodder at alcatel-lucent.be]
> Sent: Monday, March 17, 2008 6:47 PM
> To: Romascanu, Dan (Dan); Mark Townsley; ancp at ietf.org
> Subject: RE: [ANCP] ANCP MIB
> 
> 
> Hi Dan,
> 
> The ANCP MIB only uses some textual conventions defined in the GSMP 
> MIB.
> Only 3 TCs in the GSMP MIB are used in the ANCP MIB: 
> GsmpVersion, GsmpNameType, and GsmpPartitionIdType.  Nothing else from

> the GSMP MIB is used.
> 
> The current ANCP MIB is the ANCP MIB for Access Nodes (AN).  
> This MIB also defines 2 TCs in addition to the TCs in the GSMP MIB.
> 
> These TCs from the GSMP MIB can also be useful for other ANCP MIBs 
> like the ANCP MIB for Network Access Servers (NASs), which also needs 
> the 2 TCs defined for ANCP MIB for AN.
> 
> So would it therefore be better to make a separate MIB module with 
> only TCs to be imported by all ANCP MIBs, and also put the 3 TCs of 
> the GSMP MIB in this MIB module, or is it just fine to IMPORT the GSMP

> MIB as currently done?
> 
> Regards,
> Stefaan
> 
> 
> -----Original Message-----
> From: ancp-bounces at ietf.org [mailto:ancp-bounces at ietf.org] On Behalf 
> Of Romascanu, Dan (Dan)
> Sent: vrijdag 14 maart 2008 13:48
> To: Mark Townsley; ancp at ietf.org
> Subject: Re: [ANCP] ANCP MIB
> 
> Sure, using MODULE-COMPLIANCE clauses we can point to what groups or 
> objects in the GSMP MIB an ANCP device needs to support. Can somebody 
> send me a short mail pointing to what out of the current GSMP MIB is 
> considered useful and what not, and what is the new information that 
> needs to be modeled in the new ANCP MIB?
> 
> We can also arrange for a short call next week to chat about this, 
> talking this week face-to-face would have been better, but I need to 
> run to the train and plane immediately after the meeting.
> 
> Dan
> 
> 
> > -----Original Message-----
> > From: Mark Townsley [mailto:townsley at cisco.com]
> > Sent: Friday, March 14, 2008 2:42 PM
> > To: ancp at ietf.org; Romascanu, Dan (Dan)
> > Subject: ANCP MIB
> > 
> > 
> > I spoke with Dan this morning. He tells me that there is no need to 
> > import the entire GSMP MIB if ANCP doesn't need it.
> > There are ways to "pick and choose" what ANCP needs from
> GSMP for the
> > baseline to work.
> > So, I'd like to ask Dan to continue to advise us here on
> what the WG
> > needs to do.
> > 
> > Thanks,
> > 
> > - Mark
> > 
> _______________________________________________
> ANCP mailing list
> ANCP at ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
> 
_______________________________________________
ANCP mailing list
ANCP at ietf.org
https://www.ietf.org/mailman/listinfo/ancp