Re: [BEHAVE] NAT Logging -- Port violation event for MAP-E or LW4over6 BR

Dan Wing <dwing@cisco.com> Fri, 26 April 2013 16:29 UTC

Return-Path: <dwing@cisco.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 C61EC21F99EC for <behave@ietfa.amsl.com>; Fri, 26 Apr 2013 09:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.339
X-Spam-Level:
X-Spam-Status: No, score=-110.339 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QiC0kZZRtPzI for <behave@ietfa.amsl.com>; Fri, 26 Apr 2013 09:29:10 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 4D8AB21F99E0 for <behave@ietf.org>; Fri, 26 Apr 2013 09:29:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1417; q=dns/txt; s=iport; t=1366993750; x=1368203350; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=BnQLupkdDuRnJ3CKSdyFrU5Zu7nZ1b/f3E17gitQwjA=; b=GVNxz3WmP+JliC2DQHMZ+J98KV/nH5MZ6KtWuOORRH+JJLkt7Fy1DRv7 AZFigWvZAMAWO4exDp841uz5GmFarcw2YDmv4JuaZg/oKdUmHATFYzEb7 YYJUom5rH59pkQ1t1nV3D/UgtWg+XEXPxvX7Bwv0Q+s1wQUim2RCZkgH3 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwFAJCqelGrRDoG/2dsb2JhbABRgwc2Ab44gQUWdIIfAQEBAwEBAQE3NAsFCwsYLiEGMAYTiAIDCQUNtjkNiEkEjDyCIzMHgm1hA4kSijyBa4FkhhKFeIUfgy4cgS4H
X-IronPort-AV: E=Sophos;i="4.87,559,1363132800"; d="scan'208";a="79630010"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 26 Apr 2013 16:29:10 +0000
Received: from [10.32.240.196] ([10.32.240.196]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3QGT9ft015726; Fri, 26 Apr 2013 16:29:09 GMT
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <517AA14C.4030605@gmail.com>
Date: Fri, 26 Apr 2013 09:29:08 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8FA24700-118B-4BAE-8DD0-FB72C45DEE22@cisco.com>
References: <517914F3.2070003@gmail.com> <517AA14C.4030605@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT Logging -- Port violation event for MAP-E or LW4over6 BR
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: Fri, 26 Apr 2013 16:29:10 -0000

On Apr 26, 2013, at 8:46 AM, Tom Taylor <tom.taylor.stds@gmail.com> wrote:

> Well, this comment has triggered an interesting discussion in Softwires, but now that I'm putting the final touches to a reissue of the SYSLOG NAT logging draft, I see it doesn't fit in very neatly there. The border router in these cases is not a NAT, so any discussion of logging probably belongs in a MAP-specific document. The CE is also responsible for checking, and the CE is a NAT, so it fits with the CE, but I'm not sure if it's worth standardizing.
> 
> I'll leave it out unless I get comments otherwise.

I believe the intent of generating such logging messages is diagnostics/troubleshooting, in order to detect mis-configured equipment.  The mis-configured equipment is the CPE router.  I don't recall, but doesn't the MAP router send back ICMP errors if the subscriber's CPE sends packets with the wrong port number?

-d


> On 25/04/2013 7:35 AM, Tom Taylor wrote:
>> The MAP-E and LW4over6 border routers are responsible for checking that
>> the ports assigned by the CE are within the set allocated to that CE. I
>> think we need a NAT logging event to report detection of an out-of-range
>> port.
>> 
>> Tom Taylor
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave