view Side-By-Side changes

Network Working Group                                       M. Wasserman
Internet-Draft                                                     Nokia                                                ThingMagic
Expires: April 18, November 29, 2004                                    T. Goddard
                                                              Wind River
                                                        October 19, 2003
                                                                  IceSoft
                                                             May 31, 2004


     Using the NETCONF Configuration Protocol over Secure Shell (SSH)
                     draft-ietf-netconf-ssh-00.txt
                      draft-ietf-netconf-ssh-01.txt

Status of this Memo

    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.

    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.
    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 April 18, November 29, 2004.

Copyright Notice

    Copyright (C) The Internet Society (2003). (2004).  All Rights Reserved.

Abstract

    This document describes a simple method for invoking and running the
    NETCONF configuration protocol within a Secure Shell (SSH) session as
    an SSH subsystem.  Some features of the NETCONF protocol are not
   suited for use in a single shell session, and those limitations are
   described here.










Wasserman & Goddard    Expires April 18, November 29, 2004                [Page 1]

Internet-Draft              NETCONF over SSH                October 2003                    May 2004


Table of Contents

    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3

    2.  Starting NETCONF over SSH  . . . . . . . . . . . . . . . . . .  4
      2.1   Capabilities Exchange  . . . . . . . . . . . . . . . . . .  5

    3.  Using NETCONF over SSH . .  5
   2.2 Reversability of Connections . . . . . . . . . . . . . . . . .  6
   3.  Using .  7

    4.  Exiting the NETCONF over SSH Subsystem  . . . . . . . . . . . . . . . .  8

    5.  Running NETCONF from an SSH Shell  . . . . . . . . .  7
   4.  Sending . . . . .  9
      5.1   Starting a NETCONF Notifications over SSH Shell Session . . . . . . . . . . . . .  9
   5.
      5.2   Exiting the a NETCONF Subsystem Shell Session  . . . . . . . . . . . . .  9

    6.  Security Considerations  . . . 10
   6.  Running NETCONF from an SSH Shell . . . . . . . . . . . . . . 11
   6.1 Starting a NETCONF Shell Session . . 11

    7.  IANA Considerations  . . . . . . . . . . . . . 11
   6.2 Exiting a NETCONF Shell Session . . . . . . . . 12

    8.  Acknowledgements . . . . . . . 11
   7.  Security Considerations . . . . . . . . . . . . . . . . 13

    9.  References . . . 13
   8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
    9.1   Normative References . . . . . . . . . . . . . . . . . . . . . 15 14
    9.2   Informative References . . . . . . . . . . . . . . . . . . . . 16 14

        Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 16 14

        Intellectual Property and Copyright Statements . . . . . . . . 17 16























Wasserman & Goddard    Expires April 18, November 29, 2004                [Page 2]

Internet-Draft              NETCONF over SSH                October 2003                    May 2004


1.  Introduction

    The NETCONF protocol [1] [I-D.ietf-netconf-prot] is an XML-based protocol
    used to manage the configuration of networking equipment.  NETCONF is
    defined to be session-layer and transport independent, allowing
    mappings to be defined for multiple session-layer or transport
    protocols.  This document defines how XMLCONF can be used within a
    Secure Shell (SSH) session, using the SSH connection protocol [2]
    [I-D.ietf-secsh-connect] over the SSH transport protocol [3].

   NETCONF is defined as a multi-channel protocol, with separate
   communications channels for session management, protocol operations
   and notifications.  In this document, however, we have defined a
   mapping to run NETCONF over a single SSH session (a single SSH
   channel of type "session", see section 4 of [2]).
    [I-D.ietf-secsh-transport].  This mapping will allow NETCONF to be
    executed from the a secure shell session, session by a user or a simple script. Mapping NETCONF to a single SSH session does
   impose some limitations on the use of NETCONF over SSH.  In
   particular, the <rpc-progress> and <rpc-abort> elements are not
   supported, NETCONF capabilities must be exchanged over the same
   channel as the NETCONF RPC commands, and NETCONF notifications, if
   enabled, will also be transmitted over the same channel.

    Throughout this document, the terms "client" and "server" are used to
    refer to the two ends of the SSH transport connection.  The client
    actively opens the SSH connection, and the server passively listens
    for the incoming SSH connection.  The terms "manager" and "agent" are
    used to refer to the two ends of the NETCONF protocol session.  The
    manager issues NETCONF RPC commands, and the agent replies to those
    commands.  Depending upon
   negotiated capabilities, the manager may also receive  When NETCONF
   notifications is run over SSH, the client is always the
    manager, and the agent may send notifications. server is always the agent.































Wasserman & Goddard    Expires April 18, November 29, 2004                [Page 3]

Internet-Draft              NETCONF over SSH                October 2003                    May 2004


2.  Starting NETCONF over SSH

    To run NETCONF over SSH, the client will first establish an SSH
    transport connection using the SSH transport protocol, and the client
    and server will exchange keys for message integrity and encryption.
    The client will then invoke the "ssh-userauth" service to
    authenticate the user, as described in the SSH authentication
    protocol [4]. [I-D.ietf-secsh-userauth].  Once the user has been
    successfully authenticated, the client will invoke the
    "ssh-connection" service, also known as the SSH connection protocol.

    After the ssh-connection service is established, the client will open
    a channel of type "session", which will result in an SSH session.

    Once the SSH session has been established, the user (or script) will
    invoke NETCONF as an SSH subsystem called "netconf".  Running NETCONF
    as an SSH subsystem avoids the need for the script to recognize shell
    prompts or skip over extraneous information, such as a system
   message, message
    that is printed at shell start-up.

   To the user (or script), running

    In order to allow NETCONF as an SSH subsystem may look
   similar traffic to the following example.  Although this be easily identified and
    filtered by firewalls and other network devices, NETCONF servers MUST
    default to providing access to the "netconf" SSH subsystem only when
    the SSH session is established using the IANA-assigned TCP port
    <TBD>.  Servers SHOULD be configurable to allow access to the netconf
    SSH subsystem over other ports.

    To the user (or script), running NETCONF as an SSH subsystem may look
    similar to the following example.  Although this example shows the
    text transmitted by both sides, the server MUST NOT echo the commands
    that it receives back to the client.




















Wasserman & Goddard    Expires April 18, November 29, 2004                [Page 4]

Internet-Draft              NETCONF over SSH                October 2003                    May 2004


    <!-- The user (or script) invokes the SSH subsystem.  Depending upon
    the configuration of the client and server, the passphrase prompt
    may not be issued or may be replaced by a password prompt. -->

    [user@client]$ ssh -s server.example.org netconf
    Enter passphrase for key '/foo/.ssh/id_dsa':

    <!-- The NETCONF subsystem running on the server sends a complete
    XML document to the client. client/manager. -->

    <?xml version="1.0" encoding="UTF-8"?>
    <hello>
      <capabilities>
           <capability>http://ietf.org/xmlconf/1.0/base</capability>
           <capability>http://ietf.org/xmlconf/1.0/agent</capbability>
           <capability>http://ietf.org/xmlconf/1.0/base#lock</capability>
       <capability>urn:ietf:params:xml:ns:netconf:base:1.0</capability>
       <capability>urn:ietf:params:xml:ns:netconf:base:1.0#lock</capability>
      </capabilities>
    </hello>
    ]]>]]>

    <!-- The client client/manager sends a complete XML document to the server.
    server/agent. -->

    <?xml version="1.0" encoding="UTF-8"?>
    <hello>
      <capabilities>
           <capability>http://ietf.org/xmlconf/1.0/base</capability>
           <capability>http://ietf.org/xmlcong/1.0/manager</capability>
           <capability>http://ietf.org/xmlconf/1.0/base#lock</capability>
       <capability>urn:ietf:params:xml:ns:netconf:base:1.0</capability>
      </capabilities>
    </hello>
    ]]>]]>

    While the NETCONF subsystem is active, the NETCONF manager can
    interact with the NETCONF agent by sending complete XML documents
    containing NETCONF RPC elements, and the NETCONF server agent will respond
    by sending complete XML documents containing appropriate RPC replies.

2.1  Capabilities Exchange

    As indicated in the example above, the server MUST indicate its
    capabilities by sending an XML document containing a <hello> element
    as soon as the NETCONF session is established.  The user (or the
    user's expect script) can parse this message to determine which
    NETCONF capabilities are supported by the server.

    The client must also send an XML document containing a <hello>
    element to indicate the client's capabilities to the server.  The
    document containing the <hello> element must be the first XML
    document that the client sends after the NETCONF session is
    established.



Wasserman & Goddard    Expires April 18, November 29, 2004                [Page 5]

Internet-Draft              NETCONF over SSH                October 2003


   established.                    May 2004


    Although the example shows the server sending a $lt;hello> message
    followed by the client's message, both sides will send the message as
    soon as the NETCONF subsystem is initialized, perhaps simultaneously.

2.2 Reversability of Connections

   The NETCONF protocol is reversible -- either the manager or the agent
   may initiate the session-layer or transport connection. Once the
   session is established, the NETCONF capabilities exchange will be
   used to indicate which side of the connection is the agent and which
   is the manager, as indicated in the previous example.  If there is no
   agreement, each side MUST close the transport connection and log an
   error.

   In order to provide for reversability when used over SSH, it may be
   necessary for either the NETCONF agent or the NETCONF manager to have
   a well known host key, as it is always required for the SSH server to
   have a well known host key.  Thus, the server will authenticate
   itself to the client with its host key. The client will then
   authenticate itself with any allowable mechanism, as specified in
   [4].  The authenticated principle is then passed to NETCONF.

   Because the use of NETCONF may involve transferring sensitive
   configuration information in either direction, both the client and
   server must be authenticated and all of the data exchanged must be
   encrypted.  If either the client or server fails to successfully
   authenticate itself, or if it is not possible to establish an
   encrypted session, the NETCONF session MUST be aborted.
















































Wasserman & Goddard    Expires April 18, November 29, 2004                [Page 6]

Internet-Draft              NETCONF over SSH                October 2003                    May 2004


3.  Using NETCONF over SSH

    A NETCONF over SSH session consists of the manager and agent
    exchanging complete XML documents.  Once the session has been
    established and capabilities have been exchanged, the manager will
    send complete XML documents to the server containing <rpc> elements,
   and the agent will respond with complete XML documents containing
   <rpc-reply> elements.

   To continue the example given above, an XMLCONF over SSH session to
   retrieve a set of configuration information might look like this:


   <!-- The manager sends an XML document containing an <rpc>
   element. -->

   <?xml version="1.0" encoding="UTF-8"?>
   <rpc id="101" xmlns="http://ietf.org/netconf/1.0/base">
       <get-config>
           <source> <running/> </source>
           <config xmlns="http://example.com/schema/1.2/config">
               <users/>
           </config>
           <format>xml</format>
       </get-config>
   </rpc>

   <!-- The agent responds with an XML document containing an
   <rpc-reply> element. -->

   <?xml version="1.0" encoding="UTF-8"?>
   <rpc-reply id="101" xmlns="http://ietf.org/netconf/1.0/base">
       <config xmlns="http://example.com/schema/1.2/config">
           <users>
               <user><name>root</name><type>superuser</type></user>
               <user><name>fred</name><type>admin</type></user>
               <user><name>barney</name><type>admin</type></user>
           </users>
       </config>
   </rpc-reply>


   There are two NETCONF protocol operations that are not supported when
   running NETCONF over SSH, the <rpc-progress> and <rpc-abort>
   operations.  These operations use the NETCONF management channel to
   allow the processing of out-of-band operations that affect RPC
   processing on the operations channel.  Since this document defines a
   single-channel mechanism for using NETCONF over SSH, these operations



Wasserman & Goddard      Expires April 18, 2004                 [Page 7]

Internet-Draft              NETCONF over SSH                October 2003


   cannot be supported in this transport mapping.

   In this mapping, there is no way to obtain a progress indication
   regarding an outstanding RPC request, and the only way to abort an
   RPC request before it completes is to terminate the SSH session.














































Wasserman & Goddard      Expires April 18, 2004                 [Page 8]

Internet-Draft              NETCONF over SSH                October 2003


4. Sending NETCONF Notifications over SSH

   The SSH protocol has the capability to support multiple sessions, and
   therefore, theoretically to support multiple NETCONF channels.
   However, because the NETCONF over SSH mapping is designed for
   simplified scripting, use of this mapping for such multiple purposes
   is not supported.

   Instead, if both the manager and agent indicate support for the
   notification capability and the manager issues a <notification-open>
   RPC command, notifications may be sent over the SSH session,
   interleaved with NETCONF RPC commands and responses. Notifications
   are transmitted and received as described in RFC 3195 [5], with the
   exception that authentication information is passed from the SSH
   layer instead of server containing <rpc> elements,
    and the BEEP layer.

   Once agent will respond with complete XML documents containing
    <rpc-reply> elements.

    As the client or previous example illustrates, a special character sequence,
    ]]>]]>, is sent after each XML document in the server begins sending NETCONF exchange.
    This character sequence cannot legally appear in an XML document, so
    it must
   suspend all other output (i.e. other XML documents) until can be unambigiously used to indentify the end of the current
    document has been sent in its entirety. This means that asynchronous
   notifications may be delayed while waiting for the transmission event of
   other documents to be completed. It is recommended that if an agent
   has at least one notification pending and at least one response
   pending that XML syntax or parsing error, allowing
    resynchronization of the notification(s) be sent first. If a manager deems
   that notifications are particularly time-sensitive, it may open
   another NETCONF exchange.

    To continue the example given above, an XMLCONF over SSH session that is used only for notifications.

   It is acceptable for a NETCONF manager to be sending a command to the
   agent, while the agent is simultaneously sending
    retrieve a response or
   notification to the manager.

   Once the set of configuration information might look like this:


    <!-- The manager has requested that the agent send notifications, via
   a <notification-open> RPC message, the sends an XML document containing an <rpc>
    element. -->

    <?xml version="1.0" encoding="UTF-8"?>
    <rpc message-id="105" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <get-config>
        <source><running/></source>
        <config xmlns="http://example.com/schema/1.2/config">
          <users/>
        </config>
      </get-config>
    </rpc>
    ]]>]]>

    <!-- The agent may send notification
   until the SSH session is closed. responds with an XML document containing an
    <rpc-reply> element. -->

    <?xml version="1.0" encoding="UTF-8"?>
    <rpc-reply message-id="105" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <config xmlns="http://example.com/schema/1.2/config">
            <users>
                <user><name>root</name><type>superuser</type></user>
                <user><name>fred</name><type>admin</type></user>
                <user><name>barney</name><type>admin</type></user>
            </users>
        </config>
    </rpc-reply>
    ]]>]]>



Wasserman & Goddard    Expires April 18, November 29, 2004                [Page 9] 7]

Internet-Draft              NETCONF over SSH                October 2003


5.                    May 2004


4.  Exiting the NETCONF Subsystem

    Exiting NETCONF is accomplished using the <kill-session> operation.
    When a <kill-session> command is issued by the manager, the agent
    shall respond, terminate the SSH session, and close the TCP
    connection.

    To continue the example used in previous sections, an existing
    NETCONF subsystem session could be closed as follows:


    <!-- The manager sends an XML document containing a <kill-session>
    operation. Question: Where do we get the session-id? Should it be
    sent in the <hello> message? --> Issue: The base specification forbids
    the use of kill-session to kill the current session.-->

    <?xml version="1.0" encoding="UTF-8"?>
    <rpc message-id="102" xmlns="http://ietf.org/xmlconf/1.0/base"> message-id="106" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
         <kill-session>
             <session-id>0</session-id>
         </kill-session>
    </rpc>
    ]]>]]>

    <!-- The agent returns an "OK" reply. -->

    <?xml version="1.0" encoding="UTF-8"?>
    <rpc-reply id="102" xmlns="http://ietf.org/netconf/1.0/base"> id="106" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
        <ok/>
    </rpc-reply>

    <!-- The NETCONF subsystem exits, ending the SSH session and returning
    the user (or script) to the local shell prompt. -->

    [user@client]$
    ]]>]]>















Wasserman & Goddard    Expires April 18, November 29, 2004                [Page 10] 8]

Internet-Draft              NETCONF over SSH                October 2003


6.                    May 2004


5.  Running NETCONF from an SSH Shell

    The techniques described in this document could be used to access the
    NETCONF protocol over the SSH shell session, or from other shell
    types such as a console session or a Telnet [7] [RFC0854] connection.
    However, there are serious security implications associated with
    allowing NETCONF access via any method that does not provide strong
    support for user authentication, server authentication and data
    privacy.  See the Security Considerations section for more details.

    If the server supports NETCONF invocation from an SSH shell session,
    the user may choose to invoke a NETCONF program from the shell
    command line.  This would involve using SSH to establish a shell
    session, and entering the name of a NETCONF program (with the full
    path, if necessary) at the remote shell prompt.

6.1

5.1  Starting a NETCONF Shell Session

    To the user, the establishment of an SSH shell and the invocation of
    the NETCONF program may look similar to the following example:


    <!-- The user enters an SSH shell session. -->

    [user@client]$ ssh server.example.org
    user@server.example.org's password: ********

    <!-- At the shell prompt, the user invokes the NETCONF program, which
    in this example is called 'netconf', but which might have different
    names on different systems. -->

    [user@server]$ netconf

    <!-- The NETCONF program sends an XML document to the client. -->

    <?xml version="1.0" encoding="UTF-8"?>
    <hello>
        <capabilities>
            <capability>http://ietf.org/xmlconf/1.0/base</capability>
            <capability>http://ietf.org/xmlconf/1.0/base#lock</capability>
        </capabilities>
    </hello>



6.2
    ]]>]]>


5.2  Exiting a NETCONF Shell Session

    When the user has run NETCONF from a shell, he will need to exit the



Wasserman & Goddard    Expires April 18, November 29, 2004                [Page 11] 9]

Internet-Draft              NETCONF over SSH                October 2003                    May 2004


    NETCONF program using the <kill-session> operation, and then exit the
    remote shell to return to the local shell.  To continue the example
    used in previous sections, an existing NETCONF shell session could be
    closed as follows:


    <!-- The manager sends an XML document containing an <kill-session>
    operation Question: Where do we get the session-id?  Should it be
    sent in the <hello> message? -->

    <?xml version="1.0" encoding="UTF-8"?>
    <rpc message-id="102" xmlns="http://ietf.org/xmlconf/1.0/base">
         <kill-session>
             <session-id>0</session-id>
         </kill-session>
    </rpc>
    ]]>]]>

    <!-- The agent returns an "OK" reply. -->

    <?xml version="1.0" encoding="UTF-8"?>
    <rpc-reply id="102" xmlns="http://ietf.org/netconf/1.0/base">
        <ok/>
    </rpc-reply>
    ]]>]]>

    <!-- The NETCONF program exits, returning the user to the SSH prompt.
    The user then types 'exit' to exit the SSH shell and return to the
    local shell. -->

    [user@server]$ exit
    [user@client]$



















Wasserman & Goddard    Expires April 18, November 29, 2004               [Page 12] 10]

Internet-Draft              NETCONF over SSH                October 2003


7.                    May 2004


6.  Security Considerations

    NETCONF is used to access and modify configuration and state
    information, so the ability to access this protocol should be limited
    to users and systems that are authorized to view or modify the
    agent's configuration and state data.

    The identity of the server MUST be verified and authenticated by the
    client before password-based authentication data or any configuration
    data is sent to it. the server.  The identity of the client MUST also be
    verified and authenticated by the server to ensure that ensure that the incoming
    client request is legitimate before any configuration or state data
    is sent to the incoming client
   request is legitimate. client.  Neither side should establish a NETCONF over
    SSH connection with an unknown, unexpected or incorrect identity on
    the opposite side.

    Configuration data may include sensitive information, such as
    usernames or security keys.  So, NETCONF should only be used over
    communications channels that provide strong encryption for data
    privacy.  This document defines a NETCONF over SSH mapping which
    provides for support of strong encryption and authentication.

    If the NETCONF server provides remote shell access through insecure
    protocols, such as Telnet, care should be taken to prevent execution
    of the NETCONF program when strong user authentication or data
    privacy is not available.  Because it may be difficult or impossible, impossible
    in some operating environments, environments to determine whether a shell command
    was accessed over a secure protocol, protocol such as SSH, SSH or an insecure
   protocol,
    protocol such as Telnet, it may be necessary to disable insecure
    shell access to the system to prevent insecure access to a the NETCONF
    program.  Alternatively, it would be possible to disable NETCONF
    access from the command line, only allowing NETCONF to be accessed
    through invocation of the SSH 'netconf' "netconf" subsystem.

   Because NETCONF data is being sent over

    This document requires that servers default to allowing access to the standard
    "netconf" SSH protocol
   port mapping (to the NETCONF subsystem or shell), use of only when using a specific TCP port assigned
    by IANA for this
   protocol mapping would purpose.  This will allow NETCONF data over SSH traffic
    to be transferred easily identified and filtered by firewalls and other network
    nodes.  However, it will also allow NETCONF over a
   firewall boundary SSH traffic to be
    more easily identified by attackers.

    This document also recommends that has open servers be configurable to allow
    access for to the "netconf" SSH connections.  Network
   policies which restrict NETCONF operations subsystem over other ports.  Use of that
    configuration option without corresponding changes to within a trusted firewall or
    network device configuration may clash with unintentionally result in the
    ability for nodes outside of the firewall or other policies that allows network-external
   SSH administrative
    boundary to gain access to internal ssh services. "netconf" SSH subsystem.




Wasserman & Goddard    Expires April 18, November 29, 2004               [Page 13] 11]

Internet-Draft              NETCONF over SSH                October 2003                    May 2004


7.  IANA Considerations

    IANA is requested to assign a TCP port number which will be the
    default port for NETCONF over SSH sessions as defined in this
    document.














































Wasserman & Goddard    Expires November 29, 2004               [Page 12]

Internet-Draft              NETCONF over SSH                    May 2004


8.  Acknowledgements

    This document was written using the xml2rfc tool described in RFC
    2629 [8]. [RFC2629].

    Extensive input was received from the members of the NETCONF design
    team, including: Andy Bierman, Weijing Chen, Rob Enns, Wes Hardaker,
    David Harrington, Eliot Lear, Simon Leinen, Phil Shafer, Juergen
    Shoenwaelder and Steve Waldbusser.  The following people have also
    reviewed this document and provided helpful valuable input: Bill Sommerfeld.









































Wasserman & Goddard    Expires April 18, November 29, 2004               [Page 14] 13]

Internet-Draft              NETCONF over SSH                October 2003                    May 2004


9.  References

9.1  Normative References

   [1]

    [I-D.ietf-netconf-prot]
               Enns, R., "NETCONF Configuration Protocol",
        draft-ietf-netconf-prot-00
               draft-ietf-netconf-prot-02 (work in progress), August 2003.

   [2] February
               2004.

    [I-D.ietf-secsh-connect]
               Ylonen, T., Kivinen, T., Rinne, T. and S. Lehtinen, "SSH
               Connection Protocol", draft-ietf-secsh-connect-17 draft-ietf-secsh-connect-18 (work in
               progress), July October 2003.

   [3]

    [I-D.ietf-secsh-transport]
               Ylonen, T., Kivinen, T., Saarinen, M., Rinne, T. and S.
               Lehtinen, "SSH Transport Layer Protocol",
        draft-ietf-secsh-transport-16
               draft-ietf-secsh-transport-17 (work in progress), July October
               2003.

   [4]

    [I-D.ietf-secsh-userauth]
               Ylonen, T., Kivinen, T., Saarinen, M., Rinne, T. and S.
        Lehtinen, C. Lonvick, "SSH Authentication Protocol",
        draft-ietf-secsh-userauth-17
               draft-ietf-secsh-userauth-20 (work in progress), July 2003.

   [5]  New, D. and M. Rose, "Reliable Delivery for syslog", RFC 3195,
        November 2001.
































Wasserman & Goddard      Expires April 18, 2004                [Page 15]

Internet-Draft              NETCONF over SSH                October 2003 May 2004.

9.2  Informative References

   [6]

    [RFC0854]  Postel, J. and J. Reynolds, "Telnet Protocol
               Specification", STD 8, RFC 854, May 1983.

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

   [7]  Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD
        8, RFC 854, May 1983.

   [8]

    [RFC2629]  Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
               June 1999.


Authors' Addresses

    Margaret Wasserman
   Nokia
   5 Wayside Road
   Burlington,
    ThingMagic
    One Broadway, 14th Floor
    Cambridge, MA  01803  02142
    USA

    Phone: +1 781 993 3858 617 758-4177
    EMail: margaret.wasserman@nokia.com margaret@thingmagic.com
    URI:   http://www.nokia.com   http://www.thingmagic.com




Wasserman & Goddard    Expires November 29, 2004               [Page 14]

Internet-Draft              NETCONF over SSH                    May 2004


    Ted Goddard
   Wind River
   #180, 6815-8th St. N.E.
   Calgary, AB  T2E 7H7
   Canada

   Phone: +1 403 730 7590
    IceSoft

    EMail: ted.goddard@windriver.com ted@icesoft.com















































Wasserman & Goddard    Expires April 18, November 29, 2004               [Page 16] 15]

Internet-Draft              NETCONF over SSH                October 2003                    May 2004


Intellectual Property Statement

    The IETF takes no position regarding the validity or scope of any
    intellectual property 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; neither does it represent that it
    has made any effort to identify any such rights.  Information on the
    IETF's procedures with respect to rights in standards-track and
    standards-related documentation can be found in BCP-11.  Copies of
    claims of rights made available for publication 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 implementors or users of this specification can
    be obtained from the IETF Secretariat.

    The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights which may cover technology that may be required to practice
    this standard.  Please address the information to the IETF Executive
    Director.


Full Copyright Statement

    Copyright (C) The Internet Society (2003). (2004).  All Rights Reserved.

    This document and translations of it may be copied and furnished to
    others, and derivative works that comment on or otherwise explain it
    or assist in its implementation may be prepared, copied, published
    and distributed, in whole or in part, without restriction of any
    kind, provided that the above copyright notice and this paragraph are
    included on all such copies and derivative works.  However, this
    document itself may not be modified in any way, such as by removing
    the copyright notice or references to the Internet Society or other
    Internet organizations, except as needed for the purpose of
    developing Internet standards in which case the procedures for
    copyrights defined in the Internet Standards process must be
    followed, or as required to translate it into languages other than
    English.

    The limited permissions granted above are perpetual and will not be
    revoked by the Internet Society or its successors or assignees.

    This document and the information contained herein is provided on an
    "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION



Wasserman & Goddard    Expires April 18, November 29, 2004               [Page 17] 16]

Internet-Draft              NETCONF over SSH                October 2003                    May 2004


    HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
    MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Acknowledgment

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











































Wasserman & Goddard    Expires April 18, November 29, 2004               [Page 18] 17]


----