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

Russ White <russw@riw.us> Wed, 23 July 2014 20:47 UTC

Return-Path: <russw@riw.us>
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 217231A05C0 for <i2rs@ietfa.amsl.com>; Wed, 23 Jul 2014 13:47:56 -0700 (PDT)
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, RP_MATCHES_RCVD=-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 i88BiQfV8CZV for <i2rs@ietfa.amsl.com>; Wed, 23 Jul 2014 13:47:54 -0700 (PDT)
Received: from server.riw.us (server.riw.us [162.144.32.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 094461A038E for <i2rs@ietf.org>; Wed, 23 Jul 2014 13:47:53 -0700 (PDT)
Received: from dhcp-a5fc.meeting.ietf.org ([31.133.165.252]:61353) by server.riw.us with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <russw@riw.us>) id 1XA3S3-00025d-LB; Wed, 23 Jul 2014 20:47:51 +0000
References: <53CFF02D.5020209@cisco.com> <53CFF2DD.1060906@joelhalpern.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <53CFF2DD.1060906@joelhalpern.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <662111B0-E849-45EC-9493-9C04C0D434CB@riw.us>
X-Mailer: iPad Mail (11D257)
From: Russ White <russw@riw.us>
Date: Wed, 23 Jul 2014 16:47:52 -0400
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.riw.us
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
X-Get-Message-Sender-Via: server.riw.us: authenticated_id: russw@riw.us
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/dcLBDGmLGoiDri9Se1i0jToF3vE
Cc: "i2rs@ietf.org" <i2rs@ietf.org>, Joe Clarke <jclarke@cisco.com>
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 20:47:56 -0000

I would agree with this assessment -- support without the yang model. A more generic multiple model might be nice if we need the illustration... Yang should be in a separate draft.

 :-)

Russ

> On Jul 23, 2014, at 1:37 PM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:
> 
> 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
> 
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs