Re: [MIB-DOCTORS] draft-ietf-pwe3-pw-tc-mib-14.txt [was Preliminary agenda for the 8/14 IESG Telechat]

["Romascanu, Dan (Dan)" <[e-mail]>]

Bert,

Hmmmm ... I am not crazy about it, but it may be acceptable as there is
no exact equivalent in the Bridge or IEEE 802.1 MIB TCs or I did not
find it. Did you? The PWE3 folks use 4097 as a special value for 16bit
VLAN range. Sure, one may ask what 'object is not relevant means'. And
it certainly would be better to have all VLAN-related TCs in one place,
but ...

Dan
 

> -----Original Message-----
> From: Bert Wijnen [mailto:[e-mail]] 
> Sent: Saturday, August 09, 2008 12:52 AM
> To: Romascanu, Dan (Dan); MIB Doctors (E-mail)
> Subject: draft-ietf-pwe3-pw-tc-mib-14.txt [was [MIB-DOCTORS] 
> Preliminary agenda for the 8/14 IESG Telechat]
> 
> Dan, I only did a very very quick scan of  
> draft-ietf-pwe3-pw-tc-mib-14.txt
> 
> 
> ANd I found this:
> 
>   PwVlanCfg ::= TEXTUAL-CONVENTION
>      DISPLAY-HINT "d"
>      STATUS      current
>      DESCRIPTION
>           "VLAN configuration for Ethernet PW.
>            Values between 0 and 4095 indicate the actual VLAN field
>            value.
>            A value of 4096 indicates that the object refers to
>            untagged frames, i.e., frames without a 802.1Q field.
>            A value of 4097 indicates that the object is not
>            relevant."
>      SYNTAX  Unsigned32 (0..4097)
> 
> 
> I wonder how that co-exists/conflicts with the VLAN TCs that 
> we have in our BRIDGEMIB documents and those in the new 
> 802.1ap MIB modules????
> 
> Bert
> 
> ----- Original Message -----
> From: "Romascanu, Dan (Dan)" <[e-mail]>
> To: <[e-mail]>; "MIB Doctors (E-mail)" 
> <[e-mail]>; "IETF DNS Directorate" 
> <[e-mail]>; <[e-mail]>
> Sent: Friday, August 08, 2008 6:55 PM
> Subject: [MIB-DOCTORS] Preliminary agenda for the 8/14 IESG Telechat
> 
> 
> > Please find below the preliminary agenda of the 8/14 IESG telechat.
> > Please send me your questions, concerns and comments until 8/13 COB 
> > the latest.
> >
> > Thanks and Regards,
> >
> > Dan
> >
> > 2. Protocol Actions
> > Reviews should focus on these questions: "Is this document a 
> > reasonable basis on which to build the salient part of the Internet 
> > infrastructure? If not, what changes would make it so?"
> >
> > 2.1 WG Submissions
> > 2.1.1
> >
> > - Information Model and XML Data Model for Traceroute Measurements 
> > (Proposed Standard) - draft-ietf-ippm-storetraceroutes-10.txt
> > - Transport Mapping for Syslog (Proposed Standard) - 
> > draft-ietf-syslog-transport-tls-13.txt
> > - Definitions of Textual Conventions for Pseudowires (PW) 
> Management 
> > (Proposed Standard) - draft-ietf-pwe3-pw-tc-mib-14.txt
> > - Guidelines for Application Designers on Using Unicast UDP (BCP) - 
> > draft-ietf-tsvwg-udp-guidelines-09.txt
> > - Simple Network Management Protocol (SNMP) Context 
> EngineID Discovery 
> > (Proposed Standard) - 
> draft-ietf-opsawg-snmp-engineid-discovery-03.txt
> > - Internet Message Store Events (Proposed Standard) - 
> > draft-ietf-lemonade-msgevent-06.txt
> >
> > 2.1.2 Returning Item
> >
> > - A Two-way Active Measurement Protocol (TWAMP) (Proposed 
> Standard) - 
> > draft-ietf-ippm-twamp-09.txt
> >
> > 2.2 Individual Submissions
> > 2.2.1 New Item
> >
> > - IANA Considerations for the IPv4 and IPv6 Router Alert Option 
> > (Proposed Standard) - draft-manner-router-alert-iana-03.txt
> > - Extensions to the IODEF-Document Class for Reporting Phishing, 
> > Fraud, and Other Crimeware (Proposed Standard) - 
> > draft-cain-post-inch-phishingextns-05.txt
> >
> > 3. Document Actions
> >
> > 3.2 Individual Submissions Via AD
> > Reviews should focus on these questions: "Is this document a 
> > reasonable contribution to the area of Internet engineering 
> which it 
> > covers? If not, what changes would make it so?"
> >
> > 3.2.1 New Item
> >
> > - Basic Password Exchange within the Flexible Authentication via 
> > Secure Tunneling Extensible Authentication Protocol (EAP-FAST) 
> > (Informational)
> > - draft-zhou-emu-fast-gtc-04.txt
> > - Dynamic Provisioning using Flexible Authentication via Secure 
> > Tunneling Extensible Authentication Protocol (EAP-FAST) 
> > (Informational)
> > - draft-cam-winget-eap-fast-provisioning-09.txt
> > - Media Gateway Control Protocol Fax Package (Informational) - 
> > draft-andreasen-mgcp-fax-08.txt
> >
> > _______________________________________________
> > MIB-DOCTORS mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/mib-doctors
> >
> > 
> 
> 
> 
_______________________________________________
MIB-DOCTORS mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/mib-doctors