Re: [netmod] IETF91 NETMOD agenda ?

t.petch <ietfc@btconnect.com> Thu, 06 November 2014 10:35 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50EE51A1AD3 for <netmod@ietfa.amsl.com>; Thu, 6 Nov 2014 02:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dugsmJ8xy-Fn for <netmod@ietfa.amsl.com>; Thu, 6 Nov 2014 02:35:06 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0789.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::789]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 860A11A1AD0 for <netmod@ietf.org>; Thu, 6 Nov 2014 02:35:04 -0800 (PST)
Received: from AMSPR07MB052.eurprd07.prod.outlook.com (10.242.81.27) by AMSPR07MB130.eurprd07.prod.outlook.com (10.242.86.25) with Microsoft SMTP Server (TLS) id 15.1.6.9; Thu, 6 Nov 2014 10:34:41 +0000
Received: from pc6 (86.184.62.161) by AMSPR07MB052.eurprd07.prod.outlook.com (10.242.81.27) with Microsoft SMTP Server (TLS) id 15.1.16.15; Thu, 6 Nov 2014 10:34:40 +0000
Message-ID: <023801cff9ac$e6da6fc0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Andy Bierman <andy@yumaworks.com>, Benoit Claise <bclaise@cisco.com>
References: <A125E53CE190A749957C19483DC79F9F5C977E5A@US70TWXCHMBA11.zam.alcatel-lucent.com> <D8D374DB-32C6-4725-AD1B-D4E1B23BC966@lucidvision.com> <CABCOCHSoDxZfzA0dnviB2yV8GbdqmUrGmJXsFxMy8_7MpG7W+w@mail.gmail.com> <79054E89-2D09-4461-8D35-8F6FA025B71F@nic.cz> <43060BE7-53EA-4B9D-B778-2FED58C0D60C@lucidvision.com> <52AE09CB-D4AB-4421-BBA4-1D9C45EA6957@gmail.com> <54590195.3010903@cisco.com> <CAAchPMtcvd3xb9xCGEBHqTZg8G-Fg76z8T2Wi1QLHoS=W_fiag@mail.gmail.com> <54595361.5000907@cisco.com> <CABCOCHSqWWPDyTWXMj3+DUJ89GGCiHD6mhK3W7bJf-+VgS_cRA@mail.gmail.com> <545965FA.2050308@cisco.com> <CABCOCHTCtrsLYTDtWSDAyPScD-dxLC0GDuzYDtgidHok_cT7-g@mail.gmail.com>
Date: Thu, 06 Nov 2014 10:31:55 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.184.62.161]
X-ClientProxiedBy: DB4PR02CA0021.eurprd02.prod.outlook.com (10.242.174.149) To AMSPR07MB052.eurprd07.prod.outlook.com (10.242.81.27)
X-Microsoft-Antispam: UriScan:;UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB052;
X-Exchange-Antispam-Report-Test: UriScan:;
X-Forefront-PRVS: 0387D64A71
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(13464003)(24454002)(51704005)(189002)(377454003)(479174003)(14496001)(84392001)(87286001)(61296003)(102836001)(19580395003)(19580405001)(101416001)(92566001)(40100003)(116806002)(15975445006)(104166001)(42186005)(97736003)(81686999)(50986999)(76176999)(81816999)(50226001)(33646002)(4396001)(44736004)(93916002)(86362001)(92726001)(23676002)(93886004)(50466002)(46102003)(106356001)(95666004)(66066001)(105586002)(21056001)(62966003)(64706001)(62236002)(87976001)(89996001)(20776003)(47776003)(77156002)(44716002)(77096003)(88136002)(99396003)(122386002)(107046002)(31966008)(120916001)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR07MB052; H:pc6; FPR:; MLV:sfv; PTR:InfoNoRecords; A:0; MX:1; LANG:en;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB130;
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/netmod/9Zf0e_0Zmv7--X4exPwERO98fCQ
Cc: netmod@ietf.org, rtg-ads@tools.ietf.org
Subject: Re: [netmod] IETF91 NETMOD agenda ?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 10:35:08 -0000

----- Original Message -----
From: "Andy Bierman" <andy@yumaworks.com>
To: "Benoit Claise" <bclaise@cisco.com>
Cc: <netmod@ietf.org>; <rtg-ads@tools.ietf.org>
Sent: Wednesday, November 05, 2014 12:11 AM

> On Tue, Nov 4, 2014 at 3:49 PM, Benoit Claise <bclaise@cisco.com>
wrote:
> > On 05/11/2014 00:20, Andy Bierman wrote:

> >
> > That could be a lot of updates...
> > I believe we should focus on the YANG models that don't have an
existing WG.
> >
> > I would prefer to spend all the meeting time
> > trying to discuss open issues in chartered items.  I don't see why
> > the NETMOD WG needs to spend time on status reports for
> > any unchartered work.
> >
> > I don't agree that NETMOD WG should be the home of SYSLOG
> > or any other protocol specific data models. IMO all those type of
drafts
> > should try to find a home in a protocol WG with the right experts.
> >
> > Sure, NIMY (Not In My Yard) is the easy answer.
> > And where should we have syslog?
> > https://datatracker.ietf.org/wg/syslog/charter/ is concluded

OPSAWG

What else is an area WG for?

Tom Petch




>
> It is not NIMBY. The YANG experts are not all SYSLOG experts.
> Getting the right people in the room is important (you said that ;-)
> Making a few SYSLOG experts sit through 140 minutes of
> unrelated material may not be the best option for them either.
>
> It is unfortunate that the SYSLOG WG has decided the protocol
> is complete and no further work is needed.  I don't agree IETF
> process should be a good reason to choose NETMOD WG.
> This draft is already chartered and I am not trying to stop
> the SYSLOG work.  I don't want it to start a trend though.
>
>
> > Regards, Benoit
> >
> >
>
>
> Andy
>
> >
> > Andy