Re: [Softwires] [Gen-art] Gen-ART review of draft-ietf-softwire-hs-framework-l2tpv2-10

Black_David@emc.com Tue, 23 December 2008 00:53 UTC

Return-Path: <softwires-bounces@ietf.org>
X-Original-To: softwires-archive@megatron.ietf.org
Delivered-To: ietfarch-softwires-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 954143A687B; Mon, 22 Dec 2008 16:53:09 -0800 (PST)
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33B5F3A6844; Mon, 22 Dec 2008 16:53:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.543
X-Spam-Level:
X-Spam-Status: No, score=-6.543 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HkYxrGoO8s1e; Mon, 22 Dec 2008 16:53:07 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 529613A683E; Mon, 22 Dec 2008 16:53:07 -0800 (PST)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id mBN0qsFK022988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Dec 2008 19:52:54 -0500 (EST)
From: Black_David@emc.com
Received: from mailhub.lss.emc.com (numailhub.lss.emc.com [10.254.144.15]) by hop04-l1d11-si04.isus.emc.com (Tablus Interceptor); Mon, 22 Dec 2008 19:33:34 -0500
Received: from corpussmtp4.corp.emc.com (corpussmtp4.corp.emc.com [10.254.64.54]) by mailhub.lss.emc.com (Switch-3.3.2mp/Switch-3.3.0) with ESMTP id mBN0qlba003272; Mon, 22 Dec 2008 19:52:47 -0500
Received: from CORPUSMX80A.corp.emc.com ([10.254.89.201]) by corpussmtp4.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 22 Dec 2008 19:49:20 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 22 Dec 2008 19:49:20 -0500
Message-ID: <9FA859626025B64FBC2AF149D97C944A01074C43@CORPUSMX80A.corp.emc.com>
In-Reply-To: <494314A7.5050507@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Gen-art] [Softwires] Gen-ART review of draft-ietf-softwire-hs-framework-l2tpv2-10
Thread-Index: AclcxRE2yvrghM+RQvaTZ4mMosZ5XQH0eX3w
References: <9FA859626025B64FBC2AF149D97C944A01074B3E@CORPUSMX80A.corp.emc.com><49401299.4010203@cisco.com> <49427871.8040204@cisco.com> <9FA859626025B64FBC2AF149D97C944A01074B84@CORPUSMX80A.corp.emc.com> <494314A7.5050507@cisco.com>
To: gen-art@ietf.org
X-OriginalArrivalTime: 23 Dec 2008 00:49:20.0557 (UTC) FILETIME=[4A90A5D0:01C96498]
X-EMM-EM: Active
X-RSA-Inspected: yes
X-RSA-Classifications:
X-RSA-Action: allow
Cc: softwires@ietf.org, Black_David@emc.com
Subject: Re: [Softwires] [Gen-art] Gen-ART review of draft-ietf-softwire-hs-framework-l2tpv2-10
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: softwires-bounces@ietf.org
Errors-To: softwires-bounces@ietf.org

After a lengthy private discussion with Carlos, and some
serious "quality time" spent with RFC 2661 ;-), here's
where I think the two major issues from my Gen-ART review
of this draft stand:

(1) AVP for softwire profile of L2TPv2.  I'm no longer
convinced that a new AVP is needed, but the specification
of the profile needs significant clarification and cleanup.
For example, what happens if a softwire implementation of
L2TPv2 happens to receive an OCRQ message?  This has also
turned up a topic that needs to be covered in the Security
Considerations section - a brief discussion of the security
consequences of the recommendation not to hide AVPs.

(2) RFC 5405 and UDP.  In addition to referencing RFC 5405,
a recommendation for L2TPv2 use of PMTUD will be added.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires