Re: [manet-dlep-rg] London meet up?

Henning Rogge <hrogge@gmail.com> Wed, 05 March 2014 20:22 UTC

Return-Path: <hrogge@gmail.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 EEFA81A0240 for <manet-dlep-rg@ietfa.amsl.com>; Wed, 5 Mar 2014 12:22:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dlq3hJ8NHMuf for <manet-dlep-rg@ietfa.amsl.com>; Wed, 5 Mar 2014 12:22:08 -0800 (PST)
Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2EC3F1A0224 for <manet-dlep-rg@ietf.org>; Wed, 5 Mar 2014 12:22:08 -0800 (PST)
Received: by mail-qa0-f41.google.com with SMTP id j5so1550625qaq.14 for <manet-dlep-rg@ietf.org>; Wed, 05 Mar 2014 12:22:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=GT9U4KEBIBaVkpKIh5zoKsn6/UDGlXieuSzs3cdDcqE=; b=r4bNtl7WSiEnuDTa6m1xUKNxpaxD60dlq5v+QAgJzwPzyiGAFj+6ooK8VYEgHJ0ILA ns3WZQo3qb2D9mGBz8N56bf8UnkeLKwt7v4JM3jC8/heiqMUvar3GOmdBROPyWfY+FaD W3kI8MtpG0ELvJoz/3W1Yb9w6FwEnEBrNqm9UXh1jh1ekBgktMNrsauWzgsuyKzhnuUF pQmshn/XhQC/PW2YhltksReMUXoSsYzBTE0yw1D6nQjHyHLktXYwtBeVzDbZ2/ryrbnV FGQoSO1AC9fUuu1vYZlrVUCrh5udONXeyFf0GNQ/P+2JON2MpDnm25hWb26+VV3Heg02 2h6A==
X-Received: by 10.140.92.213 with SMTP id b79mr4514822qge.108.1394050924350; Wed, 05 Mar 2014 12:22:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.130.2 with HTTP; Wed, 5 Mar 2014 12:21:44 -0800 (PST)
In-Reply-To: <FB821471-E223-41BE-8D38-24C54B2B92C5@cisco.com>
References: <38A5475DE83986499AEACD2CFAFC3F98FA6C34C0@tss-server1.home.tropicalstormsoftware.com> <480A632F-CB9E-4A62-ACDA-521C1A899049@inf-net.nl> <CAGnRvuqL8z+P5BJP-duyQo2BnTSpnkv7nDnOEdAQ1RfdXu7r+Q@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F98FA6C4B60@tss-server1.home.tropicalstormsoftware.com> <38A5475DE83986499AEACD2CFAFC3F98FA6C56BA@tss-server1.home.tropicalstormsoftware.com> <CAGnRvuotok8UC-=i9RU8RvAv_wcv1DE3ubRLqibWeDLF6KRuDA@mail.gmail.com> <FB821471-E223-41BE-8D38-24C54B2B92C5@cisco.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 5 Mar 2014 20:21:44 +0000
Message-ID: <CAGnRvupAoaLtvsHh6TLXvxsBnmrLMtPCZ-VKuxR=gVPxnchWDQ@mail.gmail.com>
To: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/manet-dlep-rg/AYkUAbJWAoHiVmp8xaTsA7H4vTM
Cc: "DLEP Research Group, \(manet-dlep-rg@ietf.org\)" <manet-dlep-rg@ietf.org>, Rick Taylor <rick@tropicalstormsoftware.com>
Subject: Re: [manet-dlep-rg] London meet up?
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: Wed, 05 Mar 2014 20:22:11 -0000

I wonder if we could allow a MAC address data TLV in the multicast
discovery peer offer.

It would solve a lot of headaches with DLEP Wifi radios in Adhoc mode.

Henning

On Wed, Mar 5, 2014 at 7:49 PM, Stan Ratliff (sratliff)
<sratliff@cisco.com> wrote:
> Henning,
>
> That's true. The data items would be in the "Peer Offer" response to the
> Multicasted Discovery. Those data items (IP address and Port) will have to
> move to the discovery message. Also, any a-priori configuration will need to
> be implemented in the router instead of the modem, but that's really an
> "implementation detail".
>
> Regards,
> Stan
> On Mar 5, 2014, at 1:19 PM, Henning Rogge <hrogge@gmail.com>
>  wrote:
>
> I just looked it up, we have no data items in the UDP discovery broadcast at
> all at the moment.
>
> Henning
>
> On Mar 5, 2014 5:36 PM, "Rick Taylor" <rick@tropicalstormsoftware.com>
> wrote:
>>
>> Hi Guys,
>>
>> Thank you all very much for a very productive meeting this afternoon.  I
>> include a write up of my notes, please correct me if I have missed anything
>> pertinent.
>>
>> Stan has committed to updating the session initiation description to place
>> the TCP server in the modem, so the initial part of the protocol is:  Modem
>> broadcasts UDP Hello packets containing version, ident and TCP address/port.
>> Router TCP connects, session initiation occurs via the new TCP connection.
>>
>> Credit windowing will stay in the document, but will be clearly marked as
>> an optional part of the protocol.  There was some concern raised over the
>> clarity of the current text which will need to be address before last call.
>>
>> Vendor extensions will be defined using a new Data Item, containing a OUI
>> (or something from an existing registry) and space for a payload.  There
>> will need to be some guidance verbiage to characterise what is a valid
>> vendor extension and what is not.
>>
>> There was clarification of what both ends of a DLEP session must do on
>> reciept of an unrecognized signal and data item.  For a data item, the
>> receiver MUST ignore the data item, for a signal the recipient MUST send an
>> error status signal and terminate the TCP connection.
>>
>> There will be no facility in DLEP v1 for vendor extended signals.  Any
>> extra signals will require an uplift of the verion of the protocol and
>> require a new draft.
>>
>> There will be no such thing as a Peer Characteristic Request.  This will
>> prevent abuse and misuse of the DLEP protocol to act as a configuration
>> mechanism.
>>
>> There was further discussion concerning multiple QoS flows with seperate
>> metrics across a single link.  This was agreed to be pushed out to another
>> draft after DLEP v1, after some analysis that the proposed approach
>> (heirachial data items) will not break existing DLEP v1 implementations.
>> Stan agreed to double check that the text specified 16bit length values for
>> all TLVs (data and signals).
>>
>> There was discussion about enumerating error codes, and potential error
>> text.  The status signal MUST include an error code, 0 being success, others
>> to be enumerated after close analysis of the protocol, plus and optional
>> free text field to carry loggable information, capped at 80 bytes, utf8
>> encoded.
>>
>> There was discussion of confidence values for metrics, and this was
>> rejected as a core DLEP mechanism, and the suggestion was to use an
>> extension data item TLV instead.
>>
>> In light of achieveing their goal of listing the outstanding points that
>> needed to be reolved before DLEP can make progress to WG last-call, and
>> actually achieving suitable consensus to resolve the outstanding issues to
>> the satisafaction of one of the authors present, the DT decided to not apply
>> for a continuation of their charter, and to instead announce "Mission
>> Complete"
>>
>> Cheers,
>>
>> Rick Taylor
>>
>>
>> _______________________________________________
>> manet-dlep-rg mailing list
>> manet-dlep-rg@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet-dlep-rg
>
> _______________________________________________
> manet-dlep-rg mailing list
> manet-dlep-rg@ietf.org
> https://www.ietf.org/mailman/listinfo/manet-dlep-rg
>
>