Re: [Netconf] We NEED RESPONSES: WG Last Call ended for:draft-ietf-netconf-4741bis-04.txt

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 06 October 2010 13:43 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 1F3C53A6F36 for <netconf@core3.amsl.com>; Wed, 6 Oct 2010 06:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.985
X-Spam-Level:
X-Spam-Status: No, score=-101.985 tagged_above=-999 required=5 tests=[AWL=0.264, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
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 XTBZ4yObhI-Q for <netconf@core3.amsl.com>; Wed, 6 Oct 2010 06:42:59 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id A2EB63A6E6D for <netconf@ietf.org>; Wed, 6 Oct 2010 06:42:59 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 4DB07C0043; Wed, 6 Oct 2010 15:43:59 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id x5wxrQmubgJ6; Wed, 6 Oct 2010 15:43:58 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8EA75C000A; Wed, 6 Oct 2010 15:43:58 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 8527D15153E0; Wed, 6 Oct 2010 15:43:29 +0200 (CEST)
Date: Wed, 06 Oct 2010 15:43:29 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Message-ID: <20101006134329.GA54263@elstar.local>
Mail-Followup-To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>, ext Martin Bjorklund <mbj@tail-f.com>, "netconf@ietf.org" <netconf@ietf.org>
References: <CB69B162C87647AE97AB749466633F54@BertLaptop> <4C9B3E60.5030000@bwijnen.net> <80A0822C5E9A4440A5117C2F4CD36A640106532D@DEMUEXC006.nsn-intra.net> <20101006.133730.41786057.mbj@tail-f.com> <80A0822C5E9A4440A5117C2F4CD36A64010A8B49@DEMUEXC006.nsn-intra.net> <20101006125110.GB53607@elstar.local> <80A0822C5E9A4440A5117C2F4CD36A64010A8C4B@DEMUEXC006.nsn-intra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A64010A8C4B@DEMUEXC006.nsn-intra.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "netconf@ietf.org" <netconf@ietf.org>
Subject: Re: [Netconf] We NEED RESPONSES: WG Last Call ended for:draft-ietf-netconf-4741bis-04.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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, 06 Oct 2010 13:43:01 -0000

On Wed, Oct 06, 2010 at 03:33:59PM +0200, Ersue, Mehmet (NSN - DE/Munich) wrote:
> > On Wed, Oct 06, 2010 at 02:24:23PM +0200, Ersue, Mehmet (NSN -
> > DE/Munich) wrote:
> > > > > Section 12.2. Informative References
> > > > >
> > > > > Add draft-ietf-netmod-yang-usage-11 as informative reference.
> > > >
> > > > Why?  That document is intended for YANG module writers.
> > >
> > > Appendix C includes a normative YANG module and IANA considerations
> > > include namespace registration, etc., which follow the guidelines
> > > in draft-ietf-netmod-yang-usage.
> > > I think people who read the YANG module in 4741bis should be also
> > > pointed to the guidelines document.
> > 
> > Why? The guidelines are for module writers / reviewers not module
> > readers. You want to have them cited in each and every module we
> > publish? We do not do this for MIB modules.
> 
> It is actually the same reason why we have the informative 
> reference on:
> 
> [13]  Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for the
>       Use of Extensible Markup Language (XML) within IETF Protocols",
>       BCP 70, RFC 3470, January 2003.

Since the document in question defines a protocol that carries XML,
having this reference may seem different from requiring a reference to
the YANG guidelines how to write a YANG proper module in every YANG
module. At least in the SMIv2 space, we managed to live without it.

But then, if you feel strongly about this, lets just add it instead of
debating this long.

Lets hope the guidelines document gives the guideline that the
guidelines document select-one-of(must|MUST|should|SHOULD) be
cited. ;-)

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>