[BEHAVE] NAT MIB scope
Tom Taylor <tom.taylor.stds@gmail.com> Sun, 11 January 2015 21:43 UTC
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF8F91A1A86; Sun, 11 Jan 2015 13:43:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 JpS5j2qH8EMh; Sun, 11 Jan 2015 13:43:07 -0800 (PST)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 342211A0BE8; Sun, 11 Jan 2015 13:43:07 -0800 (PST)
Received: by mail-ie0-f171.google.com with SMTP id ar1so22703655iec.2; Sun, 11 Jan 2015 13:43:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=Q1N5OHbrTShtX+mE2uZyVoCyYUSt7Ub32Si8JLCEPFE=; b=EfExv3bjpSM907gAxrAWaUDefltrUdmxoJQ2kC4kkDeaJf8Blck5Ke9tbBlAEo4sWL lQgbvhItsXIx1ucH/perEeHxLqmS/+wpKlTD2DA1ymr8yXs9XJ1x7mBlFwlxkKl6/Vj9 C/TggX6mwNLCTi+Y0nXfM+u9r0F1UEHLDBmwggC6eLLDoqGAmaoC10evJkgoBnFOYph8 R90JRTOpaAFoNT+ky4OrYAqmT0eWw8Yf5Ydp6ua4I2u592hp2PfDUPG6t3TE+bqrcCXw feBzBhJWPXyHtdFZoPSxU7LFt5Gm1ckUFyYwUTyh0XqI5O7Pe8BFtT6Hz8IyjNXubX4c MFGA==
X-Received: by 10.50.36.103 with SMTP id p7mr12472278igj.20.1421012586349; Sun, 11 Jan 2015 13:43:06 -0800 (PST)
Received: from [192.168.0.101] (dsl-173-206-8-163.tor.primus.ca. [173.206.8.163]) by mx.google.com with ESMTPSA id qj3sm3128668igc.17.2015.01.11.13.43.05 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 11 Jan 2015 13:43:06 -0800 (PST)
Message-ID: <54B2EE69.7020807@gmail.com>
Date: Sun, 11 Jan 2015 16:43:05 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: "behave@ietf.org" <behave@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/behave/OvkM4bNFB7o85vks3DbiWw5U1oc>
Subject: [BEHAVE] NAT MIB scope
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave/>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jan 2015 21:43:09 -0000
Given present policies regarding the respective roles of SNMP and Yang, is it reasonable to say that the only configuration data that should be present in the NAT MIB is data directly relating to the control or interpretation of the remaining contents (i.e., the notifications, state information, and statistics)? I can see a Yang module for NAT configuration in my possible future. Tom Taylor
- [BEHAVE] NAT MIB scope Tom Taylor
- Re: [BEHAVE] NAT MIB scope Simon Perreault