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

RE: VLAN ID in draft-ietf-ops-vlanid-tc-mib-00.txt




Bert,
   Thanks for the feedback.  I checked with our kernel folks and they will be changing our externals so that the only VLAN ID values that can be configured are 1-4094.  So we can use the VlanIdOrNone TC.  Do you have any idea when you might be posting a new version of this draft, or do you feel there is more discussion needed before a new version could be posted?  Thanks,

Kristine Adamson
IBM Communications Server for MVS: TCP/IP Development
Internet e-mail:adamson@us.ibm.com



Bert Wijnen wrote on 01/28/2004 09:20:49 AM:

> Kristine. but a VLAN ID of 4095 is NOT a valid VLAN  ID.

> So the  TCs I have done so far say that 4095 is a wildcard, not a  value
> you  can assign to a VLAN.
>  
> Anyway, I will soon post a new ID that I hope reflects the consensus of  the
> discussion over the last month or so
>  
>
> Thanks,

> Bert
> -----Original Message-----
> From: Kristine Adamson  [mailto:adamson@us.ibm.com]
> Sent: woensdag 28 januari 2004  15:08
> To: mibs, snmp
> Subject: Re: Please review and  comment: draft-ietf-ops-vlanid-tc-mib-00.tx t
>
> Bert,

>    Our  implmentation could also use a TC with a value range of Integer32 { 0 |  
> 1..4094 | 4095 }, as we allow the configuration of a vlan ID of 4095.  As  the TC's
> are defined now, we really can't use any of them.   Thanks,

>  
> Kristine
>
> Mark Ellison wrote on  12/31/2003 02:03:54 PM:

>
> > Hi Bert,

>
> > Thanks for your reply.

>
> > I think I'd call a TC with a value range of Integer32 { 0 |  1..4094 |

> > 4095 }  a VlanIdReference or  VlanIdAssociation.
>
> > This TC would be  useful when defining an object that refers to a vlan.

> > For example, a  table where each entry can be associated with none, one,
> > or any vlan.   One alternative, with the existing TCs, would be to use
> >  VlanIdOrAny, but have the agent return noSuchInstance when there is no
> >  association with a vlan. Another alternative, with the existing TCs,
> >  would be to use VlanIdOrNone, and not have use of the special any/4095
> >  value.
>
> >  Regards,

>
> >  Mark

>
> > Wijnen, Bert (Bert)  wrote:

>
> > >Sorry for late reaction...  but I am now again looking at

> > >this document and the discussion  that we had back in October.
> > >
> > >inline
> >  >
> > >
> > >>-----Original Message-----
> >  >>From: Mark Ellison [mailto:ellison@ieee.org]
> > >>Sent:  donderdag 2 oktober 2003 20:12
> > >>To: Wijnen, Bert (Bert)
> >  >>Cc: Mark Ellison; mibs@ops.ietf.org
> > >>Subject: Re:  Please review and comment:
> >  >>draft-ietf-ops-vlanid-tc-mib-00.txt
> > >>
> >  >>
> > >>Hi Bert,
> > >>
> > >>I'm  wondering if there could be any mib or pib definition requiring a
> >  >>range of ( 0 | 1..4094 | 4095 )  for possible values?
> >  >>
> > >>
> > >>
> > >Mark, I have not seen  anyone react to this as a option that they
> > >wanted, so for now I am  not going to include it.
> > >It can of course always be added later if  a need arises.
> > >
> > >By the way, what woyuld you call/name  that TC?
> > >
> > >Bert
> > >
> > >
> >  >>Regards,
> > >>
> > >>Mark
> >  >>
> > >>
> > >>
> > >>
> >  >>
> > >
> > >
> > >
>
> Kristine Adamson

> IBM Communications Server for MVS:  TCP/IP Development
> Internet  e-mail:adamson@us.ibm.com