Re: [manet-dlep-rg] DLEP Capabilities exchange

Henning Rogge <> Wed, 22 January 2014 14:48 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 54CC01A03FB for <>; Wed, 22 Jan 2014 06:48:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OqZC8OBN4b_I for <>; Wed, 22 Jan 2014 06:47:58 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400d:c00::234]) by (Postfix) with ESMTP id 4B8C71A00E7 for <>; Wed, 22 Jan 2014 06:47:58 -0800 (PST)
Received: by with SMTP id j15so509477qaq.25 for <>; Wed, 22 Jan 2014 06:47:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=O1zLSFSB8aIXwJWo2AQwj0o0Q4L07lzfxqKHXJB7T4M=; b=BYjugDF7QuQiE44V/uVBGJzaM/Gs5A8bCe+WneSvD+oISuW1U0HqjJDbjPXvNdjwov htI3cOUp6YefB9Tur72t9AFUHV7Wol0G6QUWZX+uf8C4XW2zNLa1hfb/n++/E80IZfLC NLzpX+uCmg+HBMgIVD7sypinVD4/tXSxSIt345NdA0i58Guq4z5gO1Ztm+y0Idepsw3E fzlYjAbf1l1+xjD27pbLJgosnINitYj/JcRoePpn+QrBmkBLR3F4CqXbr6DcYwcFHWub rqhOlIgjiiPsxshiGtPgMvkUyp7TQ88dZPD2FbJvWPLfIAfj5BeFLuVu6HFKj00Ftgzv kxrA==
X-Received: by with SMTP id i5mr2844115qay.75.1390402077593; Wed, 22 Jan 2014 06:47:57 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Wed, 22 Jan 2014 06:47:37 -0800 (PST)
In-Reply-To: <>
References: <> <> <>
From: Henning Rogge <>
Date: Wed, 22 Jan 2014 15:47:37 +0100
Message-ID: <>
To: "Stan Ratliff (sratliff)" <>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 22 Jan 2014 06:53:11 -0800
Cc: "\(\) Group" <>, Teco Boot <>
Subject: Re: [manet-dlep-rg] DLEP Capabilities exchange
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DLEP Radio Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 22 Jan 2014 14:48:00 -0000

Something like a series of (boolean?) flags that tell the other side
of the DLEP session "hey, I can do X!" or "I am Y, please remember
this" ?

Henning Rogge

On Wed, Jan 22, 2014 at 3:22 PM, Stan Ratliff (sratliff)
<> wrote:
> Teco,
> Yeah, we're on the same page in that this isn't a negotiation. This is just giving the router and the modem some ways to signal the other that (for lack of a better term) "I'm special in some way" - in my case below, the satellite network is more efficient if the DR is co-located with the NC. This *could* be done with a-priori configuration, but it's easier if the NC announces itself (the NC function can, to an extent, be dynamically assigned). Please notice - I never used the word "negotiation" in the initial email… ;-) Perhaps I should have said a "Capabilities Announcement"?
> Regards,
> Stan
> On Jan 21, 2014, at 4:47 PM, Teco Boot <>
>  wrote:
>> Poeh, way back struggling with this.
>> Yes, this kind of information exchange is useful. But why would this example need negotiation? Just sending the TLV is OK, and routers can drop it or use it at own willing.
>> For for example a BW allocation sub protocol, I can imagine both modem and router MUST first agree before bothering each other with a "foreign DLEP sub-protocol language". The negotiation SHOULD NOT terminate the DLEP session. And can take place at any time after DLEP session setup.
>> The flow control and link characteristics request capabilities could be negotiated.
>> Teco
>> Op 21 jan. 2014, om 21:18 heeft Stan Ratliff (sratliff) <> het volgende geschreven:
>>> Gentlemen,
>>> Well, sigh…  I've been frankly trying to avoid this, but it's a subject I want to breach - if not for DLEP-05, then maybe for an 06.
>>> I've been thinking again about some exchange of capabilities. Not for a DLEP session startup, but to cover some specific use cases. The first one I'll throw out is this:
>>> Consider a deployment using OSPF, over satellite. That OSPF network is defined as a standard broadcast (Ethernet) segment, with a Designated Router (DR) and a Backup DR (BDR). In the satellite implementation I'm considering, it would be a good thing if the DR was co-located with the SatCom "Network Controller".
>>> So, I'm thinking about a capabilities exchange, where the modem (the satcom terminal) tells the router "I'm the NC". This would, in turn, cause the connected router to be "very willing" (whatever that means) to be the DR in an OSPF election (the next election that occurs on this link)… There would also have to be an "I'm NOT the NC anymore" message that flows from modem to router if/when that function is reassigned in the network.
>>> I'm sure there are other cases. Let's see if we can make a run at enumerating (and hopefully "generalizing") them.
>>> Regards,
>>> Stan
>>> _______________________________________________
>>> manet-dlep-rg mailing list
> _______________________________________________
> manet-dlep-rg mailing list