
From Tomaso.deCola@dlr.de  Fri Nov 16 07:31:53 2012
Return-Path: <Tomaso.deCola@dlr.de>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF71021F87E1 for <tcmtf@ietfa.amsl.com>; Fri, 16 Nov 2012 07:31:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.39
X-Spam-Level: 
X-Spam-Status: No, score=-8.39 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FJT9Gnx1Kz4M for <tcmtf@ietfa.amsl.com>; Fri, 16 Nov 2012 07:31:52 -0800 (PST)
Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.32]) by ietfa.amsl.com (Postfix) with ESMTP id A951A21F86E6 for <tcmtf@ietf.org>; Fri, 16 Nov 2012 07:31:51 -0800 (PST)
Received: from DLREXHUB01.intra.dlr.de (172.21.152.130) by dlrexedge01.dlr.de (172.21.163.100) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 16 Nov 2012 16:31:25 +0100
Received: from DLREXMBX02.intra.dlr.de ([fe80::8cc6:b83e:ddc1:4e8b]) by dlrexhub01.intra.dlr.de ([::1]) with mapi id 14.02.0318.004; Fri, 16 Nov 2012 16:31:26 +0100
From: <Tomaso.deCola@dlr.de>
To: <tcmtf@ietf.org>
Thread-Topic: Some thoughts about new scenarios for tcmtf
Thread-Index: Ac3EDOy4duakoHOCR7KDbQibMeqaCQ==
Date: Fri, 16 Nov 2012 15:31:25 +0000
Message-ID: <1A39DCC13AF3C14B83CD74124D4DCFC30BE89012@dlrexmbx02.intra.dlr.de>
Accept-Language: it-IT, de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.247.173.215]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Tomaso.deCola@dlr.de, Matteo.Berioli@dlr.de, Hartmut.Brandt@dlr.de, jsaldana@unizar.es
Subject: [tcmtf] Some thoughts about new scenarios for tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Nov 2012 15:31:53 -0000

Dear All,

As discussed some time ago, satellite and wireless access network can be at=
tractive network scenarios where tcmtf principles can be exploited.
However, usual wireless and satellite encapsulation protocol (between IP an=
d lower layers) already provide means to multiplexing and "tunneling"=20
compressed flows.=20
In this respect, the application of tcmtf in these scenarios is less attrac=
tive, as it would introduce additional overhead, resulting in less benefits=
 from=20
the bandwidth-saving point of view. Hence, we propose a deviation from the =
tcmtf concepts, so that the access network (wireless or satellite) keeps=20
untouched the protocol stack allowing the compression of data flows through=
 ROHC (for example). The access point serving as "bridge" between=20
the access network and the second leg of the network (i.e. Internet) implem=
ents a dual stack, with PPPmux and IP tunneling techniques, to multiplex an=
d tunnel=20
the compressed flows coming from the access network. The final destination =
will obviously implement a stack including the three tcmtf ingredients (com=
pression,=20
multiplexing, tunneling).

The following diagram illustrates the idea: A wireless Node A delivers data=
 to Node B though the wireless access networks and Internet.
As this idea substantially deviates from the concepts presented in draft-sa=
ldana-tsvwg-tcmtf-03, we propose to dedicate an additional I-D=20
to this idea, where implications on mobility and security should be address=
ed as well.

What is your opinion?

Best Regards,

Tomaso
 =20
											         Node B
											        +------------+
Node A                                                                   		=
				        | Appl.         |
+------------ +                                                            =
						        +------------+
| Appl.         |                                                          =
          						        | TCP/UDP |
+------------+                                                             =
       						        +------------+
| TCP/UDP |                                                         Access =
Point                       			        |        IP        |
+------------+                                                       +-----=
------------------------+                     		        +------------+
|         IP       |                                                       =
 |       Relay                              |                   		        |=
   ROHC      |  =20
+------------+                                                        +----=
------------------------+                     		        +------------+
|  ROHC       |                                                       |    =
                    |  PPPmux   |                      		        |  PPPmux =
|
+------------+                                                       |  Enc=
aps         +------------+                    		        +------------+
| Encaps     |                                                        | 	  =
         |  IPtunn.     |                                                  =
 |  IPtunn.  |
+------------+		                                 +---------------+---------=
---+                      		        +------------+
|  L2/L1       |		                                 |  L2/L1           |  L2=
/L1         |                   		        |  L2/L1       |
+------------+                                                        +----=
-----------+------------+                      		        +------------+
|					 |                                                |			        |	=09
|<------Wireless Access network-------->|                                  =
              |<------Internet----------->|
|        (WLAN, Satellite, ...)       		 |                   		    |		     =
                   |



------------------------=20
Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR)=20
German Aerospace Center=20
Institute of Communications and Navigation | Satellite Networks | Oberpfaff=
enhofen | 82234 Wessling | Germany=20
Tomaso de Cola, Ph.D.=20
Telefon +49 8153 28-2156 | Telefax=A0 +49 8153 28-2844 | tomaso.decola@dlr.=
de=20
http://www.dlr.de/kn/institut/abteilungen/san=20


From jsaldana@unizar.es  Mon Nov 19 11:49:54 2012
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9FA821F8667 for <tcmtf@ietfa.amsl.com>; Mon, 19 Nov 2012 11:49:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.392
X-Spam-Level: 
X-Spam-Status: No, score=-5.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 784zzQ-a05GJ for <tcmtf@ietfa.amsl.com>; Mon, 19 Nov 2012 11:49:53 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 742FA21F85E6 for <tcmtf@ietf.org>; Mon, 19 Nov 2012 11:49:53 -0800 (PST)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id qAJJnidr020347; Mon, 19 Nov 2012 20:49:45 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <Tomaso.deCola@dlr.de>, <tcmtf@ietf.org>
References: <1A39DCC13AF3C14B83CD74124D4DCFC30BE89012@dlrexmbx02.intra.dlr.de>
In-Reply-To: <1A39DCC13AF3C14B83CD74124D4DCFC30BE89012@dlrexmbx02.intra.dlr.de>
Date: Mon, 19 Nov 2012 20:49:54 +0100
Organization: Universidad de Zaragoza
Message-ID: <001001cdc68f$0c490f30$24db2d90$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQNsFSdb9vfVIV3n8SSg+Pirs/v/15S08blw
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Matteo.Berioli@dlr.de, Hartmut.Brandt@dlr.de
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2012 19:49:54 -0000

Tomaso,

If I understand well, the idea is that tcmtf is not used in the =
satellite
link, but only  in the "Internet" part. So the "Access Point" does not =
need
to decompress the ROHC headers.

I think that the key question is now: can this be included in the =
current
draft-saldana-tsvwg-tcmtf-03 of tcmtf or would it require a specific =
draft?

You say that the idea is different from the concepts in
draft-saldana-tsvwg-tcmtf-03. If you could provide some reasons =
supporting
this, it would be fine, I think.

We also need feedback from the list in order to set this clear.

Thank you very much,

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Tomaso.deCola@dlr.de
> Enviado el: viernes, 16 de noviembre de 2012 16:31
> Para: tcmtf@ietf.org
> CC: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de;
> Hartmut.Brandt@dlr.de; jsaldana@unizar.es
> Asunto: [tcmtf] Some thoughts about new scenarios for tcmtf
>=20
>=20
> Dear All,
>=20
> As discussed some time ago, satellite and wireless access network can =
be
> attractive network scenarios where tcmtf principles can be exploited.
> However, usual wireless and satellite encapsulation protocol (between =
IP
> and lower layers) already provide means to multiplexing and =
"tunneling"
> compressed flows.
> In this respect, the application of tcmtf in these scenarios is less
attractive,
> as it would introduce additional overhead, resulting in less benefits =
from
> the bandwidth-saving point of view. Hence, we propose a deviation from
> the tcmtf concepts, so that the access network (wireless or satellite)
keeps
> untouched the protocol stack allowing the compression of data flows
> through ROHC (for example). The access point serving as "bridge" =
between
> the access network and the second leg of the network (i.e. Internet)
> implements a dual stack, with PPPmux and IP tunneling techniques, to
> multiplex and tunnel the compressed flows coming from the access
> network. The final destination will obviously implement a stack =
including
> the three tcmtf ingredients (compression, multiplexing, tunneling).
>=20
> The following diagram illustrates the idea: A wireless Node A delivers
data
> to Node B though the wireless access networks and Internet.
> As this idea substantially deviates from the concepts presented in =
draft-
> saldana-tsvwg-tcmtf-03, we propose to dedicate an additional I-D to =
this
> idea, where implications on mobility and security should be addressed =
as
> well.
>=20
> What is your opinion?
>=20
> Best Regards,
>=20
> Tomaso
>=20
>=20
> 	         Node B
>=20
> 	        +------------+
> Node A
> 	        | Appl.         |
> +------------ +
> 	        +------------+
> | Appl.         |
> 		        | TCP/UDP |
> +------------+
>=20
> +------------+ +------------+
> | TCP/UDP |                                                         =
Access
Point
> 	        |        IP        |
> +------------+
+-----------------------------+
> 	        +------------+
> |         IP       |
|       Relay                              |
> 	        |   ROHC      |
> +------------+
+----------------------------+
> 	        +------------+
> |  ROHC       |                                                       =
|
|  PPPmux   |
> 	        |  PPPmux |
> +------------+                                                       |
Encaps         +------------+
> 	        +------------+
> | Encaps     |                                                        =
|
|  IPtunn.     |
> |  IPtunn.  |
> +------------+
+---------------+------------+
> 	        +------------+
> |  L2/L1       |		                                 |  L2/L1
|  L2/L1         |
> 	        |  L2/L1       |
> +------------+
+---------------+------------+
> 	        +------------+
> |					 |
|
> 	        |
> |<------Wireless Access network-------->|
|<------
> Internet----------->|
> |        (WLAN, Satellite, ...)       		 |
|
> |
>=20
>=20
>=20
> ------------------------
> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace =
Center
> Institute of Communications and Navigation | Satellite Networks |
> Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D.
> Telefon +49 8153 28-2156 | Telefax=A0 +49 8153 28-2844 |
> tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
>=20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From fpb@tid.es  Tue Nov 20 01:29:26 2012
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DFB321F8434 for <tcmtf@ietfa.amsl.com>; Tue, 20 Nov 2012 01:29:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qt8S0QJoYQxW for <tcmtf@ietfa.amsl.com>; Tue, 20 Nov 2012 01:29:25 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id EC44721F8431 for <tcmtf@ietf.org>; Tue, 20 Nov 2012 01:29:23 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MDS006Q350P1H@tid.hi.inet> for tcmtf@ietf.org; Tue, 20 Nov 2012 10:29:22 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 64.AC.05494.27D4BA05; Tue, 20 Nov 2012 10:29:22 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MDS006R550X1H@tid.hi.inet> for tcmtf@ietf.org; Tue, 20 Nov 2012 10:29:22 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.64]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Tue, 20 Nov 2012 10:28:45 +0100
Date: Tue, 20 Nov 2012 09:29:21 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <001001cdc68f$0c490f30$24db2d90$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A2528219DF@EX10-MB2-MAD.hi.inet>
Content-id: <584EFF939354D9419D5FE68DA10D3B15@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [tcmtf] Some thoughts about new scenarios for tcmtf
Thread-index: Ac3EDOy4duakoHOCR7KDbQibMeqaCQCeb0QAAB638AA=
user-agent: Microsoft-MacOutlook/14.2.4.120824
X-AuditID: 0a5f4e69-b7fc06d000001576-20-50ab4d72a4aa
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHKsWRmVeSWpSXmKPExsXCFe9nqFvkuzrA4OE+cYtdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoEr4/PKf2wFqw0rpk+6z97AuEmli5GTQ0LARKJ9Zx8LhC0mceHe erYuRi4OIYFtjBJrTvSzQzg/GCWu/prHCuFMY5T4c2gZUAsHB4uAqsSKz4wg3WwCWhKn764C myQs4CBx5PQ1sBJOAQuJr7tSIBYoSPw595gFZIyIQDOjxMf9D9hBapgF0iQef2AHqeEV8JY4 dLgDbCSzgJnE7UML2SDighI/Jt9jgYjrSPR+/8YMYYtLNLfehIprSzx5d4EVxGYEeub7qTVM ILaIgKPE6YPdLBC2lUTXmWtg80UF9CQW7D7IDHGbgMSSPeehbFGJl4//sU5glJiF5IxZSM6Y heSMWUjOmIXkjAWMrKsYxYqTijLTM0pyEzNz0g2M9DIy9TLzUks2MUKiLnMH4/KdKocYBTgY lXh4PW6vDBBiTSwrrsw9xCjJwaQkytvlsDpAiC8pP6UyI7E4I76oNCe1+BCjBAezkggvpw9Q jjclsbIqtSgfJiXDwaEkwfvRGyglWJSanlqRlpkDTC0waSYOTpB2HqD2LyA1vMUFibnFmekQ +VOM2hxzDrU/YeTY9qnrCaMQS15+XqqUOK8CyCYBkNKM0jy4aa8YxYHOFuZ9DjKIB5go4ea8 AlrBBLQi3gVsRUkiQkqqgVHYnXsWr9/StMvLGEWvTRf88j/ruOpypUXiOpyXzj2LatWfVtxu rGGQyaRU//Jows8r3kHPN/o8n5+0b7ZAoLpv8IqvCoKZk55fMzG7MS2m/Lh/9/KM+Xzbg363 fjeeJiCyOu6O6BcZH/dVNzNPBX5yYTZfeeXWgrIq/kzWZN15qkY38is/vFViKc5INNRiLipO BACp0C1vUQMAAA==
Cc: "Matteo.Berioli@dlr.de" <Matteo.Berioli@dlr.de>, "Hartmut.Brandt@dlr.de" <Hartmut.Brandt@dlr.de>
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 09:29:26 -0000

Hi Tomaso, Jose,

        I=B4m afraid I=B4m not able to view properly you ASCII picture, but=
 if I=B4m
not misunderstanding you, you are proposing to have a header compression
(ROHC) end to end, while having multiplexing and tunneling after the
satellite/wireless link (through the LAN with several layer 3 hops or
through the Internet). So Jose, I think Tomaso is not proposing to
decompress ROCH in the access point, but in the Node B.
        Do you think that this would be more interesting than using TCMTF e=
2e?,
given that the AP will have to de-encapsulate the existing
multiplexing/tunneling method in wireless/satellite links, and encapsulate
using TCMTF in the other side. In terms of bandwidth for sure, but how
much? Do it compensate in terms of processing capacity?

Regards,

Fernando Pascual Blanco
Telef=F3nica Global Resources
Network Automation and Dynamization
TECHNOLOGY PEOPLE GROUP
F +34913128779
M +34682005168
fpb@tid.es




On 19/11/12 20:49, "Jose Saldana" <jsaldana@unizar.es> wrote:

>Tomaso,
>
>If I understand well, the idea is that tcmtf is not used in the satellite
>link, but only  in the "Internet" part. So the "Access Point" does not
>need
>to decompress the ROHC headers.
>
>I think that the key question is now: can this be included in the current
>draft-saldana-tsvwg-tcmtf-03 of tcmtf or would it require a specific
>draft?
>
>You say that the idea is different from the concepts in
>draft-saldana-tsvwg-tcmtf-03. If you could provide some reasons supporting
>this, it would be fine, I think.
>
>We also need feedback from the list in order to set this clear.
>
>Thank you very much,
>
>Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Tomaso.deCola@dlr.de
>> Enviado el: viernes, 16 de noviembre de 2012 16:31
>> Para: tcmtf@ietf.org
>> CC: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de;
>> Hartmut.Brandt@dlr.de; jsaldana@unizar.es
>> Asunto: [tcmtf] Some thoughts about new scenarios for tcmtf
>>
>>
>> Dear All,
>>
>> As discussed some time ago, satellite and wireless access network can be
>> attractive network scenarios where tcmtf principles can be exploited.
>> However, usual wireless and satellite encapsulation protocol (between IP
>> and lower layers) already provide means to multiplexing and "tunneling"
>> compressed flows.
>> In this respect, the application of tcmtf in these scenarios is less
>attractive,
>> as it would introduce additional overhead, resulting in less benefits
>>from
>> the bandwidth-saving point of view. Hence, we propose a deviation from
>> the tcmtf concepts, so that the access network (wireless or satellite)
>keeps
>> untouched the protocol stack allowing the compression of data flows
>> through ROHC (for example). The access point serving as "bridge" between
>> the access network and the second leg of the network (i.e. Internet)
>> implements a dual stack, with PPPmux and IP tunneling techniques, to
>> multiplex and tunnel the compressed flows coming from the access
>> network. The final destination will obviously implement a stack
>>including
>> the three tcmtf ingredients (compression, multiplexing, tunneling).
>>
>> The following diagram illustrates the idea: A wireless Node A delivers
>data
>> to Node B though the wireless access networks and Internet.
>> As this idea substantially deviates from the concepts presented in
>>draft-
>> saldana-tsvwg-tcmtf-03, we propose to dedicate an additional I-D to this
>> idea, where implications on mobility and security should be addressed as
>> well.
>>
>> What is your opinion?
>>
>> Best Regards,
>>
>> Tomaso
>>
>>
>>               Node B
>>
>>              +------------+
>> Node A
>>              | Appl.         |
>> +------------ +
>>              +------------+
>> | Appl.         |
>>                      | TCP/UDP |
>> +------------+
>>
>> +------------+ +------------+
>> | TCP/UDP |
>>Access
>Point
>>              |        IP        |
>> +------------+
>+-----------------------------+
>>              +------------+
>> |         IP       |
>|       Relay                              |
>>              |   ROHC      |
>> +------------+
>+----------------------------+
>>              +------------+
>> |  ROHC       |                                                       |
>|  PPPmux   |
>>              |  PPPmux |
>> +------------+                                                       |
>Encaps         +------------+
>>              +------------+
>> | Encaps     |                                                        |
>|  IPtunn.     |
>> |  IPtunn.  |
>> +------------+
>+---------------+------------+
>>              +------------+
>> |  L2/L1       |                                              |  L2/L1
>|  L2/L1         |
>>              |  L2/L1       |
>> +------------+
>+---------------+------------+
>>              +------------+
>> |                                     |
>|
>>              |
>> |<------Wireless Access network-------->|
>|<------
>> Internet----------->|
>> |        (WLAN, Satellite, ...)                       |
>|
>> |
>>
>>
>>
>> ------------------------
>> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace Cente=
r
>> Institute of Communications and Navigation | Satellite Networks |
>> Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D.
>> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
>> tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From Tomaso.deCola@dlr.de  Tue Nov 20 04:08:23 2012
Return-Path: <Tomaso.deCola@dlr.de>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DEBA21F86A2 for <tcmtf@ietfa.amsl.com>; Tue, 20 Nov 2012 04:08:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.32
X-Spam-Level: 
X-Spam-Status: No, score=-9.32 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jN6KnARc0Zh8 for <tcmtf@ietfa.amsl.com>; Tue, 20 Nov 2012 04:08:22 -0800 (PST)
Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.32]) by ietfa.amsl.com (Postfix) with ESMTP id BCAAD21F8687 for <tcmtf@ietf.org>; Tue, 20 Nov 2012 04:08:21 -0800 (PST)
Received: from DLREXHUB02.intra.dlr.de (172.21.152.140) by dlrexedge01.dlr.de (172.21.163.100) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 20 Nov 2012 13:07:56 +0100
Received: from DLREXMBX02.intra.dlr.de ([fe80::8cc6:b83e:ddc1:4e8b]) by dlrexhub02.intra.dlr.de ([::1]) with mapi id 14.02.0318.004; Tue, 20 Nov 2012 13:07:58 +0100
From: <Tomaso.deCola@dlr.de>
To: <fpb@tid.es>
Thread-Topic: [tcmtf] Some thoughts about new scenarios for tcmtf
Thread-Index: Ac3EDOy4duakoHOCR7KDbQibMeqaCQCeb0QAAB638AAAA5CPUA==
Date: Tue, 20 Nov 2012 12:07:58 +0000
Message-ID: <1A39DCC13AF3C14B83CD74124D4DCFC30BE895C2@dlrexmbx02.intra.dlr.de>
References: <001001cdc68f$0c490f30$24db2d90$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2528219DF@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A2528219DF@EX10-MB2-MAD.hi.inet>
Accept-Language: it-IT, de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.247.173.215]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tcmtf@ietf.org, Matteo.Berioli@dlr.de, Hartmut.Brandt@dlr.de, jsaldana@unizar.es
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 12:08:23 -0000

Hi Fernando,

Yes you are right, the basic idea it to enable RoHC end-to-end (or even in =
a subpart of the whole network) and using tcmtf tunneling and multiplexing =
features only in the last segment of the network (e.g., from the AP to the =
end-users).
The point is that the Access Point, which can be regarded as a gateway in s=
atellite networks, has to de-capsulate anyway the IP datagrams incoming ove=
r the satellite link. As such, I don't see much processing complexity on th=
is node. On the other hand, the use of tcmtf on an e2e basis in this scenar=
io is not really efficient, because the tunneling-multiplexing functions ar=
e in fact already provided by the encapsulation protocol. Over the satellit=
e/wireless link.=20
With this I don't mean that e2e tcmtf is never profitable, but the scenario=
s that include satellite/wireless access network certainly require an "adap=
tation" of tcmtf concepts, as described in my proposal.=20

Regards,

Tomaso




------------------------=20
Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR)=20
German Aerospace Center=20
Institute of Communications and Navigation | Satellite Networks | Oberpfaff=
enhofen | 82234 Wessling | Germany=20
Tomaso de Cola, Ph.D.=20
Telefon +49 8153 28-2156 | Telefax=A0 +49 8153 28-2844 | tomaso.decola@dlr.=
de=20
http://www.dlr.de/kn/institut/abteilungen/san=20

-----Original Message-----
From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]=20
Sent: Tuesday, November 20, 2012 10:29 AM
To: jsaldana@unizar.es; Cola, Tomaso de; tcmtf@ietf.org
Cc: Berioli, Matteo; Brandt, Hartmut
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf

Hi Tomaso, Jose,

        I=B4m afraid I=B4m not able to view properly you ASCII picture, but=
 if I=B4m not misunderstanding you, you are proposing to have a header comp=
ression
(ROHC) end to end, while having multiplexing and tunneling after the satell=
ite/wireless link (through the LAN with several layer 3 hops or through the=
 Internet). So Jose, I think Tomaso is not proposing to decompress ROCH in =
the access point, but in the Node B.
        Do you think that this would be more interesting than using TCMTF e=
2e?, given that the AP will have to de-encapsulate the existing multiplexin=
g/tunneling method in wireless/satellite links, and encapsulate using TCMTF=
 in the other side. In terms of bandwidth for sure, but how much? Do it com=
pensate in terms of processing capacity?

Regards,

Fernando Pascual Blanco
Telef=F3nica Global Resources
Network Automation and Dynamization
TECHNOLOGY PEOPLE GROUP
F +34913128779
M +34682005168
fpb@tid.es




On 19/11/12 20:49, "Jose Saldana" <jsaldana@unizar.es> wrote:

>Tomaso,
>
>If I understand well, the idea is that tcmtf is not used in the=20
>satellite link, but only  in the "Internet" part. So the "Access Point"=20
>does not need to decompress the ROHC headers.
>
>I think that the key question is now: can this be included in the=20
>current
>draft-saldana-tsvwg-tcmtf-03 of tcmtf or would it require a specific=20
>draft?
>
>You say that the idea is different from the concepts in=20
>draft-saldana-tsvwg-tcmtf-03. If you could provide some reasons=20
>supporting this, it would be fine, I think.
>
>We also need feedback from the list in order to set this clear.
>
>Thank you very much,
>
>Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre=20
>> de Tomaso.deCola@dlr.de Enviado el: viernes, 16 de noviembre de 2012=20
>> 16:31
>> Para: tcmtf@ietf.org
>> CC: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de;=20
>> Hartmut.Brandt@dlr.de; jsaldana@unizar.es
>> Asunto: [tcmtf] Some thoughts about new scenarios for tcmtf
>>
>>
>> Dear All,
>>
>> As discussed some time ago, satellite and wireless access network can=20
>> be attractive network scenarios where tcmtf principles can be exploited.
>> However, usual wireless and satellite encapsulation protocol (between=20
>> IP and lower layers) already provide means to multiplexing and "tunnelin=
g"
>> compressed flows.
>> In this respect, the application of tcmtf in these scenarios is less
>attractive,
>> as it would introduce additional overhead, resulting in less benefits=20
>>from  the bandwidth-saving point of view. Hence, we propose a=20
>>deviation from  the tcmtf concepts, so that the access network=20
>>(wireless or satellite)
>keeps
>> untouched the protocol stack allowing the compression of data flows =20
>>through ROHC (for example). The access point serving as "bridge"=20
>>between  the access network and the second leg of the network (i.e.=20
>>Internet)  implements a dual stack, with PPPmux and IP tunneling=20
>>techniques, to  multiplex and tunnel the compressed flows coming from=20
>>the access  network. The final destination will obviously implement a=20
>>stack including  the three tcmtf ingredients (compression,=20
>>multiplexing, tunneling).
>>
>> The following diagram illustrates the idea: A wireless Node A=20
>> delivers
>data
>> to Node B though the wireless access networks and Internet.
>> As this idea substantially deviates from the concepts presented in
>>draft-
>> saldana-tsvwg-tcmtf-03, we propose to dedicate an additional I-D to=20
>>this  idea, where implications on mobility and security should be=20
>>addressed as  well.
>>
>> What is your opinion?
>>
>> Best Regards,
>>
>> Tomaso
>>
>>
>>               Node B
>>
>>              +------------+
>> Node A
>>              | Appl.         |
>> +------------ +
>>              +------------+
>> | Appl.         |
>>                      | TCP/UDP |
>> +------------+
>>
>> +------------+ +------------+
>> | TCP/UDP |
>>Access
>Point
>>              |        IP        |
>> +------------+
>+-----------------------------+
>>              +------------+
>> |         IP       |
>|       Relay                              |
>>              |   ROHC      |
>> +------------+
>+----------------------------+
>>              +------------+
>> |  ROHC       |                                                       |
>|  PPPmux   |
>>              |  PPPmux |
>> +------------+                                                      =20
>> +------------+ |
>Encaps         +------------+
>>              +------------+
>> | Encaps     |                                                        |
>|  IPtunn.     |
>> |  IPtunn.  |
>> +------------+
>+---------------+------------+
>>              +------------+
>> |  L2/L1       |                                              |  L2/L1
>|  L2/L1         |
>>              |  L2/L1       |
>> +------------+
>+---------------+------------+
>>              +------------+
>> |                                     |
>|
>>              |
>> |<------Wireless Access network-------->|
>|<------
>> Internet----------->|
>> |        (WLAN, Satellite, ...)                       |
>|
>> |
>>
>>
>>
>> ------------------------
>> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace=20
>> Center Institute of Communications and Navigation | Satellite=20
>> Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, P=
h.D.
>> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |=20
>> tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From fpb@tid.es  Tue Nov 20 05:48:55 2012
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0DAB21F8559 for <tcmtf@ietfa.amsl.com>; Tue, 20 Nov 2012 05:48:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6VSiT2Gt1FNk for <tcmtf@ietfa.amsl.com>; Tue, 20 Nov 2012 05:48:54 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id A479321F8557 for <tcmtf@ietf.org>; Tue, 20 Nov 2012 05:48:53 -0800 (PST)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MDS006G9H1ANF@tid.hi.inet> for tcmtf@ietf.org; Tue, 20 Nov 2012 14:48:52 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id B0.C0.03143.44A8BA05; Tue, 20 Nov 2012 14:48:52 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MDS006HPH1GNF@tid.hi.inet> for tcmtf@ietf.org; Tue, 20 Nov 2012 14:48:52 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.64]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Tue, 20 Nov 2012 14:48:51 +0100
Date: Tue, 20 Nov 2012 13:48:52 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <1A39DCC13AF3C14B83CD74124D4DCFC30BE895C2@dlrexmbx02.intra.dlr.de>
X-Originating-IP: [10.95.64.115]
To: "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>
Message-id: <F5EDC35DF914C1428C28E149F10463A252822CEA@EX10-MB2-MAD.hi.inet>
Content-id: <4FF7EE74B2AE564FB54373C39C3BB41A@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Some thoughts about new scenarios for tcmtf
Thread-index: Ac3EDOy4duakoHOCR7KDbQibMeqaCQCeb0QAAB638AAAA5CPUAAFf40A
user-agent: Microsoft-MacOutlook/14.2.4.120824
X-AuditID: 0a5f4068-b7f746d000000c47-34-50ab8a44c72d
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGKsWRmVeSWpSXmKPExsXCFe/ApevStTrA4NYeGYtdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoErY8/+ucwFMzwqlj6+w9TA+Mq8i5GTQ0LARGLL3yXMELaYxIV7 69m6GLk4hAQ2MEqcv3mPBcL5wSjxaO42KGcjo8Ttn0/AWlgEVCWuXG8Fs9kEtCRO313FAmIL CzhIHDl9DczmFPCXOL1qPivECgWJP+ceA8U5OEQEDCUe7JECmckssI1RYnnnZrB6XgFviSub rjOC2MwCZhK7/55hhIgLSvyYfI8FIq4j0fv9GzOELS7R3HoTKq4t8eTdBbBdjAKyEu/mQ+wV EXCUOH2wmwXCdpNYdeoMO4gtKqAnsWD3Qaj3BSSW7DkPZYtKvHz8j3UCo8QsJGfMQnLGLCRn zEJyxiwkZyxgZF3FKFacVJSZnlGSm5iZk25gqJeRqZeZl1qyiRESeRk7GJfvVDnEKMDBqMTD 63F7ZYAQa2JZcWXuIUZJDiYlUV67ttUBQnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR44wuBcrwp iZVVqUX5MCkZDg4lCd7gTqCUYFFqempFWmYOML3ApJk4OEHaeYDa73WAtBcXJOYWZ6ZD5E8x GnLMOdT+hJFj26cuINlxqPsJoxBLXn5eqpQ4rxbIUAGQhozSPLiZrxjFgY4X5nUDyfIAEyfc tFdAi5hA7nQBW1SSiJCSamBUTFe2NzGdcEvK7/3H4NZa7bX6ZT3GS8K+K36X2v/c8jtXztqD /8xMOWe2Rp1LV09zP7ai9HTpm7T6P28SrgSXRZapFMxrdd7B7xstUeTzn822WijXyyfjjkod t/K3tHPvBHvCLHT9teZbak7Z8zVn7RKlU9OuXpozobNxhd7KW9yMIfmR5kosxRmJhlrMRcWJ AOcVNplZAwAA
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, "Matteo.Berioli@dlr.de" <Matteo.Berioli@dlr.de>, "Hartmut.Brandt@dlr.de" <Hartmut.Brandt@dlr.de>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 13:48:56 -0000

Hi Tomaso,

        Although ROHC is end-to-end, headers will need to be decompressed w=
ithin
the AP in order to know where to send the packets (for example whether to
send the packets through one TCMTF tunnel or another). The benefit of
tunnel packets while compressing them (as TCMTF does) is not decompressing
headers in every hop. So, the adaptation you are proposing is to apply
TCMTF concepts out of the satellite/wireless links, do you?

Regards,

Fernando Pascual Blanco
Telef=F3nica Global Resources
Network Automation and Dynamization
TECHNOLOGY PEOPLE GROUP
F +34913128779
M +34682005168
fpb@tid.es




On 20/11/12 13:07, "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de> wrote:

>Hi Fernando,
>
>Yes you are right, the basic idea it to enable RoHC end-to-end (or even
>in a subpart of the whole network) and using tcmtf tunneling and
>multiplexing features only in the last segment of the network (e.g., from
>the AP to the end-users).
>The point is that the Access Point, which can be regarded as a gateway in
>satellite networks, has to de-capsulate anyway the IP datagrams incoming
>over the satellite link. As such, I don't see much processing complexity
>on this node. On the other hand, the use of tcmtf on an e2e basis in this
>scenario is not really efficient, because the tunneling-multiplexing
>functions are in fact already provided by the encapsulation protocol.
>Over the satellite/wireless link.
>With this I don't mean that e2e tcmtf is never profitable, but the
>scenarios that include satellite/wireless access network certainly
>require an "adaptation" of tcmtf concepts, as described in my proposal.
>
>Regards,
>
>Tomaso
>
>
>
>
>------------------------
>Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR)
>German Aerospace Center
>Institute of Communications and Navigation | Satellite Networks |
>Oberpfaffenhofen | 82234 Wessling | Germany
>Tomaso de Cola, Ph.D.
>Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
>tomaso.decola@dlr.de
>http://www.dlr.de/kn/institut/abteilungen/san
>
>-----Original Message-----
>From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>Sent: Tuesday, November 20, 2012 10:29 AM
>To: jsaldana@unizar.es; Cola, Tomaso de; tcmtf@ietf.org
>Cc: Berioli, Matteo; Brandt, Hartmut
>Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
>
>Hi Tomaso, Jose,
>
>        I=B4m afraid I=B4m not able to view properly you ASCII picture, bu=
t
>if I=B4m not misunderstanding you, you are proposing to have a header
>compression
>(ROHC) end to end, while having multiplexing and tunneling after the
>satellite/wireless link (through the LAN with several layer 3 hops or
>through the Internet). So Jose, I think Tomaso is not proposing to
>decompress ROCH in the access point, but in the Node B.
>        Do you think that this would be more interesting than using TCMTF
>e2e?, given that the AP will have to de-encapsulate the existing
>multiplexing/tunneling method in wireless/satellite links, and
>encapsulate using TCMTF in the other side. In terms of bandwidth for
>sure, but how much? Do it compensate in terms of processing capacity?
>
>Regards,
>
>Fernando Pascual Blanco
>Telef=F3nica Global Resources
>Network Automation and Dynamization
>TECHNOLOGY PEOPLE GROUP
>F +34913128779
>M +34682005168
>fpb@tid.es
>
>
>
>
>On 19/11/12 20:49, "Jose Saldana" <jsaldana@unizar.es> wrote:
>
>>Tomaso,
>>
>>If I understand well, the idea is that tcmtf is not used in the
>>satellite link, but only  in the "Internet" part. So the "Access Point"
>>does not need to decompress the ROHC headers.
>>
>>I think that the key question is now: can this be included in the
>>current
>>draft-saldana-tsvwg-tcmtf-03 of tcmtf or would it require a specific
>>draft?
>>
>>You say that the idea is different from the concepts in
>>draft-saldana-tsvwg-tcmtf-03. If you could provide some reasons
>>supporting this, it would be fine, I think.
>>
>>We also need feedback from the list in order to set this clear.
>>
>>Thank you very much,
>>
>>Jose
>>
>>> -----Mensaje original-----
>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>>> de Tomaso.deCola@dlr.de Enviado el: viernes, 16 de noviembre de 2012
>>> 16:31
>>> Para: tcmtf@ietf.org
>>> CC: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de;
>>> Hartmut.Brandt@dlr.de; jsaldana@unizar.es
>>> Asunto: [tcmtf] Some thoughts about new scenarios for tcmtf
>>>
>>>
>>> Dear All,
>>>
>>> As discussed some time ago, satellite and wireless access network can
>>> be attractive network scenarios where tcmtf principles can be
>>>exploited.
>>> However, usual wireless and satellite encapsulation protocol (between
>>> IP and lower layers) already provide means to multiplexing and
>>>"tunneling"
>>> compressed flows.
>>> In this respect, the application of tcmtf in these scenarios is less
>>attractive,
>>> as it would introduce additional overhead, resulting in less benefits
>>>from  the bandwidth-saving point of view. Hence, we propose a
>>>deviation from  the tcmtf concepts, so that the access network
>>>(wireless or satellite)
>>keeps
>>> untouched the protocol stack allowing the compression of data flows
>>>through ROHC (for example). The access point serving as "bridge"
>>>between  the access network and the second leg of the network (i.e.
>>>Internet)  implements a dual stack, with PPPmux and IP tunneling
>>>techniques, to  multiplex and tunnel the compressed flows coming from
>>>the access  network. The final destination will obviously implement a
>>>stack including  the three tcmtf ingredients (compression,
>>>multiplexing, tunneling).
>>>
>>> The following diagram illustrates the idea: A wireless Node A
>>> delivers
>>data
>>> to Node B though the wireless access networks and Internet.
>>> As this idea substantially deviates from the concepts presented in
>>>draft-
>>> saldana-tsvwg-tcmtf-03, we propose to dedicate an additional I-D to
>>>this  idea, where implications on mobility and security should be
>>>addressed as  well.
>>>
>>> What is your opinion?
>>>
>>> Best Regards,
>>>
>>> Tomaso
>>>
>>>
>>>               Node B
>>>
>>>              +------------+
>>> Node A
>>>              | Appl.         |
>>> +------------ +
>>>              +------------+
>>> | Appl.         |
>>>                      | TCP/UDP |
>>> +------------+
>>>
>>> +------------+ +------------+
>>> | TCP/UDP |
>>>Access
>>Point
>>>              |        IP        |
>>> +------------+
>>+-----------------------------+
>>>              +------------+
>>> |         IP       |
>>|       Relay                              |
>>>              |   ROHC      |
>>> +------------+
>>+----------------------------+
>>>              +------------+
>>> |  ROHC       |                                                       |
>>|  PPPmux   |
>>>              |  PPPmux |
>>> +------------+
>>> +------------+ |
>>Encaps         +------------+
>>>              +------------+
>>> | Encaps     |                                                        |
>>|  IPtunn.     |
>>> |  IPtunn.  |
>>> +------------+
>>+---------------+------------+
>>>              +------------+
>>> |  L2/L1       |                                              |  L2/L1
>>|  L2/L1         |
>>>              |  L2/L1       |
>>> +------------+
>>+---------------+------------+
>>>              +------------+
>>> |                                     |
>>|
>>>              |
>>> |<------Wireless Access network-------->|
>>|<------
>>> Internet----------->|
>>> |        (WLAN, Satellite, ...)                       |
>>|
>>> |
>>>
>>>
>>>
>>> ------------------------
>>> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace
>>> Center Institute of Communications and Navigation | Satellite
>>> Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola,
>>>Ph.D.
>>> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
>>> tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
>>>
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>
>>_______________________________________________
>>tcmtf mailing list
>>tcmtf@ietf.org
>>https://www.ietf.org/mailman/listinfo/tcmtf
>
>
>________________________________
>
>Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el =
enlace
>situado m=E1s abajo.
>This message is intended exclusively for its addressee. We only send and
>receive email on the basis of the terms set out at:
>http://www.tid.es/ES/PAGINAS/disclaimer.aspx


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From mramalho@cisco.com  Wed Nov 21 07:59:05 2012
Return-Path: <mramalho@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1531F21F855E for <tcmtf@ietfa.amsl.com>; Wed, 21 Nov 2012 07:59:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q34iXQKicGUg for <tcmtf@ietfa.amsl.com>; Wed, 21 Nov 2012 07:59:03 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE3721F854F for <tcmtf@ietf.org>; Wed, 21 Nov 2012 07:59:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10003; q=dns/txt; s=iport; t=1353513543; x=1354723143; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=TkYNP3wbMPmxtnpsXuPz0MoIChD0vDx5rUPCcgDB0ks=; b=TY933johkYHxayZ0UWjVqYkqnM3aQ/uMdgo3eVADrbV9V2HRDIuefLHi +L9z9mDEvkpYIf9uuvO9ZKdNdTYnY8epzRbqyDTBFD7nefjxqFBN02NqX m0Lg08MSlzraDUkeK+rNt5s8/R7vEodEc9V0V4PMs7TMk87gDsh7IKk8l 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAJL5rFCtJXG8/2dsb2JhbABEwkMWc4IeAQEBBAEBASRHCwwEAgEIEQQBAQsdBycLFAkIAQEEAQ0FCIgFC783jDQLg3dhA4gniiWTc4JvgWQXHg
X-IronPort-AV: E=McAfee;i="5400,1158,6902"; a="144878782"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-8.cisco.com with ESMTP; 21 Nov 2012 15:59:03 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id qALFx2mw017178 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 21 Nov 2012 15:59:02 GMT
Received: from xmb-rcd-x12.cisco.com ([169.254.2.114]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.001; Wed, 21 Nov 2012 09:59:02 -0600
From: "Michael Ramalho (mramalho)" <mramalho@cisco.com>
To: "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>, "fpb@tid.es" <fpb@tid.es>
Thread-Topic: [tcmtf] Some thoughts about new scenarios for tcmtf
Thread-Index: Ac3EDOy4duakoHOCR7KDbQibMeqaCQCtGlsAAByedIAABYolAAAth3sw
Date: Wed, 21 Nov 2012 15:59:02 +0000
Message-ID: <D21571530BF9644D9A443D6BD95B91030F5301BB@xmb-rcd-x12.cisco.com>
References: <001001cdc68f$0c490f30$24db2d90$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2528219DF@EX10-MB2-MAD.hi.inet> <1A39DCC13AF3C14B83CD74124D4DCFC30BE895C2@dlrexmbx02.intra.dlr.de>
In-Reply-To: <1A39DCC13AF3C14B83CD74124D4DCFC30BE895C2@dlrexmbx02.intra.dlr.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.233.248]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, "Matteo.Berioli@dlr.de" <Matteo.Berioli@dlr.de>, "Hartmut.Brandt@dlr.de" <Hartmut.Brandt@dlr.de>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 15:59:05 -0000

All,

I think Tomaso's suggestion could occur as a separate section in Jose's  dr=
aft (draft-saldana-tsvwg-tcmtf-03) for the case of where the (TCMTF) tunnel=
 endpoints use a different multiplexing layer (where Jose has "PPPMUX or ot=
her mux protocols" in the draft).

However, tunnel endpoints are hard enough to specify .. and now you would n=
eed to know if there is a relay somewhere in-between the tunnel endpoints t=
hat uses a different multiplexing technique.

In other words, you would need to know EVEN MORE about the capability of po=
ssible intermediate nodes (in this case that a relay is possible between yo=
ur TCMTF tunnel endpoints) . or perhaps decide if a relay is needed if the =
existing TCMTF tunnel endpoints do not use the same multiplexing layer (e.g=
., a "lossless transcode" function).

If we decide to add a section in Jose's draft, we would need to provide gui=
dance concerning how the endpoints are either configured or negotiated. If =
we want TCMTF to be "simple" and "just configured" (e.g., on WAN edges) . t=
hen negotiation and possible insertion/use of a relay is a pretty big compl=
ication to the document. However, we SHOULD address this concern (how tunne=
l endpoints are found, how we ensure relays remain on the end-to-end tunnel=
 path) in the document anyway!

Jose/Tomaso: Do you have thoughts on how the TCMTF endpoints negotiate the =
lower layers?

Michael Ramalho

-----Original Message-----
From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of T=
omaso.deCola@dlr.de
Sent: Tuesday, November 20, 2012 7:08 AM
To: fpb@tid.es
Cc: tcmtf@ietf.org; Matteo.Berioli@dlr.de; Hartmut.Brandt@dlr.de; jsaldana@=
unizar.es
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf

Hi Fernando,

Yes you are right, the basic idea it to enable RoHC end-to-end (or even in =
a subpart of the whole network) and using tcmtf tunneling and multiplexing =
features only in the last segment of the network (e.g., from the AP to the =
end-users).
The point is that the Access Point, which can be regarded as a gateway in s=
atellite networks, has to de-capsulate anyway the IP datagrams incoming ove=
r the satellite link. As such, I don't see much processing complexity on th=
is node. On the other hand, the use of tcmtf on an e2e basis in this scenar=
io is not really efficient, because the tunneling-multiplexing functions ar=
e in fact already provided by the encapsulation protocol. Over the satellit=
e/wireless link.=20
With this I don't mean that e2e tcmtf is never profitable, but the scenario=
s that include satellite/wireless access network certainly require an "adap=
tation" of tcmtf concepts, as described in my proposal.=20

Regards,

Tomaso

------------------------
Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace Center I=
nstitute of Communications and Navigation | Satellite Networks | Oberpfaffe=
nhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D.=20
Telefon +49 8153 28-2156 | Telefax=A0 +49 8153 28-2844 | tomaso.decola@dlr.=
de http://www.dlr.de/kn/institut/abteilungen/san=20

-----Original Message-----
From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
Sent: Tuesday, November 20, 2012 10:29 AM
To: jsaldana@unizar.es; Cola, Tomaso de; tcmtf@ietf.org
Cc: Berioli, Matteo; Brandt, Hartmut
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf

Hi Tomaso, Jose,

        I=B4m afraid I=B4m not able to view properly you ASCII picture, but=
 if I=B4m not misunderstanding you, you are proposing to have a header comp=
ression
(ROHC) end to end, while having multiplexing and tunneling after the satell=
ite/wireless link (through the LAN with several layer 3 hops or through the=
 Internet). So Jose, I think Tomaso is not proposing to decompress ROCH in =
the access point, but in the Node B.
        Do you think that this would be more interesting than using TCMTF e=
2e?, given that the AP will have to de-encapsulate the existing multiplexin=
g/tunneling method in wireless/satellite links, and encapsulate using TCMTF=
 in the other side. In terms of bandwidth for sure, but how much? Do it com=
pensate in terms of processing capacity?

Regards,

Fernando Pascual Blanco
Telef=F3nica Global Resources
Network Automation and Dynamization
TECHNOLOGY PEOPLE GROUP
F +34913128779
M +34682005168
fpb@tid.es




On 19/11/12 20:49, "Jose Saldana" <jsaldana@unizar.es> wrote:

>Tomaso,
>
>If I understand well, the idea is that tcmtf is not used in the=20
>satellite link, but only  in the "Internet" part. So the "Access Point"
>does not need to decompress the ROHC headers.
>
>I think that the key question is now: can this be included in the=20
>current
>draft-saldana-tsvwg-tcmtf-03 of tcmtf or would it require a specific=20
>draft?
>
>You say that the idea is different from the concepts in=20
>draft-saldana-tsvwg-tcmtf-03. If you could provide some reasons=20
>supporting this, it would be fine, I think.
>
>We also need feedback from the list in order to set this clear.
>
>Thank you very much,
>
>Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre=20
>> de Tomaso.deCola@dlr.de Enviado el: viernes, 16 de noviembre de 2012
>> 16:31
>> Para: tcmtf@ietf.org
>> CC: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de;=20
>> Hartmut.Brandt@dlr.de; jsaldana@unizar.es
>> Asunto: [tcmtf] Some thoughts about new scenarios for tcmtf
>>
>>
>> Dear All,
>>
>> As discussed some time ago, satellite and wireless access network can=20
>> be attractive network scenarios where tcmtf principles can be exploited.
>> However, usual wireless and satellite encapsulation protocol (between=20
>> IP and lower layers) already provide means to multiplexing and "tunnelin=
g"
>> compressed flows.
>> In this respect, the application of tcmtf in these scenarios is less
>attractive,
>> as it would introduce additional overhead, resulting in less benefits=20
>>from  the bandwidth-saving point of view. Hence, we propose a=20
>>deviation from  the tcmtf concepts, so that the access network=20
>>(wireless or satellite)
>keeps
>> untouched the protocol stack allowing the compression of data flows=20
>>through ROHC (for example). The access point serving as "bridge"
>>between  the access network and the second leg of the network (i.e.=20
>>Internet)  implements a dual stack, with PPPmux and IP tunneling=20
>>techniques, to  multiplex and tunnel the compressed flows coming from=20
>>the access  network. The final destination will obviously implement a=20
>>stack including  the three tcmtf ingredients (compression,=20
>>multiplexing, tunneling).
>>
>> The following diagram illustrates the idea: A wireless Node A=20
>> delivers
>data
>> to Node B though the wireless access networks and Internet.
>> As this idea substantially deviates from the concepts presented in
>>draft-
>> saldana-tsvwg-tcmtf-03, we propose to dedicate an additional I-D to=20
>>this  idea, where implications on mobility and security should be=20
>>addressed as  well.
>>
>> What is your opinion?
>>
>> Best Regards,
>>
>> Tomaso
>>
>>
>>               Node B
>>
>>              +------------+
>> Node A
>>              | Appl.         |
>> +------------ +
>>              +------------+
>> | Appl.         |
>>                      | TCP/UDP |
>> +------------+
>>
>> +------------+ +------------+
>> | TCP/UDP |
>>Access
>Point
>>              |        IP        |
>> +------------+
>+-----------------------------+
>>              +------------+
>> |         IP       |
>|       Relay                              |
>>              |   ROHC      |
>> +------------+
>+----------------------------+
>>              +------------+
>> |  ROHC       |                                                       |
>|  PPPmux   |
>>              |  PPPmux |
>> +------------+                                                      =20
>> +------------+ |
>Encaps         +------------+
>>              +------------+
>> | Encaps     |                                                        |
>|  IPtunn.     |
>> |  IPtunn.  |
>> +------------+
>+---------------+------------+
>>              +------------+
>> |  L2/L1       |                                              |  L2/L1
>|  L2/L1         |
>>              |  L2/L1       |
>> +------------+
>+---------------+------------+
>>              +------------+
>> |                                     |
>|
>>              |
>> |<------Wireless Access network-------->|
>|<------
>> Internet----------->|
>> |        (WLAN, Satellite, ...)                       |
>|
>> |
>>
>>
>>
>> ------------------------
>> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace=20
>> Center Institute of Communications and Navigation | Satellite=20
>> Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, P=
h.D.
>> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |=20
>> tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
_______________________________________________
tcmtf mailing list
tcmtf@ietf.org
https://www.ietf.org/mailman/listinfo/tcmtf

From fpb@tid.es  Mon Nov 26 05:59:49 2012
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86C6621F855C for <tcmtf@ietfa.amsl.com>; Mon, 26 Nov 2012 05:59:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level: 
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eLdMwqFUKBLA for <tcmtf@ietfa.amsl.com>; Mon, 26 Nov 2012 05:59:48 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id E102B21F8551 for <tcmtf@ietf.org>; Mon, 26 Nov 2012 05:59:46 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0ME300CU4LJL03@tid.hi.inet> for tcmtf@ietf.org; Mon, 26 Nov 2012 14:59:45 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 98.19.05494.1D573B05; Mon, 26 Nov 2012 14:59:45 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0ME300CTXLJK03@tid.hi.inet> for tcmtf@ietf.org; Mon, 26 Nov 2012 14:59:45 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.64]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Mon, 26 Nov 2012 14:59:44 +0100
Date: Mon, 26 Nov 2012 13:59:44 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <D21571530BF9644D9A443D6BD95B91030F5301BB@xmb-rcd-x12.cisco.com>
X-Originating-IP: [10.95.64.115]
To: "Michael Ramalho (mramalho)" <mramalho@cisco.com>, "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>
Message-id: <F5EDC35DF914C1428C28E149F10463A25282F857@EX10-MB2-MAD.hi.inet>
Content-id: <51211222EBEBB349AF60B09DA427F16A@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [tcmtf] Some thoughts about new scenarios for tcmtf
Thread-index: Ac3EDOy4duakoHOCR7KDbQibMeqaCQCeb0QAAB638AAAA5CPUAA6PJoAAPljbQA=
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4e69-b7fc06d000001576-60-50b375d1d9a6
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrAKsWRmVeSWpSXmKPExsXCFe9nqHuxdHOAwYd58ha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxt8PzawFn6MqerZMYm1gPOjexcjBISFgIrHsQGYXIyeQKSZx 4d56ti5GLg4hgW2MEq2ffrNDOD8YJdas2wjlTGOUuHl9ORtIC4uAqsT8CTNYQGw2AS2J03dX gdnCAg4SR05fA7M5BXwlZt/uZoJYoSDx59xjsLiIQJrE80WTmUCGMgvsYJR4uKKRFSTBK+At 0XlmFjOIzSxgJnHo8xpmiLigxI/J91gg4joSvd+/QdWISzS33oSKa0s8eXcBbA4j0D/fT61h gljmKHH6YDfUYj+JxltnwR4QFdCTaDt2hh3iOAGJJXvOM0PYohIvH/9jncAoMQvJGbOQnDEL yRmzkJwxC8kZCxhZVzGKFScVZaZnlOQmZuakGxjpZWTqZeallmxihERe5g7G5TtVDjEKcDAq 8fAqnN0UIMSaWFZcmXuIUZKDSUmUd1fR5gAhvqT8lMqMxOKM+KLSnNTiQ4wSHMxKIrxnvYFy vCmJlVWpRfkwKRkODiUJXtsSoJRgUWp6akVaZg4wvcCkmTg4Qdp5gNqngNTwFhck5hZnpkPk TzFqc8w51P6EkWPbp64njEIsefl5qVLivEYgpQIgpRmleXDTXjGKA50tzLsKJMsDTJZwc14B rWACWpF8fSPIipJEhJRUA+N2R/2rW05984n/7SGvzW4SHuXYnLiedS/XuY/Jz79fDDyludbf 5PFD2Tcib+uy1p4MWr/sbQ77kxSe77cmJ62K3V5v759z2neTvNLb3fX1Xn8e5ioum8Nx5b3M n2K+T2lv+CqZ/rEWyeSrL6q4ZHvR/WF0DlPKtrSARQXhNfz/eroz1MTddJRYijMSDbWYi4oT AUpNwvtTAwAA
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, "Matteo.Berioli@dlr.de" <Matteo.Berioli@dlr.de>, "Hartmut.Brandt@dlr.de" <Hartmut.Brandt@dlr.de>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 13:59:49 -0000

Hi All,

        Actually Jose proposed the idea of developing two new drafts: the
b)"Recommendations draft" and the c)"Dynamic Signaling Draft". That relay
between different tunneling, multiplexing or even compression capabilities
through the optimized path could be addressed to the c) draft as TCMTF
negotiation concepts in a multi-capability path. It should also be
mentioned in the original draft and recommended in the b) draft.
        For example, for the satellite scenario, it would not be necessary =
to
decompress ROHC within the Access Point, since it should only take packets
multiplexed and tunneled in a way (the existing and efficient
encapsulation protocols, which could also be adopted within the original
Jose=B4s draft as different tunnel and multiplex options), and
multiplex-tunnel them in another way (as Michael says, acting as a tunnel
and/or multiplex relay) without see layer 3 headers.

Regards,

Fernando Pascual Blanco
Telef=F3nica Global Resources
Network Automation and Dynamization
TECHNOLOGY PEOPLE GROUP
F +34913128779
M +34682005168
fpb@tid.es




On 21/11/12 16:59, "Michael Ramalho (mramalho)" <mramalho@cisco.com> wrote:

>All,
>
>I think Tomaso's suggestion could occur as a separate section in Jose's
>draft (draft-saldana-tsvwg-tcmtf-03) for the case of where the (TCMTF)
>tunnel endpoints use a different multiplexing layer (where Jose has
>"PPPMUX or other mux protocols" in the draft).
>
>However, tunnel endpoints are hard enough to specify .. and now you would
>need to know if there is a relay somewhere in-between the tunnel
>endpoints that uses a different multiplexing technique.
>
>In other words, you would need to know EVEN MORE about the capability of
>possible intermediate nodes (in this case that a relay is possible
>between your TCMTF tunnel endpoints) . or perhaps decide if a relay is
>needed if the existing TCMTF tunnel endpoints do not use the same
>multiplexing layer (e.g., a "lossless transcode" function).
>
>If we decide to add a section in Jose's draft, we would need to provide
>guidance concerning how the endpoints are either configured or
>negotiated. If we want TCMTF to be "simple" and "just configured" (e.g.,
>on WAN edges) . then negotiation and possible insertion/use of a relay is
>a pretty big complication to the document. However, we SHOULD address
>this concern (how tunnel endpoints are found, how we ensure relays remain
>on the end-to-end tunnel path) in the document anyway!
>
>Jose/Tomaso: Do you have thoughts on how the TCMTF endpoints negotiate
>the lower layers?
>
>Michael Ramalho
>
>-----Original Message-----
>From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of
>Tomaso.deCola@dlr.de
>Sent: Tuesday, November 20, 2012 7:08 AM
>To: fpb@tid.es
>Cc: tcmtf@ietf.org; Matteo.Berioli@dlr.de; Hartmut.Brandt@dlr.de;
>jsaldana@unizar.es
>Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
>
>Hi Fernando,
>
>Yes you are right, the basic idea it to enable RoHC end-to-end (or even
>in a subpart of the whole network) and using tcmtf tunneling and
>multiplexing features only in the last segment of the network (e.g., from
>the AP to the end-users).
>The point is that the Access Point, which can be regarded as a gateway in
>satellite networks, has to de-capsulate anyway the IP datagrams incoming
>over the satellite link. As such, I don't see much processing complexity
>on this node. On the other hand, the use of tcmtf on an e2e basis in this
>scenario is not really efficient, because the tunneling-multiplexing
>functions are in fact already provided by the encapsulation protocol.
>Over the satellite/wireless link.
>With this I don't mean that e2e tcmtf is never profitable, but the
>scenarios that include satellite/wireless access network certainly
>require an "adaptation" of tcmtf concepts, as described in my proposal.
>
>Regards,
>
>Tomaso
>
>------------------------
>Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace Center
>Institute of Communications and Navigation | Satellite Networks |
>Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D.
>Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
>tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
>
>-----Original Message-----
>From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>Sent: Tuesday, November 20, 2012 10:29 AM
>To: jsaldana@unizar.es; Cola, Tomaso de; tcmtf@ietf.org
>Cc: Berioli, Matteo; Brandt, Hartmut
>Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
>
>Hi Tomaso, Jose,
>
>        I=B4m afraid I=B4m not able to view properly you ASCII picture, bu=
t
>if I=B4m not misunderstanding you, you are proposing to have a header
>compression
>(ROHC) end to end, while having multiplexing and tunneling after the
>satellite/wireless link (through the LAN with several layer 3 hops or
>through the Internet). So Jose, I think Tomaso is not proposing to
>decompress ROCH in the access point, but in the Node B.
>        Do you think that this would be more interesting than using TCMTF
>e2e?, given that the AP will have to de-encapsulate the existing
>multiplexing/tunneling method in wireless/satellite links, and
>encapsulate using TCMTF in the other side. In terms of bandwidth for
>sure, but how much? Do it compensate in terms of processing capacity?
>
>Regards,
>
>Fernando Pascual Blanco
>Telef=F3nica Global Resources
>Network Automation and Dynamization
>TECHNOLOGY PEOPLE GROUP
>F +34913128779
>M +34682005168
>fpb@tid.es
>
>
>
>
>On 19/11/12 20:49, "Jose Saldana" <jsaldana@unizar.es> wrote:
>
>>Tomaso,
>>
>>If I understand well, the idea is that tcmtf is not used in the
>>satellite link, but only  in the "Internet" part. So the "Access Point"
>>does not need to decompress the ROHC headers.
>>
>>I think that the key question is now: can this be included in the
>>current
>>draft-saldana-tsvwg-tcmtf-03 of tcmtf or would it require a specific
>>draft?
>>
>>You say that the idea is different from the concepts in
>>draft-saldana-tsvwg-tcmtf-03. If you could provide some reasons
>>supporting this, it would be fine, I think.
>>
>>We also need feedback from the list in order to set this clear.
>>
>>Thank you very much,
>>
>>Jose
>>
>>> -----Mensaje original-----
>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>>> de Tomaso.deCola@dlr.de Enviado el: viernes, 16 de noviembre de 2012
>>> 16:31
>>> Para: tcmtf@ietf.org
>>> CC: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de;
>>> Hartmut.Brandt@dlr.de; jsaldana@unizar.es
>>> Asunto: [tcmtf] Some thoughts about new scenarios for tcmtf
>>>
>>>
>>> Dear All,
>>>
>>> As discussed some time ago, satellite and wireless access network can
>>> be attractive network scenarios where tcmtf principles can be
>>>exploited.
>>> However, usual wireless and satellite encapsulation protocol (between
>>> IP and lower layers) already provide means to multiplexing and
>>>"tunneling"
>>> compressed flows.
>>> In this respect, the application of tcmtf in these scenarios is less
>>attractive,
>>> as it would introduce additional overhead, resulting in less benefits
>>>from  the bandwidth-saving point of view. Hence, we propose a
>>>deviation from  the tcmtf concepts, so that the access network
>>>(wireless or satellite)
>>keeps
>>> untouched the protocol stack allowing the compression of data flows
>>>through ROHC (for example). The access point serving as "bridge"
>>>between  the access network and the second leg of the network (i.e.
>>>Internet)  implements a dual stack, with PPPmux and IP tunneling
>>>techniques, to  multiplex and tunnel the compressed flows coming from
>>>the access  network. The final destination will obviously implement a
>>>stack including  the three tcmtf ingredients (compression,
>>>multiplexing, tunneling).
>>>
>>> The following diagram illustrates the idea: A wireless Node A
>>> delivers
>>data
>>> to Node B though the wireless access networks and Internet.
>>> As this idea substantially deviates from the concepts presented in
>>>draft-
>>> saldana-tsvwg-tcmtf-03, we propose to dedicate an additional I-D to
>>>this  idea, where implications on mobility and security should be
>>>addressed as  well.
>>>
>>> What is your opinion?
>>>
>>> Best Regards,
>>>
>>> Tomaso
>>>
>>>
>>>               Node B
>>>
>>>              +------------+
>>> Node A
>>>              | Appl.         |
>>> +------------ +
>>>              +------------+
>>> | Appl.         |
>>>                      | TCP/UDP |
>>> +------------+
>>>
>>> +------------+ +------------+
>>> | TCP/UDP |
>>>Access
>>Point
>>>              |        IP        |
>>> +------------+
>>+-----------------------------+
>>>              +------------+
>>> |         IP       |
>>|       Relay                              |
>>>              |   ROHC      |
>>> +------------+
>>+----------------------------+
>>>              +------------+
>>> |  ROHC       |                                                       |
>>|  PPPmux   |
>>>              |  PPPmux |
>>> +------------+
>>> +------------+ |
>>Encaps         +------------+
>>>              +------------+
>>> | Encaps     |                                                        |
>>|  IPtunn.     |
>>> |  IPtunn.  |
>>> +------------+
>>+---------------+------------+
>>>              +------------+
>>> |  L2/L1       |                                              |  L2/L1
>>|  L2/L1         |
>>>              |  L2/L1       |
>>> +------------+
>>+---------------+------------+
>>>              +------------+
>>> |                                     |
>>|
>>>              |
>>> |<------Wireless Access network-------->|
>>|<------
>>> Internet----------->|
>>> |        (WLAN, Satellite, ...)                       |
>>|
>>> |
>>>
>>>
>>>
>>> ------------------------
>>> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace
>>> Center Institute of Communications and Navigation | Satellite
>>> Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola,
>>>Ph.D.
>>> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
>>> tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
>>>
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>
>>_______________________________________________
>>tcmtf mailing list
>>tcmtf@ietf.org
>>https://www.ietf.org/mailman/listinfo/tcmtf
>
>
>________________________________
>
>Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el =
enlace
>situado m=E1s abajo.
>This message is intended exclusively for its addressee. We only send and
>receive email on the basis of the terms set out at:
>http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From jsaldana@unizar.es  Mon Nov 26 09:08:52 2012
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1061721F85D0 for <tcmtf@ietfa.amsl.com>; Mon, 26 Nov 2012 09:08:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.824
X-Spam-Level: 
X-Spam-Status: No, score=-3.824 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DC_GIF_UNO_LARGO=2.275, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4, SARE_GIF_ATTACH=1.42, TVD_FW_GRAPHIC_NAME_LONG=1.08]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Zx9z6u7tqjO for <tcmtf@ietfa.amsl.com>; Mon, 26 Nov 2012 09:08:50 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id CAEEB21F8720 for <tcmtf@ietf.org>; Mon, 26 Nov 2012 09:08:49 -0800 (PST)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id qAQH8fIm030120; Mon, 26 Nov 2012 18:08:41 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <Tomaso.deCola@dlr.de>
References: <D21571530BF9644D9A443D6BD95B91030F5301BB@xmb-rcd-x12.cisco.com> <F5EDC35DF914C1428C28E149F10463A25282F857@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A25282F857@EX10-MB2-MAD.hi.inet>
Date: Mon, 26 Nov 2012 18:08:58 +0100
Organization: Universidad de Zaragoza
Message-ID: <010501cdcbf8$b98dac50$2ca904f0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0106_01CDCC01.1B548550"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKGt7/dSVoaNDY82MJFOPKEKDep35aKfYIg
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2012 17:08:52 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0106_01CDCC01.1B548550
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,=20

I am trying to get some light about this. First, let us try to know if =
the
picture is correct. If you put this in Courier letters, I think you can =
see
it correctly (I attach it as an image, just in case). Tomaso, is the =
picture
right?

Node A
Node B
+----------+
+------------+
| Appl.    |
| Appl.      |
+----------+
+------------+
| TCP/UDP  |
| TCP/UDP    |
+----------+
+------------+
|   IP     |                                  Access Point
|   IP       |
+----------+                             +----------------------+
+------------+
|  ROHC    |                             |       Relay          |
|   ROHC     |
+----------+                             +----------------------+
+------------+
|          |                             |          | PPPmux    |
|  PPPmux    |
| Encaps   |                             |  Encaps  +-----------+
+------------+
|          |                             |          |  IPtunn.  |
|  IPtunn.   |
+----------+	                         +----------+-----------+
+------------+
|  L2/L1   |                             |  L2/L1   |  L2/L1    |
|  L2/L1     |
+----------+                             +----------+-----------+
+------------+

           |                             |                      |
|
           |<--Wireless Access network-->|
|<------Internet-------->|
           |   (WLAN, Satellite, ...)    |                      |
|


So the first question is:

Tomaso, is there a single connection from Node A to Node B, or the =
Access
Point has to distinguish different flows? Are all packets travelling =
from A
to B?

If the answer is "Yes", then, as Fernando says, the AP does not need to
decompress/compress ROHC. It only needs to get a number of packets,
decapsulate them, and put them together into a multiplexed packet with
PPPMux.

I think we should first set this clear in order to advance.

Thanks,

Jose

> -----Mensaje original-----
> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> Enviado el: lunes, 26 de noviembre de 2012 15:00
> Para: Michael Ramalho (mramalho); Tomaso.deCola@dlr.de
> CC: tcmtf@ietf.org; Matteo.Berioli@dlr.de; Hartmut.Brandt@dlr.de;
> jsaldana@unizar.es
> Asunto: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
>=20
> Hi All,
>=20
>         Actually Jose proposed the idea of developing two new drafts: =
the
> b)"Recommendations draft" and the c)"Dynamic Signaling Draft". That =
relay
> between different tunneling, multiplexing or even compression =
capabilities
> through the optimized path could be addressed to the c) draft as TCMTF
> negotiation concepts in a multi-capability path. It should also be
mentioned in
> the original draft and recommended in the b) draft.
>         For example, for the satellite scenario, it would not be =
necessary
to
> decompress ROHC within the Access Point, since it should only take =
packets
> multiplexed and tunneled in a way (the existing and efficient
encapsulation
> protocols, which could also be adopted within the original Jose=B4s =
draft as
> different tunnel and multiplex options), and multiplex-tunnel them in
> another way (as Michael says, acting as a tunnel and/or multiplex =
relay)
> without see layer 3 headers.
>=20
> Regards,
>=20
> Fernando Pascual Blanco
> Telef=F3nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>=20
>=20
>=20
>=20
> On 21/11/12 16:59, "Michael Ramalho (mramalho)" <mramalho@cisco.com>
> wrote:
>=20
> >All,
> >
> >I think Tomaso's suggestion could occur as a separate section in =
Jose's
> >draft (draft-saldana-tsvwg-tcmtf-03) for the case of where the =
(TCMTF)
> >tunnel endpoints use a different multiplexing layer (where Jose has
> >"PPPMUX or other mux protocols" in the draft).
> >
> >However, tunnel endpoints are hard enough to specify .. and now you
> >would need to know if there is a relay somewhere in-between the =
tunnel
> >endpoints that uses a different multiplexing technique.
> >
> >In other words, you would need to know EVEN MORE about the capability
> >of possible intermediate nodes (in this case that a relay is possible
> >between your TCMTF tunnel endpoints) . or perhaps decide if a relay =
is
> >needed if the existing TCMTF tunnel endpoints do not use the same
> >multiplexing layer (e.g., a "lossless transcode" function).
> >
> >If we decide to add a section in Jose's draft, we would need to =
provide
> >guidance concerning how the endpoints are either configured or
> >negotiated. If we want TCMTF to be "simple" and "just configured"
> >(e.g., on WAN edges) . then negotiation and possible insertion/use of =
a
> >relay is a pretty big complication to the document. However, we =
SHOULD
> >address this concern (how tunnel endpoints are found, how we ensure
> >relays remain on the end-to-end tunnel path) in the document anyway!
> >
> >Jose/Tomaso: Do you have thoughts on how the TCMTF endpoints
> negotiate
> >the lower layers?
> >
> >Michael Ramalho
> >
> >-----Original Message-----
> >From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On =
Behalf
> >Of Tomaso.deCola@dlr.de
> >Sent: Tuesday, November 20, 2012 7:08 AM
> >To: fpb@tid.es
> >Cc: tcmtf@ietf.org; Matteo.Berioli@dlr.de; Hartmut.Brandt@dlr.de;
> >jsaldana@unizar.es
> >Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
> >
> >Hi Fernando,
> >
> >Yes you are right, the basic idea it to enable RoHC end-to-end (or =
even
> >in a subpart of the whole network) and using tcmtf tunneling and
> >multiplexing features only in the last segment of the network (e.g.,
> >from the AP to the end-users).
> >The point is that the Access Point, which can be regarded as a =
gateway
> >in satellite networks, has to de-capsulate anyway the IP datagrams
> >incoming over the satellite link. As such, I don't see much =
processing
> >complexity on this node. On the other hand, the use of tcmtf on an =
e2e
> >basis in this scenario is not really efficient, because the
> >tunneling-multiplexing functions are in fact already provided by the
> encapsulation protocol.
> >Over the satellite/wireless link.
> >With this I don't mean that e2e tcmtf is never profitable, but the
> >scenarios that include satellite/wireless access network certainly
> >require an "adaptation" of tcmtf concepts, as described in my =
proposal.
> >
> >Regards,
> >
> >Tomaso
> >
> >------------------------
> >Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace
> Center
> >Institute of Communications and Navigation | Satellite Networks |
> >Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D.
> >Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
> >tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
> >
> >-----Original Message-----
> >From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> >Sent: Tuesday, November 20, 2012 10:29 AM
> >To: jsaldana@unizar.es; Cola, Tomaso de; tcmtf@ietf.org
> >Cc: Berioli, Matteo; Brandt, Hartmut
> >Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
> >
> >Hi Tomaso, Jose,
> >
> >        I=B4m afraid I=B4m not able to view properly you ASCII =
picture, but
> >if I=B4m not misunderstanding you, you are proposing to have a header
> >compression
> >(ROHC) end to end, while having multiplexing and tunneling after the
> >satellite/wireless link (through the LAN with several layer 3 hops or
> >through the Internet). So Jose, I think Tomaso is not proposing to
> >decompress ROCH in the access point, but in the Node B.
> >        Do you think that this would be more interesting than using
> >TCMTF e2e?, given that the AP will have to de-encapsulate the =
existing
> >multiplexing/tunneling method in wireless/satellite links, and
> >encapsulate using TCMTF in the other side. In terms of bandwidth for
> >sure, but how much? Do it compensate in terms of processing capacity?
> >
> >Regards,
> >
> >Fernando Pascual Blanco
> >Telef=F3nica Global Resources
> >Network Automation and Dynamization
> >TECHNOLOGY PEOPLE GROUP
> >F +34913128779
> >M +34682005168
> >fpb@tid.es
> >
> >
> >
> >
> >On 19/11/12 20:49, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >
> >>Tomaso,
> >>
> >>If I understand well, the idea is that tcmtf is not used in the
> >>satellite link, but only  in the "Internet" part. So the "Access =
Point"
> >>does not need to decompress the ROHC headers.
> >>
> >>I think that the key question is now: can this be included in the
> >>current
> >>draft-saldana-tsvwg-tcmtf-03 of tcmtf or would it require a specific
> >>draft?
> >>
> >>You say that the idea is different from the concepts in
> >>draft-saldana-tsvwg-tcmtf-03. If you could provide some reasons
> >>supporting this, it would be fine, I think.
> >>
> >>We also need feedback from the list in order to set this clear.
> >>
> >>Thank you very much,
> >>
> >>Jose
> >>
> >>> -----Mensaje original-----
> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> nombre
> >>> de Tomaso.deCola@dlr.de Enviado el: viernes, 16 de noviembre de =
2012
> >>> 16:31
> >>> Para: tcmtf@ietf.org
> >>> CC: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de;
> >>> Hartmut.Brandt@dlr.de; jsaldana@unizar.es
> >>> Asunto: [tcmtf] Some thoughts about new scenarios for tcmtf
> >>>
> >>>
> >>> Dear All,
> >>>
> >>> As discussed some time ago, satellite and wireless access network
> >>>can  be attractive network scenarios where tcmtf principles can be
> >>>exploited.
> >>> However, usual wireless and satellite encapsulation protocol
> >>>(between  IP and lower layers) already provide means to =
multiplexing
> >>>and "tunneling"
> >>> compressed flows.
> >>> In this respect, the application of tcmtf in these scenarios is =
less
> >>attractive,
> >>> as it would introduce additional overhead, resulting in less
> >>>benefits from  the bandwidth-saving point of view. Hence, we =
propose
> >>>a deviation from  the tcmtf concepts, so that the access network
> >>>(wireless or satellite)
> >>keeps
> >>> untouched the protocol stack allowing the compression of data =
flows
> >>>through ROHC (for example). The access point serving as "bridge"
> >>>between  the access network and the second leg of the network (i.e.
> >>>Internet)  implements a dual stack, with PPPmux and IP tunneling
> >>>techniques, to  multiplex and tunnel the compressed flows coming =
from
> >>>the access  network. The final destination will obviously implement =
a
> >>>stack including  the three tcmtf ingredients (compression,
> >>>multiplexing, tunneling).
> >>>
> >>> The following diagram illustrates the idea: A wireless Node A
> >>> delivers
> >>data
> >>> to Node B though the wireless access networks and Internet.
> >>> As this idea substantially deviates from the concepts presented in
> >>>draft-
> >>> saldana-tsvwg-tcmtf-03, we propose to dedicate an additional I-D =
to
> >>>this  idea, where implications on mobility and security should be
> >>>addressed as  well.
> >>>
> >>> What is your opinion?
> >>>
> >>> Best Regards,
> >>>
> >>> Tomaso
> >>>
> >>>
> >>>               Node B
> >>>
> >>>              +------------+
> >>> Node A
> >>>              | Appl.         |
> >>> +------------ +
> >>>              +------------+
> >>> | Appl.         |
> >>>                      | TCP/UDP |
> >>> +------------+
> >>>
> >>> +------------+ +------------+
> >>> | TCP/UDP |
> >>>Access
> >>Point
> >>>              |        IP        |
> >>> +------------+
> >>+-----------------------------+
> >>>              +------------+
> >>> |         IP       |
> >>|       Relay                              |
> >>>              |   ROHC      |
> >>> +------------+
> >>+----------------------------+
> >>>              +------------+
> >>> |  ROHC       |
|
> >>|  PPPmux   |
> >>>              |  PPPmux |
> >>> +------------+
> >>> +------------+ |
> >>Encaps         +------------+
> >>>              +------------+
> >>> | Encaps     |
|
> >>|  IPtunn.     |
> >>> |  IPtunn.  |
> >>> +------------+
> >>+---------------+------------+
> >>>              +------------+
> >>> |  L2/L1       |                                              |  =
L2/L1
> >>|  L2/L1         |
> >>>              |  L2/L1       |
> >>> +------------+
> >>+---------------+------------+
> >>>              +------------+
> >>> |                                     |
> >>|
> >>>              |
> >>> |<------Wireless Access network-------->|
> >>|<------
> >>> Internet----------->|
> >>> |        (WLAN, Satellite, ...)                       |
> >>|
> >>> |
> >>>
> >>>
> >>>
> >>> ------------------------
> >>> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace
> >>>Center Institute of Communications and Navigation | Satellite
> >>>Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de
> >>>Cola, Ph.D.
> >>> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
> >>>tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
> >>>
> >>> _______________________________________________
> >>> tcmtf mailing list
> >>> tcmtf@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>
> >>_______________________________________________
> >>tcmtf mailing list
> >>tcmtf@ietf.org
> >>https://www.ietf.org/mailman/listinfo/tcmtf
> >
> >
> >________________________________
> >
> >Este mensaje se dirige exclusivamente a su destinatario. Puede
> >consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico
> >en el enlace situado m=E1s abajo.
> >This message is intended exclusively for its addressee. We only send
> >and receive email on the basis of the terms set out at:
> >http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >_______________________________________________
> >tcmtf mailing list
> >tcmtf@ietf.org
> >https://www.ietf.org/mailman/listinfo/tcmtf
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en =
el enlace
> situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send =
and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx

------=_NextPart_000_0106_01CDCC01.1B548550
Content-Type: image/gif;
	name="satellite.gif"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="satellite.gif"

R0lGODlhQwMQAXAAACH5BAEAAPwALAAAAABDAxABhwAAAAAAMwAAZgAAmQAAzAAA/wArAAArMwAr
ZgArmQArzAAr/wBVAABVMwBVZgBVmQBVzABV/wCAAACAMwCAZgCAmQCAzACA/wCqAACqMwCqZgCq
mQCqzACq/wDVAADVMwDVZgDVmQDVzADV/wD/AAD/MwD/ZgD/mQD/zAD//zMAADMAMzMAZjMAmTMA
zDMA/zMrADMrMzMrZjMrmTMrzDMr/zNVADNVMzNVZjNVmTNVzDNV/zOAADOAMzOAZjOAmTOAzDOA
/zOqADOqMzOqZjOqmTOqzDOq/zPVADPVMzPVZjPVmTPVzDPV/zP/ADP/MzP/ZjP/mTP/zDP//2YA
AGYAM2YAZmYAmWYAzGYA/2YrAGYrM2YrZmYrmWYrzGYr/2ZVAGZVM2ZVZmZVmWZVzGZV/2aAAGaA
M2aAZmaAmWaAzGaA/2aqAGaqM2aqZmaqmWaqzGaq/2bVAGbVM2bVZmbVmWbVzGbV/2b/AGb/M2b/
Zmb/mWb/zGb//5kAAJkAM5kAZpkAmZkAzJkA/5krAJkrM5krZpkrmZkrzJkr/5lVAJlVM5lVZplV
mZlVzJlV/5mAAJmAM5mAZpmAmZmAzJmA/5mqAJmqM5mqZpmqmZmqzJmq/5nVAJnVM5nVZpnVmZnV
zJnV/5n/AJn/M5n/Zpn/mZn/zJn//8wAAMwAM8wAZswAmcwAzMwA/8wrAMwrM8wrZswrmcwrzMwr
/8xVAMxVM8xVZsxVmcxVzMxV/8yAAMyAM8yAZsyAmcyAzMyA/8yqAMyqM8yqZsyqmcyqzMyq/8zV
AMzVM8zVZszVmczVzMzV/8z/AMz/M8z/Zsz/mcz/zMz///8AAP8AM/8AZv8Amf8AzP8A//8rAP8r
M/8rZv8rmf8rzP8r//9VAP9VM/9VZv9Vmf9VzP9V//+AAP+AM/+AZv+Amf+AzP+A//+qAP+qM/+q
Zv+qmf+qzP+q///VAP/VM//VZv/Vmf/VzP/V////AP//M///Zv//mf//zP///wAAAAAAAAAAAAAA
AAj/APcJHEiwoMGDCBMqXMiwocOHECNKnEixosWLGDNq3Mixo8ePIEOKHEmypMmTKFMSnMcimsqX
MGPKnEmzps2bOHPq3KmTpUueJ1meAkq0qNGjSJMqXcq06U2hTg/qo2JEoD4rPxf6lKiP0IOsUcOK
HUu2rNmzaD1OrbrvKtiEWx9OBUBXwNuZUwOE2pfPytCudX8CBvCmpcBggRfKc1Blb9rHkCNLnky5
csm8e/v+JZS4LWfChvchBmA3YT4qcTyztZmvCgwIbbF2PSJwV2lFX/fREjDUtstdCe4SpBVHF2zL
yJMrX868OdPWr2NHm137du7dvUvvyi0VdVvvN68+/1MRR/O8FY6nxlEv0Kc+RUAE5gt9MN+MaHGd
69/Pv7///3JZMV55fp2XHmrs7eMefO3RV9BcpA2Fk2blCAANVuzwJh9q+aDX4HRU0EWXXgntEl9X
qwGo4oostuiiWBRaiKGGfHHooYItQTiiYwadltpUx9l01SnvOeBXhwfGYWCDRBKSYkKD0RXci1RW
aeWVWF7mV5FH3qjekjg2+SRCCWYoHEx9uTSPCnahWN10hFhQo3YkLsROkAlmqeeefPbZZ5oKsgkn
W751JedpdPJoGnjB0FjTkIdpOBiNcwmQDAsSjgZAnQ8qktpAtATp56iklmrqcpCKJulnlIZoKaaH
iR3I6YMh7njqrbjmquuuvPbq66/ABivssMQWa+yxyNwmq+yyzDbr7LPQRivttNRWa+212GYrkluV
aabtt+Ay6y2A4zpUrmTchqvuusKm+5+7DcEb2bns1mvvqfTyly9Cn4k4JS0iAvCAQACLOLBuAR9c
MF0HK5KwQA4bDPHDCEtcMcMEBwxBlFKeee/HILPIMQD/UrywwBlbfLLCJrdsccQYX4yyzCyrrPHI
UzIkL2Q7h+zzzyv2rJ/QCO2bltFAJ600c0g317RBRJ8V9dJUV80zVipObfXWXHft9ddghy322GSX
bfaLu4zZ0WCzppT22XDH/dLb237WNk90/z8UTHwlgTk333IHLjhIJprkN1F7R7RLEPESkvNEh6cU
DOODV245RpM3/rhEkeNN+UPlqG3QYo1ZRQUcIZI4FeqbKopkTOsAfvnstDcUe0OkH8i66qen7voK
dxwVekSJM+SpcRtaFw2iLuGWVecnFV779NQbJP1Cxx/H/D7Ob+/8QNDrlLdD5che9H1QJWig+jcq
2L5K41cvP+3x14c+rOyHkj/47wN1vUOZW0jh3OSj9qCngO7jUfhKsgvazO+Bs1scQwbopBp9ykAI
9NsCcRLAh9TvQf0iGYg+lSEigaeE/AseTMoHwRZWbngK4VhwysQbGkoogcIz3wR1WJA7DalEPaeB
TVcqUCMhxmklK7ghom44kuK58IlwcyJCfGi68lDBiEQMomfkxD8lUsFRN5FiQ2BIJk8RRBcPmAoa
OvadNYoQiTyaSmkYyEMo2vFr/4OaGQeCRjWy0Y9v5F8cv+ixmHxQIR2ESJ429CmdJPKOkPTaIx2y
SAuORYIQyaO5wPNDTubkdpEMZddAGREEdrKRUSHjSCppSlG68pUgYaUnYUnLWtrylrjM+aUud8nL
Xo5Fa2R5mi+HeSxhKseYA0GmWIBJzGYGi5nIgaZ0uuUXZ1pTWcq0DDJD+EaYzcybNYvZylIWM3BO
7GUUMyf3bsbNzV3znbzCWfPS6TJx0hOd+CznPfWZz2+yM2CBXIg0ozJQeBrUTwWdjDSzGRWGHvSh
enLoZLKZUKZUFKIYfdFFr1bIjHr0oyANqUhHStKS+vKQIdmj20Rn0pb2B6UgIU5RYHoQUpYkHzqA
iSZdytP97DQkODXKT0v0OalwU4SnEdGJatU6g9QiM+BJk45Kk1RbTWSSPc0qc7D6w6MGp6oAWKqs
FCWQRUD1U5qZqkvAejePcP+1RCwtSKjAp4IgKcOSotncPHJQRascCTzYSVAw3Em+Omr1sJVhYUPm
2p66DuSuCBwsWPbaV+kgMLCMImxHFOvBuBJEEUQkGBcJQkOwLEJCCJQqeFBU2qsaFrGwhYwYEwJa
UI32lAIxE0Fqgdqobmm1TmqtSGa7EM4uBHnf0SF73nMw+eS0skPKkyIgUEDmUoS4sc1uWmjKx+NM
RbnesW4yn/udT7lFutQNL25Iwt2CvLUg663RmMAqqn08NZm+XR4naWEB+lYEk9oN8GMAjL2DnWa+
TK2vWfGL1r82kr/+ZW9Rx/jaMwaJFu6sZHv4itvYmNC88NGwRFQp4BKThcS2CUGubjI8yw2TdrWy
WW2IWywSFC8EuwZRxGjXtLlWDuS08OUiO74KHkW0icaKq7CJl4yU9nJvxyroMY15G+TcEvlTRh4h
Spw8ECfTornfkZiGgwrCxOhoSj6eCJeZzGbxKZlgYNbRwMZM3q6amaloRjLh3kwQAoPkvjN5b5sH
vRNBZ2TBSTF0QWzMEXaAOSbGJbSkgRJpjzh6KZWetKY3zelOe/rToA61qEcNt1RNtJqkTjVQUf3/
n2wCijIbVbWsyYQ1AEnT1JKR6Kx3XR9W+2ebAC1ZP8M5s3Guc9jk9Ceyj02XjbWzo7yOdpkDJmx+
2tNmy1ansdXJ7X0qu9nyjFetFTpuaZs7QNBWzkJ9PS92n/vdpnH3fiha7sjEGt6kvjda9I3vfvv7
3wAPuMAH/l/PmmXNBKcIO9raU4RXBuE4RstQE66RhasQthNvTsatN2GLgBUAsGErWU+iaK12RbMv
EblG0pzRkjfk4yFnKsM52PHiGlwitFiNYFE+kkxrlx2MUdQu/PWTobNxH0an0ZqsuvSmkimzLpnU
Zjrjo4gNzJsAQCVGbaqRnHdYskXxeUIiThEGMDEyt3OUHJ+zqog7fLnLbdtF3LVz5YKwvEcnbJMW
CJV2FIb5R+HV80M3LhGz41W3iP9bu0DEXhGv91W8KiH7Yedxn/ls5kluIq3Z5zMdRWzuPTzHrXXB
lCfEJ+g9qbk7RB3OEMeXty3xJQrEa34RRTiwRiKq75ZpH9u3uamSwGeq05cuKuIrJMKIN2XygQt4
rXvUzxmxPX5zfxToC/DmEaEF4EScEkbDVoaDAiHmCWHY79Kq/LN83evRLiHpNn+k3m/89gWvk/gf
hPARUcRqVB89xbeUiq83dFongO41K/TgGAV0gGdXNLOUebZxQ8tnXoTwIxUkUqyHPftHfzmBcPan
SMInRBrIXtjnUqhnYbHSGZoyR5qiF00HAGzRgnElYqwCFn53emBAQkoFUvgXLx9guH5N5n8uJxZB
SHGhNoSVMYQ7KBaMR4SqtoTM4YRMGIVSOIVUWIVWeIVYmIWkwm9FoWt35IXgAoZKI4ZHI2/xxkT2
Vm+7xIXWwoYg44a/pIYxJIdliIa7RIbZgoc/o4dm/wFs1DZP2eZtDSOI52Rt33aIzhZs6QZJ4dZt
gbhsxhaJ9VRshMhshziIj2iImKiJhXiJnZiIf2g2jViJjsiJlriJnniKnYiKqAiKRCdui7hMdIhL
cDgttWgvt0hQs9hrdvgYfPhAv1gtwfgxwwgjZkhrsRgWuVg7y/gszaguz7gU0aiF1FiN1niN2JiN
H3OBTMGNd+SNOcE2I+dTI+g14Dhg5bgPXBcZSehK7XgUG8Qc77g18zgZ7Wh9DAFWOcMOObh+WwFW
/ndVvIdLRpgS+ght8bgcBWk1C1kfePYT/EgXfKM+hgGQMIGE6fh4VLEPC7cX5pdBmLImdkUSUEhL
JdcZE8tFBYCTdEykfhwpIjVEfgQBdpFxkl6zjhWRklXRkcmFV0Ihko+1QkAYkJbUFc42WmZCkdGg
Y2rXTJI3E9V1REhHd8/TPvQQdRVkeiEYFk8JNvXokBR4lAORlODhE0xJE105EDaJWwv3YcmEHjqy
KdCgkk1JTOe4St7Bk5nHeSl0EHP1HnxDk5GRluaYkVCSlwHglvIBl8IXAHNJlB4xexNRVVTFSRhU
liwwl4ZpEfiYS53JGrUyR3HJKX4TJceRlBNIGZ85NqsJEZS5VpZ5QJipmTXRmv+LZphApAJ8E3sl
RJGngGHJiBEdWEvDKRNfogJskXkGQXrTJRBoNBBOMmTB2RTF+TXVqTMcopsQ01y9iZm/GXomcZ1I
R5QFtCapwZMH5pMtwWPT+V+QCUl3KRKnETzmWRttdR7tt5GGMpYBAAMXJxlfSTXxaUn1iZ4bCZL4
EWXtyREIx3pl4oIvKZGVlT5M9WgfMaAQFKCXcUJhdYJOh0O5NSKZoAIHA3oLuhQYGjIa+mI4uJP9
6JthFjPwA4QDeRYNeUc3ukxbORY5qjQ9mhZDuJap9J53JKRmIZiTYaRWo6SSwaTaKBkAk3ZPOqVU
WqVWeqVYmqVyg2vt1ou5VIyB0gKm9SKmTuFqu2gW01g5aaosa5otbWoUt3aMZ0GmtEOnzmKn4YKn
SuGHryiJ2HZtgEqJfyqogUpsrnh0tPhsNLOKjKqKjlqKqbhtpDiJxFapyWapi5qpfhqohxpQYxNu
m0qoooqpoUqqlHqpydap4OlXJ6oUb7qlZxoyr9qGsapu/7WaTHLah7laS3q6LL2qLb96FPTWqkkx
q6V2q/dirNSirDvBrFr6rNAardI6rdQqEynqP5sJn9mKott6Sd2qNNfqrcRDpEqxok9krjmkH+j6
M+t6cP5XDjV6pPFaSz96FIKmI7wzVjH6oUBRrz9TkCoXsDI3jjmBkZbhpHaEk49BdpFVd3mlX58i
WUPmMHBACHohWAOzJnzzgD1HrkqjsAIFdTunZQ87sQBQsRfLKBmrnVPppRuxloTJlR57rjNbfTVa
Wjibd9HAj3cgd6egfwi0C8dhni4ZEjHLNfOIQGaitHbBtDsLAD2bmEALHkLbWOXRPx8RswibaDXb
QuG6E972t1zrJbZzpl4DIw8JIBqwoX2CFSTB0J9di0hxq6K4qV4g+CPNSbb7gLZqqxtAgLED8bYw
MLcIIZkPN6+0ZJtkkXER1rgJZmXRULW2F7TN1RXcMRKKi0eIa3ePi3vNtiHUx5HBIblGkCBVaxVe
QawOkbm18a1IIZ6iBLtOEbYNWLtah7bRsA4Dw7bgoWLB4ABXVBKyu6R1q3XBd7vBobt+myC+C7y6
9xHi2a6yR7jy87WOVKM+lr2zJJ27ICc55yZDd5p2UZ+YS733wnraq3U+xr3eW7oVNHQHYybkKxL/
HOi61We/Xmu+bhayxmu7BYG7ygsJjBORQRAMKxuxWYe5+Osz83i8tIK8uTswAhyhQBAMsEG+iOF8
HdGO/loUHfxAH9yv+muvmytJJWwZSDjCOLG1T8TCRwGyiaXC6+LCZ0HD1XrDp3K0TqHDkcTDOAws
DWQZQWyXt/fD0LKEHyfDIGHDD2SkSWzEuEJ2shQHVtdlrxiREVIju+MYTTdzruWURDnFVVwbVwyT
Q3Eab+A7jWVVpbSrXSo4wWoUDLWEwZfA7PG2ZHWVnrFUGgKc/MeZSnw5DVy7duwdcpfHWMnHQ+HH
O4qMzuGs0QLJODFQgpa+qLseMpkQ/IVXr5O6/1l7wqIEsOkHXHegnH55KFEFl55cEXF8E61sLa8M
FAxFU2cWdTK2Hi0WJWV7QTeydBZ6ETB8S8H8dK94ehOoYbrsj72sAjMjF4oqqZk4qqiaqZDKip8Y
bmUzitFszY5aqtNczY3qTaq6iIw7yo10zBXYVVy0yUzLRGvBoIFsOUlrztBZyumMuuuMyiQERubH
FciaFpLsjP9cGQNFu/0LYqmRwS92ImMbvO9xwcuwgBphvdPjoP7rGQmdwJ3E0GUrROtFDxGNV23s
spQRy9Ri0jvBUJUsfA6rD1rwKUZHGi4RkQEwounlRlPSgqAsQDsdSaw7fUSHQC6tQjFdGjRt0xOn
gdNqwsx0UcSKNNBSA9VWE9BC/zLQ0ktJjSycC9zEW20R3AfFyLEOPX0Rf7zBXV29Z00RZQ3Wu/LV
VujWbG2Pab2/dhnPM0HRQjXX9YLXTdGgdi0Tw1xLgb24f72BhY0tV31JNCrETs1LQ0wZoqwxnut0
ax15Y001kU19KifSRhGkh/03zZTYYEukrjeyWPd+orHLVaweBfPLFcHEIDPYCFHaUHcyhRyxqo0x
6jHGNTaUKPzZcePDSyHchue0PohXVZtUzafcx30Rwr00AVrcOnvcQRtzt83ccI05/sfXNgHb8uPd
O+GNtI23JepJgHt6noLeGnxdwF0t4q1zZltZlWXA64d66q3AEQGvKHzZdhTCns5jEdIHup8r0cgd
cxJoRQe+ET+NtJcd4JMdJK1U3XjVFQh+yZh7wtxdE88NRRv+utuqfR3GoiK+D8jjfnlygy+r1+wy
vAQzf863SMx7twOR3pykUkucjh1efe19NqItPh+egS9+z+CLMkL90saceoQEyIPz3gwGNUL+vkS+
WkYu5UgupROdjuBdfypOOyyOomHcgyKGxXwTkRUs47BX4Wf+HWAkERkOLoMs2WHej2RuwfXtKUJt
RnJE0hTBwfydFAseSn/eFP6daH2eNIPOldMnnON5Hdpb3t07PhNZXi+RPruPHteWfumYnumavumc
3ukpQdWrpue86sZjgdIyYerRguoTQurywerKKNWMCOvSKOtxqLpAA+o0Eae2LseuLkqqPhK/rhLB
3izDThN8ykbg/KiTus3h/E+hmEvabIrJPu3LbojjrOyQeKqaWu2pKM7YTDagqu3QbIreTM3c3orf
Poe7XhS47jXtrha0LovrLqvxDtD/XOwfge9do+8dwe8k4e/F1Osl7ervvjb17kIFzxEJv0oH/zML
rxIP7+kSP/EU/1/xFu9MbU4w643fdtnow7Hx9OvxMw7yK7XkIg8xJE8TEBe3C8NDZJYQ/JjybF7p
ZNOuLV8fdXYQMe9WcQszLp/zBrHzdLTkLN+Pdgf0PaTROvWuO51mmmC1BrFgPjZ0wCvzxFPoLiTK
zvf0geJ8Uj9LVJ/VDfHnaUYMUF8Q9zX1AFD1JnHo9aL1BsH18zsQaQ/2ay/2HGGwXKFnpqwgHCZi
2T1iND82RvrVfU9ZzS3fKT4Rhn/Pfq/4Id6xgyPbI25UT4L4gI/3L7vdhql6lURlnI1f/6kRig5B
Ouz5swT6LDefkUmefD9LQBb6GzL6Rjv4zzLPG19Jsb/6VED7KP+htV++3n3/8plv9RBR+g9k0cLv
+MRPY4GvOMVLJsxPXsXf9rbvLMov/U/S/Br8/ISD403v/I6/D4gm++Z/EYEOn+Hf/eNf/rxv/Hqz
/pYf9Tzy/iaR/gIq/04+JoBm/gCRj0qcfQUNHkSYUOFChvt2BWmocBeQiAv1DUyojxBBhPNyHLzI
EWHIiiURljNiUuVKli1dvoQZU+ZMmgdRuiQ5cmNCjyAxZvxZs2A5ii1zgtzZ8aPBoz5FCl14E+pU
qlWtXjUplWXTghqfFuzJNKhTrBW1mlxXlKXAr/sUPYiWsNapg2wV2p06sexevn39/i25K2VLvAff
xkU4t+5Yg4XbhQZTu9JxwcNy6TZmXHDyVb2APX8GLVSwy82VES66rDnzvs1/R698vZUKANoAHuy7
WBtA0Xw6Rs6uDcGhbgAJENOMHVr5cubNO8vWfTt3bd6+feoWvou4caFnVU6nLR047eq/sQ/XzR1r
8ubt3YN+vhK8bdzjd2u2Lva89vTHXUcODKKyFgmFuWAEfC9BBReM6cC9CGTuoQcLXNBBBi/EsCYL
saqFwgwN2jCrwa5i5zbmiPowRRUXRBGrEp0b0aoXGWxxRRtvtAlAqmZcsUYcfwQySCGHJLJII49E
/zJJJZdkskknn4QySimnpLJKK6/EMkstt+SySy+/BDNMMccksy99rEjNyXzQLLPNmtZMs0k4s5zT
zSrr/BLPktb0r8kz+7Qz0O+sAHTJP7M8VFApE/2S0ZLOjJNJPRWltKFJJWUTy0srVXJTLT1NiJDt
4qIluoJKrc1EVMM71dR9VqXPLVdhVXVWW4PTaFROd+1K1P5evZVVYFNtldhhhVUk2FiTNZZZZLHL
9VdaixV22mOXddXZWK3lVtlacfW1NvV4LTJacePS1sR0KfOW3WbblfVdeZ+dFwAIzKVt3IYc9ZNQ
cv/tyl8o+aWSYICJNFjLhBcCFcmGD3bzYSMlljozU4gntthLipkS+MmFL27z4yNFdpJkkFU0ueCO
T2a5ZZdfhjlmmWemuWabb8Y5Z5135rlnn38GOmihXYcmumijj0Y6aaWXZrppp5+GOmqpp6a6aquv
xjprrbfmumuvvwY7bLHHJrtss89GO22112a7bbffhjtuueemu26778Y7b733Djs+vvPS8Wu/4R5c
b/b+Fi3GvhUnnNBxwwNHfKbCvZ687crvDjFyDREUO3O4PdfbR81pEh3s0t8+PW/IRodqdbJdnxv2
v2VnXSbawb797dzzlrB25DjvG3jChQ/dcd9b8s5049tO/vHjJYe868vXnr7uw59n6XrKl2dbe7x3
OQL7mMAvm3y6zRc/ffXXv7r6mtgJwMPvtKAt/pxbQy56rt1Hm3+50+oL/O4Ak3msYIA444pQAEi2
Bc6tgX9Dn0z0oYWnzEMGhXJJAeVnlQnqa0X4ewkIZRLBvoUPQwJxFcNWQxURBomE/3urnP9eFRl2
3MtXAkCMQOAgqgAcED0CSJMGD8IfIIJFBfU74DyOCIAeRoQdDqiC/PhTHMRMUT1EvIwSkWjELaow
Dswy0Q/poi0AxGGCT5HHDKIRrSLqkIcDzIkimqiSGOpva3V0Dy1GFBIwxqs2IsEia6iwQyYOkC19
LEggydiWDOExcrnTDvcUsjpFGAd27ChifeKnj0JQaBc4dMi4hJhIUO7COJNpoWHuQIsw7sJ+Q3yl
QT4ZF1NGA5UrNA9BSDLLUHZlLHp0i3FqqJHBzFIfKthkJwVJEEVIciHaCdzuugZJADjzL4pAEAp1
iRGu8LKWF0lmgXKzTYJ4MwG+ZP+kiqA5STvWTXTaEU5LhkkFHNJCJJhEDFeIqRkWHCcfK6DQPlnT
T31U0j8F9eBC5qHGfLCALgJlCiEUV1DeENSgILloRPBSUDNKlJ90cUwwHqAPMXAhGoIZZUj0OUhF
pNMkpQJQ6rr2TnspCJjo7EpLl4nRitqSMTnhqEAbClJcqgimJ2kn3TYEz4Ssy481zYcMhFEBQsAB
QgXB5GUmM59YygOgvtTNK7UYTy6S9Zkp2edKv8JVCo31IG5lCFA3wtb6PIUdCRAGEGhxhw5lVTVx
uCUVDZOtFBokWWoBndeWWlOEONWxhK2Xus5j2BFtdCdNYStXLGtG+9iPK4+NrLv/6DVabIW2sfcp
SGK/p7hgxGorVoiEEXZRBIvhE6dIMV5KFRG9iwCot3ENFxUh2quJEoK3VPAtcuMalJYO97ZgYUEk
7sAOIxjiFP8M6EBWusqEqiRZrE0q1tjT2jDmUS1H0SlmPUoW9rqlo4xL4I2+ixBp3q1wrQ1vROPH
DsFiFZQ7RYgrNwiWryYylvugB4XskuC/MqSGYilnGQMs4YME48AM3imGQbhRCjrkwLhZry9xOI8Y
qFGgs7wlQViJwYZEUiL5tdp9UdseRZgQwF4BseIEvJivcLicH3aujVycEBnCrXmphfGrcHgRs/q1
rpOsTSxHmdooh0KLtBnMlasZ/1edGkQX8Wwtbf4bZgCMucpazvISt7xcjnCUyvWjEH/JU5Av4+Yt
BrnhQ3/KTUJ8OCLeO/JMl1ffvqCQWEAFA0fkPGMyb3LPbe5yo+NMnRsB2ppz6x376Eg8ynHacp62
76U1nUhRx7jU5Tv1qFW9albDjNAv0ch/lRStV9J6g/Ab8HsuUt69vDprvkYbsOWWaaEo0axNmjKB
b+1nBSkik3shdvCsB2q7BRrW68WxQRb6jNVoRD2/xU3GHjUeZj+3IsneB7qB4lLlrKO7VLH21uKt
tnmfL8kVsS1lYsSOCsT3iVXQKhXsxyf5hNggiy7iImUpZv8UME4O7xXDRUsbQA6KOVJmKqpo7j21
IpOt4/9u895L6mwQANLCkkCIryJWaSJ9VMEG0hF3RDSiI3rEZebmdggogyHKAmu75/5NTTeL6G4W
l0UXvLZKyO+Y6rEp3Xo2rkkzDzLPegI2Mx6Jxjz6yRorJEMFgF1ZSeTcXVpYoMERzfLWld2Rn+8j
3wAmLnSLvp5jW2Ud1NbaC992d83J9CW0iIxHhPEARcBhC6dIIIpu/qdgCAAaMTcJf7ljLpaPha4E
9iHmEeLkJ+unyqARKV8+LjW/U2/jbRO2SRRh9sZY4RJACMYPCKVP+qVqjWjSiAPCLhmAaoT1ZT97
3BWCbnS/3TFB/gzwe336qKW+bM5/2+gd/GyN7JeKk5HhB1lDQvB8qCCTsb54Y8hw8CUrt6BhNPg+
LJxr7CKk/VN/9j7Sv/6MECL+CrlI/POfJoHcv/NlKb28Yz7TGUC1Ua1rixFnWyMqEI75sKGnoIV7
yRReAjFZw7/x+C85C4BMUIF4WjS1mCIpa7vis8APXDg46wotsMC7oCf/6L+DakEie7epOMCtqUED
xDu6qTfZqLuqkIcZRJIfnDuaoIUV5AymIz0kXBzNkb59sb8hjIls85ikuAqB6EHOKECnaULBycJW
88IvBMMwFMMxJMMyNMMzRMM0VMM1ZMM2dMM3hMM4IJTDOaTDOrTDO8TDPNTDPeTDPvTDPwTEQBTE
QSTEOwwIADs=

------=_NextPart_000_0106_01CDCC01.1B548550--


From fpb@tid.es  Tue Nov 27 04:40:15 2012
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AF1321F8231 for <tcmtf@ietfa.amsl.com>; Tue, 27 Nov 2012 04:40:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=2.300,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6xAMvbDoHW+P for <tcmtf@ietfa.amsl.com>; Tue, 27 Nov 2012 04:40:10 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 533B721F8534 for <tcmtf@ietf.org>; Tue, 27 Nov 2012 04:40:03 -0800 (PST)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0ME500EVKCIQ58@tid.hi.inet> for tcmtf@ietf.org; Tue, 27 Nov 2012 13:40:02 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id A5.6F.03143.2A4B4B05; Tue, 27 Nov 2012 13:40:02 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0ME500EVECIP58@tid.hi.inet> for tcmtf@ietf.org; Tue, 27 Nov 2012 13:40:01 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.64]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Tue, 27 Nov 2012 13:40:01 +0100
Date: Tue, 27 Nov 2012 12:40:00 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <010501cdcbf8$b98dac50$2ca904f0$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>
Message-id: <F5EDC35DF914C1428C28E149F10463A2528314B3@EX10-MB2-MAD.hi.inet>
Content-id: <3DE940F72F2D294C9AB9F0F2236AD7FA@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [tcmtf] Some thoughts about new scenarios for tcmtf
Thread-index: Ac3EDOy4duakoHOCR7KDbQibMeqaCQCeb0QAAB638AAAA5CPUAA6PJoAAPljbQAABILXAAAq/1eA
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4068-b7f746d000000c47-8f-50b4b4a2d7d1
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPKsWRmVeSWpSXmKPExsXCFe/Apbtoy5YAgx1LeC12fd7A6MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujK/dh5gL5tRVXDn8n6WBcV9CFyMnh4SAicSEX3sZIWwxiQv3 1rN1MXJxCAlsYJRYdKCZHcL5wSjx6vd/ZghnGqPEyvaHLCAtLAKqEmcbt4O1swloSZy+uwos LizgIHHk9DUwm1PAQuJe7zlmiBUKEn/OPQaLiwjESexbvoO1i5GDgxlozrxviiBhXgFviQnL dzKB2MwCZhLn3sxmhYgLSvyYfI8FIq4j0fv9GzOELS7R3HoTKq4t8eTdBbB6RqBvvp9awwSx ylHi9MFuqLUxEu8vnwCLiwroSbQdO8MOcZqAxJI956HOFJV4+fgf6wRGiVlIzpiF5IxZSM6Y heSMWUjOWMDIuopRrDipKDM9oyQ3MTMn3cBQLyNTLzMvtWQTIyTuMnYwLt+pcohRgINRiYf3 xOrNAUKsiWXFlbmHGCU5mJREeRes3BIgxJeUn1KZkVicEV9UmpNafIhRgoNZSYR34SqgHG9K YmVValE+TEqGg0NJgtd5M1BKsCg1PbUiLTMHmFxg0kwcnCDtPEDtNiA1vMUFibnFmekQ+VOM 2hxzDrU/YeTY9qnrCaMQS15+XqqUOK81SKkASGlGaR7ctFeM4kBnC/NGgWR5gKkSbs4roBVM QCuSr28EWVGSiJCSamBct8qnZkrVre8rhCXXX588zSP39L0bnubHH+zYs0Nj3r0I5YKfF8y8 Gs1f75PU8+Ep+uq481V3RQpX4Mv2yGtvrm/nd7fS+/TZLuBSd60bj5qb0If4hhqRR5OC7eWP fXi/ZQX7ixU5LPut2znnxb/Z7OA8k21P93330m/qt16fKJ+u+ENGk3mzEktxRqKhFnNRcSIA 8vScYlIDAAA=
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 12:40:15 -0000

Jose,

        I think that the proposition is to adopt within the original draft =
what
you have described as "Encaps". If so, the optimized path will be the path
between node A and node B, and you can be sure that traffic within that
"Encaps" is destined to node B. Given that, you can suppose that the TCMTF
path is the path between A and B, having different tunnel/multiplex in
every scope (wireless and Internet), but maintaining the compress layer.
With dynamic TCMTF signalling, somehow, every scope in the path will
select the most optimal tunneling/multiplex method in every hope
(supposing that the Access Point is TCMTF-aware).

Regards,

Fernando Pascual Blanco
Telef=F3nica Global Resources
Network Automation and Dynamization
TECHNOLOGY PEOPLE GROUP
F +34913128779
M +34682005168
fpb@tid.es




On 26/11/12 18:08, "Jose Saldana" <jsaldana@unizar.es> wrote:

>Hi,
>
>I am trying to get some light about this. First, let us try to know if the
>picture is correct. If you put this in Courier letters, I think you can
>see
>it correctly (I attach it as an image, just in case). Tomaso, is the
>picture
>right?
>
>Node A
>Node B
>+----------+
>+------------+
>| Appl.    |
>| Appl.      |
>+----------+
>+------------+
>| TCP/UDP  |
>| TCP/UDP    |
>+----------+
>+------------+
>|   IP     |                                  Access Point
>|   IP       |
>+----------+                             +----------------------+
>+------------+
>|  ROHC    |                             |       Relay          |
>|   ROHC     |
>+----------+                             +----------------------+
>+------------+
>|          |                             |          | PPPmux    |
>|  PPPmux    |
>| Encaps   |                             |  Encaps  +-----------+
>+------------+
>|          |                             |          |  IPtunn.  |
>|  IPtunn.   |
>+----------+                            +----------+-----------+
>+------------+
>|  L2/L1   |                             |  L2/L1   |  L2/L1    |
>|  L2/L1     |
>+----------+                             +----------+-----------+
>+------------+
>
>           |                             |                      |
>|
>           |<--Wireless Access network-->|
>|<------Internet-------->|
>           |   (WLAN, Satellite, ...)    |                      |
>|
>
>
>So the first question is:
>
>Tomaso, is there a single connection from Node A to Node B, or the Access
>Point has to distinguish different flows? Are all packets travelling from
>A
>to B?
>
>If the answer is "Yes", then, as Fernando says, the AP does not need to
>decompress/compress ROHC. It only needs to get a number of packets,
>decapsulate them, and put them together into a multiplexed packet with
>PPPMux.
>
>I think we should first set this clear in order to advance.
>
>Thanks,
>
>Jose
>
>> -----Mensaje original-----
>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>> Enviado el: lunes, 26 de noviembre de 2012 15:00
>> Para: Michael Ramalho (mramalho); Tomaso.deCola@dlr.de
>> CC: tcmtf@ietf.org; Matteo.Berioli@dlr.de; Hartmut.Brandt@dlr.de;
>> jsaldana@unizar.es
>> Asunto: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
>>
>> Hi All,
>>
>>         Actually Jose proposed the idea of developing two new drafts:
>>the
>> b)"Recommendations draft" and the c)"Dynamic Signaling Draft". That
>>relay
>> between different tunneling, multiplexing or even compression
>>capabilities
>> through the optimized path could be addressed to the c) draft as TCMTF
>> negotiation concepts in a multi-capability path. It should also be
>mentioned in
>> the original draft and recommended in the b) draft.
>>         For example, for the satellite scenario, it would not be
>>necessary
>to
>> decompress ROHC within the Access Point, since it should only take
>>packets
>> multiplexed and tunneled in a way (the existing and efficient
>encapsulation
>> protocols, which could also be adopted within the original Jose=B4s draf=
t
>>as
>> different tunnel and multiplex options), and multiplex-tunnel them in
>> another way (as Michael says, acting as a tunnel and/or multiplex relay)
>> without see layer 3 headers.
>>
>> Regards,
>>
>> Fernando Pascual Blanco
>> Telef=F3nica Global Resources
>> Network Automation and Dynamization
>> TECHNOLOGY PEOPLE GROUP
>> F +34913128779
>> M +34682005168
>> fpb@tid.es
>>
>>
>>
>>
>> On 21/11/12 16:59, "Michael Ramalho (mramalho)" <mramalho@cisco.com>
>> wrote:
>>
>> >All,
>> >
>> >I think Tomaso's suggestion could occur as a separate section in Jose's
>> >draft (draft-saldana-tsvwg-tcmtf-03) for the case of where the (TCMTF)
>> >tunnel endpoints use a different multiplexing layer (where Jose has
>> >"PPPMUX or other mux protocols" in the draft).
>> >
>> >However, tunnel endpoints are hard enough to specify .. and now you
>> >would need to know if there is a relay somewhere in-between the tunnel
>> >endpoints that uses a different multiplexing technique.
>> >
>> >In other words, you would need to know EVEN MORE about the capability
>> >of possible intermediate nodes (in this case that a relay is possible
>> >between your TCMTF tunnel endpoints) . or perhaps decide if a relay is
>> >needed if the existing TCMTF tunnel endpoints do not use the same
>> >multiplexing layer (e.g., a "lossless transcode" function).
>> >
>> >If we decide to add a section in Jose's draft, we would need to provide
>> >guidance concerning how the endpoints are either configured or
>> >negotiated. If we want TCMTF to be "simple" and "just configured"
>> >(e.g., on WAN edges) . then negotiation and possible insertion/use of a
>> >relay is a pretty big complication to the document. However, we SHOULD
>> >address this concern (how tunnel endpoints are found, how we ensure
>> >relays remain on the end-to-end tunnel path) in the document anyway!
>> >
>> >Jose/Tomaso: Do you have thoughts on how the TCMTF endpoints
>> negotiate
>> >the lower layers?
>> >
>> >Michael Ramalho
>> >
>> >-----Original Message-----
>> >From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
>> >Of Tomaso.deCola@dlr.de
>> >Sent: Tuesday, November 20, 2012 7:08 AM
>> >To: fpb@tid.es
>> >Cc: tcmtf@ietf.org; Matteo.Berioli@dlr.de; Hartmut.Brandt@dlr.de;
>> >jsaldana@unizar.es
>> >Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
>> >
>> >Hi Fernando,
>> >
>> >Yes you are right, the basic idea it to enable RoHC end-to-end (or even
>> >in a subpart of the whole network) and using tcmtf tunneling and
>> >multiplexing features only in the last segment of the network (e.g.,
>> >from the AP to the end-users).
>> >The point is that the Access Point, which can be regarded as a gateway
>> >in satellite networks, has to de-capsulate anyway the IP datagrams
>> >incoming over the satellite link. As such, I don't see much processing
>> >complexity on this node. On the other hand, the use of tcmtf on an e2e
>> >basis in this scenario is not really efficient, because the
>> >tunneling-multiplexing functions are in fact already provided by the
>> encapsulation protocol.
>> >Over the satellite/wireless link.
>> >With this I don't mean that e2e tcmtf is never profitable, but the
>> >scenarios that include satellite/wireless access network certainly
>> >require an "adaptation" of tcmtf concepts, as described in my proposal.
>> >
>> >Regards,
>> >
>> >Tomaso
>> >
>> >------------------------
>> >Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace
>> Center
>> >Institute of Communications and Navigation | Satellite Networks |
>> >Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D.
>> >Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
>> >tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
>> >
>> >-----Original Message-----
>> >From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>> >Sent: Tuesday, November 20, 2012 10:29 AM
>> >To: jsaldana@unizar.es; Cola, Tomaso de; tcmtf@ietf.org
>> >Cc: Berioli, Matteo; Brandt, Hartmut
>> >Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
>> >
>> >Hi Tomaso, Jose,
>> >
>> >        I=B4m afraid I=B4m not able to view properly you ASCII picture,=
 but
>> >if I=B4m not misunderstanding you, you are proposing to have a header
>> >compression
>> >(ROHC) end to end, while having multiplexing and tunneling after the
>> >satellite/wireless link (through the LAN with several layer 3 hops or
>> >through the Internet). So Jose, I think Tomaso is not proposing to
>> >decompress ROCH in the access point, but in the Node B.
>> >        Do you think that this would be more interesting than using
>> >TCMTF e2e?, given that the AP will have to de-encapsulate the existing
>> >multiplexing/tunneling method in wireless/satellite links, and
>> >encapsulate using TCMTF in the other side. In terms of bandwidth for
>> >sure, but how much? Do it compensate in terms of processing capacity?
>> >
>> >Regards,
>> >
>> >Fernando Pascual Blanco
>> >Telef=F3nica Global Resources
>> >Network Automation and Dynamization
>> >TECHNOLOGY PEOPLE GROUP
>> >F +34913128779
>> >M +34682005168
>> >fpb@tid.es
>> >
>> >
>> >
>> >
>> >On 19/11/12 20:49, "Jose Saldana" <jsaldana@unizar.es> wrote:
>> >
>> >>Tomaso,
>> >>
>> >>If I understand well, the idea is that tcmtf is not used in the
>> >>satellite link, but only  in the "Internet" part. So the "Access
>>Point"
>> >>does not need to decompress the ROHC headers.
>> >>
>> >>I think that the key question is now: can this be included in the
>> >>current
>> >>draft-saldana-tsvwg-tcmtf-03 of tcmtf or would it require a specific
>> >>draft?
>> >>
>> >>You say that the idea is different from the concepts in
>> >>draft-saldana-tsvwg-tcmtf-03. If you could provide some reasons
>> >>supporting this, it would be fine, I think.
>> >>
>> >>We also need feedback from the list in order to set this clear.
>> >>
>> >>Thank you very much,
>> >>
>> >>Jose
>> >>
>> >>> -----Mensaje original-----
>> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> nombre
>> >>> de Tomaso.deCola@dlr.de Enviado el: viernes, 16 de noviembre de 2012
>> >>> 16:31
>> >>> Para: tcmtf@ietf.org
>> >>> CC: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de;
>> >>> Hartmut.Brandt@dlr.de; jsaldana@unizar.es
>> >>> Asunto: [tcmtf] Some thoughts about new scenarios for tcmtf
>> >>>
>> >>>
>> >>> Dear All,
>> >>>
>> >>> As discussed some time ago, satellite and wireless access network
>> >>>can  be attractive network scenarios where tcmtf principles can be
>> >>>exploited.
>> >>> However, usual wireless and satellite encapsulation protocol
>> >>>(between  IP and lower layers) already provide means to multiplexing
>> >>>and "tunneling"
>> >>> compressed flows.
>> >>> In this respect, the application of tcmtf in these scenarios is less
>> >>attractive,
>> >>> as it would introduce additional overhead, resulting in less
>> >>>benefits from  the bandwidth-saving point of view. Hence, we propose
>> >>>a deviation from  the tcmtf concepts, so that the access network
>> >>>(wireless or satellite)
>> >>keeps
>> >>> untouched the protocol stack allowing the compression of data flows
>> >>>through ROHC (for example). The access point serving as "bridge"
>> >>>between  the access network and the second leg of the network (i.e.
>> >>>Internet)  implements a dual stack, with PPPmux and IP tunneling
>> >>>techniques, to  multiplex and tunnel the compressed flows coming from
>> >>>the access  network. The final destination will obviously implement a
>> >>>stack including  the three tcmtf ingredients (compression,
>> >>>multiplexing, tunneling).
>> >>>
>> >>> The following diagram illustrates the idea: A wireless Node A
>> >>> delivers
>> >>data
>> >>> to Node B though the wireless access networks and Internet.
>> >>> As this idea substantially deviates from the concepts presented in
>> >>>draft-
>> >>> saldana-tsvwg-tcmtf-03, we propose to dedicate an additional I-D to
>> >>>this  idea, where implications on mobility and security should be
>> >>>addressed as  well.
>> >>>
>> >>> What is your opinion?
>> >>>
>> >>> Best Regards,
>> >>>
>> >>> Tomaso
>> >>>
>> >>>
>> >>>               Node B
>> >>>
>> >>>              +------------+
>> >>> Node A
>> >>>              | Appl.         |
>> >>> +------------ +
>> >>>              +------------+
>> >>> | Appl.         |
>> >>>                      | TCP/UDP |
>> >>> +------------+
>> >>>
>> >>> +------------+ +------------+
>> >>> | TCP/UDP |
>> >>>Access
>> >>Point
>> >>>              |        IP        |
>> >>> +------------+
>> >>+-----------------------------+
>> >>>              +------------+
>> >>> |         IP       |
>> >>|       Relay                              |
>> >>>              |   ROHC      |
>> >>> +------------+
>> >>+----------------------------+
>> >>>              +------------+
>> >>> |  ROHC       |
>|
>> >>|  PPPmux   |
>> >>>              |  PPPmux |
>> >>> +------------+
>> >>> +------------+ |
>> >>Encaps         +------------+
>> >>>              +------------+
>> >>> | Encaps     |
>|
>> >>|  IPtunn.     |
>> >>> |  IPtunn.  |
>> >>> +------------+
>> >>+---------------+------------+
>> >>>              +------------+
>> >>> |  L2/L1       |                                              |
>>L2/L1
>> >>|  L2/L1         |
>> >>>              |  L2/L1       |
>> >>> +------------+
>> >>+---------------+------------+
>> >>>              +------------+
>> >>> |                                     |
>> >>|
>> >>>              |
>> >>> |<------Wireless Access network-------->|
>> >>|<------
>> >>> Internet----------->|
>> >>> |        (WLAN, Satellite, ...)                       |
>> >>|
>> >>> |
>> >>>
>> >>>
>> >>>
>> >>> ------------------------
>> >>> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace
>> >>>Center Institute of Communications and Navigation | Satellite
>> >>>Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de
>> >>>Cola, Ph.D.
>> >>> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
>> >>>tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
>> >>>
>> >>> _______________________________________________
>> >>> tcmtf mailing list
>> >>> tcmtf@ietf.org
>> >>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>
>> >>_______________________________________________
>> >>tcmtf mailing list
>> >>tcmtf@ietf.org
>> >>https://www.ietf.org/mailman/listinfo/tcmtf
>> >
>> >
>> >________________________________
>> >
>> >Este mensaje se dirige exclusivamente a su destinatario. Puede
>> >consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=
=F3nico
>> >en el enlace situado m=E1s abajo.
>> >This message is intended exclusively for its addressee. We only send
>> >and receive email on the basis of the terms set out at:
>> >http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> >_______________________________________________
>> >tcmtf mailing list
>> >tcmtf@ietf.org
>> >https://www.ietf.org/mailman/listinfo/tcmtf
>>
>>
>> ________________________________
>>
>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en e=
l enlace
>> situado m=E1s abajo.
>> This message is intended exclusively for its addressee. We only send and
>> receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From jsaldana@unizar.es  Wed Nov 28 01:34:42 2012
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FABB21F8235 for <tcmtf@ietfa.amsl.com>; Wed, 28 Nov 2012 01:34:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.212
X-Spam-Level: 
X-Spam-Status: No, score=-6.212 tagged_above=-999 required=5 tests=[AWL=2.388,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id stk9mIfAS52I for <tcmtf@ietfa.amsl.com>; Wed, 28 Nov 2012 01:34:40 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id F0DF621F8231 for <tcmtf@ietf.org>; Wed, 28 Nov 2012 01:34:39 -0800 (PST)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id qAS9YXda001665; Wed, 28 Nov 2012 10:34:33 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>, <Tomaso.deCola@dlr.de>
References: <010501cdcbf8$b98dac50$2ca904f0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2528314B3@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A2528314B3@EX10-MB2-MAD.hi.inet>
Date: Wed, 28 Nov 2012 10:34:36 +0100
Organization: Universidad de Zaragoza
Message-ID: <003a01cdcd4b$95485800$bfd90800$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIxe0g2RwC4T56Z/0gGmNhoSFlZgpc3n7kg
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 09:34:42 -0000

Fernando,

If I understood well, the idea of Tomaso was this:

- The "left link" (wireless) between the satellite and the AP has its =
own
well-defined protocols.
- That protocols include RoHC.
- So we can use tcmtf in the "right link" (Internet) between the AP and =
the
destination through the Internet.
- In the AP we don't need to decompress-compress RoHC.

However, I don't really know if Tomaso wanted to propose this. Let's =
wait
for his response.

Thanks,

Jose

> -----Mensaje original-----
> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> Enviado el: martes, 27 de noviembre de 2012 13:40
> Para: jsaldana@unizar.es; Tomaso.deCola@dlr.de
> CC: tcmtf@ietf.org
> Asunto: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
>=20
> Jose,
>=20
>         I think that the proposition is to adopt within the original =
draft
what you
> have described as "Encaps". If so, the optimized path will be the path
> between node A and node B, and you can be sure that traffic within =
that
> "Encaps" is destined to node B. Given that, you can suppose that the =
TCMTF
> path is the path between A and B, having different tunnel/multiplex in
every
> scope (wireless and Internet), but maintaining the compress layer.
> With dynamic TCMTF signalling, somehow, every scope in the path will
select
> the most optimal tunneling/multiplex method in every hope (supposing =
that
> the Access Point is TCMTF-aware).
>=20
> Regards,
>=20
> Fernando Pascual Blanco
> Telef=F3nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>=20
>=20
>=20
>=20
> On 26/11/12 18:08, "Jose Saldana" <jsaldana@unizar.es> wrote:
>=20
> >Hi,
> >
> >I am trying to get some light about this. First, let us try to know =
if
> >the picture is correct. If you put this in Courier letters, I think =
you
> >can see it correctly (I attach it as an image, just in case). Tomaso,
> >is the picture right?
> >
> >Node A
> >Node B
> >+----------+
> >+------------+
> >| Appl.    |
> >| Appl.      |
> >+----------+
> >+------------+
> >| TCP/UDP  |
> >| TCP/UDP    |
> >+----------+
> >+------------+
> >|   IP     |                                  Access Point
> >|   IP       |
> >+----------+                             +----------------------+
> >+------------+
> >|  ROHC    |                             |       Relay          |
> >|   ROHC     |
> >+----------+                             +----------------------+
> >+------------+
> >|          |                             |          | PPPmux    |
> >|  PPPmux    |
> >| Encaps   |                             |  Encaps  +-----------+
> >+------------+
> >|          |                             |          |  IPtunn.  |
> >|  IPtunn.   |
> >+----------+                            +----------+-----------+
> >+------------+
> >|  L2/L1   |                             |  L2/L1   |  L2/L1    |
> >|  L2/L1     |
> >+----------+                             +----------+-----------+
> >+------------+
> >
> >           |                             |                      |
> >|
> >           |<--Wireless Access network-->|
> >|<------Internet-------->|
> >           |   (WLAN, Satellite, ...)    |                      |
> >|
> >
> >
> >So the first question is:
> >
> >Tomaso, is there a single connection from Node A to Node B, or the
> >Access Point has to distinguish different flows? Are all packets
> >travelling from A to B?
> >
> >If the answer is "Yes", then, as Fernando says, the AP does not need =
to
> >decompress/compress ROHC. It only needs to get a number of packets,
> >decapsulate them, and put them together into a multiplexed packet =
with
> >PPPMux.
> >
> >I think we should first set this clear in order to advance.
> >
> >Thanks,
> >
> >Jose
> >
> >> -----Mensaje original-----
> >> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] Enviado el: lunes,
> 26
> >> de noviembre de 2012 15:00
> >> Para: Michael Ramalho (mramalho); Tomaso.deCola@dlr.de
> >> CC: tcmtf@ietf.org; Matteo.Berioli@dlr.de; Hartmut.Brandt@dlr.de;
> >> jsaldana@unizar.es
> >> Asunto: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
> >>
> >> Hi All,
> >>
> >>         Actually Jose proposed the idea of developing two new =
drafts:
> >>the
> >> b)"Recommendations draft" and the c)"Dynamic Signaling Draft". That
> >>relay  between different tunneling, multiplexing or even compression
> >>capabilities  through the optimized path could be addressed to the =
c)
> >>draft as TCMTF  negotiation concepts in a multi-capability path. It
> >>should also be
> >mentioned in
> >> the original draft and recommended in the b) draft.
> >>         For example, for the satellite scenario, it would not be
> >>necessary
> >to
> >> decompress ROHC within the Access Point, since it should only take
> >>packets  multiplexed and tunneled in a way (the existing and =
efficient
> >encapsulation
> >> protocols, which could also be adopted within the original Jose=B4s
> >>draft as  different tunnel and multiplex options), and
> >>multiplex-tunnel them in  another way (as Michael says, acting as a
> >>tunnel and/or multiplex relay)  without see layer 3 headers.
> >>
> >> Regards,
> >>
> >> Fernando Pascual Blanco
> >> Telef=F3nica Global Resources
> >> Network Automation and Dynamization
> >> TECHNOLOGY PEOPLE GROUP
> >> F +34913128779
> >> M +34682005168
> >> fpb@tid.es
> >>
> >>
> >>
> >>
> >> On 21/11/12 16:59, "Michael Ramalho (mramalho)"
> <mramalho@cisco.com>
> >> wrote:
> >>
> >> >All,
> >> >
> >> >I think Tomaso's suggestion could occur as a separate section in
> >> >Jose's draft (draft-saldana-tsvwg-tcmtf-03) for the case of where
> >> >the (TCMTF) tunnel endpoints use a different multiplexing layer
> >> >(where Jose has "PPPMUX or other mux protocols" in the draft).
> >> >
> >> >However, tunnel endpoints are hard enough to specify .. and now =
you
> >> >would need to know if there is a relay somewhere in-between the
> >> >tunnel endpoints that uses a different multiplexing technique.
> >> >
> >> >In other words, you would need to know EVEN MORE about the
> >> >capability of possible intermediate nodes (in this case that a =
relay
> >> >is possible between your TCMTF tunnel endpoints) . or perhaps =
decide
> >> >if a relay is needed if the existing TCMTF tunnel endpoints do not
> >> >use the same multiplexing layer (e.g., a "lossless transcode"
function).
> >> >
> >> >If we decide to add a section in Jose's draft, we would need to
> >> >provide guidance concerning how the endpoints are either =
configured
> >> >or negotiated. If we want TCMTF to be "simple" and "just =
configured"
> >> >(e.g., on WAN edges) . then negotiation and possible insertion/use
> >> >of a relay is a pretty big complication to the document. However, =
we
> >> >SHOULD address this concern (how tunnel endpoints are found, how =
we
> >> >ensure relays remain on the end-to-end tunnel path) in the =
document
> anyway!
> >> >
> >> >Jose/Tomaso: Do you have thoughts on how the TCMTF endpoints
> >> negotiate
> >> >the lower layers?
> >> >
> >> >Michael Ramalho
> >> >
> >> >-----Original Message-----
> >> >From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> >> >Behalf Of Tomaso.deCola@dlr.de
> >> >Sent: Tuesday, November 20, 2012 7:08 AM
> >> >To: fpb@tid.es
> >> >Cc: tcmtf@ietf.org; Matteo.Berioli@dlr.de; Hartmut.Brandt@dlr.de;
> >> >jsaldana@unizar.es
> >> >Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
> >> >
> >> >Hi Fernando,
> >> >
> >> >Yes you are right, the basic idea it to enable RoHC end-to-end (or
> >> >even in a subpart of the whole network) and using tcmtf tunneling
> >> >and multiplexing features only in the last segment of the network
> >> >(e.g., from the AP to the end-users).
> >> >The point is that the Access Point, which can be regarded as a
> >> >gateway in satellite networks, has to de-capsulate anyway the IP
> >> >datagrams incoming over the satellite link. As such, I don't see
> >> >much processing complexity on this node. On the other hand, the =
use
> >> >of tcmtf on an e2e basis in this scenario is not really efficient,
> >> >because the tunneling-multiplexing functions are in fact already
> >> >provided by the
> >> encapsulation protocol.
> >> >Over the satellite/wireless link.
> >> >With this I don't mean that e2e tcmtf is never profitable, but the
> >> >scenarios that include satellite/wireless access network certainly
> >> >require an "adaptation" of tcmtf concepts, as described in my
proposal.
> >> >
> >> >Regards,
> >> >
> >> >Tomaso
> >> >
> >> >------------------------
> >> >Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace
> >> Center
> >> >Institute of Communications and Navigation | Satellite Networks |
> >> >Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D.
> >> >Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
> >> >tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
> >> >
> >> >-----Original Message-----
> >> >From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> >> >Sent: Tuesday, November 20, 2012 10:29 AM
> >> >To: jsaldana@unizar.es; Cola, Tomaso de; tcmtf@ietf.org
> >> >Cc: Berioli, Matteo; Brandt, Hartmut
> >> >Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
> >> >
> >> >Hi Tomaso, Jose,
> >> >
> >> >        I=B4m afraid I=B4m not able to view properly you ASCII =
picture,
> >> >but if I=B4m not misunderstanding you, you are proposing to have a
> >> >header compression
> >> >(ROHC) end to end, while having multiplexing and tunneling after =
the
> >> >satellite/wireless link (through the LAN with several layer 3 hops
> >> >or through the Internet). So Jose, I think Tomaso is not proposing
> >> >to decompress ROCH in the access point, but in the Node B.
> >> >        Do you think that this would be more interesting than =
using
> >> >TCMTF e2e?, given that the AP will have to de-encapsulate the
> >> >existing multiplexing/tunneling method in wireless/satellite =
links,
> >> >and encapsulate using TCMTF in the other side. In terms of =
bandwidth
> >> >for sure, but how much? Do it compensate in terms of processing
> capacity?
> >> >
> >> >Regards,
> >> >
> >> >Fernando Pascual Blanco
> >> >Telef=F3nica Global Resources
> >> >Network Automation and Dynamization
> >> >TECHNOLOGY PEOPLE GROUP
> >> >F +34913128779
> >> >M +34682005168
> >> >fpb@tid.es
> >> >
> >> >
> >> >
> >> >
> >> >On 19/11/12 20:49, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >> >
> >> >>Tomaso,
> >> >>
> >> >>If I understand well, the idea is that tcmtf is not used in the
> >> >>satellite link, but only  in the "Internet" part. So the "Access
> >>Point"
> >> >>does not need to decompress the ROHC headers.
> >> >>
> >> >>I think that the key question is now: can this be included in the
> >> >>current
> >> >>draft-saldana-tsvwg-tcmtf-03 of tcmtf or would it require a
> >> >>specific draft?
> >> >>
> >> >>You say that the idea is different from the concepts in
> >> >>draft-saldana-tsvwg-tcmtf-03. If you could provide some reasons
> >> >>supporting this, it would be fine, I think.
> >> >>
> >> >>We also need feedback from the list in order to set this clear.
> >> >>
> >> >>Thank you very much,
> >> >>
> >> >>Jose
> >> >>
> >> >>> -----Mensaje original-----
> >> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> nombre
> >> >>> de Tomaso.deCola@dlr.de Enviado el: viernes, 16 de noviembre de
> >> >>> 2012
> >> >>> 16:31
> >> >>> Para: tcmtf@ietf.org
> >> >>> CC: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de;
> >> >>> Hartmut.Brandt@dlr.de; jsaldana@unizar.es
> >> >>> Asunto: [tcmtf] Some thoughts about new scenarios for tcmtf
> >> >>>
> >> >>>
> >> >>> Dear All,
> >> >>>
> >> >>> As discussed some time ago, satellite and wireless access =
network
> >> >>>can  be attractive network scenarios where tcmtf principles can =
be
> >> >>>exploited.
> >> >>> However, usual wireless and satellite encapsulation protocol
> >> >>>(between  IP and lower layers) already provide means to
> >> >>>multiplexing and "tunneling"
> >> >>> compressed flows.
> >> >>> In this respect, the application of tcmtf in these scenarios is
> >> >>>less
> >> >>attractive,
> >> >>> as it would introduce additional overhead, resulting in less
> >> >>>benefits from  the bandwidth-saving point of view. Hence, we
> >> >>>propose a deviation from  the tcmtf concepts, so that the access
> >> >>>network (wireless or satellite)
> >> >>keeps
> >> >>> untouched the protocol stack allowing the compression of data
> >> >>>flows through ROHC (for example). The access point serving as
> "bridge"
> >> >>>between  the access network and the second leg of the network =
(i.e.
> >> >>>Internet)  implements a dual stack, with PPPmux and IP tunneling
> >> >>>techniques, to  multiplex and tunnel the compressed flows coming
> >> >>>from the access  network. The final destination will obviously
> >> >>>implement a stack including  the three tcmtf ingredients
> >> >>>(compression, multiplexing, tunneling).
> >> >>>
> >> >>> The following diagram illustrates the idea: A wireless Node A
> >> >>> delivers
> >> >>data
> >> >>> to Node B though the wireless access networks and Internet.
> >> >>> As this idea substantially deviates from the concepts presented
> >> >>>in
> >> >>>draft-
> >> >>> saldana-tsvwg-tcmtf-03, we propose to dedicate an additional =
I-D
> >> >>>to this  idea, where implications on mobility and security =
should
> >> >>>be addressed as  well.
> >> >>>
> >> >>> What is your opinion?
> >> >>>
> >> >>> Best Regards,
> >> >>>
> >> >>> Tomaso
> >> >>>
> >> >>>
> >> >>>               Node B
> >> >>>
> >> >>>              +------------+
> >> >>> Node A
> >> >>>              | Appl.         |
> >> >>> +------------ +
> >> >>>              +------------+
> >> >>> | Appl.         |
> >> >>>                      | TCP/UDP |
> >> >>> +------------+
> >> >>>
> >> >>> +------------+ +------------+
> >> >>> | TCP/UDP |
> >> >>>Access
> >> >>Point
> >> >>>              |        IP        |
> >> >>> +------------+
> >> >>+-----------------------------+
> >> >>>              +------------+
> >> >>> |         IP       |
> >> >>|       Relay                              |
> >> >>>              |   ROHC      |
> >> >>> +------------+
> >> >>+----------------------------+
> >> >>>              +------------+
> >> >>> |  ROHC       |
> >|
> >> >>|  PPPmux   |
> >> >>>              |  PPPmux |
> >> >>> +------------+
> >> >>> +------------+ |
> >> >>Encaps         +------------+
> >> >>>              +------------+
> >> >>> | Encaps     |
> >|
> >> >>|  IPtunn.     |
> >> >>> |  IPtunn.  |
> >> >>> +------------+
> >> >>+---------------+------------+
> >> >>>              +------------+
> >> >>> |  L2/L1       |                                              |
> >>L2/L1
> >> >>|  L2/L1         |
> >> >>>              |  L2/L1       |
> >> >>> +------------+
> >> >>+---------------+------------+
> >> >>>              +------------+
> >> >>> |                                     |
> >> >>|
> >> >>>              |
> >> >>> |<------Wireless Access network-------->|
> >> >>|<------
> >> >>> Internet----------->|
> >> >>> |        (WLAN, Satellite, ...)                       |
> >> >>|
> >> >>> |
> >> >>>
> >> >>>
> >> >>>
> >> >>> ------------------------
> >> >>> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German
> Aerospace
> >> >>>Center Institute of Communications and Navigation | Satellite
> >> >>>Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso
> de
> >> >>>Cola, Ph.D.
> >> >>> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
> >> >>>tomaso.decola@dlr.de
> http://www.dlr.de/kn/institut/abteilungen/san
> >> >>>
> >> >>> _______________________________________________
> >> >>> tcmtf mailing list
> >> >>> tcmtf@ietf.org
> >> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>
> >> >>_______________________________________________
> >> >>tcmtf mailing list
> >> >>tcmtf@ietf.org
> >> >>https://www.ietf.org/mailman/listinfo/tcmtf
> >> >
> >> >
> >> >________________________________
> >> >
> >> >Este mensaje se dirige exclusivamente a su destinatario. Puede
> >> >consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo
> >> >electr=F3nico en el enlace situado m=E1s abajo.
> >> >This message is intended exclusively for its addressee. We only =
send
> >> >and receive email on the basis of the terms set out at:
> >> >http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> >_______________________________________________
> >> >tcmtf mailing list
> >> >tcmtf@ietf.org
> >> >https://www.ietf.org/mailman/listinfo/tcmtf
> >>
> >>
> >> ________________________________
> >>
> >> Este mensaje se dirige exclusivamente a su destinatario. Puede
> >> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico
> >> en el enlace situado m=E1s abajo.
> >> This message is intended exclusively for its addressee. We only =
send
> >> and receive email on the basis of the terms set out at:
> >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en =
el enlace
> situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send =
and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx


From Tomaso.deCola@dlr.de  Wed Nov 28 01:38:24 2012
Return-Path: <Tomaso.deCola@dlr.de>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B18321F8490 for <tcmtf@ietfa.amsl.com>; Wed, 28 Nov 2012 01:38:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.249
X-Spam-Level: 
X-Spam-Status: No, score=-8.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hcsv2y+nwebq for <tcmtf@ietfa.amsl.com>; Wed, 28 Nov 2012 01:38:22 -0800 (PST)
Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.33]) by ietfa.amsl.com (Postfix) with ESMTP id AB68321F842E for <tcmtf@ietf.org>; Wed, 28 Nov 2012 01:38:21 -0800 (PST)
Received: from DLREXHUB01.intra.dlr.de (172.21.152.130) by dlrexedge02.dlr.de (172.21.163.101) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 28 Nov 2012 10:37:55 +0100
Received: from DLREXMBX02.intra.dlr.de ([fe80::8cc6:b83e:ddc1:4e8b]) by dlrexhub01.intra.dlr.de ([::1]) with mapi id 14.02.0318.004; Wed, 28 Nov 2012 10:37:59 +0100
From: <Tomaso.deCola@dlr.de>
To: <jsaldana@unizar.es>, <fpb@tid.es>
Thread-Topic: [tcmtf] Some thoughts about new scenarios for tcmtf
Thread-Index: Ac3EDOy4duakoHOCR7KDbQibMeqaCQCeb0QAAB638AAAA5CPUAA6PJoAAPljbQAABILXAAAq/1eAACm3hAAAAh6K4A==
Date: Wed, 28 Nov 2012 09:37:58 +0000
Message-ID: <1A39DCC13AF3C14B83CD74124D4DCFC30BE8DBE1@dlrexmbx02.intra.dlr.de>
References: <010501cdcbf8$b98dac50$2ca904f0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2528314B3@EX10-MB2-MAD.hi.inet> <003a01cdcd4b$95485800$bfd90800$@unizar.es>
In-Reply-To: <003a01cdcd4b$95485800$bfd90800$@unizar.es>
Accept-Language: it-IT, de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.247.173.215]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2012 09:38:24 -0000

Jose,

Yes you are right, the idea is to have ROHC on the wireless segment, which =
already implement specific functionalities for multiplexing as part of the =
encapsulation protocol. The second leg of the network is instead using the =
tcmtf functions without ROHC, which is instead applied e2e (or at least unt=
il the end of the IP tunnel)

Regards,

Tomaso

------------------------=20
Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR)=20
German Aerospace Center=20
Institute of Communications and Navigation | Satellite Networks | Oberpfaff=
enhofen | 82234 Wessling | Germany=20
Tomaso de Cola, Ph.D.=20
Telefon +49 8153 28-2156 | Telefax=A0 +49 8153 28-2844 | tomaso.decola@dlr.=
de=20
http://www.dlr.de/kn/institut/abteilungen/san=20

-----Original Message-----
From: Jose Saldana [mailto:jsaldana@unizar.es]=20
Sent: Wednesday, November 28, 2012 10:35 AM
To: 'FERNANDO PASCUAL BLANCO'; Cola, Tomaso de
Cc: tcmtf@ietf.org
Subject: RE: [tcmtf] Some thoughts about new scenarios for tcmtf

Fernando,

If I understood well, the idea of Tomaso was this:

- The "left link" (wireless) between the satellite and the AP has its own w=
ell-defined protocols.
- That protocols include RoHC.
- So we can use tcmtf in the "right link" (Internet) between the AP and the=
 destination through the Internet.
- In the AP we don't need to decompress-compress RoHC.

However, I don't really know if Tomaso wanted to propose this. Let's wait f=
or his response.

Thanks,

Jose

> -----Mensaje original-----
> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] Enviado el: martes, 27=20
> de noviembre de 2012 13:40
> Para: jsaldana@unizar.es; Tomaso.deCola@dlr.de
> CC: tcmtf@ietf.org
> Asunto: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
>=20
> Jose,
>=20
>         I think that the proposition is to adopt within the original=20
> draft
what you
> have described as "Encaps". If so, the optimized path will be the path=20
> between node A and node B, and you can be sure that traffic within=20
> that "Encaps" is destined to node B. Given that, you can suppose that=20
> the TCMTF path is the path between A and B, having different=20
> tunnel/multiplex in
every
> scope (wireless and Internet), but maintaining the compress layer.
> With dynamic TCMTF signalling, somehow, every scope in the path will
select
> the most optimal tunneling/multiplex method in every hope (supposing=20
> that the Access Point is TCMTF-aware).
>=20
> Regards,
>=20
> Fernando Pascual Blanco
> Telef=F3nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>=20
>=20
>=20
>=20
> On 26/11/12 18:08, "Jose Saldana" <jsaldana@unizar.es> wrote:
>=20
> >Hi,
> >
> >I am trying to get some light about this. First, let us try to know=20
> >if the picture is correct. If you put this in Courier letters, I=20
> >think you can see it correctly (I attach it as an image, just in=20
> >case). Tomaso, is the picture right?
> >
> >Node A
> >Node B
> >+----------+
> >+------------+
> >| Appl.    |
> >| Appl.      |
> >+----------+
> >+------------+
> >| TCP/UDP  |
> >| TCP/UDP    |
> >+----------+
> >+------------+
> >|   IP     |                                  Access Point
> >|   IP       |
> >+----------+                             +----------------------+
> >+------------+
> >|  ROHC    |                             |       Relay          |
> >|   ROHC     |
> >+----------+                             +----------------------+
> >+------------+
> >|          |                             |          | PPPmux    |
> >|  PPPmux    |
> >| Encaps   |                             |  Encaps  +-----------+
> >+------------+
> >|          |                             |          |  IPtunn.  |
> >|  IPtunn.   |
> >+----------+                            +----------+-----------+
> >+------------+
> >|  L2/L1   |                             |  L2/L1   |  L2/L1    |
> >|  L2/L1     |
> >+----------+                             +----------+-----------+
> >+------------+
> >
> >           |                             |                      |
> >|
> >           |<--Wireless Access network-->|
> >|<------Internet-------->|
> >           |   (WLAN, Satellite, ...)    |                      |
> >|
> >
> >
> >So the first question is:
> >
> >Tomaso, is there a single connection from Node A to Node B, or the=20
> >Access Point has to distinguish different flows? Are all packets=20
> >travelling from A to B?
> >
> >If the answer is "Yes", then, as Fernando says, the AP does not need=20
> >to decompress/compress ROHC. It only needs to get a number of=20
> >packets, decapsulate them, and put them together into a multiplexed=20
> >packet with PPPMux.
> >
> >I think we should first set this clear in order to advance.
> >
> >Thanks,
> >
> >Jose
> >
> >> -----Mensaje original-----
> >> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] Enviado el: lunes,
> 26
> >> de noviembre de 2012 15:00
> >> Para: Michael Ramalho (mramalho); Tomaso.deCola@dlr.de
> >> CC: tcmtf@ietf.org; Matteo.Berioli@dlr.de; Hartmut.Brandt@dlr.de;=20
> >> jsaldana@unizar.es
> >> Asunto: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
> >>
> >> Hi All,
> >>
> >>         Actually Jose proposed the idea of developing two new drafts:
> >>the
> >> b)"Recommendations draft" and the c)"Dynamic Signaling Draft". That=20
> >>relay  between different tunneling, multiplexing or even compression=20
> >>capabilities  through the optimized path could be addressed to the=20
> >>c) draft as TCMTF  negotiation concepts in a multi-capability path.=20
> >>It should also be
> >mentioned in
> >> the original draft and recommended in the b) draft.
> >>         For example, for the satellite scenario, it would not be=20
> >>necessary
> >to
> >> decompress ROHC within the Access Point, since it should only take=20
> >>packets  multiplexed and tunneled in a way (the existing and=20
> >>efficient
> >encapsulation
> >> protocols, which could also be adopted within the original Jose=B4s=20
> >>draft as  different tunnel and multiplex options), and=20
> >>multiplex-tunnel them in  another way (as Michael says, acting as a=20
> >>tunnel and/or multiplex relay)  without see layer 3 headers.
> >>
> >> Regards,
> >>
> >> Fernando Pascual Blanco
> >> Telef=F3nica Global Resources
> >> Network Automation and Dynamization TECHNOLOGY PEOPLE GROUP F=20
> >> +34913128779 M +34682005168 fpb@tid.es
> >>
> >>
> >>
> >>
> >> On 21/11/12 16:59, "Michael Ramalho (mramalho)"
> <mramalho@cisco.com>
> >> wrote:
> >>
> >> >All,
> >> >
> >> >I think Tomaso's suggestion could occur as a separate section in=20
> >> >Jose's draft (draft-saldana-tsvwg-tcmtf-03) for the case of where=20
> >> >the (TCMTF) tunnel endpoints use a different multiplexing layer=20
> >> >(where Jose has "PPPMUX or other mux protocols" in the draft).
> >> >
> >> >However, tunnel endpoints are hard enough to specify .. and now=20
> >> >you would need to know if there is a relay somewhere in-between=20
> >> >the tunnel endpoints that uses a different multiplexing technique.
> >> >
> >> >In other words, you would need to know EVEN MORE about the=20
> >> >capability of possible intermediate nodes (in this case that a=20
> >> >relay is possible between your TCMTF tunnel endpoints) . or=20
> >> >perhaps decide if a relay is needed if the existing TCMTF tunnel=20
> >> >endpoints do not use the same multiplexing layer (e.g., a "lossless t=
ranscode"
function).
> >> >
> >> >If we decide to add a section in Jose's draft, we would need to=20
> >> >provide guidance concerning how the endpoints are either=20
> >> >configured or negotiated. If we want TCMTF to be "simple" and "just c=
onfigured"
> >> >(e.g., on WAN edges) . then negotiation and possible insertion/use=20
> >> >of a relay is a pretty big complication to the document. However,=20
> >> >we SHOULD address this concern (how tunnel endpoints are found,=20
> >> >how we ensure relays remain on the end-to-end tunnel path) in the=20
> >> >document
> anyway!
> >> >
> >> >Jose/Tomaso: Do you have thoughts on how the TCMTF endpoints
> >> negotiate
> >> >the lower layers?
> >> >
> >> >Michael Ramalho
> >> >
> >> >-----Original Message-----
> >> >From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On=20
> >> >Behalf Of Tomaso.deCola@dlr.de
> >> >Sent: Tuesday, November 20, 2012 7:08 AM
> >> >To: fpb@tid.es
> >> >Cc: tcmtf@ietf.org; Matteo.Berioli@dlr.de; Hartmut.Brandt@dlr.de;=20
> >> >jsaldana@unizar.es
> >> >Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
> >> >
> >> >Hi Fernando,
> >> >
> >> >Yes you are right, the basic idea it to enable RoHC end-to-end (or=20
> >> >even in a subpart of the whole network) and using tcmtf tunneling=20
> >> >and multiplexing features only in the last segment of the network=20
> >> >(e.g., from the AP to the end-users).
> >> >The point is that the Access Point, which can be regarded as a=20
> >> >gateway in satellite networks, has to de-capsulate anyway the IP=20
> >> >datagrams incoming over the satellite link. As such, I don't see=20
> >> >much processing complexity on this node. On the other hand, the=20
> >> >use of tcmtf on an e2e basis in this scenario is not really=20
> >> >efficient, because the tunneling-multiplexing functions are in=20
> >> >fact already provided by the
> >> encapsulation protocol.
> >> >Over the satellite/wireless link.
> >> >With this I don't mean that e2e tcmtf is never profitable, but the=20
> >> >scenarios that include satellite/wireless access network certainly=20
> >> >require an "adaptation" of tcmtf concepts, as described in my
proposal.
> >> >
> >> >Regards,
> >> >
> >> >Tomaso
> >> >
> >> >------------------------
> >> >Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace
> >> Center
> >> >Institute of Communications and Navigation | Satellite Networks |=20
> >> >Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D.
> >> >Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |=20
> >> >tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
> >> >
> >> >-----Original Message-----
> >> >From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> >> >Sent: Tuesday, November 20, 2012 10:29 AM
> >> >To: jsaldana@unizar.es; Cola, Tomaso de; tcmtf@ietf.org
> >> >Cc: Berioli, Matteo; Brandt, Hartmut
> >> >Subject: Re: [tcmtf] Some thoughts about new scenarios for tcmtf
> >> >
> >> >Hi Tomaso, Jose,
> >> >
> >> >        I=B4m afraid I=B4m not able to view properly you ASCII=20
> >> >picture, but if I=B4m not misunderstanding you, you are proposing to=
=20
> >> >have a header compression
> >> >(ROHC) end to end, while having multiplexing and tunneling after=20
> >> >the satellite/wireless link (through the LAN with several layer 3=20
> >> >hops or through the Internet). So Jose, I think Tomaso is not=20
> >> >proposing to decompress ROCH in the access point, but in the Node B.
> >> >        Do you think that this would be more interesting than=20
> >> >using TCMTF e2e?, given that the AP will have to de-encapsulate=20
> >> >the existing multiplexing/tunneling method in wireless/satellite=20
> >> >links, and encapsulate using TCMTF in the other side. In terms of=20
> >> >bandwidth for sure, but how much? Do it compensate in terms of=20
> >> >processing
> capacity?
> >> >
> >> >Regards,
> >> >
> >> >Fernando Pascual Blanco
> >> >Telef=F3nica Global Resources
> >> >Network Automation and Dynamization TECHNOLOGY PEOPLE GROUP F=20
> >> >+34913128779 M +34682005168 fpb@tid.es
> >> >
> >> >
> >> >
> >> >
> >> >On 19/11/12 20:49, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >> >
> >> >>Tomaso,
> >> >>
> >> >>If I understand well, the idea is that tcmtf is not used in the=20
> >> >>satellite link, but only  in the "Internet" part. So the "Access
> >>Point"
> >> >>does not need to decompress the ROHC headers.
> >> >>
> >> >>I think that the key question is now: can this be included in the=20
> >> >>current
> >> >>draft-saldana-tsvwg-tcmtf-03 of tcmtf or would it require a=20
> >> >>specific draft?
> >> >>
> >> >>You say that the idea is different from the concepts in=20
> >> >>draft-saldana-tsvwg-tcmtf-03. If you could provide some reasons=20
> >> >>supporting this, it would be fine, I think.
> >> >>
> >> >>We also need feedback from the list in order to set this clear.
> >> >>
> >> >>Thank you very much,
> >> >>
> >> >>Jose
> >> >>
> >> >>> -----Mensaje original-----
> >> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> nombre
> >> >>> de Tomaso.deCola@dlr.de Enviado el: viernes, 16 de noviembre de
> >> >>> 2012
> >> >>> 16:31
> >> >>> Para: tcmtf@ietf.org
> >> >>> CC: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de;=20
> >> >>> Hartmut.Brandt@dlr.de; jsaldana@unizar.es
> >> >>> Asunto: [tcmtf] Some thoughts about new scenarios for tcmtf
> >> >>>
> >> >>>
> >> >>> Dear All,
> >> >>>
> >> >>> As discussed some time ago, satellite and wireless access=20
> >> >>>network can  be attractive network scenarios where tcmtf=20
> >> >>>principles can be exploited.
> >> >>> However, usual wireless and satellite encapsulation protocol=20
> >> >>>(between  IP and lower layers) already provide means to=20
> >> >>>multiplexing and "tunneling"
> >> >>> compressed flows.
> >> >>> In this respect, the application of tcmtf in these scenarios is=20
> >> >>>less
> >> >>attractive,
> >> >>> as it would introduce additional overhead, resulting in less=20
> >> >>>benefits from  the bandwidth-saving point of view. Hence, we=20
> >> >>>propose a deviation from  the tcmtf concepts, so that the access=20
> >> >>>network (wireless or satellite)
> >> >>keeps
> >> >>> untouched the protocol stack allowing the compression of data=20
> >> >>>flows through ROHC (for example). The access point serving as
> "bridge"
> >> >>>between  the access network and the second leg of the network (i.e.
> >> >>>Internet)  implements a dual stack, with PPPmux and IP tunneling=20
> >> >>>techniques, to  multiplex and tunnel the compressed flows coming=20
> >> >>>from the access  network. The final destination will obviously=20
> >> >>>implement a stack including  the three tcmtf ingredients=20
> >> >>>(compression, multiplexing, tunneling).
> >> >>>
> >> >>> The following diagram illustrates the idea: A wireless Node A=20
> >> >>> delivers
> >> >>data
> >> >>> to Node B though the wireless access networks and Internet.
> >> >>> As this idea substantially deviates from the concepts presented=20
> >> >>>in
> >> >>>draft-
> >> >>> saldana-tsvwg-tcmtf-03, we propose to dedicate an additional=20
> >> >>>I-D to this  idea, where implications on mobility and security=20
> >> >>>should be addressed as  well.
> >> >>>
> >> >>> What is your opinion?
> >> >>>
> >> >>> Best Regards,
> >> >>>
> >> >>> Tomaso
> >> >>>
> >> >>>
> >> >>>               Node B
> >> >>>
> >> >>>              +------------+
> >> >>> Node A
> >> >>>              | Appl.         |
> >> >>> +------------ +
> >> >>>              +------------+
> >> >>> | Appl.         |
> >> >>>                      | TCP/UDP |
> >> >>> +------------+
> >> >>>
> >> >>> +------------+ +------------+
> >> >>> | TCP/UDP |
> >> >>>Access
> >> >>Point
> >> >>>              |        IP        |
> >> >>> +------------+
> >> >>+-----------------------------+
> >> >>>              +------------+
> >> >>> |         IP       |
> >> >>|       Relay                              |
> >> >>>              |   ROHC      |
> >> >>> +------------+
> >> >>+----------------------------+
> >> >>>              +------------+
> >> >>> |  ROHC       |
> >|
> >> >>|  PPPmux   |
> >> >>>              |  PPPmux |
> >> >>> +------------+
> >> >>> +------------+ |
> >> >>Encaps         +------------+
> >> >>>              +------------+
> >> >>> | Encaps     |
> >|
> >> >>|  IPtunn.     |
> >> >>> |  IPtunn.  |
> >> >>> +------------+
> >> >>+---------------+------------+
> >> >>>              +------------+
> >> >>> |  L2/L1       |                                              |
> >>L2/L1
> >> >>|  L2/L1         |
> >> >>>              |  L2/L1       |
> >> >>> +------------+
> >> >>+---------------+------------+
> >> >>>              +------------+
> >> >>> |                                     |
> >> >>|
> >> >>>              |
> >> >>> |<------Wireless Access network-------->|
> >> >>|<------
> >> >>> Internet----------->|
> >> >>> |        (WLAN, Satellite, ...)                       |
> >> >>|
> >> >>> |
> >> >>>
> >> >>>
> >> >>>
> >> >>> ------------------------
> >> >>> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German
> Aerospace
> >> >>>Center Institute of Communications and Navigation | Satellite=20
> >> >>>Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso
> de
> >> >>>Cola, Ph.D.
> >> >>> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |=20
> >> >>>tomaso.decola@dlr.de
> http://www.dlr.de/kn/institut/abteilungen/san
> >> >>>
> >> >>> _______________________________________________
> >> >>> tcmtf mailing list
> >> >>> tcmtf@ietf.org
> >> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>
> >> >>_______________________________________________
> >> >>tcmtf mailing list
> >> >>tcmtf@ietf.org
> >> >>https://www.ietf.org/mailman/listinfo/tcmtf
> >> >
> >> >
> >> >________________________________
> >> >
> >> >Este mensaje se dirige exclusivamente a su destinatario. Puede=20
> >> >consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo=20
> >> >electr=F3nico en el enlace situado m=E1s abajo.
> >> >This message is intended exclusively for its addressee. We only=20
> >> >send and receive email on the basis of the terms set out at:
> >> >http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> >_______________________________________________
> >> >tcmtf mailing list
> >> >tcmtf@ietf.org
> >> >https://www.ietf.org/mailman/listinfo/tcmtf
> >>
> >>
> >> ________________________________
> >>
> >> Este mensaje se dirige exclusivamente a su destinatario. Puede=20
> >> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo=20
> >> electr=F3nico en el enlace situado m=E1s abajo.
> >> This message is intended exclusively for its addressee. We only=20
> >> send and receive email on the basis of the terms set out at:
> >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede=20
> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3=
nico=20
> en el enlace situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send=20
> and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx

