[L2tpext] draft-ietf-l2tpext-l2tp-atm-02.txt
Thomas Narten <narten@us.ibm.com> Tue, 23 April 2002 19:41 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04073 for <l2tpext-archive@odin.ietf.org>; Tue, 23 Apr 2002 15:41:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA24924; Tue, 23 Apr 2002 15:40:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA24895 for <l2tpext@ns.ietf.org>; Tue, 23 Apr 2002 15:40:19 -0400 (EDT)
Received: from e21.nc.us.ibm.com (e21.nc.us.ibm.com [32.97.136.227]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03975 for <l2tpext@ietf.org>; Tue, 23 Apr 2002 15:40:14 -0400 (EDT)
Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.us.ibm.com [9.37.3.209]) by e21.nc.us.ibm.com (8.12.2/8.12.2) with ESMTP id g3NJeHuE161334 for <l2tpext@ietf.org>; Tue, 23 Apr 2002 15:40:17 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.9.21]) by southrelay02.raleigh.ibm.com (8.11.1m3/NCO/VER6.1) with ESMTP id g3NJeHM171612 for <l2tpext@ietf.org>; Tue, 23 Apr 2002 15:40:17 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id g3NJcdd11018 for <l2tpext@ietf.org>; Tue, 23 Apr 2002 15:38:39 -0400
Message-Id: <200204231938.g3NJcdd11018@rotala.raleigh.ibm.com>
To: l2tpext@ietf.org
Date: Tue, 23 Apr 2002 15:38:39 -0400
From: Thomas Narten <narten@us.ibm.com>
Subject: [L2tpext] draft-ietf-l2tpext-l2tp-atm-02.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
X-BeenThere: l2tpext@ietf.org
Some IESG comments on the security considerations section. reviewer 1 > note: > this has the same problem as PPP over AAL2 > the security section makes an unreasonable assumption on > ATM security Reviewer 2: > >9. Security Considerations > > > > ATM networks, being virtual circuit based, are generally less > > vulnerable to security attacks than IP based networks. The > > probability of a security breach caused by misrouted ATM cells is > > considered to be negligible. > > As in the case of PPP over AAL5, this is making an assumption about > who and how the ATM network is being operated and as such is > inappropriate in a standards document. I would recommend striking this > paragraph completely. > > > Currently there is no standard specification for ATM security. > > However, the ATM Forum is working on an ATM Security Framework > > document. In light of this work, the issue of security will be re- > > examined at a later date to see if L2TP over ATM specific protection > > mechanisms are still required. In the interim, basic security issues > > are discussed in the base L2TP specification [RFC2661]. > > I believe this paragraph is fine. Actually, maybe the above isn't really fine afterall. Note that draft-ietf-pppext-ppp-over-aal2-03.txt was recently updated with the following text: > System security may also be compromised by the attacks of the ATM > transport network itself. The ATM Forum has published a security > framework [11] and a security specification [12] that define > procedures to guard against common threats to an ATM transport > network. So, is it really the case to say that ATM has no security? Thomas _______________________________________________ L2tpext mailing list L2tpext@ietf.org https://www1.ietf.org/mailman/listinfo/l2tpext
- [L2tpext] draft-ietf-l2tpext-l2tp-atm-02.txt Thomas Narten
- RE: [L2tpext] draft-ietf-l2tpext-l2tp-atm-02.txt Singh Ajoy-ASINGH1
- Re: [L2tpext] draft-ietf-l2tpext-l2tp-atm-02.txt Thomas Narten