[manet-dlep-rg] DLEP Capabilities exchange

"Stan Ratliff (sratliff)" <sratliff@cisco.com> Tue, 21 January 2014 20:18 UTC

Return-Path: <sratliff@cisco.com>
X-Original-To: manet-dlep-rg@ietfa.amsl.com
Delivered-To: manet-dlep-rg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id C76241A01B9 for <manet-dlep-rg@ietfa.amsl.com>; Tue, 21 Jan 2014 12:18:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.036
X-Spam-Status: No, score=-15.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id aKywLyaS4RjJ for <manet-dlep-rg@ietfa.amsl.com>; Tue, 21 Jan 2014 12:18:27 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com []) by ietfa.amsl.com (Postfix) with ESMTP id 70BB51A0182 for <manet-dlep-rg@ietf.org>; Tue, 21 Jan 2014 12:18:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1272; q=dns/txt; s=iport; t=1390335507; x=1391545107; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=HfoRChtBPJGLr3kzmYT5VeLClIsfiEXQBRbYFJNRDcw=; b=MsV5nAXQbFioq6KPjtQ7NpNucA0flEGfHhTirvkn8k6yvk0pPhLsqzBX AJIsvcF8atSVqKFd7Jj9kh8iOv5scJMUBOYSqz7VD8JOFMXLOkGJrFqB6 bulxDMhRram69EE1yChUsi44IYrGdxZ2Tf+T0uStCp/OmBtmvFvZtJ+Vl w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAHrV3lKtJXG+/2dsb2JhbABZgwuBDqlskxwWdIIsgQsBgQAnBIgYl2irMheOFIQWgRQEmCKSGIMtgio
X-IronPort-AV: E=Sophos;i="4.95,697,1384300800"; d="scan'208";a="298763877"
Received: from rcdn-core2-3.cisco.com ([]) by rcdn-iport-8.cisco.com with ESMTP; 21 Jan 2014 20:18:09 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com []) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0LKI9xD011583 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <manet-dlep-rg@ietf.org>; Tue, 21 Jan 2014 20:18:09 GMT
Received: from xmb-aln-x03.cisco.com ([]) by xhc-aln-x11.cisco.com ([]) with mapi id 14.03.0123.003; Tue, 21 Jan 2014 14:18:09 -0600
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: "(manet-dlep-rg@ietf.org) manet-dlep-rg@ietf.org Group" <manet-dlep-rg@ietf.org>
Thread-Topic: DLEP Capabilities exchange
Thread-Index: AQHPFuXmq7CDqyipwE+xoJktNrryzg==
Date: Tue, 21 Jan 2014 20:18:08 +0000
Message-ID: <3BC2E4AC-CD56-4AEA-AB12-4197ABC3611F@cisco.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F5063DE92A3E8C49BDAD14504288A5D9@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [manet-dlep-rg] DLEP Capabilities exchange
X-BeenThere: manet-dlep-rg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DLEP Radio Group <manet-dlep-rg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet-dlep-rg>, <mailto:manet-dlep-rg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet-dlep-rg/>
List-Post: <mailto:manet-dlep-rg@ietf.org>
List-Help: <mailto:manet-dlep-rg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet-dlep-rg>, <mailto:manet-dlep-rg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 20:18:29 -0000


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.