Network Working Group                                       D. Romascanu
Internet-Draft                                               S. Mazumdar
Expires: January 11, 2006                                          Avaya
                                                             S. Adwankar
                                                                Motorola
                                                           July 10, 2005


                   Data Types for Netconf Data Models
                draft-romascanu-netconf-datatypes-00.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on January 11, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This memo defines initial set of reusable data types for NetConf
   data models.








Romascanu, et al.       Expires January 11, 2006                [Page 1]

Internet-Draft     Data Types for Netconf Data Models          July 2005


Table of Contents

   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.   NetConf Core Data Types  . . . . . . . . . . . . . . . . . .   4
   3.   Security Considerations  . . . . . . . . . . . . . . . . . .   8
   4.   IANA Considerations  . . . . . . . . . . . . . . . . . . . .   9
   5.   Acknowledgements . . . . . . . . . . . . . . . . . . . . . .  10
   6.   References . . . . . . . . . . . . . . . . . . . . . . . . .  10
        Authors' Addresses . . . . . . . . . . . . . . . . . . . . .  10
        Intellectual Property and Copyright Statements . . . . . . .  12









































Romascanu, et al.       Expires January 11, 2006                [Page 2]

Internet-Draft     Data Types for Netconf Data Models          July 2005


1.  Introduction

   NETCONF [NETCONF] configuraion protocol defines Extensible Markup
   Language [XML] based mechanisms to install, manipulate, and delete
   the configuration of network devices.  NetConf protocol can be
   conceptually partitioned into four layers:

                Layer                      Example
            +-------------+      +-----------------------------+
            |   Content   |      |     Configuration data      |
            +-------------+      +-----------------------------+
                   |                           |
            +-------------+      +-----------------------------+
            | Operations  |      | <get-config>, <edit-config> |
            +-------------+      +-----------------------------+
                   |                           |
            +-------------+      +-----------------------------+
            |     RPC     |      |    <rpc>, <rpc-reply>       |
            +-------------+      +-----------------------------+
                   |                           |
            +-------------+      +-----------------------------+
            | Application |      |   BEEP, SSH, SSL, console   |
            |   Protocol  |      |                             |
            +-------------+      +-----------------------------+

   Framework for Netconf Data Models [NETMOD] provides guidance for the
   creation of Netconf data model.  This document defines initial set of
   core data types that will be useful in defining NetConf content.

                                 Figure 1





















Romascanu, et al.       Expires January 11, 2006                [Page 3]

Internet-Draft     Data Types for Netconf Data Models          July 2005


2.  NetConf Core Data Types

   The Netconf architecture supports a clear separation between content
   and protocol.  There are major advantages to ensuring that every data
   model writer do not have to invent new data types.

   The following are initial set of reusable data types.



           <simpleType name="MD5">
                   <annotation>
                           <documentation>
                                   MD5 Message-Digest Algorithm
                             </documentation>
                   </annotation>
                   <restriction base="string">
                           <pattern value="[0-9a-zA-Z]{32}"/>
                   </restriction>
           </simpleType>
           <simpleType name="IPAddress">
                   <annotation>
                           <documentation>
                                   IP Address
                             </documentation>
                   </annotation>
                   <restriction base="string">
                           <maxLength value="39"/>
                   </restriction>
           </simpleType>
           <simpleType name="IPV4Address">
                   <annotation>
                           <documentation>
                                   IPV4 Address
                             </documentation>
                   </annotation>
                   <restriction base="dt:IPAddress">
                           <minLength value="7"/>
                           <maxLength value="15"/>
                           <pattern value=
                           "(([0-1]?[0-9]?[0-9]|2?[0-5]?[0-5])\.){2}
                  ([0-1]?[0-9]?[0-9]|2?[0-5]?[0-5])"/>
                   </restriction>
           </simpleType>
           <simpleType name="IPV6AddressFull">
                   <restriction base="dt:IPAddress">
                           <pattern value=
                   "(([0-9a-fA-F]{1,4}:){7})([0-9a-fA-F]{1,4})"/>



Romascanu, et al.       Expires January 11, 2006                [Page 4]

Internet-Draft     Data Types for Netconf Data Models          July 2005


                   </restriction>
           </simpleType>
           <simpleType name="IPV6AddressMixed">
                   <restriction base="dt:IPAddress">
                           <pattern value="(([0-9a-fA-F]{1,4}:){6})
               (([0-9a-fA-F]{1,4}:[0-9a-fA-F]{1,4})|
               ([0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}))"/>
                   </restriction>
           </simpleType>
           <simpleType name="IPV6AddressShortened">
                   <restriction base="dt:IPAddress">
                           <pattern value=
                   "(([0-9a-fA-F]{1,4}:)*|([0-9a-fA-F]{1,4}))*(::)
            (([0-9a-fA-F]{1,4}:)*|([0-9a-fA-F]{1,4}))*"/>
                   </restriction>
           </simpleType>
           <simpleType name="IPV6Address">
                   <annotation>
                           <documentation>
                                   IPV6 Address RFC 3513
                             </documentation>
                   </annotation>
                   <union memberTypes="dt:IPV6AddressFull
                                   dt:IPV6AddressMixed
                                   dt:IPV6AddressShortened"/>
           </simpleType>
           <simpleType name="DomainName">
                   <annotation>
                           <documentation>
                                   Domain Name RFC 1034
                             </documentation>
                   </annotation>
                   <restriction base="string">
                           <pattern value=
                           "([\p{L}\p{N}]*\.)*[\p{L}\p{N}]?"/>
                   </restriction>
           </simpleType>
           <simpleType name="EthernetAddress">
                   <annotation>
                           <documentation>
                                   Ethernet Address, IEEE 802.3
                             </documentation>
                   </annotation>
                   <restriction base="string">
                           <pattern value="[0-9a-fA-F]{12}"/>
                   </restriction>
           </simpleType>
           <simpleType name="PORT">



Romascanu, et al.       Expires January 11, 2006                [Page 5]

Internet-Draft     Data Types for Netconf Data Models          July 2005


                   <annotation>
                           <documentation>
                                   Port, RFC 793, RFC 768
                             </documentation>
                   </annotation>
                   <restriction base="unsignedInt">
                           <minInclusive value="1"/>
                           <maxInclusive value="65535"/>
                   </restriction>
           </simpleType>
           <simpleType name="AdminStatus">
                   <annotation>
                           <documentation>
                                   Admin Status
                             </documentation>
                   </annotation>
                   <restriction base="string">
                           <enumeration value="Up"/>
                           <enumeration value="Down"/>
                           <enumeration value="Testing"/>
                   </restriction>
           </simpleType>
           <simpleType name="OperStatus">
                   <annotation>
                           <documentation>
                                   Operational Status
                             </documentation>
                   </annotation>
                   <restriction base="string">
                           <enumeration value="Up"/>
                           <enumeration value="Down"/>
                           <enumeration value="Testing"/>
                           <enumeration value="Unknown"/>
                           <enumeration value="Dormant"/>
                           <enumeration value="NotPresent"/>
                           <enumeration value="LowerLayerDown"/>
                   </restriction>
           </simpleType>
           <simpleType name="E164CountryCode">
                   <annotation>
                           <documentation>
                                   ITU-T E.164 Country Code
                             </documentation>
                   </annotation>
                   <restriction base="string">
                           <pattern value="[0-9]{3}"/>
                   </restriction>
           </simpleType>



Romascanu, et al.       Expires January 11, 2006                [Page 6]

Internet-Draft     Data Types for Netconf Data Models          July 2005


           <simpleType name="E164SubscriberNumber">
                   <annotation>
                           <documentation>
                                   E.164 Subscriber Number
                             </documentation>
                   </annotation>
                   <restriction base="string">
                           <pattern value="[0-9]{15}"/>
                   </restriction>
           </simpleType>









































Romascanu, et al.       Expires January 11, 2006                [Page 7]

Internet-Draft     Data Types for Netconf Data Models          July 2005


3.  Security Considerations

   To be determined once specific aspects of this solution are better
   understood.















































Romascanu, et al.       Expires January 11, 2006                [Page 8]

Internet-Draft     Data Types for Netconf Data Models          July 2005


4.  IANA Considerations

   TBD.
















































Romascanu, et al.       Expires January 11, 2006                [Page 9]

Internet-Draft     Data Types for Netconf Data Models          July 2005


5.  Acknowledgements

   This document is a result of discussions at IETF 59 and 60, as well
   as on the mailing list by the following people: Sharon Chisholm,
   David Harrington, Ray Atarashi, Yoshifumi Atarashi, Bert Wijnen, Andy
   Bierman, Randy Presuhn, Chris Lonvick, Eliot Lear, Avri Doria,
   Juergen Schoenwaelder, Rob Ennes, Faye Ly, Andre Westerinen and
   Subrata Mazumdar.

6.  References

   [NETCONF]  Enns, R., "NETCONF Configuration Protocol",
              ID draft-ietf-netconf-prot-07, June 2005.

   [NETMOD]   Chisholm, S. and S. Adwankar, "Framework for Netconf Data
              Models", ID draft-chisholm-netconf-model-03, June 2005.

   [URI]      Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifiers (URI): Generic Syntax", RFC 2396,
              August 1998.

   [XML]      World Wide Web Consortium, "Extensible Markup Language
              (XML) 1.0", W3C XML, February 1998,
              <http://www.w3.org/TR/1998/REC-xml-19980210>.

   [refs.RFC2026]
              Bradner, S., "The Internet Standards Process -- Revision
              3", RFC 2026, BCP 9, October 1996.

   [refs.RFC2119]
              Bradner, s., "Key words for RFCs to Indicate Requirements
              Levels", RFC 2119, March 1997.

   [refs.RFC2223]
              Postel, J. and J. Reynolds, "Instructions to RFC Authors",
              RFC 2223, October 1997.















Romascanu, et al.       Expires January 11, 2006               [Page 10]

Internet-Draft     Data Types for Netconf Data Models          July 2005


Authors' Addresses

   Dan Romascanu
   Avaya
   Atidim Technology Park
   Building #3
   Tel Aviv,   61131
   Israel

   Email: dromasca@avaya.com


   Subrata Mazumdar
   Avaya


   Sandeep Adwankar
   Motorola
   1301 East Algonquin Road
   MS IL02-2240
   Schaumburg, IL  60196
   USA

   Email: sandeep.adwankar@motorola.com



























Romascanu, et al.       Expires January 11, 2006               [Page 11]

Internet-Draft     Data Types for Netconf Data Models          July 2005


Intellectual Property Statement

   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.

   The IETF has been notified of intellectual property rights claimed in
   regard to some or all of the specification contained in this
   document.  For more information consult the online list of claimed
   rights.


Disclaimer of Validity

   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.


Copyright Statement

   Copyright (C) The Internet Society (2005).  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.





Romascanu, et al.       Expires January 11, 2006               [Page 12]

Internet-Draft     Data Types for Netconf Data Models          July 2005


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.















































Romascanu, et al.       Expires January 11, 2006               [Page 13]