Re: [manet-dlep-rg] Session iniation and discovery

"Stan Ratliff (sratliff)" <sratliff@cisco.com> Fri, 22 November 2013 17:26 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B93F21AE00C for <manet-dlep-rg@ietfa.amsl.com>; Fri, 22 Nov 2013 09:26:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.026
X-Spam-Level:
X-Spam-Status: No, score=-10.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 EIJfuoWiH3os for <manet-dlep-rg@ietfa.amsl.com>; Fri, 22 Nov 2013 09:26:11 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id F071D1ADFBA for <manet-dlep-rg@ietf.org>; Fri, 22 Nov 2013 09:26:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3193; q=dns/txt; s=iport; t=1385141164; x=1386350764; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=JnaS0ipcifG7s8y2znL96WVZ1ccW7Xrs9rJSaKwkxHk=; b=UpkRLQTndF2W9RXP4h2sLjPbR3SvLqwkuxYvIJh53DnJ4vyG3Mih0dPU cOb/tnudzdjQ82C5iP5VyXXJ/Yaxtu9xz/rkBX6HIsRBXkOK9tJdsFapb 1GK6DQQoHj/dFUGBGgZVWeFIJ7FNV88PZke3kL+v4nNPFuPJ0tCRdrmSI w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwFAMSSj1KtJXG9/2dsb2JhbABZgwc4U7wWgSIWdIIlAQEBAwEBAQFrCwULAgEIRicLJQIEDgWHewYNwRgTBI5UMweDIIESA5gUkhKDKIIq
X-IronPort-AV: E=Sophos;i="4.93,753,1378857600"; d="scan'208";a="1551596"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by alln-iport-2.cisco.com with ESMTP; 22 Nov 2013 17:26:03 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id rAMHQ39i005868 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Nov 2013 17:26:03 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.200]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Fri, 22 Nov 2013 11:26:03 -0600
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
Thread-Topic: [manet-dlep-rg] Session iniation and discovery
Thread-Index: AQHO56PhU0eqH6pu2kCQ1yl2uPh865ox5SIA
Date: Fri, 22 Nov 2013 17:26:03 +0000
Message-ID: <A04DB055-D861-4332-B623-396422BE0422@cisco.com>
References: <38A5475DE83986499AEACD2CFAFC3F98FA5B5504@tss-server1.home.tropicalstormsoftware.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F98FA5B5504@tss-server1.home.tropicalstormsoftware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.102.41.113]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <B312A9D018EF9E4A9953ED91F940CC88@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "manet-dlep-rg@ietf.org Group, \(manet-dlep-rg@ietf.org\)" <manet-dlep-rg@ietf.org>
Subject: Re: [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 17:26:12 -0000

Rick, 

For 99.999% of this, please put me in the "+1" category. One small, extremely pedantic edit below… ;-)

On Nov 22, 2013, at 11:57 AM, Rick Taylor <rick@tropicalstormsoftware.com> wrote:

> 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.

    'Initialize' message MUST contain all mandatory DLEP metric TLVs, *and all optional metric TLVs supported by this modem*, with values.


Regards,
Stan

> 
> 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 
> _______________________________________________
> manet-dlep-rg mailing list
> manet-dlep-rg@ietf.org
> https://www.ietf.org/mailman/listinfo/manet-dlep-rg