[BEHAVE] Fwd: New Version Notification for draft-zhou-behave-syslog-nat-logging-01.txt
Tom Taylor <tom.taylor.stds@gmail.com> Thu, 06 September 2012 19:48 UTC
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8301421F8766; Thu, 6 Sep 2012 12:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.414
X-Spam-Level:
X-Spam-Status: No, score=-3.414 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aAEZQ5+tgGTX; Thu, 6 Sep 2012 12:48:53 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id DABC421F8745; Thu, 6 Sep 2012 12:48:52 -0700 (PDT)
Received: by iabz21 with SMTP id z21so2714956iab.31 for <multiple recipients>; Thu, 06 Sep 2012 12:48:52 -0700 (PDT)
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:x-forwarded-message-id:content-type :content-transfer-encoding:x-antivirus:x-antivirus-status; bh=Xp8tOe/h28kFwr2Ao0J5IAjPXjeCZuKXGq7g8bueWvs=; b=dlaD9+wEPOqs7DDvDizha4bKNxM5qoNwZHKJ/Mv2R5XN5/iu2MbTzXAVNsbWSJXgqg 7UjRfJy37z9qV29BJwHavRjq1sKZ8nq+2yVEOOkjbt/ybhcbpwrcvbz+8xBrFmYJ4k4o O8q2GlXqYlpekKxXkzdQT91ax4nLPd0JLpMBQMfalxVESsL/7nDzsMGqFIDlu+edyrd/ G8m2WrvRYIjs3WdPZUqJfBmP4v8gO0/VwKmHGlmdemtrE+zR61lPLcF8avBn5L714XHi uBKtriwCSJskNC7ku2jmU+wITW1UKTX3CQeZ9n0Bqw1tMuQa38gxiD6X37+cL3o79hk+ Qpkw==
Received: by 10.50.53.199 with SMTP id d7mr4824052igp.55.1346960932369; Thu, 06 Sep 2012 12:48:52 -0700 (PDT)
Received: from [127.0.0.1] (dsl-173-206-40-163.tor.primus.ca. [173.206.40.163]) by mx.google.com with ESMTPS id ff4sm7350559igc.5.2012.09.06.12.48.50 (version=SSLv3 cipher=OTHER); Thu, 06 Sep 2012 12:48:51 -0700 (PDT)
Message-ID: <5048FE21.9040006@gmail.com>
Date: Thu, 06 Sep 2012 15:48:49 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: "behave@ietf.org" <behave@ietf.org>, pcp@ietf.org
References: <20120906193435.11136.29014.idtracker@ietfa.amsl.com>
In-Reply-To: <20120906193435.11136.29014.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20120906193435.11136.29014.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120906-0, 06/09/2012), Outbound message
X-Antivirus-Status: Clean
Subject: [BEHAVE] Fwd: New Version Notification for draft-zhou-behave-syslog-nat-logging-01.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 06 Sep 2012 19:48:53 -0000
draft-zhou-behave-syslog-nat-logging was presented in Vancouver and was the subject of a fair amount of discussion. People were not convinced that operators would want NAT logging, even if the volume of data generated is cut down by orders of magnitude through allocation of blocks of ports. There was also the question of whether operators could agree on the log contents they require. The authors have accepted this verdict, and are prepared to wait until operator demand emerges. In the meantime, the draft has been drastically rewritten to focus on the format for a SYSLOG record, with the philosophy that all parameters are optional. Each operator selects the subset most relevant to their deployment. As mentioned in the Abstract, the authors see an opportunity to expand the scope of the draft to include PCP logging. The present draft just has indications of this possibility -- the authors have not thought it through. If the draft takes that route, it would probably define multiple log types to handle the different PCP operations. Tom Taylor -------- Original Message -------- Subject: New Version Notification for draft-zhou-behave-syslog-nat-logging-01.txt Date: Thu, 06 Sep 2012 12:34:35 -0700 From: internet-drafts@ietf.org To: tom.taylor.stds@gmail.com CC: cathy.zhou@huawei.com, tina.tsou.zouting@huawei.com, 18918588897@189.cn A new version of I-D, draft-zhou-behave-syslog-nat-logging-01.txt has been successfully submitted by T. Taylor and posted to the IETF repository. Filename: draft-zhou-behave-syslog-nat-logging Revision: 01 Title: Syslog Format for NAT Logging Creation date: 2012-09-06 WG ID: Individual Submission Number of pages: 8 URL: http://www.ietf.org/internet-drafts/draft-zhou-behave-syslog-nat-logging-01.txt ... Abstract: Under some circumstances operators will need to maintain a dynamic record of external address and port assignments made by a Carrier Grade NAT (CGN), and will find it feasible and convenient to create such records using SYSLOG (RFC 5424). The present document standardizes a SYSLOG format to meet that recording requirement. It specifies a number of fields that could be a part of the log report, leaving it up to operators to select the fields needed for their specific circumstances. [*** Subject to discussion*** The log format presented here may also be used by PCP server implementations to log the mappings they implement.] ...