-- extracted from draft-ietf-pwe3-pw-mib-08.txt
-- at Wed Jun 28 06:06:35 2006

     IANA-PWE3-MIB DEFINITIONS ::= BEGIN 
      
     IMPORTS 
         MODULE-IDENTITY, transmission 
            FROM SNMPv2-SMI -- [RFC2578] 
      
         TEXTUAL-CONVENTION 
            FROM SNMPv2-TC; -- [RFC2579] 
      
     ianaPwe3MIB  MODULE-IDENTITY 
         LAST-UPDATED "200601110000Z" --  January 11, 2006 
         ORGANIZATION "IANA" 
         CONTACT-INFO 
              "Internet Assigned Numbers Authority 
              Internet Corporation for Assigned Names and Numbers 
              4676 Admiralty Way, Suite 330 
              Marina del Rey, CA 90292-6601 
                         Pseudo Wire (PW) Management         June 2006 
                            Information Base 


      
              Phone: +1 310 823 9358 
              EMail: iana@iana.org" 
         DESCRIPTION 
             "This MIB module defines the IANAPwTypeTC and 
             IANAPwPsnTypeTC textual conventions for use in PWE3 
             MIB modules. 
      
             Any additions or changes to the contents of this MIB 
             module require either publication of an RFC, Designated  
             Expert Review as defined in RFC 2434, Guidelines for  
             Writing an IANA Considerations Section in RFCs, and should  
             be based on the procedures defined in [RFC4446]. The  
             Designated Expert will be selected by the IESG Area  
             Director(s) of the internet Area." 
      
         REVISION     "200601110000Z" --  January 11, 2006  
         DESCRIPTION  "Original version, published as part of RFC 
                       XXXX." 
     -- RFC Editor: please fill the XXXX and remove this note. 
      
         ::= { transmission YYYY } 
     -- RFC Editor: please fill the YYYY based on the IANA allocation 
     -- and remove this note. 
      
     IANAPwTypeTC ::= TEXTUAL-CONVENTION  
        STATUS     current  
        DESCRIPTION  
           "Indicates the PW type (i.e. the carried service). " 
      SYNTAX   INTEGER {  
         other(0),  
         frameRelayDlci(1),  
         atmAal5SduVcc(2),  
         atmTransparent(3),  
         ethernetTagged(4),  
         ethernet(5),  
         hdlc(6),  
         ppp(7),  
         cem(8),  -- old format  
         atmCellNto1Vcc(9),  
         atmCellNto1Vpc(10),  
         ipLayer2Transport(11),  
         atmCell1to1Vcc(12),  
         atmCell1to1Vpc(13),  
         atmAal5PduVcc(14),  
         frameRelayPortMode(15),  
         cep(16),  
         e1Satop(17),  
         t1Satop(18),  
         e3Satop(19),  
         t3Satop(20),  
                         Pseudo Wire (PW) Management         June 2006 
                            Information Base 


         basicCesPsn(21),  
         basicTdmIp(22),  
         tdmCasCesPsn(23),  
         tdmCasTdmIp(24), 
         frDlci(25)  
          }        
      
     IANAPwPsnTypeTC ::= TEXTUAL-CONVENTION  
        STATUS      current  
        DESCRIPTION 
           "Identifies the PSN type which the PW will use over the  
            network." 
        SYNTAX   INTEGER {  
           mpls       (1),   
           l2tp       (2),  
           ip         (3),  
           mplsOverIp (4),   
           gre        (5),  
           other      (6)  
           } 
     END 

--  
--      Copyright (C) The Internet Society (2006).  This document is 
--      subject to the rights, licenses and restrictions contained in BCP 
--      78, and except as set forth therein, the authors retain all their 
--      rights. 
--           
--      This document and the information contained herein are provided on 
--      an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 
--      REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND 
--      THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 
--      EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 
--      THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 
--      ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 
--      PARTICULAR PURPOSE. 
--       
--  14 Intellectual Property Notice 
--       
--      The IETF takes no position regarding the validity or scope of any 
--      Intellectual Property Rights or other rights that might be claimed 
--      to pertain to the implementation or use of the technology 
--      described in this document or the extent to which any license 
--      under such rights might or might not be available; nor does it 
--      represent that it has made any independent effort to identify any 
--      such rights.  Information on the procedures with respect to 
--      rights in RFC documents can be found in BCP 78 and BCP 79.
--       
--      Copies of IPR disclosures made to the IETF Secretariat and any 
--      assurances of licenses to be made available, or the result of an 
--      attempt made to obtain a general license or permission for the use 
--      of such proprietary rights by implementers or users of this 
--      specification can be obtained from the IETF on-line IPR repository 
--      at http://www.ietf.org/ipr. 
--       
--      The IETF invites any interested party to bring to its attention 
--      any copyrights, patents or patent applications, or other 
--      proprietary rights that may cover technology that may be required 
--      to implement this standard.  Please address the information to the 
--      IETF at ietf-ipr@ietf.org.