Re: [i2rs] Follow-up on draft-clarke-i2rs-traceability

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 23 July 2014 17:38 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7C211B29B5 for <i2rs@ietfa.amsl.com>; Wed, 23 Jul 2014 10:38:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_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 mGCPQ9UeqtiE for <i2rs@ietfa.amsl.com>; Wed, 23 Jul 2014 10:38:07 -0700 (PDT)
Received: from mailb1.tigertech.net (mailb1.tigertech.net [208.80.4.153]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 064C21B2846 for <i2rs@ietf.org>; Wed, 23 Jul 2014 10:37:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb1.tigertech.net (Postfix) with ESMTP id EA9D9D55612; Wed, 23 Jul 2014 10:37:38 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at mailb1.tigertech.net
Received: from dhcp-955b.meeting.ietf.org (dhcp-955b.meeting.ietf.org [31.133.149.91]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailb1.tigertech.net (Postfix) with ESMTPSA id 10608D5560F; Wed, 23 Jul 2014 10:37:37 -0700 (PDT)
Message-ID: <53CFF2DD.1060906@joelhalpern.com>
Date: Wed, 23 Jul 2014 13:37:33 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Joe Clarke <jclarke@cisco.com>, "i2rs@ietf.org" <i2rs@ietf.org>
References: <53CFF02D.5020209@cisco.com>
In-Reply-To: <53CFF02D.5020209@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/4rCN-PFVM_tmiq2sG1KBUjAY7Ms
Subject: Re: [i2rs] Follow-up on draft-clarke-i2rs-traceability
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jul 2014 17:38:09 -0000

I would like to see the draft adopted by the WG, without the YANG model.

Thank you,
Joel

On 7/23/14, 1:26 PM, Joe Clarke wrote:
> At the meeting yesterday, the chairs called out a few non-chartered
> drafts that had progressed and should have a final decision made as to
> their future.  One was our draft-clarke-i2rs-traceability.
>
> I would like to address the question the chairs raised on the draft and
> ask the WG if this can be adopted.  The question was, should this draft
> be standalone or part of the architecture doc.
>
> This draft originally began as comments to Alia on the arch draft.  Alia
> suggested that a draft outlining what should be logged for purposes of
> traceability should be created independent of the arch.  Since then, the
> arch has had some traceability language added, but the details spelled
> out in draft-clarke-i2rs-traceability take these "breadcrumbs" and
> expand on them specific to what would be required for those needing to
> do diagnostic operations, accounting, and auditing.  On top of that, the
> architecture draft is very well-baked right now, and would benefit from
> going through on its own.
>
> In that case, I feel that this draft-clarke-i2rs-traceability stands
> very much on its own and compliments the arch draft.
>
> Some of the feedback we've had on our latest rev (-02) was regarding the
> YANG model we added.  The comments have been that a YANG model really
> isn't needed here.  In fact, some of the general parts of this might fit
> in the new syslog model work happening in NETMOD.  We would not be
> opposed to taking out this module, and retaining the English text
> explaining the importance of logging in I2RS as well as what should be
> logged.
>
> Therefore, we (the authors) would ask the WG for two things:
>
> 1. Closure on the YANG module question.
> 2. Adoption of draft-clarke-i2rs-traceability as a WG item
>
> Thank you.
>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>