Re: [i2rs] WG Adoption call for draft-clarke-i2rs-traceability-03 from 11/24 to 12/9/14

Joe Clarke <jclarke@cisco.com> Tue, 06 January 2015 19:54 UTC

Return-Path: <jclarke@cisco.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 E3DC81A00FA for <i2rs@ietfa.amsl.com>; Tue, 6 Jan 2015 11:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level:
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_25=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 qEOc90fRns7m for <i2rs@ietfa.amsl.com>; Tue, 6 Jan 2015 11:54:03 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C2C41A033A for <i2rs@ietf.org>; Tue, 6 Jan 2015 11:54:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2539; q=dns/txt; s=iport; t=1420574043; x=1421783643; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Ff4G1g5mT/NxMAQ74fp/6W+IvNvIayb8TFq9XN5Yp3U=; b=WUfc//m/4pPqQw1e54RJXQtTt50v2yiu4E1U/Eregp6hSIGO3SxMQiax VzPo0aWFgymevtjnZju9SBuK5mvQomteEfPrMTRgq9DVAN8xKxbZu3BvS 5gWsv5S8tXTtNaCq7mXaVCLuxL7nKhTbhIJci3bTvcoppCKiQYWZ2DklR g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsEFAOk8rFStJA2J/2dsb2JhbABcgwZSWIMFwzUKhXMCgQ4WAQEBAQF9hAwBAQEDAQEBARoGDwEFNgsQCQIRBAEBAQICBQwSAwICDwIWHwkIBgEMAQUCAQEXiAkIDZFinGiTeAEBAQEBAQEBAQEBAQEBAQEBAQEBARMEgSGOVwcKgl6BQQEEiVWNSYENgmqCEyGHeIM5IoIygVogMYJDAQEB
X-IronPort-AV: E=Sophos;i="5.07,709,1413244800"; d="scan'208";a="384783392"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-7.cisco.com with ESMTP; 06 Jan 2015 19:54:02 +0000
Received: from [10.150.55.12] (dhcp-10-150-55-12.cisco.com [10.150.55.12]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t06Js2Nv016339; Tue, 6 Jan 2015 19:54:02 GMT
Message-ID: <54AC3D5A.60804@cisco.com>
Date: Tue, 06 Jan 2015 14:54:02 -0500
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Kwang-koog Lee <kwangkooglee@gmail.com>, ramki Krishnan <ramk@Brocade.com>
References: <003701d0086d$2984f060$7c8ed120$@ndzh.com> <cff289590344479d8b8e4d42574b0c89@HQ1WP-EXMB11.corp.brocade.com> <32EC0F7B-4B21-40CC-BE4D-094856893C36@gmail.com>
In-Reply-To: <32EC0F7B-4B21-40CC-BE4D-094856893C36@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/AVenBNuyIW6hfyCG2MWs2CE8bCc
Cc: Jeffrey Haas <jhaas@pfrc.org>, "i2rs@ietf.org" <i2rs@ietf.org>, Susan Hares <shares@ndzh.com>, Alia Atlas <akatlas@gmail.com>
Subject: Re: [i2rs] WG Adoption call for draft-clarke-i2rs-traceability-03 from 11/24 to 12/9/14
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: Tue, 06 Jan 2015 19:54:06 -0000

On 11/27/14 1:31 AM, Kwang-koog Lee wrote:
> Hi.
>
> I also read this document and the adoption of working group document is
> essential.
>
> Like us, many operators agree that SDN-based approach can reduce
> operational costs (the amount is depending on telco's infrastructures)
> and provide a base to build new business models on top of the
> software-based framework. But, SDN-based control technology is not still
> matured solution to control all functions of network elements, so the
> framework can be frequently changed for any updated functions and fixing
> bugs anytime. In such a case, operators may face with exceptional cases
> that they cannot know and recognize. If there’s no support of such
> traceability, many operators have difficulties for troubleshoot. So, the
> traceability which records logs in terms of SDN-based control
> transactions and retrieves some status of I2RS-based service models in
> network elements is essential.
>
> After the adoption of the working group document, I think the service
> model for the traceability itself is also needed (it includes some
> parameters for logs such as log policy, level, file size, and so on.)
> And, as the trace log field, service model name might be added.

Kwang-koog Lee, happy new year.  Thanks for your support and feedback. 
Is there a specific Service Model for traceability you had in mind?  Are 
you referring to the syslog YANG module?  I'm trying to make sure we 
account for all the feedback.  Thanks.

Joe

>
> Thanks.
> Kwang-koog Lee
>
>> 2014. 11. 27., 오전 7:11, ramki Krishnan <ramk@Brocade.com
>> <mailto:ramk@Brocade.com>> 작성:
>>
>> Support.
>> Thanks,
>> Ramki
>> *From:*i2rs [mailto:i2rs-bounces@ietf.org]*On Behalf Of*Susan Hares
>> *Sent:*Monday, November 24, 2014 9:03 PM
>> *To:*i2rs@ietf.org <mailto:i2rs@ietf.org>
>> *Cc:*'Jeffrey Haas'; 'Alia Atlas'
>> *Subject:*[i2rs] WG Adoption call for
>> draft-clarke-i2rs-traceability-03 from 11/24 to 12/9/14
>> This is to begin a 2 week adoption call for
>> draft-clarke-i2rs-traceability-03.  Please include in your comments an
>> indication of “support” or “no support.”
>> Thank you,
>> Sue Hares and Jeff Haas
>> _______________________________________________
>> i2rs mailing list
>> i2rs@ietf.org <mailto:i2rs@ietf.org>
>> https://www.ietf.org/mailman/listinfo/i2rs
>
>
>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>