Re: [radext] #136: Table state management as security consideration?
"radext issue tracker" <trac+radext@trac.tools.ietf.org> Tue, 02 April 2013 14:00 UTC
Return-Path: <trac+radext@trac.tools.ietf.org>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4718A21F8ADC for <radext@ietfa.amsl.com>; Tue, 2 Apr 2013 07:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 P3-vD735XBTu for <radext@ietfa.amsl.com>; Tue, 2 Apr 2013 07:00:00 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id B5B8121F8AD8 for <radext@ietf.org>; Tue, 2 Apr 2013 07:00:00 -0700 (PDT)
Received: from localhost ([127.0.0.1]:48319 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+radext@trac.tools.ietf.org>) id 1UN1kj-0007TF-Nl; Tue, 02 Apr 2013 15:59:57 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: radext issue tracker <trac+radext@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-radext-dtls@tools.ietf.org, aland@deployingradius.com
X-Trac-Project: radext
Date: Tue, 02 Apr 2013 13:59:57 -0000
X-URL: http://tools.ietf.org/radext/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/136#comment:2
Message-ID: <074.dfea2851d26bfdc96288acbfcdd93f63@trac.tools.ietf.org>
References: <059.d793aee480c4d789a537efce305ec9f7@trac.tools.ietf.org>
X-Trac-Ticket-ID: 136
In-Reply-To: <059.d793aee480c4d789a537efce305ec9f7@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-radext-dtls@tools.ietf.org, aland@deployingradius.com, radext@ietf.org
X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: aland@freeradius.org
Resent-Message-Id: <20130402140000.B5B8121F8AD8@ietfa.amsl.com>
Resent-Date: Tue, 02 Apr 2013 07:00:00 -0700
Resent-From: trac+radext@trac.tools.ietf.org
Cc: radext@ietf.org
Subject: Re: [radext] #136: Table state management as security consideration?
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: radext@ietf.org
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2013 14:00:01 -0000
#136: Table state management as security consideration? Changes (by aland@deployingradius.com) * status: new => closed * resolution: => fixed Comment: The draft has been updated to clarify that the session tracking method is suggested, but not required. No other method has been offered, so it's probably best to leave that text where it is. It's also been updated to note that the suggested tracking table is an extension of the cache mandated in RFC 5080 Section 2.2.2. The security considerations has been updated to note that the tracking table changes things, but the earlier text has DoS mitigation strategies. -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-radext- ncamwing@cisco.com | dtls@tools.ietf.org Type: defect | Status: closed Priority: major | Milestone: Component: dtls | Version: Severity: - | Resolution: fixed Keywords: | -------------------------+------------------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/136#comment:2> radext <http://tools.ietf.org/radext/>
- [radext] #136: Table state management as security… radext issue tracker
- Re: [radext] #136: Table state management as secu… radext issue tracker
- Re: [radext] #136: Table state management as secu… radext issue tracker