Re: [Netconf] FW: David Harrington's Discuss on draft-ietf-netconf-rfc4742bis-07: (withDISCUSS and COMMENT)

Phil Shafer <phil@juniper.net> Wed, 02 March 2011 16:37 UTC

Return-Path: <phil@juniper.net>
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 26A123A6831 for <netconf@core3.amsl.com>; Wed, 2 Mar 2011 08:37:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 8C0asPMYIVNU for <netconf@core3.amsl.com>; Wed, 2 Mar 2011 08:37:41 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by core3.amsl.com (Postfix) with ESMTP id 9DE433A681E for <netconf@ietf.org>; Wed, 2 Mar 2011 08:37:37 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKTW5ykqC441P7QQBCnMLiSLZ3X54tSVJn@postini.com; Wed, 02 Mar 2011 08:38:47 PST
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB01-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 2 Mar 2011 08:04:40 -0800
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id p22G5Pv26574; Wed, 2 Mar 2011 08:05:25 -0800 (PST) (envelope-from phil@juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.14.3/8.14.3) with ESMTP id p22Ff9ij039041; Wed, 2 Mar 2011 15:41:35 GMT (envelope-from phil@idle.juniper.net)
Message-ID: <201103021541.p22Ff9ij039041@idle.juniper.net>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
In-Reply-To: <20110302105101.GA14882@elstar.local>
Date: Wed, 02 Mar 2011 10:41:09 -0500
From: Phil Shafer <phil@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain
Cc: Andy Bierman <biermana@Brocade.com>, Netconf <netconf@ietf.org>
Subject: Re: [Netconf] FW: David Harrington's Discuss on draft-ietf-netconf-rfc4742bis-07: (withDISCUSS and COMMENT)
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: Wed, 02 Mar 2011 16:37:43 -0000

Juergen Schoenwaelder writes:
>Telling operators they
>can't use all user names say SSH allows is simply a broken idea.

Amen.  Making legitimate SSH user names illegal in NETCONF will
mean that vendors choose between allowing their customers to continue
to use odd user names and to enforce the NETCONF constraint at a
cost to their customers.  That's an easy choice.  So many initial
NETCONF implementations will enforce these constraints until customers
complain, at which time the constraints will simply be removed.

This will definitely not help interoperability, deployment, or
happiness.  And it helps teach people to ignore the constraints in
the RFC, where they really do not need any help.

Thanks,
 Phil