IETF Logo Mail Archive

[Netconf] namespace issue in the sample <hello> in RFC474 2 netconf over ssh

"Xiang Li" <xiangli@iwl.com> Mon, 05 October 2009 18:00 UTC

Return-Path: <xiangli@iwlcorp.com>
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 112B628C245 for <netconf@core3.amsl.com>; Mon, 5 Oct 2009 11:00:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[AWL=1.543, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sd9erGaO1UAD for <netconf@core3.amsl.com>; Mon, 5 Oct 2009 11:00:53 -0700 (PDT)
Received: from smtp184.iad.emailsrvr.com (smtp184.iad.emailsrvr.com [207.97.245.184]) by core3.amsl.com (Postfix) with ESMTP id D9C5228C1CD for <netconf@ietf.org>; Mon, 5 Oct 2009 11:00:52 -0700 (PDT)
Received: from relay8.relay.iad.mlsrvr.com (localhost [127.0.0.1]) by relay8.relay.iad.mlsrvr.com (SMTP Server) with ESMTP id E4684203D8E for <netconf@ietf.org>; Mon, 5 Oct 2009 14:02:27 -0400 (EDT)
Received: from dynamic5.wm-web.iad.mlsrvr.com (dynamic5.wm-web.iad.mlsrvr.com [192.168.2.146]) by relay8.relay.iad.mlsrvr.com (SMTP Server) with ESMTP id 95C85202E08 for <netconf@ietf.org>; Mon, 5 Oct 2009 14:02:27 -0400 (EDT)
Received: from iwlcorp.com (localhost [127.0.0.1]) by dynamic5.wm-web.iad.mlsrvr.com (Postfix) with ESMTP id 6F29F8D006E for <netconf@ietf.org>; Mon, 5 Oct 2009 14:02:27 -0400 (EDT)
Received: by apps.rackspace.com (Authenticated sender: xiangli@iwlcorp.com, from: xiangli@iwl.com) with HTTP; Mon, 5 Oct 2009 11:02:27 -0700 (PDT)
Date: Mon, 05 Oct 2009 11:02:27 -0700
From: Xiang Li <xiangli@iwl.com>
To: netconf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Importance: Normal
X-Priority: 3 (Normal)
X-Type: plain
Message-ID: <1254765747.450910030@192.168.1.70>
X-Mailer: webmail7.0
Subject: [Netconf] namespace issue in the sample <hello> in RFC474 2 netconf over ssh
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netconf>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2009 18:00:54 -0000

Hi
 
In RFC4271, the sample hello message shows the <hello> must be in the netconf namespace:

  <hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <capabilities>
        <capability>
          urn:ietf:params:netconf:base:1.0
        </capability>
  </hello>

But in RFC4272 Netconf over SSH, the sample hello does not use
the netconf namespace:

    C: <hello>
    C:   <capabilities>
    C:     <capability>
    C:       urn:ietf:params:xml:ns:netconf:base:1.0
    C:     </capability>
    C:   </capabilities>
    C: </hello>
    C: ]]>]]>


It appears to me this is a bug in RFC4742 since RFC4741 says:

3.1.  Namespace

   All NETCONF protocol elements are defined in the following namespace:

      urn:ietf:params:xml:ns:netconf:base:1.0


I actually saw an implementation's <hello> message using the format as
documented in RFC4742.


Thanks,
Xiang Li

v2.23.0 | Report a Bug | By Email