Re: [Softwires] Control and data plane

"Spencer Dawkins" <spencer@mcsr-labs.org> Mon, 16 January 2006 14:28 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EyVLc-0004xH-Qf; Mon, 16 Jan 2006 09:28:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EyVLc-0004xC-De for softwires@megatron.ietf.org; Mon, 16 Jan 2006 09:28:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16506 for <softwires@ietf.org>; Mon, 16 Jan 2006 09:27:15 -0500 (EST)
Received: from rwcrmhc12.comcast.net ([216.148.227.85]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyVTX-0003XN-Ps for softwires@ietf.org; Mon, 16 Jan 2006 09:36:53 -0500
Received: from s73602 (c-24-1-104-165.hsd1.tx.comcast.net[24.1.104.165]) by comcast.net (rwcrmhc12) with SMTP id <2006011614282701400dm5hne>; Mon, 16 Jan 2006 14:28:27 +0000
Message-ID: <1a1301c61aa8$f2e80e40$d0087c0a@china.huawei.com>
From: Spencer Dawkins <spencer@mcsr-labs.org>
To: softwires@ietf.org
References: <6EEEACD9D7F52940BEE26F5467C02C7302217AFD@PACDCEXCMB01.cable.comcast.com>
Subject: Re: [Softwires] Control and data plane
Date: Mon, 16 Jan 2006 08:27:14 -0600
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
Sender: softwires-bounces@ietf.org
Errors-To: softwires-bounces@ietf.org

FWIW, "control plane" is sufficiently overloaded and overused that it might 
be worth using the phrase "softwire mechanism", as Alain did when explaining 
what the control plane is. Any thoughts on this?

Spencer

----- Original Message ----- 
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: <jordi.palet@consulintel.es>; <softwires@ietf.org>
Sent: Monday, January 16, 2006 8:00 AM
Subject: RE: [Softwires] Control and data plane


>From: softwires-bounces@ietf.org on behalf of JORDI PALET MARTINEZ
>Sent: Mon 1/16/2006 8:31 AM
>To: softwires@ietf.org
>Subject: [Softwires] Control and data plane

>

>Hi all,
>
>I'm trying to clarify myself about this:
>
>3.11.2.  Privacy, Integrity, and Replay protection
>
>   The softwire Control and/or Data plane MUST be able to provide full
>   payload security (such as IPsec or SSL) when desired.  This
>   additional protection MUST be separable from the tunneling aspect of
>   the softwire mechanism itself.  For IPsec, default profiles MUST be
>  defined. [draft-ietf-v6ops-ipsec-tunnels] provides guidelines on
>   this.
>
>I'm starting to think that if I can't understand this text being 100% sure
>about what we want to say, then is not clear enough ;-)
>
>My question is, when we say contral and/or data plane, we are referring to
>the softwire protocol itself including any handshaking etc. ?
>
>So the handshaking is the payload and then is data, or data is the tunnel.
>
>Because if data is the tunnel (which is what I think), then it is already
>covered by the 2nd sentence ...


The "control' plane is the softwire mechanism. The data plane is made of the 
tunneled data.
My reading of the second sentence is that there is no a-priori restriction 
on
the way this security is achieved. For example, one can decide to protect 
the control plane
and not the data plane or vice versa, and this should be doable regardless 
of the tunneling
control mechanism softwire will use...

Does this makes things clearer?

>Moreover, are we requiring encryption or just authentication ?

Both and neither.

    - Alain.




_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www1.ietf.org/mailman/listinfo/softwires



_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www1.ietf.org/mailman/listinfo/softwires