Re: [manet] DLEP with wireline links ?

Rick Taylor <rick@tropicalstormsoftware.com> Tue, 09 March 2021 13:39 UTC

Return-Path: <rick@tropicalstormsoftware.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5750B3A0C32 for <manet@ietfa.amsl.com>; Tue, 9 Mar 2021 05:39:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNBXRJ3Z9KY5 for <manet@ietfa.amsl.com>; Tue, 9 Mar 2021 05:39:53 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 192853A0C30 for <manet@ietf.org>; Tue, 9 Mar 2021 05:39:53 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::48e4:acbb:6065:8168]) by tss-server1.home.tropicalstormsoftware.com ([fe80::48e4:acbb:6065:8168%16]) with mapi id 14.03.0513.000; Tue, 9 Mar 2021 13:39:51 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Toerless Eckert <tte@cs.fau.de>, "manet@ietf.org" <manet@ietf.org>
Thread-Topic: [manet] DLEP with wireline links ?
Thread-Index: AQHXFCImtLO+WHrB9E6EPuZQpTIJbKp7qgAQ
Date: Tue, 09 Mar 2021 13:39:49 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801F5A405BC@tss-server1.home.tropicalstormsoftware.com>
References: <20210308135112.GA45917@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20210308135112.GA45917@faui48f.informatik.uni-erlangen.de>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2a02:1648:4000:120:f579:77ca:e81:3294]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/3fQdvGFrvlq35I3hF-BuVhC7v6E>
Subject: Re: [manet] DLEP with wireline links ?
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2021 13:39:56 -0000

Hi Toerless,

I would *love* the DSL community to take an interest in DLEP (from a purely personal perspective it could help make my home connection more stable, using a selection of the techniques you describe) but I'm not sure what the next step is.  I know there is an IETF/Broadband Alliance liaison, but I think it's mostly centred around YANG model alignment, and I'm not even sure the Broadband Alliance are the right SDO.

Anyone have any suggestions?

Rick



> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Toerless Eckert
> Sent: 08 March 2021 13:51
> To: manet@ietf.org
> Subject: [manet] DLEP with wireline links ?
> 
> Sory for asking a random question on a list i don't currently contribute to,
> but Rick Taylors  presenation about DLEP in RAW reminded me to ask this:
> 
> Has DLEP in the past year ever managed to proliverate into wireline L2
> modems/interfaces ?
> 
> I was always annoyed by the absence of a good 3 evice to modem signaling
> protocol on wireline and always thought DLEP was likely the most
> pragmatic approach, but i have never seen that it did proliferate.
> 
> Use-case example:
>  - (VAX)DSL learning of training rates for the L3 device to be able to
>    set up appropriate QoS, ingres shaper etc to support better than BE QoS.
> 
>  - Similarily, CPE equipment on FTTH signaling their contractual
>    limits to the router (typically you have less then the nominal speed of 1
> Gbps)
>    (today you can only effectively set up contract aware QoS when the router
>     is run by the SP and uses TR69 provisioning - AFAIK).
> 
>  - Level of Loss/FEC for example for proactive failover (when this is not all
>    integrated into the non-modular MIC on the router.
> 
>  - Nominal Link latency, technology/variation - e.g.: If a link is copper
>    on a pole instead of fiber in th ground, latency variation of links can be
>    up to 10% due to temperature changes (if i remember correctly examplee
> calculation),
>    that would be very good to know for any control/management plane
> building an
>    e.g.: detnet solution on top of such links.
> 
> Cheers
>     Toerless
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet