From nobody Sun Jan 11 13:43:09 2015 Return-Path: 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 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" , "opsawg@ietf.org" Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 From nobody Mon Jan 12 05:48:57 2015 Return-Path: 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 234041A90EB for ; Mon, 12 Jan 2015 05:48:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable 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 GX3WS4A3Aldt for ; Mon, 12 Jan 2015 05:48:47 -0800 (PST) Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 868921A90E3 for ; Mon, 12 Jan 2015 05:48:47 -0800 (PST) Received: by mail-la0-f44.google.com with SMTP id gd6so24164089lab.3 for ; Mon, 12 Jan 2015 05:48:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=NwjcPZTIX/9z32n4Pv0hXlFfe+XWVSvedfQ6Mgk2LWc=; b=S6lTQ9hh7mgEdcu2PRGP40xy76oDnPkHp5paBoDlBtJ9Q0y9XKgA/E624lxLIPZ9aa 2SV+NYD6idGhjxOf6UWecSKdoMjekEe3q8aKgUYUiXtzydkEZaVm/y6rghJnjXzY27Ha +6AoP6tAlkGKxaXFAc2XhZuwpQlPXSs9QiumZyGiSGjS97Zv+gtnExJbGDvWIO0+icDu J98xeyvU99jC2anw3uxgUW2HxI4Yf9jQl2VuzxSh+JuLcEDkOdDZC9kvjiDi+cVhQUdf 0uKck4gUBv3gUV8MRMJOmpCIitHjbKTB9S3oO5DKxUhyO4ja7N9JoshzBIaQS6Z/1MrY X9eQ== X-Gm-Message-State: ALoCoQktBzbkm2GcGF26WKxPFQmxwiJH4GNaXEW04BLrfY5gUij2faBWzanjFvVi/9ZcD3fLIDdH MIME-Version: 1.0 X-Received: by 10.152.19.7 with SMTP id a7mr36298616lae.16.1421070526043; Mon, 12 Jan 2015 05:48:46 -0800 (PST) Received: by 10.25.84.145 with HTTP; Mon, 12 Jan 2015 05:48:46 -0800 (PST) In-Reply-To: <54B2EE69.7020807@gmail.com> References: <54B2EE69.7020807@gmail.com> Date: Mon, 12 Jan 2015 08:48:46 -0500 Message-ID: From: Simon Perreault To: Tom Taylor Content-Type: multipart/alternative; boundary=089e01494268e7efbe050c74c337 Archived-At: Cc: "opsawg@ietf.org" , "behave@ietf.org" Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2015 13:48:50 -0000 --089e01494268e7efbe050c74c337 Content-Type: text/plain; charset=UTF-8 Since the beginning I've always said that configuring the NAT with SNMP was out of scope. The problem I see is not related to SNMP vs Yang, even though Yang might be a much better choice. The problem is that NAT implementations vary very much and their configuration even more so. It might be hard to find common functionality worth standardizing. Simon On Sun, Jan 11, 2015 at 4:43 PM, Tom Taylor wrote: > 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 mailing list > Behave@ietf.org > https://www.ietf.org/mailman/listinfo/behave > --089e01494268e7efbe050c74c337 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Since the beginning I've always said that configuring = the NAT with SNMP was out of scope.

The problem I see is= not related to SNMP vs Yang, even though Yang might be a much better choic= e. The problem is that NAT implementations vary very much and their configu= ration even more so. It might be hard to find common functionality worth st= andardizing.

Simon

On Sun, Jan 11, 2015 at 4:43 PM, Tom = Taylor <tom.taylor.stds@gmail.com> wrote:
Given present policies regarding the respective rol= es of SNMP and Yang, is it reasonable to say that the only configuration da= ta that should be present in the NAT MIB is data directly relating to the c= ontrol 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 mailing list
Behave@ietf.org = https://www.ietf.org/mailman/listinfo/behave

--089e01494268e7efbe050c74c337-- From nobody Thu Jan 15 23:55:37 2015 Return-Path: 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 E07691AC3A8 for ; Thu, 15 Jan 2015 23:55:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.512 X-Spam-Level: X-Spam-Status: No, score=-105.512 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 h8aWFi00ZPC4 for ; Thu, 15 Jan 2015 23:55:35 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 7852F1AC3A0 for ; Thu, 15 Jan 2015 23:55:35 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 06424180092; Thu, 15 Jan 2015 23:55:31 -0800 (PST) To: jdrosen@cisco.com, rohan@ekabal.com, philip_matthews@magma.ca, dwing@cisco.com, spencerdawkins.ietf@gmail.com, mls.ietf@gmail.com, dwing@cisco.com, dthaler@microsoft.com X-PHP-Originating-Script: 6000:errata_mail_lib.php From: RFC Errata System Message-Id: <20150116075531.06424180092@rfc-editor.org> Date: Thu, 15 Jan 2015 23:55:31 -0800 (PST) Archived-At: Cc: mm05@mail.ru, behave@ietf.org, rfc-editor@rfc-editor.org Subject: [BEHAVE] [Editorial Errata Reported] RFC5389 (4233) X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 07:55:37 -0000 The following errata report has been submitted for RFC5389, "Session Traversal Utilities for NAT (STUN)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5389&eid=4233 -------------------------------------- Type: Editorial Reported by: Anatoliy Sivov Section: 18.2 Original Text ------------- Comprehension-required range (0x0000-0x7FFF): 0x0000: (Reserved) 0x0001: MAPPED-ADDRESS 0x0002: (Reserved; was RESPONSE-ADDRESS) 0x0003: (Reserved; was CHANGE-ADDRESS) 0x0004: (Reserved; was SOURCE-ADDRESS) 0x0005: (Reserved; was CHANGED-ADDRESS) Corrected Text -------------- Comprehension-required range (0x0000-0x7FFF): 0x0000: (Reserved) 0x0001: MAPPED-ADDRESS 0x0002: (Reserved; was RESPONSE-ADDRESS) 0x0003: (Reserved; was CHANGE-REQUEST) 0x0004: (Reserved; was SOURCE-ADDRESS) 0x0005: (Reserved; was CHANGED-ADDRESS) Notes ----- Text says that attribute 0x0003 was known as CHANGE-ADDRESS, but it was named CHANGE-REQUEST in RFC 3489. It is the only place in RFC 5389, where CHANGE-ADDRESS is used instead of CHANGE-REQUEST, as I can see. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5389 (draft-ietf-behave-rfc3489bis-18) -------------------------------------- Title : Session Traversal Utilities for NAT (STUN) Publication Date : October 2008 Author(s) : J. Rosenberg, R. Mahy, P. Matthews, D. Wing Category : PROPOSED STANDARD Source : Behavior Engineering for Hindrance Avoidance Area : Transport Stream : IETF Verifying Party : IESG From nobody Sun Jan 18 19:57:34 2015 Return-Path: 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 CAF501AD0B1; Sun, 18 Jan 2015 19:57:33 -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 5kWSfU_snfYA; Sun, 18 Jan 2015 19:57:29 -0800 (PST) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0A9C1AD0AD; Sun, 18 Jan 2015 19:57:28 -0800 (PST) Received: by mail-ig0-f174.google.com with SMTP id b16so4560129igk.1; Sun, 18 Jan 2015 19:57:28 -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:references :in-reply-to:content-type:content-transfer-encoding; bh=ZVEM48L1r3kgZx7gnUfqhi/KjORcXJY1lLHgfImzBHM=; b=WIRwwabymsffDNvi03HHj7QM0x2+4vltP016lBOAe6gou/tEcWRL2xfUtrONegIu6B ErsterzmoaKxiOrrIFyfT7eu4MQSQHo9ieJSt+Ud2o1sneFbcXYZS25nRVukxBmTfjse HLzQehiQpXuw079VbUHTG2/DpxVi5rgbnONP5zj1V/JGoR91rNeoBPzOiE7XBNEGvSCf JJ088+/2/g0E9r6Kz9NW4Su6WPRl9uyvzwgNcbw9BF9u4BEUbVLWAFCbZenxkDiDPEeC 0kQR3bZCbmzjVe1XQHC7BW8Uauhp+vOEhpEXhAvrpmdiSP5A1cLWTsZqGy38RpMKAjdc fFlg== X-Received: by 10.50.107.7 with SMTP id gy7mr16899690igb.49.1421639847941; Sun, 18 Jan 2015 19:57:27 -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 i37sm4803076iod.6.2015.01.18.19.57.27 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Jan 2015 19:57:27 -0800 (PST) Message-ID: <54BC8093.7030104@gmail.com> Date: Sun, 18 Jan 2015 22:57:07 -0500 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "behave@ietf.org" , "opsawg@ietf.org" , David Harrington , Spencer Dawkins References: <20150119034503.15593.74413.idtracker@ietfa.amsl.com> In-Reply-To: <20150119034503.15593.74413.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20150119034503.15593.74413.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [BEHAVE] Fwd: New Version Notification for draft-perrault-behave-natv2-mib-00.txt X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2015 03:57:34 -0000 Several months' work, almost done. A couple of sections need work, as indicated in the document, but there's lots to review including the complete MIB module definition. This is a major rewrite from the draft-ietf-behave-nat-11 version of NAT MIB. Reworking was needed to address all the issues outstanding against that document. I suppose the next step is to send out a series of messages walking through all the changes from draft-ietf-behave-nat-11 and how they respond to the open issues. I look forward to any comments on the new document. Tom Taylor -------- Forwarded Message -------- Subject: New Version Notification for draft-perrault-behave-natv2-mib-00.txt Date: Sun, 18 Jan 2015 19:45:03 -0800 From: internet-drafts@ietf.org .... A new version of I-D, draft-perrault-behave-natv2-mib-00.txt has been successfully submitted by Tom Taylor and posted to the IETF repository. Name: draft-perrault-behave-natv2-mib Revision: 00 Title: Definitions of Managed Objects for Network Address Translators (NAT) Document date: 2015-01-18 Group: Individual Submission Pages: 80 URL: http://www.ietf.org/internet-drafts/draft-perrault-behave-natv2-mib-00.txt Status: https://datatracker.ietf.org/doc/draft-perrault-behave-natv2-mib/ Htmlized: http://tools.ietf.org/html/draft-perrault-behave-natv2-mib-00 Abstract: This memo defines a portion of the Management Information Base (MIB) for devices implementing the Network Address Translator (NAT) function. The new MIB module defined in this document, NATV2-MIB, is intended to replace module NAT-MIB (RFC 4008). NATV2-MIB is not backwards compatible with NAT-MIB, for reasons given in the text of this document. A companion document deprecates all objects in NAT- MIB. NATV2-MIB can be used for monitoring of NAT instances on a device capable of NAT function. Compliance levels are defined for three application scenarios: basic NAT, pooled NAT, and carrier-grade NAT (CGN). Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat From nobody Mon Jan 19 12:37:13 2015 Return-Path: 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 148551ACEB6 for ; Fri, 16 Jan 2015 08:42:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=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 j-r0twwKbg8h; Fri, 16 Jan 2015 08:42:56 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C92751ACEC5; Fri, 16 Jan 2015 08:42:55 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: draft-perrault-behave-deprecate-nat-mib-v1.all@tools.ietf.org, simon.perreault@viagenie.ca, ssenthil@cisco.com, tom.taylor.stds@gmail.com, tina.tsou.zouting@huawei.com, behave@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p8 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150116164255.23606.14254.idtracker@ietfa.amsl.com> Date: Fri, 16 Jan 2015 08:42:55 -0800 From: IETF Secretariat Archived-At: X-Mailman-Approved-At: Mon, 19 Jan 2015 12:37:12 -0800 Subject: [BEHAVE] ID Tracker State Update Notice: X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.15 List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 16:42:57 -0000 IESG state changed to AD Evaluation from Publication Requested ID Tracker URL: http://datatracker.ietf.org/doc/draft-perrault-behave-deprecate-nat-mib-v1/ From nobody Mon Jan 19 12:37:15 2015 Return-Path: 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 097D21B2C82 for ; Fri, 16 Jan 2015 13:59:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=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 5LxRxBznyhT1; Fri, 16 Jan 2015 13:59:37 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C96AA1B2C68; Fri, 16 Jan 2015 13:59:37 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: draft-perrault-behave-deprecate-nat-mib-v1.all@tools.ietf.org, simon.perreault@viagenie.ca, ssenthil@cisco.com, tom.taylor.stds@gmail.com, tina.tsou.zouting@huawei.com, behave@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.10.0.p8 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150116215937.13669.37306.idtracker@ietfa.amsl.com> Date: Fri, 16 Jan 2015 13:59:37 -0800 From: IETF Secretariat Archived-At: X-Mailman-Approved-At: Mon, 19 Jan 2015 12:37:12 -0800 Subject: [BEHAVE] ID Tracker State Update Notice: X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.15 List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 21:59:39 -0000 IESG state changed to AD Evaluation::Revised I-D Needed from AD Evaluation ID Tracker URL: http://datatracker.ietf.org/doc/draft-perrault-behave-deprecate-nat-mib-v1/ From nobody Mon Jan 26 23:50:34 2015 Return-Path: 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 35C7B1B2BB7; Mon, 26 Jan 2015 23:50:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.211 X-Spam-Level: X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ZgVn4QWQJ3qM; Mon, 26 Jan 2015 23:50:30 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 383911B2BBD; Mon, 26 Jan 2015 23:50:24 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOL71875; Tue, 27 Jan 2015 07:50:22 +0000 (GMT) Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 27 Jan 2015 07:50:21 +0000 Received: from NKGEML505-MBX.china.huawei.com ([169.254.1.222]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Tue, 27 Jan 2015 15:50:14 +0800 From: "Fuyu (Eleven)" To: Tom Taylor Thread-Topic: [BEHAVE] Fwd: New Version Notification for draft-perrault-behave-natv2-mib-00.txt Thread-Index: AQHQM5wZ3ZnSCC9zhEy9NYG9dwVfrZzTo9cA Date: Tue, 27 Jan 2015 07:50:14 +0000 Message-ID: References: <20150119034503.15593.74413.idtracker@ietfa.amsl.com> <54BC8093.7030104@gmail.com> In-Reply-To: <54BC8093.7030104@gmail.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.111.99.184] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Cc: David Harrington , "opsawg@ietf.org" , "behave@ietf.org" , Spencer Dawkins Subject: Re: [BEHAVE] Fwd: New Version Notification for draft-perrault-behave-natv2-mib-00.txt X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2015 07:50:32 -0000 Hi Tom,=20 Some comments for the draft-perrault-behave-natv2-mib-00.txt, I think they = are typos:) natv2PoolIndex OBJECT-TYPE SYNTAX Natv2PoolId MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index of an address pool, unique for a given NAT instance. It is up to the agent implementation to determine and operate upon only those values that correspond to provisioned pools." ::=3D { natv2PoolEntry 2 } In this object, I think the SYNTAX should be Natv2PoolIndex. It doesn't def= ine Natv2PoolId in the draft-perrault-behave-natv2-mib-00.txt. natv2PortMapExternalPool OBJECT-TYPE SYNTAX Natv2PoolIndexOrZero MAX-ACCESS read-only STATUS current DESCRIPTION "Index of the address pool in the external realm from which the mapped external address given in natv2AddressMapExternalAddress was taken. Zero if the implementation does not support address pools but has chosen to support this object, or if no pool was configured for the given external realm." ::=3D { natv2AddressMapEntry 11 } The name of this object should be natv2AddressMapExternalPool. Cheers=20 Yu -----Original Message----- From: Behave [mailto:behave-bounces@ietf.org] On Behalf Of Tom Taylor Sent: Monday, January 19, 2015 11:57 AM To: behave@ietf.org; opsawg@ietf.org; David Harrington; Spencer Dawkins Subject: [BEHAVE] Fwd: New Version Notification for draft-perrault-behave-n= atv2-mib-00.txt Several months' work, almost done. A couple of sections need work, as indic= ated in the document, but there's lots to review including the complete MIB= module definition. This is a major rewrite from the draft-ietf-behave-nat-11 version of NAT MI= B. Reworking was needed to address all the issues outstanding against that = document. I suppose the next step is to send out a series of messages walki= ng through all the changes from draft-ietf-behave-nat-11 and how they respond to the open issues. I look forward to any comments on the new document. Tom Taylor -------- Forwarded Message -------- Subject: New Version Notification for draft-perrault-behave-natv2-mib-00.tx= t Date: Sun, 18 Jan 2015 19:45:03 -0800 From: internet-drafts@ietf.org .... A new version of I-D, draft-perrault-behave-natv2-mib-00.txt has been successfully submitted by Tom Taylor and posted to the IETF reposi= tory. Name: draft-perrault-behave-natv2-mib Revision: 00 Title: Definitions of Managed Objects for Network Address Translators (NAT= ) Document date: 2015-01-18 Group: Individual Submission Pages: 80 URL:=20 http://www.ietf.org/internet-drafts/draft-perrault-behave-natv2-mib-00.txt Status:=20 https://datatracker.ietf.org/doc/draft-perrault-behave-natv2-mib/ Htmlized:=20 http://tools.ietf.org/html/draft-perrault-behave-natv2-mib-00 Abstract: This memo defines a portion of the Management Information Base (MIB) for devices implementing the Network Address Translator (NAT) function. The new MIB module defined in this document, NATV2-MIB, is intended to replace module NAT-MIB (RFC 4008). NATV2-MIB is not backwards compatible with NAT-MIB, for reasons given in the text of this document. A companion document deprecates all objects in NAT- MIB. NATV2-MIB can be used for monitoring of NAT instances on a device capable of NAT function. Compliance levels are defined for three application scenarios: basic NAT, pooled NAT, and carrier-grade NAT (CGN). =20 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat _______________________________________________ Behave mailing list Behave@ietf.org https://www.ietf.org/mailman/listinfo/behave From nobody Tue Jan 27 05:42:55 2015 Return-Path: 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 000DD1A1A6E; Tue, 27 Jan 2015 05:42:43 -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 qVUvn9ao6fSO; Tue, 27 Jan 2015 05:42:35 -0800 (PST) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 491811A026F; Tue, 27 Jan 2015 05:42:35 -0800 (PST) Received: by mail-ie0-f173.google.com with SMTP id tr6so15111658ieb.4; Tue, 27 Jan 2015 05:42:34 -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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ttdyaCr/gbGVTat7ZVG8MPzRT38QlhwEH/DAofdW1SY=; b=wVfwELJsWhdGe2pA3qB+obcE0FSwLpTME2gUMpob05mX6z5UeskhkpElLcnMW8+nG2 FeZycMJDe4dnWIrxb/XfTV7XwClVhwz9L3A8fmsqsIE5c+wW738G0LX6dJAORpzU74RG j/gKu1LnAJbTG83SI7AciXUC961nUuJHfAXjfiYSWvUtoEhtKqjdAIwjHCmuZdmcUrOO cWp7qRyXfAlSHYmvwPedHVdq+gg7nLI8IRADFrd/XrmdcsV6T7l5QuB9tAhw748NLbQw cbt237XEaUKWmkmjnnldkXKC2TNZcQUDgJgPLo02QItI35YocCZ0QB3ufwG/7HslJYmo ZcZw== X-Received: by 10.50.176.196 with SMTP id ck4mr22448635igc.40.1422366154425; Tue, 27 Jan 2015 05:42:34 -0800 (PST) Received: from [192.168.0.101] (dsl-173-206-73-98.tor.primus.ca. [173.206.73.98]) by mx.google.com with ESMTPSA id w140sm701299iod.13.2015.01.27.05.42.33 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Jan 2015 05:42:34 -0800 (PST) Message-ID: <54C795CA.6020206@gmail.com> Date: Tue, 27 Jan 2015 08:42:34 -0500 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "Fuyu (Eleven)" References: <20150119034503.15593.74413.idtracker@ietfa.amsl.com> <54BC8093.7030104@gmail.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: David Harrington , "opsawg@ietf.org" , "behave@ietf.org" , Spencer Dawkins Subject: Re: [BEHAVE] Fwd: New Version Notification for draft-perrault-behave-natv2-mib-00.txt X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2015 13:42:44 -0000 Thank you very much. Tom On 27/01/2015 2:50 AM, Fuyu (Eleven) wrote: > Hi Tom, > > Some comments for the draft-perrault-behave-natv2-mib-00.txt, I think they are typos:) > > natv2PoolIndex OBJECT-TYPE > SYNTAX Natv2PoolId > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Index of an address pool, unique for a given NAT instance. > It is up to the agent implementation to determine and > operate upon only those values that correspond to > provisioned pools." > ::= { natv2PoolEntry 2 } > > In this object, I think the SYNTAX should be Natv2PoolIndex. It doesn't define Natv2PoolId in the draft-perrault-behave-natv2-mib-00.txt. > > natv2PortMapExternalPool OBJECT-TYPE > SYNTAX Natv2PoolIndexOrZero > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "Index of the address pool in the external realm from which > the mapped external address given in > natv2AddressMapExternalAddress was taken. Zero if the > implementation does not support address pools but has chosen > to support this object, or if no pool was configured for the > given external realm." > ::= { natv2AddressMapEntry 11 } > > The name of this object should be natv2AddressMapExternalPool. > > Cheers > Yu > > -----Original Message----- > From: Behave [mailto:behave-bounces@ietf.org] On Behalf Of Tom Taylor > Sent: Monday, January 19, 2015 11:57 AM > To: behave@ietf.org; opsawg@ietf.org; David Harrington; Spencer Dawkins > Subject: [BEHAVE] Fwd: New Version Notification for draft-perrault-behave-natv2-mib-00.txt > > Several months' work, almost done. A couple of sections need work, as indicated in the document, but there's lots to review including the complete MIB module definition. > > This is a major rewrite from the draft-ietf-behave-nat-11 version of NAT MIB. Reworking was needed to address all the issues outstanding against that document. I suppose the next step is to send out a series of messages walking through all the changes from > draft-ietf-behave-nat-11 and how they respond to the open issues. > > I look forward to any comments on the new document. > > Tom Taylor > > -------- Forwarded Message -------- > Subject: New Version Notification for draft-perrault-behave-natv2-mib-00.txt > Date: Sun, 18 Jan 2015 19:45:03 -0800 > From: internet-drafts@ietf.org > .... > > A new version of I-D, draft-perrault-behave-natv2-mib-00.txt > has been successfully submitted by Tom Taylor and posted to the IETF repository. > > Name: draft-perrault-behave-natv2-mib > Revision: 00 > Title: Definitions of Managed Objects for Network Address Translators (NAT) > Document date: 2015-01-18 > Group: Individual Submission > Pages: 80 > URL: > http://www.ietf.org/internet-drafts/draft-perrault-behave-natv2-mib-00.txt > Status: > https://datatracker.ietf.org/doc/draft-perrault-behave-natv2-mib/ > Htmlized: > http://tools.ietf.org/html/draft-perrault-behave-natv2-mib-00 > > > Abstract: > This memo defines a portion of the Management Information Base (MIB) > for devices implementing the Network Address Translator (NAT) > function. The new MIB module defined in this document, NATV2-MIB, is > intended to replace module NAT-MIB (RFC 4008). NATV2-MIB is not > backwards compatible with NAT-MIB, for reasons given in the text of > this document. A companion document deprecates all objects in NAT- > MIB. NATV2-MIB can be used for monitoring of NAT instances on a > device capable of NAT function. Compliance levels are defined for > three application scenarios: basic NAT, pooled NAT, and carrier-grade > NAT (CGN). > > > > > > Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > > > > _______________________________________________ > Behave mailing list > Behave@ietf.org > https://www.ietf.org/mailman/listinfo/behave > From nobody Thu Jan 29 08:54:41 2015 Return-Path: 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 3B0321A8742 for ; Thu, 29 Jan 2015 08:54:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 2BCndaMxxcu9; Thu, 29 Jan 2015 08:54:37 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 637BE1A1A9B; Thu, 29 Jan 2015 08:54:36 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: draft-perrault-behave-deprecate-nat-mib-v1.all@tools.ietf.org, simon.perreault@viagenie.ca, ssenthil@cisco.com, tom.taylor.stds@gmail.com, tina.tsou.zouting@huawei.com, behave@ietf.org, spencerdawkins.ietf@gmail.com X-Test-IDTracker: no X-IETF-IDTracker: 5.10.1.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150129165436.19364.25490.idtracker@ietfa.amsl.com> Date: Thu, 29 Jan 2015 08:54:36 -0800 Archived-At: Subject: [BEHAVE] New Version Notification - draft-perrault-behave-deprecate-nat-mib-v1-01.txt X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.15 List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2015 16:54:38 -0000 A new version (-01) has been submitted for draft-perrault-behave-deprecate-nat-mib-v1: http://www.ietf.org/internet-drafts/draft-perrault-behave-deprecate-nat-mib-v1-01.txt Sub state has been changed to AD Followup from Revised ID Needed The IETF datatracker page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-perrault-behave-deprecate-nat-mib-v1/ Diff from previous version: http://www.ietf.org/rfcdiff?url2=draft-perrault-behave-deprecate-nat-mib-v1-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. IETF Secretariat. From nobody Thu Jan 29 09:12:21 2015 Return-Path: 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 D9B0D1A87C4; Thu, 29 Jan 2015 09:12:00 -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 GPPBZHtE5Mal; Thu, 29 Jan 2015 09:11:59 -0800 (PST) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42C351A87D2; Thu, 29 Jan 2015 09:11:19 -0800 (PST) Received: by mail-ie0-f182.google.com with SMTP id ar1so36331944iec.13; Thu, 29 Jan 2015 09:11:18 -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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=LD6gQTXq1jhAK7da1AqvZPnmAjzXhGf2WYNUogAaP3Q=; b=I9xvZ+cmIxK1M7TLKSuXmpq4/ldzH69tEEWkoMTd4XlvsR3jpma4po9RS1XRhGKXjV ct0wC8pJkVp6tQ1FREXzH4oKQ7nhqaYzNpjpymdw89F3QOy8g2ZDVprB48yA6KICK9Y7 US0jWb5b1mT7fjvi1FhqJbXA6nvFgKl3sXUUKvWytcRnf7KDiNOtXAd9/HkendwG2i/W Ce4hoPpHTGHADV45okkkFJXr6PIIbNUrmriZBn1BdEHdSxevnAlsjQzvM8E7prUi7Wa0 W5V9GPFaJltmSOR0WOu5Sl5pLkCtQ+Dr4iTo+WWTF+SHe0nU0WdQiyMlMLGm3vXKPBeH H0MA== X-Received: by 10.107.166.13 with SMTP id p13mr1831452ioe.61.1422551478336; Thu, 29 Jan 2015 09:11:18 -0800 (PST) Received: from [192.168.0.101] (dsl-173-206-73-98.tor.primus.ca. [173.206.73.98]) by mx.google.com with ESMTPSA id b7sm1196936igx.15.2015.01.29.09.11.17 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Jan 2015 09:11:18 -0800 (PST) Message-ID: <54CA69B9.8010305@gmail.com> Date: Thu, 29 Jan 2015 12:11:21 -0500 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "behave@ietf.org" , "opsawg@ietf.org" References: <20150129165436.19364.82358.idtracker@ietfa.amsl.com> In-Reply-To: <20150129165436.19364.82358.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20150129165436.19364.82358.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: Spencer Dawkins Subject: [BEHAVE] Fwd: New Version Notification for draft-perrault-behave-deprecate-nat-mib-v1-01.txt X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2015 17:12:01 -0000 A small update based on suggestions from AD Spencer Dawkins. Primarily, deleted the list of new features that was in section 3.2, leaving that to the NATV2-MIB document. Also fixed a couple of authors' addresses and a couple of typos. Tom Taylor -------- Forwarded Message -------- Subject: New Version Notification for draft-perrault-behave-deprecate-nat-mib-v1-01.txt Date: Thu, 29 Jan 2015 08:54:36 -0800 From: internet-drafts@ietf.org To: Tom Taylor , Simon Perreault , Senthil Sivakumar , Simon Perreault , Tina Tsou , Tina Tsou , Senthil Sivakumar , Tom Taylor A new version of I-D, draft-perrault-behave-deprecate-nat-mib-v1-01.txt has been successfully submitted by Tom Taylor and posted to the IETF repository. Name: draft-perrault-behave-deprecate-nat-mib-v1 Revision: 01 Title: Deprecation of MIB Module NAT-MIB (Managed Objects for Network Address Translators (NAT)) Document date: 2015-01-29 Group: Individual Submission Pages: 59 URL: http://www.ietf.org/internet-drafts/draft-perrault-behave-deprecate-nat-mib-v1-01.txt Status: https://datatracker.ietf.org/doc/draft-perrault-behave-deprecate-nat-mib-v1/ Htmlized: http://tools.ietf.org/html/draft-perrault-behave-deprecate-nat-mib-v1-01 Diff: http://www.ietf.org/rfcdiff?url2=draft-perrault-behave-deprecate-nat-mib-v1-01 Abstract: This memo deprecates MIB module NAT-MIB, a portion of the Management Information Base (MIB) previously defined in RFC 4008 for devices implementing Network Address Translator (NAT) function. A companion document defines a new version, NAT-MIB-V2, which responds to deficiencies found in module NAT-MIB and adds new capabilities. This document obsoletes RFC 4008. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat From nobody Fri Jan 30 12:50:13 2015 Return-Path: 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 D9A401A8706; Fri, 30 Jan 2015 12:50:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 Nq6Vf2VOFy_P; Fri, 30 Jan 2015 12:50:07 -0800 (PST) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C6401A8722; Fri, 30 Jan 2015 12:50:04 -0800 (PST) Received: by mail-lb0-f180.google.com with SMTP id b6so38233621lbj.11; Fri, 30 Jan 2015 12:50:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=lYY9RJScyJhLe/MesJfm7xUe/xNEdTn6p0K4Ee53XN8=; b=dxOWJajW58mEX2mctYyDz8nLtGXnF06ud3xO4S3YwBpBrSh/vd3Fvww66k/1NQYGmH o9dnb/ZB7fQLB6AFX2SJsEkoUa1+WgrJ61WCKAGK6hNMUYcqqQJe6oe9sgTcj603RlJ3 ODFRZki0vVVBL1e2t7YmPFmd3dq78uUM/dkfgPmCClVzWhvjc4g3EJ4HH4j8hLLcc/dz v9vBSMRT/BUzmq0Sq+iGYz0O6NZAbcgyTB0vShY2nw9VBAY9Lb1jEChnVZAnZP0CkHtG VIlN7gBt3SOvZXvpGwZnJNbNVTUSmacGcICnTcZ2kaBnF4AE457dXf8vlhpj5OTosa0a fssA== MIME-Version: 1.0 X-Received: by 10.112.224.133 with SMTP id rc5mr4406223lbc.31.1422651002888; Fri, 30 Jan 2015 12:50:02 -0800 (PST) Received: by 10.152.1.6 with HTTP; Fri, 30 Jan 2015 12:50:02 -0800 (PST) Received: by 10.152.1.6 with HTTP; Fri, 30 Jan 2015 12:50:02 -0800 (PST) Date: Fri, 30 Jan 2015 14:50:02 -0600 Message-ID: From: Spencer Dawkins at IETF To: Tom Taylor Content-Type: multipart/alternative; boundary=001a11360522aaa9e8050de4bfac Archived-At: Cc: David Harrington , opsawg@ietf.org, behave@ietf.org Subject: Re: [BEHAVE] Fwd: New Version Notification for draft-perrault-behave-natv2-mib-00.txt X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2015 20:50:10 -0000 --001a11360522aaa9e8050de4bfac Content-Type: text/plain; charset=UTF-8 Hi, Tom, On Jan 18, 2015 9:57 PM, "Tom Taylor" wrote: > > Several months' work, almost done. A couple of sections need work, as indicated in the document, but there's lots to review including the complete MIB module definition. Tina was asking me about this draft - are you planning to have me send -00 to the IESG, or were you going to do another revision? Spencer, who thought he knew what the plan was, but ... :-) > This is a major rewrite from the draft-ietf-behave-nat-11 version of > NAT MIB. Reworking was needed to address all the issues outstanding against that document. I suppose the next step is to send out a series of messages walking through all the changes from > draft-ietf-behave-nat-11 and how they respond to the open issues. > > I look forward to any comments on the new document. > > Tom Taylor > > -------- Forwarded Message -------- > Subject: New Version Notification for draft-perrault-behave-natv2-mib-00.txt > Date: Sun, 18 Jan 2015 19:45:03 -0800 > From: internet-drafts@ietf.org > .... > > A new version of I-D, draft-perrault-behave-natv2-mib-00.txt > has been successfully submitted by Tom Taylor and posted to the > IETF repository. > > Name: draft-perrault-behave-natv2-mib > Revision: 00 > Title: Definitions of Managed Objects for Network Address Translators (NAT) > Document date: 2015-01-18 > Group: Individual Submission > Pages: 80 > URL: http://www.ietf.org/internet-drafts/draft-perrault-behave-natv2-mib-00.txt > Status: https://datatracker.ietf.org/doc/draft-perrault-behave-natv2-mib/ > Htmlized: http://tools.ietf.org/html/draft-perrault-behave-natv2-mib-00 > > > Abstract: > This memo defines a portion of the Management Information Base (MIB) > for devices implementing the Network Address Translator (NAT) > function. The new MIB module defined in this document, NATV2-MIB, is > intended to replace module NAT-MIB (RFC 4008). NATV2-MIB is not > backwards compatible with NAT-MIB, for reasons given in the text of > this document. A companion document deprecates all objects in NAT- > MIB. NATV2-MIB can be used for monitoring of NAT instances on a > device capable of NAT function. Compliance levels are defined for > three application scenarios: basic NAT, pooled NAT, and carrier-grade > NAT (CGN). > > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > > > --001a11360522aaa9e8050de4bfac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi, Tom,

On Jan 18, 2015 9:57 PM, "Tom Taylor" <tom.taylor.stds@gmail.com> wro= te:
>
> Several months' work, almost done. A couple of sections need work,= as indicated in the document, but there's lots to review including the= complete MIB module definition.

Tina was asking me about this draft - are you planning to ha= ve me send -00 to the IESG, or were you going to do another revision?

Spencer, who thought he knew what the plan was, but ... :-)<= /p>

> This is a major rewrite from the draft-ietf-behave-nat-= 11 version of
> NAT MIB. Reworking was needed to address all the issues outstanding ag= ainst that document. I suppose the next step is to send out a series of mes= sages walking through all the changes from
> draft-ietf-behave-nat-11 and how they respond to the open issues.
>
> I look forward to any comments on the new document.
>
> Tom Taylor
>
> -------- Forwarded Message --------
> Subject: New Version Notification for draft-perrault-behave-natv2-mib-= 00.txt
> Date: Sun, 18 Jan 2015 19:45:03 -0800
> From: internet-drafts@ietf= .org
> ....
>
> A new version of I-D, draft-perrault-behave-natv2-mib-00.txt
> has been successfully submitted by Tom Taylor and posted to the
> IETF repository.
>
> Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-perrault-behave-na= tv2-mib
> Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A000
> Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Definitions of Managed Object= s for Network Address Translators (NAT)
> Document date:=C2=A0 2015-01-18
> Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission
> Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 80
> URL: http://www.ietf.org/internet-drafts/draft-perrault-be= have-natv2-mib-00.txt
> Status: https://datatracker.ietf.org/doc/draft-perrault-behave-natv= 2-mib/
> Htmlized: http://tools.ietf.org/html/draft-perrault-behave-natv2-mib-00=
>
>
> Abstract:
> =C2=A0 =C2=A0This memo defines a portion of the Management Information= Base (MIB)
> =C2=A0 =C2=A0for devices implementing the Network Address Translator (= NAT)
> =C2=A0 =C2=A0function.=C2=A0 The new MIB module defined in this docume= nt, NATV2-MIB, is
> =C2=A0 =C2=A0intended to replace module NAT-MIB (RFC 4008).=C2=A0 NATV= 2-MIB is not
> =C2=A0 =C2=A0backwards compatible with NAT-MIB, for reasons given in t= he text of
> =C2=A0 =C2=A0this document.=C2=A0 A companion document deprecates all = objects in NAT-
> =C2=A0 =C2=A0MIB.=C2=A0 NATV2-MIB can be used for monitoring of NAT in= stances on a
> =C2=A0 =C2=A0device capable of NAT function.=C2=A0 Compliance levels a= re defined for
> =C2=A0 =C2=A0three application scenarios: basic NAT, pooled NAT, and c= arrier-grade
> =C2=A0 =C2=A0NAT (CGN).
>
>
>
>
>
> Please note that it may take a couple of minutes from the time of subm= ission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
>

--001a11360522aaa9e8050de4bfac-- From nobody Fri Jan 30 15:33:30 2015 Return-Path: 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 3A9C81A87AD; Fri, 30 Jan 2015 15:33:25 -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 gbrKh2iGAZlT; Fri, 30 Jan 2015 15:33:23 -0800 (PST) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 302C01A87E6; Fri, 30 Jan 2015 15:33:15 -0800 (PST) Received: by mail-ie0-f182.google.com with SMTP id ar1so6847034iec.13; Fri, 30 Jan 2015 15:33:14 -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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=+KAJ4EwDint11bevk9igjVqPRg8YdoSwt/nh3AJb9Fc=; b=o8+4HnCz+nLhav07fhVN9U4ofx8m2Gqa6rC6wyQZYm3ebkKxw0jBi9grdpjcLJ+0cP oS3/mmBnUnpk76KU/OcvUFP04rT4TPDg3l7Z7r5W6n7uI9J2Wyw1XLPa7mQ7Cy7OohVm l6Xm06wPbPrA824PGiJPMIkbVDVSf27feb0nK7LwujYpMeQ0JCGpwCZDfo7YF9XebvSY 8OPskYclEXSiUVNtX3Lvly2PcNbJAG5KFJzydXise2u6j6J+VtFoOQUkeJ7HdM4n+FHo fKt36bS40Y1ZM978945nZGcx0QDRD+VXZOGMb1r5GLLqeSTVcnPTRf/IH6pd6ZCx3ZDZ GSZg== X-Received: by 10.43.19.134 with SMTP id qk6mr8748737icb.29.1422660794433; Fri, 30 Jan 2015 15:33:14 -0800 (PST) Received: from [192.168.0.101] (dsl-173-206-73-98.tor.primus.ca. [173.206.73.98]) by mx.google.com with ESMTPSA id n17sm2105163igi.2.2015.01.30.15.33.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Jan 2015 15:33:13 -0800 (PST) Message-ID: <54CC14B8.1050900@gmail.com> Date: Fri, 30 Jan 2015 18:33:12 -0500 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Spencer Dawkins at IETF References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: David Harrington , opsawg@ietf.org, behave@ietf.org Subject: Re: [BEHAVE] Fwd: New Version Notification for draft-perrault-behave-natv2-mib-00.txt X-BeenThere: behave@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: mailing list of BEHAVE IETF WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2015 23:33:25 -0000 I have to do another revision to add an Operational and Management Considerations section and update the Security Considerations section. I've been working through some other stuff, but this is next on my plate, I believe. Once I submit -01, it is ready to publish, subject to any review process you need to have happen first. So far I've had comments from Eleven Fuyu, who caught a couple of errors. Tom On 30/01/2015 3:50 PM, Spencer Dawkins at IETF wrote: > Hi, Tom, > > On Jan 18, 2015 9:57 PM, "Tom Taylor" wrote: >> >> Several months' work, almost done. A couple of sections need work, as > indicated in the document, but there's lots to review including the > complete MIB module definition. > > Tina was asking me about this draft - are you planning to have me send -00 > to the IESG, or were you going to do another revision? > > Spencer, who thought he knew what the plan was, but ... :-) > >> This is a major rewrite from the draft-ietf-behave-nat-11 version of >> NAT MIB. Reworking was needed to address all the issues outstanding > against that document. I suppose the next step is to send out a series of > messages walking through all the changes from >> draft-ietf-behave-nat-11 and how they respond to the open issues. >> >> I look forward to any comments on the new document. >> >> Tom Taylor >> >> -------- Forwarded Message -------- >> Subject: New Version Notification for > draft-perrault-behave-natv2-mib-00.txt >> Date: Sun, 18 Jan 2015 19:45:03 -0800 >> From: internet-drafts@ietf.org >> .... >> >> A new version of I-D, draft-perrault-behave-natv2-mib-00.txt >> has been successfully submitted by Tom Taylor and posted to the >> IETF repository. >> >> Name: draft-perrault-behave-natv2-mib >> Revision: 00 >> Title: Definitions of Managed Objects for Network Address > Translators (NAT) >> Document date: 2015-01-18 >> Group: Individual Submission >> Pages: 80 >> URL: > http://www.ietf.org/internet-drafts/draft-perrault-behave-natv2-mib-00.txt >> Status: https://datatracker.ietf.org/doc/draft-perrault-behave-natv2-mib/ >> Htmlized: http://tools.ietf.org/html/draft-perrault-behave-natv2-mib-00 >> >> >> Abstract: >> This memo defines a portion of the Management Information Base (MIB) >> for devices implementing the Network Address Translator (NAT) >> function. The new MIB module defined in this document, NATV2-MIB, is >> intended to replace module NAT-MIB (RFC 4008). NATV2-MIB is not >> backwards compatible with NAT-MIB, for reasons given in the text of >> this document. A companion document deprecates all objects in NAT- >> MIB. NATV2-MIB can be used for monitoring of NAT instances on a >> device capable of NAT function. Compliance levels are defined for >> three application scenarios: basic NAT, pooled NAT, and carrier-grade >> NAT (CGN). >> ...