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

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Wed, 06 October 2010 13:33 UTC

Return-Path: <mehmet.ersue@nsn.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 ADFB43A6F5B for <netconf@core3.amsl.com>; Wed, 6 Oct 2010 06:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.392
X-Spam-Level:
X-Spam-Status: No, score=-102.392 tagged_above=-999 required=5 tests=[AWL=0.207, BAYES_00=-2.599, 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 Babb2ldR3EdS for <netconf@core3.amsl.com>; Wed, 6 Oct 2010 06:33:02 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 769353A6F4B for <netconf@ietf.org>; Wed, 6 Oct 2010 06:33:02 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o96DY1HP012987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 6 Oct 2010 15:34:01 +0200
Received: from demuexc025.nsn-intra.net (demuexc025.nsn-intra.net [10.159.32.12]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o96DY02J007504; Wed, 6 Oct 2010 15:34:00 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc025.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 6 Oct 2010 15:34:00 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 06 Oct 2010 15:33:59 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A64010A8C4B@DEMUEXC006.nsn-intra.net>
In-Reply-To: <20101006125110.GB53607@elstar.local>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Netconf] We NEED RESPONSES: WG Last Call ended for:draft-ietf-netconf-4741bis-04.txt
Thread-Index: ActlVTvkzcBV1VwgRgCRAHsu7dZy2AABaqHw
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>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-OriginalArrivalTime: 06 Oct 2010 13:34:00.0515 (UTC) FILETIME=[227BA930:01CB655B]
Cc: 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
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:33:03 -0000

> 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.
 
> /js

me/>