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

"Susan Hares" <shares@ndzh.com> Thu, 24 July 2014 13:25 UTC

Return-Path: <shares@ndzh.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 6CE411A0317 for <i2rs@ietfa.amsl.com>; Thu, 24 Jul 2014 06:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no
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 6auBG8IKGReN for <i2rs@ietfa.amsl.com>; Thu, 24 Jul 2014 06:25:18 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id DF1141A0301 for <i2rs@ietf.org>; Thu, 24 Jul 2014 06:25:17 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=31.133.162.238;
From: Susan Hares <shares@ndzh.com>
To: "'Joel M. Halpern'" <jmh@joelhalpern.com>, 'Joe Clarke' <jclarke@cisco.com>, i2rs@ietf.org
References: <53CFF02D.5020209@cisco.com> <53CFF2DD.1060906@joelhalpern.com>
In-Reply-To: <53CFF2DD.1060906@joelhalpern.com>
Date: Thu, 24 Jul 2014 09:25:12 -0400
Message-ID: <00c601cfa742$b3237800$196a6800$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQKI9ki+uUWdo1MbI5zLF+z+NUAorQKYkUIGmifUFEA=
X-Authenticated-User: skh@ndzh.com
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/IRWZvQbh2krqLC4PkcsukkaGHkU
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: Thu, 24 Jul 2014 13:25:20 -0000

Joel:

Are proposing that Informational models are separate documents than data
models? 

Sue 

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Joel M. Halpern
Sent: Wednesday, July 23, 2014 1:38 PM
To: Joe Clarke; i2rs@ietf.org
Subject: Re: [i2rs] Follow-up on draft-clarke-i2rs-traceability

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