[manet-dlep-rg] Session iniation and discovery

Rick Taylor <rick@tropicalstormsoftware.com> Fri, 22 November 2013 16:57 UTC

Return-Path: <rick@tropicalstormsoftware.com>
X-Original-To: manet-dlep-rg@ietfa.amsl.com
Delivered-To: manet-dlep-rg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 647C01AE3EE for <manet-dlep-rg@ietfa.amsl.com>; Fri, 22 Nov 2013 08:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.896
X-Spam-Level:
X-Spam-Status: No, score=0.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=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 aDBngewqhbaj for <manet-dlep-rg@ietfa.amsl.com>; Fri, 22 Nov 2013 08:57:40 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (unknown [188.94.42.120]) by ietfa.amsl.com (Postfix) with ESMTP id CAA4C1AE1B6 for <manet-dlep-rg@ietf.org>; Fri, 22 Nov 2013 08:57:39 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Fri, 22 Nov 2013 16:57:10 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: "manet-dlep-rg@ietf.org Group, (manet-dlep-rg@ietf.org)" <manet-dlep-rg@ietf.org>
Thread-Topic: Session iniation and discovery
Thread-Index: AQHO56PhU0eqH6pu2kCQ1yl2uPh86w==
Date: Fri, 22 Nov 2013 16:57:09 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F98FA5B5504@tss-server1.home.tropicalstormsoftware.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [manet-dlep-rg] Session iniation and discovery
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: Fri, 22 Nov 2013 16:57:41 -0000

Gents,

Am I right in thinking we are achieving some kind of consensus on session initiation and discovery?  My understanding of the proposal is:

Discovery:

1) Router SHOULD send 'Advertise' UDP messages on IANA assigned link-local multicast address:port at periodic interval ANNOUNCE_INTERVAL.
'Advertise' messages MUST contain the DLEP version TLV.
'Advertise' messages MAY contain alternate TCP address TLV.  (E.g. ipv4 fallback)
'Advertise' messages MAY contain alternate TCP port TLV. 
'Advertise' messages MAY contain secondary reliable transport protocol endpoint address TLV.  (E.g. SCTP address)

Initiation:

0) Router listens on a TCP port, the port SHOULD be the IANA assigned DLEP port.

1) Modem connects to a TCP endpoint either discovered from 'Advertise' messages, or from alternate discovery mechanism (e.g. mDNS), or a-priori configuration.

2) Modem MUST send 'Initialize' message.
'Initialize' message MUST contain DLEP version TLV.
'Initialize' message MUST contain Identification TLV.
'Initialize' message MUST contain for all mandatory DLEP metric TLVs with values.

2) Router MUST reply with 'Accept' message, or shut down the connection.
'Accept' message MUST contain DLEP version TLV.
'Accept' message MUST contain Identification TLV.
'Accept' message MUST contain Status TLV.  This will indicate: Success, Reject, etc... (TBD)
'Accept' message MAY contain secondary reliable transport protocol endpoint address TLV.  (E.g. SCTP address)

2a) If Status TLV is a failure: Router MUST and Modem SHOULD close the TCP connection.
2b) If Status TLV is a success: Session is established.

3) Router MAY stop any active discover process.

4) Router MAY stop listening for more connections on the TCP port.

Notes:

a) Stan probably has different names for the messages.
b) I have made the Router the TCP server in this example, because it forces the modem to announce it's capabilities/TLVs in the 'Initialize' message, and I believe it's the way Stan is leaning.
c) If the roles are reversed then the 'Accept' message must carry the mandatory TLVs, and an extra 'Unacceptable' message is required from the Router to Modem explaining why the Router closed the connection if it doesn't like the TLVs from the Modem.

Does this sound right?  Or am I way off?

I'd just like to get this part fixed as I have more topics up for debate, and I reckon we could announce this as progress on the WG list.

Rick